Question 1

Why are my Komoot or Strava routes losing turn-by-turn cues when synced to Garmin?

Accepted Answer

Garmin applies its own course point schema when importing routes from third-party applications, which can rename, merge, reorder, or remove the turn cues created in Komoot or Strava. Komoot&#8217;s own support documentation describes this as expected behaviour at the point of import rather than a fixable bug. The issue affects the Fenix 7, Fenix 8, Epix Gen 2, Forerunner 955, and Enduro 3.

Question 2

How do I get Komoot turn-by-turn navigation to work on my Garmin watch?

Accepted Answer

Disconnect and reconnect the Komoot integration within Garmin Connect, then trigger a fresh sync. This regenerates the course file and resolves missing turn prompts for most owners. If the resync does not help, build the route in Plotaroute and export it as a Garmin FIT file directly into the device&#8217;s Garmin/NewFiles folder, which bypasses Connect&#8217;s course processing entirely and delivers the turn cues as authored.

Question 3

Does using a GPX file transfer fix missing Garmin navigation from Komoot?

Accepted Answer

GPX transfers go through the same Garmin Connect import schema that causes the problem and do not reliably resolve it. The most dependable workaround is the Plotaroute FIT file export directly into the NewFiles folder, which avoids Garmin Connect&#8217;s pipeline.

Question 4

Has Garmin fixed the Komoot course point sync issue?

Accepted Answer

Garmin addressed a related course point fault in the Connect backend in late 2025 that affected natively built routes. That fix does not extend to routes arriving from third-party sources such as Komoot and Strava, which remain subject to the import schema behaviour. No further fix has been confirmed as of May 2026.

Question 5

What is the Tacx ERG spiral of death and how do I stop it?

Accepted Answer

The spiral of death describes ERG mode progressively losing resistance control, with the trainer escalating toward its maximum output as the rider struggles to hold the target wattage. The most common cause is cadence dropping below approximately 70 rpm, at which point Tacx ERG regulation breaks down entirely. Holding cadence consistently between 70 and 135 rpm prevents it in the majority of cases.

Question 6

What cadence range works reliably for Tacx ERG mode?

Accepted Answer

Tacx ERG mode controls resistance reliably between approximately 70 and 135 rpm. Outside this window the trainer stops regulating effectively and power tracks gear selection and cadence instead of the workout target. This applies across Tacx Neo, Flux, and Boost trainer families.

Question 7

Why is PowerMatch causing my Tacx trainer to max out resistance?

Accepted Answer

Pairing a separate power meter such as the Garmin Rally pedals or a crank-based unit with PowerMatch enabled can create a feedback loop between the trainer and the meter, driving resistance to maximum. Disabling PowerMatch entirely, or replacing it with a fixed power offset in the training application, resolves this in most cases.

Question 8

How do I fix the Tacx Neo 2T power delay and cadence over-reading after firmware 2.6.0?

Accepted Answer

Garmin released firmware 2.7.0 for the Neo 2T to address the cadence over-reading and power delay introduced by 2.6.0. Install it through the Tacx Training app. Confirming you are on 2.7.0 or later should be the first step before investigating other causes of ERG instability on this trainer.

Question 9

Why does my Tacx trainer keep disconnecting after about an hour?

Accepted Answer

ERG control cutting out after approximately one hour and reconnecting in cycles is typically linked to the Bluetooth connection rather than the ERG algorithm itself. Running the trainer control over ANT+ rather than Bluetooth resolves the dropout behaviour on setups where the head unit or training application supports ANT+.

Question 10

Why have my Garmin watch notifications stopped working?

Accepted Answer

The most common causes are a Garmin Connect app update that changed notification behaviour, a phone OS update that reset notification permissions, or a disrupted Bluetooth pairing. On Android, Garmin Connect 5.18 silenced the watch whenever the phone was in Do Not Disturb mode; upgrading to 5.19 restored independent watch DND. On iPhone, the Show Previews setting under Settings, Notifications must be set to Always or When Unlocked for alerts to reach the watch.

Question 11

How do I fix Garmin watch notifications not working on Android?

Accepted Answer

Confirm Garmin Connect is on version 5.19 or later, which reversed the DND mirroring change introduced in 5.18. If updating the app alone does not resolve it, force-quit Garmin Connect, clear its cache, and reboot the phone before reopening the app. For persistent cases, remove the watch from the phone&#8217;s Bluetooth device list, power-cycle both devices, and pair again from within Garmin Connect rather than from the phone&#8217;s Bluetooth settings.

Question 12

Why are my Garmin watch notifications not working on iPhone?

Accepted Answer

Apple requires Show Previews to be set to Always or When Unlocked under iPhone Settings, Notifications for any application to push alerts to a paired Bluetooth device. A setting of When Locked or Never silences the watch entirely. Background App Refresh for Garmin Connect must also be enabled, and Low Power Mode will suppress notification relay when active.

