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

Fenix 3 not recognized - Listed as "Unknown"

This comes and goes with different versions of the software version on the Fenix 3 but it's clear that the problem lies with GC.
We have to edit each activity manually to turn off Elevation "Correction" to show correct data.
VERY ANNOYING since this is supposed to be a trail watch.
It seems like a trivial thing to fix, when the problem first showed up it was fixed quickly but only for certain software versions for this watch.

Example:
https://connect.garmin.com/modern/activity/1069289717

Unit ID: 3906483619
Software: 6.84
  • I have the same problem since FW 7.00, and now with 7.20 the problem still persists. :mad:
  • For me it's working perfectly fine now.
    I've seen some people saying it's recognized but Elevation Corrections are still "Enabled".

    Here's mine on 7.13 beta:
    https://connect.garmin.com/modern/activity/1203426094

    And here it is on 7.20:
    https://connect.garmin.com/modern/activity/1219809750
  • I also have the problem that Elevation Correction is always enabled, though the watch is recognised as a Fenix 3 running 7.20.
  • I have the same issue since months:

    - Beginning of this year (February? March? - don't remember exactly) my F3 was appearing in GC as "Unknown", resulting in Elevation Corrections set to "enabled"
    - Since approx. March/April my F3 is being recognized correctly by GC (as "fenix 3" and the respective logotype)
    - Until at least 8th of April the Elevation Corrections was setting to "disabled", as expected
    - Somewhere between 8th of April and 15th of April the Elevation Corrections started to set to "enabled" per default for all uploaded activities, what is not correct. On those both dates I ran exactly the same route, which I run often, and can compare the elevation plots one-by-one - all of them before 8th of April are almost identical and are plausible, all of them after 15th of April are also almost identical but deviate from the previous ones significantly and are definitely wrong.
    - Changing Elevation Corrections manually from "enabled" to "disabled" corrects statistics and reports but not the elevation plot.
    - Interesting is that between that reference dates (8th and 15th of April) nothing has changed on my F3 itself! It was at FW6.90 and I didn't install, update or change anything at all, not even profile settings - hence I suspect the problem rather with the GC
    - Later FW updates to 7.00 (on 8th of May) and 7.20 (on 23rd of June) didn't change the behavior - Elevation Corrections is still setting to "enabled" resulting in wrong elevation figures.
    - I did a soft reset and later also a hard reset on my F3 - it didn't fix the issue
    - I reinstalled GE, removed and re-added F3 from/to GE/GC/GCM - it didn't fix the issue
    - I raised a request to the Garmin Support. Few weeks later they replied that "my question" is forwarded to the development team but they didn't comment on when (if at all) it will be fixed.

    Further, the GC believes (Devices -> Device Settings) that the last sync for my F3 was on 8th of May, which is not true of course - I sync it few times a week, every week.
    That could be just a coincident but 8th of May is exactly the date when I've updated my F3 from 6.90 to 7.00
    I don't know if this has something to do with the elevation problem and didn't notice any functionality drawback related to this wrong "last sync" date but it's worth to mention here, I think.

    I hope that if all who are affected by this elevation problem will report it in the forum, it might slightly increase the probability that someone at Garmin pays attention to it.

    @GARMIN:
    PLEASE LOOK AT IT AND REMEDY OR AT LEAST LET USERS KNOW WHAT THE SCORE IS.
  • I'm very disappointed with Garmin.

    I love my F3. But this issue is ruining the altimeter in the watch.

    Weeks and weeks are passing and still no solution to this...

    :mad::mad::mad:
  • I just want to remind everybody that it's very important that you write to the fenix beta team and explain the issue you're having.

    You MUST include you "Unit ID" ... NOT Serial Number.
    You get this here: Settings -> System -> About

    It seems they can have this problem corrected on a unit by unit basis in Garmin Connect.
  • Thank you Robert, I emailed them. :D
  • Former Member
    0 Former Member over 9 years ago
    Did you get a response? I emailed them last week too, and they told me that they are aware of this issue and would contact me if they needed further information. Nothing has happened since. :(
  • Former Member
    0 Former Member over 9 years ago
    Anything...? :(