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

Ride upload issue while connected to WiFI and Bluetooth

 I’ve noticed that with WiFi and Bluetooth enabled if I get home from a ride the Garmin does not auto upload and shows sync failed. If I end my ride while riding home before I’m in range of my home WiFi the ride will upload without an issue. I assume that there is a problem uploading while connected to my home WiFi and connected to my iPhone. Anyone else seen this issue? I assume my work around is to just turn off WiFi..

  • I should mention that I don't carry my phone with me on my rides.  I wear an Apple Watch.  So I finish my ride when the phone is within BT range.  On the 520 the BT connection works like a charm without me touching the phone upon the finish of my rides.  So perhaps others are not seeing the same issue as me because their phones are connected to their Edge units during the entire ride?

  • I'm still having the same issue however I just checked my iPhone and noticed GC 4.19.1.1 is now available.  I just downloaded it and will see if my problem persists tomorrow after the ride.

  • With GC 4.19.1.1 my BLE connection problem persisted.  I manually opened the GC app. and my 830 connected but the ride upload failed as I got the dreaded 'upload failed' message.  I was busy trying to get the ride uploaded while my riding buddy who has the Wahoo Bolt finished packing his bike in the car.  I was so embarrassed.  After much trial and error the ride finally got uploaded.

  • Had my 530 couple weeks now. Can confirm bluetooth is completely broken! Multiple on/off cycles, sync from GC, upload ride from 530 history all routinely fail.

    I've found pressing upload ride from 530 history is the least frustrating as it only takes half dozen attempts to work. Garmin really need fix this nonsense...

  • We “upgraded” from 510’s to 530’s. Now we have two 530’s, two iPhone XR’s, and daily connection problems. We do “forget device” and start over all the time. Most uploads fail. But our iPhones connect perfectly with all other devices. The phones are flawless. Garmin should not be selling their beta software to the public. 

  • I’ve upgraded from an 810 to an 830 and have the same issues. Occasionally my 810 wouldn’t connect to BT but the 830 is dreadful. I find that it hardly ever connects the first time I turn the device on. Turning off and on will normally connect. I’ve factory reset several times and cleared all settings from the iPhone and it makes no difference. 

  • The new Public Beta has a fix for Bluetooth communication. You can find the details about how to install and change log here.

  • Dear all,

    i got the same problem. Everything looks fine but manual sync from Connect App fails with “Your device seems to be busy, and your sync request timed out. Try again later”

    Any idea what I should do now?

    1. sign out and sign in again from the connect
    2. Synced with Garmin express via usb
    3. I ve installed beta firmware 3.33

    i got my new assigned track synced via Garmin express but why does the sync between the connect app and the edge device not work any more. 

    Thanks

    Andre

  • I'm having the same exact problem.  reset both phone and gamin 530.  says device is busy.  Only connected to Bluetooth.

  • Hi,

    I have a similar issue but not only that. Already made the beta installation but the problem persist.

    All goes well when I make a fresh pair between the two units and maybe one or more two uses without any problem, but then the connection between my smartphone and garmin edge 530 stop pairing.

    This happen with bluetooth on only or with both wi-fi and bluetooth on. Sometimes it pairs after mid ride but normally doesn't anymore. Says on garmin is trying to pair with my Xiaomi Mi A2 but never does so.

    If I reset the pair it all goes well again for more two or three uses...

    Isn't for sure a problem of the phone, because I have tested with different devices and previous with my garmin edge 520 plus and I never had this problem...

    Best Regards

    Nuno