The Deep Dive Fix Files: Founding Archive

This is a weekly roundup of significant sports tech problems that the endurance community has encountered and, where possible, resolved. Each entry covers the issue, the affected hardware or software, and the current best fix or workaround known to the community.

---

Forerunner 970 Random Vibrations with No Notification Behind Them

Forerunner 970 owners are reporting random, persistent haptic alerts with no notification, alarm, or activity event behind them. The watch buzzes during runs, during walks, and sometimes while navigating to start an activity. The screen looks normal throughout. Several owners report the vibrations correlate with structured workout pace alerts; one owner lost a Stryd connection at the same moment the vibrations started. The issue appeared shortly after the FR970 launched in early 2025, briefly went quiet, then returned for several owners after firmware 15.52 and has continued into 16.37.

Garmin engineering acknowledged the reports and asked for systematic data including log files from affected devices. No firmware fix had shipped as of the time of writing.

The workaround with the highest success rate is pausing and resuming the activity. Holding the light button to open the controls menu, or opening the music menu to trigger a brief haptic, also clears the phantom vibration for several owners. A full power cycle is the last resort if the other approaches do not work.

---

Edge 1050 Sensors Not Reconnecting After Pause or Sleep

Edge 1050 owners are reporting that ANT+ and Bluetooth sensors fail to reconnect after the device wakes from sleep or auto-pause. The issue is most pronounced on firmware 30.18 but has been present across several earlier versions. Sensors affected include the Garmin HRM, Quarq power meter, Favero RS-2 pedals, Shimano Di2, Varia RTL515 radar, Polar Verity Sense, and Trek Ion 200 RT.

One owner identified a specific trigger: if the Varia is already on or in standby when the Edge wakes, the Edge gets stuck on the Garmin logo screen and fails to reconnect to anything.

The most reliable workaround is to power the Edge fully off at a coffee stop rather than use sleep mode. The in-progress activity is preserved when the Edge is restarted, and sensors reconnect cleanly. A slower alternative is to stop the activity, restart the device, and then resume the activity. Garmin support’s standard troubleshooting advice received a negative response from the community.

---

Fenix 8 HRV Dropping and Training Status Stuck on Strained Since Firmware 21.25

Fenix 8 owners are reporting HRV values dropping and training readiness locked in Strained status since firmware 21.25. Sleep scores are affected alongside HRV. The issue persists into firmware 21.39.

The most useful evidence in the discussion comes from one owner who wore a Tactix 7 AMOLED running older 25.11 software for a night. Their overnight HRV average jumped from the high twenties to the mid forties, and training status returned from Strained to Unbalanced. A Tactix 8 Solar sharing the Fenix 8 firmware family tracked with the Fenix 8 readings. That comparison points to the firmware rather than the user’s physiology as the cause.

A counter view is worth noting: HRV naturally drops in winter and spring due to seasonal hormonal changes, and similar complaints surface annually. The cross-watch comparison makes a purely seasonal explanation harder to sustain but does not rule it out entirely.

One workaround surfaced: a factory reset to defaults restored HRV and sleep scores to normal for at least one owner. The reset does not carry forward on all devices and is not confirmed as a permanent fix.

---

Forerunner 27.09 Firmware Bugs: FR165 Fixed, FR255 / FR265 / FR955 / FR965 Still Waiting

Garmin’s January 2026 firmware 27.09 produced documented faults across the Forerunner 165, 255, 265, 955, and 965: step counts frozen at zero, sleep tracking disappearing, heart rate readings flatlined or wildly inaccurate, slow HR response during intensity changes, and cadence locking during runs. The Forerunner 165 was worst affected and received a follow-up 27.10 update addressing the faults. The FR255, FR265, FR955, and FR965 remained on 27.09 with no comparable fix shipped at the time of writing.

The pattern is not universal. A significant proportion of owners on the same firmware report no issues, which suggests the bug activates only under specific conditions, possibly related to a hardware revision, a sensor calibration state, or a particular activity pattern. Garmin support acknowledged the reports and asked for log files.

