BLE Direct Messaging Bug

Former Member over 9 years ago

Hi All,

Hope I can get some help from someone with more experience or the Garmin team:

Many times, after bluetooth loses connection (due to range) and then re-establishes the connection, when using Toybox.Communications.transmit(), the ConnectionListener returns with onError(), and the message doesn't go through.

Sadly this doesn't sort itself out and only returns to normal after switching the bluetooth connection off and then on again several times manually through the Settings menu.

Any ideas?

I've been struggling with this for some time, thinking the blame was on my Android app, but now I'm pretty sure the fault rests with the Garmin Connect infrastructure.

Thanks!

Brandon.ConnectIQ over 9 years ago

Hi Ran2000,

Apologies for not getting back to you sooner. Sometimes these threads can get missed accidentally, so don't be afraid to bump the thread if you don't get a response within a day or two.

I've been working to reproduce this issue with our Comm sample (and companion Android mobile app), and so far I haven't seen the problem. The comm sample allows me to send strings from my watch to my phone (and vice-versa). I've simply been pairing the watch and I start sending strings from the watch while walking out of range. I'm walking quite far away, and then returning to the phone, where I am able to successfully send a transmit message to the phone. I see several failures while I'm out of range, but things start working again once I'm back in range.

I also tried turning Bluetooth off on the phone to see if that would get me into a state similar to what you've seen, but that never caused me any trouble, either.

There are a few variables here that may be involved:

1. The Garmin device and firmware version
2. The Connect IQ app
3. The Garmin Connect Mobile version
4. The mobile app
5. The Android hardware and OS version

I've been testing on a vivoactive with a Samsung Galaxy S4 on Android v4.4.4 (KitKat). Can you provide me with some more information about your configuration and describe whether there is something specific that you must do to reproduce the issue?