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

Edge 830 Bluetooth connection busy when more BLT traffic, but no problem for Forerunner 945?

f|33tStA
over 4 years ago

yesterday i found something interesting, the BLT connection can go busy when other BLT devices are transmitting data, but why it's only a prob for the Edge 830 and not for the Forerunner 945?

My Jabra 65 earbuds connected to my mobile phone (both Bluetooth 5.0) during a run with my Forerunner 945, Garmin Connect Android tells me over BLT my heartrate every minute while i am listening music from Amazon with the phone App, no probs at all and working fantastic.
When i arrived at home my run already synced correctly via BLT!

to update my Physio True Up Trainings Load i started my Edge 830 and i see on Garmin Connect Android as connected, but it was impossible to sync, got always errors.

As soon, as i stopped my music and switched off my earbuds the sync of Edge starts working!

So i don't understand why the Foreruner have no probs?

i think Garmin have to look on the ANT/BT/BLE driver and do the same on Edge 830, or?

ANT/BT/BLE Forerunner 945 5.04

and do nearly the same on Edge 830, or?

  • 0 over 4 years ago

    Sounds more like your Android phone ran out of BT connections; when you turned off your earbuds you released one of those connections which the Edge then picked up.   

  • 0 over 4 years ago in reply to et01267

    i think not, i cross checked it with powered off Forerunner, same thing, my mobile phone have BLT 5.0 so there isn't a prob becuase the protocol can handle more and faster the data, the bottleneck is on Edge BLT 

  • 0 over 4 years ago in reply to f|33tStA

    Let me make sure I understand the setup. 

    1. You have some number of devices (watch, earbuds, etc) connected via BT to your PHONE.   
    2. Your Edge 830 is powered off. 
    3. You turn on your Edge -- the Garmin Connect app on the phone shows the Edge is connected, but you can't sync.
    4. You turn off the earbuds.
    5. The Edge can sync.

    So you didn't have anything else connected to the Edge, all you did was disable the connection between the Phone and the Earbuds.  How can this somehow be a problem with the Edge?   

    I might be convinced that there is a problem with Android -- 4.3 can support a max of 4 BT connections, 4.4 and higher theoretically 7, and BLE is *theoretically* more.  Or there might be a problem with the Connect app.

    In any case, why isn't your Edge syncing whatever via WiFI ?  I basically never use Connect (phone or web) for anything since the device syncs to Strava, gets software updates, routes, etc all via WiFi.

  • 0 over 4 years ago in reply to et01267

    You understand the steps correct, but when my FR945 is off, my earbuds on and edge is on, but couldn't sync and i power on my FR945 and it syncs without a problem, then the BLT on Edge must be wrong.

    i disabled WLAN on Edge, cause during the betas before 5.50 i had a problem, the vo2max wasn't synced, so Garmin told me to disable WLAN and since then vo2max sync works.
    I didn't know, if it is fixed in 5.50 but i don't want to test without a confirmation of Garmin!

    Think, there isn't a prob with my phone One plus 6 on Android 10 with BLT 5, it works greta with all other things, only in this case with Edge i can replicate the prob

  • 0 over 4 years ago in reply to f|33tStA

    I just tested my Edge 830, FR935, F5plus, and BBfit headphones all connected to my Moto Z3 Play.  All three Garmin devices were able to sync while listening to music from the phone to the headphones.  To make sure the 830 did actually sync, I pushed a new course to the device from Garmin Connect Web prior to starting the sync.

    Since my Edge 830 received the new course, I am confident that the Edge 830 did sync with all the other BT connections active.

    I too would suspect the phone in this case.

  • 0 over 4 years ago in reply to sabeard

    sorry, for my late answer, wa on holiday, it look like i haven't this prob anymore, possible that during my tests the Garmin Connect Servers where busy