#25 The Deep Dive Fix Files: Week Ending 20 November 2026

Deep Dive Fix Files Asset 3 The Deep Dive Fix Files HEADER

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 voice prompts too quiet over Bluetooth headphones with offline Spotify on software 18.32

Forerunner 970 owners on software 18.32 report that spoken pace prompts are almost inaudible when offline Spotify plays from the watch to Bluetooth headphones. The music ducks as it should, but the voice stays very quiet even with alert volume at 100 percent and Silent Mode off. The poster saw it on Apple AirPods and Shokz OpenFit 2+, and the same prompts were loud when the music came from a phone.

Setting Audio Output to Watch Speaker instead of Connected Devices made the voice loud and clear, with no noticeable ducking. That is no use if you want audio in your headphones, so treat it as a way to confirm the cause rather than a fix.

Garmin staff know of no other troubleshooting steps. They pointed to beta software 19.15, which lists a fix for inconsistent Bluetooth headset volume control and volume synchronisation, and asked the poster to test it through the Garmin Beta Program. Nobody has confirmed that the beta restores normal prompt volume, and beta builds can bring their own bugs. The poster changed several settings at once, so if you test, change one setting at a time and keep alert volume at 100 percent.

This issue remains unresolved. If you have encountered it and found a fix, the discussion is open on r/the5krunner.

Garmin Fenix 8 AMOLED Iron Grit watch face drawing late or showing the old time after waking on software 23.39 and 23.40

A Fenix 8 AMOLED Sapphire 47mm owner on software 23.39 reports the stock Iron Grit watch face drawing in two steps after the watch has been idle. The top section appears first and the complications follow about half a second later. Always-on display was off and wrist gesture was on. It does not happen if the watch was used recently, and it started on 22.44.

A second Fenix 8 AMOLED owner sees a related fault in Sleep Mode with Iron Grit as the sleep face. On each wake the watch briefly shows the time from the previous wake before it jumps to the current time. Several other owners describe the same behaviour, and other stock faces are not affected.

Resets did not cure it. The original poster tried soft, hard and factory resets and simplified the data fields, and software 23.40 did not fix it either. One owner said it came back within a couple of hours of installing 23.40. Garmin staff said their engineers could not reproduce the problem and recommended the official reset steps, then Product Support if it continues.

The workarounds are temporary. Switching to another watch face and back, changing the watch language, or restarting the watch clears it for a few hours up to about a day. Running a different face is the practical way to avoid it for now.

Garmin Edge 1050 E-Mountain Bike rides showing as generic E-Bike on Strava with Gear Selection on

An Edge 1050 owner has found that rides recorded as E-Mountain Bike arrive on Strava as a generic E-Bike when Gear Selection is turned on. Garmin Connect shows the correct type. The original FIT file still contains sport cycling and sub_sport e_bike_mountain, so the recording itself is right. The owner has two bikes, both on Bosch Smart System with the Garmin and Bosch integration enabled.

RideWithGPS classifies the same file correctly, which points at the Garmin to Strava transfer rather than the Edge. The owner links it to Garmin’s change from selecting one bike to selecting multiple bikes for a single ride. The wrong type also disrupts Strava Heatmap and activity stats for E-MTB rides.

The only workaround in the thread is to disable Gear Selection. With it off, the ride transfers as E-Mountain Bike. That removes the per-ride bike selection, so you lose that step on the Edge. The thread has no reply from Garmin yet and does not give a firmware version. To check whether you have the same fault, compare the sport and sub_sport fields in the FIT file with what Strava shows after the upload.

Wahoo SYSTM downloaded workouts freezing or stopping halfway on Mac

Several Wahoo SYSTM users on Mac report that downloaded workout videos freeze, stop partway through or fail to play. On some machines the timers stall while the audio carries on, and the app still shows metrics as if the workout were running. The reports include macOS 26.7 and an M4 Mac on macOS 27.2, and some workouts also fail to sync.

The fix that worked for two Mac users is to install the Apple Silicon version of SYSTM instead of the Intel build. One of them made the change after Wahoo support helped him, and the other said the app and workouts ran as they used to on his M4 Mac. Activity Monitor shows which build you are running, because the Kind column reads Apple or Intel for the SYSTM process.

A second workaround came from an iPad user, who stops the workout, deletes it and downloads it again. He called it frustrating and did not say whether it holds from one session to the next.

Windows users in the same thread describe the same glitches, so the Apple Silicon fix does not cover them. One of them has opened a support ticket and suspects the latest update. The thread does not show an official Wahoo fix, and the most recent post is from 6 November.

Garmin Fenix 8 Wi-Fi not connecting and Garmin Express sync error after software 23.40

