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
over 1 year 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 in reply to Garmin-Sierra

    1. No, I didn't find the pattern

    2. Yes, in my case it's perfectly ok outside of activity

    3. Yes

    4. Yes

  • 0 11 months ago in reply to Garmin-Sierra

    Only seems to happen during running activities.

    Floor count on days where no elevation recorded way down

    Yes

    Yes

    I first reported the issue back in early Aug, 13 running activities since Aug 4th have had zero elevation or temp rise. 

  • 0 11 months ago

    Luckily I did not have this problem so far but it seems to happen concentrated to some users.

    Those effects remind me at the times when programming C++ on microcontroller systems and having missed to declare a global variable as volatile.

  • 0 11 months ago in reply to Garmin-Sierra

    1.Most running activities.

    2. Yes, normal.

    3. Yes.

    4. Yes.

  • 0 11 months ago in reply to Garmin-Sierra

    1. Yes - and it impacting on my Hills score and K2 climb challenge, Walks seem ok, when I run I use Garmin Coach suggestion.

    2. Yes - but as above this figure should be far greater and using the elevation correction doesn't fix the number of floors climbed or your hill fitness score. I am also concerned that my Garmin suggestions might be inaccurate, as it will not understand the reason for the elevated heart rate and lower pace is due to an uphill climb (or the opposite for decent)

    3. Yes - I have been using elevation correction but you can reverse this and see the flatlines

    4. Yes

    Since my post 12 days ago I have updated from 20.26 to 20.29 and have also plugged watch into laptop and updated Garmin Express maps, shut down and restarted a few times.

  • 0 11 months ago in reply to Garmin-Sierra

    I first noticed it on software version 20.26 and it's continuing on 20.29.

    1. Not every activity and not for the whole of any activity so far.  I've seen it when using Run and Trail Run activity types and it's for the first few minutes (anywhere from 4 to 19 minutes).

    2. Floors climbed seems normal, I think.

    3. Yes.

    4. Yes.

  • 0 11 months ago in reply to Garmin-Sierra

    1. fw 20.29 here, two run activity in a row with flatline elevation
    2. yes, all day activities show elevation floors correct, atm pressure normally variable
    3. yes
    4. yes

  • 0 11 months ago in reply to OperationOne

    note: during my last run activity, i added an altitude field, and i was able to see it follows reasonably my altitude changes

  • 0 11 months ago in reply to OperationOne

    tested a workaround i read here yesterday: start a run activity, stop & save for later, restart the same activity, et voila altitude graph recorded as usual.

  • 0 11 months ago in reply to tomaskafka

    I do this, but I also sync my activities to a lot of other platforms and fixing this on all of them would be a big hassle. Map elevation data is also not the greatest around here.