
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 Forerunner 970 Touch Lock not working while the screen still responds
On a Forerunner 970, Touch Lock can show as switched on while the screen keeps responding to taps. The control only ever reads touch lock off, and pressing it again changes nothing. A restart makes the lock work, but it slips back to the broken state after a few minutes. In rain or heavy sweat this matters, because stray touches can pause or end an activity.
One owner on the Garmin forum traced it to Do Not Disturb. With Do Not Disturb switched off, Touch Lock behaved normally. Garmin staff replied that the two should not be linked, so this is a workaround that points to a software fault. Staff could not reproduce the problem and suggested a full reset to default settings, but the thread does not say whether that helped.
Another owner on software 18.32 says Touch Lock works fine on their watch, so not every unit is affected. Nobody has reported a firmware release that fixes it.
Suunto SHRB2 flight time reading 1 ms after firmware 3.2.6.8
After updating the Suunto SHRB2 belt to firmware 3.2.6.8, several runners found their flight time had collapsed. One owner saw an average of 1 ms and a ground contact to flight time ratio of 11320.4 percent, against 324 ms before the update. A second owner reported 1 ms and a ratio of 2419.1 percent.
Not everyone sees zero. A third owner saw flight time fall from about 290 ms to about 45 ms, and one user suggests Suunto changed the formula, so lower numbers may be expected. That does not explain readings of 0 or 1 ms, which still look like a fault.
One owner went back to the previous belt firmware after flight time stopped working on 3.2.6.8. Another has stopped using flight time and the ratio, and relies on ground contact time and balance. A forum moderator passed the report to Suunto’s product manager, but there is no official reply yet.
Suunto Vertical Titanium Solar battery drain of 8 to 9 percent a day since software 2.43.12
Several Suunto Vertical Titanium Solar owners report much shorter battery life since the June 2025 software update, version 2.43.12. One owner went from about 3 percent loss a day to roughly 8 to 9 percent under similar use. Another lost about 6 percent on a two hour hike, where 2.5 to 3 percent would be expected. A third saw the battery fall from 99 to 96 percent over 11 hours with no activity recorded.
A warranty replacement did not settle it. The original poster’s new watch ran well on older software, but it updated itself overnight even with automatic updates switched off, and the drain returned. Another owner had poor battery life on both the original and the replacement.
Not every unit is affected. One owner sees 2 to 3 percent loss a day on low sun days with 24/7 heart rate and sleep tracking turned off. Nobody has confirmed a firmware downgrade, and Suunto has not responded in the thread.
This issue remains unresolved. If you have encountered it and found a fix, the discussion is open on r/the5krunner.
Suunto Race S and Race 3S not starting to charge until the charger is swapped
A Suunto Race S or Race 3S that sometimes refuses to start charging is the subject of a forum thread started on 30 October. The first owner found the watch would not charge on its original charger, and reconnecting the cable did not help. A second owner says the same thing has happened to them recently.
The first fix that worked was a different charger. The watch charged on the second one, and the original charger later worked normally again, so the fault did not stay with the cable. The second owner only got charging to begin after plugging and unplugging several times, and cleaning the contacts helped little. They usually charge from a computer USB port rather than a wall adapter.
The first owner suspects firmware, with the watch failing to recognise the charger connection. No firmware version is named and Suunto has not responded. Another owner reports charging worked first time, so it is not every unit.
Suunto Race 2 with Stryd pods missing balance data in Stryd Power Centre
Running Stryd pods or a Stryd Duo with a Suunto Race 2 and an SMHR2 heart rate belt can leave Stryd Power Centre without ground contact balance and other pod metrics. The owner saw ground contact time in the Suunto app coming from the wrist rather than the belt, even though the pods paired to an iPhone without trouble.
The data loss appears to come from the SuuntoPlus Stryd app. One poster says Stryd told them a Suunto watch records only six fields per SuuntoPlus app while the pods send 19. That claim is secondhand and the thread does not link a Stryd statement.
The workaround that worked was to skip the SuuntoPlus app, pair the Stryd Duo directly to the watch, wear a separate chest belt, and run a manual offline sync of the pods in the Stryd app after the workout. Stryd Power Centre then held one merged file, with power, heart rate, speed and distance from the watch and balance and running dynamics from the pods. Using the SMHR2 with directly paired pods also worked, but running dynamics then came from the belt.
Garmin Forerunner 970 Wallet asking for the passcode on every payment
Some Forerunner 970 owners now get asked for the Garmin Wallet passcode on every payment. The owner in the forum thread says the watch used to ask once every 24 hours while it stayed on the wrist. Since the last software update it sometimes asks again about a minute after the previous payment.
The one workaround reported is a restart. It clears the problem, but only for a day or so before the repeated prompts return.
Garmin staff replied but have not offered a fix. They asked for the software version and a video of the behaviour with the passcode kept out of shot, and said they were not seeing other reports. The owner has not named the firmware version, so it is unclear which update introduced the change.
Garmin Edge 540 battery percentage stuck at 100% on firmware 31.33
On firmware 31.33 the Edge 540 can show 100 percent after a full charge and keep showing it through the whole ride while the real level drops. Owners say the true figure only appears after a restart, with one unit showing 87 percent once it was power cycled. One rider had the Edge cut out mid ride because the display never warned that the battery was low.
A full power off and on clears it for the moment, but the stuck reading comes back for several owners after the next charge and sleep cycle. Tapping the battery icon on the Controls screen shows an estimated time remaining, which keeps counting down while the percentage stays frozen. That gives you something reliable to watch on a long ride.
A Garmin moderator has marked the answer as verified. The fault should be fixed in public beta 31.63, and the advice is to join the beta or wait for the next public release. Another user points to the beta 31.62 changelog line about battery percent increasing while riding as the same fix.
Wahoo SYSTM downloaded workouts not loading on Windows after v7.113.0
After updating to SYSTM v7.113.0, downloaded workouts and videos on Windows 10 and Windows 11 fail with a message that the content could not be loaded. Riders say recent downloads are affected, including the October Challenge session and a new Inspiration video, while older downloads still play. Streaming the same content works.
Deleting the file and downloading it again does not help. Deleting the download and streaming the session instead worked as a stopgap for two users, which is slower on a weak connection but gets the workout on screen.
Version 7.114.0 fixed playback for the two users who tried it. One of them had been sent email instructions by Wahoo support, then retried on 7.114.0 and found downloads working without following them. The thread does not give a cause, and one user suspects the fault only affects Windows.
Garmin Forerunner 965 not pairing or syncing with Wi-Fi and Bluetooth versions at 0.00
Forerunner 965 owners describe a watch that refuses to pair with any phone, including a brand new Android 14 device. The pairing screen spins for about five seconds and drops back to the QR code, and Wi-Fi backup fails with error 0500 even on a hotspot the watch accepts. Some units also show 0.00 for the Wi-Fi and ANT, BLE and Bluetooth versions under Settings, System, About.
The usual steps did not fix it for most people. Forgetting the watch in the phone’s Bluetooth settings, reinstalling the Garmin app, restarting the phone, resetting to default settings and pairing with a third phone all failed for the original poster. Updating to 29.05 through Garmin Express left the versions at 0.00 on one watch. The Reinstall Software option failed for two users, and so did downgrading to 26.08 from an unofficial download.
The only reported fix came from a Samsung S26 Ultra owner, who got pairing working after choosing Delete all data and reset on the watch and then rebooting the phone. That wipes the watch, so sync your activities first, and the thread does not say whether the fix lasted. Another poster thinks a permanent 0.00 points to a faulty Wi-Fi and Bluetooth module that only Garmin can repair.
Wahoo KICKR Headwind not finding a Polar H9 over ANT+ after firmware 2.0.57
Since the Headwind updated to firmware 2.0.57, a Polar H9 on firmware 2.2.0 no longer pairs over ANT+ for some owners. The Headwind lists a sensor called HRM with an unknown ANT+ ID, while the Bluetooth scan finds nothing. The same strap is still found by Hammerhead and Garmin head units, so the strap itself is not the fault. Another owner says a Kickr Bike V2 connects after 2.0.57 but sends no power or speed.
The Headwind accepts only one paired sensor of each type, so a stale entry can block a new pairing. Remove every saved heart rate sensor, including old straps, wet both electrode pads, put the strap on, power cycle the Headwind and scan with the strap close to the unit.
None of these steps worked for the original poster. Wahoo support sent a Tickr HR as a stopgap and is still investigating. A Tickr or Garmin strap pairs normally, so swapping straps is the only confirmed way to keep heart rate control working until a firmware fix arrives. The forum advice is to log a support ticket that quotes both firmware versions.
Suunto Vertical 2 and Race 2 black screen during activity with SuuntoPlus Live.T
Several Suunto owners report the activity screen turning black partway through a workout. One Vertical 2 owner got a black screen after about 20 minutes of an e-MTB activity with the SuuntoPlus apps Weather, ZoneSense and Live.T all running. It began with the latest firmware update, though no version is named. Owners of the Vertical Titanium Solar and Race 2 describe the same symptom.
Removing Live.T from the SuuntoPlus list is the only fix reported so far. A reply says Live.T is heavy on resources and should not run alongside other SuuntoPlus apps. A soft reset helped at first, but the watch went black again around 22 km, so a reset only buys time.
A Race 2 owner running ZoneSense on a trail run found that long pressing the crown and moving forward and back through the screens brings the data screen back. The threads do not show whether ZoneSense alone can trigger the problem, and Suunto has not named a cause.
Garmin Forerunner 570 music silent but draining the battery after saving a run on software 18.32
After updating to software 18.32, a Forerunner 570 owner reports that the built in music player goes silent once a running activity is saved, yet keeps running in the background. The battery estimate drops from a few days to only a few hours.
The workaround is to open the Music app after saving the run and stop playback by hand. That ends the battery drain. Starting the timer app and pressing start brought the sound back for the original poster, which confirms the player was still running.
A second user says the problem has not come back in two days and believes it was fixed somehow. No official fix or acknowledgement from Garmin appears in the thread, so it is unclear whether a later software version changes the behaviour. Checking the battery estimate after each run shows whether the player is still active.
More from last week’s Fix Files roundup.
Browse every issue in the archive at the Deep Dive Fix Files hub.
Last Updated on 6 November 2026 by tfk the5krunner

tfk is the founder and author of the5krunner, an independent endurance sports technology publication. With 20 years of hands-on testing of GPS watches and wearables, and competing in triathlons at an international age-group level, tfk provides in-depth expert analysis of fitness technology for serious athletes and endurance sport competitors. See the gear tfk uses. ID

Well, speaking about the Suunto HRM2 the Flight Time data isn’t the only problem. The R-R data is a real mess too…