A Fenix 8 51mm AMOLED owner reports that Wi-Fi fails every time after software 23.40 and that Garmin Express shows “There was an error syncing with Garmin Connect”. Reinstalling 23.40 through Express changed nothing. Bluetooth sync with the Garmin Connect app still works, so activities reach Garmin Connect. A second user sees the same Express error on 23.40, while Wi-Fi still works for other downloads such as Spotify songs.

Garmin staff list the network requirements. The network must be 2.4 GHz only, on channels 1 to 11, with Open, WPA or WPA2 security. The password needs at least eight characters, and hidden SSIDs are not supported. They also ask you to check that you have not hit the watch’s saved network limit and to restart the router. One user says he has synced over a WPA2 and WPA3 mixed-mode network many times, which does not match Garmin’s list.

On the watch side, one user says a restart cleared his earlier intermittent Wi-Fi problems, and Garmin repeats the power-cycle advice. For Express, Garmin suggests updating the app, removing files that fail to sync, deleting possibly corrupted activity files from the watch, and removing the watch from Express and adding it back. No reply confirms that any of these fixed the 23.40 failure.

Until it is sorted, Bluetooth sync through the phone works as a stop-gap. Adding the Wi-Fi toggle and Sync button to Quick Settings makes it quicker to test, and one user finds joining a secure network easier from the phone app.

Suunto Race S treadmill run recording only 0.23 km after a 5 km run

A Suunto Race S owner reports that a 5 km treadmill run recorded about 0.23 km. Distance climbed very slowly during the run while the step count was correct. The thread opened on 12 November and gives no firmware version.

The owner had already used Treadmill sport mode, switched off autopause and calibrated distance manually on the watch after each run. The app confirmed the manual values were saved, but repeated calibration did not improve accuracy. Another user confirmed that manual adjustments carry over to consecutive runs, so calibrating after each run is the main workaround in the thread.

A soft reset has also been suggested, by holding the upper button for more than 12 seconds. The owner has not reported whether it changed anything. The owner said the hand was not holding the treadmill rails and that running form was unchanged. Another user suggested running outside or using a chest strap for better accuracy. Suunto has not replied in the thread and nobody has confirmed a fix.

This issue remains unresolved. If you have encountered it and found a fix, the discussion is open on r/the5krunner.

Garmin Fenix 8 scheduled workouts not syncing to the watch after software 23.40

Scheduled workouts that appear in Garmin Connect on the web and in the phone app are not reaching the watch on a Fenix 8 AMOLED running software 23.40. One user reports that workouts scheduled from intervals.icu show in Connect but never appear on the device, and only the Daily Suggested Workout is listed. A Forerunner 970 owner describes a similar fault after an automatic update, with the scheduled workouts option missing from the run menu and the watch asking to download the calendar.

Garmin staff replied in the Fenix thread that this can happen when the device has no space for additional workouts. Their suggestion is to open Manage Workouts in Garmin Connect, delete old or unused workouts from the device, and then send the workout you want again. Clearing the stored list is the cheapest thing to try first because it takes a couple of minutes and changes no settings.

Workouts sent manually from Garmin Connect to the watch still transfer normally on the Fenix 8, so you can send each day’s session by hand until the calendar sync recovers. Restarting the watch, reinstalling the update and syncing with the Connect app made no difference for the Forerunner 970 user, so those steps are not worth repeating. No confirmed fix has been posted in either thread, and the Fenix thread does not say whether the storage suggestion worked.

Garmin Fenix 8 wrist heart rate reading under 100 bpm on an indoor ride while a chest strap shows 150 bpm

A Fenix 8 AMOLED 43 mm on software 23.40 is reading far too low during indoor rides. The rider records the session on an Edge 530 with a chest strap, which shows about 150 bpm, while the Fenix optical sensor stays below 100 bpm. The watch is worn only so Physio TrueUp can pull the ride into its training data. The rider suspected cadence lock, but a tighter strap is not an option.

The top reply says the optical sensor runs in a low-power mode when no activity is recording on the watch, and that mode samples less often and can read low during hard efforts. The suggested workaround is to start an activity on the Fenix, then discard it afterwards instead of saving it. The reply says the higher-frequency heart rate is still recorded for the day.

Pairing the Fenix to the same ANT+ chest strap works only while the heart rate widget is on screen, and the connection drops when the screen turns off. A second user keeps a bicep optical strap connected to both the Edge and the Fenix. That strap stays connected while an activity is tracking, although it only works if the strap supports more than one simultaneous Bluetooth connection. Garmin staff have not replied in the thread, so there is no official explanation.

