The calculation of the instant pace in version 7.11 deviates from the actual speed in about 0.5 min/km to 1 min/km.
The calculation of the instant pace in version 7.11 deviates from the actual speed in about 0.5 min/km to 1 min/km.
All,
It looks like progress is being made on this as we hope to be addressing this in the next software update for this device. At this time, we do not have a timeline for the release of this future software…
All,
Per my last post (7 days ago), progress is being made and we would like to get a better understanding of how many users are affected by this disruption. We are still asking for some information from…
All,
This should have been resolved in sw 14.52. If you are still experiencing this, please start a new thread.
For fastest and the most detailed assistance, we encourage you to reach out directly to your…
Any progress on this Issue Garmin-Kevin?
When is the next release planned?
If Garmin uses something like Git in conjunction with the fact that the problem is very easy to reproduce, troubleshooting should…
I did 8 sprints today at 2:16/km and got 0.1 anerobic benefit so annoying. My purple training load bar is way way off its 125 whilst blue and orange are in the thousands
I've been noticing this too. I'm wondering if stride stuff reset with updates? Either way it's really annoying for sprint intervals since it's crazy far off now
Pierangelo75 I appreciate the contribution to the thread. If you choose to reconsider and reply to my email with the requested information, I would be happy to continue by submitting the report of your data to Engineering for investigation.
I had a 5k race yesterday, and Instant pace took well over 3 minutes to latch on.
I only relied on my lap time for this race, so I still managed to race the way I planned.
The last time I had the instant pace bug was on 30th November at a 3k time trial.
The only common thing between these 2 runs is that I did not run with my phone.
I think it is a possibility that this issue can only occur when the watch is not connected to a phone.
If anyone else has faced this issue while running with the watch connected to the phone, please let us know.
It looks like Garmin refuses to do anything about this issue without a giant list of things to do from us.
It helps to confirm a possible hypothesis before even attempting to gather further data about this bug.
The new beta roll out has no mention about this issue. It is at 15% roll out today, if it is available for my account, I'll update to beta today.
Even when you answer all the questions they refuse to pass along to engineering. I don't know what the point of that is
Also I took screenshots on the watch. Thats dated. That's the data point to investigate. That is what's wrong.
I bring my phone everytime and the instant pace is way wrong. Now I can't even get my sprints to be categorized with any anaerobic benefit
The problem continues for me:
https://connect.garmin.com/modern/activity/10283370500
Perhaps this is because I did not receive the updated GPS or SensorHub firmware with 13.21. Not sure why.
My software versions are
MAIN 13.21 / GPS 6.60 / WiFi 4.01 / CIQ 3.3.6 / BMX 9.0.2 / WHR 9.00.02 / ANT, BLE, BT 6.15 / Sensor Hub 20.06 / Modem 1.41