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?

" />">

" />">

0 budul over 8 years ago

Since few months, exactly the same issue.
F3 and on all new activities Elevation Corrections on Enabled.
When manually set back to Disabled, still the wrong elevation data (chart) displayed.
Contacted Garmin Support -> no reaction at all (4 days so far), really sad. :-(

0 Mathias.Bjorklund over 8 years ago

Warranty only way to fix it.

I had My unit exchanged on warranty last week due to this issue (even if there is no issue on the actual watch, only on the web)

Luckily the new one had a good unitid.

It is really pathetic that connect team can't fix this. They should be ashamed.

0 eberends over 8 years ago

I also experience this issue, which for me started on April 26th. Before that day, all was fine, afterwards all activities have elevation correction enabled. Only change for me, was that as per April 26th I travelled abroad to another time zone. After travelling back home, the issues persisted (sadly).

0 budul over 8 years ago

I had My unit exchanged on warranty last week due to this issue (even if there is no issue on the actual watch, only on the web)

Luckily the new one had a good unitid.

It is really pathetic that connect team can't fix this. They should be ashamed.

Man, this sounds crazy.
Change of working unit, just because of some stupid bug in WEB app?!
Completely ridiculous.
And together with ZERO reaction from Garmin Support... i can't simply get it.

0 budul over 8 years ago

I also experience this issue, which for me started on April 26th. Before that day, all was fine, afterwards all activities have elevation correction enabled. Only change for me, was that as per April 26th I travelled abroad to another time zone. After travelling back home, the issues persisted (sadly).

In my case, till 10th of April Elevation plots data correctly (using barometer).
Since 12th of April Elevation Chart uses "corrected" (BTW, very incorrect) data from some "shot" data source (even if correct data still in FIT file).
Garmin Support still quiet, makes me quite angry.

0 eberends over 8 years ago

I also experience this issue, which for me started on April 26th. Before that day, all was fine, afterwards all activities have elevation correction enabled. Only change for me, was that as per April 26th I travelled abroad to another time zone. After travelling back home, the issues persisted (sadly).

I've been in touch with Garmin Support and in my case they respond after a couple days and asking for additional information, .fit files, etc. I know, still no solution, but I have the idea that they are investigating the issue. For know, fingers crossed that Garmin finds the root cause and solves it.

UPDATE May 26th: Garmin Tech has been able to reproduce the issue with the files that I provided. They've opened a case and are investigating the root cause.

0 eberends over 8 years ago

Solution is coming soon

I've been in touch with Garmin Support and in my case they respond after a couple days and asking for additional information, .fit files, etc. I know, still no solution, but I have the idea that they are investigating the issue. For know, fingers crossed that Garmin finds the root cause and solves it.

UPDATE May 26th: Garmin Tech has been able to reproduce the issue with the files that I provided. They've opened a case and are investigating the root cause.

I just received word from Garmin support that they will fix the issue in the next update of Garmin Connect. I'm not sure when this update is to be released, but at least a solution seems to be coming any time soon.

0 budul over 8 years ago

I just received word from Garmin support that they will fix the issue in the next update of Garmin Connect. I'm not sure when this update is to be released, but at least a solution seems to be coming any time soon.

Received exactly the same answer from Garmin Support.
Today GC 3.19.1 appeared.
BUT for me NO effect -> still Elev Corrections on ENABLED. :(

0 karlw2000 over 7 years ago

3 1/2 months later. Has anything changed? My fenix 5s just started getting this elev correction enabled!!!