Garmin Instinct 3 Solar losing ANT+ power meter data and showing 0 watts while pedalling

An Instinct 3 Solar on software 15.18 intermittently drops ANT+ power and cadence from a Stages left-crank power meter, with both readings falling to zero while the rider is still pedalling. The original poster saw it on three rides. The meter pairs without trouble and works over Bluetooth with the Stages app. The watch recorded about 28 minutes of zero power and cadence on one ride, against about 4 minutes in the phone recording of the same ride. Zero calibration values matched at 929 on the Garmin and 927 in the Stages app.

Other owners report the same fault with different sensors. One user sees power drop to zero with a Wahoo Kickr Core 1 over ANT+. Another tried four sensors, including Quarq, 4iiii and an Elite Direto, and still had random disconnects, and a replacement watch from Garmin behaved the same way. Failures across several brands and across two watches point at the Instinct 3 rather than a single faulty meter.

A Garmin staff member said there were no widespread complaints and suggested removing the power meter from the watch’s sensor list and pairing it again, then contacting Stages if the problem continued. A new sensor battery and wiping the sensor list on both the watch and the Connect app did not help the original poster. Pairing the meter over Bluetooth to the watch failed with a too many connections error. Recording the ride on a phone app or a bike computer over Bluetooth produced far fewer dropouts, and it is the only reliable workaround reported in the thread.

Suunto Smart Heart Rate Belt 2 battery dying after a few hours of use or in storage

Owners of the Suunto Smart Heart Rate Belt 2 report that the coin cell runs out far sooner than it should. One cyclist bought the belt in September and used it for about eight hours across four rides in October. After a few weeks idle it showed no LED and ignored the button. Another owner got about 8 hours 50 minutes of tracked use before the original battery died, and the replacement cell lasted roughly one hour. Several other posters in the long thread describe the same pattern.

The first step that forum members suggest is to fit a fresh battery and then do a factory reset of the belt before retesting. One user said a hard reset got the belt working well. That user also wet the strap electrodes more than they had needed to with the older Smart Heart Rate Sensor, and the belt is meant to be worn snug with good skin contact.

A second suggestion concerns storage. One poster says leaving the sensor module clipped onto the strap can drain the battery, so they unclip it after every session. This is one owner’s habit and Suunto has not confirmed it as a cause.

No Suunto staff member has replied on the battery reports. One owner whose replacement cell also died within about an hour has contacted support and suspects a defective sensor, and another describes a sticky surface with micro-holes on top of a battery that failed. Owners with a fresh cell that still dies within a few hours are best off treating it as a warranty case.

Suunto app route elevation profile showing unrealistic steps and too little ascent after version 3.15.0

Since Suunto app 3.15.0 on iOS, runners and cyclists report that routes they create in the app show a stepped elevation profile instead of a smooth line. Scrolling along the profile also jumps between points, and the distance and elevation readouts stay put. One user tested the Manitou Incline in Colorado, which climbs from about 2,030 m to 2,620 m and should show at least 590 m of ascent. The app showed 393 m. It got worse in 3.15.1, and a second iOS owner on 3.16.0 says the bug affects both new and stored routes.

Android looks better but not fully fixed. A user on Android app 6.15.5 says the profile is smoother, although the total ascent is still about 100 m short of the official 613 m. A moderator could not reproduce the problem on Android for the Incline route. He also pointed out that straight-line segments the app cannot route along a path produce poor profiles.

The workaround that one long-time user describes is to create the route, ignore the elevation, save it as a new route and delete the original. Another member says short routes with a steady grade show the steps less, although they still appear. Suunto staff have not posted in the thread. One member says the problem is already being discussed internally at Suunto, but that is second-hand and there is no official fix or timeline.

Suunto Vertical 2 and Race 2 imported GPX file with no turn-by-turn directions

Turn-by-turn instructions do not appear on Suunto watches when you import a GPX file, which catches out runners who want to load an official race route. A trail runner preparing for a 60 km ultra asked on the Suunto forum whether this is still the case, and the replies describe workarounds rather than a built-in fix. Posters mention the Vertical 2, Race S, Race 2 and Suunto 9.

The most confirmed workaround is Komoot. Import the GPX unedited, decline any route modification, and the route appears in the Suunto app within minutes with turn instructions. Two posters confirmed it works, and one says it needs Komoot Premium. Two other users report that Komoot drops the race’s waypoints, such as aid stations, so check the route on the watch before race day.

The other option is a browser tool that adds turn waypoints to the GPX in Suunto’s format. The thread mentions turnbyturn.apert.be and addturngpx, and the addturngpx developer recommends the Low setting for both fork and bearing sensitivity. One runner found its turns accurate but excessive, with over 70 on an official race GPX and 338 turns over 173 km on the UTMB Mont-Blanc route.

