#4 The Deep Dive Fix Files: Week Ending 19 June 2026

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.

---

Garmin Edge 540, 840 and 1040 stuck in a Saving Diagnostics boot loop after the TopoActive 2026.10 map update

The TopoActive 2026.10 map pack offered through Garmin Express installs, then crashes the unit the next time it loads a route or recalculates a reroute mid ride. After that the device drops into a roughly two second loop that flashes GARMIN and Saving Diagnostics, with no menu, no reset, and often no recognition over USB. Owners report it on the Edge 540, Edge 840, Edge 1040, Edge 1040 Solar and the Forerunner 970.

Hard reset routes do not work once the loop sets in, and Garmin Express will not see the device even when it reaches MTP mode. The recovery several owners describe is to leave the unit untouched until the battery fully drains, which can take a day or two, then connect it by USB and let Garmin Express detect it for a repair or firmware reload. The fast reboot cycle is what blocks a normal connection, so the drain creates the window.

Owners whose units have not yet taken 2026.10 should hold off and keep their existing maps. When updating, run it through Garmin Express over USB rather than the WiFi Map Manager. The 2026.10 pack was pulled for the Edge 1050 after the xx40 reports, with a corrected loader referenced in a later release. Garmin staff have acknowledged the reports and asked affected owners to log the unit with their regional support office.

---

Suunto Vertical 2 and Race chest strap heart rate dropping out mid-activity after firmware 2.53.42

Since firmware 2.50.26, and still on 2.53.42, paired external straps connect at the start of an activity and then drop after a few minutes or after a pause. The reading on the watch freezes or flatlines, and the gap shows as a flat line in the app rather than empty data. Owners report it with the Suunto Smart belt, the Polar H10, Garmin straps and cheaper sensors, across the Vertical 2, Vertical, Race, Race S and Run.

The in-activity recovery is to open the sensor settings during the workout, disconnect the strap, then reconnect it, which brings the signal back without ending the session. One avoidable cause is sensor sharing: the Suunto Smart HR belt has a single Bluetooth channel, so a strap that is also live on a bike computer or a second device will not feed the watch at the same time. Remove the strap from the other device and pair it only to the watch before starting.

Suunto support has been replying with the standard steps, restart the watch and delete then re-pair the sensor, and several owners report the dropouts return immediately afterwards. Sending logs through the app right after a dropout, while the data is fresh, gives Suunto something to investigate.

---

Wahoo ELEMNT companion app crashing when selecting a planned workout on iPhone

The crash appears when you pick a planned workout in the ELEMNT companion app. The app closes immediately, while the workouts themselves still show on the head unit. One owner on an ELEMNT Roam 2 found that a plain delete from the home screen and a reinstall from the App Store did not clear it.

The step that worked was to delete the app from inside the app itself, through its own settings, and only then reinstall from the App Store. The order matters: removing it from within the app cleared the state that the home-screen delete left behind.

Treat this as a temporary recovery rather than a permanent fix. Other owners report the same crash recurring after months and returning after a clean reinstall, so a reliable fallback is to push the workout straight to the head unit, which keeps recording even when the companion app will not open.

---

Garmin Forerunner 955 and 265 not reconnecting to phone and missing the notification icon after firmware 28.05

Stable firmware 28.05 on the Forerunner 955 and the wider 165, 255, 265 and 965 family stops the watch reconnecting to the phone on its own once the two are separated and brought back together. New notifications flash briefly on the watch face, but the Bluetooth icon and the unread count do not return until you open Garmin Connect on the phone. Owners report the behaviour started only after 28.05 and was not present on 27.09.

The reliable in the moment recovery is to open Garmin Connect on the phone, which forces a resync and restores the connection until the next separation. One avoidable cause sits on the phone: several owners find the connection holds until the phone drops Garmin Connect from the background. Excluding Garmin Connect from battery optimisation keeps the background link alive for some owners, and iOS and Android behave differently after this update.

Rolling back is currently blocked. The 27.09 package is not offered for manual install, so the practical choices are the resync workaround or waiting for a corrected build.

---

Garmin Edge 850 and 1050 crashing with Saving Diagnostics when searching for an address on firmware 31.29

On firmware 31.29, typing an address or place name into the navigation menu and pressing search makes the unit display Saving Diagnostics and reboot. This is separate from the earlier 2026.10 map update boot loop, and the device rides and records normally until you open search. Owners report it on the Edge 850 and Edge 1050 across both 2025.10 and 2026.xx map versions, which points at the on-device search index rather than a single map file.

