Database Info

Intermittent freeze and no sound when making calls: hardware or software issue?

For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.

davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.

reyscott said:
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.
Click to expand...
Click to collapse
It has to be at a point now to contact the OEM. On countless occassions I've factory reset and gone to different ROMs from scratch with the issue returning. Thanks.

Hats off to Verizon! I had purchased their total protection plan awhile back where you warrant your phone for 11 bucks a month. If it's lost or stolen you pay a deductible. With this issue I was hesitant but went in anyways.
For one, I didn't have to pay anything because I brought it in on the premise that it's a manufacturer defect (microphone hardware issue). Now if they determine my phone is damaged, the warranty company charges you 299. Mine won't be.
I go in yesterday and they told me I'll be receiving the replacement at my house TODAY. I even got the FedEx shipping memo for it being delivered tonight. Then I can just sent my old one in the same box that's a prepaid label.
Super happy about this!

No Sound
davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC

cc999 said:
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC
Click to expand...
Click to collapse
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.

New Pixel
davidisflash said:
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.
Click to expand...
Click to collapse
What's the manufacture date of the new phone?
CC

cc999 said:
What's the manufacture date of the new phone?
CC
Click to expand...
Click to collapse
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.

davidisflash said:
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.
Click to expand...
Click to collapse
better than having a broken phone. I was under the impression that the newer replacements came from google and were unlockable, but I guess only a lucky few,

Bluetooth not working

Not sure if this is just my phone but bluetooth has not been working the last update of 7.1.2 and Android O the most recent version. When I toggle bluetooth it does not activate and i have tried clearing out the cache. Not sure if this is a software issue or possible related to hardware. I did have a good drop with my phone although nothing on the exterior appears damaged. Not sure if anyone else is experiencing the same thing.

Just RMAing the phone. It appears that it is only my phone doing it. Actually Google's customer service is really good. I'm glad I bought from them.
I had a Galaxy S4 from Samsung in 2013 and the battery ended up swelling and I called them for a replacement which they would not replace, but would thoughtfully sell me a new battery. Then they lost $5.3 billion from their Note 7 recall due to the battery and I was very happy and laughed.

Was this just the phone audio in your car by chance? I have a similar issue and have an open case with google about it.

marc.ientilucci said:
Was this just the phone audio in your car by chance? I have a similar issue and have an open case with google about it.
Click to expand...
Click to collapse
No it's definitely the phone. I have my Nexus 5x right now on 8.0 and it's working fine. Nothing wrong with the software.
I use Android auto as well and it's working fine. There's something wrong with the hardware component in the phone most likely. I have a 2017 Honda Civic
Did an RMA and sending it out.

mikeprius said:
No it's definitely the phone. I have my Nexus 5x right now on 8.0 and it's working fine. Nothing wrong with the software.
I use Android auto as well and it's working fine. There's something wrong with the hardware component in the phone most likely. I have a 2017 Honda Civic
Did an RMA and sending it out.
Click to expand...
Click to collapse
sorry - let me clarify my question. Was bluetooth media working and just not phone calls over bluetooth? I have a 2017 honda civic as well (LX version so a dumb head unit) and only having bluetooth phone call issues. I can play spotify and other stuff like youtube just fine.

marc.ientilucci said:
sorry - let me clarify my question. Was bluetooth media working and just not phone calls over bluetooth? I have a 2017 honda civic as well (LX version so a dumb head unit) and only having bluetooth phone call issues. I can play spotify and other stuff like youtube just fine.
Click to expand...
Click to collapse
No. Bluetooth would not activate at all so nothing worked. When i toggled the switch it would not turn on and scan for bluetooth. It appears that my situation was much significant as nothing worked. My replacement should be here tommorow. For your stock rooted set up did you just boot into TWRP then flash the latest SU ? Lately I've been running stock, so I don't know what the most recent form to root is for 8.0
Last time I rooted was like April or May of this year, but I just booted the TWRP image, flash TWRP, then flash SU

