Time and again I’ve said how the greatness that is Google Pixel software is occasionally pulled back by a few niggly bugs that show up now and then, some even nearly impossible to explain how they came about.

For instance, not long ago, a bug that has been affecting Pixel users of the Marvelous Marble wallpaper since 2018 was fixed. Prior to that, AT&T Pixel units had also experienced a Google Pay-related issue that forced Google to halt updates.

We’ve also seen other strange bugs like a dead sensor, Spotify alarm, LTE/data roaming on Sprint, broken bottom speaker, call end/charging sound, and so on.

For Pixel 3a and Pixel 3a XL owners, the nightmare that is the speakerphone bug has been here for months. Several software updates have been pushed to the handsets since the bug was first reported in December 2019, but none of them has managed to address the issue.

Google-Pixel-3a-speakerphone-bug
(Source)

I have had my Pixel 3a XL for a few months now. I have never dropped my device or have had any accidents. Just the regular daily wear and tear of putting in pocket. But, today my bottom speakers went out. No audio of some sort. I’ve tried everything, from playing music to streaming videos. You can only hear audio from the top speaker.

Then I noticed, when I receive a phone call or text message, my notification sound or ringtone is muted on both speaker. Putting someone on Speakerphone during a call, cuts the audio. I’ve also went to the sound settings and checked the ringtone and notification sounds. Normally when you select a sound or tone, you would hear a preview of the selected sound. No sound either.

So I went onto the next step and factory reset my device. I figured it could be some software issues. After factory reset, bottom speaker is still not outputting any audio. Anyone else have this issue? What can I do to fix this problem. Thanks!
Source

Months down the line, the Pixel 3a speakerphone issue is still showing up, even on replaced units. The comment below, one of many made hours ago, shows the issue is still here.

Wow, I had this problem couple of months ago, I sent my phone back and they change it with a new one. Today the same thing happened with the new one too. I’m gonna return this phone!
Source

The fact that the issue remains unaddressed even after several software updates says a lot. But the concerning bit is where the issue still persists even on new models. If anything, this could only mean one thing – that the speakerphone issue is hardware-related.

Matter of fact, a Google Product Expert in the community forums said back in February that this is likely a hardware-related issue, suggesting that affected users should send their units back for Google to review the hardware.

Please contact Google to review the hardware. This sounds like a hardware issue.

Pixel-3a-speaker-audio-hardware-related
(Source)

The big G hasn’t come out to officially acknowledge this issue, so it remains to be seen what next. We will keep an eye on the story and let you know when we have fresh developments.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.

Hillary Keverenge
2088 Posts

Tech has been my playground for over a decade. While the Android journey began early, it truly took flight with the revolutionary Lollipop update. Since then, it's been a parade of Android devices (with a sprinkle of iOS), culminating in a mostly happy marriage with Google's smart home ecosystem. Expect insightful articles and explorations of the ever-evolving world of Android and Google products coupled with occasional rants on the Nest smart home ecosystem.

Next article View Article

[Updated] Instagram crashing on all Android phones, but there are workarounds

Here's the crux of the article in video form: New updates are being added at the bottom of this story……. Original story from (June 5, 2018) follows: We're...
Jul 10, 2023 6 Min Read