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

Garmin Connect Mobile 2.7.3 problems with Vivofit sync to Galaxy S3 Android 4.3

I allowed my Samsung Galaxy S3 to update Garmin Connect to 2.7.3 last week, and since then I have had major problems syncing my Vivovit. Prior to the update it would usually sync fine although occasionally I might have to turn Bluetooth off and back on before it would work. Now it NEVER works the first time, and I have only been able to get it to work by rebooting the phone. Another new "feature" with GC 2.7.3 update is that if I turn Bluetooth off and back on, now the Garmin Connect app hangs completely and I have to kill it from the task manager. Last night it finally synced but it failed again this morning. It's not worth my time to spend a half hour every day trying to sync the crazy thing. Does anyone out there have any tips to make this work better? Can I update to an older Garmin Connect app version so it will at least work as well as it used to?

Thanks!

Sync log output below:
---Username / User Displayname---
davelsmith / davelsmith

---GCM App Version---
2.7.3

---Timestamp---
Sat, Jan 10 2015 @ 7:30 AM

---Garmin Device Info---
[device information] unit id: 3884646796, bluetooth friendly name: vívofit, product number: 1837, software version: 360, device name: vívofit, device model name:

---Android Device Info---
Ver. Release: 4.3
Ver. SDK: 18
Ver. Codename: REL
Locale: en_US
Manufacturer: samsung
Brand: samsung
Model: SGH-T999
Device: d2tmo
Display: JSS15J.T999UVUENC2
Fingerprint: samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUENC2:user/release-keys
Hardware: qcom
Host: R0210-18
ID: JSS15J
Product: d2tmo
Radio: T999UVUENC2
Serial: 3cb12464
Tags: release-keys
Type: user
User: se.infra
Board: MSM8960
Bootloader: T999UVUENC2
CPU 1: armeabi-v7a
CPU 2: armeabi

---Sync Info---
******************** SYNC RESULT ********************
Upload Status=FAILED [Failed uploading file (3884646796_6_8020.tmp). Reason=500.]
Download Status=FAILED [Unable to complete operation: Remote device disconnected [3884646796]]
Time Sync Status=FAILED [Remote device disconnected]
Overall Sync Status=FAILED
*****************************************************
SYNC#DeviceSyncUpload:
LISTED { listed=2813ms }
- 6 (80/MONITORING_B/1731B): POSTING FAILED [Failed uploading file (3884646796_6_8020.tmp). Reason=500.] { extracted=6515ms posting=124275ms }
- 7: not processed
- 8: not processed

#Auto Upload=true
#Types=[32] | [FIT_TYPE_32, FIT_TYPE_4]
*****************************************************
SYNC#DeviceSyncDownload:
BROWSED (No item to process; No downloadable items supported by this remote device, download bit mask: 4870) { browsed=8355ms }
BROWSED FAILED [Unable to complete operation: Remote device disconnected [3884646796]] { browsed=139202ms }

#BitMask=4870
  • Former Member
    0 Former Member over 10 years ago
    ******************** SYNC RESULT ********************
    Upload Status=FAILED [Failed uploading file (3884646796_6_8020.tmp). Reason=500.]
    Download Status=FAILED [Unable to complete operation: Remote device disconnected [3884646796]]
    Time Sync Status=FAILED [Remote device disconnected]
    Overall Sync Status=FAILED

    Thanks for posting your audit! The reason sync failed is due to the 500 code returned from the Garmin Connect server while sending your data from the app. The Connect servers were pretty much hammered over the holidays with uploads. We apologize. They're much more stable now, although I cannot say there will not be further hiccups. Here's a server status page: http://connect.garmin.com/en-US/status. The syncing is in order. First uploads from your vivofit to Garmin Connect, then downloads from Connect to your vivofit. The upload must succeed, in order for the download to start. That's why you see "fail" for download status too.