Bluetooth is one of the most frequently used Android features and also one of the most misunderstood. Many issues that developers experience are not caused by flaky APIs or incorrect usage, but by multiple independent state machines across discovery, connection, security, transport, audio routing, and system policies drifting out of sync. This session explains why Bluetooth behaves the way it does on Android and why many failures appear random when they are actually deterministic. The talk reframes Bluetooth as a coordination problem rather than a linear flow and introduces a systems level mental model that helps developers reason about failures more effectively. Major takeaways for the audience include understanding Bluetooth as a set of concurrent state machines, learning why connected or bonded does not always mean ready, recognizing common real world failure patterns caused by timing issues.