Database Info

SM-G920I troubles... Need your expert suggestions

its been only 26 days I purchased this phone. I was very happy to buy this phone, but it didn't lasted long. I have to take this phone to Samsung Service Centre after a week due to OTA 5.1.1 update failed. Samsung Service Centre personnel had flashed 5.1.1 using ODIN and I thought everything will be fine but I am experiencing the below problems frequently
Multiple times screen freezes and no option other than soft reset (volume down + power button).
in gallery, pictures taken through camera, the picture becomes green and all its pixels gets disturbed. happened for at least 5 pictures.
in idle / standby mode, phone will not wake up only led light flashes & screen remains black. Only option for me is to soft reset.
sometimes fingerprint unlock doesn't work (there is a message that says the same) and I have to enter the backup password manually.
Phone restarts by itself at-least couple of times (2-3 times) in a day in home network, while roaming it is pathetic.
Phone restarts while using camera, opening Google play, opening Google maps, any software application.
Phone restarts while in safe mode also (suggested by one of customer support executive to monitor my phone in safe mode)
Phone restarts during a call, this happened twice
Model #: SM-G920I
Android Version: 5.1.1
Baseband version G920IDVU2COF8
Kernel Version: 3.10.61-5228538 [email protected] #1 Thu Jun 25 17:43:05 2015
Build Number: LMY47X.G920IDVU2COF8

kishore927 said:
its been only 26 days I purchased this phone. I was very happy to buy this phone, but it didn't lasted long. I have to take this phone to Samsung Service Centre after a week due to OTA 5.1.1 update failed. Samsung Service Centre personnel had flashed 5.1.1 using ODIN and I thought everything will be fine but I am experiencing the below problems frequently
Multiple times screen freezes and no option other than soft reset (volume down + power button).
in gallery, pictures taken through camera, the picture becomes green and all its pixels gets disturbed. happened for at least 5 pictures.
in idle / standby mode, phone will not wake up only led light flashes & screen remains black. Only option for me is to soft reset.
sometimes fingerprint unlock doesn't work (there is a message that says the same) and I have to enter the backup password manually.
Phone restarts by itself at-least couple of times (2-3 times) in a day in home network, while roaming it is pathetic.
Phone restarts while using camera, opening Google play, opening Google maps, any software application.
Phone restarts while in safe mode also (suggested by one of customer support executive to monitor my phone in safe mode)
Phone restarts during a call, this happened twice
Model #: SM-G920I
Android Version: 5.1.1
Baseband version G920IDVU2COF8
Kernel Version: 3.10.61-5228538 [email protected] #1 Thu Jun 25 17:43:05 2015
Build Number: LMY47X.G920IDVU2COF8
Click to expand...
Click to collapse
Seems like a broken update install. Go to the service center again and list them all the problems thats been happening with valid proof. They will again flash the OS and give it back to you. It might possibly go but most probable that it won't, so repeat the same thing until they take it seriously so that they give you either a refund or replacement or a proper repair! The problem is, Samsung India never does replacements!

Reflash is needed otherwise have Samsung replaced your S6.

update on 30-July-2015
I am just got my S6 checked with Samsung Service Centre. The personnel has understood my problem clearly and told me that he will reflash the IMEI that will make the phone to Factory OS and then he do some random hardware test and then flash the Adroid ROM.
But unfortunately, IMEI flash failed giving errors. he says there is a problem with PBA and it has to be replaced, in other words he says it is a Mother Board issue.
[What is PBA issue? if IMEI flashing fails will imply a hardware problem?]
So, at-last it is figured out that there is a hardware problem. They asked me to go for a Service Warranty and get the Mother Board replaced. But I didn't agree to the Service Warranty. I asked for a replacement. They say, they can't help me out on phone replacement, I need to check with Direct Customer Centre team.
Thanks for your suggestions.

