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

New Garmin Connect showing incorrect elapsed time and lap averages

Today was the 1st time I uploaded after the site upgrade (I had done so last Monday and that activity showed just fine). Today's activity elapsed and moving time are incorrect and much higher than what they actually were. The watch's history shows time of 38 mins and a bit. Garmin Connect shows... 42:17 and 42:12, and adding the lap numbers makes no sense.

http://connect.garmin.com/activity/448385332#

The lap times are all in the mid 5s min/km, yet the average shown is 6:02.

Split Time Distance Avg Pace

1 6:06.4 1.00 6:06
2 5:31.0 1.00 5:31
3 5:16.6 1.00 5:17
4 5:16.3 1.00 5:16
5 5:20.9 1.00 5:21
6 5:16.1 1.00 5:16
7 5:12.4 1.00 5:12
8
Summary 42:17.0 7.00 6:02 ->> makes no sense, look at all the 5s above -> 38 mins

I delete the activity and resubmitted, same deal. I know my pace was indeed in the mid to low 5mins/km.

Has anybody else seen this? Any suggestions? Garmin 405.

0 Former Member over 11 years ago

Guys - can you not look at other posts in the forum - there is a sticky post for this 3 from the top of the forum - https://forums.garmin.com/showthread.php?74645-Time-Calculation-Issue

That's not the way the web works. A shoddy product update gets released with not enough testing, so users search for something along the lines of "garmin connect shows wrong time". This thread is the top result, so they post to this thread.

Garmin's entire business model (for the sports range, at least) is predicated on their users' obsession with the quantified self. If a software update quantifies the self incorrectly, then Garmin needs to roll the offending update back in short order, not mess around trying to fix the issue. This issue is a P1 - it's been two weeks since the sticky post you reference. Anyone working for any sort of professional software production outfit should get fired for leaving a P1 in production for two weeks. Not good enough Garmin, please step up your game.

0 KIRKWWHITE over 11 years ago

Same issue here with my 305. Total time of laps actually EXCEEDS elapsed clock time from start of run to end of run, 22 miles over 3:30:00. I stopped watch several times for traffic lights, water drink, etc, and all lap splits look good but the summation of these is close to total time of run INCLUDING all stops, plus another minute. What gives and when fixed??

0 travis.vitek over 11 years ago

https://forums.garmin.com/showthread.php?74645-Time-Calculation-Issue

0 WARDBRADY over 11 years ago

I get it, Garmin knows about the issue.....

but how long are they going to sit around before just fixing the problem, the longer they take, the more people will complain and the more duplicate threads that will exist

I run with a garmin on every run because I care about the data, if the data's wrong.... there's no point to having the device

it's extra maddening because the watch itself collects correct and accurate data, then the website takes creative liberties with your data as it uploads

0 Former Member over 11 years ago

I have the same problem with Forerunner 405 as well. :(
Since the time calculation is correct on GPS watch and exporting a tcx file to other website is correct, it seems the Garmin connect website links the wrong time calculation data.
However, i saw some friends are not suffering the issue.
Garmin was aware of this issue since 2.21, and I'm wondering how long Garmin could solve this problem....:confused:

0 davidarandall over 11 years ago

https://forums.garmin.com/showthread.php?74645-Time-Calculation-Issue

We understand that they know but we all paid hundreds of pounds for a tool that has not been doing the job for a matter of weeks now....I'm glad they know but would like an update about when they expect a resolution. The thread you highlight is closed so we can't ask there.

0 NEELBILLY over 11 years ago

Same issue with a FR 305. Sure do wish they would fix it. I guess I'll have to enter data manually. It's a shame that it isn't fixed yet.

0 Former Member over 11 years ago

I have the same issue with my garmin 305 when cycling. The average moving speed is inaccurate because the moving time does not take into account periods when the 305 is auto paused eg coffee stops. However, the split time for the activity does give the correct moving speed which matches that computed by strava. This fault needs to be fixed - it has only occurred since the "upgrade."

0 ZIRKLEDW over 11 years ago

Exactly the same problem with my forerunner 305. Sloppy.

0 Former Member over 11 years ago

Seriously - I have had this issue since February 16th. I thought for sure it would be resolved by now. C'mon Garmin. At least at update on when you might have it resolved. If can't count on time accuracy, Should I have doubts about distance too?!?!?