I've been stock rooted for some time but for the 8.0 update I rooted with SuperSU SRS3 via TWRP. Google had me actually grab a bug report and shoot it over to them along with information about the bluetooth radio manufacture of the car. I am cool with continuing to help them out. anyway, thanks for your feedback and i hope the new one works!

Got my new pixel replacement. It was the phone, I'm on the latest 7.1.2 update and it's working fine. The refurb looks brand new, you can tell it's a refurb by the charging port, but the rest of the phone is virtually new. No scratches on the glass or scuffs on the metal body. Compared to the current pixel I have with multiple long scratches along the front glass screen, even though it's a refurb its still in much better condition than my current Pixel.
I noticed my night light is super orange the screen is compared to my current Pixel. I think this is an issue related to earlier batches of the Pixel. It's just very orange with the night light but given the condition my current pixel is in, I'll still take it over my current one.

What Custom ROM that fixes Microphone Issue?

As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1

chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once

jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?

chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems

If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software

That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.

I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.

UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.

UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2

I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.

chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.

jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)

zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........

Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?

mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse

abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.

Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.

mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good:

Google Pixel Mic and Speakers not working

Hi, the speakers and microphone on my Google pixel do not work and I also noticed that video recording and the Google Assistant would refuse to work as well. My pixel also fails to recognise that a headphone has been connected to the the headphone jack. I got this phone second hand from someone but they told me they had factory reset the phone but the speakers and microphone would still not work so I think it is a hardware issue.
Help would be greatly appreciated thank you ?

jameskim153 said:
Hi, the speakers and microphone on my Google pixel do not work and I also noticed that video recording and the Google Assistant would refuse to work as well. My pixel also fails to recognise that a headphone has been connected to the the headphone jack. I got this phone second hand from someone but they told me they had factory reset the phone but the speakers and microphone would still not work so I think it is a hardware issue.
Help would be greatly appreciated thank you ?
Click to expand...
Click to collapse
It's a hardware defect affecting pixel devices produced before January 2017. It would eventually happen to the phones produced in 2016 and there's no way to tell when it would happen. Only fix is to change the motherboard. If you're able to return the phone then do it.

Arju said:
It's a hardware defect affecting pixel devices produced before January 2017. It would eventually happen to the phones produced in 2016 and there's no way to tell when it would happen. Only fix is to change the motherboard. If you're able to return the phone then do it.
Click to expand...
Click to collapse
Unfortunatly I bought a second hand pixel and did not know this issue until I tried to use audio. I'm trying to repair it myself and I read in another forum that replacing the headphone jack or the mic/speakers would solve the problem. Do I need to buy another mother board and replace it with the current one I have right now?

jameskim153 said:
Unfortunatly I bought a second hand pixel and did not know this issue until I tried to use audio. I'm trying to repair it myself and I read in another forum that replacing the headphone jack or the mic/speakers would solve the problem. Do I need to buy another mother board and replace it with the current one I have right now?
Click to expand...
Click to collapse
I personally have not done any such procedure so would let someone else answer. What I could do is to identify when your phone was produced to narrow down if that could be the issue. If that's the same then the motherboard needs changing and you might just find a beaten up working pixel for cheap and try swapping the parts unless you find the motherboard for cheap though. Could go to settings>system>about phone>status>serial number. Give is the 5 first characters. Mine is FA77M. I could read from this that it's produced in taiwan on the 21st-07-2017.

Arju said:
I personally have not done any such procedure so would let someone else answer. What I could do is to identify when your phone was produced to narrow down if that could be the issue. If that's the same then the motherboard needs changing and you might just find a beaten up working pixel for cheap and try swapping the parts unless you find the motherboard for cheap though. Could go to settings>system>about phone>status>serial number. Give is the 5 first characters. Mine is FA77M. I could read from this that it's produced in taiwan on the 21st-07-2017.
Click to expand...
Click to collapse
It says that my serial number is FA69H

jameskim153 said:
It says that my serial number is FA69H
Click to expand...
Click to collapse
FA – Taiwan Taoyuan B factory
69H - 2016-September-17th.
Your device is probably suffering from motherboard issues unfortunately.

