GPS seems to be dropping while on a run

[merrittjr]

I have the LTE version of the Pixel Watch on Google Fi. I'm using the FitBit app to track outdoor runs. The total distance is being calculated correctly, however, the splits and the map are not. On multiple runs when I look at the final data, I see about 2/3 of the way through, my route appears all wonky and the last mile time is wildly inaccurate. I would guess the GPS is going out about 2/3 of the way through. I'm not running in an area with large buildings but rather through suburban neighborhoods.

[YojanaFitbit]

Hi there, @merrittjr. Welcome to the Fitbit Community Forums.

Thanks for the information provided and for the steps tried on your own. It's odd you're having these issues with GPS tracking using the Fitbit app and to further investigate may I know the following information. Did you log using the exercise app on your watch? Or did you use MobileRun directly from the Fitbit app? 

In the meantime, while you've tried troubleshooting this situation please give a try to the following:

1. Measure your stride length manually and update it in the Fitbit app.
2. Force quit the Fitbit app and reboot your phone.
3. Restart your watch (if you're using your Pixel Watch to track your runs.)
4. Try recording your data one more time and make sure to use the exercise app.

Hope this helps.

[merrittjr]

I did use the exercise app on my watch. I haven't had a chance yet to try it again, though. I will report back once I do that. I'm trying to figure out if it's the app or the watch that's the problem. For more context I attached screenshots of my last run. Notice the end of the run where the GPS seemed off. Also notice my total distance was 3.1 miles, but yet my splits don't add up to 3.1 miles. My last several runs produce similar results, so this isn't an isolated incident.

 

[Dark_Eyes_]

The same happens to me too. The GPS drops during the run, but not for every run. It seems to happen more when it's been a while since a reboot (not sure though since it's intermittent). I use the exercice app exclusively, and rebooting the watch/phone doesn't help afterwards. Looking at the TCX file, the GPS and distances are stuck at the same value when it drops.

I would really like to know if it's a faulty hardware because I would RMA the watch. Thanks

[Dark_Eyes_]

Any new development on this issue? It's happened to me several times now (gps dropping hallway into my run) and I've tried everything suggested here except manually changing my stride length but I hardly see how that could change anything. It's kinda disappointing for a fitness watch to no be able to track runs...

[Username10001]

Add me to the list of people with this problem. Completed a 5+ mile run where the splits don't add up and the pace is calculated on the incorrect splits.  This is on a Pixel Watch (non-LTE) connected to a Pixel 7 Pro.

[Username10001]

OK - So previously I've been using the Fitbit Exercise app on the Pixel Watch.  I suspected the issue was NOT faulty GPS but an app issue.  My last couple of runs I have tracked using Strava (on the Pixel watch) and distance, splits and pace are all CORRECT.  So clearly this is a problem with the Fitbit Exercise app.

Also - I have Fitbit linked to my Strava account.  When I look at the map and the splits that were tracked incorrectly via the Fitbit Exercise app, it appears that it is the BEGINNING of the run that is dropped and not the end.

[starchilde]

yes it's the app not your fitbit. i stopped using the exercizie tracking years ago as it would drop GPS, tell me i'm riding a bike when i was walking, on a treadmill when on a bike... SMDH i just track sleep & literal steps with it, if i go anywhere i use mapmyrun to track distance, splits elevation etc...

[mapohb]

I observe this issue, since I update my pixel watch and fitbit app in mid of January. Since then one of three runs skips for at most 4 minutes the distance calculation. But only in the fitbit app. The watch calculates the distance correctly, the number of steps is in the expected range and the pace, too. Even the summary screen, when I stop the recording is correct.

But when I look into the fitbit app, some values seem to be based on a shorter distance. E.g. the android app shows on the map in the big bubble the correct distance, e.g. 4km, but the intermediate smaller bubbles, doesn't sum to the correct distance. The 3km is only 200 - 300m away from the 4km bubble. And at least one 1km section is in real longer than 1km (it includes the missing meters). The calculated pace in the app is based on the shorter distance and the real time, so it is slower than it should be.

I look into the tcx files and noticed, that gps values are correct, one value per second and different, but the distance value doesn't change for several seconds (minutes). I've calculated the distance by the gps values and the calculated value and time do match my normal pace and are almost equal to the missing distance.

Conclusion:

• GPS is working
• Internal distance calculation is correct.
• At some point, between recording and data display in the fitbit app, the distance is calculated again, but a chuck is skipped.

I couldn't find this error in tcx files recorded before I updated the firmware / app the gps.

[rexxcalibur]

This is exactly my problem. I have had some success by rolling back one of the apps that helps to sync GPS data from the watch. See my posts in the Google forums here: https://support.google.com/googlepixelwatch/thread/188028379/gps-seems-to-be-dropping-while-on-a-run...

[habylab]

Also confirming I have this issue. I have had this 3 times since February. No correlation really and it seems to be mid run rather than end of run. All using the Fitbit Exercise app. I'll have to use something else.

I reached out to support and they suggested turning off auto exercise track as they could see (presumably on the backend) that a Run was auto detected during my run I tracked via the app. I'm not sure this makes sense as the GPS error looked to have occured more than 10 minutes into the run, plus I've done plenty of runs over 10 minutes without issues. Auto detect doesn't use GPS also. 

One thing I considered was enabling Fitbit location at all times. Maybe battery saving kicks in on longer runs?

I am now using Ghostracer to track my runs although the "average" pacing number isn't the same which is throwing me off. It does audio cues though over earphones which is great!

[iheartcookies]

This happens to me but at the beginning and end of runs. I have a Charge 5.