The workaround until the fix reaches the unit is to deactivate the map in the maps settings, which removes the search index that triggers the reboot. Routes built in Garmin Connect or Komoot and sent to the device still navigate, because a loaded course does not call the address search that crashes.

Garmin staff and owners on the thread confirm the crash is addressed in stable 31.30. Install it through Garmin Express over USB, or accept it over WiFi once the rollout reaches your unit, then test an address search before relying on it for a ride.

---

Garmin Edge 1050 Shimano Di2 1x time in gear showing 00:00:00 and NaN percent in Garmin Connect

On the Edge 1050 paired with a Shimano Di2 1x drivetrain, the shift count records correctly, but gear usage and time in gear show 00:00:00 and NaN percent on the Edge, in Garmin Connect Web and in Garmin Connect Mobile. A Di2 2x road setup on the same account displays gear usage as expected, so the fault is specific to 1x configurations. The owner who filed the report reproduced it on two separate 1x bikes, a GRX gravel build and an XTR mountain build.

The cause looks like Garmin’s calculation of rear sprocket usage for a 1x setup rather than a pairing problem, because the shift events themselves are captured and counted. The failure appears only when the device tries to turn those events into time in gear for a single chainring.

There is a usable workaround for reading the data. The same activity opens correctly on axs.sram.com, which renders the Shimano Di2 1x gear usage in full even though the groupset is not SRAM. Before recording, confirm the drivetrain is set as 1x with the correct front chainring and cassette, so the shifting data Garmin stores is accurate for the day a fix lands.

---

Wahoo ELEMNT Roam 3 power meter dropping out mid ride with Speedplay or Powerlink pedals

On the ELEMNT Roam 3 paired with Wahoo Speedplay or Powerlink power pedals, the power reading connects for about thirty seconds, drops for around ten, then repeats, and owners report thirty or more dropouts across a two hour ride. The same pedals hold a stable connection on a Bolt 2, on a Roam v2 and on a phone or tablet for Zwift, so the fault is isolated to the Roam 3.

The cause is the connection protocol. Wahoo power pedals pair to the Roam over Bluetooth by design, because Speedplay Power sends more data than the ANT profile carries, and the device offers no menu option to force ANT+. The Bluetooth link is the one that drops, and a factory reset does not change which protocol the pedals use.

A sequence forces the ANT+ connection. Unpair the pedals from the Roam, open the Wahoo app and connect the pedals to your phone over Bluetooth so the Bluetooth channel is occupied, then immediately search for sensors on the Roam. The Roam then detects the pedals as a generic power meter over ANT+ rather than as Wahoo Speedplay over Bluetooth. Pair that entry and confirm ANT+ in the device settings. The pedals can revert to Bluetooth on a later ride, so check the connection type before an important session.

---

Wahoo ELEMNT Roam 3 battery draining faster on long rides after a firmware update

An ELEMNT Roam 3 that ran rides of one hundred to two hundred kilometres and finished above fifty percent began arriving at fifteen percent after a one hundred and twenty kilometre ride of about five hours, and the change tracked a recent firmware update rather than any change in riding.

The first setting to rule out is the backlight. The auto maximum backlight option holds the screen near full brightness for far more of a ride and cuts runtime sharply. Set the backlight to a fixed low level or off rather than auto, then repeat a known route and compare, because this alone restores the figure for many owners.

Two other drains are worth checking. WiFi left on hunts for networks throughout a ride, so disable it when you are away from home. Frequent rerouting and a dense navigation file also raise consumption, so load the planned course before you start rather than searching on the device. If runtime stays low after those changes, record a ride with the settings fixed and send the file to Wahoo support for comparison against the pre-update baseline.

---

Wahoo Kickr Bike V1 refusing to shift and resistance spiking mid ride

On the Kickr Bike V1, shifting intermittently stops responding, and in one case the bike dropped to its easiest gear while resistance stayed very high. It can run many sessions with perfect shifting, then glitch, often just after an ERG session but also during a normal ride, all on Zwift.

The reliable in the moment recovery is to unplug the bike from the mains and plug it back in. Shifting returns to normal at once and the fault does not return for the rest of that session. The power cycle clears it cleanly, which is why a brief electronics glitch is at least as likely as a worn part.

The shifter buttons run through plug in cable connectors, and dirty or loose contacts produce erratic shifting. Wahoo’s routine maintenance is to clean those shifter plug contacts with isopropyl alcohol and reseat them. If the episodes become frequent rather than occasional, log them with Wahoo support with dates and the sessions involved so a hardware fault can be separated from a firmware glitch.

