SW 7.60 Treadmill Calibration missing values?

Is anyone else having this issue after taking the 7.60 upgrade? After being updated to SW7.60 I noticed that doing the Calibrate & Save while in a treadmill run is missing the values in the decimal point from .61-.99 - you are only able to select values from .00-.60.

I also noticed that the calibration doesn't apply. For example if I run 2 miles on the treadmill at 8min pace and the watch is only recording 1 mile at 16 min pace, I perform the calibration to set the watch distance to 2 miles. If I immediately start another treadmill run after calibrating the watch still is reporting 16 min pace. 

 

  • I haven't noticed the issue with selecting >.60 but do have the same issue with the calibration not carrying over to the next activity.

    I am on v7.60

  • I have not been able to reproduce, so if you are still seeing this, could you reach out to me via a Private Message so we can work together to find out if this happens via a setting you are using and I am not?

  • Former Member
    0 Former Member over 6 years ago

    Did garmin figure this issue out yet?

    I’d been having same issue with version 7.60 as well. (And replicate same issue Allen and Leefox were having. It seem that every time I got on to treadmill for 5 mile run, reading got worse and worse. Calibration is not registering and is not carried over to next work out. it used to near accurate 8:30/mi (which was consistent with my treadmill) to 12:00/mile, 15:00/mile and finally stuck at around 18:00/mile. After running 5 miles, my watch would register 2.7-3.25 miles total. Calibrate&save will let me adjust upto 5.50 but missing 0.50 thru 0.99 in selection process (I guess it’s fine with me that it’s missing 0.50-0.99 since I’m running 5.03 miles). 

    To note, I had my original fenix 5 plus for 2 month and was running 7.10 without this issue until 7.60 upgrade, when treadmill recording started going wrong. I was still under 90 day warranty from local shop so I exchanged my fenix 5 plus for new. Same issue after 2 weeks of use, which leads me to conclude software issue...