Google Pixel Watch 2 GPS data missing

[DrWatson]

Just took my Pixel Watch 2 LTE for its first parkrun today and recorded on it on Fitbit exercise. I don't have data on the watch but it was connected to my phone by Bluetooth. It only tracked just over the first KM of the run before the GPS cuts out. Final distance is correct (estimating from stride length?) but there is no map tracking beyond that point. Any solutions?

Moderator edit: Subject for clarity.

[rexxfan]

Thanks for chiming in. Glad to hear it worked out for you. I'm not sure I've got the energy to fight with them anymore. I just wish they would acknowledge there's a problem and offer to exchange defective units via some sort of recall. Perhaps if some high profile android-focused blog picked up the story it might help.

[kanickl]

I have the same issue with my pixel watch 2 and fitbit running. I have opened a ticket with fitbit support on this and I would advise everyone here to contact support so that they have to open a ticket.

My problem is the same as described above, recordings of training always fail on the gps tracking with varying discatences covered. I usually run about 8km and the data only collects gps data for 0.3km.

Using the fitbig app to records bycicle rides does not seem to be affected for me.

[rexxfan]

For what its worth I decided to give up on Google/Fitbit for the time being. I reset the watch and put it away for now. Perhaps I will trade it in on something in the Fall. I replaced it with a, not too unreasonably priced, Garmin Vivoactive 5. So far (after just a few days of use) it's been good enough for my purposes. There are things the Pixel Watch did that I miss a bit, but not so much that I'm willing to continue to suffer with the unstable GPS issue. The Garmin GPS, as you might expect, has been flawless so far and it's definitely nice not to have to recharge it every night or put up with sudden unexplained turbo battery drain. Best of luck to you all.

[k_mcclean]

I have nothing to add to this really, just noting I have the same issue. Watch tracks some exercises ok, on others cuts off after a short while. Very annoying, makes the watch less than useful. I've tried every step here, can't get anywhere. If this is a hardware issue, I would expect Fitbit to send out replacement watches

[RSCLE5]

Pixel Watch 2 user. The watch will start a run, say its connected to GPS. I run 3-4 miles hit stop. Open the app and it syncs then says I ran for 11 seconds total with 0 GPS information. If this isn't fixed I am selling it on ebay and buying a Garmin. I noticed one time I got a text while running and hit it to look, then went back to my run screen. That seems to kill the GPS, which it shouldnt? If it does, thats horrible. I noticed last night my watch GPS permissions for the fitbit app were set to "while using the app", I set it to always. If this doesn't fix it and it happens a few more times I will be looking for other watch options. I need to know how far I go and how fast I am so I can compare it and get better at running over time. This should be a non issue for a "smart watch".

[rexxfan]

Been there, done that. I initially thought it would solve the issue but in the end it didn't, at least for me. For what its worth, since I switched to the Garmin Vivoactive 5 a few weeks ago I've walked the same routes over which I experienced multiple GPS failures with the PW2 and I haven't had a single failure. So the PW2 GPS implementation is clearly inferior to Garmin's. Whether that's due to a software or hardware issue (or both) I've got no idea. I'd just like someone at Fitbit/Google to acknowledge there's an issue and actually look into it, but there seems to be no interest in doing so, at least in my experience with the support team. So yeah, my conclusion stands, if GPS tracking of your workouts is important to you, I'd strongly suggest avoiding the PW2. If its a hardware issue only affecting some small percentage of units, it's possible you could get a good one, but do you want to take the chance?

[MiniSumo]

The google advice so far hasn't worked for me, the retailer has agreed to a refund.

My last advice saw a factory reset, no you can't use the latest backup in recovery and yes you will have a lack of synchronisation between alarms even if it indicates it's set to go. Oh, another reset to fix that too.

Whilst the first Pixel Watch 2 didn't seem to have the GPS / Heartrate / Rapid Discharge issues, that was the one the crown wheel fell off!

I think rexxfan's on the money for replacement.

[RSCLE5]

Thanks Rexxfan and minisumo for the info...The thing I noticed that seems to cause my watch to not track the gps especially is if you press the dial and go to the home screen, or check a text message. Anything that takes you out of the active tracking screen causes it to not track. I find it hard to believe there aren't google employees who use this watch and go on a run and this doesn't happen to them at some point. But maybe not...they might just be wearing them for the time and texting functions. Not actual exercise. Its frustrating, because as a runner stats are everything.

On a positive note last night I ran a 5k (3.1 miles) and ran on the right side of the road in my neighborhood. After my run I got in my car and drove the same route to compare the mileage. It was probably within about 10ft of being on to 3.1 miles in the car. That could be because of where my wheels on the car started or where I stopped my watch or the gps actually locked on. So that is at least good that its mostly accurate...that is when it works properly! Oddly enough though on the map view of that 3.1 mile run, the gps lines are still not quite straight and overlapping parts of the run on the same road showed varying results on the map. As in zigzags rather than a straight path, but it calculated the right distance at least.

[MiniSumo]

When I'm setting off for an activity, I just go - I don't return to the home screen or check messages.

I don't have tilt or touch to wake enabled. pressing the crown wheel wakes on the activity recording from where I side-swipe to end recording.

I'm not suggesting you don't have an improvement but it's not going to be a solution.

In terms of accuracy of tracking, by it's nature, GPS will always have a wobble. Generally, GPS is accurate to within 5-10 meters, whilst we may see some correlation there are a number of factors influencing what we see including satellite geometry, signal blockage, atmospheric conditions as well as the receiver design/quality.

[MiniSumo]

Good luck on your resolutions, my Pixel Watch 2 was returned today and I'm moving on. 😁👍

[RSCLE5]

MiniSumo, I understand. I have done maybe 4-6 runs since I posted about mine. All being around a 5k (3.1 miles) and it has worked very well. My only complaint with the GPS is that the paths are a little jig jagged in comparison to my other watch (amazfit gtr4). I ran with a watch on each arm to compare stats/gps. Then I got in my car and drove that same route on the road (I ran on the road, not a sidewalk so it was a closer comparison). The Pixel Watch 2 was about 10ft within the exact 3.1 miles in comparison to my car. The amazfit gtr4 showed the same 3.1 miles about 25ft farther. So its good to know the PW2 is accurate in distance though! I just hope it keeps working. Goodluck to you and whatever you choose next!

[TheGingerDev]

Some good news.  My replacement watch finally arrived today.  Took it for a 5 mile walk this evening, and the GPS tracked all the way.  It also doesn't appear to have the charging issue of the previous unit:  just put it on the charger and it starts charging straight away with no messing about. 

I haven't had chance to see if any of the other issues I had have been "fixed", but they were all pretty minor.  All-in-all the replacement "feels" more stable so far.  I just hope I haven't gone and jinxed it now.  🤞