kishore927 said:
I am just got my S6 checked with Samsung Service Centre. The personnel has understood my problem clearly and told me that he will reflash the IMEI that will make the phone to Factory OS and then he do some random hardware test and then flash the Adroid ROM.
But unfortunately, IMEI flash failed giving errors. he says there is a problem with PBA and it has to be replaced, in other words he says it is a Mother Board issue.
[What is PBA issue? if IMEI flashing fails will imply a hardware problem?]
So, at-last it is figured out that there is a hardware problem. They asked me to go for a Service Warranty and get the Mother Board replaced. But I didn't agree to the Service Warranty. I asked for a replacement. They say, they can't help me out on phone replacement, I need to check with Direct Customer Centre team.
Thanks for your suggestions.
Click to expand...
Click to collapse
Any updates after this? Samsung India will never give in a replacement! NEVER EVER. I've tried arms and legs for my previous samsungs even within just 28 days but still they never did. They keep on insisting that the quality of repair will be excellent and i don't need to worry etc etc. Also, once you lose your 7 day window, you aren't eligible for a DOA. But, with increasing complexities in smartphone hardware, its difficult to replicate an issue within 7 freaking days! Please let us know what happened with your phone now! And yea, PBA is nothing but "printed board assembly" which is that green electrical board with all circuits and capacitors and other ICs.

ultraquantum said:
Any updates after this? Samsung India will never give in a replacement! NEVER EVER. I've tried arms and legs for my previous samsungs even within just 28 days but still they never did. They keep on insisting that the quality of repair will be excellent and i don't need to worry etc etc. Also, once you lose your 7 day window, you aren't eligible for a DOA. But, with increasing complexities in smartphone hardware, its difficult to replicate an issue within 7 freaking days! Please let us know what happened with your phone now! And yea, PBA is nothing but "printed board assembly" which is that green electrical board with all circuits and capacitors and other ICs.
Click to expand...
Click to collapse
Thanks for the follow up & sorry for the late response.
Yes, after this, I had to go through a difficult time. First they insisted me to go through repair, which i denied. After justifying the problems and pain that I was going through, they offered me a new handset as a replacement. When went to see this new replaced handset, the box is of dirt and a pen mark. It was looking like a potential tampered set. When questioned about this, they responded that they are giving a new handset and the dirt on the box is of mishandling by office boy & delivery person. When Opened the box, i was shocked to see the dirt hand print on the warrant card box also, & more disturbing is that there was dirt on the screen of the phone.
It was hard to believe myself, this was happening to me and for a one month old phone. When I rejected the new handset and demanded my money back. Again they took several days for process and finally did a refund. After nearly 2 months, a happy ending.
As I was in love with S6, did 2500 rupees insurance valid for 2 year, bought tough Armor case from Sipgen & Spigen Screen Gaurd, both together I spend around 3500 rupees. Tough Armor and screen guard are not used at all, now got wasted. Need to find someone who can use the same.
Now, I am back to my SII, which is still a reliable phone for me. SII is loaded with 5.1.1 which is being developed by Lysergic Acid. Thanks for his contribution and support.
S6 & services in India made me to think of moving to iOS. New Samsung devices with New Android features are being developed, but the core OS is not stable. Now, it is time for Android developers to concentrate on OS Stability, battery consumption so that people like me should feel secured when using new phones with new Android versions.

LG V10 Boot Loop of Death

As We Knw ... The LG V10 might have the same bootloop problem as the G4
However now we are hearing that Alot of the LG V10 users are suffering from the same issues with the bootloop as owners of the LG G4 suffered. Many owners of the handset went onto Twitter and Facebook to vent their frustration.
It is said that the only fix that has been effective to date is to put the handset into the freezer or put it in an oven with the oven on minimal heat. It seems that pulling the battery or doing a factory reset doesn’t help.
Unlike the LG G5 where owners only suffered from boot loops in the earlier batches, this time around it has been said that the problems with the V10 arrived ten months after the release of the device. The only good news is that the handsets are under warranty.
"Lately, many of us experienced bootlooping devices. LG had a similar problem with the G4 and it took months until the acknowledged the problem officially and offered uncomplicated repairs. Talking to LG they said it was not yet publicly released that there was a problem with the V10 too "
see on Reddit : https://www.reddit.com/r/lgv10/comments/4yao1s/v10_bootloop_please_report_in_this_sticky_thread/
so if u want sign this Petition : https://www.change.org/p/lg-electro...=des-lg-petitions_share-no_msg&fb_ref=Default

