Garmin, Wahoo, Suunto Firmware Bugs: August 2026 Roundup

Two weeks of firmware pain across the major platforms. Issues #10 and #11 of The5kRunner's Deep Dive Fix Files, covering the weeks ending August 7 and August 14, 2026, paint a messy picture for Garmin, Wahoo, and Suunto users right in the middle of race season. If you race triathlons or run ultras, some of these bugs hit exactly where it hurts.

Garmin: Forerunner, Fenix, and Edge All Affected

The Forerunner 970 is dealing with rowing session resets and alarm volume spikes that users are reporting mid-workout. Garmin Coach rest days are also misbehaving, and the metronome is going silent on some builds alongside music pause failures under firmware 18.14. These are not minor cosmetic glitches. A metronome dropout mid-run or a music freeze during a long effort on the Forerunner 970 is genuinely disruptive for tempo work. The Venu 4 adds music crashes and spontaneous reboots to the pile, which is embarrassing for a watch positioned partly as a lifestyle device. On the Fenix 8, phone disconnect alerts are misfiring, the wrist gesture for the timer is unreliable, and calendar sync is dropping. The Fenix 7 glance order is also shuffling unexpectedly. Given that Fenix 8 Pro had [trail visibility issues flagged back in May](/en/articles/fenix-8-pro-s-trail-visibility-issue-persists-2026-05-14), the platform has been accumulating a noticeable bug debt across the summer.

Week two brings more Garmin edge cases. The Edge 840 is seeing Connect IQ data fields break and elevation profile redraws glitch out, which matters a lot for cyclists using custom power or climbing metrics. The Edge 1050 and 840 are showing reversed compass readings and the 1050 is throwing false Varia 820 radar connections, meaning you think a car is detected when there isn't one. That is a safety-relevant failure, not just an annoyance. The Edge 840 is also failing device recognition after the beta 32.10 push. The Forerunner 955 Solar is reporting sensor hub failures, and the Instinct 3 is suffering button freezes and intensity minutes undercounting. Undercounting intensity minutes means your weekly training load data is wrong, which flows directly into recovery and readiness scoring. These are the kinds of bugs that quietly corrupt long-term data sets.

Wahoo: Roam 3 Loops and Bolt GPS Drag

Wahoo's Roam 3 is caught in reboot loops in week one, a problem serious enough that mid-ride navigation becomes unreliable. The Bolt V1 is pulling slow GPS locks, which anyone who has stood at a start line waiting for signal knows is maddening. In week two, the Roam 3 has Strava Live Segments failing, the Bolt V3 has FIT file access issues (meaning post-ride data may not export cleanly), and the Kickr is dropping proper resistance control inside Zwift. That last one is a trainer-software integration failure. If you are doing structured ERG intervals on the Kickr and resistance spikes or collapses unpredictably, the session data is worthless and the workout itself is compromised. Wahoo has been under pressure since the JetBlack ITC dispute earlier this year, and firmware quality on the software side needs sharper attention.

Suunto: Elevation Errors and False Off-Route Alerts

Suunto Vertical 2, Race S, and Race 2 are all dealing with false off-route alerts, random restarts, elevation errors, and short distance reporting under software version 2.56.18. For trail runners and ultra athletes who rely on the Vertical 2 as a primary navigation device, false off-route alerts during a race are a serious problem. Elevation errors and distance undercounting directly undermine the baro altimeter data that the watch calculates from air pressure changes, and that corrupts climb tracking and segment matching. Week two adds power meter reconnection failures on the Vertical 2 and Race 2, heart rate broadcast issues to Wahoo head units, and a conflict between the Coros armband optical PPG sensor and a Stages power meter. The Race S is also draining battery faster than expected and failing to fetch data from Intervals.icu.

What's missing from all of this is urgency. None of these three brands have published clear public fix timelines for the issues flagged in week one before week two added new ones. Garmin has a history of patching quietly across firmware revisions, which we have tracked since [earlier in 2026](/en/articles/garmin-firmware-bugs-in-2026-six-issues-and-confirmed-fixes-2026-06-14), but the pace of new issues is outrunning confirmed fixes. Suunto's elevation and distance errors on 2.56.18 are particularly concerning given how long similar issues lingered on older Race firmware. The Coros armband conflict with Stages is also a reminder that multi-device ANT+ or Bluetooth setups still create edge cases that optical PPG sensors and power meters handle badly when they step on each other's signals.

If you are racing in August or September, the practical advice is straightforward. Avoid beta firmware if you have a race in the next three weeks. Stick to the last stable release you know worked. If you are on a Wahoo Roam 3 and hitting reboot loops, the workaround is a full reset before your next big ride. Suunto Race 2 and Vertical 2 users on 2.56.18 should check community threads daily for a patch. The Garmin Edge compass reversal on the 1050 and 840 is the single most alarming issue here from a safety standpoint, and Garmin needs to move fast on that one.