A teardown of the second Android 17 QPR2 beta has surfaced a hidden feature called Voicecast, according to Android Authority. The Google Pixel Voicecast feature would let Pixel phones broadcast a user's live voice over Bluetooth, a capability their phones currently lack: existing Pixel audio-sharing tools handle music and video, but not a microphone feed.
The Android 17 QPR2 Voicecast toggle lives inside developer options and isn't publicly enabled. Everything known about it so far comes from this teardown; Google hasn't discussed the feature publicly or said which Pixel models might eventually get it.
Pixel phones already support an Auracast-branded feature called Audio sharing, but it only handles media playback: music, podcasts, and video, not a live microphone feed. Samsung's earlier Auracast implementation shared media audio. One UI 8.5 renamed the feature Audio Broadcast and added broadcasting through the phone's microphone.
The build Android Authority found is clearly unfinished, with rough edges included. That's still a meaningfully different situation than a feature glimpsed only in marketing copy or a leaked roadmap slide.
What is the Google Pixel Voicecast feature?
Voicecast turned up in the second Android 17 QPR2 beta after Android Authority enabled it through developer options during testing. Switching it on adds a Voicecast tile to Quick Settings. Tapping that tile opens a setup window for starting a broadcast.
From there, users can create either a public or private channel. Both require a broadcast name; private channels also demand a password, a setup that echoes what Samsung already offers on Galaxy phones.
Once a broadcast starts, the window gains "mute" and "end" buttons. The mute button is supposed to silence the microphone without ending the session, but in this beta it simply ends the broadcast instead.
How Pixel Voicecast Bluetooth audio sharing could work
Voicecast appears to extend Pixel's existing Bluetooth audio-sharing framework, though the teardown doesn't confirm every implementation detail, including whether it runs on the identical Auracast pipeline that powers Audio sharing today. What's established is Auracast's basic design: it's part of the Bluetooth LE Audio standard and supports one-to-many broadcasting, meaning a single source can send audio to multiple compatible devices at once instead of pairing with just one.
Google's existing Audio sharing only transmits media audio. Voicecast would add a second input source, the phone's microphone, letting a Pixel owner speak to a nearby audience without any extra hardware beyond the phone itself.
Android Authority describes the potential reach as broadcasting to an unlimited number of nearby people, provided each listener has a Bluetooth LE Audio-compatible device. Existing Pixel Audio sharing sessions connect via a QR code scan or a Fast Pair tap rather than a manual Bluetooth pairing process.
When Google expanded Auracast eligibility on Pixel phones in September 2025, it pointed to guided tours, airport announcements, gym televisions, and shared podcasts as examples of where one-to-many broadcasting is useful. Android Police described that expansion as a step toward making broadcast audio a mainstream feature rather than a niche perk. Voicecast appears to build on that same groundwork, extending a pipe built for streaming media so it can also carry a live voice feed.
Pixel Voicecast vs Samsung's Audio Broadcast
Samsung's version of this has existed on Galaxy phones for some time. Under One UI 8.5, it's called Audio Broadcast; earlier versions, running One UI 6.1 through 8.0, called it Auracast. According to Android Authority, it already lets Galaxy owners share both media and voice with nearby LE Audio devices.
Samsung's own support documentation confirms the mechanics of the broadcast setup itself: users name a broadcast, can optionally lock it with a password, and nearby listeners with compatible headphones, such as the Galaxy Buds3 Pro, can tune in once they enter that password. On Galaxy devices, listeners can search for broadcasts through the phone and the Galaxy Wearable app.
If Voicecast ships, the "speaker" role wouldn't require a Galaxy phone or separate broadcasting hardware. A Pixel owner could act as the source using just the phone already in their pocket.
Google grouped itself alongside Xiaomi and Samsung 11 months ago as offering "full Auracast support" on recent phones. Voice broadcasting specifically has remained a Samsung advantage that Pixel couldn't match, at least until this teardown surfaced.
What's known about Voicecast hardware and rollout
Google's existing Auracast rollout covers the Pixel 8 series and newer, alongside compatible phones from Samsung and Xiaomi, but the company hasn't said which models, if any, will get Voicecast specifically. Listener compatibility adds a separate requirement: both the broadcasting phone and the receiving earbuds or hearing aids need Bluetooth LE Audio support. Confirmed compatible listening devices include the Pixel Buds Pro 2, Galaxy Buds 3 and Buds 3 Pro, and select Sony, Sennheiser, and JBL products.
Google's own history with Auracast shows that broad hardware eligibility hasn't guaranteed a clean rollout. When Android 16 first reached the Pixel 9 series, Auracast wasn't enabled by default and required a manual toggle in developer options; Google later made the feature available by default in Android 16 QPR1. The Pixel Buds 2a shipped without Auracast support at all.
Reporting also turned up two unexplained gaps. Auracast was disabled on the Pixel Buds Pro 2 when paired with a Pixel phone; a Reddit user found that resetting the phone's Bluetooth settings restored it, and testing with a non-Pixel device confirmed the block lived on the phone side rather than the earbuds.
Separately, Android Authority enabled Auracast on a rooted Pixel 9a and confirmed that model's omission was a software restriction rather than a hardware limitation, though that finding was specific to the Pixel 9a rather than the entire A-series lineup.
Asked about the inconsistencies, a Google spokesperson told Android Authority the company had "nothing new to share about Auracast at this time." Android Authority has also reported that Samsung has pushed Auracast support across a wider range of its own phones, tablets, earbuds, and TVs than Google has managed so far.
What to watch
Voicecast, as it exists in the current beta, is a hidden, unfinished feature with a mute button that ends broadcasts instead of muting them. There's no announced timeline for a public release.
Three questions matter heading into the stable Android 17 QPR2 release. Whether Voicecast survives outside developer options at all. Which Pixel models actually get it. And whether Google offers clearer eligibility information this time around than it did with Audio sharing, whose rollout left users guessing why some earbuds worked and others didn't.
Comments
Be the first, drop a comment!