Huawei Nexus 6P random shutdown and won't boot without charger - Nexus 6P Q&A, Help & Troubleshooting

Hi guys, I have bought a nexus 6P secondhand but I'm dealing with the problem of random shutdowns. After that it won't boot unless it is hooked to a charger. Some facts that I think might be of some influence or what I have tried:
- I bought it with Cyanogenmod 14.1, first day flashed back to stock 7.0 but kept my bootloader unlocked;
- Today I flashed an OTA update to 7.1.1;
- It happens random while using the phone, but I manage to reproduce the failure when using Google Camera and take pictures very rapidly (don't really know what the phone activity is at that moment)
- I've got a new battery on the way, might that be the issue?
- Battery status (percentage etc) doesn't make a difference. Might as well happen at 100%
- It doesn't happen while on the charger;
- It didn't happen in safe mode (didn't test this for too long though, but the fast camera action didn't kill the phone;
Does these descriptions make any bells rinkle? For me it looks like a defective battery but I'm happy to hear some expert about this
Thank you all for reading!

Yup, mine does the same thing. I believe it is supposed to be fixed with the new 7.1 release. Its the most inconvenient thing ever. I rarely takes pics now because nobody has a usb-c charger to get my phone turned back on. I'm running stock 7.0. It's not your battery.

Well that would kinda suck, I just updated to 7.1.1 and the problem is still there. Do you have a source for this thing?

I had the same random reboots.
I too suffered from random reboots in 7.1.1 dp2. They increased in frequency gradually. One night, it stuck in bootloop. Couldn't even boot into recovery. Browsed through threads here and reddit posts. All said the only solution was to RMA as without recovery nothing is possible. Huawei is replacing the motherboard as it's under warranty.

I just updated to 7.1.1 and I also can still confirm it's happen. I called huawei and they told me it was a software issue and it's not resolved and there is no fix other than to load 6.x on the phone. So basically, I we have a turd of a phone and nobody seems to want to fix it. Google told me it was a hardware issue and now Hauwei tells me it's a software issue. Maybe it's time for a new phone.

Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.

IM0001 said:
Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.
Click to expand...
Click to collapse
I loaded the image directly from google. I've never rooted or loaded a rom on this phone. I've only run factory images. I don't have the time to tinker like I used to.

Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.

Well that was how I reverted from CM to stock 7.0, by using the flash-all function (even though the flash all didn't work, had to flash the seperate files, but result was the same). The 7.1.1 upgrade was with a OTA flash using ADB sideload because I was rooted and TWRP recovery was active, so the OTA update didn't work for me. To be honest, I don't think my problem is a software issue. Is there any 'deeper' software than the complete rom? Is the kernel flashed seperately?

IM0001 said:
Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.
Click to expand...
Click to collapse
This fiasco has been happening for tons of people for weeks now, including me. Mine was just 2 weeks out of warranty, both google and huawei are pointing fingers at each other and nobody cares. I have tried all the methods possible, to flash different versions of pure factory image, nothing worked.

What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.

also face this problem previously and Huawei replace battery. just 1 week before the warranty run out
Sent from my Nexus 6P using Tapatalk

rmoney said:
What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.
Click to expand...
Click to collapse
Every charger worked for me. Now even carry a powerbank with me for when it lets me down outdoors I can get it powered on again. Plugging it in the PC also works just fine. Even a standard samsung charger (with micro-usb -> usb C adapter) works.

hah! Mine just started doing this!
I got the phone back from huawei for the 15% battery issue.. and it came back with this issue after going to 7.1.1

Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?

Hafidel36 said:
Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?
Click to expand...
Click to collapse
Mine is locked, on 7.0 I didn't have this issue.. on 7.1.1 It started.
on developer previews for it wasn't an issue either..

This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.

andrewnelson23 said:
This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.
Click to expand...
Click to collapse
That seems to be another know defect, you should look it up on here. Plenty of people are having that problem, but it is different from this thread.

I am having the same problem too! I was trying to raise this for two times on both XDA and reddit and no body seemed to care until you came up with this!
Mine randomly happens when taking photos with HDR+ and with the battery less than 50% (based on my observation). I replaced the battery by myself not long ago though.

Huawei says going back to 6.0.1 will fix the issue... and is blaming google, saying their pixel devices have this issue on 7.1.1 too.

Related

ICS problem solved. Best of luck to everyone else.

Update - After 2 months I couldn't take it any more so I sold it and actually got a rating of "good". The other solution involved a sledge hammer. I can't believe they didn't notice the 1 hour battery life. More proof that quality control worldwide is going down hill. Apologies to who ever gets mine as a refurbished unit or parts from it.
Screenshots
http://forum.xda-developers.com/album.php?albumid=6825
Battery Life from 100% to 0%
ICS .11 & .17 - 6 to 8 minutes (Pic 1)
ICS .21 - 35 to 52 minutes (Pic 5)
ICS .24 - 50 to 65 minutes (Pic 11)
Bug count
RR & Boot Loop - once on may 14th after 2 months on ICS
Battery meter stuck at 100% - 4 times
Irregular charge and discharge cycles - lost count
Battery meter continues to go up a few % after charger is unplugged - lost count
Screen flickered - 8 times
Screen unresponsive / no input - 11 times
No sound what so ever - once
Irregular charging ping sound - lost count
ICS .24 - Finally got over 1 whole hour of battery life from a full charge.
ICS .21 - Since the 9.2.1.21 update I had it 4 times total, it's been alternating with another bug where it goes from charged to zero battery and shuts down the second I unplug the charger. The infinite power bug must only be triggered by OTA update because I tried reinstalling the .21 firmware. The zero battery "bug" could be the result of the infinite power bug allowing the tablet to actually stay on long enough to completely drain the battery. Since .11 update the charging ping sometimes stutters and sometimes plays half a ping and stops. Just had a new bug of no charging ping. The tablet and the sound was on at the time. Battery was at 82% and icon changed to charge mode but no ping sound.
ICS .11&.17 - battery drain from 100% to 0% in about 7 mins and charges up in about the same amount of time. Had this bug for over a month from march onwards. I first got the infinite power bug after upgrading to ICS, it's where the battery meter stays at 100% for hours on end without being plugged in for charging.
My TF101 is from the B30 batch.
I do not have the dock.
I haven't used the camera since HC and I just noticed there is dust on the INSIDE of my case after the "repair". There's no way to clean it except to open it myself. The trim is also now separating a bit from the main body on the top left and bottom left. When I got it back from the repair center it was just a little on the left side only.
Things I have tried
Downgrading to HC, but method was very old and likely not a complete downgrade as it did not work. Battery status wipe, Reboots, factory data resets, cold boots, changing various settings, etc. I sent it in for repair which was a waste of shipping costs. Emailed ASUS twice, response time is longer than 1 week. Calling is much faster but same results no one knew if it was hardware or software problem. After sending it in for repair the left side of my TF101 looks like it had been spudged open so they could have already check the hardware. Dragging around a 12FT extension cord is still currently the best solution I've come up with.
Thanks for making a dedicated thread!
Suggestion: Throw a couple more keywords in the title to help others find it. Eg: based on your symptoms, maybe add something like "battery meter issues, shutdown when unplugged from charger" or something similar.
did you try wiping the device?
I managed to pre order my TF101 a full week before the official release date. Now it's come back to bite me in the rear end cause my warranty is up today. I have the service number and RMA from march so maybe they will still honor it if it turns out to be a hardware issue.
Nullinvoid said:
did you try wiping the device?
Click to expand...
Click to collapse
That would probably be my first step as well, if we assume it's not a hardware problem.
knoxploration said:
That would probably be my first step as well, if we assume it's not a hardware problem.
Click to expand...
Click to collapse
Do you guys mean the factory data reset cause I tried that at least about 25 times by now in the span of a month.
yanbo2012 said:
Do you guys mean the factory data reset cause I tried that at least about 25 times by now in the span of a month.
Click to expand...
Click to collapse
Yep. Have you tried doing a reset and supplying a brand-new Google account, so that it doesn't immediately copy any old data to the tablet? (Or even just not supplying an account or connecting to WiFi / Bluetooth at all, so it's 100% stock)?
Has it ever had a custom ROM or been rooted?
knoxploration said:
Yep. Have you tried doing a reset and supplying a brand-new Google account, so that it doesn't immediately copy any old data to the tablet? (Or even just not supplying an account or connecting to WiFi / Bluetooth at all, so it's 100% stock)?
Has it ever had a custom ROM or been rooted?
Click to expand...
Click to collapse
The bug occurs even if no account is entered. Wifi, gps, bluetooth on or off it still happens. I had it rooted to overclock on android 3.2.1 I rolled back to 3.0.1 to unroot and get ICS, quite regretting that decision as it ran fine except for a few browser crashes which doesn't seem like a big deal now. I also tried downgrading to 3.0.1 from ICS, still had the bugs. It's running stock ICS right now and the browser rarely ever crashes.
did you try up up down down left right left right b a start?
Sorry, couldn't resist....
gee one said:
did you try up up down down left right left right b a start?
Sorry, couldn't resist....
Click to expand...
Click to collapse
If it had a game controller attached I would have tried that also.
yanbo2012 said:
The bug occurs even if no account is entered. Wifi, gps, bluetooth on or off it still happens. I had it rooted to overclock on android 3.2.1 I rolled back to 3.0.1 to unroot and get ICS, quite regretting that decision as it ran fine except for a few browser crashes which doesn't seem like a big deal now. I also tried downgrading to 3.0.1 from ICS, still had the bugs. It's running stock ICS right now and the browser rarely ever crashes.
Click to expand...
Click to collapse
How did you downgrade? It's my understanding that some methods leave the kernel Asus shipped with ICS in place, and hence aren't truly 100% downgrading...
knoxploration said:
How did you downgrade? It's my understanding that some methods leave the kernel Asus shipped with ICS in place, and hence aren't truly 100% downgrading...
Click to expand...
Click to collapse
That's most likely why it didn't work. I had the link to that guide saved but since it didn't work I deleted it. I'll have to wait for an official release or a better more complete method of downgrading.
I had a similar issue with my phone at one point. I went into cwm and wiped battery stats and it seemed to clear my problem up. I'm sure if it would work in this instance but it couldn't hurt to try.
headbangerkorn said:
I had a similar issue with my phone at one point. I went into cwm and wiped battery stats and it seemed to clear my problem up. I'm sure if it would work in this instance but it couldn't hurt to try.
Click to expand...
Click to collapse
Tried that too, twice.
I really don't think this is an ICS issue as you are the only one reporting it (that I've seen). Sounds more like a hardware problem to me....
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
I really don't think this is an ICS issue as you are the only one reporting it (that I've seen). Sounds more like a hardware problem to me....
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I have sent it in for repair, no change. The left side looks spudged open so they could have checked, but no one can tell me if they actually did check the hardware. They ask me to send it back for repair again. If they did replace it with andother TF101 it could be a refurbished one that has other kinds of bugs and be scratched and in worse condition than mine. If they gave me a brand new one it could also still have these or other issues. I am waiting on official or better unofficial way to downgrade to HC.
If anyone knows more about the hardware for the TF101 please post your thoughts on what could be going on with these bugs.
Could your battery not just be simply shagged?
cspiby said:
Could your battery not just be simply shagged?
Click to expand...
Click to collapse
A few days before ICS update I had 7 hours of use out of one full charge. I always shut down instead of sleep. Normal battery life is usually 6 and half to 7 hours and 15 mins. The combined total hours of use during the 100% power bugs after .21 was 4-5. If it is really the battery then ASUS is the stingiest company in the world cause they should have replaced it at the repair center when I sent it in.
has anyone suggested to clear your battery stats in clockworkmod (assuming you have it)
Sent from my Transformer TF101 using Tapatalk 2

