 You don't need to be an 'investor' to invest in Singletrack: 6 days left: 95% of target - Find out more
Having just started getting back into running (well, plodding, mainly due to the minging trails although don't know how long my creaking knee will last) when I pull my phone out to save the live pace/km shown is significantly less (like 30s per km less) than the figure it gives you when you save the run. Anyone know why this is? It might do this on rides as well but they are all about the segments for me so can't say I ever noticed. Obviously if the saved time was less than the live this wouldn't be a problem.....
Elapsed time v moving time? Do you stop, or go reaaaaally slow at points so that it thinks you've stopped?.
Tbh there's always a few secs diff between my garmin and Strava.
I don't imagine live pace on a phone is particularly accurate either btw.
ye as above sounds like elapsed time time/moving time. Plus Strava isn't entirely accurate, you can do the same route several times and get different altitude /amount of climbing readings by +/-50ft
It's the moving time vs total time, strava bases your pace on moving time.
If you set the type to 'race' it then uses elapsed time.
And on the above link it says if you don't manually pause, it will automatically calculate the non moving time with your devices accelerometer, however if you manually pause at least once it won't do this and will only use your manual pauses.