I found the post below from a couple of years ago and see that it was resolved. This is what my app is currently doing, this is very frustrating as I am currently training for a half marathon and would love to be able to see how I am doing throughout the run, but since my pace and avg pace times are based off of incorrect moving time that isn't possible. I have updated and also deleted and redownloaded the app. Is there something that I need to do in the app or a fix that is coming with a new update??
.
.
.
.
.
.
.
Solved
Moving time and elapsed time not correct
-
2 years ago
- 18 replies
+4
- Hub Starter
The last three times I have run using Strava it has incorrectly had my moving time less that half the time of my run. For example this morning I ran 12.3km in 1 hour 11 minutes (without stopping) yet my moving time is listed as 29 minutes.
As a result my average pace is completely wrong and all segments are wrong.
It is correctly tracking the distance I have covered so don't see how this could be a gps issue? Also I have used RunKeeper simultaneously, which has worked fine. I am having to delete my Strava activity and port from RunKeeper.
Any idea what is causing this? I have been using Strava with no problems with my phone for a long time so don't understand why it has started doing this?
Best answer by Scout
RESOLVED: As of November 14th, we've released a fix that should resolve the issue for all athletes in the most recent app version. Please update your Strava app to 333.10 or above using the instructions below.
Google Play Store:
Strava: Track Running, Cycling & Swimming
How to update your apps on Android: Support - Google
11 people like this