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

FR955 Bug Report: GPS stops when "Watch face" hotkey is used

I've had a Fenix 3 and FR935, and regularly made use of a hotkey to go back to the watch face during an activity. For instance, I'm biking and want to look at the compass: I click the watch face hotkey, then scroll to the right widget/glance, then click "start" again to go back to the activity.

I noticed today on my 955 that, even though the timer keeps running, GPS stops updating when I'm viewing the watch face. This is NOT true when other non-activity screens are up, for instance if I use a hotkey to pull up the stopwatch and use that during an activity. I can look at the stopwatch screen the entire activity, and distance and time will accrue normally. 

This could be related to another bug I've noticed: if I go back to the watch face, then return to i.e. a running activity, CIQ fields in that running activity crash. Specifically, I use the "Single Field" field for both running and cycling. If I go back to the watch face during an activity, I just see "CIQ!" on this screen once I go back to the activity. I can recover it by editing the screen and re-selecting "Single Field," without ever stopping the activity. Again, this doesn't happen if I simply bring up a stopwatch/timer - only if I go all the way back to the watch face.

  • Confirm the same here. I have notice comment through a number of threads on this and  hopefully the way you have detailed it and compared to prior devises will result in it being addressed!

  • I confirm the same bug also. And definitely it is not related to the "CIQ fields in that running activity crash", which is here only since fw 12.20.

    "GPS off when return to Watch face during activity" issue has been present at FR945 LTE which I owned previously and stayed there until now. At FR955, the issue has been there since launch, as this watch had been very likely hugely inspired by FR945 LTE with most of its behavior and (unluckily) bugs.

    Until now, no one from Garmin payed attention. , could you please step in?

  • i can confirm 's experience. this hotkey worked fine on my 935 and my friend who had a 945 confirmed that this worked too. but with my 945LTE and 955, a hotkey stops the GPS logging. i spent a lot of time going back and forth with Garmin last year with the 945LTE but never got a  satisfying answer. one response was engineering said that their 935 in house did the same thing and asking for evidence from others that it used to work properly. i supplied that evidence (i crowd sourced here on the FR and Fenix forums) and then Garmin went dark and never followed up. :( 

  • Well that’s hyper obnoxious. 

  • All-

    Thank you for your participation in this forum thread.  So that I may assist you further, please reply with the following:

    1. May we, if necessary, have permission to email you?
    2. May we, if necessary, have permission to view/access your Garmin Connect account?
    3. In what country do you live?
  • Hi Kevin

    1. Yes

    2. Yes

    3. USA

    Regards

    Stephen

  • 1. yes
    2. yes
    3. USA

    as i noted above, i spent extensive time discussing this with Garmin support over my year of ownership of my 945LTE (supplying videos, my activities, and even getting others on the forums to comment about their own experiences). i hope they see this "change" is a big detriment to their user base.  the GPS should not stop logging when one is in activity and using the hotkey to check a widget or watch face.

  • Yes/yes/USA. I can send a link for the exact activity I tested on but I’m not sure how permissions work for insider access - it’s not public and I’d rather not set it so if I can help it. 

  • Apple watch is stepping up quickly in the space. I just hope Garmin will not end up like another Nokia.

    I agree the steps required to supply videos and multiple of conversations can be painful. 

    A good engineer should be able to fix the bugs before released or identify the bugs when a problem statement is highlighted.