I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
squareballz said:
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
Click to expand...
Click to collapse
Yes and it is quite irritating.
Hi, I have exactly the same problem.
Do you have a case on the phone? Perhaps it's detecting that you are in dock mode? Just throwing some things out there since it does not seem to be widespread.
squareballz said:
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
Click to expand...
Click to collapse
I thought I was going crazy when I picked up a call it was super loud prior to putting it to my ear lol I have no case nor screen protector so this is a legit bug.
Interesting....just applied March update. I'll see if this remedies it.
bakemcbride21 said:
I thought I was going crazy when I picked up a call it was super loud prior to putting it to my ear lol I have no case nor screen protector so this is a legit bug.
Interesting....just applied March update. I'll see if this remedies it.
Click to expand...
Click to collapse
March update did not fix it. It's getting really annoying
Time for an RMA. This can't be software related since very few are seeing it. Could be hardware so a different unit is in order. Good luck.
Sent from my Pixel 2 using XDA-Developers Legacy app
I'll bet this is happening to more people than we think. Very rarely do I chime in, I'm usually a lurker. But I figure I better say something because this problem has already happened to me twice today. It is really really frustrating. Especially for a device as expensive as this one.
bobby janow said:
Time for an RMA. This can't be software related since very few are seeing it. Could be hardware so a different unit is in order. Good luck.
Sent from my Pixel 2 using XDA-Developers Legacy app
Click to expand...
Click to collapse
RMA time??? Not on Verizon lol I don't use my phone to talk enough to justify getting an unlockable phone on RMA.
I'll deal with the occasional speakerphone pickup for the $50 I paid for the phone (well work paid) and having it unlocked/rooted etc
jascolli said:
I'll bet this is happening to more people than we think. Very rarely do I chime in, I'm usually a lurker. But I figure I better say something because this problem has already happened to me twice today. It is really really frustrating. Especially for a device as expensive as this one.
Click to expand...
Click to collapse
I'll bet it's not. The device has been out 6 months and I see 4 users with the problem out of thousands out there. If you don't want to RMA then there is no reason to complain especially if you paid 50 bucks. That's why they do RMA for instances like this. Manufacturing flaws happen, deal with it or replace the device
'nuff said.
Sent from my Pixel 2 using XDA-Developers Legacy app
Guys, I think I found out what's causing this to happen.
The 3.5 audio adapter.
I did not plug in the adapter for 2 days, and the phone did not default to loudspeaker during phone calls.
But last night I plugged in and listen to music, after unplugging, the phone all go into loudspeaker again when phone calls are made/received. Restart the phone and now it never happened.
Gonna monitor few more days and update here.
OK, it is confirmed after using the audio adapter, the phone will definitely switched to loudspeaker mode during phone calls on default , it happens randomly and i would say 70 percent of the time.
its been the 5th day i did not plug in the audio adapter , all my phone calls are not defaulted to loudspeaker, and worked flawlessly.
Google team if you're seeing this, please make a fix to it!
I've had this issue a few times and I've never used the audio adapter. I did send Google feedback about it through the settings menu a couple of months ago, but I've never heard back from them. It's been a while since I've experienced this issue and for sure it's annoying when it happens. I thought it happened because of a previous phone call loudspeaker state. If you had the loudspeaker on on a previous call then the next call would also have the loudspeaker on when it shouldn't.
miamistevie said:
I've had this issue a few times and I've never used the audio adapter. I did send Google feedback about it through the settings menu a couple of months ago, but I've never heard back from them. It's been a while since I've experienced this issue and for sure it's annoying when it happens. I thought it happened because of a previous phone call loudspeaker state. If you had the loudspeaker on on a previous call then the next call would also have the loudspeaker on when it shouldn't.
Click to expand...
Click to collapse
I still use the loudspeaker during phone calls, but at the next call, the phone does not default to loudspeaker.
I have been having two problems with my Pixel 2:
1) i cannot use a headset all the time for phone calls. I have to reboot the phone first then it's ok. I don't use the phone enough to have determined what has been done beforehand to cause this.
2) Sometimes the phone defaults to speaker phone for a phone call. Rebooting fixed it. I did use the headset the other day and then the past 2 calls were on speaker phone and tapping the speaker button did not change the setting.
Related
I've searched and it doesn't seem that many others are having this problem. My wife also has a Droid Charge and has never had this happen.
Basically, mid-call (usually 5-10 minutes, 1-2x a day), the other party will stop hearing me. I can hear them, but they can't hear me. If I hang up and call back, the problem is still there. Cycling airplane mode doesn't help... I actually have to reboot the phone. It's gotten to the point where I tell people if it happens, I'll call them back (since it takes a while to reboot).
This is with the stock ROM, as well as Humble 1.5.
Usually it's just silence on their end, but once in a while, the problem manifests as a screechy, random fax-type noise. Same thing... I can hang up and call voicemail and have it sound like that. I always have to reboot the phone.
Has anyone else had this problem, and if so, were they able to fix it w/o getting a replacement phone?
Thanks.
I have the exact same situation. Wife and I both have DCs. I got mine first. About the second day I had it, the screetching noise happened. It was so loud it almost blew my ear out. Hanging up and redialing did not help. I had to reboot the phone. I exchanged for a new phone for that and other reasons. The new replacement on does the same thing once in a while and the wife says there is sometimes a clicking noise then she can't hear me at all but I can hear her fine. She has had the screetching noice once.
91point6 said:
I have the exact same situation. Wife and I both have DCs. I got mine first. About the second day I had it, the screetching noise happened. It was so loud it almost blew my ear out. Hanging up and redialing did not help. I had to reboot the phone. I exchanged for a new phone for that and other reasons. The new replacement on does the same thing once in a while and the wife says there is sometimes a clicking noise then she can't hear me at all but I can hear her fine. She has had the screetching noice once.
Click to expand...
Click to collapse
Weird. I've only had the screeching noise one time. Usually, it's like my end is on mute.
I thought it might be the switch to 4g recently, but remembered it happened before then, too. Plus, it doesn't happen on my wife's phone at all.
I guess I'll have to get a replacement. Is there any way to ensure I get a new phone and not a refurb if I do a warranty replacement?
Sent from my Android using Tapatalk
Flapjack said:
Weird. I've only had the screeching noise one time. Usually, it's like my end is on mute.
I thought it might be the switch to 4g recently, but remembered it happened before then, too. Plus, it doesn't happen on my wife's phone at all.
I guess I'll have to get a replacement. Is there any way to ensure I get a new phone and not a refurb if I do a warranty replacement?
Sent from my Android using Tapatalk
Click to expand...
Click to collapse
You are going to get a refurb unless you are within 14 days. You can argue and they might give you a new one if you threaten to port out but other then that you will not get a new phone.
moondrius said:
You are going to get a refurb unless you are within 14 days. You can argue and they might give you a new one if you threaten to port out but other then that you will not get a new phone.
Click to expand...
Click to collapse
Damn. I'm a bit over 30 days. That really sucks, as I seriously doubt they'll be able to reproduce the problem with my phone, but will take it back and "refurb" it to the next unsuspecting owner.
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
epg0 said:
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
UberGoat said:
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
Click to expand...
Click to collapse
I don't think my issue is with the speaker, because even the headset speaker doesn't work when the sound cuts out. It seems like it must be a software issue.
UberGoat said:
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
Click to expand...
Click to collapse
Same exact thing here. Ive tried calling but they want me to put up another $350 until the recieve the defective device which could be a week. So frustrating.
Grims said:
I don't think my issue is with the speaker, because even the headset speaker doesn't work when the sound cuts out. It seems like it must be a software issue.
Click to expand...
Click to collapse
Yeah I have exactly the same issue as you. Was playing music on my phone through headphones. Took headphones out when I arrived at where I was walking. When I put my headphones back in to listen to music again, the screen said it was playing but nothing came out. I took out headphones and didn't get any sound out the speaker. I rebooted and all was fine again.... Is this a software bug or hardware? Should I try get a replacement for my phone?
timfimjim said:
Yeah I have exactly the same issue as you. Was playing music on my phone through headphones. Took headphones out when I arrived at where I was walking. When I put my headphones back in to listen to music again, the screen said it was playing but nothing came out. I took out headphones and didn't get any sound out the speaker. I rebooted and all was fine again.... Is this a software bug or hardware? Should I try get a replacement for my phone?
Click to expand...
Click to collapse
It's possible it's an issue with the headphone jack thinking headphones are plugged in when they're not. I've seen it happen before, and even plugging in headphones didn't resolve it until I cleaned the jack. Haven't seen that issue on a brand new device though.
Google has fantastic support, so I'm going to wait it out as long as possible so if I do have to RMA it I'll have a better chance of getting a later hardware revision.
Is the devices still locked and rooted? My still new from factory. When I do a factory reset sound will work for few seconds and give out. I am going to try to root and unlock load a custom rom and see if that fixes the problem.
Mine is stock, unrooted.
It has to be a software issue because when I reboot the sound works again.
I really do not want to RMA, everything else seems fine.
Just rooted unlocked flashed a custom rom. Still no sound...then just now out of nowhere sound works??
emeniit ealdne
Reporting a similar issue on my end. Doublethinking if I ripped out the headphones too roughly but initially thought my right earbud was busted so a coworker opted to let me use his. It was playing YouTube videos on loudspeaker just fine during lunch. OTW back to the office noticed that sound notifications were buggy. Plugged in coworker's headphones to confirm if mine was busted but experienced same outage. Then both earbuds went silent. Thought I had to clean the jack when I got home but I did a restart and they work fine.
I have the same problem with my N5. When I adjust the volume with the rocker, I no longer hear the sound that lets you know it's being changed. It resolves itself after a few minutes, but it concerns me.
Sent from my Nexus 5 using Tapatalk
I have the same issue. Restarting put it right. Last night I used headphones, and it's possible that this is what causes the sound to stop working, since I can't remember hearing any notifications after that.
epg0 said:
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
gdarren said:
I have the same issue. Restarting put it right. Last night I used headphones, and it's possible that this is what causes the sound to stop working, since I can't remember hearing any notifications after that.
Click to expand...
Click to collapse
In my case it is the headphones. Everything works fine until the headphones are pulled out. Now sound is not working again, hoping it will fix itself like it did yesterday. 2nd time this has happened. Reboot does not fix my problem. How did yall clean the headphone jack safely?
kp432 said:
In my case it is the headphones. Everything works fine until the headphones are pulled out. Now sound is not working again, hoping it will fix itself like it did yesterday. 2nd time this has happened. Reboot does not fix my problem. How did yall clean the headphone jack safely?
Click to expand...
Click to collapse
I just posted about this issue -- a reboot does fix the issue. I also had it partially working with just the left earbud working. Once again, a reboot fixed.
zmattmanz said:
I just posted about this issue -- a reboot does fix the issue. I also had it partially working with just the left earbud working. Once again, a reboot fixed.
Click to expand...
Click to collapse
Ive rebooted multiple times, wiped re-flashed rom, and nothing. The only reason i unlocked/rooted was hopes that a new Rom would fix. Started acted this way fresh from the box. Thinking of flashing the whole .img?
This problem started for me a few days ago, when I got a call and noticed there was no sound from the speaker. After fiddling with my sound settings and rebooting all was working again for a few hours, then the sound stopped again. I had a colume toggle widget installed which I though may have been causing a prob so uninstalled it. This morning, I had no sound from the speaker again. Did a safe mode boot and still no sound. Fiddled with the volume controls, rebooted a couple of more times and still nothing. I rang Google, and while I was on hold, hit the speaker button and the speaker worked fine in-call. Spoke to a Google device "expert" who had not heard of this prob, and suggested I do a factory restore (the good old "Have you tried turning it off and on again?" fix). Just did a factory restore and the speaker is working fine again. So seems like a software issue, I hope Google addresses this soon.
hi guys,
not sure if this is still actual but same thing happened to my missus tonight. she missed the work today cos of this. there is no sound what so ever. for now I haven't have much time to play with it as she was running late. its the latest device bought just few weeks ago and there is latest update on it. its in factory state, untouched, no root as she doesnt want me to touch her phones (not sure why ??? )
anybody else still having same issues these days? anyone can confirm if it is SW or HW issue?
thx
it seems a software issue though i never faced it try flashing the factory imange after a clean wipe or switch to cm
bhavstech said:
it seems a software issue though i never faced it try flashing the factory imange after a clean wipe or switch to cm
Click to expand...
Click to collapse
phone is in factory condition as I mentioned I haven't touch it as I'm not allowed only thing what was done is the OTA update from new.thats all.
will see tonight when she come back from work. in worst I will RMA what I dont really want to do
rikardo1979 said:
phone is in factory condition as I mentioned I haven't touch it as I'm not allowed only thing what was done is the OTA update from new.thats all.
will see tonight when she come back from work. in worst I will RMA what I dont really want to do
Click to expand...
Click to collapse
If it's completely stock then perform a factory reset from the stock recovery and make sure she hasn't installed any apps that could interfere with sound. Apps like Tasker may be.
- Sent from an IceCold Hammerhead!
My gf has been complaining ever since I got this phone that she cant hear me when I'm talking and that I sound all muffled. Been searching around on here and google and found a few others with this issue...Is this with everyone's device?! Or is it only a few that are having this issue?! I dont want to go back to my s4 I was hoping to sell it this week!!
RMA looks like it will take a few weeks too, but if all of them are like this..
I am also having this problem. Friends complain of low/soft voice. Zero problems on speaker, video recordings, and inline mic. Maybe a software issue?
Sent from my Nexus 5 using xda app-developers app
exxpired said:
My gf has been complaining ever since I got this phone that she cant hear me when I'm talking and that I sound all muffled. Been searching around on here and google and found a few others with this issue...Is this with everyone's device?! Or is it only a few that are having this issue?! I dont want to go back to my s4 I was hoping to sell it this week!!
RMA looks like it will take a few weeks too, but if all of them are like this..
Click to expand...
Click to collapse
Can you try covering the microphone on the top of the phone (maybe with your finger) while your on the call and see it she hears you any better?
I think the noise cancelling mic may be causing issues for some of us. Let me know.
jasbur17 said:
Can you try covering the microphone on the top of the phone (maybe with your finger) while your on the call and see it she hears you any better?
I think the noise cancelling mic may be causing issues for some of us. Let me know.
Click to expand...
Click to collapse
First try didn't seem to make a difference... Will try again tomorrow
Sent from my Nexus 5 using Tapatalk
jasbur17 said:
Can you try covering the microphone on the top of the phone (maybe with your finger) while your on the call and see it she hears you any better?
I think the noise cancelling mic may be causing issues for some of us. Let me know.
Click to expand...
Click to collapse
Right so I left myself loads of voicemails.
Putting some bluetack on the noice cancellation mic does make all the difference in the world!
N/C Covered up:
Test 1: Speak normally on the phone Result: Can hear fine
Test 2: Speak with the phone a little away from my face (not on loudspeaker): Still hear fine
N/C Uncovered:
Test 1: Speak normally on the phone Result: Can hear okay
Test 2: Speak with the phone a little away from my face (not on loudspeaker): Cant hear anything very very faint
Test 3: Speak with the phone on loudspeaker Result: Can hear fine.
I made a thread a few days ago with mic concerns too but only when I was taking on speakerphone... I'm assuming it has something to do with noise cancelation
I was driving on the freeway today and talking on the phone with the speaker phone setting on, and the other person kept saying it sounded like I was getting disconnected. However, when I was at a stop or driving slower (without much background noise) it was fine.
Has anyone else ran into this issue? Or any issue using the speaker phone for phone calls?
Talking on the phone through the earpiece worked fine.
I'm trying to figure out if this is a hardware issue so I can get an exchange.
OTSS said:
I made a thread a few days ago with mic concerns too but only when I was taking on speakerphone... I'm assuming it has something to do with noise cancelation
I was driving on the freeway today and talking on the phone with the speaker phone setting on, and the other person kept saying it sounded like I was getting disconnected. However, when I was at a stop or driving slower (without much background noise) it was fine.
Has anyone else ran into this issue? Or any issue using the speaker phone for phone calls?
Talking on the phone through the earpiece worked fine.
I'm trying to figure out if this is a hardware issue so I can get an exchange.
Click to expand...
Click to collapse
Speaking on the phone headset is fine for me, unless i move a little away from the mic, so if im not holding the phone directly to my cheek it starts to get quiet and cut up! I tried factory reset, removing all mods, kernel still seems the same. Its really annoying bcuase any slight movement away from my face and I get complaints from the other end saying they cant hear me! Spoke to google and they said just send it back, but im willing to pay £350 and wait 3 weeks for a new handset if they dont have stock..Im short on cash right now!
exxpired said:
Speaking on the phone headset is fine for me, unless i move a little away from the mic, so if im not holding the phone directly to my cheek it starts to get quiet and cut up! I tried factory reset, removing all mods, kernel still seems the same. Its really annoying bcuase any slight movement away from my face and I get complaints from the other end saying they cant hear me! Spoke to google and they said just send it back, but im willing to pay £350 and wait 3 weeks for a new handset if they dont have stock..Im short on cash right now!
Click to expand...
Click to collapse
I don't think you'll have any luck with a replacement. In other threads I noted that I had this same issue with the Galaxy S3 and a replacement didn't make any difference. I think it's just the tone/pitch of some voices that get seen as background noise. Anyway, on the S3 someone pointed me to a setting to turn off noise reduction and that fixed my problem. I don't think the N5 has such a setting.
jasbur17 said:
I don't think you'll have any luck with a replacement. In other threads I noted that I had this same issue with the Galaxy S3 and a replacement didn't make any difference. I think it's just the tone/pitch of some voices that get seen as background noise. Anyway, on the S3 someone pointed me to a setting to turn off noise reduction and that fixed my problem. I don't think the N5 has such a setting.
Click to expand...
Click to collapse
I had an s4&s3 and never had this problem before :/
exxpired said:
I had an s4&s3 and never had this problem before :/
Click to expand...
Click to collapse
I never had it with the S4 either. I had one of the first international S3s. I flashed alot of ROMs and at some point I stopped having to change the setting, so it must have been fixed in an updated ROM.
jasbur17 said:
I never had it with the S4 either. I had one of the first international S3s. I flashed alot of ROMs and at some point I stopped having to change the setting, so it must have been fixed in an updated ROM.
Click to expand...
Click to collapse
Well, I just increased my overdraft to cover the cost of the replacement while I sell my s4, I really cant go back to it...this phone is t fast to leave. Im on the phone to google now for a replacement just to test it..make me feel better that it may just be software
I've also been getting complaints from my wife about barely hearing me sometimes. I then called for an RMA and ironically, I was talking to Google Support using the N5 and the conversation went without a hitch. I still followed through with the RMA purchase but will continue to test my N5 and see if this problem persists. I can cancel the order within the next couple of days if I find that my N5 is fine, or if it is shipped before I can cancel, then I will just return the new one, or keep it for my wife, or sell it for a small profit. I hope that it's just my wife's hearing cuz I really love this phone.
donkeyhitman said:
I've also been getting complaints from my wife about barely hearing me sometimes. I then called for an RMA and ironically, I was talking to Google Support using the N5 and the conversation went without a hitch. I still followed through with the RMA purchase but will continue to test my N5 and see if this problem persists. I can cancel the order within the next couple of days if I find that my N5 is fine, or if it is shipped before I can cancel, then I will just return the new one, or keep it for my wife, or sell it for a small profit. I hope that it's just my wife's hearing cuz I really love this phone.
Click to expand...
Click to collapse
I actually gave the kind lady an example of when it happens and her reply was "sorry sir, I didn't quite get that"
Sent from my Nexus 5 using Tapatalk
I fixed it for myself by editing build.prop.
I changed persist.audio.fluence.voicecall=true to false.
That disabled the noise cancellation for normal calls.
The fix for those without root would be to cover the secondary mic on the top of the phone I guess.
greenkabbage said:
I fixed it for myself by editing build.prop.
I changed persist.audio.fluence.voicecall=true to false.
That disabled the noise cancellation for normal calls.
The fix for those without root would be to cover the secondary mic on the top of the phone I guess.
Click to expand...
Click to collapse
Been looking for this option everywhere!! Going to try it now, Thanks!
EDIT:
Sir, I do indeed love you
Seems alot better.
Although it you can hear more noise in the background but hey.
DELETE
I had this issue and applied the fix shown above by editing the props file.... now people I call are reporting an echo their end!!!
liltbrockie said:
I had this issue and applied the fix shown above by editing the props file.... now people I call are reporting an echo their end!!!
Click to expand...
Click to collapse
Wish I could explain to Google that by turning noice cancellation off it fixes it kinda... But then id have to confess on rooting :/
Noticed it's pretty hard to talk outside.. Walking along a road.. Left myself a voice mail after my Gf complained about the noise (God she moans) sounds of cars going past really load... My replacement unit should be here tomorrow.. I hope it's not equally ****ed
Sent from my Nexus 5 using Tapatalk
I've been using the phone for a couple of days and all calls have sounded perfect, but today I finally talked to my wife with her new N5 and my N5 and I have to tell you it sounds horrible. The mic on these on the other side sounds dull and low. I hope this gets fixed with a software update. How is the fix with the build props working for you guys. I'm tempted on trying it out. I could hardly hear my wife, (maybe that's a good thing).
cral said:
I've been using the phone for a couple of days and all calls have sounded perfect, but today I finally talked to my wife with her new N5 and my N5 and I have to tell you it sounds horrible. The mic on these on the other side sounds dull and low. I hope this gets fixed with a software update. How is the fix with the build props working for you guys. I'm tempted on trying it out. I could hardly hear my wife, (maybe that's a good thing).
Click to expand...
Click to collapse
I can tell you my Gf can hear me better now.. Seems like the mic is now over sensitive now though with noise cancellation turned off
Sent from my Nexus 5 using Tapatalk
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:
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.