14 State Machines That Must Agree for Bluetooth to Work

on YouTube ↗39m

" summary

Android Bluetooth requires 14 state machines to reach consistent states for simple connect/pair flows, not just one. The stack uses the state-machine base class plus a handler looper FIFO message model and a typical 10 second timeout to avoid phantom connected states; codecs negotiated are LDAC/AAC/SBC and LE Audio moves to LC3 with multi‑streaming. Debugging relies on Bluetooth dumps + HCI logs + logcat, unit/mock loopers, and CLI-driven end‑to‑end tests; these patterns cut false positives and codec deadlocks in practice.

AI-written summary · about

" chapters (16)

1. 0:00Bluetooth state machines intro
2. 2:08Android Bluetooth stack
3. 3:57State machine basics
4. 6:1014 state machines explained
5. 6:55Foundation state machines
6. 11:30Audio pipeline state machines
7. 14:25LE audio and GATT state machine
8. 17:20Thread safety patterns
9. 19:49Observer pattern sync
10. 21:40Registry pattern coordination
11. 22:42Bluetooth failure modes
12. 26:16Debugging with dumps
13. 28:04Key takeaways
14. 29:32Q&A
15. 32:26Timeout strategies
16. 34:56Resources and future

" related talks

• 40mState of Bluetooth LE on Android in 2023Erik Hellman · Android Makers by droidcon 2023
• 35mState of BLE on Android in 2022Erik Hellman · droidcon London 2022
• 34mBluetooth Low Energy in Android: Getting it DoneSyzmon Janc, Lukasz Rymanowski · Android Builders Summit 2013
• 38mBluetooth LE for Modern Android DevelopmentErik Hellman · droidcon Berlin 2021
• 46mBluetooth Low Energy on Android: Top Tips for the Tricky BitsStuart Kent · Mobilization 2017
• 41mEVERYTHING IS BETTER WITH(OUT) BLUETOOTHRonaldo Pace, Falko Richter · droidcon Berlin 2018
• 31mAn introduction to Bluetooth mesh for Android developersMartin Woolley · Droidcon Italy 2018
• 25mKeeping Up Continuous Development of BLE-Based AppsMoyuru · DroidKaigi 2022