Google Quietly Adds LHDC v5 High-Resolution Bluetooth Codec to Android 17 Pixel Builds

Google has quietly rolled out native support for Savitech’s LHDC v5 Bluetooth audio codec in the stable release of Android 17 for Pixel phones, arriving in June 2026. The update lets compatible Pixel models stream high-resolution wireless audio—up to 24‑bit/192 kHz—directly to earbuds and headphones without needing third‑party apps. For audio enthusiasts, it’s a leap forward in Bluetooth sound quality that pushes the envelope past aging standards like aptX and AAC, and for the first time brings a genuine alternative to Sony’s LDAC into the core of Google’s mobile OS.

What Is LHDC v5 and Why It Matters

LHDC stands for Low Latency High‑Definition Audio Codec, developed by Taiwanese semiconductor company Savitech. It’s one of only a handful of codecs certified by the Japan Audio Society for High‑Resolution Audio Wireless transmission, alongside LDAC and some proprietary implementations. Version 5 of the codec, introduced in 2024, ups the ante with support for sampling rates up to 192 kHz at 24‑bit depth, a scalable bitrate that can peak at over 1 Mbps, and adaptive algorithms that juggle bitrate, latency, and error correction based on radio conditions.

The real‑world promise is straightforward: more musical detail, a wider soundstage, and fewer compression artifacts during wireless playback. Where older codecs like SBC compress audio aggressively—often throwing away frequencies above 16 kHz—LHDC v5 aims to preserve the full audible spectrum and then some. Its low‑latency mode, typically dipping below 30 ms, also makes it viable for gaming and video without lip‑sync problems.

Android 17’s Implementation: A First for AOSP‑Based Phones

Until now, LHDC support on Android was a patchwork affair. Smartphone manufacturers like Xiaomi, OPPO, and OnePlus have included it in their custom firmware for years, but it never landed in the Android Open Source Project or Google’s own Pixel builds. Users who wanted to stream LHDC to their high‑end earbuds either had to buy a non‑Pixel phone or rely on beta‑quality codec injection apps that required root access.

Android 17 changes that. The June 2026 stable update bakes the codec directly into the Bluetooth stack on Tensor‑powered Pixels. In developer options, a new “HD Audio: LHDC” toggle appears, and the system automatically negotiates the highest‑quality connection when a supported accessory is paired. Early reports from testers indicate that the handshake is seamless—pair an LHDC‑capable earbud, and the phone immediately switches to the codec, with a notification badge confirming the active streaming mode.

What’s notable is that this is not a Play Services add‑on or a Pixel Feature Drop gated behind regional flags. The support is native, compiled into the system image. That gives it deeper integration with the audio pipeline, lower power consumption, and the possibility of future enhancements through monthly security patches.

Which Pixel Phones Get the Upgrade?

Google hasn’t issued a formal compatibility list, but Android 17’s system requirements hint that all Tensor‑based Pixels dating back to the Pixel 6 family are eligible for the over‑the‑air update. In practice, LHDC v5’s high bitrate demands a modern Bluetooth radio and sufficient processing horsepower, so the feature is likely to be enabled on devices with at least a Tensor G3 or newer chipset—think Pixel 8, 9, and the 2026 range. The Pixel Fold and Tablet may require separate validation.

Early adopters on Reddit and XDA Developers confirm that after sideloading the stable build, their Pixel 8 Pro and Pixel 9 handsets automatically negotiated LHDC v5 when connected to Audeze Maxwell and Sennheiser Momentum 4 headphones that had received firmware updates to enable LHDC. Older Pixels, such as the Pixel 7a, reportedly see the toggle greyed out, suggesting hardware limitations in the Bluetooth controller.

LHDC v5 vs. Other High‑Resolution Codecs

To understand where LHDC v5 slots into the hierarchy, a quick comparison of the dominant high‑quality Bluetooth codecs is useful.

LHDC v5 outruns LDAC on paper: higher sampling rate ceiling, lower latency, and adaptive bitrate that can scale up when the wireless channel is clean. In practice, LDAC’s “best effort” 990 kbps mode often stutters outside ideal environments, while LHDC v5’s adaptive algorithm should maintain a more stable connection without manual quality tier selection.

