Problems with Run Pace Workout App

Question

Level 1

10 points

Problems with Run Pace Workout App

OK .. I ran with my iPhone for the first three runs to get the AW calibrated. So, I thought I would go solo for the next two runs (AW and Bluetooth Headphones) and see how things worked.

I have come across an interesting problem...

I have been running for 40 years (I am 51 years old), and pretty much know by feel what an 8:00 minute mile feels like vs. an 8:30 or 9:00 minute mile. So today I ran a route a I run a lot and I ran fairly easy/moderate pace for me what felt like 8:00 minute miles. That was confirmed by glancing at the AW during the run and seeing 8:04, 7:58, 8:02, etc.

So I expected to see something like 8:02 for my average pace at the end of the run. To my surprise, the average pace on the watch and the iPhone activity app showed 8:51 ???.

Now there were a few stops at intersections, but I was diligently paused the AW each time (even though it is a pain in the a** to do so ... please let us use the Friends button to pause/un-pause).

I am thinking the AW is using elapsed time / distance to calculate average pace, instead of moving time / distance.

Anyone seeing similar results?

Apple Watch Sport 38mm, iOS 8.3

Posted on Jun 3, 2015 10:27 AM

Reply

Answer 1

Jtnorr

Level 1

0 points

Jun 3, 2015 1:47 PM in response to bobv190

I ran today for the first time with watch and phone. My run was 1.1 miles off and the pace of course was off because of the distance. my heart rate was about 20 beats a min. off also. I know it was my first run with it so I will see if it gets better. I will have to use my Garmin on the longer training runs and the apple watch for the easy runs

Reply

Answer 2

bobv190 Author

Level 1

10 points

Jun 4, 2015 4:40 AM in response to Jtnorr

For me, distance seems to be pretty close. The route I ran yesterday normally is about 5.5 miles, the AW came in a little short at 5.41 miles. Not having any issue with HR, seems to track almost perfectly with my chest strap. Cycling is another story, as there tend to be more dropouts on the bike.

My issue is that the average pace at the end of the run seems way off. It seems to me that it is counting paused time in the average pace calculation, not a big deal, but it shouldn't do that.

It may take a few more runs for it to get dialed in.

Reply

Answer 3

Jun 7, 2015 5:32 PM in response to bobv190

I definitely I have the same problem. I ran 8.68 miles today at exactly an 8 minute pace (mapped it online after the run) but the watch has me running 7.5 miles at 9 minutes pace! And when I look at the watch it always said I was running 8:30-9:30 pace. I ONLY run with my phone, never with just the watch, and I've had it for about a month now. I'm a long-time runner and know pace very well. I have no idea how it can be so off but I find it really disappointing.

Reply

Answer 4

Jtnorr

Level 1

0 points

Jun 7, 2015 5:36 PM in response to adriennejg

I have seen a few articles tell you to do walks with e watch in the workout app. After doing a few 20 min' walks it will get better. I just don't have time to walk! lol I will try it soon and se If it get better. I use my garmin for long runs so its not a big deal.

Reply

Answer 5

G3gator

Level 3

596 points

Jun 7, 2015 5:58 PM in response to bobv190

"I was diligently paused the AW each time (even though it is a pain in the a** to do so"

I dont understand why there isn't an automatic pause/restart for walking, running & cycling. It is something my relatively inexpensive bike computer does.

Reply

Answer 6

bobv190 Author

Level 1

10 points

Jun 8, 2015 5:11 AM in response to G3gator

I don't get it either.

You would think a company the size of Apple would have poached employees from Garmin, Polar, TomTom, etc. to actually find out what functionality is important to runners/cyclists. Certainly autopause is near the top of the list. I would add to it the ability to map functions to the Friends button (kind of useless as it is) like pause/unpause, etc. I find using the touchscreen when your hands are sweaty is pretty tough.

Plus, the 5 second HR recording interval is far to infrequent, especially when doing intervals. Should be 1 second.

Reply

Answer 7

G3gator

Level 3

596 points

Jun 8, 2015 5:28 AM in response to bobv190

Have you reported your issues to Apple? The more of us that do, the better chance of getting this thing fixed. I hope.

George

Reply

Answer 8

Jun 9, 2015 4:41 AM in response to G3gator

We should! What's the best forum or mechanism to report to apple? I was hoping they monitored these boards.

Reply

Answer 9

Jun 9, 2015 5:10 AM in response to bobv190

I just got my watch last week and comparing the pace on AW and Nike Running: AW is a little off, the running distance is about 13 kilometers:

I carry the iPhone during the running.

Nike Running Apple watch (Per Kilometers)

5'07'' 5'29''

5'08'' 5'21''

5'08'' 5'31''

5'11'' 5'24''

I know AW still counts time during your pause, but even consider this difference, the pace on AW is still off. During my running, AW calculation for each kilometers always longer than Nike Running, some times the distance off by 400meters, sometimes 700 meters during a 13kilomters running.

HR monitor is very close and I like it very much.

Reply

Answer 10

G3gator

Level 3

596 points

Jun 9, 2015 5:03 AM in response to adriennejg

https://www.apple.com/feedback/watch.html

Reply

Answer 11

G3gator

Level 3

596 points

Jun 9, 2015 5:04 AM in response to xiaodongStar

Did you have your phone with you during the runs? If not, had you 'trained' your watch?

George

Reply

Answer 12

Jun 9, 2015 5:12 AM in response to G3gator

Yeah..I have my iPhone5s during the running. I believe the first running on Friday for 13 kilometers should be enough for calibration. But the records after Friday is still off

Reply

Answer 13

Jun 9, 2015 5:35 AM in response to G3gator

I always have my phone on me when running. Thank you for the link!

Reply

Answer 14

bobv190 Author

Level 1

10 points

Jun 9, 2015 5:42 AM in response to bobv190

A little positive news ... I did a run that I know is exactly 5 miles with the AW only yesterday, and when I was done the final distance ... 5.02 miles. Pace looked pretty good also .. 8:14/mile. Although, I still believe that pause time is counting in the pace calculation .. this run only had a short pause at an intersection.

Can't wait for watchOS 2.0 ... sounds like we may be able to use Siri to pause/unpause. Plus, 3rd party running/cycling apps with access to all the sensors of the AW are bound to be better.

Reply

Answer 15

G3gator

Level 3

596 points

Jun 9, 2015 5:44 AM in response to bobv190

"Can't wait for watchOS 2.0 ..."

Yes. The potential is there. With a little tweaking it could be outstanding.

George

Reply