Fenix 6X Pro Solar bug: watch "canceling" activity (running) about 400m to 600m after starting

Hello all.

Not sure if there's a thread for this, but I could not find it: I'm a die-hard Garmin fan and user, and currently rocking my Fenix 6X Pro Solar (for about 2 years). I notice that sometimes - more often than I'd like, to be honest - the watch simply interrupts an activity (running, in my case) after I start (normally 400m to 600m into the run). I don't know if it is a GPS connection glitch (but I only start my activities once it latches on to the satellite - "go green"...) or if the watch "reads" that the activity is "too low/slow" (pace, heart rate, whatever...) and automatically cancels/suspends it... Of course, there's no troubleshoot example for this on the manual. Anyone having the same issues? Any tricky or solution to fix/minimize/avoid? Thanks.

0 philipshambrook over 1 year ago

If you have Autopause selected turn that off.

0 Data over 1 year ago

If you have Autopause off already; I have seen a similar problem, 6 Pro would return to the watchface, and from that point on, record only time, no distance, track, or external sensors. It happened mostly at the same point in one of my routes, 600 meters into a run, just after entering a park with dense tree cover, where all my GPS watches had struggled with bad GPS reception in the past. Maybe you can identify a trouble spot and avoid it?

0 tmk2 over 1 year ago in reply to Data

Problems with GPS reception should not cause such issues. Ucommanded return to watch face usually means that the watch crashed and rebooted.

0 Data over 1 year ago in reply to tmk2

tmk2 said:
Problems with GPS reception should not cause such issues. Ucommanded return to watch face usually means that the watch crashed and rebooted.

When it happened at the same spot 3 or 4 times without any indication of a reboot in the errorlogs or the debug folder, I thought it might have been a bug in the Run activity where it didn't handle the loss of GPS in the first km of a run properly. But you may be right, the watch may have restarted without logging anything. It was just very odd.