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.

  • Hi, I’d like to also be contacted about this issue. You have my permission to email me and review my connect data. 

    I’m located in the US. 

    Thanks,

    Scott

  • I’m also running the Chicago marathon this weekend so this issue is time sensitive for me. Thanks. 

  • Good luck with the marathon! 
    I certainly wouldn’t load any new firmware before then incase it has some other negative effects !

  • I am also experiencing this bug. No data is logged into the data file for the entire duration that the watch face or Notifications glance are being viewed. 

    1. You have permission to email me.

    2. You have permission to view/access my Garmin Connect account.

    3. I live in the U.S.

    Today I had a 6-mile run that lasted about 56 minutes. My watch recorded a data point every second, for 1.2 MB of GPX data. But there is a 00:02:08 gap in the data when I was using the watch face and glance. Here is an abbreviated data file with only the first data point, last datapoint, and two adjacent data points surrounding the issue.

    <?xml version="1.0" encoding="UTF-8"?>
    <gpx creator="Garmin Connect" version="1.1"
    xsi:schemaLocation="www.topografix.com/.../1 ">www.topografix.com/.../11.xsd"
    xmlns:ns3="">www.garmin.com/.../v1"
    xmlns="">www.topografix.com/.../1"
    xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:ns2="">www.garmin.com/.../v3">
    <metadata>
    <link href="connect.garmin.com">
    <text>Garmin Connect</text>
    </link>
    <time>2022-10-05T16:38:19.000Z</time>
    </metadata>
    <trk>
    <name>Marshall Running</name>
    <type>running</type>
    <trkseg>
    <trkpt lat="40.66063684411346912384033203125" lon="-80.11801779270172119140625">
    <ele>336.600006103515625</ele>
    <time>2022-10-05T16:38:19.000Z</time>
    <extensions>
    <ns3:TrackPointExtension>
    <ns3:hr>68</ns3:hr>
    <ns3:cad>53</ns3:cad>
    </ns3:TrackPointExtension>
    </extensions>
    </trkpt>

    ... [ valid data elided ]

    <trkpt lat="40.66366489045321941375732421875" lon="-80.0972683914005756378173828125">
    <ele>320.399993896484375</ele>
    <time>2022-10-05T16:54:09.000Z</time>
    <extensions>
    <ns3:TrackPointExtension>
    <ns3:hr>78</ns3:hr>
    <ns3:cad>0</ns3:cad>
    </ns3:TrackPointExtension>
    </extensions>
    </trkpt>
    <trkpt lat="40.66670483909547328948974609375" lon="-80.0989105738699436187744140625">
    <ele>319</ele>
    <time>2022-10-05T16:56:17.000Z</time>
    <extensions>
    <ns3:TrackPointExtension>
    <ns3:cad>0</ns3:cad>
    </ns3:TrackPointExtension>
    </extensions>
    </trkpt>

    ... [ valid data elided ]

    <trkpt lat="40.66069618798792362213134765625" lon="-80.1184913702309131622314453125">
    <ele>340.399993896484375</ele>
    <time>2022-10-05T17:35:51.000Z</time>
    <extensions>
    <ns3:TrackPointExtension>
    <ns3:hr>162</ns3:hr>
    <ns3:cad>89</ns3:cad>
    </ns3:TrackPointExtension>
    </extensions>
    </trkpt>
    </trkseg>
    </trk>
    </gpx>

  • There were also corruptions in the HR and cadence data for several seconds before and after the dropout, highlighted in pink. I use an external HRM.

  • I have the same problem w/ my just purchased (on Oct 22, 2022) 4 day old Forerunner 955 Solar.  I compared the 955 Hot Key behavior with my Fenix 6s Sapphire Pro and the Fenix 6S does NOT have this Hot Key to Watch Face problem.  

    Note - when using the Watch Face Hot Key and returning to my run/walk/hike activity  my CIQ  "Race Screen" crashes on the 955 Solar but NOT on the F 6S Pro with the same "Race Screen"

  • All,

    Please see our recently released beta software for a fix addressing this report. If you prefer to not install this beta software, we hope to be rolling out a public software update soon, though I do not have a timeline for this release. If you are still seeing this issue after installing the beta software, please contribute your observations in the appropriate beta bug reports section of the beta forums for your specific device.

    Enrolling in Garmin Beta Software Program

  • All,

    For those of you who are enrolled in the beta software program, did installing 13.15 resolve this disruption for you?

  • the ßeta software has fixed the problem for me.  

    • The activity continues to record when I HOT KEY to the watch face & look at the compass, take a O2 reading etc and pressing the START button returns to the activity albeit to the 1st activity screen not the screen from which it was HOT KEYed away.
    • the CIQ screen no longer crashes.

    Now if only the LAP button would return to the watch face like the Fenix 6 pro, I would not need the hot key to do that Slight smile

    So, it works for me but would be nice it it returned to the activity screen that it was HOT KEYed form