---

Garmin Fenix 8 randomly rebooting mid run after software 21.25

After updating a Fenix 8, Fenix 8 Pro or Enduro 3 to stable software 21.25, the watch reboots on its own during activities and during normal use. The reports cluster around scrolling through glances or the morning report, a track change in a connected music app, and cold conditions. The activity pauses at the crash and resumes after the restart, so recorded data is usually kept, but the interruption lands mid run, mid ride and during ski touring.

A full factory reset does not clear it for most owners, which points at the firmware rather than a single corrupted setting. The crash is reproducible enough that some owners trigger it by scrolling the same screens each time.

The fix most owners report is software 21.30. After installing it the reboots stop. Take it through Garmin Express over USB, or accept it over Bluetooth or WiFi once the rollout reaches your unit, then repeat the activity that crashed before to confirm. Garmin support gave a separate workaround to owners still on 21.25: recalibrate the buttons from the system settings.

---

Garmin Forerunner 970 heart rate jumping to a false high reading overnight and wiping sleep and HRV

On the Forerunner 970 the optical heart rate sensor sometimes stops tracking correctly overnight. The watch records you falling asleep, then resting heart rate jumps from the low 40s to a stuck reading near 119 for the rest of the night, stress sits at 100, and no HRV is recorded. Sleep, Body Battery and recovery figures for that night are lost.

The sensor does not recover on its own once this starts. It keeps returning invalid values until the watch is restarted, so the gap runs until morning if you do not intervene.

The workaround is a restart. Turning off sleep mode after waking returns the readings to normal, but the night is already gone. No menu setting prevents the crash, so the practical step is to catch it early, and a restart before bed reduces the chance of losing a full night of data.

---

Suunto Vertical 2 and Race S running pace zones resetting to default after a soft reset or firmware update

On the Suunto Vertical 2 and Race S, running pace zones revert to their default values after a soft reset and after each firmware update, including 2.53.42. Power zones are not affected. Only the running pace zones reset, which is enough to break pace zone alerts on the next run if you do not notice.

A Suunto moderator on the same thread notes that a reset should not change these settings, which places it as a firmware fault rather than expected behaviour. Several Vertical 2 and Race S owners reproduce it every time.

The workaround is to set the pace zones in the Suunto app rather than only on the watch, then resync after any reset or update so the values return. Check the zones before a session that depends on pace alerts, because the reset is silent. Power zones survive the reset, so a quick look at the pace zones alone confirms whether the values held.

---

Garmin Fenix 8 metronome beats stuttering and skipping during runs

On the Fenix 8 series, including the Fenix 8 Pro and Enduro 3, the metronome produces an uneven beat during activities. Beats pause, then several land close together, so the cadence you set drifts out of time. It is most obvious with audio tones through paired headphones, but the wrist tone and vibration drift too. Owners reported it across firmware going back to the early 12.x releases.

The fault has tracked the device since launch and appears tied to timing under load. It shows up most when the watch is doing other work at the same time, such as scrolling through glances or handling a track change in a connected music app. The Forerunner 970 shows the same behaviour, so the cause sits in the shared operating system rather than one model of watch.

Garmin marked it resolved in software version 22.35. Install that through Garmin Express over USB, or accept it over Bluetooth once the rollout reaches your unit, then repeat the session that drifted before to confirm the beat holds. For anyone not yet on 22.35, lowering the watch workload during a run reduces how often the beat slips. The recorded activity itself is not affected, only the audible and vibrating cue.

---

Garmin Venu 4 not pairing with the Schwinn IC4 or Bowflex C6 indoor bike and recording no metrics

The Venu 4 finds the Schwinn IC4 and the bike’s Bluetooth icon lights up, but pairing then times out with the message “Device not in pairing mode”, or it pairs yet sends no cadence, speed or distance into the Indoor Bike activity. The same failure hits the Bowflex C6, which uses the same hardware as the IC4. Owners report it on Venu 4 software 16.37 and 17.33, and note the same bike paired without trouble on the Venu 2 and Venu 3.

The failure reaches well beyond the Venu 4. Owners of the Fenix 7X Pro on 26.09, the Enduro 3, the Instinct 3 Solar and the Epix Gen 2 describe the identical timeout against the IC4. Garmin opened an investigation and has been contacting affected owners by email.