A hard reset, holding the power button until the watch shuts down and restarting, clears the symptoms for some owners. A full factory restore does not roll back the firmware and does not fix the underlying sensor behaviour for most.

---

HRM 600 Chest Strap Dropping Heart Rate and Respiration Data on BLE Secure

Garmin HRM 600 owners are reporting repeated heart rate dropouts and missing respiration data when the strap is connected via BLE Secure. The HR reading tanks from a real-world value such as 150 bpm to roughly half for stretches of seconds to minutes, while respiration data drops out. The sensor still shows as connected throughout. Tempo runs and interval sessions are most affected.

The fault is specific to BLE Secure. Owners who have switched the strap to ANT+ report the dropouts stop. The cost is the loss of Running Economy and several newer metrics that require BLE Secure. Battery draw on the watch is also different: approximately 7 percent per 90 minutes on ANT+ versus 11 percent on BLE Secure.

Attempts that have not consistently fixed it: thoroughly wetting the electrodes, electrode gel, different shirts, different strap positions, shaving the chest, disabling phone Bluetooth during the run, and ruling out 2.4 GHz interference. The most reliable in-run workaround is pressing the capsule button mid-run, which briefly reconnects and clears the dropout. Firmware updates to the FR970 and Fenix 8 have not resolved it on either platform.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

---

Edge 1050 Screen Blanking for a Fraction of a Second Mid-Ride

Edge 1050 owners are reporting the screen going black for roughly a second during rides, then coming back on the same page it was showing. The blank is not tied to sensor activity, recording state, or button presses. It can happen mid-ride, at a coffee stop, and when the Edge is sitting idle on a desk. Visually the screen wipes from bottom to top in a flash; the wake-up is instant with no fade.

The behaviour has been present across multiple firmware versions from launch through the current 30.18. Some owners on beta 28.13 reported the issue went away after a replacement unit; others did not. Garmin engineering acknowledged the reports and asked for video evidence, which is difficult because the blank is too short to capture in normal helmet-cam framing.

Standard troubleshooting, including power cycling, factory reset, and firmware sync via Garmin Express, does not stop the blanking for most owners.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

---

Varia RTL515 Alerting Only Once Per Vehicle Stream and Firing False Positives After Stops

A long-running safety discussion among Varia owners has surfaced a design behaviour rather than a bug: the Varia RTL515 produces a single audible alert for the first vehicle in a stream, with no further alerts for following vehicles until the entire stream has cleared. The radar detects each vehicle correctly and the head unit screen updates, but the audible cue stays silent.

The complaint is that on busy roads, a rider who has had to look away hears the first beep, glances back, sees one car, and assumes the road is clear. The screen continues to show additional approaching vehicles but with no audible prompt.

A related and separate fault: the RTL515 fires a rapid series of false positives in the first 30 seconds after restarting from a complete stop, even on an empty road or trail. The issue tends to clear once the ride is moving steadily. Saddle-bag interference has been tested and ruled out for most owners.

The RCT715, the camera-equipped variant, has a different known behaviour: incident detection can fire on road bumps or fast descents when paired with non-Edge head units, because the onboard accelerometers handle incident logic without the benefit of the Edge’s sensor array. Pairing with an Edge head unit transfers incident detection to the head unit and removes most of those false positives.

---

Connect IQ Data Fields Stuck in the Install Loop and Failing to Appear on the Device

Garmin owners hit a recurring failure when installing or updating Connect IQ data fields. On the device, the store shows the blue Install button, switches to Installing, then drops back to the blue Install button. The data field never appears under the device menu, and the Connect IQ app lists it as not installed. Updating already-installed fields often ends in a permanent waiting in queue message. The fault affects current devices including the Edge 1050, Forerunner 965, and Fenix 7 and is not tied to a single firmware version.

The underlying cause is a broken link between the Garmin Connect app and the Connect IQ app, leaving the device effectively unassociated from the store. Standard steps including clearing cache, logging out and back in, and reinstalling the Connect IQ app alone usually do not fix it.

