This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What does "elapsed time" actually mean?

Former Member over 7 years ago

I thought it was self-evident but I have noticed recently that at least for some tracks, "elapsed time" is well short of "end time" - "start time". Auto-pause is turned on, which affects "time" as expected but the activity is never stopped.

Top Replies

trux over 4 years ago in reply to Former Member +1

Yes, it could perhaps remove the last non-moving section, but then again, you would certainly find people complaining about it too. The way it is done is logical, makes sense, and if you need to see the…
trux over 4 years ago in reply to Former Member +1

I would much rather have streamlined such as records by sport i.e. 20k road run record separate to 21k trail (same with road cycling and MTB)

Not exactly what you want, but if you often ride or run in…

All Replies

0 ASmugDill over 7 years ago

http://www8.garmin.com/manuals/webhelp/forerunner920/EN-US/GUID-545C7C14-6E4B-4E6D-A7F5-215C49DBB821.html Elapsed Time
The total time recorded. For example, if you start the timer and run for 10 minutes, then stop the timer for 5 minutes, then start the timer and run for 20 minutes, your elapsed time is 35 minutes.

0 Former Member over 7 years ago

http://www8.garmin.com/manuals/webhe...C49DBB821.html Elapsed Time
The total time recorded. For example, if you start the timer and run for 10 minutes, then stop the timer for 5 minutes, then start the timer and run for 20 minutes, your elapsed time is 35 minutes.

What you describe is exactly "end time" - "start time". This is not happening, which means either the document quoted is wrong or Garmin Connect is computing incorrectly. I have an activity from Friday night that began at 9:01pm and ended a few minutes after midnight. Garmin Connect thinks elapsed time is 2:21:21. This is not the first time this has happened either. I wonder if there is a bug when computing elapsed time for events that cross midnight. I see incorrect results every one of these events I have going back as far as September. However, today's activity, which did not cross midnight, looks about right.

Strava thinks the elapsed time for Friday's activity is 3:09:34. Strava's estimate for today's activity is within a minute of Garmin Connect's.

0 Former Member over 4 years ago

I don't know whether a solution was ever found but it seems to me as if it is from the time you start even past when you stopped it and only once you say done. Have had several runs where I stopped the watch for 1min literally and then started it again but elapsed time shows about 10 min more than the actual moving time.

0 trux over 4 years ago in reply to Former Member

Yes, the Elapsed Time in activities is indeed in the true exact sense of the word - time that elapsed from the beginning to the end (regardless whether you moved, or not), while the Moving Time also respect the wording, and only shows (or should show) the time when you moved.

0 Former Member over 4 years ago in reply to trux

Yes but it seems as if it doesn't stop when you press stop but rather when you select Done on the exercise.

0 trux over 4 years ago in reply to Former Member

No, not when pressing Done. It stops when you Save the app, which is logical, because when you just press Stop, you can still restart it, and continue in the activity (that happens also with the auto-stop feature on), hence it was not closed.

0 Former Member over 4 years ago in reply to trux

Apologies I meant SAVE. Yeah so the issue with this is that I stop the activity but don't necessarily save it immediately so even though I was doing the exercise for 60min for argument's sake I might catch my breath etc en then only save. But your explanation makes sense, thank you.

The functionality could be more intelligent in keeping time since stop is pressed in the back to either continue if start is pressed again or to subtract if start is not pressed but save selected. Small things really.

Thanks again.

0 trux over 4 years ago in reply to Former Member

Yes, it could perhaps remove the last non-moving section, but then again, you would certainly find people complaining about it too. The way it is done is logical, makes sense, and if you need to see the true time of the activity, you should look at the Moving Time, anyway.

0 Former Member over 4 years ago in reply to trux

It's more a case of, when uploaded to i.e. STRAVA some people may not understand and think that my sub 40 10k was not sub 40 because time elapsed says 52 min so I must have rested hehe

But yeah agree, can't please all the people all the time ;)

0 trux over 4 years ago in reply to Former Member

You can trim the activity in Garmin Connect, and remove the offending dead parts.