Red Light Of Death - Should I Be Concerned?

Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
S.H.A.D.E said:
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
Click to expand...
Click to collapse
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
propably you could check the rev of those n4's (asking them in pm's). i can't imagine rev11+ have this problem anymore. I still won't believe this happened without a reason
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
These many people you speak of? That's not even half possible for it to RLOD on pure stock without any mods it's just to save the hardware its the phones built in safety net...unless you plan on OCing to 1.98ghz and set it to performance and run antutu that will most likely do it for you
Sent from my Nexus 4 using xda app-developers app
Hi,
It happened wih or without running an Antutu bench. Yes some users have reported the red light on stock with rev 10 or with rev 11.
Antutu is not directly the culprit, it's due to a bad read of battery stuff (in a stress condition even at 50% battery the phone think you are out of battery then shutdown + heat, there is an issue with some phone about the battery contact inside the phone). If it's happen you can try to let your phone in charging for hours, sometimes it's enough. But the better thing is to open your phone then disconnect / reconnect the battery.
It happened also while flashing something in recovery mod, 40% battery, flash then reboot and bam red light...
Also on a French forum it happened during a download while browsing...
I agree we not know all the conditions together when it happened but it seems this is slightly random. Maybe a combination of circumstances...
It's "just" related to some weird battery reading issue.
For example I ran a bunch of Antutu bench with / without overclocking at different battery % (even at 11% battery ) without any issues, at least until today...
Take a look here: http://forum.xda-developers.com/showthread.php?p=36304348
So does this problem happen to everybody or is only a minority of nexus 4 users affected? Do you think google would've fixed this problem by now??
Re,
It seems it's a minority phones who are concerned...
I don't know if Lg / Google have worked on the problem. As I read maybe the rev 11 are less concerned? But I'm not sure...
Don't be afraid, use your phone and if that happens rma or open your phone, there is always a solution
Alright, read a lot of threads and it looks like removing the battery and starting it again works perfectly. I also read somewhere that its due to too much pressure being applied on the thing the connects the battery to the phone.. - http://forum.xda-developers.com/showthread.php?t=2128392&highlight=red+light+of+death&page=2
Yes, it's what I said, ah I forgot this link.
When you search, you find
Happened to me a few days after I got it (100%stock, not rooted); I left it charging for some time and it turned on again like nothing happened. Didn't happened since.
Only time I had it was when I first rooted.
It got stuck in a boot loop on the "X" screen and when I rebooted to clear the cache the red light flashed and I had to hold the power button in to turn it off.
Booted into recover fine after that.
No issues since.
Alright that's good to hear. When did you guys get your nexus?? Maybe google resolved this issue.
I got mine very recently ordered in late February. It did red light because I flashed a mod which was for the nexus 7 but i flashed it on my nexus 4. I just went into recovery and flashed stock, phone was fine.
Sent from my Nexus 4 using xda app-developers app
Alright. Sounds good.
Got mine last week but it's a Rev 10 not an 11.
indoh said:
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Click to expand...
Click to collapse
That is not true.. Red light appears due to some small chip next to the battery which is hardly put in there, you just need to release some pressure and it will be fine.. (there's a youtube video)
Loosen the screws?? Do you have a link to the YT video?
Ordered mine when they were first available, got it 2-3 weeks later (end of November).
Got a bricked rev11 301k here. Tried everything untill I get my replacement (takes a bit longer since I live in holland). Check out http://forum.xda-developers.com/showthread.php?t=2177787&highlight=nexus+4+bricked for more info. Now I try to drain the battery and let it charge (put it in a cold enviroment for a full 24 hrs. Got past the google logo for half a second and saw the stock recovery before it went dead again

[Q] Vertically jerking screen problem anybody?

Had been very pleased with this device in the the three months that I've had it. Until yesterday that is.
Basically the screen is jerking up and down on its own. When looking at the homescreen, the only way I can think to describe it is it's like 60% of the screen starting from the bottom is moving up and down by about 2mm on its own. I can see it eating pixels as it does so (it eats into home screen shortcuts). It also does this jerking motion when in an application or using a the keyboard.
I haven't dropped the phone, it hasn't got wet. It is completely stock unrooted and was bought SIM free in the UK in December and not tied to any network.
Things I've tried to fix it :
1.Numerous reboots.
2. Uninstalling the couple of apps that I'd installed around the time I noticed the problem.
3. Just done a full battery drain and now giving it a full charge keeping it switched off to see if does anything, (can't say I'm hopeful).
Next step is to back up / get my data off it and do a factory reset. Despite the bloatware, the stock ROM isn't too bad.
I was also thinking of just rooting it and running a cyanogen mod also.
Would be great if anyone has any ideas what I can try or if they've seen this issue before and remedied it. I can't find anything in Google and I wouldn't be surprised if it's just a random bad luck hardware problem -- which is worse than it might be on account of living in Southeast Asia -- but the device was purchased in the UK in December. Anybody know if there is such a thing as international warranty for LG phones ?
Thank you in advance.
I wouldn't root it send it to lg it sound like a serious hardware problem the g2 seems to be plagued with problems
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
I wouldn't root it send it to lg it sound like a serious hardware problem the g2 seems to be plagued with problems
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yeah I won't bother rooting it. A factory reset has made no difference and it's actually worse now and totally unusable, the screen just pogo's / jitters up and down an inch at time constantly.
The phone was bought on 22th of December, I'm pretty annoyed at getting little more than three months out of it. It would be understandable perhaps if I dropped it, or it go wet, none of these happened and the hardware has just failed for no reason.
For sure the LG repair centre where I livein Bangkok won't want to know as it was bought in the UK. And no doubt I'll get slammed for import duty both ways together with eating the postage sending back to the UK. I think I'll feel better taking a lump hammer to it and make a youtube stating what I think of £400 phones that last 2 months and carry no international warranty.
Have you dropped your phone?
Yep it is sad I hope my g2 doesn't go through the same thing i will definitely get a backup device sooner than later but like I said earlier the g2 seems to be plagued with problems which means the nexus 5 prob has the same problems maybe maybe not I'm a little nervous now because in the us most of us buy our phones locked with contract in the UK everybody buys there devices unlocked without contract from what I've heard if your looking for a new device I would wait for the xperia z2 looks very nice
Sent from my LG-VS980 using Tapatalk
droidafx said:
Had been very pleased with this device in the the three months that I've had it. Until yesterday that is.
Basically the screen is jerking up and down on its own. When looking at the homescreen, the only way I can think to describe it is it's like 60% of the screen starting from the bottom is moving up and down by about 2mm on its own. I can see it eating pixels as it does so (it eats into home screen shortcuts). It also does this jerking motion when in an application or using a the keyboard.
I haven't dropped the phone, it hasn't got wet. It is completely stock unrooted and was bought SIM free in the UK in December and not tied to any network.
Things I've tried to fix it :
1.Numerous reboots.
2. Uninstalling the couple of apps that I'd installed around the time I noticed the problem.
3. Just done a full battery drain and now giving it a full charge keeping it switched off to see if does anything, (can't say I'm hopeful).
Next step is to back up / get my data off it and do a factory reset. Despite the bloatware, the stock ROM isn't too bad.
I was also thinking of just rooting it and running a cyanogen mod also.
Would be great if anyone has any ideas what I can try or if they've seen this issue before and remedied it. I can't find anything in Google and I wouldn't be surprised if it's just a random bad luck hardware problem -- which is worse than it might be on account of living in Southeast Asia -- but the device was purchased in the UK in December. Anybody know if there is such a thing as international warranty for LG phones ?
Thank you in advance.
Click to expand...
Click to collapse
Hello, same problem with me too, mine screen starts to jittering (like there is an earthquake inside my phone) after the latest update for kitkat, the updates says for optimising apps and such.
But recently i realize if i block my mobile data, and only using wifi for the data transfer, my phone stabilize much much better than when i used GSM/3G to do internet activity. When i used 3G my phone jittering like crazy, sometimes bottom half of my screen is gray pixels and bottom up of my screen dancing like crazy almost 70-80 % of the time. But when i block my mobile data and using only wifi, 80-90% of the time is OK, still a bit jitterish, but waaay much better.
There is also member of this forum experienced this and suggest to full cycle charger for couple of times. He say his phone stabilize after do full cycle charger (depleted ur battery until conpletely empty, than charge to 100% while turning off the phone). Im trying it tonight.
I also consult with some cellphone tech support (in shopping mall). They say maybe when i did my update, there are some data corruptions, so my phone did not update properly (corrupted). Because when you factory reset your phone, people said that it retain the latest update of software. So if you already did a corrupted update, it will stay even if you factory wipe the phone.
Seizure ?
Sent from my LG-D803 using XDA Free mobile app
It's a hardware issue, it's been discussed on this forum dozens of times. If nothing helps (including updating to the latest available version), send it in for repairs.
benz23 said:
Hello, same problem with me too, mine screen starts to jittering (like there is an earthquake inside my phone) after the latest update for kitkat, the updates says for optimising apps and such.
But recently i realize if i block my mobile data, and only using wifi for the data transfer, my phone stabilize much much better than when i used GSM/3G to do internet activity. When i used 3G my phone jittering like crazy, sometimes bottom half of my screen is gray pixels and bottom up of my screen dancing like crazy almost 70-80 % of the time. But when i block my mobile data and using only wifi, 80-90% of the time is OK, still a bit jitterish, but waaay much better.
There is also member of this forum experienced this and suggest to full cycle charger for couple of times. He say his phone stabilize after do full cycle charger (depleted ur battery until conpletely empty, than charge to 100% while turning off the phone). Im trying it tonight.
I also consult with some cellphone tech support (in shopping mall). They say maybe when i did my update, there are some data corruptions, so my phone did not update properly (corrupted). Because when you factory reset your phone, people said that it retain the latest update of software. So if you already did a corrupted update, it will stay even if you factory wipe the phone.
Click to expand...
Click to collapse
so how did it go did the charging discharging solve the issue.
nosh10 said:
so how did it go did the charging discharging solve the issue.
Click to expand...
Click to collapse
Nope, still my screen jittering...
Does anybody know how much LG would charge to fix this.
Sent from my LG-D802 using Tapatalk
Im taking it in on LG Service Center this morning, the tech guy said its Hardware problem, about some sockets loose or something like that, He fix it and because im still have the warranty, so its free, no idea how much if the warranty is expired. And i still retain the KitKat OS (4.4.2). but my data is wiped out.
So far no jitters... I let you guys know if the jitters comeback.
phone automatic jerking
hello my s9380 phone have too much heating problem…during heat my phone is again and again restarting..also my phone is automatic touches screen and automatic jerking….can anyone help me how to solve my phone problem…my phone is rooted phone….
i have this flickering problem 1 week now i try to find a way to remove the rooted status on download mode so i can send it to warranty... anyone can help? flashed kdz with flash tool but rooted still stays red.. i tried to do factory reset using power+volum down but i cant do it...
Op...sounds like you have a faulty digitizer have you sent it in yet?
After 15 months own this phone, now this problem came to me too so unlucky because this happened after my warranty end...
Such a beautiful monster with so many hardware (screen or lcd) defects
I got same issue recently for many days, typically starts after turning screen on. Finally got it fixed by discharging fully and charging back again. No issue now. And I try not to charge phone too often only when battery is close to zero. Try charge and recharge a few times if it doesn't work. Works for me ?
Passing this on so others can benefit.

[Q] Nexus 4 sudden signal loss, battery drain and shutdown!

Hi all,
First post so go easy :angel:
I've had my N4 for about 18 months. Ever since 4.4.3 (now on 4.4.4 and nothings changed) I think I have been having some probelms.....I also dropped my phone around the time of the update so can't rule out a hardware problem, anyway....
On full charge the phone is, after a random amount of use perhaps around half battery, it drops signal completely....then it start goiing crazy, opening apps clicking on things (sometimes locks up) then shuts it's self off.
Once I turn it back on it says the battery is almost out.....even though before the crash it was at 50%???? (Please see imnage below for "cliff edge" on battery screen shot!)
I have tried safe mode, I have done a factory reset and removed all and any apps except facebook. Other symptoms include forgeting wifi and other account logins!
Also worth noteing I dropped it and smashed the screen, I then had it repaired and voided the warrenty (?) because I needed it same day for work.....dont know if thats connected was working fine for a while after this happened.
I have seen various posts of this forum and other about this kind of thing but no exact answers.....any help would be great 7 months until free new phone
Sudden drop is extreme right....
Re flash factory images for a full wipe, if it doesn't work after that then its probably hardware (sadly), maybe you could get a moto g? I've heard there really good and cheap.
Sent from my Nexus 4 using XDA Free mobile app
Sounds like something went wrong during the repair or drop and that this is a hardware issue. As suggested, try flashing full stock, but I am pretty sure this is a hardware problem, unfortunately.
Sent from my Nexus 4 using XDA Free mobile app
Thanks guys .....Ive been doing as much reading as pos.
Some people are saying reather than the drop its maybe just a failed battery? thoughts?
It could definitely be a possibility. If you are up to it, you could purchase a new battery and try to replace it, there is just the risk of damaging something further.
Sent from my Nexus 4 using XDA Free mobile app
Same things happen to me. I thouhgt the battery is comming to end and orderd new one but I have read that people have some similar problems after updating from 4.4.2
On nexus 5 people also have problem with to fast battery drain. I have similar problems. I lose network, afterwards battery drop from 20-40% -> 0%
Sent from mobile
Just happened again...
http://img842.imageshack.us/img842/4405/tlam4.jpg
Sent from mobile
Not that I'm any expert but I think that your battery might be damaged
I have ordered new one. I shall see.
Sent from mobile
Please do update on how you get on Rajnus.
Nice to know Im not alone anyway :good:
ArcNexus said:
Please do update on how you get on Rajnus.
Nice to know Im not alone anyway :good:
Click to expand...
Click to collapse
Ofcourse...
Sent from mobile
Same thing is happening to my wifes NEXUS 4. Hers is a little over a year old now. It was dropped and I replaced the screen a few months ago, but ever since the new updates, her phone has been going CRAZY!
The phone randomly loses signal, battery drains quickly and apps open close (ghost touches) and then it shuts down.
I've cleared the cache, reset to factory defaults and even run in safe mode and nothing. The phone is useless now, she maybe gets 2 hours of normal use out of it before it goes completely nuts again.
One of us should roll back to 4.2.2. and report the result
Rajnus said:
One of us should roll back to 4.2.2. and report the result
Click to expand...
Click to collapse
Facing similar issues. Have posted it here. http://forum.xda-developers.com/nexus-4/help/fast-battery-discharge-t2799931/post53790262?nocache=1
Any solutions?
I am waiting for a new battery. Try rollback to 4.2.2.
ITs same on my phone after an 4.4.3 update teh N4 gone rogue before the update it was working just fine I just did factory reset got back to 4.2.1 android and its doing the same
Just to keep you up to speed...I suspect it may be the battery....or perhaps power management issue/conflict??
Trick is if I keep my battery charge above 60-65% it's fine......get below that and the trouble start.....weird. hvaing said that seems to drain faster than normal also. My hope are pinned on battery solution once Rajnus trys it.
Although not looking foward to taking phone apart to replace it
Today after the first symptom I rebooted phone and after reboot my battery was at 14%. It looks like to me that we have constant drain but system some how is not registering it properly. I will restart after every 10%
Edit: 85% ->reboot -> 57%
Sent from mobile
I'm glad to see I'm not the only one suffering from this issues as well. I replaced my screen and digitizer about 3 months ago and never had issues. Last week I updated from 4.4.2 to 4.4.3 (and 4.4.4 shortly after) and started having the same issues where there would be ghost touches on the screen once I got to around 70% battery, loss of radio/signal, and when I would restart the phone, I would lose majority of the battery charge. I tried flashing stock back on the phone and the problem still is present.
slbp180 said:
I'm glad to see I'm not the only one suffering from this issues as well. I replaced my screen and digitizer about 3 months ago and never had issues. Last week I updated from 4.4.2 to 4.4.3 (and 4.4.4 shortly after) and started having the same issues where there would be ghost touches on the screen once I got to around 70% battery, loss of radio/signal, and when I would restart the phone, I would lose majority of the battery charge. I tried flashing stock back on the phone and the problem still is present.
Click to expand...
Click to collapse
Just to repeat that is exactly what is happening to me word for word.

Battery dead?

My N10 started to automatically power off a few months ago when the battery indicator showed 10%, and that power-off number gradually increased over the past few months. Two days ago it automatically powered off when the battery was 25%. But the trouble now is that, when plugged in with a power adaptor, the battery does not seem to get charged even though it shows charging when I push the power button. I tried to power it on once, but it automatically powered off again.
Is it an indication that the battery is dead?
Also, when I was trying to remove the battery, I broke some piece around the pins on the orange ribbon cable on the left. What is this cable for? Digitizer? Can this cable be replaced somehow?
Mine started doing the same thing. It only does it if I leave it on standby for a few days. When I start using it, it will say 25% left but it will auto power down immediately. If you plug it in and turn it back on, it says 0%.
Sent from my XT1585 using Tapatalk
Mine started having an issue of not charging, even though it says it is. The battery is currently stuck at 66%. It doesn't shut down on me though. But I powered it off until I could find a solution. I don't think it's a software issue that would be fixed with a factory reset since I tried turning the tablet off overnight and charging it. Still stuck at 66%. When plugged in, it's not discharging. But it doesn't seem to be taking a charge either. Or at least not enough to charge it any higher. My guess is that the battery needs to be replaced. They go for about $30-$40 on ebay. So it looks like that's going to be my best option. I just hope the battery is the issue and I'm not buying a new one for nothing.
After I disconnected the battery for a short while and cleaned the USB port with alcohol, now the battery can be fully charged. However, the orange ribbon cable (under the guy's left hand thumb in this picture http://www.powerbookmedic.com/wordpress/wp-content/uploads/2012/11/nexus10-takeapart-006.jpg) on the left side is broken when I tried to remove the battery. Anyone know what is the cable for? I couldn't find it anywhere (ebay or anywhere else) to buy.
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
mark.l said:
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
Click to expand...
Click to collapse
I updated my N10 with the August 24 version of CM. Maybe you're right that the battery could be caused by the recent CM version.
mark.l said:
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
Click to expand...
Click to collapse
I'm running CM as well. I'll try flashing the newest version. If that's the issue, maybe they have fixed it. If not, I'll try rolling back to an older version and see if that does it and report back. To roll back, do you just simply flash an old version over the existing one? I've never had to go backwards before.
Coming back in here to confirm that my issue was indeed Cyanogenmod. Went back to the last Snapshot and it charged up again.
So I can reinstall Cyanogenmod again without it messing up ?
BackDaws said:
So I can reinstall Cyanogenmod again without it messing up ?
Click to expand...
Click to collapse
Yeah, just flash the latest snapshot. I think the date is 8/20
jsgraphicart said:
Coming back in here to confirm that my issue was indeed Cyanogenmod. Went back to the last Snapshot and it charged up again.
Click to expand...
Click to collapse
How to report it? I am not sure what version does not have this issue. Still running on older version. When having time, Ill try September's version.
mark.l said:
How to report it? I am not sure what version does not have this issue. Still running on older version. When having time, Ill try September's version.
Click to expand...
Click to collapse
Go check out the Nexus 10 cm13 thread. There's a lot of talk about it already
jsgraphicart said:
Go check out the Nexus 10 cm13 thread. There's a lot of talk about it already
Click to expand...
Click to collapse
Hi, thanks, found it and the yalready have JIRA issue for tracking the fix
so we can close this thread I assume as all of us are happy that CM caused drainig our batteries

Categories

Resources