Garmin Fenix 8, Edge 840, Forerunner 970 Bug Roundup: August 28 2026

Week 13 of The Deep Dive Fix Files covers a wide spread of firmware headaches across Garmin's current lineup, plus a pair of Wahoo issues that have been quietly frustrating riders. If you are running software 22.43 on the Fenix 8, ghost touches and the display-off toggle are the two bugs you need to know about right now. Random restarts and unexpected battery drain on the same watch round out a rough patch for Fenix 8 owners heading into fall race season.

Fenix 8 Software 22.43: What Is Breaking and Why It Matters

The ghost touch issue on Fenix 8 under firmware 22.43 is particularly nasty during workouts. Unintended screen inputs during a run or swim can dismiss alerts, skip intervals, or accidentally trigger focus modes, which are also behaving erratically in this build. Ghost touches on a touchscreen watch trace back to the capacitive digitizer layer misreading electrical noise, not the optical PPG sensor underneath, so sweat and pressure changes during exercise make the problem worse. Garmin has not confirmed a fix timeline as of August 28, and users are reporting the display-off toggle failing to engage consistently, which hammers battery life on a watch rated at up to 29 days in GPS mode. Compare that to the Coros Vertix 3, which has stayed relatively clean firmware-wise through the same period, and the Fenix 8 situation looks frustrating for the price point.

The random restart and battery failure reports are a separate problem, likely unrelated to the display bug. Several users describe the watch shutting down mid-activity with 20 to 30 percent battery remaining, which is the kind of failure that matters on a 10-hour ironman bike leg. The Fenix 8 Solar variant is supposed to extend runtime significantly in strong sunlight, but a software-triggered shutdown makes that hardware advantage irrelevant. Until Garmin pushes a patch, the practical advice is to keep the watch on an older firmware build if you have a long race coming up.

Forerunner 970 and Edge 840: Smaller Bugs, Real Consequences

The Forerunner 970 has three separate issues in this week's roundup: floors climbed miscounting, always-on display inconsistency, and charging vibration triggering at the wrong moment. Floors climbed uses the barometric altimeter, which reads air pressure changes to estimate vertical gain, so any firmware miscalibration in that pressure-to-elevation conversion will throw off the count. The always-on display bug is a nuisance more than a safety issue, but on a watch that competes directly with the Apple Watch Ultra 2 on lifestyle usability, it erodes confidence. LiveTrack message delivery failures are also reported, which matters for athletes whose support crew or family tracks them during ultras or long-distance triathlons.

On the Edge 840, auto pause is misfiring again, a problem that also appeared in earlier builds and was covered in the [August 15 roundup](/en/articles/garmin-wahoo-suunto-firmware-bugs-august-2026-roundup-2026-08-15). The Elite Avanti ERG control issue means some users cannot hold target watts in structured sessions, which breaks interval precision for cyclists doing threshold work. GNSS track duplication is a separate headache: the Edge 840 is logging two overlapping GPS tracks in some cases, likely a data-writing conflict between satellite systems rather than a hardware problem with the GPS receiver itself. Elevation zeroing out mid-ride is also back, a baro altimeter parsing bug that has appeared and disappeared across multiple Edge generations. For the Edge 1050, unwanted sensor pairing popups are interrupting navigation, which is genuinely distracting when you are descending at 60 km/h.

Wahoo Roam 3 and Kickr Move: Two Issues Worth Flagging

Wahoo is not immune this week. The Roam 3 is dropping GPS signal in certain conditions, which is a real problem for riders who rely on the device for navigation in remote terrain. GPS dropouts on a cycling computer trace back to satellite acquisition and signal processing in firmware, not a failure of the physical antenna, and Wahoo's track record on fixing these quickly has been mixed. The Kickr Move is producing roller noise that users describe as new and unexpected, suggesting a firmware change may have altered motor control behavior. The Varia RV820 radar is throwing false positive alerts in group riding scenarios, flagging passing riders as rear-traffic threats. That one is a known limitation of Doppler-based radar in dense traffic, but a firmware-level filter should be able to reduce false positives significantly.

What is missing from this week's picture is any confirmed fix release from Garmin for the Fenix 8 22.43 issues. The [Fenix 8, Edge 850, Suunto Race 2 roundup from August 22](/en/articles/fenix-8-edge-850-suunto-race-2-bug-fix-roundup-august-2026-2026-08-22) documented similar problems, and six days later there is still no patch. The Connect web interval editor bug affecting structured workout creation is also unresolved, which hits Hyrox and triathlon athletes who build complex sessions on desktop before syncing to their device. The Edge 850 cadence averaging inconsistency is a quieter issue but worth watching if you do cadence-based cycling drills.

The verdict here is clear: if you are racing in September on a Fenix 8, hold off on updating to 22.43 until Garmin confirms a fix. The Forerunner 970 issues are less severe but worth monitoring, especially if LiveTrack is part of your race-day safety plan. Wahoo Roam 3 owners doing navigation-heavy routes should check firmware release notes carefully before updating. And with the [Fenix 9 launch now confirmed](/en/articles/garmin-fenix-9-18-variants-leaked-before-august-25-launch-2026-08-23), some of these Fenix 8 pain points may quietly push buyers toward holding out for the next generation instead.