u/the5krunner

On a Fenix 8 AMOLED running software 22.41, pressing the upper right button to open the activity list returns the watch to the watch face and dims the screen roughly three times in ten. The same thing happens while scrolling through glances, sometimes mid-scroll. The behaviour matches the palm gesture, which is the deliberate screen-off action, being triggered when the palm is nowhere near the watch. One owner recorded video of it and posted a full test log in the thread on the Garmin forum.

Disabling touch entirely stops it. That is the diagnostic rather than a fix, since it confirms the touchscreen is registering a palm cover, but it also tells anyone who needs a working watch this week that button-only operation is stable.

Turning always-on display off, returning to the watch face with the lower right button, and turning always-on display back on clears the fault. It holds until the next restart, at which point it returns. Toggling always-on display without first returning to the watch face does not clear it, so the order of those steps matters.

Restoring settings from a backup makes it substantially worse. A full reset with data, set up without a phone and without restoring, produced no occurrences at first and around one percent after a restart. Completing the transfer wizard from a backup taken on an Epix Pro Gen 2 brought the rate straight back to between twenty and thirty percent. Two soft resets before that had no effect at all.

Garmin has asked the reporting owner whether a hard reset and re-enabling touch changes anything, and the thread is still open.

Did turning always-on display off and back on clear the false palm gesture on your watch?

The optical heart rate sensor on the Suunto 9 Peak Pro stops mid-night on a recurring basis. The green LEDs go dark, the heart rate screen sits on Measuring indefinitely, and the sleep record ends at the moment the sensor stopped, so a full night is logged as one or two hours. Recovery and HRV figures for that day are built on the truncated record. Owners have tracked it across software 2.48.16, 2.50.26 and 2.50.28, and the reports continue in the thread on the Suunto forum.

A soft reset restores the sensor. Sync the watch first if it is not permanently connected to the phone, because the reset is done from the watch and any unsynced data on it is worth protecting before rebooting.

Toggling Power Saving mode on and then off again brings the sensor back without a reboot. One owner reported the same result from switching energy saving mode on and off. This is the faster route and it avoids the sync step, so it is worth trying before a restart.

The fault has a long history of appearing to be fixed and returning. One owner ran firmware 2.40.44 for an extended period specifically because every release between 2.40.44 and 2.48.16 reintroduced it, and downgraded after each update. A moderator tested a 9 Peak Pro over roughly a week without a recurrence and reported the sensor working, then an owner recorded a stop after a month of clean nights, which shows a week of testing does not clear the fault. Turning SpO2 off has been suggested and has not produced a difference for the owners who tried it. The same stop has been reported on the Race S.

The frequency has risen through August 2026. One owner who had seen it once a month, always between the 17th and the 19th, logged two stops in the first week of August and another on the night of 14 August.

Did toggling power saving mode on and off restore the sensor without a reboot on your watch?

The daily suggested workout on an Edge 840 can stay on the previous day's session even after the head unit has synced with the phone. Powering the unit fully off and back on makes the correct workout appear straight away. Owners who also carry a Forerunner 265 or a Forerunner 965 see the watch update correctly on the same account on the same morning, so the plan itself is right and only the Edge is showing stale data. The reports and Garmin's response are in the thread on the Garmin forum.

The fault sits in the wake path rather than the sync. Waking the unit from sleep or suspend leaves several screens rendering whatever they held when the unit went to sleep, and the training days widget shows the same behaviour, with the marker bar staying under the day the unit was last used. Scrolling to the very bottom of that screen and back forces a redraw and the widget corrects itself. One rider reports the stale state appears only when the unit is woken before noon in Central European Time, and never in the afternoon.

Powering the unit fully down rather than short-pressing to sleep is the reliable workaround. A short press puts the Edge into standby, which is the state that produces the stale workout, and a long press through the power off prompt clears it. Not every owner gets a result from this. One rider on an 840 with a synced phone and a 965 reports the workout does not change after a full power cycle either.

Garmin has an open investigation and has added affected riders to it by name on the thread. The same behaviour has now been reported on an Edge 1040 paired with an Epix Gen 2, where the two devices showed matching workouts until roughly a week ago and have since drifted apart.

A separate discrepancy appears in the workout itself. One rider with 316W set as the auto-detected FTP on both an Edge 840 and a Forerunner 965 found the ten second interval targets in the same suggested workout differed between the two devices, which points at the workout being generated on the device rather than pushed intact from Garmin Connect.

Did a full power off and on refresh the suggested workout on your Edge?

Amazfit has shipped native FTMS connectivity for its Rowing Machine profile, so the watch now pairs directly with FTMS-compatible ergs like the Concept2 RowErg and shows power and distance on the wrist instead of just the erg console.

Garmin does not have this built in. Garmin owners get the same data only by buying a third-party Connect IQ data field from an independent developer, unlock-coded per device, and it is not part of the native experience.

The same update also adds Manual Rest tracking in Pool Swimming, an Always Locked touchscreen mode for wet or gloved hands, and an Athlete Defaults profile that turns on Do Not Disturb, mutes alerts, and sets GPS to maximum precision automatically. Availability varies: Always Locked skips the T-Rex 3, and Athlete Defaults is limited to the Cheetah 2 Ultra, Cheetah 2 Pro, Balance Ultra, and Balance 3.

Is native FTMS support the kind of thing that actually moves a buying decision, or does it only matter to the small number of owners who already train on a rowing machine?

Further reading: https://the5krunner.com/2026/08/10/amazfit-ftms-rowing-update/

