Imagine being in the middle of an important call, needing to switch to speakerphone for privacy, only to find the button doesn’t respond—or worse, lags just long enough for everyone around you to overhear something you’d rather keep private. This is the frustrating reality for Pixel 9 and Pixel 10 users, who’ve been grappling with a persistent bug in the Google Phone app’s speaker button. But here’s where it gets controversial: Google has officially stated it won’t fix the issue, leaving users wondering why they’re paying premium prices for flagship devices with unresolved flaws.
The problem first surfaced with the Pixel 9 series last year and has carried over to the Pixel 10 lineup. Users report that tapping the speaker button during calls often results in a delay of up to two seconds—or worse, no response at all. For instance, one Pixel 10 Pro XL user shared their exasperation on Google’s community support page, explaining how they sometimes need to tap the button multiple times before the call switches to the external speaker. This isn’t just an inconvenience; it’s a disruption to everyday functionality, especially for those who rely on speakerphone for work or personal calls.
And this is the part most people miss: The issue persists whether the device is running the stable Android 16 build or the latest Android 16 QPR2 Beta 3.2 update. It’s not an isolated glitch but a recurring problem that dates back to May 2024, when a Pixel 9 Pro user first flagged the “noticeable lag” after pressing the speaker icon. By September, a Pixel 10 Pro XL user took to social media to vent, noting that while other buttons worked flawlessly, the speaker toggle required frantic tapping to function—if it worked at all.
Interestingly, some users have reported that reverting to an older version of the Google Phone app resolves the issue, suggesting the bug may stem from recent updates. Yet, despite widespread complaints, Google’s Issue Tracker labeled the problem “Won’t Fix (Infeasible)” in October, citing a lack of actionable information. This decision has left many users feeling abandoned, especially since the workaround—using the notification toggle instead of the in-app button—feels like a clumsy Band-Aid for a premium device.
Here’s the burning question: Is Google prioritizing convenience over customer satisfaction? For Pixel owners who shelled out for a flagship experience, this unresolved bug feels like a betrayal. While Google’s stance may be technically justified, it raises broader concerns about accountability and user experience. Shouldn’t a company of Google’s caliber be able to fix a bug affecting a core feature? Or is this a sign of deeper issues in their software development process?
As one Redditor, cliffr39, aptly put it, “I just want the speakerphone icon to actually work right when I press it.” It’s a simple ask, yet one that remains unfulfilled. For now, Pixel 9 and 10 users are left hoping for a miracle—or at least a change of heart from Google. But until then, the workaround remains: avoid the Google Phone app’s speaker button like the plague.
What do you think? Is Google justified in not fixing this bug, or should they prioritize resolving it for their users? Let us know in the comments—this is one debate that’s far from over.
