The time calculation issue is reported as fixed. It's different all right but not fixed. I uploaded my runs from the last two days and I'm showing a pace of 2:47/km. I'm fast, but not that fast ;)
Same thing here. I reloaded runs three times and it gave different times each time. How hard can this be. The data should be a direct transfer. This is from a 305. Interesting that Garmin can't even figure out it's own eight year old technology. What's wrong with these people.
There still seems to be a problem. The final time on my Forerunner 405 watch (38:05.17) doesn't match the final time uploaded to Garmin Connect (38:07). The total split times off my watch (38:06.62) match the Garmin Connect finish time uploaded except for some rounding that they do for some reason.
On a different run my watch recorded 44:27.63 which matched my split times exactly, but Garmin Connect is displaying 44:26.
Same issue here. There needs to be some QC improvements at Garmin. How tough is it to actually check these calculations first prior to uploading the new release? It sure gives the impression the 1st year co-op student is in charge of the website.
I just figured out what it's doing. If you pause during your workout it stops the time right there. I usually pause for about a minute at the halfway point and the total duration of my workouts match the halfway mark. The previous bug took into account the pauses, now it just stops counting at the pause.
I agree that it could have been tested better. Now let's hope it doesn't take another 3 weeks to fix this. At some point we won't be able to re-upload. There's only so much data that can be stored on the watch.
Completely agree this is still very much an issue. It's just wrongly calculated the time in a different way than before - LOL! I ran 3 miles today and right at the beginning of my run my watch auto-paused for a second. So despite running 3 miles in 29:56 (elapsed time), on garmin connect my time is showing as 5 seconds, Avg. pace .02 min/mile. Really?! Why is Garmin not checking that their fixes actually work before posting them? This is getting really frustrating.
My runs outside are now working so that times on the watch match the upload to Connect and any paused time is being correctly accounted for. Re uploading old runs also fixes those that were previously incorrect. However, I use a foot pod for distance when on the treadmill and these are not uploading correctly. This morning I did 4 miles in just over 5 minutes! Total elapsed time is correct but the calculation for pace appears to being performed on the paused time or active time does not continue to be registered after any pause has taken place. Very frustrating. The error has changed from counting all time as active to only now counting a small amount of time which is far less than the actual time you were active for.
+1 for pauses resulting in the end of time recording on some run. Some of the incorrect time runs were corrected once the recent "fix" was put in place, but other activities were made much worse.
See splits for one of the runs which stops tracking moving time after first auto-pause of the run:
In addition activities entered manually were affected during this time, not just .tcx uploads. I enter swim workouts manually and the during this whole fiasco Connect has been recalculating distances I enter manually and changing time/100 yard metrics.
Agh. Having same issue with 405. Of course, it had to be the day i did my speed intervals so I can't look at the graph, because mine stops at 16:45 even though I ran a full hour. It also changed runs that were already uploaded (changed those to 16:45 also) as the elapsed time. C'mon Garmin people pull it together.
I just figured out what it's doing. If you pause during your workout it stops the time right there. I usually pause for about a minute at the halfway point and the total duration of my workouts match the halfway mark. The previous bug took into account the pauses, now it just stops counting at the pause.
I agree that it could have been tested better. Now let's hope it doesn't take another 3 weeks to fix this. At some point we won't be able to re-upload. There's only so much data that can be stored on the watch.
Guy
that is exactly what it's doing, I stopped my timer waiting for a train to pass today and that was the end time of my activity duration (even though I kept going for a while after that)
distance was correct, splits were correct, just overall time was really screwed up
hopefully someone at garmin notices what you mentioned
