In the case of unsuccessful Bluetooth connection, actively disconnect without executing context. unregisterReceiver (receiver); At this point, there may be multiple Bluetooth broadcast registrarReceivers, which may crash on some Huawei phones due to a broadcast limit of approximately 1000. Suggest fixing this issue.

[stylsw]

After calling establishConnection, it was found that the context. registerReceiver (receiver, new IntentFilter (BluetoothAdapter. ACTION_STATE.CHANGED) in RxBleAdapterState Observable) would be triggered;

In the case of a successful Bluetooth connection, actively disconnecting through dispose will execute context. unregisterReceiver (receiver);

If the Bluetooth connection is not successful at this time, actively disconnect through dispose without executing context. unregisterReceiver (receiver); At this point, there may be multiple Bluetooth broadcast registrarReceivers, which may crash on some Huawei phones due to a broadcast limit of approximately 1000. Suggest fixing this issue

[dariuszseweryn]

Hello,
Thanks for using the library and for the report. Could you provide a step by step reproduction scenario and some logs that support the case so I could act? A memory dump showing leaks could also be useful. Thanks!

[stylsw]

Hello, you can use a fake device to execute the establishConnection method, then perform a dispose operation before the connection is unsuccessful, and log before the unregisterReceiver of RxBleAdapterState Observable. You will find that the unregisterReceiver execution has not been triggered. This is a must see scenario.