Dariusz Seweryn

There are two things: 1. The OS limits 2. The actual Bluetooth Chip limits — there are numerous Bluetooth Chip manufacturers there and capabilities of the chips and firmwares that...

Hello @fonix232 Thank you for using the library. > This is a quite annoying oversight that has not been fixed for the past two years, and doesn't even require that...

> I agree that on lower level APIs, the emulation of these properties (via manual filtering after the system returns the results?) would be the way to go - although...

`RxBleScanResult.getBleDevice().getBluetoothDevice()`

Version `1.3.0-SNAPSHOT` is no longer closing the `RxBleConnection` if an error happens during a connection operation (i.e. `RxBleConnection.characteristicRead`) which allows for a retry which may succeed as Android is sometimes...

Thank you @lorenzowoodridge Thing is that there is a tone of bugs on Android OS regarding bonding BLE devices. I have tried to bond Android 7.1.2 with Android 4.4 /...

Hello @RobLewis From what I know you are correct with the difference between `pairing` and `bonding`. @uKL is also right saying that BLE does not require pairing/bonding to communicate (as...

You may retrieve the `BluetoothGattCharacteristic` and set the write type appropriately.

Hello, This looks like an [Android API bug](https://stackoverflow.com/questions/32363931/bluetoothgatt-returns-empty-service-list-after-connection). While it is possible for the library to introduce some mitigations (i.e. retrying the discovery process in this situation) they are likely...

Currently retry would need to be implemented in a `RxBleCustomOperation` on the `RxBleConnection.queue()` function as the internal logic treats an empty list of services as a valid result and caches...