A2DP: The Fire Hose
The Advanced Audio Distribution Profile was ratified in 2003, when Bluetooth headsets were mono earpieces for phone calls and the idea of streaming CD-quality stereo to a pair of over-ear cans was science fiction. A2DP was designed for one job: push audio from a source to a sink, one direction, no acknowledgments, no guarantees.
The protocol runs over Bluetooth Classic, the original BR/EDR radio that has powered every wireless headphone you have ever owned. Audio gets encoded with the SBC codec, a mandatory fallback that every Bluetooth device must support. SBC can push up to 328 kbps of stereo audio. At that rate, it sounds acceptable. At 192 kbps, which is what many phones actually negotiate down to in congested 2.4 GHz environments, it sounds like someone threw a blanket over your speakers.
The deeper problem is architectural. A2DP streams audio in a single direction. There is no acknowledgment mechanism at the audio transport layer. The source device has no idea whether the headphones received the last packet, dropped it, or are buffering through a packet storm. The headphones have no way to request a retransmission. If the radio environment degrades, the audio simply degrades with it. Gaps get filled. Artifacts accumulate. The protocol shrugs.
For 22 years, this was the best we had.
The Isochronous Channel
LE Audio, finalized by the Bluetooth SIG in 2020 and now shipping in real products, does not improve A2DP. It replaces it. The new architecture is built on Bluetooth Low Energy, the same radio that runs your fitness tracker and your smart door lock, and it introduces something A2DP never had: a transport layer that knows whether your headphones got the data.
The mechanism is called the isochronous channel. The word comes from Greek: "iso" meaning equal, "chronos" meaning time. Isochronous data arrives at its destination at a precise, fixed rate, and it has a finite lifetime after which it becomes invalid. If a packet of audio data arrives 50 milliseconds late, it is worse than useless. It is a click, a pop, a discontinuity in the waveform. The protocol throws it away.
There are two flavors. The Connected Isochronous Stream, or CIS, handles point-to-point audio: your phone to your headphones. The Broadcast Isochronous Stream, or BIS, handles one-to-many: a TV in a sports bar broadcasting to every pair of headphones in the room. Both are built on the same radical idea that A2DP lacked: audio packets are perishable freight, and the transport layer should treat them that way.
Two Bits That Change Everything
Inside every CIS packet header, there are two fields that do more work than anything in A2DP's entire specification: the Sequence Number (SN) and the Next Expected Sequence Number (NESN). Each is a single bit. They toggle between 0 and 1.
When your phone sends an audio packet with SN=0, your headphones receive it and respond with a packet whose NESN=1, meaning "I got SN=0, send me SN=1 next." If the phone does not see that response, or sees NESN=0 (meaning "I did not get your last packet"), it resends.
This is acknowledgment-based flow control, and it is absurdly simple. Two bits. But those two bits give the transport layer something A2DP never had: knowledge. The source knows what was received. The sink knows what to expect next. Retransmissions happen at the Link Layer, in microseconds, before the audio buffer runs dry.
A2DP had no such mechanism. It sent audio into the void and hoped.
The Group That Syncs Your Left and Right
Here is where the architecture gets genuinely clever. Your true wireless earbuds, or your over-ear headphones with separate left and right drivers, need synchronized audio. A2DP handled this badly. Classic Bluetooth can only maintain one audio stream per connection, so true wireless earbuds used a relay system: the phone sends everything to the right earbud, and the right earbud forwards the left channel to the left earbud. This adds latency, drains battery on the relay side, and desyncs when the relay link degrades.
CIS solves this with the Connected Isochronous Group, or CIG. A CIG groups multiple CIS channels under a single timing reference. Your phone sets up two CIS channels inside one CIG: one for the left channel, one for the right. Both channels share the same clock. The headphones receive both streams and present them to the audio DACs at the same instant, synchronized to within 10 to 15 microseconds.
No relay. No forwarding. No asymmetric battery drain. The phone talks to both earbuds directly, and the protocol guarantees they play in lockstep.
The BIS side has its own grouping mechanism: the Broadcast Isochronous Group, or BIG. A BIG wraps multiple broadcast streams under a shared timing reference, so a single transmitter can push different audio streams, different languages, different content, and every receiving headphone locks onto the stream it wants. There is no pairing. There is no connection. The receiver synchronizes to a periodic advertising train, reads the BIG info, and starts consuming isochronous packets. If a packet is lost, the protocol retransmits it in a subsequent sub-event within the same isochronous interval. No acknowledgments, because there is no one to acknowledge. The transmitter just sends it again.
LC3: Half the Bits, Better Sound
The isochronous channels carry audio encoded with LC3, the Low Complexity Communication Codec. LC3 is mandatory for every LE Audio device, the same way SBC was mandatory for A2DP. But the comparison ends there.
For stereo audio at 48 kHz and 16-bit depth, SBC typically runs at 328 kbps. LC3 delivers comparable quality at 160 kbps. At the same bitrate, LC3 is dramatically better, especially in the midrange and lower frequencies where SBC turns to mush. At 248 kbps, SBC sounds broken. LC3 at 248 kbps sounds clean.
The codec supports frame durations of 7.5 and 10 milliseconds, sampling rates from 8 kHz to 48 kHz, and bit depths of 16, 24, and 32 bits. It can handle an unlimited number of audio channels. LC3plus, the extended variant, scales up to 345 kbps and adds support for higher-resolution audio.
The efficiency matters because LE Audio runs over the Low Energy radio, which is designed to sleep between transmissions. Less data means less airtime. Less airtime means less power. A pair of headphones that previously needed 20 hours of Classic radio time can achieve the same audio quality with a fraction of the radio duty cycle. That is either longer battery life or a smaller battery. Probably both.
The Dual-Mode Mess
If this sounds like a clean transition, it is not.
The problem is that every Bluetooth audio device in the world still runs A2DP. Your car. Your old speaker. Your parents' TV. LE Audio cannot talk to any of them. So headphone manufacturers are building dual-mode devices: Classic Audio and LE Audio, side by side, in the same pair of headphones. Two complete Bluetooth audio stacks. Two sets of codec implementations. Two connection management systems. All sharing one antenna and one 2.4 GHz radio.
The results have been rough. Some headphones that support LE Audio lose multipoint capability when LE Audio mode is enabled. The Sony WF-1000XM5, a flagship product, warns users that turning on LE Audio disables multipoint. Users report random dropouts where one earbud stops playing and requires a disconnect-reconnect cycle. Windows 11 has been slow to adopt LE Audio at the OS level, leaving headphone manufacturers to ship their own USB dongles.
The root cause is that A2DP and LE Audio are not two versions of the same protocol. They are two completely different architectures running on two different Bluetooth radios. The Classic BR/EDR radio and the Low Energy radio share a frequency band but almost nothing else. Supporting both means maintaining two independent state machines, two independent connection managers, and two independent audio pipelines. It is not a firmware patch. It is a fork in the stack.
What Your Next Headphones Will Do
Qualcomm's Snapdragon Sound Elite Gen 2 platform, announced at Snapdragon Summit 2026, is the first chip platform designed to make dual-mode feel seamless. It supports LE Audio natively, handles LC3 encoding and decoding in dedicated DSP hardware, and brings gaming latency below 48 milliseconds. It also includes on-device AI processing, which is a separate story entirely.
Nothing's Headphone (a), launched earlier this year, ships with LE Audio support alongside LDAC and Classic Bluetooth. Samsung's Galaxy Buds line has been gradually enabling LE Audio features. Apple has reportedly begun LE Audio support in iOS 26.
The transition will take years. A2DP is not going away. It will live alongside LE Audio the way IPv4 lives alongside IPv6, quietly handling the devices that do not know anything has changed. But inside the newest headphones, the isochronous channel is already running. Two bits at a time, checking whether you heard what it sent, and resending if you did not.
A2DP sent audio into the void for 22 years. The void is starting to answer back.


