Firmware 5.20 and current pace

Confirmed. It's jumping around like squirrel on cocaine. :p

@PMctheory11
5sec smoothing in some custom app or stock? Thx!

I see the same thing. On 4.70 my pace graph was relatively smooth. On 5.20 it's all over the place.

Both walks were done using a foot pod with GPS as the speed source. The next time I'm going to try it with the foot pod as the speed source, instead of GPS.

I was using GPS + GLONASS and my track is good.

Did a walk today with the foot pod as the speed source. Pace curve on Garmin Connect is smoother and flatter (I was walking at a consistent cadence and therefore pace).

The data on Training Peaks reflects what I saw on Garmin Connect. Strava was a different story. Strava disregarded the pace data from the foot pod and recalculated from GPS. The pace curve on Strava was all over the place like yesterday's walk.

Overall average pace was correct, as were the kilometre splits, as far as I'm aware. I noted that yesterday when I looked at my instantaneous pace whilst I was out, it was not jumping around all over the place and was reasonably consistent. Not like the graph in Garmin Connect shows.

Today I thought the instantaneous pace from the foot pod was a little high. It could be that it's not yet calibrated properly.

Not just a display issue

I want to reiterate that this isn't a display problem. It's actually tracking pace wrong. My graphs are super jumpy now too, in clear contrast to the relatively smooth lines before. When I set a narrow pace window for a workout, the alerts are all wrong. For example, I'll slow down to what feels like 9:30 pace and it still beeps, thinking I'm going faster than 8:15.

Even 10 second smoothing doesn't help. For now I'm going to wear one of my kids watches on my other arm, so I can have accurate current pace.

Same here, although I use a 630 (which also has this firmware).

https://connect.garmin.com/modern/activity/1302631779

Hi !

Today, first run with v5.20 and indeed, the pace graph is nothing but spikes and peaks with even holes as if I'd stopped several times where I ran constantly.

This needs to be fixed ASAP ! I'm always wondering how a firmware update can ruin functions from the previous versions that much (not only for Garmin, just for all devices from all companies).

Constant and regular pace is a key feature of such devices !

Cheers
Jay

Seriously, does anybody test the new firmware and actually go for a run before it's released to public? Out of 10.000 people working for Garmin you would of thought someone would notice.

After 4.70 I changed from current pace to 5s rounding (i use single run field).
Now I read that for new FW it does not help and rounding shall be longer.

Thank you guys for warning (luckily I skipped it - never install new FW before the race),

Totally agree with Savage711. Is it really so hard to get a device and run for 30 mins?
I can do it for you, Garmin, for free.
Just make sure I will be able to revert

We appreciate the discussion, and have escalated this issue to the device teams for further investigation and resolution.

We do apologize for any inconvenience that this has caused in the meantime.