- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Sometimes after connecting a smartphone to the BT-Module, the Module can't find the connected peer (__find_bonded_peer).
Most times a re-pairing will fix it, but not always.
I tried with "Maximum Bonded Devices" and without.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
At the moment im on another bug, but that seems to be solved.
Of course i'm checking about that problem if it occurres.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which Smartphone?
Which version of the OS on the Smartphone?
There are some issues with iOS 8.2 and Bluetooth.
Are you trying to use Passkey pairing?
Whats the connection interval?
Which app are you using from the SDK to run the tests?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The smartphone as Samsung Galaxy S4 mini with Android 4.4.
Yes, I'm using Passkey pairing.
The module will send new data on every second.
The app based on the sample of android (BluetoothLeGatt).
It's not always, it comes from time to time. I only tested on time to reconnect, but also no notification. If I removed the device and paired it again, I got the notifications again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had originally thought that this issue was similar to the one reported here:Re: Un-pairing / un-bonding from a BLE sensor device
However, after studying both, I'm not sure any more.
It sounds like what you are saying is that many times, after connecting your Android phone to our 20737S, our module forgets the bonding information and can no longer find the connected peer - and notifications stop.
In most cases re-pairing will fix the issue and notifications continue, but not always.
I will probably need to check with the developers on this one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does your application store client configuration descriptor in the NVRAM after phone writes into it, and restores it after the reconnection. According to the spec the client configuration descriptor for bonded devices needs to be persistent. After reconnection the phone does not need to register for notifications again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think the data shoulb be stored.
Also the Android-App will register for the notifications on every start.
If there are no notifications, closing and starting the app again and the notifications are working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Closing and starting the app can cause registration. I think you need to start looking at the traces.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this still an issue? Any updates? Is this "BT-Module" you have mentioned here the tag3?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
At the moment im on another bug, but that seems to be solved.
Of course i'm checking about that problem if it occurres.