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?

" />">
" />">
  • My issue is still not solved so they probably add production batch by batch and my batch is still missing....

    I can't understand WHY in the £$€£$€ they don't trust the product id stored in the fitfiles (thats what it is for...). If they should do something regarding the unitid they should block it being used at all and state that this is a not a genuine Garmin product. (Even if mine is an exchange unit directly from Garmin due to the poor GPS performance, so definetely a genuine one)
  • My issue is still not solved so they probably add production batch by batch and my batch is still missing....


    Interesting additional fact is that if I enter my non-functional unitid in their support tool it identifies the unit type as fenix 3 from the non-functional unit-id....

    I verified that this tool that it is fully identifying the unit type on unit-id and not on series. Single unit-id holes found in series.

    The tool can be found on https://support.garmin.com/emailFormNew/sv-SE/device/xxxxxxx?identifierType=SERIAL_NUMBER
    Change xxxx to the unit-id or more easily https://support.garmin.com/sv-SE/contact/email
  • Fortunately it's the bit we really care about, right? ;)

    Ran to work this morning and again the elevation corrections are disabled, as they should be.
    Thumbs up to the posters here who have kept the pressure up on Garmin to get this fixed.


    Mostly, yes,and I'm happy! But I think the unknown device in GCM is the cause of missing LTHR and no app autoupdates via GCM. Still annoying.
  • Mostly, yes,and I'm happy! But I think the unknown device in GCM is the cause of missing LTHR and no app autoupdates via GCM. Still annoying.


    My device on my Profile page has always been OK, so it's possibly not related to the Elevation corrections and Fit Contributor fix?
  • Maybe a different messed-up database? ;)
  • Elev corrections are now disabled again for my Fenix 3 as they should be.
    I'm very happy that this issue has been solved (for me...)
  • Former Member
    0 Former Member over 8 years ago
    Finally solved, after 11 months with this stupid error.

    It wouldn't have been so bad if the manual deactivation had brought a correct elevation diagram. This problem is still there: enabling elevation correction changes the elevation diagram, disabling the "correction" doesn't change it back.
  • Finally solved

    Nope, still only for some unitids. Mine still not working.
  • After suffering from this issue for the last 11 months I'm noticing some changes/progress in GC now (using fenix 3):
    • Upon uploading a new activity to GC, the Elev Corrections are disabled there per default (as expected)
    • The Elevation Graph seems to match the barometric data from the device (as expected)
    • A manual change of Elev Corrections from 'disabled' to 'enabled' changes elevation statistics (as expected) but doesn't change the Elevation Graph (same issue as when "Elev-Corrections-Bug" was present but vice versa now). That's what I wouldn't expect but in fact I don't care - no issue for me as long as the graph matches my barometric data.
    • The device (fenix 3 in my my case) is still displayed as 'unknown' in my user profile in GC. On the other hand I don't know if I have ever seen it there with the real name - I've never checked it deliberately before the "Elev-Corrections-Bug" has occured (April 2016).

    So, I don't know if the issue is completely solved now but I personally am happy with the current situation, hoping there will be no fallback again...
  • 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. :-(