Question 13

Why is my Garmin watch not showing call or text notifications?

Accepted Answer

If platform-specific steps have not resolved the issue, a clean re-pair is the most reliable fix. Remove the watch from the phone&#8217;s Bluetooth device list entirely, power-cycle both devices, and pair again from within Garmin Connect. A factory reset of the watch alone, without first removing the Bluetooth pairing entry from the phone, does not fix the problem in most cases.

Question 14

Why is my Garmin watch battery draining fast after a firmware update?

Accepted Answer

Three distinct causes account for most post-update battery drain. The optical heart rate sensor can get stuck in active mode and sample continuously around the clock; starting an activity and backing out from the initial GPS screen resets it. The battery gauge can lose its calibration reference values; a full discharge and recharge cycle restores accurate reporting. A Garmin Connect or Connect IQ application can also remain stuck running in the background overnight; the phone&#8217;s battery statistics will confirm this, and force-quitting the app resolves it.

Question 15

Why is my Forerunner 255, 265, or 955 battery dying quickly after firmware 27.09?

Accepted Answer

The Forerunner 255, 265, and 955 are among the models most affected by battery drain following firmware 27.09. The most common cause is the optical heart rate sensor remaining in active mode after the update. Starting an activity, waiting on the initial activity screen until the GPS bar appears, and then backing out without recording resets the sensor to its resting state. Battery life typically returns to normal within the subsequent charge cycle.

Question 16

How do I recalibrate my Garmin battery gauge after a firmware update?

Accepted Answer

Run the watch down to a low charge level, then charge it fully and leave it connected for several minutes after reaching 100 percent. This re-establishes the minimum and maximum voltage reference values that the gauge uses to estimate remaining charge, and restores accurate battery reporting.

Question 17

Can a Connect IQ app cause Garmin battery drain?

Accepted Answer

Yes. A recently installed Connect IQ application or third-party watch face can remain continuously active after a firmware update, loading the Bluetooth connection and draining both the phone and the watch. Check the phone&#8217;s battery usage statistics: Garmin Connect or Connect IQ showing several hours of background activity during an inactive period is the diagnostic signal. Removing the recently added app or watch face eliminates the drain.

Question 18

Why is my Garmin Coach plan not showing on my watch?

Accepted Answer

The most common cause on current app builds is the calendar sync selection in Garmin Connect. Enabling only the Garmin coaching plans option is not sufficient; you also need to enable events and challenges in the same calendar sync list for the plan to reach the watch. A second cause is the watch holding a stale calendar state, which requires a full Garmin Connect reinstall to clear. A third cause, for owners with both a watch and an Edge, is the primary training device being set to the wrong unit under Manage Device Priority.

Question 19

How do I fix Garmin Coach not syncing to my watch?

Accepted Answer

Open Garmin Connect, go to calendar sync settings, and ensure both Garmin coaching plans and events and challenges are enabled. If the plan still does not appear, perform a full reinstall: log out of Garmin Connect, delete the application, unpair the watch from the phone&#8217;s Bluetooth settings, reinstall, and pair again. The plan should appear under Run, Training after the sync completes.

Question 20

Why does my Garmin training plan show in the app but not on the watch?

Accepted Answer

This is a known sync fault specific to Coach plans and structured training schedules. Manually created workouts sync without issue; only plans generated by Garmin Coach or imported structured plans are affected. The calendar sync checkbox fix resolves it for most owners on current app builds.

Question 21

Why is Garmin Coach not counting my completed workouts?

Accepted Answer

Garmin Coach sometimes fails to register a completed workout, recording the activity correctly but not marking the plan session as done and shifting the remaining schedule. Manually rescheduling the affected workout back to its original date in Garmin Connect and syncing restores the correct plan sequence.

Question 22

Why does my Garmin watch show the message 'Download your training calendar from Garmin Connect'?

Accepted Answer

This message indicates the watch is holding a stale calendar state and is unable to retrieve the plan. A full Garmin Connect reinstall resolves it: log out, delete the app, unpair the watch from the phone&#8217;s Bluetooth settings, reinstall, and pair again through Garmin Connect. Do not attempt to fix it by factory resetting the watch alone, as this does not clear the calendar state.

Question 23

Do Garmin AMOLED watches get screen burn-in?

Accepted Answer

Yes. Image retention has been documented on the Garmin Epix Gen 2, the Venu series, the Forerunner 265 and 965, and the Fenix 8. It manifests as faint ghosting of static watch-face elements, typically only visible against a solid-colour test screen. Once present, it is a permanent physical change in the panel and cannot be reversed through software or recalibration.

Question 24

Does always-on display cause burn-in on Garmin watches?

