I spotted a fresh r/GooglePixel thread where a Pixel 10 Pro XL owner says their phone connected to 911, but the audio that came back was a harsh mix of garbled beeps, screeches, and faint human fragments, not a normal voice line. The poster says they tried four times, then grabbed a Pixel 7 on the same carrier in the same spot and got through immediately with clear audio, which makes the behavior on the new phone feel deliberate rather than random.
Another commenter with a Pixel 10 reported the same result the night before, which is what pushed this beyond a one‑off tale for me. Every other call reportedly sounds normal on the Pixel 10, so the symptom appears tied to emergency calling, not day‑to‑day voice quality, at least in these cases.
Right away, I saw people in the comments drag in the Pixel’s history with emergency calling, including a community‑compiled list of failures since 2022 and 2023’s PSA noting that some owners still couldn’t dial 911 during emergencies on select models, which is why emotions run hot the second a new report lands.
To be clear, what is being described here is different from the prior failures where the phone would hit the call screen and never connect, because in this thread the call connects but the line turns into noise, a crucial distinction that changes both diagnosis and stakes. That nuance matters, since several commenters were talking past each other about “same old Pixel 911 issues,” which risks blurring a new symptom with an older, already‑patched cause.
It is also important not to confuse this with the widely publicized 2021 bug, which Google traced to an interaction with the Microsoft Teams app that could prevent a 911 call from completing at all, a problem Microsoft and Google addressed with updates in early 2022.
The new reports do not read like that, since the 911 call connects here, only the audio is broken, which points away from the old Teams stack issue and toward something else in the chain. In the thread, readers float ideas like RTT/TTY toggles, Wi‑Fi calling, and modem or carrier interplay, and the original poster later mentions using Google Fi while another commenter on Verizon said their Pixel 10 got through fine, which hints at possible carrier variability rather than a universal device failure.
So far, the thread shows just two concrete reports of the same symptom, which means this could still be a network issue rather than a widespread flaw, and there is no reason to panic based on what is visible today.
If a check is needed, schedule a test through the local non‑emergency line, which 911.gov recommends, instead of placing unscheduled tests that could tie up resources or lead to penalties in some jurisdictions. Google’s feedback path is available from Settings, About phone, Send feedback, and loading the ticket with call times, carrier, and location details gives engineers something to chase, which several commenters in the thread also urged.
The bottom line here is that this is a new‑looking 911 behavior on Pixel 10, not the old “can’t dial at all” bug, and it might be limited to certain networks, but it deserves a quick investigation, so count on us to keep watching the thread and related reports as more data lands.
If you have placed a real 911 call on a Pixel 10, please share what happened in the comments below, including carrier, Wi‑Fi calling, and SIM setup, so the community can spot patterns faster and separate signal from noise.