Why Your Headphones Sound Worse the Second a Call Starts

Your headphones are not broken, and neither is the app. The moment anything asks for your microphone, Bluetooth swaps to a different profile — and that profile was designed for intelligible speech, not music.

The giveaway is that it happens instantly and reverses instantly. Music is fine, the call connects, everything goes muffled and slightly distant, the call ends, and the music is fine again.

Two profiles, and only one at a time

Bluetooth does not have a single “audio” mode. It has separate profiles for separate jobs, and your headphones support several.

A2DP — the Advanced Audio Distribution Profile — is the one playing your music. The Bluetooth SIG’s own description is that it “defines the requirements for Bluetooth devices necessary for support of the high-quality audio distribution”. It is one-directional: it sends audio to your headphones and expects nothing back.

HFP — the Hands-Free Profile — is the one that takes over on a call. It exists so that “a Mobile Phone can be used in conjunction with a Hands-Free device”, and it carries the microphone as well as the earpiece.

Here is the part that matters: you cannot run both at once. Microsoft’s own support answer on this exact question puts it plainly — “you cannot use two different Bluetooth profiles at the same time” — because they have different bandwidth, latency and power requirements.

So the instant something needs your microphone, the connection leaves the high-quality one-way profile and enters the two-way call profile. Both directions now share a link that was specified for speech. Everything you hear degrades, because the link is no longer being asked to do the job A2DP was written for.

The popular explanation is nearly right

On r/techsupport, the top answer to someone describing exactly this says it is because Bluetooth “only supports two simultaneous audio channels, so you can either get stereo output or one channel for output and one for microphone.”

That is a good intuition and it gets the reader to the right conclusion, but it is not what the specifications say. The constraint is not a fixed count of channels — it is that A2DP and HFP are different profiles with different requirements, and the connection is in one or the other. The practical result is the same. The reason it is worth being precise about is that it tells you where the fix is: not in a channel setting, but in which device is being asked for the microphone.

What to actually do

On a laptop or desktop, this is fixable in about thirty seconds. The switch is triggered by your headphones being selected as the input device. Choose a different microphone and they stay in the high-quality profile.

• Windows — Settings → System → Sound → Input, and pick the laptop’s built-in microphone array instead of the headset.
• macOS — System Settings → Sound → Input, same idea.
• Then set the output back to your headphones if it moved.

You will sound like your laptop’s microphone, which is usually a fair trade: everyone else hears a slightly worse you, and you hear a considerably better everyone.

On a phone, you generally cannot. The Reddit thread ends where every version of this thread ends — “is there no way to make my phone use my phone mic instead?” — and the honest answer is that phones route call audio and microphone together, and do not expose the choice.

If it matters enough, leave Bluetooth. Wired earbuds have no profiles to switch between. Wireless headsets that ship their own USB transmitter are not using Bluetooth at all, which is exactly why gaming headsets sound the same on voice chat as off it.

The check, if you want to confirm it

Play music, join a call with your microphone set to the headset, and listen to the music. Then change the input device to anything else while the call is still running. The music quality will jump back, mid-call, without touching the headphones. That is the profile switching, and it is the whole of the phenomenon.