Google has essentially declared a persistent speakerphone bug affecting its Pixel 9 and Pixel 10 smartphones as unfixable, frustrating many owners [1] [2]. The bug causes a severe lag or failure when toggling the speakerphone during calls, and despite months of complaints, the company has opted not to issue a software patch, citing insufficient diagnostic data [3].
- Laggy speaker toggle: Pixel 9 and Pixel 10 users report that pressing the speakerphone icon during a call often lags (sometimes by up to 2 seconds) or doesn’t respond at all [4]. This makes it hard to switch to speaker mode without interrupting the conversation.
- Started in May 2025: The issue emerged after Google introduced a new Phone app interface in May 2025. Pixel 9 devices first saw the bug after that update, and the problem carried over to the newly launched Pixel 10 series [5]. Even the latest Android 16 builds (including beta releases) have not resolved it.
- Google’s “Won’t Fix” response: In late October, Google closed an official issue tracker report on this bug with a status of “Won’t Fix (Infeasible),” saying there wasn’t enough “actionable information” to address it [6] [7]. The company advised affected users to file new reports with more data, effectively putting the onus back on customers.
- User frustration & workarounds: Pixel owners are disappointed that a basic calling feature is glitchy on premium phones [8]. Many are sharing workarounds (like using the speaker toggle in the notification shade or reverting to an older app version) to cope with the bug while they wait – hopefully – for Google to revisit the issue [9] [10].
Speakerphone Bug Plagues Pixel 9 and Pixel 10
Reports across Reddit and Google support forums show that Pixel 10, Pixel 10 Pro XL, and the previous Pixel 9 series are all affected by this glitch [11]. When users tap the speakerphone button during a phone call, the phone sometimes takes one to two seconds to switch audio output, or it fails to switch at all unless pressed repeatedly [12]. The Pixel community first noticed the bug on Pixel 9 phones in mid-2025 after a Google Phone app update redesigned the call interface. Notably, Google rolled out sweeping UI changes to its dialer app in May 2025, around when these speakerphone issues began [13]. The launch of the Pixel 10 later in the year didn’t eliminate the problem – in fact, Pixel 10 owners found the same laggy toggle on their brand-new devices, indicating the bug is tied to the software, not the hardware [14].
Users have confirmed that the issue spans multiple software versions. It shows up on both stable Android 16 builds for Pixel 10 and on the latest Android 16 QPR2 beta releases [15]. This suggests the culprit is likely the Google Phone app’s new in-call user interface rather than a specific Android OS bug. One telling clue: some users report that if they revert to an older version of the Phone app (with the previous interface), the speakerphone button responsiveness goes back to normal [16]. This points to Google’s revamped dialer UI as the source of the delay, possibly due to some inefficient processing in the new design.
Interestingly, the bug does not occur when using the speakerphone toggle from the call notification shade (the mini call controls that appear in the notification bar) instead of the full-screen call interface [17]. One Reddit user noted that tapping the speaker icon in the notification drop-down activates speaker mode immediately with no lag [18]. This workaround suggests the problem lies specifically in the Phone app’s in-call screen UI, not in the core calling functionality. Other community findings have reinforced this theory: the audio hardware and Android audio routing seem to work fine, since the toggle responds instantly via notifications or third-party apps. It’s the Pixel dialer’s interface layer that appears to be introducing a bottleneck.
Google Acknowledges Bug but Won’t Fix It (Yet)
After months of user reports, Google finally acknowledged the speakerphone toggle bug through its official Issue Tracker – but not in the way users hoped. A Pixel user filed a formal bug report in late August 2025, providing logs and descriptions of the problem [19]. Google’s support team responded and monitored the issue for a while, even requesting additional diagnostic data from users. By October 19, 2025, however, Google marked the issue as closed with a “Won’t Fix (Infeasible)” status, effectively declaring that no software update was planned for it [20].
“We’re closing this issue due to not having enough actionable information,” the Google representative wrote in the issue tracker update [21]. “If you continue to have this issue, please file a new issue and add the relevant information along with a reference link to the earlier issue.”
In other words, Google claimed that they couldn’t reproduce or pinpoint the bug internally due to a lack of data, and thus wouldn’t be patching it at this time [22]. They marked the case as “Won’t Fix (Infeasible)” on October 20, 2025, essentially shelving the problem unless new evidence emerges [23]. This was a blow to affected Pixel 9 and 10 owners, especially those with the latest Pixel 10 devices. The Pixel 10 series was only a few months old at that point, yet users were being told that a core calling feature glitch would not be immediately resolved [24].
Google’s official stance has caused consternation in the Pixel community. Many found it alarming that Google would stop short of fixing a basic functionality bug on its flagship phones. Some community members pointed out that this is not a niche or obscure bug – it impacts everyday usage like taking calls on speakerphone for hands-free conversations. “It’s pretty disappointing for a $1,000 phone that’s brand new,” one user wrote on Reddit, echoing a widespread sentiment that Google should prioritize a fix rather than asking users for more data.
Google’s advice to “file a new issue with more information” also frustrated users, who felt they had already provided ample reports since May. Nonetheless, Google’s decision implies that the burden is on users now: unless enough new bug reports with detailed logs are submitted to convince Google’s engineers to take another look, the speakerphone lag may persist indefinitely [25]. For now, no official patch or timeline for a fix has been offered.
It’s worth noting that this speakerphone bug, while annoying, isn’t a safety issue – and that may be part of why Google triaged it the way they did. In the past, Google has moved swiftly to fix critical problems (for example, a Pixel 9 Pro bug affecting 911 emergency calls got urgent attention) [26]. By contrast, a laggy speaker button is seen as a minor inconvenience rather than a show-stopper. Still, long-time Pixel fans argue that premium phones should get polish as well as innovation. The Pixel 10 line boasts cutting-edge AI features and camera tech, yet such basic glitches undermine the user experience and trust in Google’s quality control.
Frustrated Users Turn to Workarounds
Pixel 9 and 10 owners have not been shy about voicing their frustration. On forums like Reddit and Google’s support site, countless threads chronicle the annoyance: calls put on speaker take extra seconds to connect, leading to awkward silences or confusion on the other end. Some users who frequently toggle speakerphone (for instance, to drive hands-free or join conference calls) find the bug especially aggravating – a daily nuisance on phones that cost top dollar. “It feels like we’re beta testing a device we paid full price for,” one commenter lamented, reflecting the feeling that Pixel users are often guinea pigs for Google’s software quirks [27].
Rather than wait indefinitely for an official fix, the community has crowdsourced various temporary solutions and workarounds to deal with the speakerphone toggle bug. Here are a few measures Pixel users are taking to mitigate the issue:
- Use the notification shade toggle: Instead of tapping the speaker icon on the call screen, swipe down to the call notification and tap the speaker icon there. This method bypasses the faulty in-call UI and activates speaker mode instantly with no lag [28].
- Revert the Phone app update: Some users have rolled back to an older version of the Google Phone app (pre-May 2025 update) which uses the previous interface. Doing so has been reported to restore the speaker button’s responsiveness [29]. This involves uninstalling updates or sideloading an older APK and disabling auto-updates for the Phone app.
- Try alternative in-call actions: A few tricks can improve responsiveness on the current app. For example, double-tapping the speakerphone button sometimes gets it to register on the second tap [30]. Likewise, keeping the Phone app in a minimized window or switching to landscape orientation during the call (instead of the normal portrait fullscreen) has helped some users avoid the delay [31]. These methods likely reduce the new UI’s glitchy behavior, though results vary.
- Switch to a third-party dialer app: As a last resort, some have tried using alternative phone dialer apps (from the Play Store) that don’t exhibit the speaker lag [32]. While the experience may not be as seamless as Google’s stock app, it can be a useful stopgap for those who rely heavily on speakerphone calls.
None of these workarounds are ideal or permanent – they’re band-aids until Google issues an official fix (if it ever does). Users must weigh the inconvenience of the bug against the hassle of workarounds like app downgrades or third-party tools. For many, simply using the notification shade toggle has become second nature to avoid the lag.
Outlook: Will Google Revisit the Issue?
For now, Google’s position is that no fix is forthcoming unless new information emerges. The speakerphone toggle bug remains in limbo, marked as “infeasible” to solve based on the data Google has. That said, the story might not be over. If enough Pixel 9/10 owners continue to submit bug reports with logs and feedback, Google could potentially reopen the investigation [33]. There’s precedent for bugs being revisited after public pressure – especially if a future Android update exacerbates the issue or if a high-profile tech discussion draws attention to it.
Pixel users and industry watchers will be keeping an eye on Google’s monthly software updates. It’s conceivable (though not guaranteed) that a future patch or Phone app update could quietly improve the speakerphone responsiveness. Google tends to bundle dozens of fixes in its Pixel Feature Drops and security updates, so a fix could slip in if the engineers identify the root cause. Hope remains that Google will eventually prioritize this nagging bug, especially as new complaints keep surfacing from Pixel 10 owners who expect flagship-level stability [34].
In the meantime, affected users are encouraged to report the issue through official channels (and include diagnostic info) to help Google gather actionable data [35]. It’s an extra step that many wish wasn’t necessary, but it may be the only way to get Google’s attention back on this problem.
Ultimately, this episode underscores a key point for Pixel enthusiasts: cutting-edge features and AI tricks are great, but the basics need to work flawlessly. A laggy speakerphone button is not a headline-grabbing failure, but it’s an everyday irritant that impacts real-world use. As Google moves forward with the Pixel lineup, users will be looking for reassurance that such issues are addressed in a timely manner – so that innovation doesn’t come at the cost of reliability [36] [37]. Pixel 9 and 10 owners love their phones’ capabilities, and they’re simply asking for the fundamentals (like phone calls) to work without a hitch. Google’s next steps – or lack thereof – on this speakerphone bug will be telling for how it balances new features with polish in its user experience.
In the absence of an immediate fix, Pixel users have adapted with workarounds and persistence. The ball is now in Google’s court to respond to its users’ concerns. Will an upcoming update finally deliver relief for the speakerphone bug? Pixel fans certainly hope so [38]. For now, they’ll be watching each monthly patch closely and making their voices heard, determined not to let this glitch be swept under the rug.
References
1. www.androidcentral.com, 2. www.nextpit.com, 3. www.bgr.com, 4. piunikaweb.com, 5. piunikaweb.com, 6. www.bgr.com, 7. www.androidauthority.com, 8. www.androidcentral.com, 9. www.androidauthority.com, 10. piunikaweb.com, 11. piunikaweb.com, 12. piunikaweb.com, 13. www.nextpit.com, 14. piunikaweb.com, 15. piunikaweb.com, 16. piunikaweb.com, 17. piunikaweb.com, 18. piunikaweb.com, 19. piunikaweb.com, 20. www.androidauthority.com, 21. www.bgr.com, 22. www.bgr.com, 23. piunikaweb.com, 24. www.bgr.com, 25. www.bgr.com, 26. www.bgr.com, 27. android.gadgethacks.com, 28. piunikaweb.com, 29. piunikaweb.com, 30. piunikaweb.com, 31. www.nextpit.com, 32. piunikaweb.com, 33. www.bgr.com, 34. piunikaweb.com, 35. www.bgr.com, 36. www.webpronews.com, 37. www.webpronews.com, 38. piunikaweb.com
