Bluetooth keeps cutting out because the link is a narrow, shared, unlicensed radio channel that loses its turn when something louder crowds it out. A 2.4 GHz signal at roughly 0 dBm must compete with Wi-Fi, USB 3.0 noise, microwave leakage, and even the water in your hand. When the packet misses its scheduled slot, the audio buffer runs dry and you hear silence. That is the physical mechanism. Everything that follows is a variation on it.

Bluetooth audio is not a wire with an invisible cable. It is a timed radio schedule carrying compressed frames with a few dozen milliseconds of slack. When people say the connection "cuts out," they are usually describing one of three things: a dropout from radio interference, a choppy stutter from buffer starvation, or a reconnect loop from power or pairing problems. These have different fixes, which is why random troubleshooting advice so often fails.

Classic Bluetooth splits the 2.4 GHz band into 79 channels, each 1 MHz wide, hopping about 1,600 times per second. Bluetooth Low Energy uses 40 channels at 2 MHz. The hop is not random. It adapts to avoid bad channels, a feature called adaptive frequency hopping. When Wi-Fi occupies a chunk of the band, the radio tries to skip those channels. The avoidance has limits, and that limit is where dropouts begin.

The audio path adds a buffer. SBC, the mandatory codec, runs at roughly 200–345 kbps and gives the system a few tens of milliseconds to recover a missed packet. A single lost frame can be masked by retransmission. A burst of lost frames cannot. When the buffer empties, the decoder has nothing to play, and you get a click or a gap. This is why interference shows up as intermittent clipping rather than a clean disconnect.

There is a second timing layer. Bluetooth schedules traffic in slots, and audio gets reserved slots so voice and music stay continuous. If a competing radio steals those slots, the audio job is deferred. Deferral is invisible until it exceeds the buffer. The phone, headset, and router are all negotiating for the same airtime without talking to each other, because none of them owns the band.

Quantifying the interference

A common Bluetooth radio transmits near 0 dBm to 10 dBm, which is a small fraction of a watt. Wi-Fi access points commonly operate at 15–20 dBm, and a nearby router can be over 100 times stronger in linear power terms than the earbud. Distance matters more than raw power: radio energy falls off with the square of distance, so moving a router two feet can change the picture.

The band overlaps around 2.400–2.4835 GHz in the US. Wi-Fi channels are wide, at 20, 40, 80, or 160 MHz, while Bluetooth channels are 1–2 MHz. A single 80 MHz Wi-Fi channel covers a third of the Bluetooth band at once. Adaptive hopping helps, but when a wide channel sits over the band, the escape routes shrink.

USB 3.0 is a frequently missed source. Its connectors and cables can radiate broadband noise centered near 2.4 GHz, and that noise is not a coordinated signal that hopping can dodge. The interference is local and physical, often strongest within a foot of the cable. The symptom is distinctive: dropouts only when a drive or dock is active.

Timeline: what happens in the first 300 milliseconds

Time Event What you perceive
0 ms Radio slot assigned to audio Nothing
1–2 ms Wi-Fi burst or USB noise corrupts the frame Nothing yet
10–20 ms Retransmission attempt fails Nothing yet
20–40 ms Buffer level falls below the safety margin A tiny click, often unnoticed
40–100 ms Adaptive hopping skips the bad channel Brief recovery
100–200 ms Repeated interference overwhelms retries Audible stutter
200–300 ms Buffer empties and decoder starves Silence or a gap

The exact numbers vary by codec and device. The structure is consistent: interference is absorbed for a short window, then becomes audible. That is why the first symptom is rarely a disconnect. It is a stutter you might blame on the music file.

Edge cases that break the usual explanation

Some dropouts are not radio problems at all. Here are the counterintuitive cases worth checking before you move the router.

Power delivery fallback: A headset that negotiates a weak charging state can brown out its radio. The dropouts cluster when the battery is low or the case is nearly empty. Multipoint contention: When one headset connects to a laptop and phone at once, both links share the radio. Audio can cut when the second device pings for attention. Codec mismatch: A device forced into a high-bitrate codec over a congested link has less buffer headroom, so it stutters earlier than a low-bitrate codec would. Antenna detuning: A hand, a metal desk, or a phone case over the antenna shifts its tuning and cuts range by half without any new interference source. Firmware asymmetry: The phone and earbud may run different Bluetooth stack versions, and a known-good pairing can regress after only one side updates.

One professional caveat: a dropout that survives every radio change may be a scheduling bug in the host stack, and no amount of router moving will fix it.

What people get wrong about Bluetooth dropouts

The most common misconception is that range is the problem. Bluetooth Classic is rated for about 10 meters in open air, and Low Energy for roughly 30–100 meters depending on the PHY. In a room, walls and bodies cut that considerably. But most desk dropouts happen within a meter, where range is irrelevant and interference dominates.

A second misconception is that pairing problems are connection problems. If the device disappears from the list entirely, the radio link is fine and the pairing record is corrupt. If it stutters but stays connected, the radio link is degraded. These are different failure modes with different remedies.

A third is that more antennas or a newer phone will solve it. The host radio is often not the weak point. The earbud has a tiny antenna and a small battery, and the body absorbs 2.4 GHz energy. The limiting factor is frequently the far end, which is why one headset drops and another does not on the same phone.

A fourth is that "Bluetooth 5" means a stable link. The version number describes capabilities like longer range modes, not the quality of your environment. A Bluetooth 5.3 earbud next to a noisy dock will still stutter.

Practical actions with thresholds

Start with the cheapest test that isolates the cause. Move the phone and earbud at least three feet from any USB 3.0 cable, dock, or active external drive. If dropouts stop, the cause was local noise, not distance. This single check resolves a large share of desk setups.

Then check the buffer symptom pattern. If audio cuts for under a second and recovers, treat it as interference. If it disconnects and requires a manual reconnect, treat it as pairing or power. If it cuts only during calls, suspect the call audio profile, which uses a lower-quality bidirectional codec with tighter timing.

Concrete steps and thresholds:

Put the router's 2.4 GHz radio on channels 1, 6, or 11 and keep the earbud at least six feet away when possible. Disable 40/80/160 MHz width on 2.4 GHz if the router allows it; narrower channels leave more hop room. Keep the earbud within 10 meters of the phone in open space and within roughly 5 meters through one interior wall. Charge the headset above 20 percent before a long call; low-battery radio fallback is real. Remove the phone case if it covers the antenna area, and avoid holding the phone against your body during a call. Update firmware on both ends, then re-pair rather than just reconnecting. If dropouts persist, reset the network settings on the phone and re-pair from scratch.

Reconciling the thresholds: the 10-meter figure is an open-air rating, the 3-foot USB check is a noise field test, and the 20 percent battery figure is a conservative floor. They address different failure modes, so a device can pass one and fail another. Use them as a sequence, not a single score.

Limits of what this explains

No article can diagnose your specific dropout without seeing the spectrum around you, and Bluetooth has no built-in interference log a consumer can read. The mechanism here explains the common cases and the shape of the fixes. It does not prove which source is active in your room.

A phone's Bluetooth settings often hide codec and profile details, so you may be unable to confirm which codec is running. The adaptive hopping behavior is also opaque, and the host stack may override it. Intermittent firmware bugs on either end cannot be seen from the outside and may require the manufacturer's logs.

If you have tried the noise isolation, channel changes, firmware updates, and re-pairing in that order and dropouts continue, the remaining likelihood is a hardware fault in the earbud antenna or the phone radio. That is a warranty question, not a settings question. General educational information only; for a persistent hardware fault, consult the device manufacturer or a qualified repair professional.