Question 1

Why is my Forerunner 970 vibrating for no reason?

Accepted Answer

The Forerunner 970 has a documented phantom vibration fault where the watch buzzes with no notification, alarm, or activity trigger behind it. It affects some owners on firmware 15.52 and 16.37 and has been present since the watch&#8217;s launch. The most effective in-activity response is to pause and resume the activity, which clears the vibration for most owners. A full power cycle resolves it in more persistent cases. Garmin engineering is aware and has requested log files from affected devices.

Question 2

Why is my FR970 buzzing randomly mid-run?

Accepted Answer

Random buzzing on the Forerunner 970 during a run is the same phantom haptic fault. Some owners find it correlates with structured workout pace alerts or sensor dropout events, though the watch produces no visible notification. The pause-resume workaround stops it in most cases. If the vibrations persist after a power cycle, the Garmin forum thread has the most current owner-reported fixes.

Question 3

Why won't my Edge 1050 sensors reconnect after a pause?

Accepted Answer

The Edge 1050 has a documented fault on firmware 30.18 and earlier where ANT+ and Bluetooth sensors fail to re-establish after the device sleeps or auto-pauses. The most reliable workaround is to power the Edge fully off at a coffee stop rather than using sleep mode. The active ride is preserved when the Edge restarts and sensors reconnect cleanly on power-up.

Question 4

How do I stop my Edge 1050 sensors dropping out after a coffee stop?

Accepted Answer

Switch from using the sleep mode to a full power-off at stops. Hold the power button to shut the Edge down, then restart it when you are ready to ride. The in-progress activity saves and resumes without data loss. If the Varia radar is on or in standby when the Edge wakes, this can trigger a complete failure to reconnect; powering off and on resolves it cleanly each time.

Question 5

Why is my Fenix 8 always showing Strained training status since the last firmware update?

Accepted Answer

A fault in Fenix 8 firmware 21.25 and later versions has produced locked Strained or Unproductive training status and depressed HRV readings for a significant proportion of owners. The issue persists into firmware 21.39. A factory reset has restored normal HRV for at least one owner, though results vary. The fault is associated with the firmware rather than with user physiology, based on cross-watch testing where owners moved to a device running different firmware and saw HRV return to normal.

Question 6

Why has my Fenix 8 HRV dropped after a software update?

Accepted Answer

HRV suppression on the Fenix 8 following a firmware update has been specifically linked to the 21.25 release, though the pattern of seasonal HRV variation means some cases may have a physiological explanation. If the drop coincided closely with a firmware update and persists across weeks rather than cycling naturally, the firmware fault is the more likely cause. A factory reset is the most substantive workaround currently known.

Question 7

Why is my Forerunner 265 step count stuck at zero?

Accepted Answer

Step counts freezing at zero on the Forerunner 265, 955, and 965 are a known fault associated with firmware 27.09. The Forerunner 165 received a corrective update in firmware 27.10; the other affected models were still awaiting a similar fix at the time of writing. A hard reset, holding the power button until the watch shuts down and restarting, clears the symptom for some owners temporarily.

Question 8

Why did my Forerunner sleep tracking stop working after the 27.09 update?

Accepted Answer

Sleep tracking disappearing is part of the same 27.09 firmware fault that affects step counting, heart rate accuracy, and cadence detection on the FR255, FR265, FR955, and FR965. The FR165 version of the fault was fixed in 27.10. A hard reset clears it temporarily for some owners. The underlying issue requires a firmware update from Garmin to fix permanently.

Question 9

Why is my HRM 600 heart rate dropping to half during a run?

Accepted Answer

The HRM 600 has a documented dropout fault on BLE Secure connections where the HR reading tanks to approximately half the actual value for periods of seconds to minutes, with no change in the connection status. The fault is specific to BLE Secure; switching to ANT+ stops the dropouts. The cost of switching is losing Running Economy and several other metrics that require BLE Secure. Pressing the capsule button mid-run temporarily reconnects the strap and clears the dropout for the immediate session.

Question 10

Should I use ANT+ or BLE Secure for the HRM 600?

Accepted Answer

ANT+ is more stable and eliminates the dropout fault, but loses Running Economy, Lactate Threshold estimation, and several newer metrics that require BLE Secure. The choice depends on whether those metrics matter to your training. If you run with a structured heart rate focus and do not use Running Economy, ANT+ is the reliable option. If Running Economy is part of your data set, BLE Secure is required and the capsule button workaround is the best available mitigation.

Question 11

