Related

Still getting zero elevation with the 20.29 update.

morey000
3 months ago

Happened with some prior betas, but then it went away and starting providing proper elevation data.

But- now, I’ve done multiple runs and other activities with 20.29, restarted and such- and the elevation data is completely flat.  (Uh, when it shouldn’t be)

  • 0 2 months ago in reply to flocsy🤠

    Thank you to everyone for your participation so far! Although it may seem odd, it does look like the current workarounds of either using an elevation as a data field and/or stopping, resuming the activity later, going back to your watchface, and then re-starting the same activity works. I know this is not ideal, but it seems to keep elevation from flatlining so far. You can also change the elevation source in the meantime as well: How do I Change the Elevation Source in Garmin Connect? (previously known as Elevation Correction).

    Thank you for your patience as we investigate! 

  • 0 2 months ago in reply to Garmin-Sierra
    Garmin-Sierra said:
    an elevation as a data field

    Would that mean ANY of the data fields that are in the Elevation group? Elevation OR Avg. Ascent, OR...?

  • 0 2 months ago in reply to flocsy🤠

    I believe that any data fields in the Elevation group will work, as long as it is visible during the activity (and not on a page that you don't actually view). Some users stated that assigning it as a data field fixed it, but others have needed to stop and resume the activity later. 

  • 0 2 months ago in reply to Garmin-Sierra

    Ok, to me it sounds like Garmin has no idea what causes the bug, neither has a workaround, because the so called workaround is not clear. In the previous comment the list of workarounds had "and/or" between them, now it sounds more like "and, but"... 

    Let me summarize: Garmin acknowledges the bug, has no idea yet how to fix. There's no known workaround, but because the bug doesn't happen all the time, some users who tried to find workarounds think they have found one, but actually they just had an activity that would anyway have elevation data. Others tried to use the workarounds and we're not so lucky.

  • 0 2 months ago

    I encountered this for the first time today on my 965 with firmware 20.32.

  • 0 1 month ago in reply to johnpane

    I had a zero elevation run today. Even for flat the Netherlands that's quite impassible.

    I know you are quite busy with the long, long list of bugs, but could you give an update?

  • 0 1 month ago

    Yesterday’s run had flat elevation data again, but they’re not all like that.  One other thing I noticed- perhaps this will be helpful to Garmin.   
    The temperature data was also completely flat for the run.  

  • 0 1 month ago

    Happened recently to me as well. Had just installed datafield RaceScreen when this problem started.  Uninstalled it and elevation during my Run activity was back. 

  • 0 1 month ago

    I wish I had seen this thread earlier. I'd had a Forerunner 955 Solar for a couple of years, and in the last couple of months started randomly having runs with zero elevation change recorded. It was inconsistent, some runs would be fine and others would be missing elevation without me changing any settings or my behavior.

    After going back and forth with Garmin support and trying several things including cleaning the barometer altimeter, they decided to replace my watch. I opted to pay to upgrade to the new 965 with a full warranty, but 3 runs into the new watch I'm again having the zero elevation issue on some runs, with others being fine on the same route.

    So, I guess this is a firmware issue after all and I didn't need to replace my watch. Disappointed 

  • 0 1 month ago

    This seems to be getting more and more frequent for me. My last three runs have all had this issue.