Related
Hi everyone,
I bought a Oneplus One in past July with enthusiasm.
After few days of use, began the "ghost swipes" issue (as every owner of the One) and multitouch issues (my phone is basically recognizing 1 finger at the same time) preventing any pinch to zoom or notification expand gesture.
But that's not the worst, after few weeks of use, began the most annoying issue I ever had on a device : my touchscreen is going crazy detecting contacts on the touchscreen by itself.
This issue began slowly but is getting worse over time. I noticed that the issue appears only after keeping my phone on my pocket for a while... I need to wait up to 10 mins after taking it out for the problem to disappear.
At first, a simple reboot was temporary the issue but not anymore. It's simple, I only can use my phone 10% of the day... During the remaining 90% it calls numbers, takes photos, deletes messages by itself...
Watch this video, it speaks for itself :
I do not know if anyone else has the same issue or not and I can't determine if it is a software problem, a hardware one or a combination of both...
I opened a support ticket on Oneplus website (but it seems I won't have answer before a few weeks... ) and I don't even know if they will accept doing a swap (OPO support is one of the worst I know).
What's sure is I am really disapointed by this device, whatever its price tag... And I won't recommend it to anyone and I won't give out my invites.
Guys, don't buy this phone and wait for the next Nexus device with which you'll have a high quality device at a decent price...
I let them a little while to find a fix to this situation and if nothing comes, I'll buy another one and use all means at my disposal to be refunded (the French law is quite helpful in the field).
.ant1
There are many users facing this issue. Check around the forums you'll see numerous threads about this issue, you might also find some tips to reduce the issue.
AFAIK this is as of yet not permanent fix for this issue, but since i dont have this issue i havent been following it so i might be wrong. Good luck though.
Google "bacon 55"
Sent from my OnePlus One using Tapatalk VIP
The only solution is to RMA the device. Took me 6 weeks of haggling with One Plus but finally the RMA is in process.
Alright,
Phone: Nexus 5 2013
Android: 5.1.1
Country: Canada
So I've started to get a lot of issues on my Nexus 5 that I ordered back in November 2013 (when it was released) and they are too big to be left alone. If I cannot fix them, I'll have to buy a new cellphone and there's none that interest me right now, nor that I want to change my current Nexus 5.
Issues:
My Nexus 5 doesn't connect to my cellular network anymore. I'll stay on "No service" and refuse to connect to any Operator Network stating that the network is unavailable at the moment, even thought it is. Sometimes, it'll connect to the network for 15 to 30 minutes, before losing it for the next 8 hours.
It becomes hot really, really quick randomly. The upper back part of it becomes hot, and according to the Nexus 5 architecture, the battery isn't even located there so I don't know what could make it heat up like that. This happens even without it being charged, and without me using it a lot (games, apps, etc.)
The phone will randomly restart for no reason, and sometimes stay stuck on a "boot loop" (Starting apps X of Y... before restarting).
The vibrate mode is messed up. It'll vibrate every 30 seconds for a notification (email, Facebook, SMS, etc.) despite the fact that there's nothing, absolutely nothing. Right now I disabled the vibration/sound mode to avoid that issue.
The battery gets drained really, really fast. Like overnight, while not being used it'll fall from 100% to 5%. It never used to do that. When I don't use it overnight, it would lose maybe 20%, even less than that. It started recently as well.
All these issues were present in past versions of Android, starting at 4.4 so I doubt the version is in cause here, but it's still a possibility I guess.
I got my SIM card changed for a brand a new one, troubleshooted the phone with everything I could find online before giving up and restoring it to it's default settings, but the issues are still present. I don't know what I should check anymore. If you have any comments, experiences or solutions I could try to solve my issues, please let me know since at this point I'll most likely try all of them. Also, if you need more information on my phone, system, etc. let me know as well.
Thank you.
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
firemaned said:
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It used to be rooted, but it's not anymore. Any way I can make sure that it's rooted or not? When I used the SuperSU app back then I realized at some point that it wasn't rooted anymore (it was telling me that this app can only be used on rooted devices). I think the bootloader is unlocked because when I open my device, it shows me the little lock icon, but it's open (unlocked). Also, it's freshly reset to factory default (from yesterday).
dahawthorne said:
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
Click to expand...
Click to collapse
I already did a Factory Reset on my phone yesterday, so I guess I don't have to do another one? Right now, if I follow what you just told me, I should wait until the release of Android 6.0 (M) and upgrade to it then see if it solves my issues. I just hope that it won't take a long time to be pushed to my phone like it was with Android 5.0. Or your other solution is to flash the latest preview for Android 6.0 (M) on my phone and see how it goes, right?
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
dahawthorne said:
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
Click to expand...
Click to collapse
That was my original plan. I called the Play Store support this week and they told me that my phone was elligible for a replacement till April of 2016. I found that weird because it would make it a 2 years and a half guarantee but at least I had my backup plan in mind. Then I called today to order a replacement and the guy told me that my guarantee expired back in November 2014 (1 year after I bought my Nexus 5, which made sense) so now I'm stuck with this one. I don't know why, but since this morning (after creating this thread), the cellular network cameback. It still drops sometimes but only for a few seconds and if not, I enable/disable the Plane mode to make it connect again. However, the battery drain, phone heat, random restart and messed up vibration issues are still present. I can deal with them however until Android 6.0 (M) gets released. The most important thing was the cellular network. We'll see tomorrow how it goes. Still awaiting tips and tricks for my other issues if anyone have some.
For the battery draining issue, I think I have the paid version of Greenify somewhere and was thinking of using it to see if it helps, even though I didn't have that issue at the beginning.
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
CalculatedRisk said:
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
And I imagine that the factory image is still present on the device? This is what I find weird, because when I "reset" my factory to defaults, it restores it to Android 5.1.1 even though the device came with 4.x. I come from the computer field, and a Factory Reset on a computer uses the manufacturer's image present on the CD, DVD, USB or partition given with the computer to reinstall the original OS that was present on it and the OEM software as well. If the computer was eventually upgraded to Windows 8.1 and came with Windows 7, Windows 7 will be restored, not Windows 8.1. So I can understand now that a "Factory Reset" doesn't really return the device to its factory state, right?
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
dahawthorne said:
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
Click to expand...
Click to collapse
I did have an OTA update to 5.1.1, yes.
And I talked to one of my friend who's really into phones (used to work for Bell and he's usually the person I go to whenever I have issues with my cellphone), and he suggested me to wait until Android 6.0 comes out, and then to fastboot it on my Nexus 5 since OTA updates can be buggy sometimes. I could actually fastboot the phone right now (well tonight) with Android 5.1.1, but if Android 6.0 is to come out next week (or the one after), it might worth the wait, depending on whether or not I can keep the cellular network working. Otherwise I would have to go through 2 flashboots in 2 weeks and I can't really be bothered to do that
And I don't know where the CPU is in the Nexus 5 (I could look it up) but the zone where the heat is isn't where the battery is so there's that. However, my friend told me that the fact that my cellular network isn't working could explain why the battery is being drained so fast, but can't explain the vibrate mode and random restarts issues.
I was having battery issues on Stock ROM, but now I am using CM12.1 so battery is not draining very fast.
When I am inside my home or in some other house or building, the network disconnects very often. However, if I am outside, the network works pretty well.
The notification LED, when being configured using CM12.1 settings, shows blue color on green color selection and green color on blue color selection.
I had some of the same problems with my phone, it would reboot randomly throughout the day. With mine if I charged it overnight with it off when I turned it on in the morning it would only be at 85%. I ended up contacting LG and I paid $170 to get it fixed, they have replaced the mainboard twice so far. After the second time it had no issues, and that lasted a couple months but I have sent it back again to be fixed. If you bought the phone on a credit card they usually extend the warranty by a year, that's what I did, filed a claim and they sent a cheque for the repair cost, very simple actually. But I suspect it might be the same problem as mine, some hardware issue, especially if you've reset the phone.
Just for info, the CPU is indeed at the top rear of the phone, so this is undoubtedly where the heat is coming from.
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016 - see step 11 saying "The Quad-core, 2.26 GHz Snapdragon 800 SoC is layered beneath the RAM".
I reckon it's a rogue app, which I hope isn't a system app, running wild - a system app will be hard to cure.
A ROM refresh is probably a good place to start, and if you can wait for Android 6.0 then why settle for less...
Wiped my os on nexus 5 trying to install nethunter only comes on in twrp. very new to this be easy on me ive previously installed a vm lab with kali linux.
I have downloaded adb and fastboot
Using winace . Before this my pc would not recognize my device, "no drivers". But now it shows up on the pc control panel as active and found
However snap pea still cant find drivers although now it says are you fornatting your phone with only one option "yes" then it just dissappear. ... but before I downloaded adb, fast boot ... snap pea was simply saying no drivers found.... Please help. ..thank you.
Sent from my GT-I8190 using XDA Free mobile app
Here's an update on my situation: the cellular network is back at both my house and my workplace. The way it works, it seems that it takes it a day to "adapt" itself to the location and then gives me network. So at first after the Factory Reset, I didn't have network at my house, the day after I did. Now, when I went to work on Monday I didn't have network, but when I did on Tuesday, I did. My job is an hour of road away too, and at some places on the road I don't get any network, but it happens less and less as I travel back and forth.
The random restart and overheating issue are still present however. I didn't test the notifications (on vibrate) but I will soon. As long as I have my cellular network, I don't care about the other issues, until Android 6.0 (M) gets released and I fastboot it on my phone.
Now, since I bought my Nexus 5 using a MasterCard, I remembered that they have a promotion which double the guarantee on electronics (up to a 1 year), which means that I have a 2 years guarantee on my phone. So I called LG, and they have a promotion right now, $150 to get my phone repaired by their tech center IF it can be repaired. If they can't, they send it back and gives me a 50% refund (around that number).
My current plan of action is to wait for Android 6.0 (M) to get released, flashboot it on my phone and see how it goes from there.
Thank you for all the replies so far, they really helped me and still help me today
Good luck man. Keep us updated.
Sent from my Nexus 4 using XDA Free mobile app
Alright so, I fastbooted Android 6.0 on my Nexus 5, and it seems to have done the trick. I have network everywhere now, even on the road. I still lose it from times to times (a few seconds only), but this is a "normal" behavior considering the carrier I have. The notification issue is also gone, and so does the restart issue since I didn't have it once so far. But I only fastbooted it yesterday evening so it might be too soon to say that.
Now, I still have the "overheating" issue, but it could be from me playing Fallout Shelter, I really don't know. I used to play Clash of Clans alot, and graphically speaking, I think it's more demanding than FS, but I never had that overheating effect before. One thing I noticed however is that after fastbooting Android 6.0, my battery drops real fast, even when idle. I thought that Android 6.0 was supposed to improve the battery life. I'll try to see what process, app or activity is taking the most juice out of it, but I'm sure this isn't normal.
Alright so it took me an hour to go from my house to my workplace, and my battery went from 34% to 12%, while being on standby. This isn't normal I guess. I'll need to charge it to 100% once, and then use the Battery setting to see what's taking all the juice.
Might have spoke too soon. When going to work today, I went in a room where there's usually no signal (or the signal is very weak), and lost the network. It's normal in that room so I didn't pay much attention to it, but now I'm not able to get back on the network. Even searching for the Network Operator fails. Sigh, it really looks like I'll have to send it to LG for repair. I guess I need to fastboot it first to erase all my data, because they need to use my phone to test the repairs they make?
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.
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.
reyscott said:
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.
Click to expand...
Click to collapse
It has to be at a point now to contact the OEM. On countless occassions I've factory reset and gone to different ROMs from scratch with the issue returning. Thanks.
Hats off to Verizon! I had purchased their total protection plan awhile back where you warrant your phone for 11 bucks a month. If it's lost or stolen you pay a deductible. With this issue I was hesitant but went in anyways.
For one, I didn't have to pay anything because I brought it in on the premise that it's a manufacturer defect (microphone hardware issue). Now if they determine my phone is damaged, the warranty company charges you 299. Mine won't be.
I go in yesterday and they told me I'll be receiving the replacement at my house TODAY. I even got the FedEx shipping memo for it being delivered tonight. Then I can just sent my old one in the same box that's a prepaid label.
Super happy about this!
No Sound
davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC
cc999 said:
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC
Click to expand...
Click to collapse
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.
New Pixel
davidisflash said:
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.
Click to expand...
Click to collapse
What's the manufacture date of the new phone?
CC
cc999 said:
What's the manufacture date of the new phone?
CC
Click to expand...
Click to collapse
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.
davidisflash said:
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.
Click to expand...
Click to collapse
better than having a broken phone. I was under the impression that the newer replacements came from google and were unlockable, but I guess only a lucky few,
I'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..