Why does my Edge 1050 screen flash off mid-ride?

Accepted Answer

The Edge 1050 has a documented screen blanking fault where the display goes black for less than a second and then returns to the active page. It is not tied to a specific action, recording state, or sensor event and occurs on firmware 30.18 and earlier versions. Garmin engineering has acknowledged the reports but has not confirmed a fix. Standard troubleshooting including power cycling and factory reset does not resolve it.

Question 12

Is the Edge 1050 screen blanking a hardware or software fault?

Accepted Answer

The cause has not been officially confirmed by Garmin. The pattern, which occurs at random and reproduces on some replacement units, does not point definitively to either hardware or firmware. The mix of outcomes after replacement units suggests there may be a hardware component, but the firmware cannot be ruled out without a confirmed fix.

Question 13

Why does my Varia only beep once when there are multiple cars behind me?

Accepted Answer

The Varia RTL515 is designed to alert once for the first vehicle in a stream, not once per vehicle. Subsequent vehicles in the same stream do not trigger additional audible alerts, though they appear on the head unit screen. This is a design behaviour rather than a fault. Treating the first beep as a cue to check the screen, rather than assuming it indicates a single vehicle, is the practical workaround.

Question 14

Why does my Varia beep repeatedly after I stop?

Accepted Answer

The RTL515 fires a series of false positive alerts in the first 30 seconds after restarting from a complete stop, even on empty roads or off-road trails. The false positives clear once the bike is moving steadily. This is a known behaviour and is not triggered by saddle bag position or electrical interference. Waiting 30 seconds after moving off before relying on the alerts as accurate is the practical approach.

Question 15

Why are my Connect IQ data fields not installing?

Accepted Answer

The most common cause is a broken link between the Garmin Connect app and the Connect IQ app following a Garmin Connect update. The install button cycles between Install and Installing without the field ever appearing on the device. The fix with the highest success rate is to uninstall Garmin Connect entirely, open the Connect IQ store app so it authenticates cleanly, and then reinstall Garmin Connect, which re-establishes the device association automatically.

Question 16

Why does Connect IQ say 'waiting in queue' when I try to update?

Accepted Answer

The waiting in queue message is the same broken device-store association. After reinstalling Garmin Connect as described above, the queue message clears and pending updates install. If the app reinstall does not resolve it, using the web store at apps.garmin.com and syncing the device bypasses the mobile app queue entirely and installs the update directly.

Question 17

Why are my Spotify Made for You playlists empty on my Garmin watch?

Accepted Answer

Garmin&#8217;s integration with Spotify handles algorithmically generated playlists differently from manually built ones. The Made for You playlists, including Discover Weekly, Daylist, and the BPM-matched running mixes, sync to the watch but arrive empty due to a fault in the authorisation handshake between Spotify and Garmin. Manually built playlists are not affected. The workaround is to copy the Made for You playlist&#8217;s contents into a new ordinary playlist in the Spotify desktop app; that copy syncs to the watch correctly.

Question 18

How do I get my Garmin to sync the 170 BPM running playlist from Spotify?

Accepted Answer

Open Spotify on a desktop, find the 170 BPM Run or equivalent playlist, select all tracks, and drag them into a new playlist of your own. Give the new playlist a name, save it, and then sync through Garmin Connect. The copy syncs where the original does not. Note that the copy is a static snapshot and will not update automatically as Spotify refreshes the original playlist. Repeating the process occasionally keeps the content fresh.

Question 19

Is Garmin Connect+ Nutrition worth it to replace MyFitnessPal?

Accepted Answer

Based on current owner experience, the feature works reliably for straightforward logging but has specific gaps that affect daily use. Barcode coverage outside the United States is incomplete, foods entered outside a meal window log to the wrong time, and there is no way to delete items from the saved foods list. At $69.99 per year it undercuts MyFitnessPal Premium at approximately $80, and it removes the third-party sync step. Whether those advantages offset the workflow gaps depends on how heavily you rely on recipe creation and custom meal categories, where MFP and Cronometer remain stronger.

Question 20

Why does Garmin Connect+ Nutrition log food on the wrong date?

Accepted Answer

A known bug causes food entries made at certain times or outside designated meal windows to appear on an incorrect calendar date. The workaround is to enter food immediately after a meal rather than in advance or retrospectively, which reduces the likelihood of the date misattribution. Garmin has not confirmed a fix for this specific behaviour.

Category: Deep Dive Fix files

#0 The Deep Dive Fix Files: Week Ending 22 May 2026