#3 The Deep Dive Fix Files: Week Ending 12 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 Morning Report showing wrong training readiness or Body Battery not recovering overnight

Three separate faults produce this symptom. The first sits in the Morning Report itself, which terminates the sleep session the moment any button is pressed during the night. Body Battery and training readiness lock in at that point and will not update further. Leave the buttons alone overnight, or rely on raise-to-wake instead of pressing anything.

Battery saver mode is the second cause. When active, it can disable wrist heart rate through the night, which starves the recovery algorithm of the data it needs. Disabling battery saver, or re-enabling wrist heart rate inside that mode, restores the overnight readings.

The third cause sits in the user profile. A maximum heart rate set too high or too low distorts every calculation downstream, readiness included. Set the maximum manually in Garmin Connect and sync.

Garmin PacePro progress freezing mid-race or calculating wrong split paces

PacePro fails in three ways here. The progress bar can freeze mid-race with the time-ahead field showing only dashes. Rebuilding the strategy and re-syncing it before race day clears this.

A strategy will not activate if the GPS has not matched the course start point. Beginning roughly 100 metres before the line and pressing start there gives the device the location match it requires.

Split paces come out wrong when the course was imported from a third-party GPX file. Recreating the course from scratch in Garmin Connect produces correct splits.

Garmin running dynamics showing zeros or missing from Garmin Connect after the run

The HRM Pro and HRM Pro Plus must be paired over ANT+ rather than Bluetooth for running dynamics to record. Re-pair the strap by selecting ANT+ in Sensors and Accessories. The newer HRM 600 instead requires BLE Secure.

Zeros across the dynamics fields usually mean the strap or pod is worn upside down. Check the orientation against the markings before assuming anything worse.

Running dynamics record only during running activities. Multisport and generic workout profiles do not capture them, so a missing data set after a multisport session is expected behaviour rather than a fault. Some watches do not support running dynamics at all, even though they accept a foot pod. Check the device against Garmin’s compatibility list before assuming a hardware problem.

Garmin Express not detecting your device, map updates stuck, or the download failing

Third-party USB cables are the usual reason Garmin Express fails to detect a device. Many are charge-only and carry no data. Use the Garmin data cable, plug it directly into a USB port rather than a hub, and run Express as administrator on Windows.

Map updates that sit at zero percent are a separate problem. Express processes one update at a time, so letting smaller updates finish first often unblocks the queue. Clearing the cache by unchecking all options in General Settings resolves the more stubborn cases.

Large downloads pause when the computer goes to sleep and cannot always resume afterwards. Disable sleep before starting a large map download, and use a wired ethernet connection where possible.

Garmin Body Battery stuck at 5 percent overnight

A soft reset clears most cases. Hold the power button until the watch shuts down, restart it, and confirm the green sensor lights flash when the watch is held still.

Battery saver mode can disable wrist heart rate overnight, which leaves Body Battery without the data to recover. Check the toggle and make sure wrist heart rate is set to on rather than during-activity-only. A wrong maximum heart rate in the profile distorts the readings here as elsewhere, so set it manually in Garmin Connect.

After any reset the metric needs several days to recalibrate. A low or erratic reading immediately afterwards is not a sign the fix has failed.

Garmin watch stopped logging whole nights of sleep after a firmware update

On the Forerunner 165, firmware version 20.32 introduced a regression that stopped whole nights logging. Check for a follow-up firmware release and install it.

Where firmware is not the cause, battery saver disabling optical heart rate overnight is the most common explanation. The sleep window in Garmin Connect also matters: it must bracket the actual hours slept, so widen it if sleep starts earlier or ends later than the set window.

A loose band, or one worn over the wrist bone, drops the optical signal when the wearer is still. Tighten the fit and move the watch above the bone to restore the overnight trace.

Garmin barometric altimeter logging wrong elevation gain on runs and rides

The altimeter needs a valid starting reference. Take the device outside and wait for a full GPS fix before pressing start, so the opening elevation is correct.

GPS corrects the altimeter during the activity. This is fairly reliable, though GPS vertical accuracy is limited and will not fully compensate for a bad starting point.

A sensor port blocked by sweat or sunscreen causes lagging readings, so rinse and dry the port. Saving a place-based location at regular start points also helps; whatismyelevation.com gives the correct elevation to enter.

Wahoo ELEMNT, BOLT 1 and ROAM 1 wrong date showing January 2006 and GPS not working after August 2025

The 10-bit GPS week counter rolled over on 17 August 2025, and affected devices calculated the date as January 2006. Only the ELEMNT, BOLT 1 and ROAM 1 are affected.

Wahoo released a firmware fix: build WR24-17055 for the ROAM 1 and build WB17-17055 for the BOLT 1. Install it through the Wahoo app over WiFi, then take the device outside for a full GPS sync.

A factory reset is optional but clears any corrupted session data. Second-hand first-generation units may not have the fix installed, so check the firmware build before riding.

Wahoo BOLT 1 and ROAM 1 GPS taking 5 to 15 minutes to lock after the August 2025 firmware update

After the firmware rewrite the GPS chip has to download a fresh almanac. This is a one-time process that needs uninterrupted outdoor time. Navigate to the map page immediately after powering on, then stand still outside under clear sky until acquisition completes.

Where the map page method does not work, a factory reset has resolved the slow acquisition. Sync all rides first, reinstall the firmware, then repeat the outdoor almanac step.

Wahoo ELEMNT BOLT and ROAM rerouting back to the original deviation point after rejoining a planned route

Corrupted map data is the most common cause. Connect to WiFi, delete all maps in Manage Maps, and re-download the region you need.

Calibrating GPS before the ride helps: navigate to the map page and wait for acquisition before pressing start. Confirm that Reroute Automatically is enabled in the ELEMNT app settings.

If the problem continues mid-ride, end the active route on the device and reload it from the route list.

---

More from last week’s Fix Files roundup.

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

Last Updated on 12 June 2026 by the5krunner