Historical Elevation problem

Answered

Follow

Gerald Ruis

• March 01, 2021 08:18

Hello everybody,

After the new update I have the problem that the 'Historical Elevation' is not displayed correctly. I have attached the FIT file, you can see it in the photo).

www.alpencross.biz/GPS-Daten/Ride.fit

 

1

• 

  Michael Heinz

  • March 01, 2021 16:17

  So, this is already listed as a "Known Bug" - you can find that post in the forum.

  That said, I've experienced this, too, and on all the rides I've done! Problem seems to be simply a display bug, not a problem with the data - when the rides upload to Strava they look great.

  0

  Comment actions Permalink
• 

  Ali

  • March 02, 2021 07:55

  Hi All - yes, this happen if you leave the ride screen, go to the home screen and then get back to the ride on the historical view. This will be fixed in the next update.

  0

  Comment actions Permalink
• 

  Gerald Ruis

  • March 02, 2021 08:00

  All right, thank you very much

  0

  Comment actions Permalink
• 

  Ivo Smolis

  • March 26, 2021 08:18
  • Edited

  Hello. After newest update (25th March) historical elevation still sometimes shows this straight line

   

  

  0

  Comment actions Permalink
• 

  Ali

  • March 26, 2021 08:23

  Hi Ivo, that's odd. We received a confirmation from the test group that it was working well. The previous times it happened when doing these steps on the ride

  1. In-ride jump to the home screen (long pressing bottom right hand button)

  2. Get back to the ride screen by tapping on the profile

  Could you confirm the steps that lead to this on your unit?

  0

  Comment actions Permalink
• 

  Ivo Smolis

  • March 26, 2021 08:30

  Maybe I was too quick to post this as now I can't "reproduce" the result. It appeared after going to the main menu and back into the ride (I'm messing with my settings now) but after I tootk this photo I exited to the menu (long press bottom right button) and re-entered the ride which in fact solved the issue (i.e. the line disappeared and graph corrected itself).

  And now no matter what I do it remains correct.

   

  So it's not a repeating bug - maybe it was a single case or now the requirements for it to occur are very "specific"

  0

  Comment actions Permalink

Please sign in to leave a comment.