SW version 24.19 gradient issue

Hello,

With the latest FW release (24.19), I'm facing a severe issue with grade (percentage) : The slope values displayed by the device are incorrect.

For example, on a severe slope, gradient values of 1 or 2% are displayed instead of 9 to 10%, and sometimes even negative values are displayed ..... This was not happening with previous FW version ....

This happens whatever the speed is during the climb .

Despite this issue altitude values remain correct, only gradients are wrong.

Seems really like a software bug ???

Top Replies

All Replies

0 pxl 2 months ago

chfreund38 said:
really like a software bug ???

yes, all edge with this FW suffers from this,

but, who needs gradient info, anyway? it is just a number, why anyone cares ^_^

0 krazyeone 2 months ago in reply to pxl

Who needs Power data? speed , heart rate, all are just a number , who cares?

0 malo23 2 months ago

Same here. On double digit climbs I thought they must've lost one digit.

@garmin please fix that!

0 pxl 2 months ago in reply to krazyeone

krazyeone said:
Who needs Power data? speed , heart rate, all are just a number , who cares?

exactly! ;)

that's why you don't get reliable wrist HR data on any garmin watches now :D

it's not that all other metrics depend on HR :P

0 krazyeone 2 months ago in reply to pxl

I was sarcastic , for me is important to know if I am on 12 % or 8 %

to be trutalky honest I switched to Wahoo Bolt V2 only to display good gradient

0 raphnou 2 months ago

same issue....

0 2888722 2 months ago

Having the same issues. Talked to support and they are sending a new device. Just saw this I don’t want a new device just a fix

0 krazyeone 2 months ago in reply to 2888722

Maybe not all devices are affected by this bug

where can I speak with suport?

0 2888722 2 months ago in reply to krazyeone

I used the chat feature on the support web page.

0 FCA 2 months ago

I just contacted support too and they are sending out a refurbished replacement device and I have to send mine to them.

Seems a bit excessive for what appears to be a firmware issue, but nevermind.