PROTOCOL NOTES / 12

21 · Android 10 leaf over a single BLE link

Participants: Galaxy, Pixel, Peer

Implemented software · Tested on hosts and emulators only · Physical qualification pending

Starting state

Sealed ride. Galaxy (Android 10, no Wi-Fi Aware) advertises capability flags 0x30: BLE link and host capable, one BLE link, no Wi-Fi Aware, so it is a leaf, and it is its own root. Pixel is in the mesh over Wi-Fi Aware with Peer at root 0 and has a free BLE slot; Pixel has the lower peer ID.

Ordered events

  1. Galaxy → Pixel

    BLE advertising with the ride service UUID and encrypted ride information showing one BLE link and no Wi-Fi Aware

  2. Pixel → Galaxy

    Lower peer ID connects as central after a verified GATT read because Galaxy advertises a greater root, L2CAP, TLS and greeting linkKind ble

  3. Galaxy → Galaxy

    At its one-link limit close the L2CAP listener on accept and stop advertising

  4. Galaxy → Pixel

    hello, advert, handoff_prepare and probes in datagram frames, Pixel answers handoff_ready, Galaxy activates and Pixel acknowledges

  5. Pixel → Galaxy

    Pixel mix of Pixel and Peer, and acks

  6. Galaxy → Pixel

    Galaxy mix containing only its own microphone

  7. Pixel → Peer

    Forward the Galaxy mix unchanged over Wi-Fi Aware

  8. Galaxy → Galaxy

    Keep scanning with GATT reads only, never opening a second channel

Fields and messages

Capability byte bits 4-5 set, bits 6-7 zero, bit 2 clear; greeting linkKind ble, mediaPort 0; mix descriptors with edge; speaker set and mixer set with the Galaxy index only.

Authorization and invariants

A device on Android API level 29 or older advertises exactly one BLE link and never holds two channels; at the limit its listener is closed, so no channel is accepted at stack level; two leaves never link with each other; Bluetooth calls never run on the UI thread; a leaf forwards nothing onward.

Timers

L2CAP open 5 s; ClientHello 1 s; liveness 3 s suspect and 6 s dead; reconnection after 1, 2, 4 then 5 s; GATT re-reads every 3 s while roots differ or the scanner's parent link is not healthy, otherwise every 15 s; Bluetooth call watchdog 5 s.

Resource lifetime

Capability flags persist for the device; the BLE channel, TLS and hop keys belong to one connection; the Galaxy voice and mix sources persist for the ride.

What the rider sees

Diagnostics show BLE limit 1, no Wi-Fi Aware and the BLE link counters; if no path remains the rider is told to bring the app forward only on Apple devices, while Android keeps advertising in the background.

Failure branches

After channel loss the Galaxy reopens its listener and resumes advertising, and Pixel reconnects within the cooldown; no second central can open a channel while the listener is closed; while its parent link is only suspect the Galaxy opens no second channel and can link to another host only after that link has closed; a blocked Bluetooth call is reported as bt_call_stuck and treated as failed; Android 10 support in a distributed build is a separate product decision.

Resulting state

Galaxy is a leaf: child of Pixel over its only BLE link, with its listener closed and no longer advertising; it keeps scanning with GATT reads only; it hears the ride through Pixel's mix and is heard through its own mix.

Evidence boundary

Implemented software; host and JVM tests only. Host tests cover leaf capability flags (no Wi-Fi Aware, one BLE link), lobby planning through a BLE host and the channel multiplexer; JVM tests cover the one-link limit of Android 10 and older, the listener closing at the limit, the incoming cooldown and the bt_call_stuck watchdog. Spike evidence only: one channel stable for 21 min with p95 below 41 ms, two concurrent channels wedge the Android 10 stack. The Android 10 leaf is physically unqualified.

← All scenarios

Authority: RWCP v2 reviewed scenario catalogue, scenario 21. Public examples are synthetic. This guide is maintained against the private implementation; it does not imply access to its source.