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,
Related
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
The issue is real and Google have confirmed it. They've been working on a fix and the official word was an OTA update was going to be released this week:
Just a heads up that our initial tests look good and that we are expecting to send out an OTA within one to two weeks that will resolve the issue. Thanks for your continued patience!
Click to expand...
Click to collapse
code.google.com/p/android/issues/detail?id=13674
silfer said:
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
Click to expand...
Click to collapse
Argh. I did not have this problem until yesterday (had the phone since January). Now my phone will reboot right after a call.
apreichner said:
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
Click to expand...
Click to collapse
I've had three Nexus S so far. The first one I picked up on dec 16th and didn't get a single reboot on - but the oleophobic coating on the screen was coming off in spots so I swapped it for another unit.
The second unit had issues rebooting. I saw it immediately - it rebooted while sitting on my desk. I could constantly recreate this by streaming audio over BT in my car - every 10-15 minutes it would reboot.
I picked up a mt4g for a few weeks to see if they could sort whether this was a hardware of sw issue (that thing is a brick to hold) and eventually picked up a third Nexus S once they identified it as a SW issue. This device has not rebooted a single time in the 27 days I've had it. I can stream audio and make long calls without an issue.
All three devices have operated with identical configurations. Based on this I'd say that some units are worse than others.
Maybe it's issue with the hardware tolerances and some hardware that falls within the accepted tolerance is not operating as expected and causing kernel panics as a result. This would explain why some have this issue constantly and others rarely or never see it. Perhaps it's something seemingly unrelated that everyone experiencing the reboots has in common. It would be nice if Google weren't so tight lipped about this. Supposedly the OTA will address these issues and moving forward it should be irrelevant.
I get this issue at least 60% of my calls (not that i call much). i have made 4 calls today, and 3 of them my phone rebooted during the proccess.
I am returning this to CW tommorrow for a replacment unit, i love the phone dearly but do not want to be robbed for £429 but not being able to take it back if they do not resolve.
It could be a batch issue, or something i guess, but that's not my job to find that out, that's for the people i paid for the hardware/software
I hope i get another unit, and if not problem free at least i can rely on a warranty, hopefully making sure if google slack on fixing this i can get my money back.
If it fixes soon or the new handsets ok, i can keep this lil beauty of a phone
I've had my SNS since launch. My phones has rebooted on me twice. It was right after playing a 3D game. Right after i exited the game the phone rebooted. Funny though, it hasn't happened again.
I've gone back to using my Desire until Google sort this out. For me, any call above 5 minutes has a 50% chance of rebooting the handset.
The handset (running stock 2.3.2 and un-rooted) will on occasion spontaneously reboot as well. Not good.
It is a bug that seems to be very limited in scope but is very serious for those affected. Personally, I've never had it happen to me or my wife.
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
apreichner said:
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
Click to expand...
Click to collapse
Getting the insurance is definitely the right choice. I hope you enjoy your phone and your stay here!
I get periodic reboots on both my phones.
It is not that noticeable, since it often happens when I am not using the phone and unless I glance at it and see the start animation, I may be unaware of it.
But it has happened during a call as well (couple of times on each phone) and then it is definitely noticeable.
I have this bug... not during phone calls but random reboots. 2-3 a day. I hate it but its tolerable.
Weird, I don't have this bug
If flashing a custom rom, the problem will be solved? Since i am considering if i should get Nexus s later on.
Thanks
Hey guys,
My mic and headset are not working at all when making or recieving calls. When I restart my phone it works for a while but it reoccurs after few minutes. I tried reflashing and wiping my phone still it's persistent. I get bluish greenish lines flickering at the screen rarely which does does cause the screen to freeze sometimes. Any help? Is it a software or hardware isssue?
Thanks in advance
My mic stopped working this week. Talked to support and they got me a new phone should be here monday or tuesday. Still inside of the one year warranty. I was on beta O came back to 7.1.2 still did not work. it is a hardware malfunction. Its weird because ok google works but i have to yell at the phone for it to hear me. I have a buddy that has a similar issue to what you have going on. He drops his all the time so I am assuing that is why his is broke. If you have the extended warranty through google just use that its no cost.
Having issues as well, though a little different. When I plug in a wired headset - but only one with a mic - things go haywire. The volume starts gradually going down, and the Google Assistant screen comes up.
Sounds like this is a hardware issue, so need to start the return process. Problem is, I am not the original owner. The original owner said she bought it direct from Verizon in November. So still under warranty. Do I need a receipt or do they just go my the IMEI or serial number?
fungo45 said:
Having issues as well, though a little different. When I plug in a wired headset - but only one with a mic - things go haywire. The volume starts gradually going down, and the Google Assistant screen comes up.
Sounds like this is a hardware issue, so need to start the return process. Problem is, I am not the original owner. The original owner said she bought it direct from Verizon in November. So still under warranty. Do I need a receipt or do they just go my the IMEI or serial number?
Click to expand...
Click to collapse
Just the IMEI and serial. When they ask for the account associated with the pixel just give them your gmail account that you signed into the pixel with.
I had the same problem, thought it was a software problem but then it wasn't, talked with Google support and they shipped out my replacement phone!! Within 2 days I got it and ever since then it worked fine!
I didn't had warranty but they made an exception for this one time so I was blessed!!
this is odd. i have the same issue. I can get it back temporarily by rebooting... didn't start for me until yesterday.
As of Saturday, my Pixel refuses to make or take phone calls. It seems to work flawlessly in all other regards.
If I get a phone call it takes a long time to acknowledge that I've selected to answer the call. I can then neither hear the other person, nor can they hear me (no line noise, complete silence). If I choose to hang up, the Phone app ceases to work, and within a few minutes the whole phone reboots. Making call doesn't even get that far, as as soon as I initiate the call the phone app ceases, and again, within a few minutes the phone reboots.
I chatted with Google Pixel Help twice yesterday. They checked a bunch of things with me, then suggested a factory reset when those didn't work. Yesterday, the issue only seemed to occur after the phone had sat idle from a reboot for a while. So initially after the factory reset things were working. When I got home, however, the problem persisted, and was now occurring every single time the Phone app was used. It's now 100% reproducible:
https://youtu.be/5YSJpLVBR1A
https://youtu.be/sENelMnE4eI
I've tried using 3rd party dialers, but they all seem to throw over to the stock phone app as soon as the call is made. I have no idea what happened.
Google hasn't been helpful, as their support person said I'm out of warranty (purchased in late-Oct. 2016), and thus have to deal with Telus. I have I feeling I know how that's going to go (ie: not well).
Anyone else ever experienced anything like this?
Happend to me too.
I just got an email back from the Google Store Support manager. She just reiterated that the phone is out of warranty and suggested that I visit UBreakIFix to see about getting it repaired.
Overall, I'm quite unimpressed with Google's support on this. If I have to replace the phone, I'm seriously going to consider something other than Google.
saltorio said:
I just got an email back from the Google Store Support manager. She just reiterated that the phone is out of warranty and suggested that I visit UBreakIFix to see about getting it repaired.
Overall, I'm quite unimpressed with Google's support on this. If I have to replace the phone, I'm seriously going to consider something other than Google.
Click to expand...
Click to collapse
Well I mean if the phone is out of warranty they are following the same guidelines literally any other manufacturer would. Their response is kind of a non-problem and your reaction is kinda poor. Anyways for now try rolling back to the factory image before current and then updating back to current, might do something.
Edit: preferably keeping the -w intact but you can try dirty flashing it first
Hey friends. I posted here a few weeks back saying I was having issues with my Pixel freezing and restarting itself. I've already factory reset and reflashed. No dice. My warranty is out by a month so I can't get it replaced.
I have a friend who said he could replace the battery for $35 USD. It's a great price but I don't know that it's 100% the battery. I was hoping you all could maybe chime in and let me know what you guys think. It's very intermittent. It can happen when I'm watching a YouTube video or during a phone call. I've seen a lot of other people having this issue and I think it's crazy Google won't back there problem when it's a known issue. Any advice is appreciated.
Also, an unrelated question. I never seem to get the current security patches until the end of the month. I still don't have Feb. patch and my wife and a friend of mine have had it for a while.
Thanks!
Edit: More information
If the battery is charging and discharging properly, I don't know that I would attribute the freezing/restarting to the battery at all. The Pixel microphone defect could be one possible cause. It's a small crack in a solder joint that can intermittently cause the phone to freeze or reboot when it attempts to use audio. Just do a search for the issue and you should see some articles about the issue.
ForeverZ3RO said:
Hey friends. I posted here a few weeks back saying I was having issues with my Pixel freezing and restarting itself. I've already factory reset and reflashed. No dice. My warranty is out by a month so I can't get it replaced.
I have a friend who said he could replace the battery for $35 USD. It's a great price but I don't know that it's 100% the battery. I was hoping you all could maybe chime in and let me know what you guys think. It's very intermittent. It can happen when I'm watching a YouTube video or during a phone call. I've seen a lot of other people having this issue and I think it's crazy Google won't back there problem when it's a known issue. Any advice is appreciated.
Also, an unrelated question. I never seem to get the current security patches until the end of the month. I still don't have Feb. patch and my wife and a friend of mine have had it for a while.
Thanks!
Edit: More information
Click to expand...
Click to collapse
This has happened to me on a few sparse occasions, I've not found any particular trigger, but can confirm it is not the battery. I also highly recommend against doing a third party battery replacement on any phone that lacks a removable back honestly. I would recommend fully reflashing using the flash all file with the -w intact (back everything up obviously) a couple times. As far as the security patches they are released on the 5th of every month I believe. Manually checking for system updates may resolve your problem as the ota signal might just not be pushing to your device properly. If this doesn't work then you can always grab the factory image on the day of release and manually flash it (without the -w obviously).
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..