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

Elev Corrections 'Enabled' When They Should be 'Disabled'

For about a couple of months now, for all outdoor (GPS on) activities recorded on my Fenix 3, Garmin Connect has decided to apply Elev Corrections - Enabled. It never did this before (over the past 2.5 years of Fenix 2 and Fenix 3 ownership) and the little pop-up notes in GC clearly state that Elevation Corrections should disabled by default for devices with a barometric altimeter (which the Fenix 3 has). I know that it's a simple task to switch back to 'Disabled' Elev Corrections, but apart from being an annoyance to do, that only updates the summary elevation data (elev gain, elev loss, min elev and max elev), the elevation graph remains at the 'Corrected' elevations. I can see this as I use a foot bridge over a major road and the corrected elevation plot reflects ground level and not the up and down of the foot bridge - whereas the barometric elevation data the watch records on the .fit file tracks the elevation profile of the foot bridge perfectly (the pictures below help illustrate the point).

As an extra note, Garmin Connect is correctly recognising my Fenix 3 and it's software version. I reported this to the Fenix 3 beta software team email some time ago, but I know from past issues similar to this (such as Garmin Connect seeing the Fenix 3 as 'Rubber Ducky' etc.) that they have stated on the forum that they can only do so much to 'prod' the Garmin Connect team to sort these issues out.

Is anyone else still having this problem and, if so, has anyone had any joy going through the Garmin Customer Service process to get a resolution?

" />">
" />">
  • Same problem here....you have to enable it for your profile to be shown on the Profile-Site. In Germany Profil/Einstellungen/Benutzerprofil...scroll down to 'Connect-Statistiken'.
  • Ah... Thanks a lot Oliver!
    After enabling it in the Settings I see the device on my Profile screen now and it's displayed as "unknown"
  • any solved?

    I have, the same problem... Elevation correction is default enabled and elevation's graph haven't original data from watches after elev. corr. disabled.
    I've fenix3.
  • Garmin wrote that they haven't problem on Connect but I have problem with my fenix3. Should I have to factory reset, I did but problem is still here.

    I'm waiting for next solution from them.
  • I did finally get a message back from Garmin acknowledging this issue with the Garmin Connect website (not our watches) and saying they are working in a fix, but they don't know yet when that fix will be released.
  • When did you got this message? I got friday and they wrote that their web site is right.
  • That was just over a week ago, but the way the reply was worded it did not sound like the fix would be coming soon (something like 'we have no timeframe for this yet'). It took me nearly 2 months to get that response, so I'm not holding my breath; Elev Corrections are still automatically on for a run earlier today.
  • I'm still fighting against the Garmin Support Team.
    Finally, on September 20th (after more than three months silence and a friendly reminder) I've got an email from them.
    Their wording implied (not stating it explicitly however) that the issue is known and should have been fixed with "one of the latest updates for F3" (citation).
    They have suggested to use the WebUpdater (not the Garmin Express) to re-install the F3 SW (even if I have the latest one - WebUpdater offers an option to overwrite it).
    Believing that this is a GC issue (rather than a device issue) I was quite sceptic but I did it - it didn't fix the problem however.
    So I reported it and provided them one more example with even more explanations, screenshots, etc.
    What I've got from them (on September 29th) was: "we have analyzed your data in Garmin Connect and we don't see any problems there" - I was totally speechless...
    So, on October 4th I've emailed them again with yet another example - no answer so far...