The Real‑World Impact on Audio Quality

For the average listener, the jump from AAC or aptX to LHDC v5 is analogous to moving from a 128 kbps MP3 to a lossless FLAC file—provided their earbuds can resolve the difference. Budget true‑wireless buds won’t suddenly sound like reference monitors, but mid‑range and high‑end products with decent drivers and digital‑to‑analog converters now have a wireless pipeline that doesn’t bottleneck the source material.

Streaming services that offer lossless or high‑resolution tiers—Tidal, Qobuz, Apple Music, and Amazon Music HD—stand to benefit the most. On a Pixel phone, Android’s mixer can pass through native sample rates, avoiding the resampling that often muddies the output. Combine that with LHDC v5’s high bitrate, and the result is a perceptible increase in clarity, separation, and bass definition.

Critically, because LHDC v5 is bidirectional in its latest spec, future firmware updates could also enable microphone input at high resolution, improving voice call quality—though no earbuds currently use this for calls.

Windows Users: An Unexpected Ripple Effect

Windows enthusiasts might wonder why this matters to them. The short answer: it doesn’t—yet—but it could. Microsoft’s desktop OS remains surprisingly stingy with Bluetooth codec support. Out of the box, Windows 11 handles SBC and AAC, and with compatible hardware it can fall back to aptX. LDAC is absent unless you install third‑party drivers or use a dedicated USB Bluetooth transmitter. LHDC support is completely off the radar.

Google’s move to bless LHDC v5 on Pixel phones doesn’t directly alter Windows, but it does reshape the accessory market. Earbud and headphone makers who want to be “Google‑approved” or feature in the Pixel ecosystem will now have a strong incentive to include LHDC v5 in their firmware. Once enough audio products support the codec, pressure may build on Microsoft to license and implement it in a future Windows 11 update—or on chipmakers like Qualcomm and Intel to include it in bundled Bluetooth stacks.

In the meantime, Pixel phone owners who also use a Windows laptop will face an asymmetric audio experience: high‑resolution LHDC on the phone, but a downshift to AAC or SBC when those same earbuds connect to the PC. It’s a gap that power users may close with external DACs or dedicated Bluetooth transmitters, but it underscores the fragmentation still plaguing the Bluetooth audio world.

What This Means for the Bluetooth Audio Ecosystem

Native LHDC v5 on Pixel is a strategic counterweight to Sony’s LDAC dominance. LDAC, while excellent, is tied to Sony’s licensing program and has seen adoption primarily on Android handsets because Apple refuses to support it. LHDC, by contrast, is positioned as an open‑standard alternative, though it too requires licensing from Savitech. Google’s endorsement—even if Pixel market share is modest—signals to the industry that LHDC is ready for prime time.

We’re likely to see a fresh wave of wireless earbuds and headphones branding themselves with “LHDC v5” logos, much as we saw with “LDAC” in previous years. Chinese manufacturers like Edifier, SoundPEATS, and FiiO, which already have LHDC‑equipped models, will now have an easier time marketing to Pixel users. More importantly, the codec’s presence in AOSP means custom ROMs on other phones might eventually unlock it, broadening the installed base.

For audiophiles, choice is always a plus. Having two viable high‑resolution codecs—LDAC and LHDC—available on the same phone ensures that no single earbud brand gets a monopoly on sound quality. It also encourages codec developers to keep pushing bitrates and reducing latency.

Looking Ahead

Android 17’s LHDC v5 integration is more than a bullet point on a changelog. It’s a quiet declaration that high‑res wireless audio shouldn’t be a premium extra; it should be built into the platform. While Pixel users are the immediate beneficiaries, the ripples will spread.

Microsoft, too, should take note. As the ecosystem around LHDC expands, Windows’ outdated Bluetooth codec support will look increasingly inadequate. A future where a cheap pair of earbuds can deliver lossless‑quality audio over Bluetooth is coming—and if Redmond doesn’t prepare, PC users will be left with last‑decade sound. For now, Android 17 and a compatible set of LHDC v5 headphones are the clearest window into that high‑fidelity wireless future.