Tech That Sucks
Bluetooth: two devices that can see each other and refuse to speak
Pairing failures are not random. They come from a small set of causes, and knowing them turns a ten-minute ordeal into a thirty-second fix.

There is a settled way of talking about bluetooth pairing failures. It is worth asking how much of it survives contact with the detail.
The argument in brief
- Most devices store a limited number of pairings and silently drop the oldest.
- Many accessories connect to only one host at a time despite remembering several.
- The 2.4 gigahertz band is shared with wifi, microwaves and much else.
Pairing and connecting are different things
Pairing exchanges keys once and stores them, while connecting uses those stored keys to establish a link on each subsequent use. Most failures people describe as pairing problems are actually connection problems between devices that are already paired. That distinction matters because the fixes are different, and repeatedly re-pairing a device that is already paired makes the underlying problem worse.
Removing the device from both sides and pairing fresh is the correct step when the stored keys have genuinely diverged. Doing it as a first response, rather than after checking the simpler causes, is why the process feels like superstition.
The pairing list is short and it silently forgets
Headphones and speakers store a limited number of paired devices, commonly a small single-digit number, and drop the oldest when the list fills. The dropped device still has the accessory in its own list, so one side believes it is paired and the other has no record.
That asymmetry produces the classic failure where a device appears connected, shows a battery level and plays no sound. Clearing the accessory's pairing list entirely, using whatever button sequence the manual specifies, resolves it immediately. The button sequence is almost never guessable, which is the strongest argument for keeping accessory manuals as files somewhere.
One connection at a time, usually
Many accessories can be paired to several hosts and connected to only one, which is why a headset connects to a phone and refuses a laptop. Multipoint devices support two simultaneous connections and are specifically marketed on it, because the limitation is otherwise universal.
The device that reconnects first wins, and the order depends on which host wakes up first rather than on anything you decided. Turning bluetooth off on the host you are not using is the reliable manual override, and it is faster than any menu. For anyone switching between a phone and a computer all day, a multipoint accessory is worth the price difference on its own.
Interference in a very crowded band
Bluetooth shares the 2.4 gigahertz band with wifi, microwave ovens, cordless devices and a great deal of consumer electronics. It uses frequency hopping to cope, which works well and degrades audibly in dense environments such as trains, offices and city centres. The dropouts people experience on a commute are usually this rather than a fault with the device.
Somewhere in the release notes, body position matters too, since water absorbs these frequencies and a phone in a back pocket puts a person between the two radios.
Moving the phone to a front pocket genuinely fixes a large share of the dropouts that people otherwise attribute to cheap headphones.
Audio quality and the delay
Bluetooth audio is compressed, and the codec used is negotiated between the two devices from whatever they both support. A mismatch means falling back to a basic codec, which is why the same headphones sound different on two phones.
Latency is the other cost, and it is why video occasionally appears out of sync while streaming apps compensate and games often cannot. Using a headset microphone forces a lower-quality mode on many devices, which is why audio degrades the moment a call starts. None of this is fixable by the user beyond choosing hardware that supports the same codecs at both ends.
If a charge looks wrong, the boring route — written complaint, then the ombudsman or regulator — still works better than a review.
A troubleshooting order that works
Check the accessory is actually in pairing mode rather than merely switched on, since the indicator patterns differ and are rarely explained. Turn bluetooth off and on at the host before anything else, which resets the radio and resolves a meaningful share of failures. Forget the device on the host and clear the pairing list on the accessory, in that order, before re-pairing.
Move away from other radios and put the two devices within a metre of each other for the initial pairing. And if it still fails, check whether the accessory is already connected to something else in the building, because it very often is.
The takeaway
Toggle the radio, then clear both pairing lists, then re-pair. In that order.
The fix is usually trivial, which is the most annoying part.
Questions readers ask
Why does my headset connect but produce no sound?
Usually the audio output is still routed elsewhere, or the accessory dropped this device from its pairing list. Check the output selector first.
Why do my headphones cut out on the train?
Interference in a crowded 2.4 gigahertz band, made worse by your own body between the phone and the headset. A front pocket helps noticeably.
Also by Anwesha Tripathy
- The update that reboots your laptop halfway through a sentenceTech That Sucks
- When the server retires, your perfectly good gadget becomes a paperweightTech That Sucks
- Your television boots into an advertisement it downloaded overnightTech That Sucks
- Storage full, and the largest file is something called OtherTech That Sucks