Three workarounds have a track record. The one with the highest success rate: uninstall the Garmin Connect app entirely, open the Connect IQ store app so it logs in cleanly, then reinstall Garmin Connect, which relinks all devices automatically. A second option is to create a spare activity profile with no Connect IQ data fields in it, switch to it, run the installs and updates, then switch back. A third is to use the web store at apps.garmin.com rather than the mobile app, then sync the device.

---

Spotify Made for You Playlists Syncing Empty to Garmin Music Watches

Garmin Music watch owners report Spotify’s algorithmically generated playlists, including Discover Weekly, Daylist, and the BPM-matched mixes such as 170 BPM Run, syncing to the watch but showing zero songs once there. The same playlists are full and playable on the phone and desktop. Manually built playlists sync normally; only the Made for You type fails.

This hits the running use case directly, since the BPM-matched mixes are exactly what many runners load to hold cadence. The issue has been reported on the Fenix 8, Forerunner 265, Forerunner 245 Music, and Venu 3. Several owners noticed it began after a watch firmware update, with firmware 21.19 cited on the Fenix 7S, or after Garmin Connect prompted a fresh Spotify sign-in. Both point to an authorisation handshake between Spotify and Garmin rather than a storage or wifi fault.

The workaround with the best track record: on the Spotify desktop app, open the Made for You playlist, select all tracks using Ctrl+A or Cmd+A, and drag them into a new ordinary playlist of your own. That manual copy syncs to the watch normally. The copy is a static snapshot and will not refresh as Spotify updates the original, but it resolves the empty playlist problem immediately.

Standard steps including reinstalling the Spotify Connect IQ app, a factory reset, and changing the wifi network do not fix the empty playlist behaviour for most owners.

---

Garmin Connect+ Nutrition Tracking: Specific Bugs and the Workarounds Owners Have Found

Garmin Connect+ Nutrition tracking launched in January 2026 as the headline reason to subscribe. Four months in, owner feedback identifies several specific faults alongside the general workflow complaints. Foods entered outside a designated meal-time window default to the wrong time and require manual correction. Photo recognition struggles with multiple servings of the same item, logging three chicken wings as one. Barcode data outside the United States is incomplete or missing for many common products. At least one owner reports food being logged on the wrong calendar date entirely.

At least one owner reports product recognition working correctly for 99 percent of their scans, with the only frustration being an inability to delete items from the saved foods list.

The comparison against existing nutrition apps is relevant because Connect+ Nutrition is priced partly as a replacement for them. At $69.99 per year, it undercuts MyFitnessPal Premium at approximately $80 per year, and it brings food data into the same app as workouts and recovery. It lags both MyFitnessPal and Cronometer on recipe creation, custom meal categories, and overall workflow refinement.

Workarounds for the date bug: enter foods immediately after a meal rather than in advance or retrospectively. For barcode misses outside the United States, manual search by name or the photo option provides a fallback. The missing ability to delete saved foods has no workaround at the time of writing.

---

Frequently Asked Questions

Why is my Forerunner 970 vibrating for no reason?

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’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.

Why is my FR970 buzzing randomly mid-run?

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.

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

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.

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

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.

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

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.

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

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.

Why is my Forerunner 265 step count stuck at zero?

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.

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

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.

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

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.

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

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.

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

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. Some owners report improvement after a device replacement, others do not.

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

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, some resolved, some not, suggests there may be a hardware component, but the firmware cannot be ruled out without a confirmed fix.

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

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. Being aware of the limitation and treating the first beep as a cue to check the screen, rather than assuming it indicates a single vehicle, is the practical workaround.

Why does my Varia beep repeatedly after I stop?

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 for 30 seconds after moving off before relying on the alerts as accurate is the practical approach.

Why are my Connect IQ data fields not installing?

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.

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

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.

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

Garmin’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’s contents into a new ordinary playlist in the Spotify desktop app; that copy syncs to the watch correctly.

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

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.

Is Garmin Connect+ Nutrition worth it to replace MyFitnessPal?

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.

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

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.

Browse every issue in the archive at the Deep Dive Fix Files hub.

Last Updated on 5 June 2026 by the5krunner