Related
I'm having a few Issues with audio on my pixel that I'm having a hard time finding answers to.
1. The biggest issue that I'm having the hardest time finding info about is this; when listening to music through my headphones after about 5 seconds there will be a pop, the all the audio on my phone will stop working completely. no, mic, no assistant, no headset, bluetooth, speakerphone, or speaker in general.
2. Often, my pixel will just not detect headphones at all. or detect them, then play no sound.
3 Sometime only the mic stops working. I know this one is common in android in general.
A reboot fixes all these things, but the headphone pop happens every single time. I'm talking with support now and they want me to factory reset the phone, so we'll see what happens after that. My questions are if any of you have found fixes, and if the problems happen on custom ROMs. And Does ROMing void the warranty on this phone?
Did you buy your phone from Verizon or Google? The pop and audio dying compare results of a poorly made headphone plug. Check with another pair of headphones and see if you get the same results unless you already have. If the alignment is slightly off it could be shorting across contacts although I don't understand why would work for a short period of time and then stop.
I had the issue with several pairs of headphones and auxillary cables. I talked with Google support and they had me factory reset the phone, and that seems to have fixed the headphone jack issue. The other issues still persist with the mic and call problems though.
The guy from Google support doesn't seem to be getting it. I told him that I'm still having issues the other stuff, but he keeps asking if I tried other headphones. This is the 5th time he's asked.
Yeah, the mic only works about %20 of the time. I've had to restart my phone just to make phone calls for about a week now. I'm going to try and get a replacement.
I'm having an issue from time to time where the phone speaker at the top stops working when taking a call. Only happened twice in 3-4 months. reboot fixed it... ugh..
That's how mine started. Now, o times out of ten I have to restart my phone and pray that my phone likes me that day to make a phone call.
Figured I would pop in here guys. Had a Pixel since launch and have had myriad problems, mic stopped working and couldn't make calls, headphones not being recognized. Factory reset didnt help, safe mode no help, etc. Scoured the net and found on google product forums a possible solution, tried it and so far it has worked.
https://productforums.google.com/forum/#!topic/phone-by-google/4kyIdArEve8
basically go to clock app, find alarms and delete them, then delete data and cache from clock app and reboot. worked a charm for me, try it out.
I'll give this a shot. How long has this been working for you?
Anyone having issue with music "skipping" when connected to a 3rd party bluetooth for cars?
chadhoard said:
Anyone having issue with music "skipping" when connected to a 3rd party bluetooth for cars?
Click to expand...
Click to collapse
Occasionally. Typically a reboot fixes it for me.
magicCrazyThing said:
I'll give this a shot. How long has this been working for you?
Click to expand...
Click to collapse
meant to post earlier but got tied up, this worked for a few hours then back to the same thing. I RMA'd the phone and have a new one now. Hope this one is better
also fyi, my verizon new/possibly refurb phone was received today running 7.1 , not 7.1.1 , i thought some had questions about that.
CaddymanLNL said:
meant to post earlier but got tied up, this worked for a few hours then back to the same thing. I RMA'd the phone and have a new one now. Hope this one is better
also fyi, my verizon new/possibly refurb phone was received today running 7.1 , not 7.1.1 , i thought some had questions about that.
Click to expand...
Click to collapse
I'm just waiting until I get another screen ordered for my MXPE to swap my pixel. If that one has issues too I'll probably just try to get my money back. I love this phone, but that's not an issue I can handle.
magicCrazyThing said:
Yeah, the mic only works about %20 of the time. I've had to restart my phone just to make phone calls for about a week now. I'm going to try and get a replacement.
Click to expand...
Click to collapse
I have the exact same issue Are we sure it's a hardware problem?
d3sm0nd said:
I have the exact same issue Are we sure it's a hardware problem?
Click to expand...
Click to collapse
If it's not, then it has to be a really deep seated software issue. I flashed pure Nexus to see if it still did it and had no luck at all. Lol
magicCrazyThing said:
If it's not, then it has to be a really deep seated software issue. I flashed pure Nexus to see if it still did it and had no luck at all. Lol
Click to expand...
Click to collapse
Then i'm ****ed because I bought off ebay and I nobody can exchange my phone. I have to send it to Google and wait probably weeks until I get a new one. :crying:
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,
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
I have got a Pixel at relatively cheap price recently. Everything works perfectly except the there are problem at earpiece and earphone jack. I can't hear anything from the earpiece when using the build-in phone app or any other phone application. I originally think of hardware problem. But the strange thing is, if I play record message in whatsapp, I can hear the recording from the earpiece! I have tried some hardware testing app download from google play, some app crush when testing the earpiece while some could play sound with the earpiece. Another issue is there is no sound at the earphone jack. However, when I use the hardware testing, the earphone jack actually work! I have tried to contact google but since I am at a country without google playstore, they can offer no assistance. And they say they did not receive any similar report. Google just ask me to find some local workshop to fix it since I don't the warranty anyway. But if it is a problem with the motherboard, I don't think local workshop can fix without changing a new one. I have try some some of the custom Rom and kernel, but nothing works.
Does anyone have the same issue and got a solution to it?Or Maybe it is a hardware problem? I hear some people it is a manufacturing flaw on the motherboard.
Thanks.
I have the very same problem, again. My old Pixel got that bug and now my replacement as well. Makes me think, that it is Android Pie related.
Have you ever tried safe mode or done factory reset? I have encountered same issue, and got fixed by a local guy. please check my previous thread for more detailed info.
bush911 said:
Have you ever tried safe mode or done factory reset? I have encountered same issue, and got fixed by a local guy. please check my previous thread for more detailed info.
Click to expand...
Click to collapse
I have tried safe mode and done factory reset but still not working. Where did you find the guy and how he fix it?
I am currently using a Bluetooth headphone and it works alright.
The guy is in China.
After the earphone was fixed and last almost half a year, I got a new issue. I was traveling in Dubai, suddenly the phone became very hot and can not turn on screen. I had to long press the power key to turn it off.
After that, I never powered the phone on
Finally, I found another guy and got the phone fixed.
So, Damn google. I will never buy a pixel phone until it launches months later
jacky0407 said:
I have tried safe mode and done factory reset but still not working. Where did you find the guy and how he fix it?
I am currently using a Bluetooth headphone and it works alright.
Click to expand...
Click to collapse
bush911 said:
The guy is in China.
After the earphone was fixed and last almost half a year, I got a new issue. I was traveling in Dubai, suddenly the phone became very hot and can not turn on screen. I had to long press the power key to turn it off.
After that, I never powered the phone on
Finally, I found another guy and got the phone fixed.
So, Damn google. I will never buy a pixel phone until it launches months later
Click to expand...
Click to collapse
Did you find the guy on taobao? Or can you leave his contact to me? I am travelling China next month. Maybe I can find him to fix my phone.
Yes on Taobao, the guy lives in Shenzhen. Will PM you details when I log in PC
jacky0407 said:
Did you find the guy on taobao? Or can you leave his contact to me? I am travelling China next month. Maybe I can find him to fix my phone.
Click to expand...
Click to collapse
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.