Arju said:
FA – Taiwan Taoyuan B factory
69H - 2016-September-17th.
Your device is probably suffering from motherboard issues unfortunately.
Click to expand...
Click to collapse
I saw some units @ the shop as I'm looking to buy one. Are any of these safe from mic problem? Some of it is still nougat. Thank you!
FA6A6
FA69H
FA69G

Hiyaslalabs said:
I saw some units @ the shop as I'm looking to buy one. Are any of these safe from mic problem? Some of it is still nougat. Thank you!
FA6A6
FA69H
FA69G
Click to expand...
Click to collapse
FA6A6 - Produced in Taiwan Taoyuan B factory - 2016-October-6th
FA69H - Produced in Taiwan Taoyuan B factory - 2016-September-17th
FA69G - Produced in Taiwan Taoyuan B factory - 2016-September-16th
From what I understand, all devices produced in January 2017 and after should have this issue fixed. Pixels made in 2016 is pretty much a ticking "bomb"... someday the issue will occur. I personally would stay away from the devices you mentioned. If you find a device with the third character being 7 then you should be safe. My device is FA77M which reads - Produced in Taiwan Taoyuan B factory - 2017-July-21st, which should be safe.

Arju said:
FA6A6 - Produced in Taiwan Taoyuan B factory - 2016-October-6th
FA69H - Produced in Taiwan Taoyuan B factory - 2016-September-17th
FA69G - Produced in Taiwan Taoyuan B factory - 2016-September-16th
From what I understand, all devices produced in January 2017 and after should have this issue fixed. Pixels made in 2016 is pretty much a ticking "bomb"... someday the issue will occur. I personally would stay away from the devices you mentioned. If you find a device with the third character being 7 then you should be safe. My device is FA77M which reads - Produced in Taiwan Taoyuan B factory - 2017-July-21st, which should be safe.
Click to expand...
Click to collapse
Thanks for that information mate. It's hard to find that version of yours though.

I have a november 2016 pixel and uBreakiFix (canada & US, but I did it through Canada) replaced the motherboard free of charge even 8 months outside of my warranty period.
I'd consider going to them.

Unfortunately I bought it second hand and I don't have the receipt ( I live in Sydney btw), so even if I did go to my local ubreakifix I don't know if they'll fix it for me.

Audio and microphone stopped working about 1 month ago.
It stopped working on Phone (the local Google app), WhatsApp, Skype & HangOuts.
I could still hear podcasts and music and YouTube. Though I did notice that bluetooth and wired headphones with microphones didn't appear to work.
I tried Safe Mode.
The issue still occurred.
I did a complete Factory reset of the phone.
The issue still occurred.
I have only installed the apps that I use constantly, which includes WhatsApp and Hangouts.
The issue still occurs with bluetooth and wired headphones.
---------- Post added at 02:04 AM ---------- Previous post was at 01:58 AM ----------
Hiyaslalabs said:
Thanks for that information mate. It's hard to find that version of yours though.
Click to expand...
Click to collapse
FA69D0301461
What about this? I have same issues help me

Similar Issue, but I suspect MindTheGapps or Lineage Update
My sons Pixel has similar issues. It started around August.
During Calls he could listen but the mic did not work. Then in Whatsapp and Youtube app videos would not play, while the same videos from youtube played fine in the Browser app.
Usually after restart it works until Spotify crashes the phone, or at least Spotify was active while the phone crashed. Why comes MindTheGapps with pre-installed Spotify anyway? After install from Playstore there are two versions on the phone.
Sometimes after a hard phone crash, mic and speaker work for a while, also a short time after factory reset (until Spotify, Youtube and Whatsapp are reconfigured), then mic and speaker stop to work again. Sometimes the Speaker works for a longer period but the mic does not.
Sometimes there is a message that the system process has stopped responding and if I want to stop it or wait. After the next phone crash this message disappears.
Its hard to believe that this is a hardware issue, while the phone falls into the manufacturing dates of the reported motherboard issues.
Next thing I am going to try is to use OpenGapps and if that does not help, revert to Stock ROM. Maybe this resolves the issue.
Thanks.

