AW5 LTE GPS accuracy problem

[NME42]

Probably right. Maybe this will simply disappear with a new AW release.
Still no idea if this problem is only with AW5 LTE or other devices also affected.

 

[rbart]

I don’t know.
It seems very few people run with aw LTE...
Or most people are casual runners who don’t care about accuracy

 

[NME42]

Most likely. But still strange that only AW5 users like us found their way to this forum.

 

[NME42]

Tried a new path and asked the Stryd developers if they know about this accuracy issue. Maybe they have a better channel to Apple.

 

[mk313]

I don’t know.
It seems very few people run with aw LTE...
Or most people are casual runners who don’t care about accuracy

Or they don’t experience the issue. I’m someone who runs with an Apple Watch 5 LTE but I just don’t experience any tracking issues.

 

[NME42]

Or they don’t experience the issue. I’m someone who runs with an Apple Watch 5 LTE but I just don’t experience any tracking issues.

What is your network provider?

 

[rbart]

Or they don’t experience the issue. I’m someone who runs with an Apple Watch 5 LTE but I just don’t experience any tracking issues.

It also depends where you run.
If you run in "open" places, there is no problem.
But where you run under trees or in places where the GPS reception is difficult you can have issues.
I am also wondering if the accuracy issue is not linked to a process or an app on the watch that get/sends data on LTE
If you use apple built in workout app, the problem is really less visible as apple smoothes a lot the tracking.

 

[NME42]

My awful track yesterday was in an area with good reception.

 

[mk313]

What is your network provider?

Sprint.

 

[NME42]

Got the info in the Apple Watch Stryd forum from another user to switch OFF motion calibration & distance:

Calibrate your Apple Watch for improved Workout and Activity accuracy - Apple Atbalsts (LV)

Improve the accuracy of your distance, pace, and calorie measurements.

support.apple.com

 

[rbart]

Strange ...
Motion calibration is supposed to help in case of poor gps reception
If you use a stryd, it can be in conflict but for people like me ...

 

[nill1234]

My tracking with the standard app is perfectly fine never seen such horrible tracking. LTE is mostly on.

 

[NME42]

First run (20km) with LTE ON and motion&calibration OFF: very good track, no glitches. But we all know: one run is no run. Maybe if I have ten runs in a row with no glitches, I can confidently say that this fixes it. But it looks promising at least.

@rbart: I would say that our watches have enough calibration data to go through areas of bad reception.

 

[rbart]

As some people don't have any issues, I am wondering if a complete reset (without backup restore) of my iPhone + my watch could help
I have tried many times with my watch, but I haven't restored my phone "as new iphone" for 2 years...
I will also test with your setting

 

[NME42]

Today a folk running with his iPhone and an AW (connected to Stryd) reported the exactly same problem as we AW-only runners have. Sounds like an issue in the GPS software both on iOS and watchOS.

Second run today with LTE on: still good.

 

[rbart]

You are right.
Yesterday I have walked with my watch+phone and I has the same accuracy issues with very strange tracking in some places.
The actual track is in light blue with 2 stops in shops (light blue circle)
So it's not really linked to the watch hardware.

 

[NME42]

Wow, looks crazy. So there is at least hope. Maybe Apple is more interested in fixing problems with iPhones than with Apple Watches. And if they fix it on the iPhone, the AW fix should be possible.

 

[rbart]

I have very small hope ...
I think it's not in their problems top list .

 

[NME42]

In German we have the saying: "hope dies last". ;-)

But you are right. Currently it seems that adding more emoijis is top priority.

 

[rbart]

I have an opened incident for months without any news ...
May be I will try again, but first I will try you setting and/or reset both my phone and watch

 

[rbart]

I have found something interesting.
I have looke into my old trackings and I have noticed the same issues with my previous AW series 2 when running with my iPhone.
It was
- same iPhone 7
- iOS12
- apple watch series 2
- watchOS5
So the problem is not new, not limited to series 5, not limited to watchOS 6/iOS 13
It's linked with the algorithms that apple uses to track position when using GPS+LTE (on watch or iPhone)

 

[NME42]

So good and bad news at the same time.

 

[NME42]

Ok, third run with the "motion calibration" setting to OFF and LTE on. Bad news: two glitches. Not really absurd ones, but still annoying.
So no solution yet.

 

[rbart]

Today, I have decided to restore "to new iphone + DFU" and to new watch an restart all from scratch.
I will see if it helps or no ...
I was a bit surprised that the "motion calibration" setting could fix the issue.

I have lot of runner friends who use Garmin watches, and they also have big glitches sometimes ...
So it's not only an apple watch issue

 

[NME42]

Good luck!

In my very long history with Garmin watches I only had two times such glitches.