Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Slight annoyance: Today I went for a 10.1 K run. As I ran, I got distance in tenths of a KM, eg 1.01 etc. But when it clocked 10, you only get tenths of a KM, eg 10.1. I don't often run further than 10, but that's a bit annoying. Why they couldn't make the font grow a bit smaller to allow four digits on screen at once, is a bit silly.
 
there are definitely issues with the GPS on the Apple Watch... I have been running the same route for years and suddenly my Apple Watch is telling me I am running it 30 seconds a mile slower than my iPhone told me; think I trust my iPhone GPS a lot more.

does anyone know, assuming you run with both the iPhone and Series 2 Apple Watch but start your run on the NRC App on the iPhone, will the iPhone GPS override the Apple Watch GPS?


This happened to me with all my activities. Then I remembered why? The watch is still learning my paces. So I've been off on everything. Even elliptical. but it's getting back to normal.
 
There shouldn't be a lot of learning going on with GPS.

@section215 - is the recorded distance the same as prior runs? Is the time accurate? Have you measured the route with other tools? i.e. other than prior results, what tells you your iPhone's measurement is accurate? Could they be splitting the difference and the actual # be in between the two? Just food for thought as people so often assume what they're using already is the more accurate when something new doesn't match up exactly.

So far I'm finding the AW2 gps to be pretty much on track with what I've been getting with a couple different Garmin running watch.
[doublepost=1478222627][/doublepost]
Why they couldn't make the font grow a bit smaller to allow four digits on screen at once, is a bit silly.
That'd suck for an older runner who could just see the three digit sized font...

Pretty common behavior on the watches I've had. It's never bothered me though, so I'm not entirely sure why it makes any difference.
 
is the recorded distance the same as prior runs? Is the time accurate? Have you measured the route with other tools? i.e. other than prior results, what tells you your iPhone's measurement is accurate? Could they be splitting the difference and the actual # be in between the two? Just food for thought as people so often assume what they're using already is the more accurate when something new doesn't match up exactly.

Thanks for the thoughts.

I am positive the issue is with the GPS on Apple Watch. I have been running for many many years, and am fortunate to spend a lot of my year in different places around the world... I know the pace I run at, how it feels, and it makes no sense to look at my Apple Watch telling me for example I am running 15 minute miles when I am running hard.

Unfortunately the problem happened again today... according to my Apple Watch GPS, I ran in a literal straight line through downtown Manhattan, which if true would have meant I was bulldozing through entire buildings and the middle of city blocks. I think downtown Manhattan is a bad zone for GPS generally, I remember in the very early days of running with my iPhone the cell connection for GPS down there was inconsistent and sometimes led to bizarre results.
 
I think downtown Manhattan is a bad zone for GPS generally
Concrete slot-canyons are notoriously bad for GPS, which determines position based on measuring the transit time of the radio signals from the GPS satellites above the horizon at that time. Occluded satellites reduce the number the device can "hear", and multi path reflections mess with the radio signal transit times.

I had a Fenix3 that was bad with this, while the 920xt on my other wrist did much better. Implementations definitely vary.
 
The last 2 times (that i am aware of anyway) i have run with the NRC app i started it with the watch.
I also have my phone on me in an armband (which i don't touch at all) and when i'm running, i get voice feedback through both watch and the phone.

Has anyone else had this? the first time it happened, I started the run on the watch and about 100m later i raised my arm to see my clock face... maybe the app crashed on me after starting the run...

I re-started the app and from what i could gather, the run started from where i was 100m along my route, with voice feedback thereafter coming from both devices.

When i finished my run, i stopped it on the watch and when i looked at the NRC app on the phone, only 1 run existed (that of the watch, starting down the street a little).

Another point might be that the volume on the phone was up which meant i could hear the phone's voice feedback much easier than when it is turned down low.

Interested in other people's opinions on this...
 
Hey i'm currently trying out the plans(my coach) from the NRC app and was wondering if i can use them with the NRC app on the watch (without my phone)?
 
Hey i'm currently trying out the plans(my coach) from the NRC app and was wondering if i can use them with the NRC app on the watch (without my phone)?
Did a run today doing just that. When syncing activity to the phone NRC app it asked me which activity from my plan I wanted the run attributed to.
 
Did a run today doing just that. When syncing activity to the phone NRC app it asked me which activity from my plan I wanted the run attributed to.
Thanks! But i guess intervals aren't working at the moment on the watch (without phone)?

Edit:So tried my first run today with my new AW2 and really loving the experience running without a phone:D The only thing that's a bit odd ist that after exporting the run to RunKeeper, RunKeeper shows a different distance (and of course pace) than the Nike app?! It's shown correctly in the Nike app and in Rungap but not in Runkeeper?

Edit2: Figured it out. RunKeeper just took the map and there were a few inaccuracies when i was running through a forrest. On the map it was a straight line instead of the curvy roads. Edited the map on RunKeeper and everything is fine now
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.