Wrong time, therefore wrong everything

[raabmar]

I am a new user, looking for a simple app without social, sharing, upsell etc. that's why I came here. But I struggle with the basics

For instance it shows me 30 minutes for a run, but actually it was only around 20 minutes. I was surprised when it told me (audio cue) after only a few minutes running that I am already running 12 minutes for the first kilometer.

Maybe it starts tracking when I enable GPS, before I actually start running?

It's a bit difficult to use the app when the only thing that seems to be accurate is the GPS (distance, map) but timing is completely off.

I read somewhere about the GPS time, but why? And why would it show wrong.

I have the phone in my pocket while running but the map shows my run 100% correct

[raabmar]

So I found two related issues those are many years old:
#910
#1170

Not sure, if it all makes much sense if time is unreliable. Why not using the actual current time instead?

[gerhardol]

Time on locations are set from system time in the phone (not the more accurate GPS time due to user feedback, can be enabled though).
Time is only calculated on locations when an activity is started (not when paused).
So the issue may be that the location update has not been delivered and an old location with old time stamp is used.

[raabmar]

Thanks for the feedback, I went through some old issues and wiki and read about that change.

• "Time from GPS points" is disabled (default).
• "Current speed from GPS points" is disabled (default).
• Autopause is disabled (default).
• Autolap(m) was set to 1609.34 (default) but Audio Cue intervall (m) was set to 1000; from a user point of view that's a confusing mismatch but in my eyes should not matter for the entire time calculation; I will change Autolap(m) to 1000 so troubleshooting is easier
• I switched from miles to kilometers in the settings

I only did 3 runs yet, I have the lap and pace cue feature enabled and I can tell from 2 out of 3 runs it's the first lap that leads to this.

The total time is wrong also. How is the total calculated? From what I hear now, it's probably not calculated by end time minus start time, but a total of the individual laps. If the first lap is completely wrong, then the total time is wrong, and everything else is wrong.

Time is only calculated on locations when an activity is started (not when paused).

OK, then this should be not an issue, currently I only start/stop, no pause in between, no autopause

So the issue may be that the location update has not been delivered and an old location with old time stamp is used.

I am not sure if I get this right. In theory, if I just start a run and end a run, I only need the time at start, start/end time of laps, time at end. If pauses or autopauses are happening, then probably those start/end timestamps are also required.

If I am 100% sure that the first audio cue (after the first lap) is wrong, I wonder where the problem happened. Is the keyword here "location update"? When is the location update happening? Because the GPS tracking on the map is perfectly correct.

My gut feeling still tells me it started taking the start time stamp from the time the GPS was enabled, not from the time when I actually started the activity.

Because 1st run it seemed to be fine. 2nd and 3rd run it was clearly wrong. I am very sure on my 2nd and 3rd run I spent some minutes walking, choosing music, etc. before I started the actual activity. A lot points to that, but I only have 3 runs yet to confirm it.