With all the reports of bootloop, it sure seems like more than 5 people would've signed the petition by now!
Sent from my LG-H901 using XDA Free mobile app

mine too . hardware failure. sudden death. i tired putting it in the freezer for 24 hours like i read on one thread and it worked. but after few hours went back to its final death ;(

I'm curious If motherboard was exchanged after Boot Loop is the problem solved or should I be aware of repeating the problem in the near future

Mine just died too after a year. Stuck on LG logo and won't boot.
H960AY model, MB replaced under warranty

Mine just died yesterday, two months out of warranty. I was a moderate (about twice a month) user of battery waster too (which will get a phone hot).
It happened seemingly out of nowhere too. I had it charging for about an hour unplugged it and launched Monster Legends and the screen went black. I had to unplug the battery to get it turned on and then it started looping. It wasn't even hot, it was warm but no where near what it has been in the past.
I put it in the freezer for 5 minutes and it worked briefly after so I figured it was the dreaded boot loop.
I went to tmobile and they gave me 200 credit (they were aware the phone was broke) and I was able to jump to the v20 for 100.
Seeing as the specs are nearly identical it wouldn't be too far out to say that this phone has enough similarities that the G4 problem jumped to the v10.
My manufacturer date was Nov 2015, LG didn't officially acknowledge the soldering issue of the G4 until Jan 2016 so hopefully those of you with a manufacturer date past Jan 2016 will be safe.
Only reason i picked the v20 is because of the capacity, low amount of junkware and removable battery. If it wasnt for that i would have gone back to Samsung, I might still do that when the note 8 comes out.
What really urks me is that the problem came out of left field without any warning so I wasn't able to backup if I needed to. Fortunately google backs up my media automatically so it wasnt a huge loss for me.
Sent from my LG-H918 using XDA-Developers Legacy app

So, I've had my V10 since it's release on AT&T. Just went into the death loop, same as my wife's G4, hers was replaced under warranty and got the V20. Mine however was not under insurance do to a military deployment and they never added it back. I got a S7 active, anyway. Still at almost 2 years old LG WILL replace the board inside and return it to working condition, just Google LG repair, leave the purchase date blank, it being a known defect they have to replace it regardless of age. You will loose root, because it will come back with 6.0+ on it.
Good luck to everyone I am not planning on owning another LG after this, back to Samsung for me.

Dakotahorse said:
So, I've had my V10 since it's release on AT&T. Just went into the death loop, same as my wife's G4, hers was replaced under warranty and got the V20. Mine however was not under insurance do to a military deployment and they never added it back. I got a S7 active, anyway. Still at almost 2 years old LG WILL replace the board inside and return it to working condition, just Google LG repair, leave the purchase date blank, it being a known defect they have to replace it regardless of age. You will loose root, because it will come back with 6.0+ on it.
Good luck to everyone I am not planning on owning another LG after this, back to Samsung for me.
Click to expand...
Click to collapse
Were you successful in getting your phone repaired, or is it currently being looked at? I just found the page to send mine in for repair, I just hope it isn't a total waste of time since this has been my favorite phone I have owned.

Lazarus65 said:
Were you successful in getting your phone repaired, or is it currently being looked at? I just found the page to send mine in for repair, I just hope it isn't a total waste of time since this has been my favorite phone I have owned.
Click to expand...
Click to collapse
I got it back in less than a week, they had it repaired and shipped back out teh same day it arrived lol
Sent from my SAMSUNG-SM-G891A using Tapatalk

Interesting I've heard horror stories about people turning their phones in and then having problems getting status updates or having to wait a month (or longer) to get the phone back.
Of course at the same time people are more likely to complain about it than to compliment.
I was going to send my v10 in but I decided to turn it in to mobile broken and get 200 credit so it ended up costing 104 to update to the v20. I just couldn't afford to go without a phone for a week let alone a month.
Sent from my LG-H918 using XDA-Developers Legacy app

To freeze or bake to revive from bootloop?
Hello everyone, i just received the bootloop of death on my v10 3 days ago & i am seeing where the home remedies worked for many people. I am going to stick a new, fully charged battery in my phone & then try one of these remedies. I need it to stay on long enough to back up my 2,500 photos... does anyone know if putting it in the freezer or oven makes it stay on longer than the other? & also how long did you freeze/bake your phones?
Any advise would be greatly appreciated!!!

If the faulty solder connection is really the reason why this happens I would imagine baking it could potentially actually fix the problem by melting the solder to make a solid connection.
A buddy at work fixed his playstation by setting a blow dryer to hot and putting it on the solder I am not sure where the loose connection is so I wouldn't know if this method would work without knowing where to aim it.
The freeze method works but it worked for about 5 minutes for me but I only put it in for 10 minutes so it might work longer if you put it in longer.
I would just be careful with the bake method and make sure you take out the battery! Also wouldn't put it up too high.
Sent from my LG-H918 using XDA-Developers Legacy app

Thank you i am going to try putting my phone in a ziplock bag & placing it in the freezer. After 15minutes i will insert the battery & try to turn it on while it's plugged into my computer & if it works i'll leave it plugged in while in the freezer to do a backup. If not i plan on putting the motherboard pannel in the oven...

Will be my last LG
I got the bootloop of death late last month. After reading about baking and freezing stories, decided to no bother, stored most things on the SD card anyway. Changed all of my account passwords to be safe. Got it in November of 2015. Verizon was no help. Called LG, said they had extended the V10 warranty by three months from the build date, which means that I missed the cut off by three weeks. Fortunately I have a SquareTrade warranty, got it fixed in less than a week. Also had them replace the screen because of the screen burn/retention issue. Probably my last LG, there's no excuse.

I've just got mine back. after the warranty the phone just froze and and restarted and then it doesn't go anywhere after boot screen. I've sent it to the service center and it is out of warranty and they said it was the MainBoard that need to be changed and that thing cost a lot, luckily, there's this super cool lady from the Philippines and from that invoice after receiving the faulty device she' said that for you to save i will mention here it is still under warranty and "wallah" got the phone back mainboard replaced and paid nothing.

Since it seems to be heat related I wonder if qc2 is a contributing factor since qc2 cannot adjust power output instead the extra juice is dissipated as heat.
Both g4 and v10 have quick charge it's interesting these are the two phones affected by the issue the most.
Sent from my LG-H918 using XDA-Developers Legacy app

It is not true that quick charge 2.0 does not have temperature control. It has such mechanism. I have seen the phone to reduce the charge rate for example during a hot summer day or if i use the phone while charging. Problem here i think can be solved by 2 different things.
1. Too much heat generated by the hot snapdragon 808 chipset (common component between G4 and V10).
2. Component on the motherboard that got screwed after some moths of usage.
It will be very useful if everybody having the problem shares the date of manufacturing of his phone and date when he bought it. It can be seen easily from the "LG phone from" program in google play. This way we can isolate if the problem appears only with certain (early?) batches or is consistent with late too. Mine is manufactured at the middle of january 2016 and i bougt the phone in march. So far i did not have any problem but as i see problems start to appear after 10 to 12 moths of usage so it may appear every moment.

Does anybody suffer bootloop after he/she changed motherboard ?

neptun2 said:
It is not true that quick charge 2.0 does not have temperature control. It has such mechanism. I have seen the phone to reduce the charge rate for example during a hot summer day or if i use the phone while charging. Problem here i think can be solved by 2 different things.
1. Too much heat generated by the hot snapdragon 808 chipset (common component between G4 and V10).
2. Component on the motherboard that got screwed after some moths of usage.
It will be very useful if everybody having the problem shares the date of manufacturing of his phone and date when he bought it. It can be seen easily from the "LG phone from" program in google play. This way we can isolate if the problem appears only with certain (early?) batches or is consistent with late too. Mine is manufactured at the middle of january 2016 and i bougt the phone in march. So far i did not have any problem but as i see problems start to appear after 10 to 12 moths of usage so it may appear every moment.
Click to expand...
Click to collapse
Yesterday I came across two LG V10s that had bootlooped. Both were H961N models and doing a quick check by using its IMEI, I found the manufacturing dates of both the phones being October and November of 2015 respectively.
Mine is also the H961N but produced in January of 2016. Fingers crossed.

I just got mine back today. Looking at the email they sent me about the phone it was a capacitor that failed. Before sending it in I put the phone near a fan with the back cover and battery removed and it booted up for a second before dying. I am also out of warranty by a year and they still took it in for free. Just leave the date blank. So the freezer method does work, but it has to be kept cool or it will shut off again.

GPS issues after Nougat update

Hi all,
I'm shouting out just to see if anyone has experienced GPS symptoms like mine.
I installed the Nougat update (via LG UP I think). I then even hard reset once Nougat was installed.
Now when I use GPS in driving apps like Maps or Waze, it loses the gps lock and searches for location quite frequently.
I even downloaded the GPS Status app and did a cold start and refreshed my agps data etc...
I'm pretty sure I had no issues before the upgrade (but I also recently went on a long road trip whereas I don't normally drive which could have accentuated the dormant issue) so was just curious if this has happened to anyone else?
I'm familiar with some hardware G5 GPS issues so before I contact Verizon or LG I figured I would just see if anyone has had any post Nougat GPS issues.
Thanks,
T

