Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
AW5 LTE GPS accuracy problem
- Thread starter rbart
- Start date
- Sort by reaction score
Still having the same problems as described here. Dead-on accuracy everywhere (even under tree cover, etc) with LTE off, but with LTE on, often shown going down side streets that I never even traversed while on a run with inaccurate distance and pace.
I have had some increase in accuracy with LTE on using Workoutdoors with the setting "Use Calibrated Distance Estimates (Uses when GPS is off)" turned to the OFF position. It is definitely not perfect, but the tracking is a significant improvement over the regular workout app. Of course, I am but one person giving you information on a few runs, so it may not work as well in your case but it may be worth a try. It's still disappointing overall, but for those of us that need to be connected to LTE for some reason while running (but spent $500+ to not bring your phone on a run!) this could get you closer to a middle ground.
I have had some increase in accuracy with LTE on using Workoutdoors with the setting "Use Calibrated Distance Estimates (Uses when GPS is off)" turned to the OFF position. It is definitely not perfect, but the tracking is a significant improvement over the regular workout app. Of course, I am but one person giving you information on a few runs, so it may not work as well in your case but it may be worth a try. It's still disappointing overall, but for those of us that need to be connected to LTE for some reason while running (but spent $500+ to not bring your phone on a run!) this could get you closer to a middle ground.
Hi Jared, I did extensive tests with different training apps and the result at the end was almost identical when it came to zig zigs on courses. Thanks for the tip for WOD's setting, this makes sense at most probably the current location in these cases does not make any sense.
May I ask you to look up when your AW5 has been produced?
You just need the two characters in position 4 and 5 of your serial number and can look up in this table (page is in German, but only the table is relevant): https://de.tab-tv.com/?p=18086
I am using a Stryd footpod with the native Stryd app and am anxiously awaiting Stryd support in the WOD app.
May I ask you to look up when your AW5 has been produced?
You just need the two characters in position 4 and 5 of your serial number and can look up in this table (page is in German, but only the table is relevant): https://de.tab-tv.com/?p=18086
I am using a Stryd footpod with the native Stryd app and am anxiously awaiting Stryd support in the WOD app.
I agree that WOD without this setting changed is, to me, pretty much exactly the same as using the native app - that is to say, total garbage.
My watch was a Sept 2019 build date. Has the trend toward better performance on watches made later panned out? I saw that discussed earlier in the thread. I have considered trying to get Apple to exchange the watch, but just haven't had the energy to do it yet.
My watch was a Sept 2019 build date. Has the trend toward better performance on watches made later panned out? I saw that discussed earlier in the thread. I have considered trying to get Apple to exchange the watch, but just haven't had the energy to do it yet.
It is not great. Here’s a portion of the worst run I had with it - which was a 9 mile race where it was .27 (!!!) long. I should be on the gray Kachinka Hollow Road. I missed an award by 3 seconds. Ugh. I was so, so mad. It’s usually not THIS far off, but the longer my run, the further ahead my GPS distance is than my running partners.
Attachments
Yeah, I run to place and win, so it’s imperative that my watch be accurate. Especially in a longer race like this one, where it’s not as easy to gauge your overall pace (or place) during the race.
I would never go into an important race relying on GPS accuracy no matter what watch it is, be it Apple or Garmin. Only in combination with a Stryd. Missed my PB on 10k by 13 seconds because of unreliable GPS which is well within accuracy tolerance.
It’s always worked fine for me until this particular watch. My previous Garmin watches were right on with the mile markers which are wheel measured. So I’ve never had reason for a Stryd. I am generally a less-is-more runner anyway.
Some new feedbacks with my "new" watch:
- I still have glitches in some areas
- glitches are more visible with WOD (no GPS smoothing) than with Apple builtin app
I have changed my phone operator (SFR->Orange) to check if it changes something : IT'S THE SAME
Other observations:
- I have made some runs with my phone, so the location is given by the iPhone, the watch is only a remote display. I have noticed exactly the same glitches, so I can say that the problem is not related to the Apple Watch 5, but to Apple Core Location services. For me it's purely software. My wife with an S3 (not LTE) has the same glitches when Che runs with her phone.
- I don't really believe this issue can be fixed with a newer S5 watch.
So my only hope is a software fix with watchOS7/iOS14 ...
I hope my tests can help. I will probably go back to Apple after more testing
- I still have glitches in some areas
- glitches are more visible with WOD (no GPS smoothing) than with Apple builtin app
I have changed my phone operator (SFR->Orange) to check if it changes something : IT'S THE SAME
Other observations:
- I have made some runs with my phone, so the location is given by the iPhone, the watch is only a remote display. I have noticed exactly the same glitches, so I can say that the problem is not related to the Apple Watch 5, but to Apple Core Location services. For me it's purely software. My wife with an S3 (not LTE) has the same glitches when Che runs with her phone.
- I don't really believe this issue can be fixed with a newer S5 watch.
So my only hope is a software fix with watchOS7/iOS14 ...
I hope my tests can help. I will probably go back to Apple after more testing
I agree.
I think it's a software design choice from Apple. They probably put an higher priority to network connectivity than to GPS accuracy. When cellular connectivity is bad, I think they push the SOC to prioritize the network connectivity and decrease the GPS part (maybe for battery efficiency reason).
Then you get a very poor location accuracy, but they probably think that casual users don't care.
For people who run only with their phone, they probably assume that an iPhone is not a perfect running device.
And for people who run with AW ... there are very few complaints and they don't care.
I think it's a software design choice from Apple. They probably put an higher priority to network connectivity than to GPS accuracy. When cellular connectivity is bad, I think they push the SOC to prioritize the network connectivity and decrease the GPS part (maybe for battery efficiency reason).
Then you get a very poor location accuracy, but they probably think that casual users don't care.
For people who run only with their phone, they probably assume that an iPhone is not a perfect running device.
And for people who run with AW ... there are very few complaints and they don't care.
I have just spent 1 hour with Apple support at phone.
I have talked to a "supervisor", he seems to have understood the problem.
For him, it's a software issue, he has seen that I have raised this case many times.
Finally he told me to wait for watchOS 7 to see if it fixes the problem ...
Let's hope ...
I have talked to a "supervisor", he seems to have understood the problem.
For him, it's a software issue, he has seen that I have raised this case many times.
Finally he told me to wait for watchOS 7 to see if it fixes the problem ...
Let's hope ...