Garmin, Suunto and Wahoo Bugs: July 2026 Tracker

Three consecutive weeks of bug reports landed between early and late July 2026, and the picture is not flattering for any of the major brands. Across issues 6, 7 and 8 of The Deep Dive Fix Files, trackers counted 18 faults in the week ending 3 July, 33 in the fortnight ending 17 July, and another sizeable batch through 24 July. That is a lot of workarounds to memorise before your next long ride or race week.

Garmin: The Longest Bug List

Garmin carries the heaviest load across all three issues, which is partly a function of market share and partly a function of firmware update frequency. The Fenix 8 AMOLED is arguably the worst offender right now. Firmware 21.39 triggered crashes, 22.35 introduced random reboots and lost step counts, and a separate fault is logging phantom distance while the watch is sitting still on your desk. For a watch retailing above $900, that is embarrassing. The Forerunner 970 shows up across multiple weeks too: pace freezing to 0:00, elevation errors, sleep tracking failures, HRV dropouts, and a metronome that misbehaves. Runners using this watch for structured track sessions or treadmill work should double-check their treadmill distance figures and not trust the pace field blindly mid-interval. The Forerunner 570 has its own problems, including strength training button lockups and a boot loop that leaves the watch stuck on startup. The Forerunner 165 is throwing voice prompt errors, which matters if you rely on audio cues instead of glancing at your wrist during tempo runs.

The Edge cycling computer lineup is getting hit just as hard. The Edge 1050 alone accumulates Wi-Fi faults, sensor reconnection failures, ClimbPro gradient errors, map data field freezes, and TopoActive freezes across the July period. ClimbPro gradient bugs are a real problem for cyclists who pace climbs by grade rather than feel: if the displayed gradient is wrong, your effort targets are wrong. The Edge 850 hit a boot loop when loading courses and lost standby GPS lock. The Edge 840 and 540 also appear in the crash and reboot loop reports. Varia RTL515 pairing failures on the Edge 1050 and 840 show up in issue 6, which is a safety concern more than a data concern since that radar system is there to warn you about traffic approaching from behind. You can track the longer history of Garmin firmware instability in our earlier piece on [Garmin firmware bugs in 2026](/en/articles/garmin-firmware-bugs-in-2026-six-issues-and-confirmed-fixes-2026-06-14) and the [June 2026 bug tracker](/en/articles/garmin-and-wahoo-bugs-june-2026-six-issues-tracked-2026-06-18).

Suunto and Wahoo: Smaller Lists, Real Problems

Suunto appears across all three issues. The Vertical 2 shows a black screen fault, unreliable battery reporting, and an update loop that traps the watch in a cycle of failed firmware installs. The Race 2 accumulates sticky notifications, power meter dropouts, backlight activation failures, and its own update loop. Power meter dropouts on the Race 2 are worth flagging specifically: the watch pairs with power meters over ANT+ or Bluetooth, and when that connection drops mid-ride, your training load data for the session is compromised. The Suunto 9 Baro and 9 Peak Pro both show map, distance, route, and vibration problems in issue 7. The baro altimeter on these watches uses air pressure to calculate elevation, not GPS satellites, so a firmware error affecting that sensor pipeline hits vertical gain accuracy directly. Light-mode map labels introduced in firmware 2.56.18 are described as hard to read, which is a usability regression rather than a data fault but still frustrating mid-navigation.

Wahoo contributes two entries across the period. The ELEMNT ROAM logged an average power calculation fault in issue 6. For cyclists training with a power meter and targeting specific average watts over an interval or a full ride, a display error here is not trivial. Wahoo SYSTM on Windows also appears in issue 7 with a fault, though the source does not detail the exact nature. That affects indoor training sessions more than outdoor riding.

On a more positive note from the same ecosystem, a developer called RiversideArt shipped 18 Connect IQ apps in a single month, all free or one-time purchase with seven-day trials, built deliberately outside the Connect+ subscription model. In a period where platform monetisation pressure is real, that stands out.

What Is Missing From These Reports

The fix files are useful, but there are gaps. The sources confirm faults exist and describe symptoms, but confirmed firmware resolution timelines are absent for most entries. You know the Fenix 8 AMOLED crashed on 21.39 and rebooted randomly on 22.35, but there is no published date for a clean build. Comparing this to how Polar handles firmware transparency is instructive: Polar's release notes tend to be more explicit about what was broken and when. Coros is also worth watching here. The Pace 3 shows up only once across the three issues, with a dial failure in issue 7. That is a much shorter bug list than Garmin or Suunto, which reflects either a more conservative update cadence or a smaller user base filing reports. Apple Watch Ultra 2 does not appear at all in endurance-specific bug trackers like these, partly because its audience skews away from power-meter-integrated training and partly because watchOS updates move on Apple's own schedule.

The Forerunner 970 is shaping up as a watch that launched with serious ambitions and is grinding through a rough firmware adolescence. Pace freezing, elevation errors, sleep failures, HRV dropouts, and metronome misfires across consecutive weeks is a pattern, not a one-off. If you are a runner who paid over $600 for this watch and are seeing these issues, the workaround culture is real: check The Deep Dive Fix Files weekly and hold off on updating firmware until the community confirms a stable build. Our earlier look at the [Fenix 8 Pro trail visibility issue](/en/articles/fenix-8-pro-s-trail-visibility-issue-persists-2026-05-14) shows this is not a new pattern for Garmin's premium tier.

Bottom line: if you are on a Fenix 8 AMOLED, hold at a stable firmware build until 22.35 reboots are resolved. Forerunner 970 runners should verify elevation and pace data manually post-run. Suunto Race 2 cyclists should check power meter pairing stability before race day. If you want a shorter bug list right now, the Coros Pace 3 or Polar Vantage V3 are the cleaner bets in mid-July 2026. Neither matches the Garmin ecosystem's depth of third-party app support, but they are not asking you to memorise workarounds every weekend either.