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

Activity Time wrong with no way to correct it?

Former Member
Former Member
I used my Garmin Forerunner 235 early in the morning, It was switched off before training.
I turned it on and made sure it synced with Garmin connect on my phone before starting the activity.

The time is wrong after syncing again:mad:, it shows 107:01:21 instead of 1 hour 20 minutes, the actual time it took.

  • While it is the individual user's prerogative to leave a Forerunner‑235 switched off in between timed activities, despite the known issues of the watch losing its clock time, and possibly consuming (or losing) more battery power than leaving the watch switched on always…

    The time is wrong after syncing again:mad:
    …how many times do people have to be told that syncing does not adjust the clock time on the watch, but that – as clearly stated in the Owner's Manual, and brought up in various discussions threads in this forum time and time again – it is set automatically by GPS location, after the watch has acquired satellite signals?

    The clock on the mobile phone or tablet device is not regarded as an authoritative information source for the time-of-day. Even if the handset is a ‘Jesus phone’. Even if it would be more convenient for the user to simply accept the phone's clock time with a lesser degree of confidence, than to go outside. Even if this tidbit is contrary to the user's beliefs about how consumer IT works, and forces the user to actually do some reading (instead of being all-output-and-no-input), find out what the manufacturer as the authoritative information source said about the device, and dismiss his/her assumptions and correct his/her misperceptions.
  • Former Member
    0 Former Member over 8 years ago
    @AlfredKidd,

    Based on the picture it looks like you are experiencing an issue that Garmin Connect is currently experiencing where the Moving Time for the activity is displaying greater than the overall Time for the activity. This is an issue that has been escalated to the Garmin Connect team and a fix is expected soon.

    We apologize for any inconvenience in the mean time. There is also more discussion on this issue in this thread: https://forums.garmin.com/showthread.php?355419-Moving-Time-Wrong-Suddenly
  • If i may highjack this thread a little bit with an activity minutes question.

    this morning i synced both my Fnix 3 HR and my Edge 1000 because i saw that they are set for english miles instead of km, (with dont seems to change even if i change and then save and then sync.

    anyway, since then i now have 66164 intense minutes in the last 2 days (yeah ive been biking quite alot, but not that much!) and i dont know how to change it.
  • Former Member
    0 Former Member over 8 years ago
    @ASmugDill you are not helping at all, it feels more like a personal attack on me as a person than solving a bug in the system. Thank you!

    @GFM1011, that is great news, I'm glad you are already working on it, If I find anything else I will report it to help you improve the product.
  • @ASmugDill you are not helping at all, it feels more like a personal attack on me as a person than solving a bug in the system. Thank you!
    That syncing with your phone does not set the time on the Garmin device is not a bug. I hope you now understand you misperception about that particular aspect, and take steps to correct it and recalibrate your expectations for your own benefit; that's the only help that other users can render. We can't (and have no reason to want to) alter the design to more closely match what you expect or prefer, but you can change yourself to suit the status quo.
  • Former Member
    0 Former Member over 8 years ago
    The bug has nothing to do with what you are saying, I did see the time sync when I got a GPS fix just before the activity, but after that the Moving Time for the activity displaying greater than the overall Time for the activity, that is the bug we are talking about! maybe YOU should read a bit better.