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

Moving Time Wrong Suddenly

Former Member over 9 years ago

The last 2 rides I have done (Yesterday & Today 4th July 2016) seem to be displaying differently in Garmin Connect and I don't know why.

For years now the Elapsed time is as it suggests and moving time just the time you were actually going along. So stopped at traffic lights or the café then moving time stops. The last two rides the moving time is the same as elapsed time and Time showing time in the saddle.

I know the auto pause is still working as it shows me every time I stop and start and my average speed is calculated properly.

I have Strava Connected so uploads to Strava are automatic and they appear correct on there.

Anyone else seeing this?

0 Darter2 over 8 years ago

At the bottom of the Garmin Connect web page it states the current version is 3.8.1.1. Could it be that June 29, 2016 was the implementation date and that rolling back to version 3.8.1.0 would solve the problem?

You would think!

0 alit1881 over 8 years ago

I'm at the point I am tired of waiting for Garmin. It has been one month now and you would think it would be a simple enough issue that can be fixed quickly. I want my data to be good. Not practical for everyone but I track my rides with RideWithGPS as well and their moving time calculation is on par with Garmin's.

yes i rode today ,i was actually away for over six hours

garmin connect shows
Accumulative 5.14 mins
time 5.14 mins
moving time 6.18

tue data is
Accumulative time 6.18
time 5.16 give or take a minute normally
moving time 5.14 as this was my actuall riding time.

spoke to garmin today who are aware of issue but no time scale to putting problem right.

the question is why have an expensive data colection device thats works perfect and uploadable to enable the data to be analysed when garmin connect basically jumbles everything u,p the data collected today shows me completing ride of 81.2 miles at a rate of average speed of 11.3 average mph actually it almost 16.average mph . so how good is garmin connect at calculing data currently not as good as an abacus (a frame of diffferent coloured beadds used to calcuate sums of data chinese i think) come on garmin i know is summer but please get your finger out. and sort it out.

0 Former Member over 8 years ago

Fixed?

Auto pause is set on my Garmin 510. This morning I rode a bit over 40 miles. The ride was uploaded using the mobile app. It appears that the problem is fixed!

0 Former Member over 8 years ago

It appears that the problem is fixed. (7/28/2016) With auto-pause set on my Edge 510 the Ride speed/time was very close to Moving speed/time.

0 Former Member over 8 years ago

You would think someone earning the money would have thought of roll back to previous

At the bottom of the Garmin Connect web page it states the current version is 3.8.1.1. Could it be that June 29, 2016 was the implementation date and that rolling back to version 3.8.1.0 would solve the problem?

Exactly a simple and easy fix. They could even give it a new number so it looked like somebody fixed this mess.

0 Tpcorr over 8 years ago

Glad they finally fixed it. I'll be able to check later this weekend when I ride my bike. They apparently did not fix the issue for previously downloaded workouts. How hard could that be to do?

0 Former Member over 8 years ago

We appreciate the discussion, and thank you Wayne_P for posting the screenshot.

There was a small back-end Garmin Connect update that was released yesterday afternoon (Central Time) that address this issue of the Moving Time displaying incorrectly. The expectation is that any new activity uploaded will not exhibit this issue.

We are waiting to hear back from the Garmin Connect teams regarding any automatic fixes of the previously uploaded data. We will update this thread when more information is available.

0 Darter2 over 8 years ago

We appreciate the discussion, and thank you Wayne_P for posting the screenshot.

There was a small back-end Garmin Connect update that was released yesterday afternoon (Central Time) that address this issue of the Moving Time displaying incorrectly. The expectation is that any new activity uploaded will not exhibit this issue.

We are waiting to hear back from the Garmin Connect teams regarding any automatic fixes of the previously uploaded data. We will update this thread when more information is available.

I noticed the fix after doing a ride Saturday and this morning. I really hope they can do something with our previous uploaded data. But thank you for getting back to all of us.

0 marcossaad_ over 8 years ago

We appreciate the discussion, and thank you Wayne_P for posting the screenshot.

There was a small back-end Garmin Connect update that was released yesterday afternoon (Central Time) that address this issue of the Moving Time displaying incorrectly. The expectation is that any new activity uploaded will not exhibit this issue.

We are waiting to hear back from the Garmin Connect teams regarding any automatic fixes of the previously uploaded data. We will update this thread when more information is available.

Bug still there...
Activity uploaded yesterday July 30th show wrong mov time.
https://connect.garmin.com/modern/activity/1280615542

Time 2:43:45

Moving Time 4:18:09

Elapsed Time 5:12:24

0 Tpcorr over 8 years ago

It's fixed for me. I'm in the U.S. Maybe it's a regional thing?

https://connect.garmin.com/modern/activity/1281778495