How Bluetooth actually works
Two devices that have never met agree to talk, then spend the entire conversation changing radio channel 1,600 times a second in a pattern only they know — in the same crowded slice of spectrum as your microwave, your Wi-Fi and everyone else's headphones.
Everything lives in the same crowded band
Bluetooth operates between 2.400 and 2.4835 GHz — a narrow strip of spectrum that anyone may use without a licence. That freedom is why Bluetooth exists at all, and it is also why it is competing with half the devices in your home.
Most radio spectrum is licensed: a company pays a great deal of money for exclusive use of a slice and nobody else may transmit there. The ISM bands are the exception — set aside for industrial, scientific and medical use, and open to anyone whose equipment meets the rules on power and behaviour.
A licence-free band is the only way a device costing a few pounds can ship worldwide. It is also, inevitably, where everything ended up.
Bluetooth's answer: never stay in one place
Faced with a band it cannot control, Bluetooth takes a different approach from Wi- Fi. Rather than picking a channel and defending it, it divides the band into 79 channels one megahertz wide and changes channel 1,600 times a second — a new one every 625 microseconds.
This is frequency-hopping spread spectrum, and it is why Bluetooth survives in an environment that ought to be unusable. If a hop lands on a channel being clobbered by Wi-Fi, that one tiny packet is lost and the next hop is somewhere else entirely. Interference has to follow you across the whole band to actually break the link.
The hop sequence is derived from the address and clock of the device acting as master, so both ends compute the same pattern independently and stay in step without ever transmitting it. Another Bluetooth pair nearby is using a different sequence, so the two only occasionally collide — and when they do, they have both moved on within a millisecond.
The takeaway Bluetooth shares an unlicensed band with everything else and copes by refusing to stand still — 1,600 channel changes a second, in a pattern only the two ends can compute.
Pairing happens once; connecting happens constantly
People use 'pairing' to mean 'getting it to work', which hides a distinction worth knowing. Pairing is a one-off negotiation that creates a shared secret. Connecting is what happens every time afterwards, and it uses that secret without asking you anything.
Proving the other device is the right one
The hard problem in pairing is not encryption — it is making sure you established the key with the speaker in front of you and not with someone in the next room. Bluetooth picks a method based on what the two devices can actually do.
| Method | Used when | What you experience |
|---|---|---|
| Numeric comparison | Both ends have a screen | Matching six-digit codes to confirm |
| Passkey entry | One has a keypad, one a screen | Typing a code shown on the other |
| Just Works | Neither has a screen or keypad | Nothing — it simply connects |
| Out of band | Both support NFC | Tap the devices together |
Just Works is the weak one, and it is what most headphones use. It encrypts the link, but it cannot verify who is at the other end, so it is theoretically vulnerable to someone in range intercepting the pairing itself. In practice this requires an attacker present at the exact moment you first pair a device, which is why it is tolerated for earbuds and not for anything that matters.
Why it fails in the ways it does
Already bonded elsewhere
Many headphones only hold one bond, or a small number. Pairing with a new phone silently evicts an old one, which is why the laptop stops finding them.
Not in pairing mode
A device that is bonded stops advertising to strangers. Holding the button until it flashes differently puts it back into discoverable mode.
Stale key on one side
Delete the device on the phone but not the headphones and the two disagree about the secret. Both sides have to forget.
Multipoint confusion
Newer headphones hold two active connections and switch between them — which can look like a fault when audio arrives from the device you were not expecting.
The takeaway Pairing creates a shared secret; bonding saves it. Almost every Bluetooth annoyance is a disagreement about stored keys, or a device that has quietly run out of room for them.
Bluetooth is two different technologies
This is the single most useful thing to know about Bluetooth, and it is almost never explained. Since 2010 the name has covered two radio systems that share a band and a brand and essentially nothing else. They cannot talk to each other.
Why Low Energy exists
Classic Bluetooth keeps a connection alive, which means transmitting regularly whether or not there is anything to say. That is entirely reasonable for a speaker and hopeless for a door sensor that needs to run for three years on a battery the size of a coin.
BLE inverts the assumption. The radio is off by default. A device wakes briefly, advertises or sends its handful of bytes, and goes back to sleep — possibly for seconds or minutes. Averaged over an hour it might transmit for a fraction of a second, which is how a temperature sensor lasts years on a CR2032.
BLE describes itself, rather than using fixed profiles
Classic Bluetooth defines a fixed catalogue of profiles: A2DP for audio, HFP for hands-free calling, HID for keyboards. Both ends must implement the same profile, and adding a new kind of device means standardising a new one.
BLE instead uses GATT, a generic structure of services and characteristics that a device publishes about itself. A heart rate monitor advertises a heart rate service containing a measurement characteristic; anything that understands GATT can read it without prior arrangement. It is closer to a tiny self-describing database than a protocol.
| Profile | What it does | Which technology |
|---|---|---|
| A2DP | Stereo audio streaming | Classic |
| HFP / HSP | Calls — microphone and earpiece | Classic |
| AVRCP | Play, pause, skip, volume | Classic |
| HID | Keyboards, mice, controllers | Both |
| GATT services | Sensors, watches, trackers, beacons | Low Energy |
| LE Audio / LC3 | The new audio stack | Low Energy |
This split explains a common confusion: a fitness tracker that connects instantly and reports its battery, yet cannot play audio. It only speaks BLE, and audio has historically been Classic-only. LE Audio is now changing that, which is the subject of step 05.
The takeaway Classic and Low Energy share a name and a band and are otherwise separate systems. Classic streams; Low Energy wakes up, says something small, and goes back to sleep.
How audio actually gets there, and why it lags
Bluetooth audio is not a wire. The sound is compressed before it is sent and decompressed at the other end, and both of those take time. That time is why a video can look out of sync and why musicians will not use Bluetooth headphones.
CD-quality stereo is about 1.4 Mbps uncompressed. A Classic Bluetooth link realistically carries a few hundred kilobits per second once overhead and retransmissions are accounted for. The audio therefore has to be compressed, and the choice of compressor — the codec — is negotiated when the devices connect.
| Codec | Typical bitrate | Latency | Notes |
|---|---|---|---|
| SBC | 192–328 kbps | ~170–270 ms | Mandatory; every device has it |
| AAC | ~250 kbps | ~120–200 ms | Apple devices; efficient at low rates |
| aptX | 352 kbps | ~80–120 ms | Qualcomm; common on Android |
| aptX Low Latency | 352 kbps | ~40 ms | Made for video; needs both ends |
| LDAC | 330–990 kbps | ~150–200 ms | Sony; highest bitrate, least robust |
| LC3 | 160–345 kbps | ~20–50 ms | LE Audio; better quality at lower rates |
Where the delay comes from
Latency is not one thing. It accumulates through the chain, and no single part is unreasonable.
- The sending device gathers audio into a block — you cannot compress a sound you have not yet received. This alone costs several milliseconds.
- The codec compresses that block, which takes processing time on both the phone and, later, the earbud.
- The packet waits for its transmission slot in the hopping schedule.
- Lost packets are retransmitted, so the receiver holds a buffer of audio to play from while it waits. This buffer is the largest single contributor.
- The earbud decompresses and converts to analogue, then drives the speaker.
The buffer is the interesting trade-off. A large buffer means a dropout in a crowded room is invisible, because there is a reservoir of audio to keep playing from. A small buffer means low latency and an audible stutter every time a packet is lost. Manufacturers tune this differently, which is why some earbuds feel responsive and fragile while others feel laggy and unbreakable.
Why video is usually fine anyway
Two hundred milliseconds of delay would make lip-sync obviously wrong, yet Netflix on a phone looks correct. This is because Bluetooth reports its own latency to the source device, and the video player simply delays the picture to match. It works perfectly for recorded video and not at all for anything live — games, instruments, video calls — where the sound has to respond to you in real time.
Calls sound worse than music for a structural reason
Music uses A2DP, a one-way stream with a decent bitrate. The moment a call starts, the link switches to HFP, which is bidirectional — the microphone now has to send as well. That halves the capacity available in each direction, and older versions of HFP used a narrowband codec built for telephone speech.
The audible result is familiar: music playing beautifully, then the moment a call connects the quality collapses and stays collapsed until the call ends. LE Audio removes this by using the same codec in both directions.
The takeaway Audio is compressed, buffered against interference, and reassembled — and the buffer that makes it robust is the same thing that makes it late.
The parts that have genuinely changed
Bluetooth has a reputation built on how it behaved a decade ago. Several things have changed substantially enough that the old complaints are becoming out of date, even if the devices in your drawer have not caught up.
LE Audio moves audio onto Low Energy
Announced in 2020 and appearing in devices from around 2023, LE Audio finally moves audio off Classic Bluetooth. Its codec, LC3, delivers better quality than SBC at roughly half the bitrate — which translates directly into longer battery life or more robustness, whichever the manufacturer prefers.
LC3
Better sound at half the data rate, so either the battery lasts longer or the link becomes more resistant to interference.
True stereo
Each earbud receives its own stream directly, rather than one relaying to the other. Both last the same time and either can be used alone.
Calls stop degrading
The same codec is used in both directions, so a call no longer collapses the quality.
Auracast
One transmitter, unlimited receivers — the genuinely new capability.
Auracast is the interesting one
Every Bluetooth connection until now has been point to point. Auracast lets a device broadcast audio that any number of nearby receivers can tune into, rather like a radio station with a range of a room.
The applications are immediately obvious once you hear them: silent televisions in a gym or an airport that you listen to through your own earbuds; a museum tour with no borrowed handsets; a cinema broadcasting an audio description track; a lecture hall where the hearing aids in the room receive the microphone directly. That last one is the reason hearing aid manufacturers pushed hardest for it.
Direction finding
Bluetooth 5.1 added the ability to measure the angle a signal arrived from, using an array of aerials and the tiny phase differences between them. Combined with signal strength, this turns 'somewhere within ten metres' into a position accurate to tens of centimetres.
This is what allows a phone to point an arrow at a misplaced tracker rather than just getting warmer, and it is being used for indoor navigation in buildings where GPS cannot reach.
| Version | Year | What it added |
|---|---|---|
| 4.0 | 2010 | Low Energy — a separate technology under the same name |
| 4.2 | 2014 | Better privacy and larger packets |
| 5.0 | 2016 | Four times the range, or twice the speed, for BLE |
| 5.1 | 2019 | Direction finding to within centimetres |
| 5.2 | 2020 | LE Audio and the LC3 codec |
| 5.3 / 5.4 | 2021–23 | Efficiency, and encrypted broadcast to many devices |
| 6.0 | 2024 | Channel sounding — true distance measurement |
The takeaway Audio is moving to Low Energy, which fixes the call-quality collapse and adds broadcasting to unlimited listeners. Direction finding turns proximity into actual position.
Why it stutters in exactly the places it does
Bluetooth failures are not random. They happen on train platforms, in gyms, at conferences and while walking with your phone in the wrong pocket — and each of those has a specific, physical explanation.
Your body is mostly water, and water absorbs 2.4 GHz
This is not a metaphor — it is the same absorption a microwave oven exploits. A human body is an effective blocker at this frequency, which is why the classic Bluetooth failure is a phone in your right back pocket and an earbud in your left ear. The signal has to pass through you.
Move the phone to a front pocket or the other side and the problem usually disappears entirely. Earbud manufacturers work around this by having one bud relay to the other, or — with LE Audio — by sending to both independently.
Crowds are the hardest environment
A busy train platform might hold several hundred phones, wireless earbuds, smartwatches and fitness trackers, all hopping through the same 79 channels. Frequency hopping copes remarkably well with a handful of neighbours and progressively less well as the number climbs, because the chance that a hop lands on an occupied channel rises with every extra device.
| Situation | What is happening | What helps |
|---|---|---|
| Phone in the far pocket | Your body absorbs the signal | Move it to the near side |
| Busy station or gym | Hundreds of devices in the same band | Little — it is congestion |
| Next to the microwave | High-power leakage around 2.45 GHz | Move a few metres away |
| Near a busy Wi-Fi router | Wide Wi-Fi channels covering many hops | Move Wi-Fi to 5 GHz |
| Only when the laptop is on | USB 3 ports emit broadband noise at 2.4 GHz | Move the dongle or use an extension |
| Fine still, stutters walking | Changing geometry and body position | Reposition the source device |
The USB 3 problem is real and badly known
Unshielded USB 3 ports and cables emit a surprising amount of radio noise centred right around 2.4 GHz. A Bluetooth dongle plugged into the port next to an external drive can be swamped by it. Intel published a paper on this and the standard advice — move the dongle to a front port, or put it on a short extension lead away from the machine — genuinely works.
What Bluetooth does about interference on its own
Modern Bluetooth uses adaptive frequency hopping. Rather than using all 79 channels blindly, both ends keep track of which ones are consistently unreliable — because a Wi-Fi network is sitting on them — and take them out of the hopping pattern. The link narrows to the clear channels and stops wasting hops on the busy ones.
This is largely why Bluetooth and Wi-Fi coexist as well as they do, and why the advice to move your Wi-Fi to 5 GHz helps so much: it does not just reduce the interference, it hands Bluetooth back a third of the band.
The takeaway Six steps, 1,600 channel changes a second and adaptive avoidance of busy frequencies — and the most common cause of a dropout is still that you put your phone in the wrong pocket.