Classic Bluetooth SPP, BLE GATT services and clients, notifications and reconnection. Radio roles and GATT client/server roles are separate design choices; define the application data contract explicitly.
Select LE Coded from measured delivery and airtime under the same workload, not from a nominal range multiplier. First prove that the connection uses LE Coded in the intended direction. Then establish which coding scheme the transmitter actually used; requesting S=2 or S=8 does not make that preference a per-packet guarantee. Applicability: Bluetooth Core 6.1…
Prove two different transitions: additional activity permitted by continuation events, and a negotiated change of subrate parameters. Neither should be inferred from a successful request call. Record the effective factor and completion status, then measure the first useful application response from several arrival phases in the idle schedule. Applicability: Bluetooth Core 6.1 and Zephyr v4.2.0,…
PAwR fits a sensor product only when three budgets agree: each device owns a defined response opportunity, its packet fits that opportunity, and the host supplies the response before the controller’s deadline. A schedule with enough numbered slots is necessary but does not establish reliable reporting or application freshness. Applicability: this analysis pins Bluetooth Core…
Compare LE L2CAP CoC and GATT for bulk transfers through platform support, framing, backpressure and recoverable commit semantics.
Interpret ATT errors using opcode, handle and procedure context, separating permissions, security prerequisites and value failures.
Define bond admission, finite storage, authorized eviction and one-sided key-loss recovery without weakening security.
Design event-driven iOS BLE recovery with stable restoration identifiers, app-owned operation journals and a real-device lifecycle test plan.
Separate Android permission denial, scanner failures and missing advertisements with an OS-and-target-SDK matrix and a controlled acceptance sequence.
Separate radio reception, duplicate suppression, OS reporting and UI deduplication before judging BLE discovery latency, freshness or RSSI.
Allocate legacy BLE advertising and scan-response bytes separately, preserve first-packet discovery fields and validate names and AD structures at their boundaries.