what´s TIME?

Time: how much time is recorded when the timer is running, so this excludes any pauses whether they are auto or manual.
Moving Time: Exactly what it sounds like, time spent moving. If auto pause is on it is a bit redundant since it should be very close to the Time field though they won't be exact due to GPS lag and how you have auto pause configured. If auto pause is off and manual pause is not used at stops this can be useful data since it will be very different from the Time field.
Elapsed Time: The total amount of time from when you start an activity to when it is ended, including any time spent in auto or manual pauses. Elapsed time is never used to calculate a speed or pace since I think Garmin assumes when people pause they don't want that included in their speed (i.e. time spent waiting at a stoplight).

It looks like those speeds are actually using the correct fields, it's just they are inverted for some reason. I'm not sure why it does that for you, I have never had that issue and I use auto pause, maybe it's a bug with your specific device. Your average speed should not be the same as your buddy's since with auto pause on elapsed time will be the same but that is not used to calculate speed at all.

And if the only reason you use auto pause is to save battery and not to exclude time at stops you can probably turn it off without hurting battery life. I can't speak for all Garmin devices, but any of the ones I've used still keep the GPS running and all sensors active during auto pause, it just stops the timer, so it doesn't save any battery at all.

I hope this helps, if you can somehow get that flipping moving time and time figured out then it should work for you.

Time: how much time is recorded when the timer is running, so this excludes any pauses whether they are auto or manual.
Moving Time: Exactly what it sounds like, time spent moving. If auto pause is on it is a bit redundant since it should be very close to the Time field though they won't be exact due to GPS lag and how you have auto pause configured. If auto pause is off and manual pause is not used at stops this can be useful data since it will be very different from the Time field.
Elapsed Time: The total amount of time from when you start an activity to when it is ended, including any time spent in auto or manual pauses. Elapsed time is never used to calculate a speed or pace since I think Garmin assumes when people pause they don't want that included in their speed (i.e. time spent waiting at a stoplight).

It looks like those speeds are actually using the correct fields, it's just they are inverted for some reason. I'm not sure why it does that for you, I have never had that issue and I use auto pause, maybe it's a bug with your specific device. Your average speed should not be the same as your buddy's since with auto pause on elapsed time will be the same but that is not used to calculate speed at all.

And if the only reason you use auto pause is to save battery and not to exclude time at stops you can probably turn it off without hurting battery life. I can't speak for all Garmin devices, but any of the ones I've used still keep the GPS running and all sensors active during auto pause, it just stops the timer, so it doesn't save any battery at all.

I hope this helps, if you can somehow get that flipping moving time and time figured out then it should work for you.

First of all, thank you for the response.
But I was not able to understand the difference you explained between TIME and Elapsed Time as you said.
"Time: how much time is recorded when the timer is running". What timer?
"Elapsed Time: The total amount of time from when you start an activity to when it is ended". ok, that I understand.
Actually if you see my buddy´s activity, TIME and Elapsed Time are exact the same.
I just start an activity ... and Conducting an activity they both are the same, don´t they?
So, my question remains: What is TIME?
On regarding the auto-pause I can assure you it saves battery once the "data RECORDING processes itself consumes battery.
A matter of fact someone has already published total battery time depending on the recording interval .


[TABLE="width: 1"]
[TR]
[TD] 7.5
[/TD]
[TD] MostOften
[/TD]
[/TR]
[TR]
[TD] 15
[/TD]
[TD] MoreOften
[/TD]
[/TR]
[TR]
[TD] 25
[/TD]
[TD] Normal
[/TD]
[/TR]
[TR]
[TD] 35
[/TD]
[TD] LessOften
[/TD]
[/TR]
[TR]
[TD] 50
[/TD]
[TD] LeastOften

[/TD]
[/TR]
[/TABLE]


Regards,

Yes, if you start an activity and do not pause the watch in any way time and elapsed time will be the same. Time is all time spent doing an activity while the timer is running, so not auto or manually paused. Elapsed time is how much total time passed on the clock regardless of pauses, so if you took the time of day when you started and ended the activity and calculated the difference that would be elapsed time. Elapsed time is like a clock that you can't pause and time is more like a stopwatch that you can. For example, many runners will pause their watch, either manually or using auto pause, at intersections when they have to wait so that the waiting time spent doing nothing is excluded from the pace calculations.

Thanks for the info on auto pause, never knew that.

So let's see:

ELAPSED TIME: activity's period regardless any kind of pause. Period between the time of day when you started and ended the activity.
MOV. TIME: activity's period when in movement. (Regardless any kind of pause?, case in which if no pause at all Time might be bigger than mov. time)
Time: activity's period, moving or not, minus paused period, auto or not.
Is that it?

Regards,

That's right, though I believe moving time is also off during pauses, not 100% sure on that one since I only ever pause when I'm not moving.