Related

Still getting zero elevation with the 20.29 update.

morey000
2 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 HaraldPoesch

    This morning I used my chest strap and had no problems with Elevation in my run.. I did no restart, recalibrate or other unusal things.... Now I have no idea when the Altimeter is working wnd when not Unamused

  • 0 2 months ago

    Today I joined the club :( This was my first run since I upgraded to 20.29 (though I did some walks) and the elevation is flat. Interestingly the walk from home to where I started to run and the walk back home after the run both have correct elevation profile. All the run was in the same place I ran hundred times before, no trees, buildings.

  • 0 1 month ago in reply to HaraldPoesch

    use of chest strap doesn't seem to have an effect on whether or not I get elevation data.  but- good suggestion

  • 0 1 month ago

    Interestingly enough- the elevation data is intermittent.  Some runs I get it, some runs I don’t.  Shrug‍♂️ 

  • 0 1 month ago

    BTW everyone in this thread: have you reported it to Garmin customer support? They're not reading the forum, so they won't even know about the problem unless we all report it! 

    support.garmin.com/.../

  • 0 1 month ago in reply to flocsy🤠

    Have you received a response? I contacted them directly at the weekend and am waiting. The same issue is effecting other 55/65 watches. I have commented on other forum pages and Garmin have been responding to some users, so they are aware and hopefully resolving the issues.

  • 0 1 month ago in reply to Hels_Bells_76

    No response so far. I reported it 8 days ago.

    But yesterday I got an "answer" to something else I reported on 15th Sep. Well it was a link to where they explain what is Training Effect. Indeed my bugreport was about Training effect, so the bot/agent correctly picked that up, though they surely have not read the other 2 sentences or have not understand why it's a bug that I got a "Tempo" 5.0 overreaching categorization for a 13 minute 1km walk. Or they just don't care...

  • 0 1 month ago in reply to flocsy🤠

    I've not read the training effect page, not if I have, not recently but I have had similar problems - I was running a base effort, or so i though (in the HR zone 2 range i had set), but the pace was maybe a bit too fast at times, and ultimately what fixed my issue was reviewing how my HR zones were set up. I was actually running a Z3 effort which i has set up as Z2 - so it was correctly telling me I did a tempo run as both the Heart rate effort and speed were over what is conserved base by Garmin for my VO2 Max score.

    I think that it considers both the Heart rate effort and Pace when providing the status so both need to be accurate. I always use HRM pro chest strap - so I know at least that is accurate.

    For the pace however, this needs accurate GPS but also links in with current elevation issues - if i run a route that doesn't finish at the start point then I could be running an overall elevation loss with a faster pace than usual, so it might be an easy effort. Then i might finish with a warm down walk up-hill to the start point, recovering from the run and a harder effort walk going up hill.  If the watch isn't actually recognising the elevation gains/losses then it will say is a tempo run as as its not considering the decent and also thinking that im really struggling as im doing a slow walk with a heart rate that is getting higher?1?

    I think all the data, insights etc are all really great - when it all works, so I'm really disappointed that Garmin are being so slow to resolve this issue with elevation.

    Hopefully my experience & thoughts around training effect help though?

  • 0 1 month ago

    Same problem here. No elevation data. 

  • 0 1 month ago

    I have this problem too. It goes on for several versions. For me, it only manifests for activity Electrical cycle. Walking and running are no problem. As someone writes here, you need to stop the activity, choose Continue later. After continuing, the height already counts.