Android Bluetooth Sockets

Step 1: Define the socket contract

1. DEFINE RFCOMM/SPP client | RFCOMM server | LE L2CAP CoC client | LE CoC server | blocking-call hang | stream corruption | API 36 settings migration | target-37 EOF | background connection.
2. IDENTIFY min/compile/target SDK, Android/device/OEM and peer matrix, transport, client/server roles, RFCOMM service UUID/name or LE PSM-disclosure mechanism, authentication/encryption requirements, adapter/permission state, connection deadline, message framing, payload bounds, one read owner, one write serializer, lifecycle/process owner, background mechanism, and retry semantics.
3. READ the exact current BluetoothSocket, BluetoothServerSocket, and BluetoothSocketSettings pages for the selected SDK branch.
4. READ references/api-matrix.md; inspect the compile SDK stubs before using settings symbols not listed there.
5. ROUTE GATT to android-ble/android-ble-gatt-queue, logical LE CoC protocol design to ble-protocol-stack, throughput tuning to ble-throughput, and application cryptographic handshakes to noise-protocol.

Completion: transport, API branch, peer rendezvous, security, blocking-call owner, framing, cancellation, background, and observable failure states are explicit.

Step 2: Inspect the Android project

RUN from the Android project root:

python3 scripts/inspect-project.py --root . --json