You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.
I have used this app to receive MID messages from an iOS app.
I am now trying to send messages and I am struggling to understand some of the logic.
When I call BluetoothGattCharacteristic.setValue(), this only sets the local value, which only goes to the other side after they have tried to read it.
So one can call BluetoothGattServer.notifyCharacteristicChanged() to suggest a read operation.
So, my question is: the only way to be sure the data has been read (before I can write more), is to wait for the next BluetoothGattServerCallback.onCharacteristicReadRequest() call? Is it the way it is supposed to work?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have used this app to receive MID messages from an iOS app.
I am now trying to send messages and I am struggling to understand some of the logic.
When I call BluetoothGattCharacteristic.setValue(), this only sets the local value, which only goes to the other side after they have tried to read it.
So one can call BluetoothGattServer.notifyCharacteristicChanged() to suggest a read operation.
So, my question is: the only way to be sure the data has been read (before I can write more), is to wait for the next BluetoothGattServerCallback.onCharacteristicReadRequest() call? Is it the way it is supposed to work?
The text was updated successfully, but these errors were encountered: