This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Here we go again: altimeter is wrong on fast ascent

Here we go again! Today while i'm coming at home from the sea, i tried for the first time navigation and voilà: altimeter was totally wrong! When i was near my home that is about 110m asl, altimeter reported 75m! I tried to calibrate it but when i set correct altitude, it started to count slowly to calibrated altitude like my Fenix 5X did; altimeter was set on continous calibration. More info here: https://forums.garmin.com/forum/on-t...on-fast-decent ! I can't believe it! Luckily this time i bought it on Amazon, so if things don't change quickly, i'll return it and i'll stay with my Spartan Ultra that never had this bug!
  • Is this in the prod version now or just beta?
  • Roll out of the 4.00 production sw has seemingly been halted, so it may be a little while until someone can confirm (4.00 shouldn’t be much different to 3.56 beta, so the answer is likely yes).
  • Former Member
    0 Former Member over 6 years ago
    Is anybody else still seeing some slight elevation issues on fast activities (road cycling on rolling hills for example)? I'm seeing about 10 percent less elevation than I should. Its really just on quick changes at higher speed it seems. Runs, walks, etc seem better. I'm on 3.53 beta which should be the same as firmware 4.00...

    It also seems my altimeter isn't fast to change on the watch face (and slightly better on ABC widget).... which leads to the altimeter being off regularly when not in an activity. I have to calibrate a few times a day. I know weather plays a part. But is anyone seeing this? Being new to garmin does the watch face update altimeter real time or on a delay? Mine seems to be every 30 to 90 seconds.

    either way, altimeter and elevation are way is way better than it was a few weeks ago
  • ...does the watch face update altimeter real time or on a delay? Mine seems to be every 30 to 90 seconds.


    Typically the refresh frequency of data on watch faces is low (30 secs or more is normal) to reduce the hit on the battery.
  • Former Member
    0 Former Member over 6 years ago
    Typically the refresh frequency of data on watch faces is low (30 secs or more is normal) to reduce the hit on the battery.


    Good to know. Being new to Garmin, I'm still trying to learn all the ins and outs. Thanks!
  • Hey Group, Coming late to this thread here. I have had the Fenix 5 plus for a couple of weeks now and it looks like 4.0 might have fixed this issue. I am curious with those who don't have the 4.0 update yet, have you compared the elevation charts when the corrections are ENABLED vs. DISABLED in garmin connect. Just wondering if that option for now improves the accuracy of the activity. I know this doesn't help during the activity but at least the record is accurate??