The reliable workaround is a bridge app. QZ on Android reads the bike over Bluetooth and rebroadcasts the metrics to the watch over ANT+ through a USB OTG transmitter, which restores cadence, speed and distance. It needs both the app and the dongle, so there is a cost and some setup. Without extra hardware, you can start a Cardio activity and turn on Heart Rate Broadcast, which sends your heart rate to the IC4 console, though it does not pull bike metrics back to the watch.

---

Garmin Edge 1050 stuck on Acquiring Satellites after a GPS firmware update

After a recent GPS firmware update to version 16.01, paired with software in the 31.18 to 31.29 range, the Edge 1050 sits on Acquiring Satellites and never gets a fix. At each start it shows updating GPS firmware then update successful, yet the satellite search never completes, so there is no GPS speed and no navigation. Owners saw it begin immediately after they accepted the GPS firmware update.

Connected sensors still work, so a speed sensor, power meter, heart rate strap and the barometric altimeter all report normally. That isolates the fault to the GPS firmware. Garmin support confirmed it as a known issue, separate from the 2026.10 map update boot loop.

Owners report that software 31.30 clears it, with the unit finding satellites in about thirty seconds afterwards. Take the update through Garmin Connect or Garmin Express, then start an outdoor ride to confirm the lock. A hard reset and a full factory reset did not resolve it for most owners, and some units returned from service still faulty until 31.30.

---

Garmin Forerunner 970 and 570 track auto-detection drawing a rectangle instead of an oval on a 200m track after firmware 17.33

On the Forerunner 970 and Forerunner 570, after stable software 17.33, the Track Run profile redraws the GPS trace as a rectangle instead of following the oval. It happens on 200m tracks rather than the standard 400m. The map and the lap shapes both show squared corners, even after a normal calibration walk in lane one. Owners report it started only after 17.33, with the same fault logged on the 570.

The cause is the track auto-detection layer. It snaps your recorded points onto an assumed standard oval, and on a 200m track that geometry does not match, so the correction distorts the trace into a rectangle. Both watches share the firmware, so the behaviour appears on the 570 and the 970 together.

The workaround is to switch to the plain Run activity profile with Track Detection turned off, which records the raw GPS oval rather than the snapped shape. Changing data recording from Smart to Every Second further cleans the trace on a tight 200m loop. The distortion sits in the snapping step, so disabling Track Detection returns both the shape and the snapped distance to the underlying GPS recording.

---

Garmin Fenix 8 not connecting to a power meter during a multisport or triathlon

On the Fenix 8, Fenix 8 Pro and Enduro 3, a multisport activity such as a duathlon or triathlon does not connect to a paired power meter if the meter is asleep or out of range at the moment you start the activity. There is no power data screen and no power recorded for the bike leg, while a standalone bike activity with the same pairing connects normally. Owners reproduced the failure every time when they started the event away from the bike.

The watch links to its paired sensors only at the start of the activity. A Favero Assioma or similar pedal that is sleeping in transition never wakes into the session, and the watch does not retry during the bike leg. Garmin support confirmed the device does not automatically pair to additional sensors mid-activity. The same setup connected after T1 and T2 on last year’s firmware.

There are two practical fixes. Start the multisport activity within range of an awake power meter so it links before the gun. Where the start line sits away from the bikes, wake the meter in transition, then hold the middle-left button and open Watch Settings, Connectivity, Sensors and Accessories to trigger the connection by hand during the activity. Marking a transition now needs a long press of the lap button on current firmware, so rehearse the full multisport sequence before race day.

---

Garmin Forerunner 970 and 570 instant pace lagging during intervals

On the Forerunner 970 and Forerunner 570, the instant pace data field updates slowly. When you change speed the number lags for several seconds, sometimes a minute or two at the start of a run, and it is worst on hills and during intervals. Average pace moves while instant pace stalls, which makes the field hard to pace from. Owners report it persists through software 16.37.

The reading is taken from the GNSS chipset with a long averaging window of roughly twenty to thirty seconds, rather than the shorter software-calculated value used on earlier Forerunners such as the 955. The change carried into the 970 and 570 from launch. Release notes referenced an improvement, but owners report no real change on their units.

The workaround owners describe is a footpod. A Stryd returns a roughly three second instant pace that tracks speed changes, which makes interval and tempo sessions usable again. Garmin’s standard advice, Every Second recording with the All and Multiband GPS setting and a hard reset, did not resolve the lag for most owners. The footpod takes over as the pace and distance source once paired, so calibrate it against a known distance for accurate splits.

---

More from last week’s Fix Files roundup.

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

Last Updated on 22 June 2026 by the5krunner