Bonding/Pairing Issues

Hello @all,

There are known issues with bonding devices on Android BT, those are mentioned herehttps://github.com/iDevicesInc/SweetBlue/wiki/Android-BLE-Issues(please note these are all general Android BT problems we have to worry about, not the “SweetBlue” library problems). In particular those are the problems regarding bonding:

Bonding/Pairing Issues
• Encrypted characteristics cause a whole host of issues around bonding state on some devices.
• If you try to read or write an encrypted characteristic and you're not bonded (even if the API says you’re bonded), the characteristic operation can silently fail and implicitly kick off a bonding operation without retrying the operation. Sometimes it does automatically retry the operation though. Managing this is a huge headache.
• Bonding state on some Android devices can’t be reused across multiple connection sessions. Every time you reconnect you have to clear bonding state programmatically and re-bond.
一些电话,即LG G4和三星S6,哈哈ve subjective issues with bonding if you try to use the public BluetoothDevice.createBond() method. Instead you should use a private equivalent that must be called through reflection that forces low-energy transport mode.

This can was confirmed by us yesterday as for example HTC M8 (which I experienced in LocationApp and Gtag1App a device with quite well implemented BT) could not bond to SmartTag2 at all (other device, Smasung S5 could do that easily). This will also lead to UI complication and redesign as we have to deal with this, new to us, flow with pairing a.k.a. bonding:.

Are there any solutions available or known?