Is there any reason why this is happening?
Right, I thought it is different with LTE version of Watch![]()
The error you get is huge, it's more than 2-3%.
You should try to reset calibration settings and run in open sky area to try recalibrate
Maybe it can help ...
It's really a very bad track, but I am not sure it has an impact on the distance measured by the watch.Upping this thread so that it is clear that the problem is not fixed. AT ALL.
Am currently providing information Apple about the problem, maybe it will be fixed. Found several other folks with the same issue (mostly German Facebook group). Also, same problem is reported for iPhone 11.
Just to show what the current status is, did today a run with LTE/cellular enabled. Blue is run from yesterday (no LTE), yellow today (with LTE). Disgusting.
View attachment 921510
View attachment 921511
I’m having this very issueMy watch has been replaced, but it's still the same with the new one.
The distance calculated by the watch is over estimated and I am very dissapointed.
Running activity is most important for me in a smartwatch...
Is it an LTE issue ? a watchOS6 issue ?
makes no differenceI was rereading this thread and saw this. I’m going to try this. All of the times I’ve reset my calibration settings and then did the next activity, it’s been on my treadmill in the basement of my house. Curious to see if it affects it. I run a lot of the same routes so I’ll be able to compare.
I find the gps route to be accurate but the splits wrongI don’t know.
It seems very few people run with aw LTE...
Or most people are casual runners who don’t care about accuracy