Endurance score over 65k

Got my Fenix 7 Pro 10 days ago and was looking at the Endurance score graph. I notice that I have an Endurance score from before the Fenix 7 Pro (I had a Fenix 5 Plus) which is over 65k so it messes up the graph.

Is it just me and is there any way to get rid of the earlier numbers?

Top Replies

Garmin-Laurie 8 months ago in reply to 8992279 +2 verified

Update September 17, 2024:

Our engineers are indicating the issue with extreme spikes in Endurance Score was resolved with the 16.22 SW update. So if you have not already, please update your SW to the…
Garmin-Laurie over 1 year ago in reply to dxbydy +2

Update: March 21, 2024

Our engineers did identify a software related concern that was causing a spike in the Endurance Scrore graph, after a new device was added. This has since been resolved with the…
dxbydy over 1 year ago in reply to Dan.Boilermaker +1

Yes - same on the watch. I have emailed support - lets see if they can do anything.

Image below.. The screen is not scratched - just a badly positioned old screen protector I had left from my Fenix 5…

All Replies

0 [Redacted] over 1 year ago

Wait, I thought Endurance Score isn't covered by True Up / Unified TS? 65k makes absolutely no sense anyway. lol

0 Dan.Boilermaker over 1 year ago

dxbydy said:
65k

65355 is the largest value of a 16bit unsigned variable. I'm assume that there is some sort of initialization issue with GC for data points prior to your actual data. Does the same plot show up on the watch? Might be a call to Garmin Support or just let it slide off to the left over the next few weeks.

0 dxbydy over 1 year ago in reply to Dan.Boilermaker

Yes - same on the watch. I have emailed support - lets see if they can do anything.

Image below.. The screen is not scratched - just a badly positioned old screen protector I had left from my Fenix 5 Plus ;)

0 MisterFrag over 1 year ago in reply to Dan.Boilermaker

Dan.Boilermaker said:
65355 is the largest value of a 16bit unsigned variable.

You transposed two digits, that should be 65535, not 65355.

0 dxbydy over 1 year ago

I am starting to wonder if it was because I had a non endurance score enabled watch when endurance score was introduced and then got the 7 pro. The 65535 numbers look to start when the 7 pro was released at the end of May when I had a 5 plus.

0 Garmin-Laurie over 1 year ago in reply to dxbydy

Update: March 21, 2024

Our engineers did identify a software related concern that was causing a spike in the Endurance Scrore graph, after a new device was added. This has since been resolved with the Q1 software update version 16.22.

If you are still experiencing this after you have updated the software to version 16.22, please feel free to reach out to me via Private Message.

0 8992279 8 months ago in reply to Garmin-Laurie

I am still having this issue and I am using 17.28. can you send me a PM?

+1 Garmin-Laurie 8 months ago in reply to 8992279

Update September 17, 2024:

Our engineers are indicating the issue with extreme spikes in Endurance Score was resolved with the 16.22 SW update. So if you have not already, please update your SW to the latest version. If you are still experiencing this specific concern, please fell free to contact me via Private message.