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

Any way to "force" a sync of an activity on Forerunner 220?

Former Member over 10 years ago

I have a Forerunner 220 and an activity from this morning that won't sync - it's like it thinks it already synced. I use Bluetooth to Garmin Connect on my Samsung Galaxy S5. The watch connects, and I can see in Garmin Connect that it connects and says "Sync Complete" within 1 second.
I have rebooted the phone multiple times.
I have turned Bluetooth off and back on on the watch.
I have started and ended another activity on the watch, and watched it sync successfully.
I've unpaired the device and re-paired it.
This one seems to be marked as already synced, and I can't find any way to force it to re-do.
Any help?

0 Dugiflopper over 10 years ago

If you connect it to your computer via the usb cable you could try to "import" it. On the modern GC you do that from the activities listing page. From the old GC you select upload, then look for the "manual upload" link. If your forerunner is like most of the newer Garmin devices, then the activity is in the /Garmin/activities folder.

Typically when an activity doesn't send there might be something wrong with the file. Sometimes it even causes new activities to not upload. If it will not import, then I'd suggest copying it to your computer with it's file explorer (drag and drop) and then delete it from your device. Then you can post that file somewhere as see if a user that has the .fitfilerepair tool will fix it for you.

Anytime you have an issue with syncing files, I'd think the Garmin Express sub-forums would be the better place to post as there are actual Garmin reps answering posts there. Unless of course you use the moblie app, in which case there's a sub-forum for that too.

0 Former Member over 10 years ago

Thanks, I was able to see it in the folder you indicated after connecting via USB. And from there I was able to upload it successfully! Thanks for the info on the sub-forums as well, though hopefully I won't have future issues this path won't resolve.