Android 17's stable release for Pixel phones arrived in June 2026 with a list of well-publicized features—but a buried toggle in Developer Options reveals something else entirely. Tucked away and unmentioned in official release notes, support for the LHDC v5 Bluetooth audio codec has quietly landed on Pixel devices. The addition means Pixel users can now stream high-resolution, low-latency audio over Bluetooth without relying on third-party accessories or per-device licensing, a shift that challenges the dominance of Qualcomm’s aptX and Sony’s LDAC.

LHDC, short for Low Latency High-Definition Audio Codec, is an advanced Bluetooth codec developed by Savitech and certified by the Japan Audio Society for Hi-Res Audio Wireless. Version 5, finalized in 2024, builds on previous iterations with improved transmission efficiency, lower latency (targeting under 30ms), and support for 24-bit/192kHz audio at up to 1Mbps bitrate. It also introduces adaptive bitrate streaming that dynamically adjusts to interference and distance, plus multi-stream support for true wireless earbuds. For Pixel users, this means out-of-the-box access to studio-grade wireless audio—provided they know where to look.

The discovery first surfaced on enthusiast forums and Reddit in the days after the Android 17 OTA hit Pixel 6 and newer devices. Users poking through Developer Options noticed a new entry under the Bluetooth audio codec selection menu: “LHDC” and “LHDC (HD)”. Selecting it on devices paired with LHDC-capable earbuds or headphones instantly delivered perceivably richer audio. One early tester with a Pixel 9 Pro and a pair of Xiaomi Buds 4 Pro reported “noticeably wider soundstage and tighter bass compared to AAC” when streaming Tidal Masters. Initial logs confirmed the codec negotiating at 24-bit/96kHz with a stable 900kbps connection.

Why would Google embed such a significant feature without a word? The answer likely lies in the complex licensing and certification landscape. LHDC, while open in the sense that it does not require per-device licensing fees like aptX, still requires device makers to pass certification to use the logo and branding. Google’s official support documentation for Pixel’s Bluetooth codecs still lists only SBC, AAC, aptX, aptX HD, LDAC, and LC3. By leaving LHDC out of the release notes, Google may be walking a fine line, offering the underlying support without making a splash while certification deals with LHDC’s governing body remain under wraps. It’s a pattern we’ve seen before—previous Pixel feature drops have included experimental codec support that later graduated to full user-facing features.

Enabling LHDC v5 on a Pixel running Android 17 is straightforward but requires a few taps off the beaten path. First, dive into Settings > About phone, and tap “Build number” seven times to unlock Developer Options. Navigate to System > Developer Options, scroll to the Bluetooth Audio Codec section, and you’ll see the new entries. They’re available only when a compatible audio sink is connected; otherwise, they default back to system-selected codecs. This design ensures the codec is only offered when beneficial, preventing connection instability.

The practical impact is substantial for audiophiles and casual listeners alike. LHDC v5’s adaptive technology means it can scale from 192kHz/24-bit luxury down to 48kHz/16-bit during interference, all without audible dropouts. In a side-by-side comparison using identical FLAC tracks and a FiiO BTR7 DAC, LHDC v5 over a Pixel 8a edged out LDAC in both latency (28ms vs 42ms) and objective signal-to-noise ratio under controlled conditions, though the margin narrowed at extreme distances. For gamers, that sub-30ms latency is a game-changer, enabling wireless audio that rivals wired headsets in responsiveness—a metric where Bluetooth has historically stumbled.

Compared to LDAC, which has long been the high-bitrate king on Android, LHDC v5 offers a more modern codec design that better handles coexistence with Wi-Fi and other 2.4GHz traffic. Where LDAC’s 990kbps mode often stutters in crowded RF environments, LHDC’s adaptive algorithm can dial down to 400kbps seamlessly without the audio glitches that plague LDAC’s fallback to 660kbps or 330kbps. For dense urban environments or busy offices, LHDC’s resilience gives it a clear edge. And unlike Qualcomm’s aptX Adaptive, which requires both phone and headphone chipset-level support, LHDC can be implemented in software on the source device—hence its appearance on Pixel hardware without a Snapdragon Sound badge.

The Windows connection here is tantalizing. Microsoft has gradually expanded Bluetooth codec support in Windows 11, adding AAC and aptX, but LHDC remains absent from the official codec stack. If Google’s grassroots approach pressures headphone makers to adopt LHDC more widely, Windows users stand to benefit when those same peripherals are paired with a laptop or desktop. Already, community projects like Alternative A2DP Driver enable LHDC on Windows, but native support would streamline the experience. Pixel’s hidden inclusion might be the nudge that brings LHDC to mainstream Windows audio, much as LDAC’s ubiquity on Android convinced Sony to open its encoder to Windows developers.

Google’s silence might also hint at future Pixel Buds plans. The current Pixel Buds Pro rely on AAC and, more recently, LC3 for LE Audio. Integrating an LHDC transmitter into Android 17 lays the groundwork for a future Google-branded audio accessory that can fully exploit the codec’s capabilities. A “Pixel Buds Pro 2” with LHDC v5 would instantly become the best way to experience lossless audio wirelessly from a Pixel phone—a narrative that fits with Google’s increasing emphasis on premium ecosystem lock-in.

For now, the LHDC v5 support remains an open secret. It’s absent from Google’s developer documentation and support pages, and strings referencing the codec inside the OS lack the usual consumer-friendly labels. Yet the fact that it’s present in a stable, publicly rolled-out build suggests it’s more than a forgotten debug flag. Typically, such codecs are gated behind system properties and stripped from production firmware until they’re ready. Its survival through the final release candidate implies a deliberate decision to include it, even if unadvertised.

Users should exercise a modicum of caution. When testing new codecs, some Bluetooth accessories may behave erratically. Early adopters on forums have noted that some LHDC-capable devices require a firmware update to properly negotiate the Pixel’s implementation, and connection drops were spottier with older LHDC v3 headphones. Savitech maintains a list of certified LHDC v5 headphones, which includes recent models from Xiaomi, Edifier, and Shanling. Sticking to that list minimizes hiccups.

As the Android 17 rollout continues across all supported Pixel models—from the Pixel 6 to the newest foldables and tablets—the LHDC v5 codec will land in millions of pockets. It’s a quiet revolution for mobile audio, one that elevates the Pixel from a competent media player to a hi-fi transport that can challenge dedicated digital audio players. With the codec’s presence buried but fully functional, the ball is now in headphone makers’ court to seize the opportunity and market their LHDC compatibility to Pixel owners. Until then, a few taps in Developer Options unlocks a feature that redefines what wireless audio can do on a Google phone.