Related
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

20.26: No altitude change during activity (recorded wrongly as flat with 0m elevation)

tomaskafka
11 months ago

Hi everyone, I've run into a problem with my Garmin Forerunner 955 after updating to firmware 20.26. Yesterday, during a race in hilly terrain, the altimeter got stuck at a single value:

The issue was also visible in the altimeter widget. While it was measuring normally before and after the activity, during the race (where other runners' watches measured about 150m of elevation gain), mine showed a flat line.

I ran the race using the Run profile with PacePro enabled, but navigation turned off.

This seems like a newly introduced bug, as I run often and this is a first time I have seen it, right after updating to 20.26.

  • 0 11 months ago

    I had the same problem on my last run

    Garmin 965 with version 20.26

    Sensor version 30.09

  • 0 11 months ago

    Have the same issue with the latest update. It also happened a few weeks ago on an older update. I find that if I check altitude during the run, the elevation data gets recoded correctly (instead of starting altitude and flat thereafter). I have since added altitude to my all in one data field. I hope this fixes it until Garmin fixes the bug on their end. It is extremely annoying getting 0 elevation gain after a hard workout!!!

  • 0 11 months ago in reply to DL

    Thanks. I have now added an Elevation field to my activity profile and this resolves the issue. 

  • 0 11 months ago

    There is a work around to resolve the issue untill Garmin makes a fix.

    On your watch just add an elevation field to your activity.

    Works for me.

  • 0 11 months ago

    Hi,
    Same here, no altitude change since firmware 20.26, Forerunner 255, Sensor Hub 31.09

  • 0 11 months ago

    Hi, it's the opposite for me. I just noticed that all my runs have been giving double the altitude for the past 12 days. I run every day, my runs have always been 80 to 150m of elevation, I do the same routes and I have 150 to 310m now, all the runs are similarly impacted. The battery that runs out at full speed on top of that, it's starting to be a lot for a watch of this range.

  • 0 11 months ago

    Thank you for sharing, everyone. Please answer the following so we can further investigate: 

    1. Is your elevation flatlining during every activity?
    2. Does your all day elevation/floors climbed data look normal (outside of activities), or is it also 0/flatlining?
    3. May we have permission to view your Connect account so we can view examples?
    4. May we, if necessary, have permission to reach you via email?
  • 0 11 months ago in reply to Garmin-Sierra

    Hi,

    I have the same issue on 255 after the update to 20.26. No issues before the update. 

    1. No. I had a run with realistic elevation data, then I had another one couple of hours later on the same day with flatline.

    2. Floors climbed looks normal. 

    3. Yes.

    4. Yes.

  • 0 11 months ago

    Hi,

    1. No. My first runs after update looked normal, but my last 3 all had this issue.

    2. Floors climbed looks normal. 

    3. Yes.

    4. Yes.

  • 0 11 months ago in reply to 1497946

    I’ve experienced this annoying bug in the last couple of weeks - note there is an option to enable elevation corrections in Garmin Connect - I’ve done this and then also reloaded to Strava. It’s a pain but better than nothing.