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

I have the same problem with my Fenix 3, I have to disable the elev correction on every single activity.

Has anyone received feedback from Garmin recently? The last post about it was almost 2 weeks ago...

Same issue with fenix 3, too...
When will it be fixed...? Disappointing.

I too have had this issue for many months. What I was wondering is if anyone affected by the Elevation Corrections issue can successfully see IQ graphs in their workouts. See the last few posts on this page for details:

https://forums.garmin.com/showthread.php?362160-Row-app-problems-(outdoor)-Anyone-else-get-them&p=918045#post918045

I was wondering if the two issues were related?

I've had a mail exchange with Garmins German support staff two months ago regarding this issue. They basically said: it's not a bug - it's a feature, turned on for every GPS enabled device. I proceeded to send them a screenshot of the tooltip on the connect page (the one where it says: elevation correction is disabled for GPS devices with barometric altimeter). Support responded with: we passed this along to the relevant department. So I still have to disable elevation correction for every single activity. The watch is correctly recognized by GC, but apparently something still goes wrong behind the scenes. Really would like to see this resolved.

I've had a mail exchange with Garmins German support staff two months ago regarding this issue. They basically said: it's not a bug - it's a feature, turned on for every GPS enabled device. I proceeded to send them a screenshot of the tooltip on the connect page (the one where it says: elevation correction is disabled for GPS devices with barometric altimeter). Support responded with: we passed this along to the relevant department. So I still have to disable elevation correction for every single activity. The watch is correctly recognized by GC, but apparently something still goes wrong behind the scenes. Really would like to see this resolved.

@ckeddf - Even if you disable the height corrections, the diagram still comes from connect, not from your unit. I would be really surprised if your device is truly recognized, see higher up in this thread. You could also see this in garmin connect mobile under "settings" - "profile" and scroll down to see the last synced unit...

I've had this issue since January 2016. They seems to dropped my support case, that's the solution as you can see in this thread. Not solving it, just ignore....

@pete: I wouldn't be too surprised if the issue about fit file extensions doesn't work either. My belief is that the sw that decides which fit file parser should be used gives wrong information (inside connect server farm) and thus give the files to wrong parser (or wrong parameters to the parser) and this gives these strange errors. The more I think about it the more angry I is that Garmin doensn't fix it.

@ckeddf - Even if you disable the height corrections, the diagram still comes from connect, not from your unit. I would be really surprised if your device is truly recognized, see higher up in this thread. You could also see this in garmin connect mobile under "settings" - "profile" and scroll down to see the last synced unit...

I've had this issue since January 2016. They seems to dropped my support case, that's the solution as you can see in this thread. Not solving it, just ignore....

I agree, behind the scenes the watch is not recognized. At least disabling elevation corrections gives the correct accumulative values for ascent and descent as they were shown on the watch. Still, it doesn't bode well that the issue persists for so long.

I tried to restart the suppportcase since I not only have the height corrections failure but also that ConnectIQ extensions as peteholloway guessed half a year ago not handled correctly and I'm considering buying a stryd.

1. First respond from Garmin support was that "it is fixed and closed"
2. I said NO
3. Garmin support then say. "No it is not closed, but we don't know how to fix it" we gather information from lots of customers....
4. I got fed up and pinpointed the issue exactly and sent a VERY detailed bugreport of the issue.

- It is identifying the unit not (only) on the productid inside the fitfile and also on the unitid.

I verified this by taking a friends unitid and binary modified a failing fitfile (6 bytes modified, 4 unitid+2crc), and can after this prove that
height corrections is enabled and fit file extensions is not handled in one case, and in the other case height corrections disabled and connectiq extensions enabled.

The problem is not on the file_id (as I first guessed), but on the first device_info message. (

ogarmin$ diff nonworking/72FC2603.csv working/modserial.csv
2031c2031
< Data,3,device_info,timestamp,"856094353",s,serial_number,"####mine_not_working###",,manufacturer,"1",,garmin_product,"2050",,software_version,"8.2",,device_index,"0",,source_type,"5",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
---
> Data,3,device_info,timestamp,"856094353",s,serial_number,"##friends_working###",,manufacturer,"1",,garmin_product,"2050",,software_version,"8.2",,device_index,"0",,source_type,"5",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,



I strongly believe that they forgot an else branch in the unit identifications when they tried to identify the quatix/tactix. Some unitid's got lost in there productiondatabase and since they are poor programmers they failed.

Same problem here. The annoying side-effect is that IQ apps are not updated automatically via the Connect app. The app reports a new version is installed (gets the version number from the store probably, not from the watch), but this is wrong, the watch still has the old version (can be checked with apps that display their version on the watch, e.g. DozenRun). Only Garmin Express is able to update my apps. Very annoying.

Elevation Corrections Disabled

Anyone else with Elevation Corrections working correctly again? I did a paddle yesterday and Elevation Corrections are disabled again, for the first time in a very long time. Unfortunately Connect IQ graphs do not yet show correctly, unless I modify the device serial number in the fit file.