0ft Elevation Gain

I have the same issue with cycling, I don't know what is the reason that sometimes it works, or sometimes it doesn't.

I have the same problem for a long time. I don't like it anymore. In a week, I had to hard reset the watch twice during activity. This results in Watts being wasted and I have to delete Stryd activity.

I don't enjoy it. Such an expensive watch and it has such a flaw. I will buy COROS.

Same issue. I think it is getting more and more frequent.

What does not work:

- Disable auto calibration for altimeter.

- Open an activity (but dont start) then cancel and start it again

What I think works:

- Start an activity then stop and discard it and start it again

Me too. I found this problem in some other post and I understood that it's a firmware problem that happend not every time. I read in some posts that I must disable auto calibration for altimeter, but change only that I have not zero meter of difference in my track: profile is always false and without sense. I try to change mode to find altitude, only with barometer or only with GPS: with first I had 0 meter of difference and with second I have quote profile but not right for nothing, without any sense. So what wait Garmin to solve it? I'm lucky only that in thos period I'm not interesting about trail training, only street, but move it!

And I hope that this next firmware upgrade Garmin solve it. I tried too start an activity, stop, delete and restart. There is not zero elevation, is it true, but profile is not too much true. I watch it against another from a 955 not solar in the same track and is different and false. I don't understand if it's a problem only with solar version or what. What experiences you have about it?

Effepigi said:

I don't understand if it's a problem only with solar version or what.

I’ve seen it happen several times on my 955 non-solar edition. According to the forums, it’s also happening on several other current watches (255, 265, 965, etc). 

It’s clearly a software problem and it doesn’t happen consistently.

For example, I have seen an activity with (incorrect) 0 elevation change sandwiched between two activities with non-zero elevation change (e.g. when I record separate activities for a warmup, workout, and cooldown).

I’ve also seen:

- floors being counted properly immediately before an activity with incorrect 0 elevation change.

- elevation being (incorrectly) 0 for the first half of the activity, but non-zero for the 2nd half (or vice versa, can’t remember)

- elevation appearing to be ok based on the data fields/pages during the activity, but being recorded as 0 to the FIT file (so the activity chart shows a flat line even though the elevation chart during the activity was not flat)

- an activity where elevation was incorrectly recorded as 0 but lap GAP differs from regular lap pace in a way that seems to match the elevation changes during the activity

Today I did firmware upgrade with v21.19 and maybe now look much more better. I did only a little run of 5Km, but elevation today have a sense. We will see in the next days what happend...