+ Bluetooth
+
+
+The device has no Bluetooth LE hardware, so no scan or connection can ever succeed (e.g. an Android XR headset).
An ExpectedCondition: the hardware said no, which is not a defect anyone can fix.
Inspects this Throwable and returns a BleExceptionInfo if it is a known Kable exception, or null if it is unrelated to the BLE layer.
Returns true if this throwable indicates the BLE session is irrecoverably broken and should be torn down (triggering reconnection), as opposed to a transient condition that can be retried.
Connects to the given BleDevice and waits for a terminal state or timeout.
Connects to the given BleDevice and waits for a terminal state or timeout.
Disconnects from the current device.
Disconnects from the current device.
Clears the platform's cached GATT service table for the connected peripheral, so the next discovery re-reads the device instead of replaying the cache. Necessary when a device reboots into a different GATT profile (e.g., ESP32 OTA loader) on the same BLE MAC, and as recovery when a bonded device that was out of range for a long time reconnects against a cache the platform never refreshed.
Requires a live connection: the implementation needs the platform's connection handle, so callers must invoke this while connected and then reconnect to pick up the fresh service table.
Returns true if the cache was invalidated. Default implementation returns false for platforms without a service cache.
Clears the platform's cached GATT service table for the connected peripheral, so the next discovery re-reads the device instead of replaying the cache. Necessary when a device reboots into a different GATT profile (e.g., ESP32 OTA loader) on the same BLE MAC, and as recovery when a bonded device that was out of range for a long time reconnects against a cache the platform never refreshed.
Requires a live connection: the implementation needs the platform's connection handle, so callers must invoke this while connected and then reconnect to pick up the fresh service table.
Returns true if the cache was invalidated. Default implementation returns false for platforms without a service cache.
Returns the maximum write value length for the given write type, or null if unknown.
Returns the maximum write value length for the given write type, or null if unknown.
Executes setup after the requested BLE profile is available. This is shared by radio, OTA, and DFU flows, so implementations should keep profile-entry setup bounded and avoid transfer-hot-path work here when a caller can reuse an already discovered BleService.
Executes setup after the requested BLE profile is available. This is shared by radio, OTA, and DFU flows, so implementations should keep profile-entry setup bounded and avoid transfer-hot-path work here when a caller can reuse an already discovered BleService.
Requests the platform to return to balanced BLE connection priority (default ~30–50 ms interval). Call after latency-sensitive operations (initial config drain, DFU) to reduce ongoing battery draw. Default implementation returns false for platforms that don't support it.
Requests the platform to return to balanced BLE connection priority (default ~30–50 ms interval). Call after latency-sensitive operations (initial config drain, DFU) to reduce ongoing battery draw. Default implementation returns false for platforms that don't support it.
Asks the platform to switch to a high-throughput / low-latency BLE connection priority for the duration of the connection. Used by latency-sensitive flows like firmware updates. Returns true if the request was issued. Default implementation returns false for platforms that don't support it.
Asks the platform to switch to a high-throughput / low-latency BLE connection priority for the duration of the connection. Used by latency-sensitive flows like firmware updates. Returns true if the request was issued. Default implementation returns false for platforms that don't support it.
The device has no Bluetooth LE hardware, so no scan or connection can ever succeed (e.g. an Android XR headset).