Related
Options

Fenix 8 v22.35: Pace stays at 0:00 and gets stuck, even though GPS is working fine

Magnutre

Hi everyone,
I’ve been encountering a recurring issue since the latest software update. On both Monday and today, I experienced a bug with my pace display during my running workouts: the pace suddenly drops and remains stuck at 0:00 min/km.


Pausing and resuming the activity seems to fix the problem temporarily, but it recurs very quickly. It doesn't appear to be a GPS signal issue, as the route is tracked correctly on the map in real-time, and auto-laps are still triggering as expected.
However, the data analysis for running dynamics (power, ground contact time, etc.) is completely skewed. Furthermore, the pace data on Garmin Connect remains at 0:00. Interestingly, while the data is displayed correctly on Strava, there is a discrepancy between the interval times recorded on Garmin versus those shown on Strava.


On Monday, I tried a soft reset (holding the Light button), but the problem returned today. This time, I attempted to clear the temporary files. Notably, I haven't had this issue on other days; it only occurred this Monday and Wednesday during track sessions with my running club (in a group of about 10 people).
Has anyone else encountered this issue? If so, have you managed to resolve it without having to perform a full factory reset of the watch? This bug is really frustrating because I had to run 'blind' on Monday, and I had to stop and restart the activity today just to get it to work. It’s particularly concerning as I have a race scheduled for this Sunday.

Top Replies

All Replies

  • 0 in reply to 8253847

    Be careful last time i did an intervall an it didn‘t stuck. Next time it does…

  • 0 in reply to 7336854

      Thank you for reporting this concern. I have reached out to you to collect details of this concern via email. 

    **

  • 0 in reply to Garmin - LF

    I can also confirm that a hard reset without restoring from a backup has solved the issue for me. Redoing all my customisations by hand has been annoying, though. I am crossing fingers that the bug does not reoccur.

  • +1 in reply to Pasotaman

    Thank you for your patience. We really appreciate you taking the time to help us get this reported, so we can work to get this resolved. Our engineers are still investigating this concern. Once there are any more specific updates, we will post here again. So be sure to bookmark this thread. 

    In the mean time, if you experience this concern, you can pause and unpause your activity to bring the pace back. 

  • 0 in reply to Garmin - LF

    Just to confirm that this issue still exists in 22.41 as it happened to me again this morning.

    The pause and restart work around does help to an extent, but as the issue repeats it's not ideal.

    This morning I did a 3 mile run with some sprint/fast intervals included.

    The watch reset pace to zero during the first interval. I paused and restarted and the pace came back.

    The pace remained for the second interval but then reset to zero on the third again.

    Pausing and restarting brought it back again, and the fourth interval recorded correctly.

    So you really have to constantly check your pace reading and be prepared to pause and restart regularly which isn't great. 

    I've not tried the factory reset yet as I keep hoping whatever the latest update is will fix this, but the will be my next step I think.

  • 0 in reply to 7336854

    Same here, it still exists in 22.41 during Quick intervalls and also normal running activities...

    It’s really annoying having to keep an eye on the pace the whole time, yet still missing it—usually during the high-intensity phases of the intervals, when not seeing the pace is most bothersome. 

  • 0 in reply to sirvival007

    Thank you for the update. You are correct. Our engineers are still investigating this concern. So a fix has not yet been released for this. Once there are further updates, we will post these here. So please keep this thread bookmarked.

    And thank you for your patience. 

  • 0 in reply to Garmin - LF

    The issue has persisted for 10 weeks now. My patience has run out. I’ve now resolved the problem myself by switching to the Coros Pace Pro. Everything is working perfectly again.

  • 0 in reply to BurkhardtS

    Same here, I sold the Fenix 8 Amoled and I am now using a Coros Nomad. I cannot afford to keep a 1000€ device that no longer does its main function. I also sold the Edge 540 for the same reason, too many bugs ruin the experience. 

  • 0

    They say that when the level of frustration becomes high enough, you’re ready for a change.

    I’ve used Garmin and Fenix ​​watches since the Fenix ​​2—followed by the 3HR, 5, 6, 7, and now the 8—for mountaineering, outdoor activities, running, training, and tracking, and I was willing to pay the premium price for quality.

    But lately, the products haven't come anywhere close to living up to the marketing claims; the constant software issues and the complete disregard for what users and customers actually say or want have simply become infuriating.

    And as if that weren't enough, now they want us to pay for a subscription, too.

    The market regulates itself; from now on, I’ll be looking at other manufacturers.

    Good work, Thanks @garmin