Was that just in the activity summary; the one you see when you stop and save the activity? I've also seen some ridiculous ascent totals in this activity summary, but later viewing details in activity history and once uploaded to Garmin Connect all is fine. The last example was a MTB ride yesterday, the summary had something mad like 32,000m but in the history and on GC it was correct, in line with total ascents of my Fenix 3 and a friend with an Edge 520 (all around 530 metres total ascent). I'm reporting these findings to the beta team, but if you've seen the same it wouldn't hurt someone else sending in their observations of the bug (email details of bugs to [email][email protected][/email] ).
Was that just in the activity summary; the one you see when you stop and save the activity? I've also seen some ridiculous ascent totals in this activity summary, but later viewing details in activity history and once uploaded to Garmin Connect all is fine. The last example was a MTB ride yesterday, the summary had something mad like 32,000m but in the history and on GC it was correct, in line with total ascents of my Fenix 3 and a friend with an Edge 520 (all around 530 metres total ascent). I'm reporting these findings to the beta team, but if you've seen the same it wouldn't hurt someone else sending in their observations of the bug (email details of bugs to [email][email protected][/email] ).
I have this too and the value "32768 m" is display in the lower right position after saving an MTB ride, see attached image. I think the number "32768" is actually a memory data. In a byte-wide memory there are 32768 unique addresses numbered from 0-32767. I hope they can fix this bug in and update.
Was that just in the activity summary; the one you see when you stop and save the activity? I've also seen some ridiculous ascent totals in this activity summary, but later viewing details in activity history and once uploaded to Garmin Connect all is fine. The last example was a MTB ride yesterday, the summary had something mad like 32,000m but in the history and on GC it was correct, in line with total ascents of my Fenix 3 and a friend with an Edge 520 (all around 530 metres total ascent). I'm reporting these findings to the beta team, but if you've seen the same it wouldn't hurt someone else sending in their observations of the bug (email details of bugs to [email][email protected][/email] ).
Yes, exactly what you have seen. Now I'm home I've looked again at the activity and it's 2500ft odd.
