Venu 3: after upgrade to 13.17: Wi-Fi Sync shows "Transfer complete (1 file failed)."

Hey there,

I performed the Venu 3 firmware upgrade from 12.12 to 13.17.

After the upgrade, performing "Settings >> System >> Connectivity >> Wi-Fi >> Wifi Sync" shows an error "Transfer complete (1 file failed)." within a red circle.

Activities and other data seeminlgy are synchronized as they do show in Garmin Connect, but still I would like to understand what this failed file message is about and eventually get rid of it.

Thanks for suggestions.

  • Hi...

    Have a Vivoactive 5 which updated to v13.17 last week.

    Other than heavier than expected battery usage, it was working fine before that.

    As soon as that update completed, I noticed that my phone notifications were not coming through... 

    Then I picked up that my device was not syncing to my phone over Bluetooth. It seemed to sync sync fine over WiFi (to my Garmin Connect profile) for a day or two but then that began to fail too.

    Instead, an error code 0500 alert would pop up. 

    I tried all the things... Rebooted the device, rebooted my phone, deleted and reinstalled the app (later on)...

    I made the mistake of removing the device and it refuses to be re-added back to ConnectID... Even my iPad had the same issues (my smartphone is a Samsung).

    Eventually, connecting the Vivoactive 5 to my PC directly, updating the  Garmin Express application, then rebooting my PC (because it Express was not picking me up the Vivoactive 5), and then it finally it seemed to work...

    In that all I was able to re-add the WiFi networks which I could not connect to nor re-add from the Vivoactive itself, from my device and from Garmin Express on PC.

    And now I get the "Transfer failed due to 1 failed" error but I'm grateful it can actually sync again!

    Oh! I updated a bunch of Connect IQ apps and I am seeing a remarkable improvement in the battery life.

    I used to see it start squealing around Day 4 due to it draining energy at 1.5%/hour. But after this update and the IQ apps update, that rate has dropped to about 0.35%/hour.

  • Hello Garmin-Tracy,

    could you share with us some more details, please? For instance, which file it is that fails to be synchronized? What is its content/function? Is there any way I can see what goes wrong in some logging page on the watch itself or in the Garmin Connect app?

    Thank you!

  • I'm still having issues with my Venu 3 after the last update. See Arrow up️ for previous issues. I'm still trying to sync my watch through WiFi and when it does it say transfer in progress then the Garmin connect app shows on my watch then it immediately goes back to the controls menu? I'm not receiving the failed up update like I was a couple weeks ago but I'm not able to sync or answer calls through my watch. 

  • Hi! 

    I'm having the same problem with the WiFi sync... 

    Also my stress graph is deleting it self every day around 13.30. When I sync I still get the data in Garmin connect, but on my watch it's gone. 

    I did a soft reset, deleted all my .fit files and even did a hard reset (including deleting the connect app), but sadly nothing worked.

    The problems all started after I downloaded the new software. Hopefully the problem will be solved soon. 

  • 1. It only notifies incoming calls with a single tone and one vibration. Why?

    I need vibration and sound notification for the whole incoming call until I react or it will be answered or dropped. 

    I understand that this can eat battery , than make it adjustable manually in settings 

    Vibro and Sound notification : 1 time / 5 seconds /10 seconds / 30 seconds etc. 

  • Hello - We are aware of the body battery behavior. Please follow this thread for updates - forums.garmin.com/.../13-17-body-battery-vanished

  • Hi Everyone - 

    This behavior has been resolved, you should be able to use the wi-fi sync option without a problem.

    Thanks!

  • I just tested it and I confirm that the error message is gone. 

    However, I am curious to know whether you just suppress the message now by some server-side configuration or whether the root cause was fixed and the file is being transferred correctly now.