Wondering if anyone has experienced similar Pixel Watch issues to me. I've been a long time Garmin user until buying a PW3 before Christmas. Lots of annoying niggles such as Fitbit app updates nuking the sync with phone and activities randomly not using GPS, but one problem really irks me.
I've recently noticed that my pace and distance in the Fitbit watch app seems a little inaccurate. Distance is usually about 2-3% under and pace similarly reduced. I've ran with my PW3 and my wife's Garmin VA4 in case I was going crazy but it's clear from the raw FIT/GPX file data.
What I've noticed is the GPS lat/long data between the two devices is really close, as is the distance when using Haversine to calculate from lat/long, but the PW3 distance values in the GPX are consistently lagging behind. It's like the Fitbit app is ignoring GPS and relying on some other input to calculate distance and pace, such as stride/cadence.
Today, I was running a steady pace and thought I'd play with this theory by giving my watch wearing arm some vigorous shakes while running. I look down at the watch and I'm doing 3:30/km on an easy run. Think I'd know if I was running that pace. I stop shaking my arm and it corrects back to the pace I expect.
Surely others have noticed this? Using Strava distance correction to use the GPS data for distance/pace calculation corrects it nicely, but I'm sick of my on-run data being off. Hard intervals are a total mess.