Since software 22.35 the Fenix 8 drops running pace to 0:00 at the point you enter a fast interval, then holds it there for the rest of the activity. GPS continues tracking the route correctly and distance still records, but running dynamics, running power, and all pace data on Garmin Connect are corrupted from that point. Owners who inspected their FIT files on the thread found enhanced_speed falling to 0.000 metres per second after the first thirty seconds of a hard effort, which is why Connect reports a pace near zero or close to an hour per kilometre.

The fault has been reproduced with an external heart rate strap, with a foot pod, and on GPS alone, which rules out a single accessory as the cause.

Pausing and resuming restores the pace field temporarily, but it drops again at the next hard interval, making it a mid-session rescue rather than a fix.

Garmin's troubleshooting sequence on the thread runs in order:

1. confirm no battery saver mode is active,
2. confirm no focus mode is reducing satellite settings,
3. restore the activity to defaults from activity settings, then
4. reinstall the firmware from System, About, eight presses on the light button,
5. Reinstall software.
6. A factory reset without restoring a backup is the final step, since a restored backup can carry the fault back.

None of these has been confirmed to hold through a full interval session, so treat them as diagnostic steps.

Did a clean reinstall without restoring a backup get pace tracking through a full set of fast intervals?

On firmware 22.35 the Enduro 3 returns to sleep mode on its own after you manually end sleep focus, as long as you are still inside the scheduled sleep window. The sequence is consistent: end sleep focus, then stay still or cover the watch, and it drops back into sleep mode. Notifications stop arriving until you end sleep focus again. The same behaviour appears on the Instinct 2X. The owner who filed the bug discovered it when alerts failed to come through after waking.

Garmin confirmed on the thread that while the watch is inside the scheduled sleep window, re-entry into sleep mode is driven by activity level, not by the manual end command you just gave. Low movement reads as going back to sleep, so the watch re-enters the mode.

Starting any timed activity blocks re-entry more reliably than movement alone, because it overrides the inactivity logic for the whole session. That is the quickest fix.

The lasting fix is to set the sleep schedule in Garmin Connect so the watch is outside the scheduled window at the point you normally wake. Once the scheduled wake time is earlier than your actual rising time, the inactivity logic does not fire. This is configuration rather than a firmware patch, so anyone whose schedule runs past their real wake time will keep seeing it.

Did adjusting the sleep schedule sort it, or does it still re-trigger?

On firmware 31.29 and later, the Edge 1050 resets its alert tone volume to zero every time the unit is powered off and on again. Turn and navigation prompts, sensor connection alerts, and lap tones all go silent on the next ride without any warning. Owners on this thread confirm the volume stays at whatever level it was set during the session, then returns to zero on the next power on.

The fix each time is to go into Settings, then System, then Display and Sounds, and set the tone volume manually before starting the ride. It takes about five seconds but has to be done after every cold start. Setting a data field on the activity screen to show the tone volume level makes the reset visible at a glance rather than discovering it mid-ride when a turn prompt fails to sound.

Garmin has not patched this in any release up to 31.33. Owners who tried a factory reset report the behaviour returns after the first power cycle following setup.

Does yours reset every time, or only after a longer time off?

After updating a Kickr v6 to firmware 5.6.13, the trainer drops its Bluetooth connection to Zwift mid-session and the power reading disappears. The connection returns within a few seconds in most cases but the dropout is enough to break ERG mode and force a manual gear change to stay near the target wattage. Owners on this thread report it on both Windows and macOS, and with both the Wahoo companion app and direct Bluetooth connections, which rules out a platform-specific cause.

Pairing the Kickr to Zwift over ANT+ instead of Bluetooth resolves the dropout for most owners. The connection stays solid through sessions that previously dropped multiple times. If your trainer is near the computer, a direct ANT+ USB dongle placed close to the Kickr rather than at the machine is the setup that holds best.

Switching from Bluetooth to ANT+ requires unpairing the trainer from Zwift's Bluetooth device list and re-adding it as an ANT+ power source. Zwift will show it as a separate device entry. Once paired over ANT+, ERG mode works normally and the power reading holds through intervals.

Wahoo has not released a firmware update that addresses 5.6.13. The Bluetooth stack change in that release appears to have introduced a timing issue that ANT+ avoids entirely.

Has the ANT+ pairing held through full sessions for you, or are you still seeing drops?

The Edge LIGHTS battery field is designed to show the lowest battery among all connected lights. With a Varia RearVue 820 connected on its own, the Edge reports its level correctly. Add a second light such as the UT800 and the field switches to tracking the headlight instead of the radar, so an RV820 sitting near 30 percent can read close to 80 percent on the Edge. Owners on this thread describe it on the Edge 1050 with the RV820 paired alongside a headlight.

The RV820 connects to the Edge over Bluetooth as a radar but uses ANT for light controls and battery reporting. The battery rollup across the light network stops returning the radar's lower value once a second light joins, so the figure on screen tracks the headlight rather than the unit that will run out first.

Two methods give the true level. Connect only the RV820 before a ride, where it reports correctly, or keep the Varia phone app open during the ride. The phone app shows the radar battery independently and gives the audible low alert. Third-party Connect IQ battery fields written for older Varia units do not yet support the RV820.

Until the reporting is corrected, charge the RV820 every two to three rides rather than trusting the Edge figure. The wrong reading only appears when more than one light is connected, so a radar-only setup shows the correct level.

Anyone found a Connect IQ field that reads the RV820 correctly when a headlight is also connected?