After updating to the new version a day or 2 ago my tablet will now randomly shut down if i leave it in sleep for a while. This is weird because i never had this issue before the update but now i do. Please help because its kinda annoying. Tf201 running 4.0.3 build 9.4.2.13
lamboboy732 said:
After updating to the new version a day or 2 ago my tablet will now randomly shut down if i leave it in sleep for a while. This is weird because i never had this issue before the update but now i do. Please help because its kinda annoying. Tf201 running 4.0.3 build 9.4.2.13
Click to expand...
Click to collapse
I think if you look at other threads you will see you are not alone.
It is still early but there are many that are having issues with this update.
My theory is that the shutting down is from the battery dying due to increased battery drain while it is sleeping. I am hoping to get a better idea tonight when I leave it to sleep.
Same here. But today I had my Prime shut down for no reason after long sleep, took me longer then usual to start it back up again, battery was not dead, still at 60%.
punchup said:
I think if you look at other threads you will see you are not alone.
It is still early but there are many that are having issues with this update.
My theory is that the shutting down is from the battery dying due to increased battery drain while it is sleeping. I am hoping to get a better idea tonight when I leave it to sleep.
Click to expand...
Click to collapse
Not shure that this is the problem because i left mine in sleep it charge overnight, and this morning it was stuck in sleep. I do agree that battery life does seem much more limited than before.
Same Issue Here
Mine is doing the same thing! Never had this issue until the most recent OTA. I even tried a Factory Reset but think that made it worse. I called Asus and they recommended charging it to 100%, turning off Sleep, let it drain all the way down and see if the problem continues. I am guessing this will not work but worth a shot.
fixed
The new .14 update today fixed it.
Installed. 14
Just installed. 14, will see what happens. That was a fast turn around on another OTA!
I have 9.4.2.15-20120221 installed, but I still have the problem.
When I put the tablet to sleep mode, it randomly switch display on (after 3-5 minutes), than sleeps again. After a 30 minutes it suddenly shuted down.
still shutting down
I have the same issue at this point and time. Is there a solution to this problem yet?
biggaboss said:
I have the same issue at this point and time. Is there a solution to this problem yet?
Click to expand...
Click to collapse
Have you updated your Prime to the latest firmware? The latest firmware is 9.4.2.21 for U.S. Prime users.
Have you tried a factory reset? That often helps resolve different software related issues.
I do have the latest firmware installed, the one you are mentioning. But havent tried the factory reset. Will try that know. But what about the applications I bought after I do the factory reset?
So I tried the factory reset and the problem persists. Even if I set Wi-Fi off when tablet is asleep it seems that something related to this is causing the Tablet to shut down!!
It will still happen randomly for no reason. Anyone has any updates on this?
biggaboss said:
So I tried the factory reset and the problem persists. Even if I set Wi-Fi off when tablet is asleep it seems that something related to this is causing the Tablet to shut down!!
It will still happen randomly for no reason. Anyone has any updates on this?
Click to expand...
Click to collapse
SOD's are common on ASUS devices. It's related to their kernel power management and attached devices in some cases. Mine will do an SOD when it's in deep sleep for an extended amount of time, but since it doesn't deep sleep on the charger, I just leave it be when I'm at work on the charger and everything is fine, or I shut it down. Every rom uses the stock kernel and so far the two devs for custom kernels may not have fixed the issue completely either.
Sent from my Transformer Prime TF201 using xda premium
Related
I was psyched to avoid the random reboots with the .13 update for the TF201. However, I have a new issue, which I haven't seen mention of in this forum. Overnight, my Prime won't wake up from sleep. It's not the Sleep of Death, because I've got it plugged in all night. (though I do have that too, when not plugged in).
What happens is this: After charging overnight (or several hours), I press the power button, and it doesn't wake up. That's it. Any number of presses, and nothing happens. I have to hold the power for 10 seconds to get a reboot, at which point it works fine, and shows full battery (it was plugged in all night, recall).
If I put it to sleep for short periods, it wakes up fine. But overnight, no wakey.
Has anyone else seen this, and do you know if this is a known issue that Asus is going to address?
Thanks,
I thought this was the sleep of death issue. I have been having this problem since the .13 update. It takes about 10 minutes or less for me on sleep for it to occur, plugged in or not. I had no problems before the update.
This is the sleep of death issue. Gary said if the testing goes well, there should be an update by next week or sooner. I have the same problem as you, weather plugged or not after more than an hour or so in sleep it will not wake up.
I was really lucky, my prime had no problems (only the GPS one)BUT after the last update ive been having the exact same problem as the OP, i guess in order to fix the problems from some transformers prime they created problems for others
I've been having a sleep of death issue with the latest update, .21.
I pretty much always keep my Prime docked in the keyboard. After long periods in sleep (at least 2 hours or so) the Prime will not wake up. This happens both while on the charger and not.
I haven't tried taking it out of the dock overnight, yet. I guess that'll be my next step.
Anybody else having SoD issues in the .21 update?
stinebd said:
I've been having a sleep of death issue with the latest update, .21.
I pretty much always keep my Prime docked in the keyboard. After long periods in sleep (at least 2 hours or so) the Prime will not wake up. This happens both while on the charger and not.
I haven't tried taking it out of the dock overnight, yet. I guess that'll be my next step.
Anybody else having SoD issues in the .21 update?
Click to expand...
Click to collapse
ehm.., wops, saw this 10 sec after i posted, but yea, me and atleast one more at swedroid got this issue ever sins we updated to .21, :/
I have the same issue since .21. Had it one time now. (Only charged it one time since .21)
It was docked when I charged it.
I hope they fix it in the next update.
Just turned on my phone from overnight and it seems to have no "SoD" you guys are experiencing. I didn't leave it docked though.
Yep. I'm having the damn SoD problem too now. I've had no problems until this! Argh!
I've got SoD after .21 too
For now I've set it to never sleep and wait for next update when the problem fixed.
Me too.
Sent from my Transformer Prime TF201 using Tapatalk
I've been having this since the latest update as well. It happens whether it's on the charger or not. So far I haven't had it out of the dock long enough to know if being docked has anything to do with it, but I do know that removing it from the dock once it happens doesn't clear the issue. However, I did notice that if I go under Settings > ASUS Customized Setting > BATTERY SAVING and uncheck MobileDock Battery saving mode, it doesn't seem to happen. After I did that it didn't happen for about 36 hours, but as soon as I re-checked it to test, it happened the first time it went to sleep. Maybe a coincidence, but prior to that I couldn't make it more than a couple of hours without it happening. Might be worth a try as a work around if you're having this issue.
Last night I docked my Prime for the night to recharge. I left it sitting there opened. After a few seconds I noticed it reboot. "Oh great!" I thought to myself. After it came back up it fell back asleep, I tried to wake it up but it had turned off. I let it do this again to confirm, then I unplugged the charger. Again I left it open, let it fall asleep, and again it turned off. Now, if I close it this will not happen. On .28 I would get an concessional SOD when it was closed and charging. I thought JB had fixed the issue until I discovered the bug last night.
Anyone able to reproduce this?
Scumbag Inc. said:
Last night I docked my Prime for the night to recharge. I left it sitting there opened. After a few seconds I noticed it reboot. "Oh great!" I thought to myself. After it came back up it fell back asleep, I tried to wake it up but it had turned off. I let it do this again to confirm, then I unplugged the charger. Again I left it open, let it fall asleep, and again it turned off. Now, if I close it this will not happen. On .28 I would get an concessional SOD when it was closed and charging. I thought JB had fixed the issue until I discovered the bug last night.
Anyone able to reproduce this?
Click to expand...
Click to collapse
Do you have an SD card in the dock? If you do then it is a known problem that was also on the tf300 and was patched there so should be patched here also soon. If you do have one in there try taking it out and see if it still happens.
flumpster said:
Do you have an SD card in the dock? If you do then it is a known problem that was also on the tf300 and was patched there so should be patched here also soon. If you do have one in there try taking it out and see if it still happens.
Click to expand...
Click to collapse
No SD card in dock.
Scumbag Inc. said:
No SD card in dock.
Click to expand...
Click to collapse
Is this on the official ota? you could try doing a factory reset and see if that fixes it.
flumpster said:
Do you have an SD card in the dock? If you do then it is a known problem that was also on the tf300 and was patched there so should be patched here also soon. If you do have one in there try taking it out and see if it still happens.
Click to expand...
Click to collapse
I have a similiar problem, my prime reboot itself after it went asleep for 15-20 secs and I have SD card inserted in th dock. I tried your suggestion (removed the SD card) and I was lucky, the problem disappeared. Thanks!:laugh:
Scumbag Inc. said:
Last night I docked my Prime for the night to recharge. I left it sitting there opened. After a few seconds I noticed it reboot. "Oh great!" I thought to myself. After it came back up it fell back asleep, I tried to wake it up but it had turned off. I let it do this again to confirm, then I unplugged the charger. Again I left it open, let it fall asleep, and again it turned off. Now, if I close it this will not happen. On .28 I would get an concessional SOD when it was closed and charging. I thought JB had fixed the issue until I discovered the bug last night.
Anyone able to reproduce this?
Click to expand...
Click to collapse
My TF201 when goes into sleep mode WITHOUT dock I cannot wake it up....
I have this issue, and it has been happening since the last ICS update. I'm out of options to try, so I'm sending it to RMA to see what happens, hopefully it gets fixed before my warranty ends. I have tied down my problem at least to the battery meter thinking the battery is dead, then shutting down since the device thinks the battery is dead. Once I rebooot the battery shows normal and the battery stats shows a severe crater in the graph when the battery was thought to be dead.
Prime turns itself off
lamboboy732 said:
I have this issue, and it has been happening since the last ICS update. I'm out of options to try, so I'm sending it to RMA to see what happens, hopefully it gets fixed before my warranty ends. I have tied down my problem at least to the battery meter thinking the battery is dead, then shutting down since the device thinks the battery is dead. Once I rebooot the battery shows normal and the battery stats shows a severe crater in the graph when the battery was thought to be dead.
Click to expand...
Click to collapse
I have had this so I contacted Asus support and sent it in for repair. I will let you know how it goes when I get it back.
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.
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.
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