Suggested way of using connection about rxandroidble HOT 6 CLOSED

In the first block what would happen is:

1. rxBleConnection would be established
2. once the rxBleConnection will be available the readCharacteristic() will trigger
3. once the readCharacteristic() will finish the writeCharacteristic() will start
4. subscribe() will get the writtenBytes

With the second block - with the current implementation (which will try to share the connection between both subscription) it is uncertain wether the readCharacteristic() or writeCharacteristic() will be triggered first. In such a simple example there is no big difference but if the communication would be stateful in some way the other subscription could change the state of the first one.

My suggestion is to use the first block as there you can execute the flow exactly as you want.

from rxandroidble.

In the first case, you mean if I can't read some characteristic from other device, I can't write?

from rxandroidble.

Usually if you can't read from a characteristic that means that the connection is broken and you have to establish a new one. So yes. If a readCharacteristic() would fail you won't be able to writeCharacteristic

from rxandroidble.

But if the device in the other side doesn't write any characteristic, what will I read?

from rxandroidble.

I think that you should learn more about the Bluetooth Low Energy.
The characteristic is a kind of a property on the server device. What it will serve during readCharacteristic() is up to the server.
I am sorry but this is not really question about the library itself but more about how the BLE works. I suggest you to check www.google.com or ask a question on www.stackoverflow.com .

Best Regards

from rxandroidble.

Thanks for your suggestion.

from rxandroidble.