Accepted Answer

Always-on display is the primary risk factor in reported cases. Owners who run AOD continuously, particularly with a high-contrast watch face holding static elements such as a battery bar or fixed digits in fixed positions, are the cohort reporting retention. Owners using gesture or tap-wake with the standard display timeout overwhelmingly report no issues after one to two years of daily use.

Question 25

Which Garmin watches are at risk of AMOLED burn-in?

Accepted Answer

Any Garmin watch with an AMOLED display is subject to the same underlying physics. Confirmed reports span the Epix Gen 2, Venu 2, Venu 3, Forerunner 265, Forerunner 965, and Fenix 8. With the Forerunner 70 and 170 completing the transition of the Forerunner line to AMOLED, the risk applies to every current Forerunner model.

Question 26

How do I prevent burn-in on my Garmin Fenix 8, Forerunner 265, or Forerunner 965?

Accepted Answer

Leave always-on display disabled, or if you use AOD, select a watch face built to Garmin&#8217;s AOD style guidelines that use dimmed and outlined elements rather than solid bright fills. Lower display brightness and shorten the display timeout. Avoid third-party watch faces that hold bright static elements in fixed positions for extended periods. These measures applied from the start of ownership are the only reliable prevention; existing retention cannot be undone.

Question 27

Why is my Garmin watch not charging past 90 percent?

Accepted Answer

The Fenix 8, Forerunner 265, and Forerunner 965 developed a firmware fault following the March 2026 updates in which the charging circuit halts at 90 percent due to a coulomb counter calibration error. This is a software fault, not a hardware or battery failure. Garmin&#8217;s fix is firmware 21.20 for the Fenix 8 and firmware 14.18 for the Forerunner 265 and 965, installable via Garmin Express.

Question 28

Is the Garmin 90 percent charging issue a hardware or firmware fault?

Accepted Answer

It is a firmware fault. The underlying cause is a coulomb counter calibration error in which the firmware&#8217;s charge accounting diverges from the battery&#8217;s actual state, causing the charging circuit to stop prematurely at 90 percent. The battery hardware is not failing. Updating to the correct firmware version via Garmin Express resolves it.

Question 29

What firmware fixes the Garmin watch 90 percent charging bug?

Accepted Answer

Firmware 21.20 for the Fenix 8 and firmware 14.18 for the Forerunner 265 and 965. If the update has not arrived over Wi-Fi, connect the watch to a computer running Garmin Express and apply it directly. Do not replace the battery before confirming the firmware update has been applied, as the fault is software-side.

Question 30

Why are my Garmin watch charging contacts not working properly?

Accepted Answer

Sweat, body oil, and moisture accumulate on the rear charging pins as a thin film that progresses to visible green or white crust over time, causing intermittent contact. Symptoms include the cable connecting only at a specific angle, the charge indicator flashing and dropping, or charging starting and stopping in cycles. This affects every Garmin model with rear-pin charging from the Forerunner 245 series and Fenix 5 onwards.

Question 31

How do I clean Garmin watch charging contacts?

Accepted Answer

Apply isopropyl alcohol at 90 percent concentration or stronger to a soft toothbrush and work it in small circles across the four pins on the watch back and the corresponding pins on the charging cable. Distilled water on a cotton swab is a milder alternative for light accumulation. Do not use metal tools on the pins. The silicone dust caps sold for the charging port trap moisture against the pins and accelerate corrosion; remove them. Rinsing and drying the back of the watch after workouts and swims before re-wearing or charging prevents accumulation before it begins.

Tag: Firmware

#17 Deep Dive Feature Files: Week Ending 17 October 2026

#16 Deep Dive Feature Files: Week Ending 10 October 2026

#15 Deep Dive Feature Files: Week Ending 3 October 2026

#14 Deep Dive Feature Files: Week Ending 26 September 2026

#13 Deep Dive Feature Files: Week Ending 19 September 2026

Garmin CIRQA Update – Significant New Version and Fixes

#12 Deep Dive Feature Files: Week Ending 29 August 2026

#11 Deep Dive Feature Files: Week Ending 15 August 2026

#10 Deep Dive Feature Files: Week Ending 8 August 2026

#9 Deep Dive Feature Files: Week Ending 1 August 2026

#8 Deep Dive Feature Files: Week Ending 25 July 2026

#7 Deep Dive Feature Files: Week Ending 18 July 2026

#6 Deep Dive Feature Files: Week Ending 11 July 2026

#5 Deep Dive Feature Files: Week Ending 4 July 2026

#4 Deep Dive Feature Files: Week Ending 27 June 2026

#3 Deep Dive Feature Files: Week Ending 13 June 2026

#2 The Deep Dive Fix Files: Week Ending 5 June2026

#1 The Deep Dive Fix Files: Week Ending 30 May 2026