Short answer: use read for occasional values, write for commands, write without response for fast streaming to the device, notify for frequent updates from the device, and indicate when you need each update acknowledged.
The five operations
- Read: your app asks, the device answers once. Good for battery level or firmware version.
- Write (with response): the device confirms receipt. Use for settings and commands that must not be lost.
- Write without response: no confirmation, higher throughput. Use for streaming data such as firmware chunks.
- Notify: the device pushes updates without acknowledgement. Use for sensor readings.
- Indicate: like notify, but the phone acknowledges each one, so it is slower and more reliable.
Choosing the write type in Kotlin
// Android 13+ (API 33)
gatt.writeCharacteristic(
characteristic,
data,
BluetoothGattCharacteristic.WRITE_TYPE_NO_RESPONSE
)
The characteristic must support the property you use. Check characteristic.properties for PROPERTY_NOTIFY, PROPERTY_INDICATE, PROPERTY_WRITE and PROPERTY_WRITE_NO_RESPONSE.
Enabling notify or indicate
Both need the CCCD descriptor written, as covered in our BLE troubleshooting guide. Use ENABLE_NOTIFICATION_VALUE for notify and ENABLE_INDICATION_VALUE for indicate.
Quick decision table
- One-off value? Read.
- Command that must arrive? Write with response.
- Large data, speed matters? Write without response, in chunks.
- Live sensor data? Notify.
- Critical events that must not be missed? Indicate.
FAQ
Is notify faster than read?
For repeated updates, yes. One CCCD write replaces many read requests.
Can a characteristic support both notify and indicate?
It can declare both, but you enable one at a time through the CCCD value.