No notification sound, ringing or alarms

So, anyone else suffering from the weird sound bug? In essence, there is no notification sounds, ringing or alarms coming through, phone is not on silent and no active DnD mode. And normal media playback is as expected, speakers work fine as well, it's just alarms, ringing and notifications. It gets weirder tho, because if headphones are plugged in sounds can be heard but not when unplugged. Android 10, latest patch too and I'm really confused at this point so any ideas are appreciated. TNX

Hi I have the exact same problem, it occurred after installing the December patch, I tried to do more reset but the problem persists, I contacted google assistance and they told me they will let me know, were you able to solve this problem?
The only option is to wait for another update to correct the problem? Or possibly downgrade to android 9? With android 10 all the problems started including the whistle in the video recording
I opened a problem report on the google issue tracker. Sorry For my bad english.
Pixel 3a
Android 10
December patch

Please star it and comment if you have this issue. Thanks a lot.
issuetracker.google.com /issues/ 146012752

Mine started doing this today. The funny thing is I used a bluetooth for my ear at work and switched to BT in the car when I left work. No ringing comes from the phone, but through BT I now hear the individual ringtones that I have set over car speakers BT and ear BT. It never did that before. Makes me think that using BT somehow caused it. Very odd. I went to Sprint store and let them poke around with it. Two employees had no luck. They stated that they had never seen this problem.
------------------------------
UPDATE. I was directed by Google to either mail it back (7-10 day turnaround-sure!) or take it to UBREAKIFIX like they did to "soopervoo." It was repaired yesterday in about 3 hours! They even offered a loaner phone for the time, but I declined. All is good in my Pixel 3a world again. Oddly, the phone continues to try to update playMusic every so often to the Nov update which is already on my phone.

CoolKitty said:
So, anyone else suffering from the weird sound bug? In essence, there is no notification sounds, ringing or alarms coming through, phone is not on silent and no active DnD mode. And normal media playback is as expected, speakers work fine as well, it's just alarms, ringing and notifications. It gets weirder tho, because if headphones are plugged in sounds can be heard but not when unplugged. Android 10, latest patch too and I'm really confused at this point so any ideas are appreciated. TNX
Click to expand...
Click to collapse
Did you ever have any luck getting your sound fixed on your Pixel 3A?

9878 said:
Mine started doing this today. The funny thing is I used a bluetooth for my ear at work and switched to BT in the car when I left work. No ringing comes from the phone, but through BT I now hear the individual ringtones that I have set over car speakers BT and ear BT. It never did that before. Makes me think that using BT somehow caused it. Very odd. I went to Sprint store and let them poke around with it. Two employees had no luck. They stated that they had never seen this problem.
Click to expand...
Click to collapse
Hello and happy new year! Unfortunately I have not found any solution, I wait for the next update, if it does not solve the problem I will ask for the replacement of the mobile phone. My suspicion is that the December update breaks the lower speaker.

I have similar issue like this for past 3 months, what ever ringtone I set, by default Google duo notification is ringing. But i can hear custom ringtone on whatsapp call.

I have a similar problem with a different phone brand. I tracked the issue to be related to enabling the automatic DND option which tents to not properly go away after it turns off. Sad that is the same on the pixel which I'm looking at buying...

This bug just started for my mom's Verizon Pixel 3a this week. It was working in early Dec 2019, but something recently broke. The call ringer sounds do not work, but YouTube audio does.
I did a full system reset where it temporarily fixed the sound, however, during the app updates, it reverted back to no sound.
Chatting with Google support wasn't useful. They just sent the standard bug report email.
If anyone has any suggestions, please advise.

