Android BLE

Step 1: Define the Android BLE contract

1. DEFINE scan/discovery | advertise/peripheral | direct/automatic GATT connection | service discovery/cache | read/write/subscribe | background presence/connection | bond/re-pairing | Android 17 migration | OEM failure.
2. IDENTIFY min/compile/target SDK, device/Android/OEM matrix, BLE central/peripheral and GATT client/server roles, identity/filter, foreground/background/process-death behavior, permissions, association/bond model, connection owner, callback executor, operation queue, timeout/retry policy, and user-visible behavior.
3. READ references/ble-overview.md and the current Android BLE overview before choosing the platform flow, role names, or security boundary.
4. SEPARATE central/peripheral link roles from GATT client/server procedure roles. Name both axes in state, logs, and tests.
5. TREAT pairing/link protection as shared device transport security, not app isolation. For sensitive data, define application-layer confidentiality, authentication, and key ownership.
6. READ the official Android BLE background guide, Bluetooth permissions, and relevant API-level branch before editing.
7. READ references/source-audit.md before applying Android 17 claims from secondary sources. Separate all-app changes, target-37 changes, older enforced requirements, empirical OEM behavior, and Bluetooth Classic-only changes.
8. ROUTE ADB executable/device/shell/diagnostic mechanics to android-debug-bridge, Android GATT connection/status failure diagnosis to android-ble-gatt-status, BLE inspector/diagnostic Compose surfaces to android-ble-inspector, local BluetoothGattServer database/request/notification internals to android-ble-gatt-server, remote client operation serialization/races to android-ble-gatt-queue, RFCOMM and LE L2CAP CoC socket transports to android-bluetooth-sockets, logical GAP/GATT/ATT/L2CAP design to ble-protocol-stack, PHY/MTU throughput tuning to ble-throughput, application security protocols to noise-protocol, and generic Kotlin/coroutine/build mechanics to their dedicated skills.

Completion: SDK/device matrix, both role axes, permission/background model, transport/application security boundary, connection/operation owner, and observable success/failure states are explicit.

Step 2: Inspect the app