Some problems remain on the watch itself. Waypoints can be ignored if they sit even 0.39 m off the route, and the distance to next waypoint field usually shows the distance to the end of the route. The addturngpx developer also says the turn arrow can point the wrong way at forks and calls that a firmware bug.

Garmin Epix Gen 2 and Forerunner 955 not pairing with Garmin Connect on Pixel 11 Pro and Pro XL

Several owners report that a Garmin watch will not pair with the Garmin Connect app on a new Pixel 11 series phone. The Epix Gen 2 and Forerunner 955 are named most often, and an Instinct 2 Solar owner on a Pixel 8 describes the same loss of a pairing that used to work. The app keeps spinning while it searches and the watch never appears in the list, even after reinstalling the app, clearing its cache and resetting pairing on both devices. The same watches paired without trouble on a Pixel 9 Pro and a Pixel 10 Pro XL, so the thread points at the phone side rather than the watch.

The fix that worked for the original poster was switching Wi-Fi off on the phone and then reconnecting the watch. He was not sure it was not a coincidence, and another owner who turned Wi-Fi off on both the phone and the watch saw no change. One user suggests Pixel phones filter poorly between Wi-Fi and Bluetooth on the 2.4 GHz band, so moving the phone to a 5 GHz network or disabling 2.4 GHz is the next step, followed by resetting the phone’s network settings.

A separate cause is the watch still sitting in the Android Bluetooth device list from an earlier pairing. Removing it there and then pairing from inside Connect is the suggested fix for the plain unable to pair case. Garmin staff only linked the Connect Bluetooth troubleshooting article and have not named a cause or an app version that fixes it.

If you need the watch syncing before a race, the order that costs least is Wi-Fi off, then forgetting the watch in Android Bluetooth settings, then a network settings reset, then the 5 GHz switch.

Garmin Forerunner 970 ghost touches while scrolling, with the screen tapping itself and opening menus

Forerunner 970 owners report that the touchscreen registers a tap while they scroll through glances, menus and settings, which opens screens several levels down without a finger being lifted. One owner describes it as a micro lag where the scroll stops and a touch is registered instead. Some also see the on-screen keyboard repeat letters. The thread has passed 170 replies and Garmin staff posted in it again this week.

Software does not appear to be the cause. Owners saw it on versions 16 and 17.33 and on newer releases, and Garmin has not named a version that fixes it. In the cases posted, a reset, a power cycle, and toggling phone pairing, Wi-Fi and Always On Display made no difference.

Garmin’s first steps are to install the latest software, remove any screen protector, clean the display and restart the watch. Staff say they are handling reports case by case, and their latest reply asks owners on current software to contact them with the software version, a description of the pattern and a video.

The only fix reported so far is a replacement unit. One owner said the replacement works, but a repair shop found that only one of four watches it tested behaved properly, and other owners report the fault on two or three replacements in a row. That suggests a hardware problem on at least some watches, although Garmin has not said so.

Garmin Connect Android 5.30.1 MyFitnessPal calories showing 0 on the Nutrition page

Garmin Connect users on Android report that MyFitnessPal intake shows correctly in the Nutrition glance on the home screen but as 0 calories and 0 g of macros once they open the detailed Nutrition page. One example is 2,478 of 2,653 calories on the glance and zero on the page. Another user sees only the current day in the app, with earlier days missing in the app but present on the Garmin Connect website. The reports are on Connect 5.30.1, and one user says 5.29.0.1 still works on a different phone.

The workaround suggested is to open the Nutrition page on the Garmin Connect website and press the Sync with MyFitnessPal button to force a manual sync. If that fails, disconnect MyFitnessPal from your Garmin account and connect it again. No one in the thread has confirmed that this restores the app page.

Force-stopping the app, clearing its cache, reinstalling it and reconnecting MyFitnessPal did not help for the users who tried them. An earlier bug that blanked the home screen glance was cleared by a later Connect update, so a newer app release is the most likely route to a fix here. Garmin staff asked follow-up questions in the thread but have not given a fix or a timeline.

Because the website shows the data, the sync from MyFitnessPal to Garmin is working and the fault sits in how the Android app displays it. For fuelling totals on long training days, the website is the reliable place to read them for now.

Garmin Edge 1050 new and saved courses not syncing from the Garmin Connect app

Some Edge 1050 owners report that courses sent from the Garmin Connect app on iPhone no longer arrive on the device. A single sync used to be enough. Now most attempts fail, and a course only appears after many repeated syncs, if it appears at all. The pattern is described in a thread on the Garmin forum, which does not name a firmware version.

