Ok I've had the Moto Z for a while and its a great phone. Or it was until a few weeks ago. In the space of a couple of weeks a few official updates were sent to my phone and thinking nothing of it I updated as requested. The last update has seriously messed the phone up.
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
What I've tried to do about it:-
- I've tried running in safe mode, which makes no difference
- I've tried a full reset, which makes no difference
- I even unlocked the bootloader and installed a custom OS (Lineage). Thinking that obviously this will wipe out the new update from Lenovo and the phone would have to work properly again. But no, nothing changes, somehow Lenovo have done something beneath the OS that's causing these problems.
The question:-
Does anyone have any idea what could be causing this or have you at least seen these issues before?
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
apocalypse_bg said:
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
Click to expand...
Click to collapse
The point of my post is obvious, I've got a issue with my phone and want to know if anyone has seen this issue with the Moto Z before and if they have any idea what may fix it. The question is right there near the end:
"Does anyone have any idea what could be causing this or have you at least seen these issues before?"
Click to expand...
Click to collapse
apocalypse_bg said:
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
Click to expand...
Click to collapse
I've tried a different ROM:
- I even unlocked the bootloader and installed a custom OS (Lineage).
Click to expand...
Click to collapse
Honestly don't know how my post was unclear at all, but I've gone and tried to make it even more clear with a quick edit, hope that helps.
I have exactly the same problem. For me it occurred after updating to nougat. So fare I tried nearly everything. Disabling nearly everything to the bare minimum, custom ROMs, resetting, trying to flash only parts of the Android 6 firmware (modem, Bluetooth, DSP) since a complete downgrade is not possible, using all kinds of battery tools with a rooted device, using custom kernels... I always ended up with a constant battery drain of 3 to 8 percent per hour no matter what I did. Same in flight modus. Since under Android 6 the device didn't show this behavior I think that the problem must be somewhere in the firmware beneath the OS level. An the cruel thing is that sometimes without a reason for maybe an hour or two my moto z doesn't drain an works fine so that I do not believe in a hardware problem.
Thanks for the post. Yeah it seems like something has been changed underneath the OS. I know that sometimes memory config gets changed with newer Android operating systems (at least I think so?), but could that cause all these problems?
BTW, do you have all three of the problems I mentioned? Battery drain, sound stops working and charging stops working?
Since in this condition the Moto z is not really usable for me I switched back to my old phone and I am not using it that much as a daily device, I cannot really tell about sound or charging problems. So far I did not notice those problems.
DonnieDio said:
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
Click to expand...
Click to collapse
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
DonnieDio said:
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
Click to expand...
Click to collapse
None of the above ever happended to me
StarStorm said:
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
None of the above ever happended to me
Click to expand...
Click to collapse
I've never seen anything like it before. Its so random as well. I mean yesterday I rebooted and then charged the phone before I left for Football at 4pm. At about 11pm that night I heard the battery low sound (45% of the battery had be used by Android OS..). First thing I thought of was that usually the phone wouldn't still be making sounds by now. Since as I said earlier usually the speaker stops working along with charging within a hour or so of a reboot and this had been over 7 hours without a reboot. So I tried plugging it in and it started to charge. But then when I woke up this morning again the sound was disabled and it won't charge, it just took longer for the problem to occur this time..
How can we stop asking to update to this patch?
I has already disabled this on the developer preferences but still asking every 10 minutes
Any suggest please
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
doug107hk said:
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
Click to expand...
Click to collapse
Yep I've also had that as part of my problem, though it had only happened a few times over the course of the month so I forgot about it with all the other problems I mentioned going on.
Basically my phone would be sitting on, say 40%, and after a reboot it would start up in the single digits.
I recently tried changing to a custom kernel to see if maybe that was causing the problem (I'd already tried changing OS). But all the problems are still there using the new kernel. Think my next step should be to try to go back to a 7.0 Android version. Are there any custom Android ROMs using 7.0?
It is said that the Motorola Manager can rescuer lost data even if the data has been covered on phone , is it true ?
Just curious what came of this. My Z, unrooted, has started running crazy hot and the battery life is not good. 6-10 hours. When I connect it to my Anker PowerDrive 2 in the car, the battery actually discharges faster or I get the slow charge warning.
Hi I have exactly the same problems as the op and tried resetting to no avail.Its driving me nuts.
Short update about the massive battery drain problem: like I wrote above, in the past weeks I tried everything from custom kernels to custom roms, resetting, deleting and so on. Nothing helped. So I went back to stock and didn't use the phone the last weeks. Today I read in an other thread about bluetooth problems that a fix for the not working bluetooth was to activate flight mode, restart the phone and deactivate flight mode. So I activated flight mode, pressed the power button for 10 seconds or so until the phone restarted an deactivated flight mode. And now the absolute strangest thing happened: for the last 5 hours the phone lost 0% battery in standby with wifi and lte on. Since I did all the mentioned things above without any effect I do not understand this at all but right now I think that this could be a (temporally) fix also for the battery drain problem.
Related
After updating to ICS I cannot charge my phone while it's off.
I always charge the phone during the night and never let it fully die but today I didn't see that the battery level is so low and my phone died now I cannot turn it on to charge it. I get constant reset, my LED flashes blue/red and it resets non stop.
2 nights ago forgot about that problem and woke up at 3 o'clock to find out that my phone has been restarting for about 4 hours.
Give any advice.
P.s. My girl's also with Neo, also updated to 4.0.4, same problem there...
A quick video to show the issue: http://youtu.be/ajwFwEeg0gY
DNDimitrov said:
After updating to ICS I cannot charge my phone while it's off.
I always charge the phone during the night and never let it fully die but today I didn't see that the battery level is so low and my phone died now I cannot turn it on to charge it. I get constant reset, my LED flashes blue/red and it resets non stop.
2 nights ago forgot about that problem and woke up at 3 o'clock to find out that my phone has been restarting for about 4 hours.
Give any advice.
P.s. My girl's also with Neo, also updated to 4.0.4, same problem there...
A quick video to show the issue: http://youtu.be/ajwFwEeg0gY
Click to expand...
Click to collapse
I just found out after reading your post that I have the same problem but I removed some app so don´t know if has anything to do with removed app!
Downgraded to GB and you can charge your phone normally. After be careful to don´t let your phone battery complete drain.
I am trying some roms besides official to see if I found out one that can allow charging in off mode. Is annoying this….
EDIT1: I just made a clean update from GB to ICS without removing any app or installing any different kernel and is charging in off mode.
So this behavior any something to do or with removed app or with different kernel installation!
Have to find out.
EDIT2: No. Is not Kernell issue or Super User that I just flash by CWM. So last option is any removed app or eventually any combination of factors.
Yes, I am in the process of downgrading, good thing is that we have two Neo's so I can use the other one's battery
Dudes! I managed to charge my phone but darn it wasn't easy.
Now one of these is on the way: http://www.ebay.com/itm/190586739151?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649
Are you sure it's a hardware issue, because I've tried 4 different ICS ROMs (Stock ICS, JJDoctor's, KA20 and AOSP 4.0.4) and I've been able to charge my phone while off in all of them.
Maybe getting your phone to a service center will find the culprit.
Akath19 said:
Are you sure it's a hardware issue, because I've tried 4 different ICS ROMs (Stock ICS, JJDoctor's, KA20 and AOSP 4.0.4) and I've been able to charge my phone while off in all of them.
Maybe getting your phone to a service center will find the culprit.
Click to expand...
Click to collapse
Is not a hardware issue.
I also had the same problem but now I don´t!!!
I downgrade to GB and flash ICS again and problem is gone.
Why? Don´t know.
Probably is a combination of things.
I never said anything about hardware issue. At least don't remember it.
After flashing back to GB and upgrading to ICS the problem was gone until I removed all apps that don't use directly from system/vendor/app
Now I cannot charge again but hopefully I won't leave my battery to totally die again.
chargamon file nuff said
Sent from my Xperia neo using xda premium
Chargemon, if I'm not mistaken, is replaced when installing cwm. This means I should be facing this problem as well. Let me check...
Sent from my MT15i using XDA
EDIT: I couldn't replicate the problem. The phone started charging normally when off. A few seconds in the light went from green to red, but I think it recalculated the battery from 90% to 89%, hence the switch. Perhaps this only happens when the battery is fully drained?
Hello all. So here is my situation.
Motorola Milestone X2
Last night I successfully rooted the phone and installed CMOD 10 using these directions
http://forum.xda-developers.com/showthread.php?t=2101633
Everything went fine. Charged the phone overnight, went for a jog this morning running both Pandora and c25k app. Absolutely no issues.
So I get to work and the phone just shuts off. Will not power back on or into fastboot. When plugged into USB, green light comes on.
After several minutes it will randomly power back on. Then after using it for a few minutes, it will just shut off again. Powering on and shutting down seems to happen randomly.
Any suggestions? Thanks in advance
doogie87 said:
Hello all. So here is my situation.
Motorola Milestone X2
Last night I successfully rooted the phone and installed CMOD 10 using these directions
http://forum.xda-developers.com/showthread.php?t=2101633
Everything went fine. Charged the phone overnight, went for a jog this morning running both Pandora and c25k app. Absolutely no issues.
So I get to work and the phone just shuts off. Will not power back on or into fastboot. When plugged into USB, green light comes on.
After several minutes it will randomly power back on. Then after using it for a few minutes, it will just shut off again. Powering on and shutting down seems to happen randomly.
Any suggestions? Thanks in advance
Click to expand...
Click to collapse
Quick update. It is draining the battery. The next time it booted up I watched carefully, and the red light in the corner was flashing and it said 5% battery, even though it had a full charge just a couple of hours ago. Something must be draining it badly if it will not even run very long while plugged in. Again, any fix for this would be greatly appreciated.
doogie87 said:
Quick update. It is draining the battery. The next time it booted up I watched carefully, and the red light in the corner was flashing and it said 5% battery, even though it had a full charge just a couple of hours ago. Something must be draining it badly if it will not even run very long while plugged in. Again, any fix for this would be greatly appreciated.
Click to expand...
Click to collapse
SBF back to stock and see if it still does the random power downs. If it still does than I'm sorry to say but its your phone
TheTechnicalBoss said:
SBF back to stock and see if it still does the random power downs. If it still does than I'm sorry to say but its your phone
Click to expand...
Click to collapse
Is there a reason to think that flashing to CMOD 10 actually broke the hardware? I have never had battery issues before. SBFing back I am sure would resolve the issue but then what?
And I am not talking "I used to get 12 hours, now I get 10" I am talking "I used to get 12 hours, now I get 12 minutes."
Even when plugged in, if I use it very much, it will die. Surely this is an issue of the phone incorrectly reporting the battery levels. I ran the battery calibration app (not at 100% charge since I cannot seem to get it that high) and it seemed to have no effect.
When I try to have the OS boot into recovery to try clearing the battery data, I just get an icon that look like the little android guy standing in front of a caution sign.
doogie87 said:
Is there a reason to think that flashing to CMOD 10 actually broke the hardware? I have never had battery issues before. SBFing back I am sure would resolve the issue but then what?
And I am not talking "I used to get 12 hours, now I get 10" I am talking "I used to get 12 hours, now I get 12 minutes."
Even when plugged in, if I use it very much, it will die. Surely this is an issue of the phone incorrectly reporting the battery levels. I ran the battery calibration app (not at 100% charge since I cannot seem to get it that high) and it seemed to have no effect.
When I try to have the OS boot into recovery to try clearing the battery data, I just get an icon that look like the little android guy standing in front of a caution sign.
Click to expand...
Click to collapse
cyanogen 10 has issues on our phone. plain and simple. also check the battery stats and see whats running. i had an issue once with facebook running 99% of the time consuming way too many resources. id sbf and try again from stock. if theres still issues try running cm9 it runs nicely and its my daily driver.
...............................
Lorenzo VonMatterhorn said:
cm9 is a bit better in quite a few aspects. i would try it over cm10. for battery life alone. i have stayed on it the longest now, surpassing eclipse, which used to be my favorite. :good:
---------- Post added at 12:15 AM ---------- Previous post was at 12:13 AM ----------
battery life on cm10 is absolutely horrible. it will never be anything close to stock, and you will be lucky if you can get it to last you a whole day. even when working properly.
Click to expand...
Click to collapse
Not necessarily, I've gone two days with 3g radio on but with minimal use on cm10 it really just depends on the hardware variations. Just like how two phones of the same model over clock differently because of minor flaws and variations durring manufacturing.
Sent from my Nexus 7 using XDA Premium HD app
So I was finally able to get it to charge to 100% and then used the battery calibration app.
I could not tell immediately if that did anything, but it seems to be holding its charge today. Guess we will see how it does over the next couple of days.
Thanks!
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
--yep mine too. I'm thinking it has to do with the heaying problem. Mine crashes and dies when there are many apps running/ wifi on with downloads while watching youtube., etc. another is when I recprd videos at 4k pr 720p for about 8-10 mins. My phone heats up real hard. I'll try resetting it and hopefully this fixes it. ps. Haven't done anything to my z5c yet. no unlocked bootloader, no root.,etc.
Same problem
I had the same problem
Device have charge (50,60,70 or more), show 0% and turn off.
Hardware problem maybe ???
any solution found?
hi,
I know it's been a long time you posted this but I'm currently facing that exact same problem.
Could you find any solution in the end?
Thanks
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
It looks like your battery is just dying. This was a common issue with Nexus 6p and other phones.
Resetting batterystats won't help... it doesen't have anything to do with it
Hi people, nexus 6P owner since 2 years now. I remember when I received the phone I could reach without worries 5 to 6 hours of Screen but then, after nougat and now Oreo, I've never achieved again that numbers.
After rooting my phone, flashing carbon rom and installing elemental X kernel, I played with governor profiles and improved my SOT a little over this year but it was getting worser and worser by every day (2 to 3 hours of screen on time and heavy idle drain). Finally, the real problem came the other day when for the first time my phone shutdown at 29% suddenly after opening the camera.
So I read internet and found in the nexus 6 (not 6P) forums that someone suggested a solution concerning a problem with how the phone meter the battery remaining, suggesting doing a series of steps of charge discharge that I will list here. This, and changing to ABC rom may have done the trick, as now I'm getting much more normal battery life (considering the degradation of 2 years, 2700mah left approximately) of 4, 4 and a half hours (yours will be better) SoT and an idle drain of less than 0,5% per hour, and apparently it didn't shutdown early anymore.
So, give this steps a try if you tried everything like I did and you still having problems with battery drain.
STEPS THAT MAY SOLVE EARLY SHUTDOWN PROBLEM:
- Charge your phone to 100% and use it until it shutdowns (look at what percentage).
- Boot to recovery by pressing power and vol - button, and once in there let it drain the battery until it shutdowns by itself (may take a lot of time so increase brightness to maximum in the recovery menu under settings to consume it faster).
- Now it has really reached 0% and if you try to power it on it won't let you by blinking red in the notification led.
- Plug the charger and leave the phone off until the battery indicator show it's full.
- Unplug it and turn it on, it should show you the battery at less than 100%, like 95%, 90% or even less depending on how bad it was calibrated (mine showed 95%).
- Plug it to the charger without turning it off until reaching 100% and only then unplug it first and then turn it off quickly.
- Plug it one more time (off) until the icon shows it is full and then unplug it and turn it on, now it should say a number closer than before, like 98% or 99% (mine was 99) or it may be 100%. If it shows 100% then you're good to go with the calibration, but if it shows less, repeat the process by letting charge until 100 and then doing the same steps as before until you turn it on without charging and finally it shows 100% battery.
Please report back if this steps worked for you, because for me I think it made the trick.
Now for the battery drain what I did was this steps,
STEPS THAT MAY STOP THE POST-NOUGAT HEAVY BATTERY DRAIN (android OS drain, etc):
-Unlock and Root the phone
- Install ABC rom (check the post here in XDA)
- Flash ElementalX kernel (also here)
- Install the app "ex kernel manager" from the play store
- Enter settings and disable printers (you still can enable them if you have to print something)
- Install Greenify from the play store and select all the apps that don't use notifications.
- Uninstall unnecessary apps that you don't use anymore.
- In the Ex Kernel manager app go to CPU -> governor options and select "load". Choose one of the following recommended profiles: Excalibur V2, Dragon Fly v1, Butterfly or DeadPool. (Or check the guide in XDA about governor profiles).
- Finally activate the run on boot option and reboot to recovery, wipe dalvik and cache and then boot into system.
If you have luck like me, your phone will run very smooth and battery life will be normal to it's current degradation. My phone now last me all day like before and I don't have to charge it twice or three times like I did and best of all, when I don't use it, it almost don't lose battery (2 to 3% overnight).
Also I've never seen again that android system process consuming the same amount as the screen!
I hope this serve someone and maybe save some phones too , I never resigned my 6p because it's a great phone with one of the best cameras out there even today and with great speakers too.
Please let me know if it worked for you! Of course I don't promise it will, but you have nothing to lose anyway! Good luck.
Pd. Sorry for my English , I'm from Argentina
UPDATE: Today my nexus shutdown at 10% but only because I opened on purpose the camera to check if that is the problem, and aparently it is. I've read that when then phone has low power, an app that consumes a lot of battery like the camera may cause shutdown to prevent the phone damaging internal components. So no fix for that at the moment, just don't use the camera with low percentage.
Hi, I don't know if this thread is still on but I'd like to say that I had the same issue. I have a Nexus 6, as you said, and I've installed on it the Resurrection Remix ROM (Neo version). After that, the phone suddenly shut down everytime it reaches 20 or 30 %. I tried two solutions they suggested me;
1) In bootloader menu, go on bootloader logs and press start button for 10 seconds more or less (when you get Google logo and the phone actually boot)
2) Try to reboot the phone in Safe mode and then back in Normal mode
I've also tried to calibrate again the battery (maybe I did it wrong); I followed a guide on it but I can't remember every step of it (if interested I'll try to find it again). Nothing worked, the phone still presents the same issue and I really don't know what to do. I'd like to try this too hoping it works otherwise the last thing I can do, I guess, try to flash again the ROM. Do you have any suggestions? Thanks so much
P.S.
The battery works PERFECTLY; before I flashed the ROM it worked so damn good so I really can't believe that it needs to be replaced, I know that the phone is really old but it always worked fine so it's more logical presume that the problem is with the flashing
Using Stock Nexus 6 Shamu Kernel, with last TWRP and RR OS
Just replace your battery - you might think it's the flashing etc, but at the end of the day my money is on your battery just having called it day, which they can do quite suddenly.
I found that once that early shut down starts it gets worse quick.
It's not that big of deal to change out on these phones anyway and if you do it yourself it's cheap (15 dollars or so). - I've just done it for the second time, not that I was having early shutdowns with my first replacement but after about 18 months life was starting to wane.
Just sharing my experience with my nexus 6p.
Early shutdown problem sure gives us headache. Already tried several methods like calibration, reflashing to factory images, downgrade to minor build or major build, none of them works.
The only solutions that works for me is replace the battery, only cost between $10 to $20 for me (it depend on type battery that you buy, mine is OEM one)
Hello, giving a try to the OP guide regarding early battery shut down. Just a quick question - how long does it take for battery to drain out while in recovery mode? Screens been on for like 2hours now, I see top right screen corner the battery % completely disappear, but recovery still usable. Just wonder, how long it will take for phone to auto shutdown while in recovery mode?
And if this does not work, I'll just replace battery, like @reintakura wrote above.
This device is a disaster. Does it really work?
I tried this the other day. The phone shut off when the low battery came on. I kept powering it up. The first few times it shut off immediately. The next time it turned on and said I had 10% left. Let that 10% run down, it powered off. I kept powering it on... it would boot. I did this maybe 50 times, every time it would boot and then shut down. Then the last time it got "stuck" on the Shutting Down screen. I let it sit like that for a good 10 minutes. It never powered off, it just was stuck on the shutting down screen. I held the power button down to initiate a hard shut down. Plugged it into the charger, device off. Screen said it was 100% a few hours later. Turned on device, device reported 100% used it until it got to 70% and then the low battery light came on and it powered off. Let it charge overnight with device off. Right now it's slowly losing battery, I'm at 76% and it hasn't shut down.
Strange stuff going on.
i was facing the same problem, two days ago i returned to 8.1 abc rom
i'm getting 4h sot and no early shutdown
I can't believe I spent $200 on this **** phone and waited 3 years to get it thinking its the best thing since fried rice, mine started shutting down at 20-30% now it shuts down anywhere from 30-85%!!!!!!!! ahahahahahaha in the end its my fault for buying refurbished, someone obviously sent this crap back already and they did nothing to fix it and conned me into buying it.
Paquinho said:
Please let me know if it worked for you! Of course I don't promise it will, but you have nothing to lose anyway! Good luck.
Click to expand...
Click to collapse
Hi, there. This reply is way late, but I've been away for years and I've only now decided to come back, so I'm necroposting on everything that's relevant to me right now. I hope that's not a serious offense.
I've had my 6P since August 2016. I bought it NOS from Google Fi at a slight discount. It worked like a charm for me for years until around winter 2018/2019, when it started shutting down in the cold. I figured that was understandable. I bike a lot, even in sub-zero temperatures, and I tended to keep my phone in the breast pocket of my windbreaker.
It didn't care too much for that.
So, I started putting it into my backpack and it stopped shutting down.
Then, this summer (2020), the battery went off a cliff. It's been dying anywhere from 80 to 10% since June. Maps and the Camera are the big killers, but the battery will plummet from literally any use.
Yet, it will idle for days if leave it alone.
I recently decided to just wipe the thing back to factory and see if that solved anything. It was quite a feeling to scuttle all of my SMS (I backed them up to my Google account, but it seems like they've gone to some mysterious corner of the Internet from which they cannot be retrieved. Alas). It was kind of a catharsis to throw it all away.
I did back up all my media, however.
The factory reset solved nothing, so I tried the OP's recommendation. I loaded into the bootloader and, instead of waiting on the primary screen, I went into (stock) Recovery (my phone isn't yet rooted) and ran the display test a bunch of times. I alternated between that and selecting "Barcodes" since the all white screen is a bigger drain on the battery than the black and green default.
Eventually, the thing died, but it took hours. This, despite that it would die at the snap of the fingers when in the OS. Strange. I charged the device while off until it said it was full. It came on at 95%. I followed the OP's guide until it turned on at 100.
Yet, it still started draining immediately.
The current culprit is "Mobile Network Standby," which is rich because this phone has no SIM, so why is it even bothering to try and futz with the mobile network? I had been keeping the device on Airplane Mode, but I'd forgotten to turn it back on. I just reactivated that mode, so we'll see if that helps.
However, if I watch a guitar repair video on YouTube (pretty staid, not like gaming or an action movie), the battery just nosedives again.
I don't think that rooting and flashing a new ROM is going to solve this issue.
I bought a replacement battery. I'm just not eager to try and install it. So I may just try root and flash, since it's easier. I guess we'll see what happens.
wedel219 said:
Hi, there. This reply is way late, but I've been away for years and I've only now decided to come back, so I'm necroposting on everything that's relevant to me right now. I hope that's not a serious offense.
I've had my 6P since August 2016. I bought it NOS from Google Fi at a slight discount. It worked like a charm for me for years until around winter 2018/2019, when it started shutting down in the cold. I figured that was understandable. I bike a lot, even in sub-zero temperatures, and I tended to keep my phone in the breast pocket of my windbreaker.
It didn't care too much for that.
So, I started putting it into my backpack and it stopped shutting down.
Then, this summer (2020), the battery went off a cliff. It's been dying anywhere from 80 to 10% since June. Maps and the Camera are the big killers, but the battery will plummet from literally any use.
Yet, it will idle for days if leave it alone.
I recently decided to just wipe the thing back to factory and see if that solved anything. It was quite a feeling to scuttle all of my SMS (I backed them up to my Google account, but it seems like they've gone to some mysterious corner of the Internet from which they cannot be retrieved. Alas). It was kind of a catharsis to throw it all away.
I did back up all my media, however.
The factory reset solved nothing, so I tried the OP's recommendation. I loaded into the bootloader and, instead of waiting on the primary screen, I went into (stock) Recovery (my phone isn't yet rooted) and ran the display test a bunch of times. I alternated between that and selecting "Barcodes" since the all white screen is a bigger drain on the battery than the black and green default.
Eventually, the thing died, but it took hours. This, despite that it would die at the snap of the fingers when in the OS. Strange. I charged the device while off until it said it was full. It came on at 95%. I followed the OP's guide until it turned on at 100.
Yet, it still started draining immediately.
The current culprit is "Mobile Network Standby," which is rich because this phone has no SIM, so why is it even bothering to try and futz with the mobile network? I had been keeping the device on Airplane Mode, but I'd forgotten to turn it back on. I just reactivated that mode, so we'll see if that helps.
However, if I watch a guitar repair video on YouTube (pretty staid, not like gaming or an action movie), the battery just nosedives again.
I don't think that rooting and flashing a new ROM is going to solve this issue.
I bought a replacement battery. I'm just not eager to try and install it. So I may just try root and flash, since it's easier. I guess we'll see what happens.
Click to expand...
Click to collapse
your battery is probably aged, I got the same problem and replacing battery is the only solution that'll work.
Sent from my angler using XDA Labs
Ata Ur Rehman said:
your battery is probably aged, I got the same problem and replacing battery is the only solution that'll work.
Click to expand...
Click to collapse
I reckon that you are correct. However, I am noticing that my phone hasn't crashed since I followed the OPs charging guide. That's something, at least.
Although monstrous battery drain is still a huge problem. I will be swapping the battery.
My question is: root first and flash something custom, just to see what happens? For evidence gathering ... in the name of empiricism.
Or just go ahead with the swap before doing anything else?
wedel219 said:
I reckon that you are correct. However, I am noticing that my phone hasn't crashed since I followed the OPs charging guide. That's something, at least.
Although monstrous battery drain is still a huge problem. I will be swapping the battery.
My question is: root first and flash something custom, just to see what happens? For evidence gathering ... in the name of empiricism.
Or just go ahead with the swap before doing anything else?
Click to expand...
Click to collapse
yeah try root and installing ABC oreo ROM if that doesn't make differ at all then replacing battery is the only solution.
Sent from my angler using XDA Labs