Concept renderLE Audio runs on the Bluetooth Low Energy radio and uses the LC3 codec, which replaces SBC for A2DP and mSBC for HFP voice on Android. Android 13 is the first release with built-in support, and the phone hardware must support it too. Pick the path by use: live voice, later file sync or playback.
A voice pendant, earbud or pair of glasses has three ways to move audio over Bluetooth. Classic A2DP and HFP are the established path. LE Audio with LC3 is the newer one. Plain BLE data moves files rather than audio streams. The right choice depends on whether the device streams audio live, syncs files later, or plays audio back to the wearer.
This guide uses only first-party statements from the Bluetooth SIG and Android Developers, as of October 31, 2026. Those pages publish no power or latency figures, so this guide has none either. Where a number is missing, the text says so and tells you what to measure. Voice capture products in this guide assume consented, visible capture with a clear indicator. This is an engineering summary. It gives no compliance or legal advice.
What do the official sources say?
Each row below paraphrases or quotes one statement from a first-party page, as of October 31, 2026.
| Topic | What the source says | Source |
|---|---|---|
| LE Audio radio and codec | Runs on the Bluetooth Low Energy radio and introduces the LC3 codec, described as high quality and low power. | Bluetooth SIG, as of October 31, 2026 |
| LC3 versus SBC quality | The SIG says LC3 improves audio quality over the SBC codec in Classic Audio. The page also carries a vendor quote about roughly half the bit rate. That wording is a statement on the SIG page. Nobody has measured it on your hardware. | Bluetooth SIG, as of October 31, 2026 |
| Power saving | The SIG says designers can use the saving for longer battery life or a smaller battery. It gives no current figures and does not discuss latency. | Bluetooth SIG, as of October 31, 2026 |
| First Android release | Android 13 (API level 33) includes built-in support for LE Audio. | Android Developers, as of October 31, 2026 |
| Codec mapping on Android | LC3 is the default codec and replaces SBC for A2DP (media) and mSBC for HFP (voice). | Android Developers, as of October 31, 2026 |
| Hardware dependence | Android exposes isLeAudioSupported(), which reports whether the device hardware supports LE Audio. Support depends on the OS version and on the individual phone hardware. | Android Developers, as of October 31, 2026 |
How do the three paths compare?
The table keeps the vendor-published facts and marks every gap. A gap means the vendor did not publish the figure, so it needs a measurement on your board.
| Path | Codec | Fits | Power and latency |
|---|---|---|---|
| Classic A2DP / HFP | SBC for media, mSBC for voice (the codecs LC3 replaces on Android) | Playback to the user, and live voice over the headset profile | Vendor did not publish figures in the sources we checked. Measure on your board. |
| LE Audio unicast with LC3 | LC3 for both media and voice on Android | Live voice streaming and playback, on phones with LE Audio hardware support | The SIG describes it as low power. No current or latency figures were published. Measure on your board. |
| Plain BLE data | No audio profile. Your firmware moves encoded audio as data. | Later file sync, where nobody listens live | Not covered by the sources we checked. Measure on your board. |
Codec mapping: Android Developers, as of October 31, 2026. The fit column is our engineering reasoning from that mapping and from how each path moves data.
Which path fits which use case?
| Use case | Path to evaluate | Phone gating | Basis |
|---|---|---|---|
| Live voice streaming to the phone | Classic HFP (mSBC), or LE Audio voice (LC3) when the phone supports it | Android 13 or later, and phone hardware that reports support. iOS: we could not confirm from a first-party page. | Android Developers, as of October 31, 2026 |
| Later file sync | Plain BLE data | Does not depend on LE Audio. Your app owns the transfer protocol. | Engineering reasoning |
| Playback to the user (earbud, glasses speaker) | Classic A2DP (SBC), or LE Audio media (LC3) when the phone supports it | Same phone gating as live voice. | Android Developers, as of October 31, 2026 |
Live voice is the real design fork. On Android, the Classic voice path uses mSBC and the LE Audio voice path uses LC3, so the two paths differ in codec as well as in radio behavior.
What pitfalls follow from the sources?
These items are engineering reasoning drawn from the statements above. They are not reports of any company's incident, and we have no measured results to report.
- OS version is not enough. Android reports hardware support per phone through isLeAudioSupported(). A phone on Android 13 or later can still lack support, so a list of supported OS versions overstates your reach.
- The bit-rate claim is not your result. The roughly half bit rate wording is a vendor quote on the SIG page. Treat it as a reason to test LC3. Keep it out of your battery budget until you measure.
- The power saving has no published size. The SIG describes the saving but gives no current figures. A battery plan built on it has an unsourced input until you measure.
- iOS is an open question in this guide. We could not confirm iPhone behavior from a first-party page. A design that assumes LE Audio on iOS carries an unverified assumption.
- Latency is undocumented in the sources. The SIG page does not discuss it. Anything that depends on how fast speech reaches the phone or the ear needs your own measurement.
- Support status can change. Android documentation is version-sensitive. Re-read the linked pages before you freeze a requirement.
What should you test on your own board?
We have not run these on your product, and this page reports no results. The pass line is yours to set per product requirement, and you should record the basis for it.
| What to test | How to instrument or capture | Raw data to record |
|---|---|---|
| Current draw per path | Power the board from a current-logging supply. Run the same audio scenario over Classic HFP, Classic A2DP, LE Audio unicast and BLE file sync. | Current trace per path, firmware build, module and SoC, radio settings, phone model, scenario length. |
| Mouth-to-ear latency | Play a known signal at the microphone and capture it at the phone or earpiece with a second recorder on a shared clock. | Both audio captures, the offset method, path, codec, phone model and OS version. |
| Phone matrix | Pair the device with Android phones that do and do not report LE Audio support, and with iPhones. Log what the phone reports. | Phone model, OS version, result of isLeAudioSupported(), connection outcome, audio path that was used. |
| Fallback to Classic | Connect to a phone without LE Audio support and start live voice. Log the profile that is negotiated. | Connection log, negotiated profile and codec, time to first audio, any user-visible error. |
| Voice quality per codec | Record the same speech through mSBC and LC3 in your enclosure, then run your speech-to-text on both. | Source audio, decoded audio from each path, transcript output, reference transcript, enclosure revision. |
| File sync behavior | Transfer a stored recording over BLE data with the screen off and the app in the background. | File size, transfer start and end times, interruptions, battery state before and after, phone model. |
| Capture indicator | Confirm the visible recording indicator is on whenever audio is captured, on every path. | Indicator state log against the audio capture log, firmware build. |
What should you decide before you choose?
Take this list to your firmware team, your module vendor or any team building the product for you, including us.
- Does the device stream audio live, sync files later, play audio back, or more than one of these?
- Which phones must work on day one, and have you checked LE Audio hardware support on each?
- What is the confirmed iPhone behavior, from Apple's own documentation and your own tests?
- If a phone lacks LE Audio, what should the device do, and who tests that path?
- Which published figures are you relying on, and which still need a bench measurement?
- What latency does the product need, and where did that requirement come from?
- Does the product make a visible indication whenever it captures audio?
- Which Bluetooth stack and SDK will you use, and does its own documentation give power figures you can check?
Questions about LE Audio and Classic Bluetooth
What is the difference between LE Audio and Classic Bluetooth audio?
LE Audio runs on the Bluetooth Low Energy radio and introduces the LC3 codec. Classic Audio uses the SBC codec for media. The Bluetooth SIG says LC3 improves audio quality over SBC. As of October 31, 2026. Bluetooth SIG, LE Audio.
Which Android version supports LE Audio?
Android 13 (API level 33) is the first release with built-in LE Audio support. The phone hardware must also support it, and Android exposes isLeAudioSupported() to check at runtime. As of October 31, 2026. Android Developers, LE Audio overview.
Does iPhone support LE Audio?
We could not confirm it from a first-party page, so this guide makes no claim either way. Check Apple's current documentation and test on real iPhones before you commit the product to LE Audio on iOS.
Do I need LE Audio if my device only syncs recordings later?
Not for the sync itself. A device that stores audio and transfers it later can move it as plain BLE data, so the transfer does not depend on phone LE Audio support. You still need LE Audio or Classic if the device plays audio back to the user or streams live voice. This point is our engineering reasoning. No vendor page states it.
What happens if the phone does not support LE Audio?
On Android the check is per phone, so some phones will not support it even on a supporting OS version. Whether your device falls back to Classic automatically is a design and test item for your product, and we have no measured result to report. Android Developers.
Choosing the Bluetooth audio path for a voice wearable? Tell us about your device. For how we scope this kind of product, see AI recording wearable development and our engineering approach.
Primary sources
Both pages were accessed on 2026-10-31. Bluetooth support changes with releases, so confirm on the live pages.
- Bluetooth SIG, LE Audio (bluetooth.com/learn-about-bluetooth/recent-enhancements/le-audio), accessed 2026-10-31.
- Android Developers, LE Audio overview (developer.android.com/develop/connectivity/bluetooth/ble-audio/overview), accessed 2026-10-31.
Planning an AI recording wearable? Tell us what it needs to do. A Duobay engineer replies within 1 business day. Send a project brief →