I have the same issue. It is very annoying. Hopefully they sort this out.

Strange, could possibly be a coincidence and is the hardware failure finally setting in, but the timing sounds a bit suspicious..

Yes, I've got the same thing since the nougat update along with a host of other problems that I'll bring up in another thread. Ok, I'll touch on them here, but start a new thread rather than thread-Jack. Since the nougat update I have four noticeable problems, the NAV issue being one of them. Two other minor annoyances and one big one. When I plug in a fast charger, oem or not (I have several), I frequently get TWO notifications, one that says slow charge and one that may say charge, or fast charge. If I unplug and replug, everything is fine. I've also been getting ghost images when I change screens. Also, my multitude of Bluetooth headsets (mostly LG) have become unusable for phone calls. Fine for streaming audio, but unuseable for calls. All these problems started after the nougat update. I did a factory reset with no change. Verizon is going to send me a new phone. If it's not on nougat, I'm NOT going to update it! I was very happy with my phone until I got the update, now I'm just frustrated. When Google/LG/Verizon fix the bugs, then I'll update! Right now I'm just aggravated with the whole thing.
D Dave

my also having same problem ....

fyi, I ended up contacting Verizon and they eventually escalated me to tier 2 and the tier 2 guy said it was a rare known issue to have a hardware gps issue and he said to swap the unit. Since I wasn't under warranty with them I contacted LG and will send it in to them.

..same issue
@up
What does "swap the unit" means?
Wysłane z mojego LG-H850 przy użyciu Tapatalka

@MARCIN2M - It means they were willing to send me a new phone in exchange for the old phone.
Update... I got my phone back from the LG repair center. It's the same phone I sent them (same serial number). On the very sparse notes that came in the box, it said they re-flashed the memory. I don't know exactly what was meant by that. GPS seems to work now.

tahlsr said:
@MARCIN2M - It means they were willing to send me a new phone in exchange for the old phone.
Update... I got my phone back from the LG repair center. It's the same phone I sent them (same serial number). On the very sparse notes that came in the box, it said they re-flashed the memory. I don't know exactly what was meant by that. GPS seems to work now.
Click to expand...
Click to collapse
Hi, were you able to find out what flashing your phone means?

Sorry tase25, I'm not sure. My gps is still working great even today.

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

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

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

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

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

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

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

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

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

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

Earpeice, Microphone, and Headphone Jack not working, even after reboot and updating

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..