Forum

Voice notification is a great concept, but it isn't working so well for me. I like the idea of it telling me how far I've gone and how long I've been running so I can control my pace appropriately but I seem to get a delay, and the distance and time don't match up properly.

Today, I ran ~5.7 miles. I carried both my Droid and my Garmin Edge 705 (bike GPS) and started them at the same time. When SportyPal called out the 5 mile point, I looked at my Garmin and I was already at 5.5 miles. I stopped both at the same time, and the totals had almost exactly the same distance and time. In other words: not long after it called out 5 miles, I stopped and SportyPal was showing that I'd run 5.7 miles, just the same as the Garmin did. The times do keep up though, so the voice notification makes me think I'm running a lot slower than I actually am.

It's odd. The final total seems to be correct, but the voice notification is way off. This makes it impossible to get an accurate idea of my pace from the voice notification, which makes the feature effectively useless to me. If it was close to accurate, I would love this feature.

Today I had the notification set for every 0.25 miles but I first noticed the problem last week when I had it set to 1.0 miles.

I am getting the same problem. I have the voice notifications set to 1 mile and the readout is usually about 1 minute late. It will say "1.0 Mile crossed far, 7 minutes and 55 seconds" But I really finished my first mile at 7:05.
I am using a Nexus One with wired headphones. I listen to Pandora while I run. I have gotten this problem every time I run.
The time that it reads is correct for the time that it says it. In other words, it said "7 minutes and 55 seconds" at 7:55 but i had crossed my first mile prior to that. I hope I'm making this clear and not more confusing.
Thank you for the great app. I hope you can fix this soon!

I suspect that it may have something to do with me playing music in the background. It wouldn't surprise me if there was contention for audio resources between the music player and SportyPal. My next run is scheduled for Wednesday. I'll try running without the music to see if that makes a difference. However, I really like listening to music when I'm running. It seems to keep me running better.

I barely get any delay, even when running Google Listen or playing music. But that's with a Nexus One, with plenty of juice, so it might be an issue with processing power. This is when walking, notification frequency set to 1.0km

(OT: Come to think of it, the notification sounds like "1.0 meters crossed for..", has the kilo been left out or is it just hard to recognize?)

I was too busy to run yesterday so I didn't get to run until today.

I ran without music today. The delay problem was the same. It's not the music.

It appears to be off by about 0.1 miles per mile. In other words, when it calls 1 mile, I'm actually at 1.1 miles. When it calls 5 miles, I'm actually at 5.5 miles. I was checking the display every time it called out whole miles and it was consistently wrong by 10% every time. The display on the SportyPal screen is correct. It's just the voice notification that's off.

One thought I just had was that I should try setting time based notifications instead of distance based and see if that does any better. I may not get a chance to try it until next week though.

I tried going back to distance based notification today since there was a new release (1.4.7). The problem is still there, same as before.

One odd thing that was different today though was that at the 0.5 mile point, it announced "five hundred point zero miles". The ones after that that I could understand were fine (sometimes the music obscures them), but that was weird.

I guess I can try it again on my next run, which should be tomorrow.

I didn't think to check the forum Friday before I ran. It did it at 0.25 (two hundred fifty point zero miles) and 0.5 (five hundred point zero miles) but not 0.75 (zero point seven five miles).

Glad to learn that you found it and fixed it. :)

Tried it again today. It works fine at 2:30 and 12:30. The problem starts at 22:30 and also happens at 32:30 and 42:30. I didn't run long enough to find out if it went until 52:30 or beyond.

I rode 50 miles yesterday and the distance-triggered notifications got progressively farther off as time went on, to the point where it was announcing a mileage figure well over 3 miles too short compared to the distance actually displayed on the screen by the time I finished my ride.

I do not listen to music or anything, since it (at this point early in the season) about 3 hours to finish my ride, and I don't want to completely drain the battery. In fact, I had restarted the phone immediately prior to the ride, so only email and SportyPal were actively doing anything. I really like the motivation that the distance based notifications can provide, and I guess it telling me I have traveled less than I actually have.