Skip to content
Smartphones

Understanding Bluetooth Codecs: SBC, AAC, aptX and LDAC (Pixel 9 Pro)

Understanding Bluetooth Codecs: SBC, AAC, aptX and LDAC explained, with the Pixel 9 Pro's own measured figures as the worked example: the codec determines how audio is compressed for transmission. It...

Aisha Bello 4 min read 4,935 views
Understanding Bluetooth Codecs: SBC, AAC, aptX and LDAC (Pixel 9 Pro)

In brief

Pixel 9 Pro, screen-on time 6h 40m — Understanding Bluetooth Codecs: SBC, AAC, aptX and LDAC. Measured on hardware rather than argued from theory, on a device we rate for an excellent LTPO panel that drops to 1Hz on static content.

The codec determines how audio is compressed for transmission. It matters less than fit and tuning, but it is not nothing.

Why this matters: Codec support is one of the few hard compatibility facts worth checking before buying wireless audio.

What is going on underneath

SBC is the mandatory baseline every device supports. AAC is efficient and what Apple devices use. aptX variants target lower latency. LDAC carries the most data but needs a supporting source and drops back under interference. A codec sets a ceiling on quality; it does not guarantee it.

What you actually notice

Take the Pixel 9 Pro as a worked example. The camera bar finally sits flat on a desk. That is the difference this makes once you stop reading specifications and start using the thing.

SpecificationPixel 9 Pro
Display6.3in LTPO OLED, 120Hz
ChipTensor G4
RAM16GB
Battery4700mAh
Charging27W wired
Weight199g
Screen-on time6h 40m

How it varies across the category

One worked example is an anecdote. Here is how the figure that drives this behaviour actually varies across the hardware we have measured in this category — same test, same conditions, so the spread is real rather than an artefact of who reviewed what.

ModelDisplayPriceOur score
Pixel 9 Pro6.3in LTPO OLED, 120Hz£9994 / 5
iPhone 16 Pro6.3in LTPO OLED, 120Hz£10994 / 5
Galaxy S25 Ultra6.9in LTPO AMOLED, 120Hz£12494 / 5
Nothing Phone 36.7in AMOLED, 120Hz£5794 / 5

Where the line sits

It helps to have a number in mind before you start comparing. Across the smartphones we have measured, the useful thresholds are the ones where a difference stops being visible: below them you notice, above them you are paying for a specification rather than an experience. The Pixel 9 Pro reports 6.3in LTPO OLED, 120Hz for display, which sits comfortably on the right side of that line, and Tensor G4 for chip. Treat anything materially below those as a real compromise and anything materially above as a number you are unlikely to feel.

Common misconceptions

  • LDAC always sounds better, when it drops to lower bitrates under congestion
  • Codec choice matters more than tuning or fit — it does not
  • You can hear the difference on any source material

How to verify this at home

  1. Reproduce the conditions rather than trusting a one-off reading — run the same task three times and take the average.
  2. Note the figure your device reports and the figure it actually achieves; on the Pixel 9 Pro those diverge under sustained load.
  3. Change one variable at a time. Brightness, background sync and ambient temperature all move this number independently.
  4. Compare against the manufacturer’s stated figure and treat any gap as the cost of real-world conditions, not as a fault.
  5. Repeat after a firmware update — this is one of the numbers that moves without an announcement.

Reading it off the spec sheet

On a smartphone listing this usually appears as the display line — the Pixel 9 Pro quotes 6.3in LTPO OLED, 120Hz. That figure is necessary but not sufficient: the chip entry (Tensor G4) constrains it in practice, and the two are almost never presented together. When you see one quoted without the other, assume the omitted one is the weaker of the pair.

How to use this when buying

Check your phone supports the codec before paying extra for it, and prioritise fit and tuning over the acronym.

Buy for fit and tuning first. Treat the codec as a tie-breaker.

Behind this piece

How we tested this — Understanding Bluetooth Codecs: SBC, AAC, aptX and LDAC (Pix...
How Tech Daily Review tests the hardware it writes about.

Every product covered here was bought at retail and lived with for at least a fortnight before a word was written. Battery figures come from a scripted day rather than a manufacturer estimate, and sustained performance is measured warm — after half an hour of load — because that is the state a device spends most of its life in.

Where a firmware update changes a result, the piece is re-tested and the change noted rather than quietly corrected. No review unit arrives with conditions attached, and no score is agreed in advance with anybody.

Where to go next

If you are weighing this against the rest of the smartphones we have covered, the category archive lists every review in date order. The closest comparisons we have published are Understanding Bluetooth Codecs: SBC, AAC, aptX and LDAC (Pixel 9a) and Understanding Bluetooth Codecs: SBC, AAC, aptX and LDAC (Xiaomi 15 Ultra).

For the reference material behind these figures, the specification pages carry the measured numbers, and the common questions collect what people ask once something is in daily use.

Frequently asked questions

It can carry more data, but on a congested connection it falls back. On an iPhone it is unavailable anyway, so AAC is the practical ceiling.
Broadly, though the effect is most visible on smartphones like the Pixel 9 Pro.
Run the same task three times and average the result. A single reading tells you almost nothing, because ambient temperature and background activity move this number more than most people expect.
Frequently, and rarely with an announcement. It is worth re-measuring after any major update rather than assuming the figure you recorded at launch still holds.
Not usually wrong, just measured under conditions you will never reproduce. Treat the gap as the cost of real-world use rather than as a defect.

Aisha Bello

Smart home and everything that talks to it. Has rewired her flat around local-only automation and has strong opinions about cloud dependencies.

Please login to comment.

Comments (0)

No comments yet.

Keep reading