Fenix stop record GPS data during activity

In my last 2 running activities my Fenix 5X stopped recording GPS data for about 2km, but all other data was recorded correctly (pace, distance, speed etc.). In fact the final distance and the average pace are correct.
By analyzing the fit file at https://www.fitfileviewer.com/ and looking at the recorded data, I can see that all data is recorded correctly and only the latitude and longitude data is missing for about 2km.

It had only happened once in the past, about 1 month ago. But now it seems like a recurring problem as it happened both yesterday and today.

The Fenix is practically new because it was replaced under warranty with a new one at the beginning of September.

The activities are as follows:
https://www.strava.com/activities/4322205288
https://www.strava.com/activities/4317110142


or on garmin
https://connect.garmin.com/modern/activity/5806089254
https://connect.garmin.com/modern/activity/5801107361

  • With apologies to Garmin and the forum members; I had included *all* GPS dropouts, including legitimate ones due to no GPS available (tunnels). So it happens much less; only once every 10 runs or so. During walking more often. I'm OK with the occasional dropout during running and walking isn't real important to me, so I'm not going to investigate further.

    I hope that these GPS dropouts will also be minor and infrequent for you all too - otherwise, it's probably best to try all the usual like resetting and contacting Garmin support.

  • I have run twice after the master reset.  So far no issues

  • Two days ago I had the same issue (first time in 1,5 years). As described by some of you guys the data for pace and distance are still present in the .fit files (both via USB and saved from GC) and only the position is missing. Within the data gap there is a Garmin Segment which I downloaded recently to the watch. This segment was correctly detected and shown during the run, so also here GPS connection was not lost. The position data started again at a point where I manually stopped the activity for a short break.

    The next two activities were different and tracked without issues. So I tried to reproduce the faulty acitivity as much as possible. I started at the same point, ran without interruption and without touching the watch (just a data screen without any connect iq datafields). I did not change any settings and I used the same sensors (Garmin footpod and Tempe, no HRM). My only hypothesis was that it has something to do with the segment, because the start of the gap was just 100m before the start of the segment and I recently put it on the watch.

    Again the segment was detected correctily and after uploading the activity via WiFi, everything was correct. So I failed in reproducing the issue and I cannot contribute to find a solution.

  • I experienced the same, first time a year ago. The GPS position is either known or inferred correctly from an inertial navigation mechanism; my position on the map is updated correctly, but the track is not drawn, and the GPS data isn't present in the FIT file. It wasn't/isn't a GPS coverage issue: another Fenix worn on the other wrist always did create FIT files with all GPS data in them.

    It seemed to happen more frequently during walking activities, esp. after short pauses waiting to cross a busy road. Rarely while running, and never during cycling, so there might be a correlation with slow speed, but that's just a wild guess. Too little data to go on.

    I could never reproduce it. Tried running/walking without sensors for weeks, and it never happened during these weeks, but that doesn't prove anything. Tried without a phone connection: never a problem with Bluetooth off, but that doesn't prove a relation either.

    It's a bit it obsessive.. but if it really matters to have my activity recorded correctly, for a challenge or something, I use a Fenix 1 to co-record.

  • As I experienced this issue only once in 1,5 years (>600 activities), I cannot really comment on your findings, but my case was during a run with no pause before the position recording stopped and I had bluetooth swithed off.
    With my Fenix 1 I definetely had worse GPS-tracking than with a F3 and now my F5+, but unfortunately it "died" four years ago.

  • Hi,

    I have the same issue as you had. Did you found a solution? Did you tried to uninstall Dozen run? Did it help you?

    Thanks in advance for your reply

  • Hi, did hard reset solved the issue?

  • Thank you for reply and enjoy your 6x. I finally tried a hard reset yesterday. I'll see what happens in the next weeks