Related
I have run into the dreaded headphone jack problem. The phone won't play audio through the speakers and doesn't use the microphone because it thinks that headphones are connected. I've tried resetting it to factory settings and it didn't fix anything which is why I think it's not a software problem.
After some Googling I found that I'm not the only one to have this problem and that Google is replacing the units with this hardware fault. Unfortunately I didn't buy the phone via play store so I can't return it directly to google.
I'd like to try and fix it myself. If anyone knows where I could buy a headphone jack for the 5" pixel I'd be very grateful. Before I buy the replacement part I was thinking of removing the headphone jack and trying to start the phone like without it. My reasoning is that the phone would then default to playing the sound through speakers and I would be sure that it's a headphone jack problem. Would that work at all or the phone won't even start?
I need your advice and opinions, thanks
Please keep us updated as I'm facing the same issue:/
Alaadragonfire said:
Please keep us updated as I'm facing the same issue:/
Click to expand...
Click to collapse
I ordered a replacement headphone jack and as soon as it arrives, within the next 2 weeks I hope, I'll replace it and see if that gets it fixed.
A couple of more details:
-problems started about 3 days after updating to Oreo
-at the beginning the volume would first turn itself gradually down to zero and I had to fight it with the volume up (I would always lose eventually xD)
-there was usually a loud pop heard through the headphones after that 'battle' and then the audio and mic would completely cut off
-restarting the phone would enable the audio and mic again but the problems returned as soon as I plugged in the headphones again (tried with several different headphones)
-factory reset didn't fix it and after a couple of days of problems I'm now stuck with no audio at all and no mic input
-my phone can't recognize the headphones anymore
I have the exact struggle, restart will work for a while and then problem return, when I contacted google they offered a replacement but since I'm not in Canada at the moment, they will not be able to process my replacement request, but google representative told me that I can try and replace the mic with the charging port(as it all comes together) and it should fix the issue, but I also think that it might be the headphones jack, also this happened after I tried Android O beta.
FooFighter312 said:
I ordered a replacement headphone jack and as soon as it arrives, within the next 2 weeks I hope, I'll replace it and see if that gets it fixed.
A couple of more details:
-problems started about 3 days after updating to Oreo
-at the beginning the volume would first turn itself gradually down to zero and I had to fight it with the volume up (I would always lose eventually xD)
-there was usually a loud pop heard through the headphones after that 'battle' and then the audio and mic would completely cut off
-restarting the phone would enable the audio and mic again but the problems returned as soon as I plugged in the headphones again (tried with several different headphones)
-factory reset didn't fix it and after a couple of days of problems I'm now stuck with no audio at all and no mic input
-my phone can't recognize the headphones anymore
Click to expand...
Click to collapse
please update the progress, i'm having the same problem. I hope it get fixed after you replace the headphone jack
malstroms said:
please update the progress, i'm having the same problem. I hope it get fixed after you replace the headphone jack
Click to expand...
Click to collapse
I'm still waiting on the part to arrive. I'm expecting it within the next two weeks. I'll try to document the replacement with photos and/or video so others can do it if it turns out successful
Okay guys, here's the update with some good news and some bad news.
The replacement headphone jack arrived yesterday and the good news is that I replaced it and it seems to have fixed the problem! Yay!
But the bad news is that in the process I damaged the LCD screen so now I'm waiting on a replacement LCD. I guess I should've expected that because the screen and LCD itself are extremely sensitive and the damage is not even visible, but it's simply not working anymore.
So how do I know it actually works? Well since the phone used to be paired to my PC via bluetooth, whenever I turn on my PC a notification sounds on my phone if I want to pair or not.
Minor bad news - I tried to record the whole process as a tutorial for anyone who'll try to fix this themselves but my camera's battery died halfway and I lost everything I recorded.
Here are the 2 teardown videos I used for guidance: First and Second. I highly recommend you watch them entirely before attempting anything.
I got the headphone jack on eBay from here. It is totally overpriced but it's the only place I was able to find it.
I'm getting my replacement LCD and adhesive for it from Replace Base
FooFighter312 said:
Okay guys, here's the update with some good news and some bad news.
The replacement headphone jack arrived yesterday and the good news is that I replaced it and it seems to have fixed the problem! Yay!
But the bad news is that in the process I damaged the LCD screen so now I'm waiting on a replacement LCD. I guess I should've expected that because the screen and LCD itself are extremely sensitive and the damage is not even visible, but it's simply not working anymore.
So how do I know it actually works? Well since the phone used to be paired to my PC via bluetooth, whenever I turn on my PC a notification sounds on my phone if I want to pair or not.
Minor bad news - I tried to record the whole process as a tutorial for anyone who'll try to fix this themselves but my camera's battery died halfway and I lost everything I recorded.
Here are the 2 teardown videos I used for guidance: First and Second. I highly recommend you watch them entirely before attempting anything.
I got the headphone jack on eBay from here. It is totally overpriced but it's the only place I was able to find it.
I'm getting my replacement LCD and adhesive for it from Replace Base
Click to expand...
Click to collapse
Thanks for the updated! Are you sure problem is fixed by changing the headphone jack ? It's not temporary fixed like before ? BTW the link for eBay headphone jack is already sold out
Alaadragonfire said:
Thanks for the updated! Are you sure problem is fixed by changing the headphone jack ? It's not temporary fixed like before ? BTW the link for eBay headphone jack is already sold out
Click to expand...
Click to collapse
Well I'll know for sure as soon as I replace the LCD. I'm hoping it will arrive during the next week and then I'll update this thread again
Alaadragonfire said:
I have the exact struggle, restart will work for a while and then problem return, when I contacted google they offered a replacement but since I'm not in Canada at the moment, they will not be able to process my replacement request, but google representative told me that I can try and replace the mic with the charging port(as it all comes together) and it should fix the issue, but I also think that it might be the headphones jack, also this happened after I tried Android O beta.
Click to expand...
Click to collapse
I definitely recommend others try to get Google to replace it. I got mine from Swappa second hand and they still respected the warranty. Much easier and cheaper than replacing it yourself.
wow its nice to hear that it work, but some say that its the charging port board that has a problem(the location of the microphone). should i buy headphone jack replacement or charging port board?
yesterday i put i my pixel into freezer for 2 hour(i tried this because it help my previous phone which is nexus 5x come back to life for a while haha) and rebooted to safe mode and tried to record and microphone work, rebooted to normal and until now it still work, but im hoping that your replace method would be a permanent fix and i will do that too.
please update this thread again as soon as you replace your lcd
thank you
Another update. I got the replacement screen today but the problem hasn't been fixed. Well, partly it has been. The speaker now finally works when nothing is plugged in but the phone can't recognize any headphones. So, like Mattish13, if you can get it replaced by Google do so. Fixing things on my own is my hobby and was logical since I couldn't get mine replaced by Google, but this fix is not worth your time or money, trust me. I'm guessing the next thing to get replaced would be the daughterboard, maybe that would fix the problem finally, but in my opinion it's not worth it.
Ironic how so many problems with the headphone jack appeared for so many people and at the same time Google decided to ditch the jack for Pixel 2 :laugh:
Edit: just to be clear, since I already invested in a new screen and new jack, I will drop in another 25$ for the new daughterboard. If that doesn't fix it, nothing can
malstroms said:
wow its nice to hear that it work, but some say that its the charging port board that has a problem(the location of the microphone). should i buy headphone jack replacement or charging port board?
yesterday i put i my pixel into freezer for 2 hour(i tried this because it help my previous phone which is nexus 5x come back to life for a while haha) and rebooted to safe mode and tried to record and microphone work, rebooted to normal and until now it still work, but im hoping that your replace method would be a permanent fix and i will do that too.
please update this thread again as soon as you replace your lcd
thank you
Click to expand...
Click to collapse
As strange as it sounds the freezer trick works! I think the issue appears when the phone heats or it's heat related
FooFighter312 said:
Another update. I got the replacement screen today but the problem hasn't been fixed. Well, partly it has been. The speaker now finally works when nothing is plugged in but the phone can't recognize any headphones. So, like Mattish13, if you can get it replaced by Google do so. Fixing things on my own is my hobby and was logical since I couldn't get mine replaced by Google, but this fix is not worth your time or money, trust me. I'm guessing the next thing to get replaced would be the daughterboard, maybe that would fix the problem finally, but in my opinion it's not worth it.
Ironic how so many problems with the headphone jack appeared for so many people and at the same time Google decided to ditch the jack for Pixel 2 :laugh:
Edit: just to be clear, since I already invested in a new screen and new jack, I will drop in another 25$ for the new daughterboard. If that doesn't fix it, nothing can
Click to expand...
Click to collapse
Any updates ?
Alaadragonfire said:
Any updates ?
Click to expand...
Click to collapse
Yes, sorry for forgetting to post earlier. I changed the daughterboard and it appeared to be working perfectly. But about 30 minutes later the microphone again wasn't working and there was no audio. I was back at the beginning.
Then I did a factory reset and again it worked. But every time, after about 30 minutes it stops working. At this point I have no idea what the exact problem is.
I've definitely fixed it partly somehow because before I couldn't get the microphone and speaker to work at all. Now I can, but it fails after some time eventually. The headphones jack works normally until the failure happens.
I've tried the freezer trick after that and had no noticeable improvement. My theory now is that the problem probably was on the daughterboard but the replacement one I got (which is actually a refurbished part) might have had the same problem but not as serious as my original part.
FooFighter312 said:
Yes, sorry for forgetting to post earlier. I changed the daughterboard and it appeared to be working perfectly. But about 30 minutes later the microphone again wasn't working and there was no audio. I was back at the beginning.
Then I did a factory reset and again it worked. But every time, after about 30 minutes it stops working. At this point I have no idea what the exact problem is.
I've definitely fixed it partly somehow because before I couldn't get the microphone and speaker to work at all. Now I can, but it fails after some time eventually. The headphones jack works normally until the failure happens.
I've tried the freezer trick after that and had no noticeable improvement. My theory now is that the problem probably was on the daughterboard but the replacement one I got (which is actually a refurbished part) might have had the same problem but not as serious as my original part.
Click to expand...
Click to collapse
Thanks for the update, interesting... Maybe the daughterboard is faulty as well, but didn't Google response was that there is a crack line in the audio codec, as far as I know the audio codec is on the motherboard, I guess this problem won't be fixed after all, it is really annoying!! I wanted to get another pixel maybe XL this time, I found some offers with used ones, but now I am really afraid to buy one and this problem appears with the second phone.
Yes, found that response but unfortunately changing the motherboard is not possible because I couldn't find any place that sells them and I guess it's the same as getting a new phone in the end ?
I ended up getting a pixel XL but Google said this problem appears on devices manufacturered before March 2017,so I made sure when I was buying that I got a device manufactured after that and I did. So far so good ?
FooFighter312 said:
Yes, sorry for forgetting to post earlier. I changed the daughterboard and it appeared to be working perfectly. But about 30 minutes later the microphone again wasn't working and there was no audio. I was back at the beginning.
Then I did a factory reset and again it worked. But every time, after about 30 minutes it stops working. At this point I have no idea what the exact problem is.
I've definitely fixed it partly somehow because before I couldn't get the microphone and speaker to work at all. Now I can, but it fails after some time eventually. The headphones jack works normally until the failure happens.
I've tried the freezer trick after that and had no noticeable improvement. My theory now is that the problem probably was on the daughterboard but the replacement one I got (which is actually a refurbished part) might have had the same problem but not as serious as my original part.
Click to expand...
Click to collapse
I had this problem and Google said pixel has warranty till 2019 and sent me a new one... However they sent me the wrong color and I have no choice in the manner
knowitall72 said:
I had this problem and Google said pixel has warranty till 2019 and sent me a new one... However they sent me the wrong color and I have no choice in the manner
Click to expand...
Click to collapse
Do you mean your phone had warranty till 2019 or all pixel devices, because when I contacted Google the guy on the phone told me my phone has warranty till Jan 2018, which sucks in my case as I'm at the moment outside of Canada and won't be returning till summer 2018
Alaadragonfire said:
Do you mean your phone had warranty till 2019 or all pixel devices, because when I contacted Google the guy on the phone told me my phone has warranty till Jan 2018, which sucks in my case as I'm at the moment outside of Canada and won't be returning till summer 2018
Click to expand...
Click to collapse
I believe all pixel devices because I bought mine just after they came out in Australia... Phone screen broke and when I replaced it I had these problems... Told Google it was a hassle contacting my australian provider and would cost alot and they said it had warranty until '19 and that they would replace it here in the states free of charge... It may have been only till '18 but my first pixel was faulty as well and I had it exchanged out there n straya so maybe that's why it is until 2019
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:
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.
I've been having problems with my pixel. After about 20 mins after rebooting the phone the mic, Earpeice, and Headphone Jack don't work. It just happened out of the blue one morning and it's stopped working since. I've already completely wiped the phone with twrp and flashed Android P, nothing is working. Any ideas?
It's a hardware issue with the audio codec inside the motherboard. If you got warranty still you can replace it from Google.
Alaadragonfire said:
It's a hardware issue with the audio codec inside the motherboard. If you got warranty still you can replace it from Google.
Click to expand...
Click to collapse
Is this confirmed? My Nexus 6P recently died, so I picked up a Pixel secondhand to replace it. It worked fine until I updated it to 8.1 and then all these issues started, which made me think it was software related. I've read a ton of threads all over the internet on this, and I see people replacing the mic/charger port, the headphone jack, and the daughter board and still having the same issues.
I saw somewhere (can't remember where now) that someone finally had this problem fixed by installing the Android P preview. Has anyone else had any success with that? Since I got this secondhand, I can't just get a warranty repair/replacement. I can send it back, but then I'd have to pay almost twice as much to get a Pixel 2, so I'd prefer to get this working if possible.
Thanks
velvet_man said:
Is this confirmed? My Nexus 6P recently died, so I picked up a Pixel secondhand to replace it. It worked fine until I updated it to 8.1 and then all these issues started, which made me think it was software related. I've read a ton of threads all over the internet on this, and I see people replacing the mic/charger port, the headphone jack, and the daughter board and still having the same issues.
I saw somewhere (can't remember where now) that someone finally had this problem fixed by installing the Android P preview. Has anyone else had any success with that? Since I got this secondhand, I can't just get a warranty repair/replacement. I can send it back, but then I'd have to pay almost twice as much to get a Pixel 2, so I'd prefer to get this working if possible.
Thanks
Click to expand...
Click to collapse
It is confirmed unfortunately. Many people had this problem with their devices that are manufactured in 2016 and before January 2017. If you are able to send it back I suggest you do.
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.
Thanks guys. I sent the phone back. It was a certified refurb through Amazon, so I should get a full refund once they get the phone back in the mail. I want to order another one, but how do I verify that it was made after Jan 2017?
Thanks!
truvatech said:
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.
Click to expand...
Click to collapse
I want to second this experience for anybody that finds this thread. My wife's phone was purchased Dec 2016 and lost microphone/speaker last week. Used the help feature to chat with google, they sent us for repair and uBreakiFix replaced the motherboard at Google's expense 8 months out of warranty. I'm very happy to see Google standing behind their device.
OK, so here's my 2pence worth... I have a Pixel manufactured in 2016 and it has been faultless for 10 months. I have been very craeful with it. I applied the 5 July 2018 Security Update and my microphone stopped working. I tried all the usuals to fix it but nothing. As a last resort I enrolled in the Android P beta program and installed it. My microphone started working again with Android 9. However, with the latest update build PPP5.180610.010 the microphone is buggy again... so I think it's a software driver issue. Anyone else want to confirm this?
plittlefield said:
OK, so here's my 2pence worth... I have a Pixel manufactured in 2016 and it has been faultless for 10 months. I have been very craeful with it. I applied the 5 July 2018 Security Update and my microphone stopped working. I tried all the usuals to fix it but nothing. As a last resort I enrolled in the Android P beta program and installed it. My microphone started working again with Android 9. However, with the latest update build PPP5.180610.010 the microphone is buggy again... so I think it's a software driver issue. Anyone else want to confirm this?
Click to expand...
Click to collapse
I don't think so. Flakey hardware - not a complete failure, but bad enough connection that it isn't reliable. Had you done a complete factory reset, I bet it would have worked for a bit. Then, when the signal is bad for long enough the system can't deal with it and the behavior re-surfaces. You could design resilient software to account for the slow failure. At least that is my guess, based on the experience I had (swapping SIMS would fix the phone for a while, sometimes microphone would go out first, sometimes wireless data).
Note10.1Dude said:
I don't think so. Flakey hardware - not a complete failure, but bad enough connection that it isn't reliable. Had you done a complete factory reset, I bet it would have worked for a bit. Then, when the signal is bad for long enough the system can't deal with it and the behavior re-surfaces. You could design resilient software to account for the slow failure. At least that is my guess, based on the experience I had (swapping SIMS would fix the phone for a while, sometimes microphone would go out first, sometimes wireless data).
Click to expand...
Click to collapse
Damn, hope not
OK, so what serial number do I need to check for on eBay, so that I get a 2017 manufactured Pixel?
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
udahy.manna said:
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
Click to expand...
Click to collapse
Yes, 3 weeks is exactly the same time as when I updated to the 5 July 2018 security update, and then my microphone started going funny. Please try going to SAFE MODE and then clear the CACHE from the Phone app.
Press and hold the power button to bring up the power options. Press and HOLD on the Restart icon. Choose SAFE MODE.
Once in SAFE MODE, press and hold the PHONE app icon, and choose the 'i' for information. Choose Storage, then press the CLEAR CACHE button.
Reboot the phone again in SAFE MODE, and try calling your OWN mobile number then leave a message.
Tell me if your microphone is working again.
plittlefield said:
Yes, 3 weeks is exactly the same time as when I updated to the 5 July 2018 security update, and then my microphone started going funny. Please try going to SAFE MODE and then clear the CACHE from the Phone app.
Press and hold the power button to bring up the power options. Press and HOLD on the Restart icon. Choose SAFE MODE.
Once in SAFE MODE, press and hold the PHONE app icon, and choose the 'i' for information. Choose Storage, then press the CLEAR CACHE button.
Reboot the phone again in SAFE MODE, and try calling your OWN mobile number then leave a message.
Tell me if your microphone is working again.
Click to expand...
Click to collapse
No bro.. I tried like you said..but not working..
udahy.manna said:
No bro.. I tried like you said..but not working..
Click to expand...
Click to collapse
That's a shame.
I can absolutely confirm THAT MY PROBLEM IS A SOFTWARE ISSUE... I have just installed an update to the PHONE app from Google on Android 9 and made 3 telephone calls this morning with NO PROBLEMS at all.
Here's the summary again for those that it might help.
1. Pixel on 8.1.0
2. Update to 5 July 2018 Security Patch
3. Microphone not working
4. Enroll in Android 9 P beta
5. Install Android 9 beta
6. Microphone now working
7. Sometimes microphone fails
8. Reboot in SAFE mode and clear Phone app CACHE
9. Reboot in SAFE mode and make a few calls with microphone working
10. Update to latest Phone app version 22.0.204206752 (31 July 2018)
11. Phone and Microphone working perfectly
That's all I can say really.
Paul
OK, so it's been another trouble free day with the phone, making calls and using Google Assistant with my WORKING MICROPHONE fixed by software... and not a soldering iron
I made and received a dozen calls and asked Google for help with all sorts.
So, things can be fixed without sending it away.
My serial number begins FA69M which means...
FA = Where it's been built
6 = Year of production (2016)
9 = Month of production (September)
M = Day of production (21)
...so it's a pre 2017 Pixel Sailfish which had the problem and now it doesn't thanks to Android 9 beta.
Paul
udahy.manna said:
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
Click to expand...
Click to collapse
Did you fix?
Damn, I've been thinking to buy it, the 128GB model, since I'm not kinda guy who changes cellphone like cloths, just updating for another 2 year or more. I'll be updating the device to Android Pie for the app support. Please advice me if I should buy it or not. I'm fully convinced to buy Google Pixel 128GB model since it is compact has a great camera and it provides a real smooth experience with stock android. only thing holding me back is that MicroPhone Issue that people are complaining about. Please help me make the decision.
Sam33t said:
Damn, I've been thinking to buy it, the 128GB model, since I'm not kinda guy who changes cellphone like cloths, just updating for another 2 year or more. I'll be updating the device to Android Pie for the app support. Please advice me if I should buy it or not. I'm fully convinced to buy Google Pixel 128GB model since it is compact has a great camera and it provides a real smooth experience with stock android. only thing holding me back is that MicroPhone Issue that people are complaining about. Please help me make the decision.
Click to expand...
Click to collapse
i had this issue a while back but since ive updated to the december update i havent had any mic, speaker issues at all. its the best phone to me ive had...and ive had alot. i say get it..im gonna get the pixel 2 xl and the pixel 3 as well..
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.