You pair your headphones, the car stereo, or that cheap JBL speaker. Android pops up "Connected." You hit play. Sound comes blasting out of the phone's own speaker while your Bluetooth device sits there silent. This happens most often after you've paired a device for phone calls first — think a car kit or a smartwatch — because Android remembers that profile and quietly ignores the media side.
I had a client last month with a Jabra headset paired to a Galaxy S22. It worked fine for calls. Music went to the phone speaker every single time. Took me ninety seconds to fix once I knew where to look.
Why this happens
Bluetooth isn't one connection. It's a bunch of separate profiles stacked on top of each other. The two that matter here are HFP (Hands-Free Profile) for calls and A2DP (Advanced Audio Distribution Profile) for music and media. A device can be connected on HFP and completely disconnected on A2DP, and Android will still show the friendly green "Connected" label because it only checks that something is linked.
That's the trap. The Bluetooth icon lies to you. Calls route to the headset. Media routes to the phone speaker. Android's not broken — the media profile just never got enabled, or it got toggled off by a buggy firmware update, or the device is fighting with another connected gadget over who gets audio priority.
Other common triggers: a device that only supports HFP (some old car kits), a smartwatch hogging the A2DP slot, or a Bluetooth stack crash that leaves the profile in a half-connected state.
The fix — in order
- Check the per-device media toggle. This is the one people miss. Open Settings → Connected devices → Bluetooth. Tap the gear icon next to the device name. You'll see two switches: Phone calls and Media audio. If Media audio is off, flip it on. That alone fixes it about 70% of the time.
- Toggle Bluetooth off and back on. Not airplane mode. Just the Bluetooth radio. Wait ten seconds, turn it back on, and let it reconnect. If the media profile was stuck in a bad state, this resets it.
- Forget and re-pair. Long-press the device → Forget. Then pair fresh from scratch. When Android asks which profiles to enable, say yes to media. Re-pairing rebuilds the profile stack cleanly.
- Kill other connected audio devices. If a smartwatch or second headset is connected, Android sometimes hands A2DP to the wrong one. Disconnect everything except the device you actually want to hear from.
- Check Developer Options for A2DP overrides. Enable Developer Options (Settings → About phone → tap Build number 7 times). Then go to Settings → System → Developer options and look for Disable Bluetooth A2DP hardware offload. Toggle it on. Reboot. On some Qualcomm devices — I've seen it on Pixels and OnePlus phones — this is the only thing that unsticks media audio.
- Clear Bluetooth cache. Go to Settings → Apps → Show system apps → Bluetooth → Storage → Clear cache. On Samsung it's under Settings → Apps → Show system apps → Bluetooth → Storage. Do NOT clear data unless you're ready to re-pair everything.
Step 1 fixes most cases. Skip everything else if the Media audio toggle was just off.
If it still won't work
Check the obvious stuff in this order:
- Does the device actually support A2DP? Some cheap car kits and old headsets are calls-only. Read the manual or search the model number.
- Is another app holding audio focus? A buggy podcast app or a stuck VoIP call can lock the media channel. Force stop anything audio-related and try again.
- Reboot the phone. Honest fix. The Bluetooth service is a system process and it crashes more than you'd think.
- Update the device firmware. A client's Bose SoundLink had exactly this bug. Bose pushed a firmware fix two months later. Not your phone's fault.
- Test with a different phone. If the same headset misbehaves on another Android, the device is the problem, not your phone.
If none of that works, back up and do a network settings reset: Settings → System → Reset → Reset Wi-Fi, mobile & Bluetooth. You'll lose saved Wi-Fi passwords, but it wipes the corrupted Bluetooth profile database. I've used this as a last resort maybe a dozen times in fifteen years.
The pattern to remember: "Connected" doesn't mean every profile is connected. When audio goes to the wrong place, check the per-device Media audio toggle first. It's almost always the answer.