Bluetooth audio problems

Wireless audio fails in a handful of specific ways. Each has a cause you can identify in under a minute.

The sound is delayed

Every Bluetooth link adds latency: the audio is compressed, transmitted, buffered and decoded, and that takes between roughly 100 and 300 milliseconds depending on the codec and the devices. It is unavoidable, not a fault, and it is why a test tone can seem to start late.

It only matters when sound has to line up with something. Video players compensate automatically by delaying the picture, which is why films look fine and games do not — a game cannot delay the picture without delaying your controls. If latency matters to you, a wired connection or a dedicated low-latency dongle is the only real answer.

Only one earbud plays

In a true wireless set, one bud connects to your device and relays to the other. When that relay drops you get one working side, and the silent bud still lights up and still charges, so it looks broken.

Fix it in this order: put both buds in the case and close it for ten seconds; if that fails, remove the set from the device's Bluetooth list and factory reset the buds with the manufacturer's button sequence, then pair again. Confirm with the left/right test rather than by listening to music, which can be nearly mono anyway.

Everything turns tinny during a call

This is the most misdiagnosed Bluetooth behaviour there is. A headset can run in one of two modes: a high-quality one-way mode for media, and a low-bandwidth two-way mode for calls that carries a microphone as well. The moment an application claims the microphone, the system switches to the call mode, and the audio quality collapses to something like a telephone.

Nothing is broken. Close the application holding the microphone — a conferencing app left running in the background is the usual culprit — and the quality returns. On Windows you can also disable the "hands-free" profile for that device so it never switches, at the cost of the microphone.

The sound stutters or drops out

Bluetooth shares the 2.4 GHz band with Wi-Fi, microwave ovens and a great deal of else. Stuttering in a busy office, on a train or next to a router is interference rather than a device fault. Your own body counts too: keeping the phone in the pocket on the opposite side from the primary earbud is enough to cause dropouts, because water absorbs those frequencies.

Try moving the source device to the same side, keeping it in line of sight, and switching your router's 2.4 GHz channel if the problem is worst at home.

The volume steps are too coarse

Some devices keep a single shared volume, others keep separate device and host volumes. When they are separate and both are low you get a quiet signal amplified loudly, which is noisy; when both are high you get a handful of usable steps at the bottom. If your volume goes from too quiet to too loud in one press, set the headset volume near maximum and control it from the source, or the other way round, and see which gives you finer control.

Channels sound swapped or the image is odd

Some headsets apply spatial or surround processing by default, which moves sound around deliberately and makes the stereo check hard to read. Turn any such mode off in the manufacturer's app before testing, then run the test again. If the channels are still reversed with all processing off, the set is faulty, which is rare enough to be worth a warranty claim.

Testing wireless audio properly

Allow for the delay on every step, use a quiet room, and keep the source device close and in sight. Then run the headphone test, which checks both drivers, the channel order and the top end.

One caveat on the top end: several Bluetooth codecs discard the highest frequencies to save bandwidth. A hearing range test over Bluetooth therefore tends to read lower than the same test over a wire, and the difference is the codec rather than your ears.

Last reviewed 2026-09-22.