Why Bluetooth Audio Sounds Terrible on Calls

You put your headphones on, play a track, and it sounds superb. Then a call comes in, you answer it, and the same headphones suddenly sound like a drive-through intercom. The music in the background turns muddy, everything goes mono, and the person on the other end says you sound distant and robotic.

This is not a fault. It is not your headphones degrading, your connection weakening, or an app misbehaving. It is Bluetooth doing precisely what it was designed to do, and the design decision dates back to the late 1990s.

Understanding why makes the workarounds obvious, because once you know what triggers the switch, you can avoid triggering it.

What actually happens when the call starts

Bluetooth audio is not one thing. There are two separate profiles, and a device can only be in one of them at a time.

The reason for the gap is bandwidth. A classic Bluetooth link has a fixed budget, and a two-way voice channel has to fit inside the same budget as the one-way music stream. Something has to give, and what gives is the stereo channel and most of the frequency range.

A2DP gives you a one-way stereo stream with enough bandwidth for genuinely good audio, and no microphone at all. HFP — the Hands-Free Profile — carries audio in both directions and pays for it by dropping to mono at a sample rate that cuts everything above about 4kHz. That is telephone bandwidth, and it is why voices lose their consonants and music turns to mush.

The switch happens automatically the instant an application requests the headset microphone. You do not choose it, and in most cases you are not told it happened.

Why it happens before you even make a call

The most frustrating version of this is music quality collapsing with no call in progress at all. The cause is an app holding the microphone open in the background — Teams, Zoom, Discord, Slack, a browser tab with a meeting room open, or a voice assistant listening for a wake word.

Any one of those pins the connection into HFP for as long as it holds the microphone, and the audio stays mono and muffled until it lets go.

On Windows, this is also why a single pair of headphones appears twice in the output list, once as “Headphones (Stereo)” and once as “Headset (Hands-Free)” — Bluetooth headphones connected but no sound on Windows covers how to pick the right one.

Fix 1 — Use a different microphone

This is the real solution, and everything else on this page is a compromise around it. If the headset microphone is never used, the connection never leaves A2DP, and your headphones stay in full stereo for the whole call.

On a laptop or desktop, use the built-in laptop microphone, a USB microphone, or a webcam microphone, and keep the headphones as the output device.

• Windows: Settings → System → Sound → under Input, choose the microphone you want. Then in Output, select the headphones entry ending in Stereo.
• macOS: System Settings → Sound → set Input to the built-in or USB microphone and Output to the headphones.

The built-in microphone on most laptops made in the last few years is genuinely better than any Bluetooth headset microphone, because it is not constrained by the HFP channel at all. A cheap USB microphone is better still.

On a phone, this is harder — using the phone’s own microphone while routing audio to Bluetooth headphones is not exposed in most call apps. A wired headset sidesteps the whole problem, and USB-C or Lightning earbuds with an inline microphone cost very little.

Set it per-app, not just system-wide

Most conferencing apps have their own device selection that overrides the system default, and it often defaults to the headset.

• Zoom: Settings → Audio → set Microphone to your laptop or USB mic and Speaker to the headphones.
• Teams: Settings → Devices → set Speaker and Microphone separately.
• Discord: User Settings → Voice & Video → Input Device and Output Device.
• Google Meet / browser calls: the camera icon in the address bar, or the in-call settings menu.

Crucially, these apps let you set input and output to different devices, which is exactly what you need. Set the microphone to something that is not the headset, and the headphones will stay in stereo for the entire meeting.

Fix 2 — Turn on wideband speech

If you must use the headset microphone, at least get the better of the two voice codecs. Wideband Speech uses mSBC at 16kHz instead of CVSD at 8kHz, and the difference is immediately audible.

Windows: Press Win+R, type mmsys.cpl, go to the Recording tab, find your headset microphone, open Properties → Advanced, and check the default format. Some drivers expose a Wideband Speech option under the Levels or a vendor-specific tab. Keeping the Bluetooth driver current from your laptop manufacturer matters here, because wideband support depends on the driver.

Android: Settings → System → Developer options → look for Bluetooth HFP wideband or Disable Bluetooth A2DP hardware offload. Developer options are enabled by tapping Build number in About phone seven times.

Both devices must support it. An older headset paired with a modern phone still falls back to narrowband.

Fix 3 — Check the codec and the connection

While A2DP is active, the codec in use determines quality. On Android you can see and change it:

Settings → System → Developer options → Bluetooth Audio Codec. LDAC and aptX HD give the best quality in good conditions and are the first thing to break in poor ones. If you get stuttering, dropping to AAC or SBC trades quality for stability.

Interference also matters more than people expect. Bluetooth transmits at around one milliwatt on the congested 2.4GHz band, and a weak link degrades audio before it drops it outright. Moving your phone out of a back pocket and onto a desk is a genuinely effective quality fix — why Bluetooth headphones keep disconnecting goes into the physics of that in detail.

Fix 4 — Clean the microphone

Before blaming the protocol entirely, check the hardware. Headset microphones sit in small ports that collect dust, pocket lint and earwax, and a blocked port sounds exactly like a bad connection.

Look for the small mesh-covered holes on the earbud stem or the headphone’s lower housing. Clean gently with a dry soft brush. Do not use liquid, compressed air at close range, or anything sharp.

What LE Audio changes

The constraint that causes all of this is specific to Classic Bluetooth. Bluetooth LE Audio, with the LC3 codec, was designed to remove it.

LC3 is efficient enough to carry high-quality stereo audio and a microphone stream at the same time, so there is no profile switch and no collapse to mono when a call starts. It also supports higher-quality bidirectional voice, multi-stream audio for true wireless earbuds, and Auracast broadcast.

Support is arriving steadily rather than suddenly. It requires:

• Headphones with LE Audio support — recent Samsung Galaxy Buds, Sony, Jabra and Bose flagship models.
• A phone or PC with a Bluetooth 5.2 or later radio and LE Audio enabled.
• Operating system support. Android 13 and later, Windows 11 with a compatible driver, and recent Samsung devices have it. Apple has not adopted LE Audio across the AirPods line in the same way, using proprietary extensions instead.

On Android, check Settings → Connected devices → the gear beside your headphones for an LE Audio toggle. On Windows 11, Settings → Bluetooth & devices → Devices shows LE Audio support where both the adapter and headset qualify.

If your existing headphones do not support it, no setting will add it. It is a reason to check the specification when you next replace them, not a fix for what you own now.

Myths worth dropping

• “Expensive headphones have better call quality.” Over classic Bluetooth they do not, because the HFP channel constrains everything equally. A flagship headset and a budget one sound similar on calls, which is why the difference between them is so stark between music and voice.
• “It is a weak signal.” Signal strength affects dropouts and stuttering, not the profile switch. If quality collapses the instant a call connects and recovers the instant it ends, that is the profile, not the radio.
• “A Bluetooth 5.3 dongle will fix it.” A newer Bluetooth version does not change the profiles in use. Only LE Audio with LC3 on both ends does.
• “Turning off noise cancelling improves it.” ANC is processed inside the headphones and does not consume Bluetooth bandwidth. It is unrelated.
• “Clearing the Bluetooth cache fixes call quality.” That fixes pairing and connection faults, not an inherent protocol limitation.

Realistic expectations

If you can use a separate microphone, do — it is the only fix that genuinely restores stereo quality on calls, and it costs nothing on a laptop.

If you cannot, enabling wideband speech is a real improvement and worth the few minutes of setup. Everything else is working within a limit that classic Bluetooth was never designed to exceed.

For the next pair of headphones, LE Audio support is the specification that actually matters for this problem.