Wearables and Wireless: Bluetooth Internals for the Brave
summary
Covers concrete failure modes and fixes for wearables: ghost advertisements from stopping before callbacks, rapid start/stop floods that require reboots, and GATT deadlocks from concurrent requests. Shows exact debugging tools and flows — btsnoop_hci.log, dumpsys bluetooth_manager, ADB bugreport + Wireshark — and prescribes tactics: wait for callbacks, use one callback per advertiser, backoff retries, limit scan filters to about 5–7, and clear bond cache after firmware updates; notes manufacturer data is 31 bytes and mentions Bluetooth 5.4 periodic adverts.
AI-written summary · about
chapters (12)
- 0:00Bluetooth for wearables intro
- 2:37Bluetooth evolution in wearables
- 6:12Bluetooth stack breakdown
- 10:56Advertising and scanning basics
- 16:15Debugging ad pitfalls
- 17:18Scanning best practices
- 20:31Service UUIDs and data
- 23:45GATT server/client exchange
- 27:45Data exchange lifecycle
- 31:45Pairing vs bonding
- 35:30Debugging reliability
- 39:50Bluetooth future in wearables
related talks
35mDeep into Android Bluetooth Bug Hunting: New Attack Surfaces and Weak Code Patterns
55mBluetooth on Embedded Linux Systems Deep Dive
46mSpinning the Phisycal Web with Android and Bluetooth 5
46mSpinning the physical web with android and bluetooth 5
41mEVERYTHING IS BETTER WITH(OUT) BLUETOOTH
19mWhat's all that hype about BLE?
34mA journey in Android's BLE world
30m"Android Wear iBeacon development"