Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

    Me too. the workout screen eventually says the pace is 0:00 when I use either quick intervals or preprogrammed intervals and this is what is shown in the charts in garmin connect. However, the standard watch screens show the pace around what I feel to be right and the intervals in garmin connect show this time, pace and distance etc (in the table not on the chart). The charts illustrate the intervals changing at the right point, just 0 pace (and other data) during them

  • 0

    I am experiencing the same issue. During programmed strides before my workouts. Is this addressed in v22.38?

  • 0

    Same for me. It started about 3 weeks ago and it happens when there is a sudden increase in running pace, both in a programmed run and a free run. It is temporarily fixed by pause and resume later but it comes straight back again. Overall distance logging is fine - it is only the pace that drops to zero.

  • 0

    Hello  ,

    Is there a timeline for solving this issue?

    My watch (Fenix 8 51mm AMOLED) updated to v22.38 yesterday. I was hopeful this annoying bug was solved. However, it was nog addressed in the changelog, and this morning I experienced the 0.00 pace again at intervals on the track with this new firmware.

    During the start of a running workout (standard running application) the pace is correctly displayed (around ~5.00 min/km in my case). At the moment I start with strides (~3.00 min/km) or intervals (around ~4.00 min/km), the pace drops to zero. This is not connected to steps in a structured workouts, this morning I increased the pace without changing the workout step or pushing the lap button.
    One the pace shows 0.00, it often remains at zero during the rest of the workout. However, I have noticed that after the intervals, during cooldown, the pace restores when the watch is paused for a moment (drink break). As long as you run 'slowly' again, the pace is displayed normally again.

    Also strange: the average lap pace is correctly displayed. The GPS track is unaffected, no artefacts. So the watch is correctly registering the location data. This is an error in the calculation of the pace in the new firmware(s). Strava recalculates pace etc. based on the GPS data, and shows normal pace graphs.

  • 0 in reply to mordacks

    Thanks for posting, I also upgraded to 22.38 hoping that this was fixed. This is bad news, Above all I need a device that is reliable and my Fenix 8 has not been reliable for too long Expressionless . If this is not fixed during July I will seriously reconsider permanently switching to another brand, race season will resume and I need reliability above every other consideration.

  • 0 in reply to 8253847

    Agree. And this affects all flagship running models reading through the forum posts. Which means many runners training more seriously are affected by this. Garmin really should release a fix ASAP. In the meantime, can a moderator propose an easy way to downgrade to a version before 22.35? 22.35 is where this started.

  • 0

    I can reliably reproduce this issue on firmware 22.38, just go for a regular road run, do a sprint (I guess that anything below 3m20s/K). Pace will get stuck at 0.00 as soon as you hit 3m20s/Km or less. You can pause and resume to get it working until the next sprint, of course.

    I have a race this Sunday, I've asked in the support ticket for a downgrade, I cannot race with the Fenix 8 as it is now.

  • 0

    I'm also experiencing this issue. I also have a Fenix 8 and a HRM-600.

    As you can see after about 4km the pace stopped being measured, same for the running power (probably derived from the running speed).
    This is a recurring issue which messes with every metric on my training program.

  • 0

    I have same problem. Fenix 8 51mm AMOLED

  • 0 in reply to 4759186

    I will reach out to those of you I have not already, to collect details for this investigation. 

    **