The first cause to rule out is the course limit. A forum user says the Edge 1050 holds 100 courses, and that the cap was recently lifted to 200 on beta firmware and newer devices. Once the device is full, new courses do not transfer. Deleting old courses on the Edge frees slots and should let the new ones through.

The second cause is route content, particularly routes built in Komoot. Another user says Garmin rejects routes whose waypoint categories do not match the categories it supports, and that setting every waypoint to Info lets the transfer complete. The original poster has not confirmed this, so it is a test rather than a known fix.

A route that still fails can be sent by another method. A third-party iPhone app called Ridekit pushes courses to the Edge 1050 over Bluetooth without an internet connection. A forum user who says he makes the app recommended it in the thread, so treat that as self-promotion rather than an independent test.

Garmin Edge 1050 Wi-Fi sync failing on UniFi access points but working on a phone hotspot

Edge 1050 Wi-Fi sync fails for some riders on UniFi networks, while an iPhone hotspot connects every time. A thread on the Garmin forum includes packet captures from a user with UniFi U6 Pro and U6 Mesh access points on firmware 6.8.2, using 2.4 GHz, with the Edge on software 32.20. A second user with two U6 Pro access points reports the same behaviour, with many WPA authentication failures in the logs.

The captures show the Edge stops listening about 12 ms after it sends its join request. The access points replied within 17 to 51 ms, and the Edge missed nearly all of those replies, went quiet for about 350 ms and then restarted the join. The poster’s join success rate on the access points fell from about 84 percent between November 2025 and January 2026 to 0 percent from July to November 2026.

The only fix that worked was restarting the access points. They had been running for 269 days. After the restart the Edge joined on five of six attempts. The poster says the access point replies appear to slow down with uptime, so the problem may return and the restart may need repeating.

The same user ruled out WPA3 and protected management frames, roaming between access points, transmit power, 802.11ax, 802.11k, channel 1 versus channel 6 and phone Bluetooth. None of those changes helped. A phone hotspot works as a fallback in the meantime, and Garmin has not offered a fix yet.

Garmin Edge 1050 showing the wrong time after a time zone change

An Edge 1050 can show the wrong time after a region changes its time zone rules, even when the phone shows the correct time. A thread on the Garmin forum describes a rider whose region moved from MST (UTC-7) to UTC-6 year-round. The Edge rolled back an hour while the phone stayed correct. The thread does not name a firmware version.

A forum user pointed to a Time Zone Map update, version 43.00, listed in Garmin Express, and asked whether it had been installed. The original poster then synced the Edge with Garmin Express, which they believe pulled in that map, and the time was correct afterwards. To try the same fix, connect the Edge to a computer, open Garmin Express and run a sync so that any pending updates install.

The thread has only two replies and is locked, so this is a single rider’s result rather than a confirmed pattern. Checking Garmin Express for a pending Time Zone Map update is a cheap first test before resetting the device.

More from last week’s Fix Files roundup.

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

Last Updated on 20 November 2026 by tfk the5krunner


Small things I always use

Health, recovery and sleep

  • Kineon MOVE+: Red and infrared light for sore knees, Achilles and other joints after hard training. I use it.
  • FreeStyle Libre 3 Plus: Shows how my blood sugar responds to diet. Occasional use.
  • hDrop: Measures my sweat loss in summer and indoors. I use it.
  • Fourth Frontier Zone: Checks my heart under load in hard sessions.
  • Oura Ring 5: My partner’s recovery tracker of choice.
  • Eight Sleep: A cooling mattress cover my partner and I use nightly.

Watches and sensors

On the bike

Home and indoor training

  • NPE Runn: Makes my basic treadmill smart, sending more accurate speed and distance to my watch and Zwift. I use it.
  • Google Wifi: Keeps Zwift connected in my pain cave. I use it.
  • Apple TV 4K: Zwift on the big screen. I use two.
  • Google Nest Doorbell (wired, 2nd gen): My video doorbell, running in both Google Home and Apple Home via Starling. I use it.


Reader-Powered Content

Buy me a coffee

This content is not sponsored. It’s mostly me behind the labour of love, which is this site, and I appreciate everyone who supports it.

Support the site: Follow (free, fewer ads) · Subscribe (paid, ad-free) · Buy Me A Coffee

Written by real people, with AI assistance. Fact-checked and verified for originality. See the Editorial Policy. FTC: Affiliate Disclosure — some links pay commission. As an Amazon Associate, I earn from qualifying purchases.

Leave a Reply

Your email address will not be published. Required fields are marked *