• State Not Answered
  • Replies 30 replies
  • Subscribers 0 subscribers
  • Views 6380 views
  • Users 0 members are here
Options
Related

Known issues/bugs (admin please make sticky) v2.0

carl.andersson
Not sure why there isn't a thread already devoted to this, but considering people ask the same questions over and over I thought perhaps we should put together a list of known/acknowledged bugs and issues for people to check.
I don't want this to become a complaint thread - there's plenty of those already, and I just want us to focus on issues that have been raised and someone at Garmin (the Beta team, the support team etc.) have confirmed are issues they are working on.
This is by no means an exhaustive list - but I want to focus on the issues that a newbie may come across after buying the watch (or that may give them pause for thought before even buying the watch) and to help give Garmin a real "hit-list" of the issues causing their customers pain.

If you have an issue/bug that you want me to add to the list then post below (or DM me if you'd prefer) with the following
  • Issue/Bug encountered
  • Description of what it is/what it affects
  • How to recreate the bug/issue
  • Response from Garmin (if any)
  • Ways to mitigate/fix/avoid the issue (if possible)
  • Time-frame indicated from Garmin for it to be fixed (if any)


I want to pull this into two separate sections - software/firmware issues and sensors/communication issues. I'm happy to consider another way to structure it if people think it will make more sense.

Edit: I had to pull this into a new thread as I wasn't aware of the 10k character limit on a post so my original bug report became too large to fit in the first post of the thread!
  • 0
    Another issue:

    The F5 does not override autosplit when creating workouts (e.g. make w 6x 1.6km interval workout in GC , sync, then do the workout on a F5 with autosplit set to 1km).

    Here's how my FR610 handles laps in this scenario (correct):



    Here's how the F5 handles it (wrong):

  • 0
    Another issue:

    The F5 does not override autosplit when creating workouts (e.g. make w 6x 1.6km interval workout in GC , sync, then do the workout on a F5 with autosplit set to 1km).



    This is per design and not a bug. As with everything else it's very poorly documented.
    Disable autolap to get the old behaviour. The easiest way to do this is to have dedicated app for interval workouts. I have a copy of the running app called "Interval running" where I disable autolap and have some custom screens setup that's handy when doing inteval workouts, like a whole screen with numbers for the last lap.
  • 0
    Another issue:

    The F5 does not override autosplit when creating workouts (e.g. make w 6x 1.6km interval workout in GC , sync, then do the workout on a F5 with autosplit set to 1km).


    stewa285 beat me to it but yeah essentially they're correct. But even if it's a bug rather than working by design the workaround of creating a new run activity with auto-laps turned off still works.
    I will add your issue to the list though so people can see the work-around solution.
  • 0
    Issue/Bug encountered: After a swim session, altitude reported is totally wrong +/-400m regarding actual altitude. Same problem from firmware 2.4 to 4.1.
    Description of what it is/what it affects: Altitude reported until a new altitude calibration
    How to recreate the bug/issue: make a swim indoor session (without GPS)
    Response from Garmin (if any): ?
    Ways to mitigate/fix/avoid the issue (if possible): No way to avoid, need to recalibrate with GPS altitude after a swim session ...
    Time-frame indicated from Garmin for it to be fixed (if any): ?

    Regards
    PS: I'have seen a F5X topic on that:
    https://forums.garmin.com/showthread.php?377770-488m-after-swimming-calibrating-the-alti-without-shortcuts


    I'm assuming the ? for the response from Garmin is because you haven't logged this as a bug? I can see from the other forum that some other people have though so I'll use that.

    Stupid question time though - what does this actually affect? Like obviously the altitude is way out after a swim and needs to be recalibrated, but what is the impact of that? Does it mean the floors climbed information is wrong? Does it affect the barometer information/storm warning accuracy?
    Or is it just that the altitude information on the watch shows up incorrectly till you go to use a GPS powered activity?
    Just trying to gauge the "real-world" impact of this bug.
  • 0
    Indeed, i didn't log the bug.

    The impact is wrong displayed altitude on watchface, altimeter and frequently storm alerts after swim sessions. I had to desactivate the Storm alert!
    And if you are not waiting enough time before a run or cycling sessions, there is an offset in altitude for all session...
    Regards
  • Former Member
    0 Former Member
    When using navigation the distance remaining field provided by the navigation guide and the distance remaining field that you can add on a data screen are NOT the same. It's a bug and as a hiker who uses the navigation feature, quite annoying to see. I have screenshots if needed too.
  • 0
    Can anyone post Garmin's official response to the GPS issue?

    Because I have yet to hear anything resembling an acknowledgement to the issue from their side.
  • 0
    This is per design and not a bug. As with everything else it's very poorly documented.
    Disable autolap to get the old behaviour. The easiest way to do this is to have dedicated app for interval workouts. I have a copy of the running app called "Interval running" where I disable autolap and have some custom screens setup that's handy when doing inteval workouts, like a whole screen with numbers for the last lap.


    No offence, but is this your opinion or is this actually documented?

    As said, my old FR610 automatically disables autosplit for workouts (without affecting the "on" setting for general runs).
    I have trouble believing Garmin would be inconsistent, depending on the watch.
  • 0
    it's a change of behaviour for sure, but it's consistent on later Garmin models so I agree, it's not a bug. It's easy to work around to.

    CW
  • 0
    When using navigation the distance remaining field provided by the navigation guide and the distance remaining field that you can add on a data screen are NOT the same. It's a bug and as a hiker who uses the navigation feature, quite annoying to see. I have screenshots if needed too.


    Yes, can you please attach with a screenshot? thanks