Dariusz Seweryn

I have not encountered the issue you are describing. I successfully tested connections that spanned ~3 days (over a weekend). There are known issues with Android BLE stack that has...

> old phones with android 7 are failing to close the connections I haven't noticed this before — how can you tell that they are failing to close connections?

The library is _always_ calling `BluetoothGatt.close()` when ending the connection `BleAlreadyConnectedException` Javadoc: ``` /** * An exception being emitted from an {@link io.reactivex.Observable} returned by the function * {@link com.polidea.rxandroidble2.RxBleDevice#establishConnection(boolean)}...

Android has its limits of how many connections it can handle at any given time. Search for `BluetoothGatt` limitations on different API levels. It was ~4 at API 18, 7...

Ideally between scanning and connecting to the device there should be ~0.5 second delay. This was observed to help. There is also a known issue (race condition) on Android in...

Unfortunately I do not know how could I help you further with this issue. This looks like an Android OS BLE stack problem and I do not know any further...

[There was an issue with how many Bluetooth Devices cache entries an Android device may handle](https://issuetracker.google.com/issues/37068528#comment21). This could explain some of the issues @SmartShepherdUser has faced.

From what I know it is currently max 13 connections per system (since 9.0 prior to it it was 7). [Source](https://stackoverflow.com/questions/41365009/what-is-the-max-concurrent-ble-connections-android-m-can-have). There is an additional restriction in maximum `BluetoothGatt` objects...

Though it seems to be quite away from the original topic — that is some interesting idea. I will extract it as a separate issue. I have quite a lot...

I wanted to play around with other stuff (like encryption and binding) which I do not have a lot to do before going to `RxJava 2` because of the opportunity...