HI i have a vivosmart 4 and when i look in my garmin connect account since 4th march only a few odd days data is there. It has been working well before 4th march. I manually sync using a usb cable so how often is it recommended that i should sync?
HI i have a vivosmart 4 and when i look in my garmin connect account since 4th march only a few odd days data is there. It has been working well before 4th march. I manually sync using a usb cable so how often is it recommended that i should sync?
In theory you shouldn't lose data but stuff happens and you're not the first to raise this issue. I actually sync multiple times a day but if that's not possible, try to sync once per day.
If you're wondering what "stuff" means, even though it shouldn't, it could be a firmware update that occasionally can affect data or even a crash that can wipe out data. Even the change to DST can have an effect.
Thanks, i will try and sync more often and see what happens. I didn't sync yesterday but have done this morning and it didn't bring across the steps from yesterday but it did bring across the sleep stuff. My steps from this morning did come across though. I am wondering if l should reset the device and see what happens. I do remember having problems with the last upgrade and it kept on saying that it couldn't find the device when it was plugged in. Maybe something has gone wrong there.
I have been going back and forth with garmin support about this for over a month and it appears the problem is with garmin express version 6.20. There is a support ticket open for this issue since other people have reported it. Here are your options:
1. Sync daily, late in the day, and make sure you go to bed after midnight (yes I know stupid idea);
2. Manually import all your data from the watch using connect. The data is still in the watch although connect is not bringing it across during a sync. Seems to work fine except for a hiccup on the end of week sundays;
3. Downgrade to express version 6.16, all your problems will go away. I am still running 6.16 on one of my computers and that's how I identified the problem.