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

TIME not syncing

Former Member over 6 years ago

So I turned my vívofit 4 on for the first time around 6pm the day before Thanksgiving. So now my device resets at 6pm and sees it as midnight. My watch part shows the accurate time and date but all my activities reset at 6pm.

For instance, I went to the gym at 6am yesterday and according to the times on the app it saw it as noon.

So so if I go to sleep at 10pm when I look at my sleep log it shows that I went to sleep at 4am. It’s getting confusing and I don’t know how to fix it. I have reset my band. Reinstalled the app. And my phone is set to the right time. And like I said my display shows the accurate time and date.

0 Garmin-Kara over 6 years ago

This may be related to another issue we are currently tracking. We do have a temporary workaround while we investigate this issue:

1. Change the time zone on your phone (in the phone's general settings) to any other time zone.
2. Sync the watch (Garmin Connect Mobile sync or PC (Garmin Express sync) . This should result in the watch showing the new time zone.
3. Change the time zone back and sync again. This should fix both the watch time and the time reported for the activity tracking data.

The data should go back to normal the NEXT day.

I will update this thread once we have a resolution this issue.

0 Former Member over 6 years ago

Same issue on Vivosmart 4. Any updates by chance?

0 Garmin-Kara over 6 years ago

We have release a new software update for this issue. Please sync your device with Garmin Express or Garmin Connect Mobile to allow the update to install. The latest software version is 2.70. If you are still experiencing this issue after the update software, please contact your local Product Support.

0 Former Member over 6 years ago

Note- I received a replacement, and software already updated to 2.70. The time inaccuracies described in original post were still present. The solution also posted up above, however, did work.