Current pace cue is way wrong.
I love Run Keeper and I love having the lady tell me how far,
how long, and my fast I am going. I have her tell me average pace
and current pace. I have learned that she perfect with most of the
infmoration,but crazy when she tells me current pace. I have a GPS
Garmon watch that I also wear. I check when the audio cues come up.
When I am at a 10:30 pace, she will say 14 minute pace and then
another time she will say 7 minute pace. I am pretty steady and I
know that I never run at either of these paces. The average pace is
usally correct. How can I get her to tell me my real current
pace.
Also, I can not see my milage splits from my android phone. My
friends with an iphone can. Is this just a different between the
tow systems, or I'm I missing something?
Thanks
Jennifer
2 Posted by Gustavo on 26 Oct, 2011 02:35 PM
There are plenty of topics about current pace error in the forum, however, Support just ignore them. Why? I use the Android version.
3 Posted by dsobel1 on 01 Nov, 2011 12:00 AM
My android phone has similar problems. The lapsed time is accurate but I do not think I do a 3min 10sec pace!. It takes some of the miles from previous runs and adds it to my current run. Never accurate. Maybe for free is what I get. If I cannot find a fix I will abandon the app.
D
4 Posted by Dave Buck on 24 Mar, 2012 09:28 PM
Add my frustration to the list. For me, Runkeeper always tells me a faster pace.
If I run 1 mile in 10 minutes, the voice will tell me my pace is 9:40 or 9:30, never 10 minute mile.
Today, I ran 1:17:45 minutes and went 8.38 miles according to Runkeeper. Get the calculator out and that should be a 9.27 pace, right? But Runkeeper says my average pace was 9:16 minute miles.
Dear Runkeeper support, doesn't runkeeper use final time divided by final distance to get average pace? What gives?
5 Posted by Eric Dickmann on 21 Apr, 2012 01:02 PM
I've noticed the same problem regarding current pace. I think the issue is that when using a GPS, it's like a trail of breadcrumbs. In other words, lots of individual readings are taken and averaged out to get your location, speed, pace, etc. To be accurate, a few readings have to be combined and averaged out. Right now, it appears that current pace is a single breadcrumb which and can vary significantly. Just watch your screen and you'll see that numbers are all over the place. But average them out, and they're very accurate. I turned off current pace cues and use current split pace and average pace instead. You'll find those much more accurate. What RunKeeper really needs to do for current pace is average the number out more like the formula they use for the charts on the website. If you look at pace information on the charts, you'll see it's pretty consistent but doesn't match at all what you see on the phone. They are clearly using different formulas for each and need to switch so that the app uses the same one as the website.
6 Posted by Dave Buck on 21 Apr, 2012 04:55 PM
@Eric, I'll try switching to current split pace. But, I'm not liking that I have to turn off the current pace cues. I like them.
My suggestion to Runkeeper is to stop using whatever equation that they are using to report Average Pace and use the following equation instead:
Total minutes run / Total miles run.