You can no longer post new replies to this discussion. If you have a question you can start a new discussion
Why is 'paused time' now included in activity?
Former Member
After a recent update to Garmin Connect, it now includes time when I have paused my 305, I am not interested in the time included in my coffee stop, and it skews the rest of my data, nor do I want to make it two or more routes. If I ride for an hour, have a 5 min stop, ride another hour, I have ridden 2 hours, not 2:05. Infuriating as it did not do this before. Time to change App?
Thanks for that, I have now seen the many threads on this, and from the sticky it has been known for some time. Glad that it was easy to find that somebody was on the case.
I have same issue; by last two (02-22-2014, 03-02-2014) transfers activities from 405 to Garmin Connect app I have noticed differences in avg pace time and time calculation.
Datas on device are correct but on app are wrong. Is this related to time issues from recent update?
What should I do when this will be fixed? Will datas will be fixed automatically or should I do another upload and how?
This problem seems to be related to Garmin Connect and not to users devices or the firmware on them.
It is fairly likely that nobody outside of Garmin knows what they will do to fix this. It is possible that they will fix the problem and re-scan all activities uploaded in the last month and the problem will just vanish. It is also possible that you would have to upload your activities again. If it comes to that, you just have to locate your .fit files (their location depends on which platform and client software you are using) upload them manually via the upload page.
Original problem now fixed, down side is my ride/run stops when I pause the device, even though after the pause distance and everything works the overall time of the activity stops at the first time you pause the session. This means the stats on Connect are pretty useless. What happened to old adage, if it is not broke don't fix it, or before you role out an update, how about testing it...