Update
Called Google support and they redirected me to UBreakiFix to inspect and repair.
Took a few hours, but they replaced the speakers.
Looks like I had a bad unit but seems to be fixed now.
soopervoo said:
This bug just started for my mom's Verizon Pixel 3a this week. It was working in early Dec 2019, but something recently broke. The call ringer sounds do not work, but YouTube audio does.
I did a full system reset where it temporarily fixed the sound, however, during the app updates, it reverted back to no sound.
Chatting with Google support wasn't useful. They just sent the standard bug report email.
If anyone has any suggestions, please advise.
Click to expand...
Click to collapse

Hi everyone! Phone replaced by Google, problem solved! Faulty unit.

Hi All,
same problem with my daughter Pixel 3a, only vibrates , but no ringer at all
i buyed the phone from amazon
on december, this problem started a week ago
so it is hardware related ?
i think im out of warranty
how much does google honor a warranty ?

maxolini said:
Hi All,
same problem with my daughter Pixel 3a, only vibrates , but no ringer at all
i buyed the phone from amazon
on december, this problem started a week ago
so it is hardware related ?
i think im out of warranty
how much does google honor a warranty ?
Click to expand...
Click to collapse
One year.

9878 said:
One year.
Click to expand...
Click to collapse
Cool
im good!!
bought november last year

maxolini said:
Cool
im good!!
bought november last year
Click to expand...
Click to collapse
FYI, mine was a hardware (speaker) problem.

this 3a I have can play YouTube audio on the earspeaker, so I think that's normal, the ringer uses the bottom speaker right? next to the charging USB3 port, if I do a complete factory reset, that will not fix it?

maxolini said:
this 3a I have can play YouTube audio on the earspeaker, so I think that's normal, the ringer uses the bottom speaker right? next to the charging USB3 port, if I do a complete factory reset, that will not fix it?
Click to expand...
Click to collapse
Two factory resets did not work for mine. Mine was acting the same, bottom speaker was crackly, intermittent, and then went out completely.

9878 said:
Two factory resets did not work for mine. Mine was acting the same, bottom speaker was crackly, intermittent, and then went out completely.
Click to expand...
Click to collapse
I am here to pig pile onto the issue. Running the January patch and never getting OTA notifications (running Magisk), I finally sideloaded Feb and then March updates last week. Just a few days later, I was talking on speakerphone and it got all crackly for a few seconds and then quit. That's the last I heard of it. Safe mode, two resets and even a full factory flash didn't fix it.
Just went through diagnostics with Google support and the verdict is the same...take it to ubreakifix under warranty. At least the phone is still useable, unlike the first gen Pixel microphone.

Here is one more confirmation that there is definitely a problem with the Pixel 3a's bottom speaker. Mine cut in and out a couple of times and then died completely. My phone was four months old at the time, purchased directly from Google, and has always lived in an Otterbox Defender case and had never been dropped.
I contacted Google and they said I could send it in for replacement. And I said, "Hey - wait a minute! I bought my phone from Google so I'm supposed to get an advanced replacement!" So he wanted my IMEI and confirmed that, yes, I had that option. But I was concerned that both the agent and website confirmed that I would receive either a new or (most likely) refurbished device.
The Google warranty website said that I had the option of having the phone replaced by Google or going to a local ubreakifix shop, of which there are several in my area. I called them up and the guy I spoke to said it was a common problem on the Pixel 3a! And they had the part in stock.
Since my phone was in perfect condition, other than the speaker, I chose the ubreakifix option instead of having Google send me a, probably used, replacement. I dropped it off, went to get something to eat, and while I was eating, I was messaged that my phone was ready for pickup. I took a look at the paperwork for the repair and the repair cost to Google listed was about $80. I asked the gentleman how much the exact same repair would cost for a Pixel 3a that was not under warranty and he said $140! Damn! I priced the speaker part if bought directly from China on Aliexpress and it was less than $10 from most vendors.
A search of the Google support forums shows that many Pixel 3a owners have had their speakers fail. It's a problem that can't be missed because your phone never rings!
If it fails again under warranty, I will have the speaker replaced. If it fails again after the warranty period, I will order a replacement speaker from China and do my own replacement.