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

Average pace issue

Since 30/4 , both of my run has been wrong....on Strava, it's totally normal, implying the raw data should be fine, but on Garmin connect Android app, the lap display calculation is de definitely off (notice how the step avg pace and the actual per km avg pace diff.).

Top Replies

Garmin-Luke over 1 year ago +3

All,

We have been able to reproduce this internally and are currently looking into a resolution for this disruption. Once we have any updates, I will be updating this thread. At this time, no further information…

All Replies

0 MK over 1 year ago

I'm having the same issue... I noticed it started a few days ago. I'm on the android app as well.

0 MK over 1 year ago

I went back to earlier activities and I noticed the same problem. Might be an app update the broke the step average... Do you have the same issue on earlier runs? (I went back to January and still spotted the problem. I can swear it was fine back then)

0 Northman over 1 year ago in reply to MK

I have the same issue, even for older runs, where the pace was definitely shown correct (1-2 weeks ago). The error occurs only for the fast intervals and not for warm-up, the rests in between or cool-down. The shown pace would be correct for the distance but half the time...

The pace is correct in the web version. It affects only the app.

0 MK over 1 year ago in reply to Northman

My warm ups and cool downs are also messed up, unless they only have one lap in them, then it is fine... I confirm it's only an android app thing for me, as it displays as expected in the web app.

EDIT: Typos

0 Garmin-Luke over 1 year ago

All,

We have been able to reproduce this internally and are currently looking into a resolution for this disruption. Once we have any updates, I will be updating this thread. At this time, no further information is necessary. Thank you for your patience while we work on this disruption.

0 aidandowd over 1 year ago in reply to Garmin-Luke

I am still seeing this issue. Do you know when it will be resolved?

0 Northman over 1 year ago in reply to Garmin-Luke

Even the last app update (4.65.1 / 11th April) has the issue.

0 MK over 1 year ago in reply to Garmin-Luke

Thanks Garmin-Luke

0 MJ over 1 year ago in reply to Garmin-Luke

It looks like this might be a pretty simple coding error. For multi-segment groups of runs, it appears that the pace is currently being calculated as the total time / (total distance * number of segments). I suspect the intent was to sum the individual segment distances, but mistakenly the code is repeatedly using the total distance for the group instead of the individual segment distances.

This seems to be the case in what I see for my personal runs and also matches the OP's posts.

It would be nice to get this fixed in the next release.

0 Barman1234 over 1 year ago

bug still on ver 4.65 from 11 april