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.
Admit an extended-advertising record to device discovery only after the receiving layer has established that its data is complete and the application parser has validated the result. A recognizable name or service identifier in an early fragment is not evidence that the rest of the record arrived. A truncated report must not be repaired by…
HCI USB Bulk Serialization is a transport-mode migration. It needs controller descriptor support, a compatible host driver, a controlled alternate-setting transition and packet dispatch that preserves the intended order. A Bluetooth version label or working legacy ACL traffic is insufficient evidence. Applicability: Bluetooth Core 6.3, Volume 4 Part B USB transport. The SIG’s Core 6.2…
Before blaming the radio for a missing controller event, establish that the event is supported, enabled, required by the attempted procedure and visible at the HCI receive boundary. An application callback is the last observation in that chain, not the first. Applicability: Bluetooth Core 6.1 HCI event-selection commands and Linux v6.12 initialization source. The worked…
After a byte disappears from an HCI UART stream, recognizing a plausible packet-type byte does not prove that framing has recovered. Choose the recovery mechanism from the actual transport contract, and distinguish locating a packet boundary from proving that its payload is intact. Applicability: Bluetooth Core 6.1 UART transport, commonly called H4, and Three-wire UART…
A broadcast receiver is not ready merely because it found periodic advertising. Readiness requires the intended BIG, the selected BIS streams, successful synchronization, usable data paths and valid application data. Keep evidence for each boundary so recovery does not reuse an old stream accidentally. Applicability: Bluetooth Core 6.1 Broadcast Isochronous Group synchronization and Zephyr 4.2.0…
A late sample is not necessarily a radio loss, and an ISO receive callback is not necessarily carrying usable data. Preserve the controller’s SDU status, the host delivery boundary and the consumer deadline decision as separate evidence. Applicability: Bluetooth Core 6.1 HCI ISO data and ISOAL concepts, plus Zephyr 4.2.0 host ISO receive APIs. The…
A HID report can arrive intact over Bluetooth and still operate the wrong host control. The Report Map defines how bytes become buttons, relative movement, absolute values or vendor-defined data. Validate that interpretation before treating a successful notification as a working instrument interface. Applicability: HID over GATT Profile 1.2, USB HID 1.11 descriptor rules and…
Mesh privacy has several independent controls. Changing the Bluetooth advertiser address does not automatically replace clear network discovery information, enable private proxy discovery or restrict how long a proxy remains discoverable. Qualify those behaviors as separate states. Applicability: historical Bluetooth Mesh Protocol 1.1 private-beacon and proxy procedures, with Zephyr 4.2.0 solicitation receive behavior identified explicitly….
Directed forwarding is useful only when the required path exists, its address scope matches the traffic and failures produce a controlled recovery. Enabling a feature flag or seeing one PATH_REQUEST does not establish that a usable directed path has been installed. Applicability: historical Bluetooth Mesh Protocol 1.1, focusing on dynamically discovered, non-fixed paths to a…
Define a Mesh subnet bridge as a small, reviewable forwarding matrix. Sharing two NetKeys with a node does not mean every message should cross between those subnets. The bridge table identifies the permitted subnet pair, source, destination and direction; application authorization remains a separate boundary. Applicability: historical Bluetooth Mesh Protocol 1.1 subnet bridging and Zephyr…