Galaxy Watch Series devices poor GPS Fix performance

[usertlOcykGzxn]

Watch seems to be plagued with problems resolving GPS fix when not tethered to a phone.   I went out for a run, without my phone and it took the watch close to 10 minutes to get a GPS Fix.  This severely limits the functionality of the "Outdoor/Fitness" aspect of the watch.

Is there a planned fix?

[LongHiker]

@SoggyWhiteBread In the top photo your watch is able to get a clear GPS signal and therefore records more data points. The blockiness of the bottom picture indicates that the watch couldn't consistently read GPS signals. This can happen if the signal is obscured or weak. 

[SoggyWhiteBread]

Which makes sense, but it's the exact same path and both days were clear skies -- so is there something else that might be causing that?

[randomdude925]

Hello, I purchased a Galaxy watch 4 back in December 2022 and have always had an awful experience with the GPS sensor. After about four months of owning the watch I installed a software update and lost all ability to GPS fix for over a year, regardless of what apps were installed or how many times I software reset. A few days ago GPS started working again, but it is so inaccurate that it may actually be worse than just not having it. The images below show the results I have been getting.

Run where I ran around for a bit then went on a trail, my watch never recorded the trail at all and still somehow still ended up with more distance measured than I actually did. 

This image shows how jittery the watch is with recording. This one was actually a little over 1 mile, probably 1.1, but my watch guessed 1.29

I ran a mile exclusively on a track, four laps. My watch guessed I went into a neighborhood? IDK, but it said I did 1.44 miles when I did 1 exactly. 

This one is just funny because I started and finished in the same spot on the actual run. My watch says 4.4 but in reality I would be surprised if it was more than 3.75

When I purchased this watch over a Garmin, I was thinking the choice was between great GPS, alright everything else (Garmin) and passable GPS and great everything else (Samsung.) I would not have purchased the watch if I knew I would have no GPS or unacceptably inaccurate GPS depending on the day with Samsung. Very disappointing. 

[realaud]

Have you calibrated the compass in Google Maps? If the compass is miscalibrated, your stats will be incorrect.  If your location data is incorrect on your watch, it should also be incorrect on your phone, since the watch takes its data from the phone settings (only so much room on the watch for its own settings).  Make sure your phone has use precise location on and, seriously, recalibrate the compass (which, actually, should be done periodically).  You can also calibrate the compass on the watch by pulling up the apps screen, scrolling down to compass, clicking on compass, swiping up on the compass and scrolling down.  You will then see the button to calibrate.  If you don't see the compass on your app screen, add it in the wear app, but it should be there unless you removed it.

[randomdude925]

I did not know that was a thing that would help! I hope this works next time I run on Monday! Thanks!

[useru94oypIq0Q]

Over the past eight years, I have consistently utilized the same running route, and I've observed a recent discrepancy in distance and pace measurements. My Galaxy Watch 8 Classic appears to be overestimating these metrics by approximately 10-15%. Specifically, a 5-mile run is typically recorded as 5.5 to 5.6 miles, despite clean GPS tracks. Interestingly, upon uploading the data to Strava, the correct distance is reported. Please advise what to do because if a solution is not available I'll unfortunately have to return the watch! 

[Robin621k]

It is way off. I am currently testing this by wearing both a Pixel watch 4 and a Watch 8 classic. Distance is always off by 15%. I just ordered a pedometer to further test this.

[useru94oypIq0Q]

Thanks for your kind reply, at least I now know that I am not alone who is facing this issue. And I guess there is no easy solution to it 😢

[useru94oypIq0Q]

The Samsung watch consistently overestimates running distance and pace by approximately 15%, despite multiple troubleshooting efforts including app switching to sportswerks, wiping watch cache, disabling location accuracy, and a full factory reset.
Having run the same route for over eight years with various devices—Garmin, Huawei, Amazfit, and previous Samsung models, I am confident in the accuracy of the physical mile markers and can assert with certainty that the watch's readings are incorrect.
Interestingly, once the activity is uploaded to Strava, the distance is automatically corrected, suggesting a discrepancy between the watch’s native GPS processing and Strava’s post-processing algorithms. This points to a potential firmware or software calibration issue within the Samsung device that warrants further investigation.