Related
I can't seem to find any information on this issue.
I charge the battery fully on my external charger and then when I put it in my Inspire it shows red with no battery charge then shuts down. When I power it on with the usb plugged in then the battery shows full and I can unplug it. If I power it off then back on it then shows empty again, even if I quick plug in the usb. I have 3 backup batteries and this happens with 2 of them. All of the batteries worked fine until this started happening. I just rebooted with the usb plugged in and when I check the battery info on my ICS rom it shows 0%, charging (AC), 21s on battery. When I unplugged the usb and refreshed the battery info it now shows 99%, not charging, 3s on battery.
Any help would be greatly appreciated, my son's Inspire does not have this issue with the same batteries that i use so it has to be related to my phone.
This happens on my phone rom, Melcheizedek v2.1 and on one of my Boot Manager roms, Lords ICS v 7.4.
Thanks!
I dont know if this will help.
Try using a different stable Gb rom. If problem persists, power off, pull the battery out, put back the same battery, power on. If it still happens, try cleaning the battery connectors. In the past week or so in either this section or the inspire 4g (either the general or Q&A) someone explained how to clean them.
Edit: does the same problem happen in recovery? My guess is yes, regardless if it's software or a hardware prob.
Sent from a dream.
Teichopsia said:
I dont know if this will help.
Try using a different stable Gb rom. If problem persists, power off, pull the battery out, put back the same battery, power on. If it still happens, try cleaning the battery connectors. In the past week or so in either this section or the inspire 4g (either the general or Q&A) someone explained how to clean them.
Edit: does the same problem happen in recovery? My guess is yes, regardless if it's software or a hardware prob.
Sent from a dream.
Click to expand...
Click to collapse
I will try a GB rom today. I just completely reformatted and re-installed Melchizedek - AOSP ICS booted my phone and battery shows red, no charge. Reboot with usb connected to AC and full charge shows then when i unplug still full charge. When i am in recovery it shows battery --% for a few seconds then it changes to full.
Coffee still hasn't kicked in
In recovery it shows 100%. If you stay in recovery what happens?
Same problem? It discharges and then shuts down?
Can you use the battery cover from your sons cellphone?
Do you remember what you did when you first noticed the problem?
Insight to something that happened to me a few weeks back.
I was running a Gb miui rom, I installed a mod or something the device bootlooped. Erased everything, used my backup, but then the battery would discharge insanely fast. 3-5% per minute. From 80% it went down to 65%, rebooted, then it would show 76%. Wipped everything, installed a different stable rom, no apps whatsoever, same problem. I went into recovery, same issue in recovery, erased, (this part I'm a bit foggy) I believe the same thing happened in recovery with a formatted system.
Can't remember if I installed another rom or just went back to my backup.
Powered off the cell, swapped batteries with another phone, the issue was gone.
My assumption is that by pulling out the battery it solved the problem.
In your case, you already pulled out and tried several batteries. But they work in your sons cell. However, with several batteries it is unlickly (the spelling for that just seems wrong for some reason) to be a battery (just ranting to see where my mind goes).
Still waiting to know what happens in recovery.
If it happens with different roms, Im assuming you full wiped. Especially if you are running one from the collective and lord. You probably know more than I do
Try using a different battery cover if you can, and also try booting your cell without the sd card.
Try them seperately to see if either one works.
Hope something I said works, or at least gives you ideas to try something else.
Edit: I just re-read your initial post. It happens with two out of your three batteries. That's a tough one.
Whats the difference between the batteries? Does your sons battery work on your cell?
You can disregard cleaning the connectors - probably.
Or clean the connectors on the bats and the cover. Or try your sons bat connector with those batteries.
Could you re-phrase your initial post along with everything that has happened and what you have tried?
Sent from a dream.
Teichopsia said:
Coffee still hasn't kicked in
In recovery it shows 100%. If you stay in recovery what happens?
Same problem? It discharges and then shuts down?
Can you use the battery cover from your sons cellphone?
Do you remember what you did when you first noticed the problem?
Insight to something that happened to me a few weeks back.
I was running a Gb miui rom, I installed a mod or something the device bootlooped. Erased everything, used my backup, but then the battery would discharge insanely fast. 3-5% per minute. From 80% it went down to 65%, rebooted, then it would show 76%. Wipped everything, installed a different stable rom, no apps whatsoever, same problem. I went into recovery, same issue in recovery, erased, (this part I'm a bit foggy) I believe the same thing happened in recovery with a formatted system.
Can't remember if I installed another rom or just went back to my backup.
Powered off the cell, swapped batteries with another phone, the issue was gone.
My assumption is that by pulling out the battery it solved the problem.
In your case, you already pulled out and tried several batteries. But they work in your sons cell. However, with several batteries it is unlickly (the spelling for that just seems wrong for some reason) to be a battery (just ranting to see where my mind goes).
Still waiting to know what happens in recovery.
If it happens with different roms, Im assuming you full wiped. Especially if you are running one from the collective and lord. You probably know more than I do
Try using a different battery cover if you can, and also try booting your cell without the sd card.
Try them seperately to see if either one works.
Hope something I said works, or at least gives you ideas to try something else.
Edit: I just re-read your initial post. It happens with two out of your three batteries. That's a tough one.
Whats the difference between the batteries? Does your sons battery work on your cell?
You can disregard cleaning the connectors - probably.
Or clean the connectors on the bats and the cover. Or try your sons bat connector with those batteries.
Could you re-phrase your initial post along with everything that has happened and what you have tried?
Sent from a dream.
Click to expand...
Click to collapse
When I boot into recovery it initially shows no charge for maybe 20 - 30 seconds and then shows full (or whatever level the battery really is). The battery level stays normal then and works perfectly fine all the while I am in recovery.
I just rebooted with the battery I was using all day, it was plugged into a usb ac at work until about 3.5 hours ago, and it rebooted with a normal battery level, I rebooted again and it was normal again. I booted this same battery in the morning and it showed no charge but now it works fine. I then rebooted with a second battery and again it booted fine with full charge. I put in a third battery, this was the one it first happened on, and it booted with no charge. I put back in the battery I had in all day and it booted with normal charge again. I checked the bad battery and the good battery and both have about 4.2 volts.
When it happened the first time it was only with 1 battery, that was about a week ago. I just got 2 new batteries in the mail and one worked fine and the second booted up showing no charge like the other one. That was 2 days ago, since then every battery seemed to do it until now, I just checked 5 batteries and only the first bad one and the one new one that was bad don't work, weird.
It seems like the bad battery screwed up something in my phone but it's hard to believe that whatever it was would survive a system format. Now it seems to be working fine...I don't like things that fix themselves...
Well, if you have the time let's try troubleshooting the issue with only the bad batteries (as long as if you believe it to be software related only).
Keep in mind that I'm trying to help figure this out, and to keep bumping this thread until someone more knowledgeable joins in.
If its software, remove the sd card, format everything. Power off, remove the battery, while the battery is out press and hold the power button (hoping the cell works something like a pc) for 30s. Then install - I don't know - any rom? Load a few basic apps you use/need. See what happens with the bad battery.
You did say the bad battery does work in another cell?
Sent from a dream.
Teichopsia said:
Well, if you have the time let's try troubleshooting the issue with only the bad batteries (as long as if you believe it to be software related only).
Keep in mind that I'm trying to help figure this out, and to keep bumping this thread until someone more knowledgeable joins in.
If its software, remove the sd card, format everything. Power off, remove the battery, while the battery is out press and hold the power button (hoping the cell works something like a pc) for 30s. Then install - I don't know - any rom? Load a few basic apps you use/need. See what happens with the bad battery.
You did say the bad battery does work in another cell?
Sent from a dream.
Click to expand...
Click to collapse
I don't believe it's software related, I reformatted and re-installed the rom I was using and still had the issue. I have been using the same rom for a while with no issues. I'll check the 'bad' batteries on my son's phone tomorrow.
Edit: Booted normal this morning again, I think I can close this issue for now. I am a bit uncomfortable with not finding the root cause but at least it ended in my favor. Thanks for your input!
You are welcome. My next step was going to be to link your issue in another thread. Good luck.
Sent from a dream.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Try full wipe and reinstall ROM, if doesn't work flash another ROM. If doesn't work again, maybe it's problem whith battery controller, you would have to go to service centre
DHD
I had a similiar problem and it happened after i started playing with ICS DHD Roms. I downloaded a stock WWE sense 2 rom and flashed that. I then flashes the latest Stock WWE 2.5 Sense rom and all is still ok. Dunno if the stock flashing (through exe from PC) it was unrooted though. Fixed it but its fine now. So maybe try that.
Perhaps this may help.
http://forum.xda-developers.com/showthread.php?p=26010421
Sent from my Inspire 4G using XDA
Thanks for sharing my post on the Inspire forums, Teichopsia.
I'm convinced that there's something in the non-sense ROMS that doesn't get the battery charge % correctly immediately after booting. I'm having the same symptoms as the original poster is having. Two of my batteries are after market and two are HTC. The generic ones have the problem of registering 0% on reboot after swapping the batteries in. If you have them on the charger they work fine and show 100% after about 30 seconds. If you reboot with the same battery it's fine until you change to a different one. The latest ICS Rom I'm using has the problem with any reboot, even if the same battery is in. If I'm using real HTC batteries this problem doesn't manifest itself on Cyanogenmod or AOSP ROMs.
EDIT: I should clarify that the after market batteries fail on any reboot without the charger with the latest ICS ROM I'm trying, but the HTC batteries are fine.
I've had success with booting into recovery mode and wiping battery stats. This is not a permanent fix but is useful when you don't have access to a charger and need to swap batteries.
The full procedure is this: with phone off hold power and vol down, select recovery, advanced, wipe battery stats, yes, go back, reboot system now.
Bad battery I think. Ik had the same problem with a brand new, original battery.
Charged it fully with external charger, booted phone with it but showed 0% juice....
I had to boot with the charger plugged in, and then after booting it went to 100%
Send the battery back because this was not normal, recieved a new one and didn't have the problem.
btw I was on IceColdSandwich rom...
Im running ICS 4.0.4 aospX 1.0.0-MR1 on my HTC Inspire 4g with a Anker® 1600mAh Li-ion Battery For HTC Desire HD, Inspire 4G - White and had this problem initially.
The only way my phone would boot up was if it was plugged in, otherwise it would show a dead battery warning when the homescreen loaded, and then it would shutdown. If I booted it while plugged in, then disconnected the cable, then it would run off the battery just fine.
What I did to fix it was to shutdown the phone, take off the battery cover, removed the battery ( the Anker one), blew into the compartment to make sure there was nothing interfering with the connectors, wiped the battery's connectors with my finger, and then i replaced the Anker battery, pushed hard on it to make sure the connection was good, and booted the phone.
To my surprise, this actually seemed to fix the problem. Whatsmore, after I put the battery cover back in place, the phone continued to boot with no issue, meaning I did not have to push on the battery to make sure the nodes were connecting. I even shook the phone in my hand to see if this would loosen the battery connection, but it still booted fine.
I then took out the battery and replaced it to make sure it would still boot, and it did. Hope my solution works for you! Cheers!
CM is having issues on the One X with reported battery levels as well.
Sent from my HTC One X using xda app-developers app
After the latest update my M9 charges very slow. It takes 6 hours or even more than that, even with the Rapid Charger 2.0
If I reboot my device before before I charge it, then it charges normally, in under 2 hours.
Any solutions?
I am trying to fing out where the problem is, and I suspect GSAM Battery Monitor Pro and maybe an app called Screen Adjuster that might somehow interfere.
I have an unbranded device and it runs the official firmware.
Is anybody else having the same issue?
Have you tried wiping the cache and recalibrating the battery by holding both volume buttons and power button at the same time for over a minute?
No, I haven't. Are there any other issues I should expect if I recalibrate the battery?
Have the same issue .. S-OFF, ARHD 8.1, Firmware 1.40.401.8
No solution yet :/
So it must be the new firmware. This is really bad. I have cleared the cache but I don't really see the point of recalibration. If I restart my device before charging, it always charges after the reboot normally...
I disabled GSAM yesterday and the screen adjuster app, but the problem remains. I wonder, is there anybody out there running the new firmware without this issue?
Same issue here. Stock non-rooted ROM, stock firmware, S-Off, unlocked BL.
Had also the same issue with 1.40.401.5, thought it would be fixed in the official update (1.40.401.8). It appears it's not... Bad news when an update supposed to solve issues brings new ones...
With 1.40,my charging is way quicker with a quick charge 2.0 adapter. GSam battery monitor reports higher ampere and a battery change ~80%/h now (from empty to 85% as usual). Before this, battery change stalled quickly but now it's stable.
Did you factory reset your device after the update?
Same problem here.
No factory reset after the update. Should I? Or is there another way?
I did a factory reset when I first noticed problem with slow charging. At first it seemed to work and it charged normal speed but now its back to slow.
My M9 will only charge when i turn it off, plug it in the ac. If its on, even though the indicator says its charging, it doesnt, help.
The update was supposed to improve (quick) charging... Instead it made it worse ;(
I'm curious if there is anyone who does not have this problem...
Sent from my HTC One M9 using Tapatalk
I charge my phone from 17 to 100% in 2hours with .8 firmware.
kire.htc said:
I charge my phone from 17 to 100% in 2hours with .8 firmware.
Click to expand...
Click to collapse
With the original charger?
Mine charges a bit faster with the quick charger, but only after a full reboot. And only once, after disconnecting the charger it reverts back to verrry slow charging when connected again.
I've the same issue. All stock, latest firmware.
Unless i reboot the device, it takes 8 hours to charge. If i reboot it before plug in, it takes about 2 hours.
Something is wrong were...
Same problem here but it is intermittent. I plugged my phone in earlier and it charged 10% in 1.5h on a 2A charger. So annoying!!!!
This is a big issue for me since I cannot rely on my M9 to get me through the day without having a charger with me. I am going to stop using my M9 till the problem gets solved somehow. Sorry HTC but this is a big issue for me and despite the fact that I love HTC products, I cannot ignore this issue. Back to my iPhone...
I agree on the Factory Reset, I do it every time I take a OTA update. It's jus my practices as it solved issues in the past and I kinda stick to it...
Sent from my HTC One M9 using Tapatalk
no its a real bug, regardless of the charger, when it appears only a reboot solves it
anyway the 5.1 / 2.x update is close but yea bug like that will cause serious hurt
This past week, I purchased a 2014 Note 10.1 off Craigslist. I did check it out before buying it, and the device is in pristine condition, including the screen. It booted fine, and I went partway through the setup (the guy had factory reset it) before closing the deal. It is the wifi-only model, 3G RAM, 8-core Exynos version. It's white if that matters.
Anyways, a while later when playing with it some more, completing setup, etc, it just died on me. I wasn't home, and didn't have a place to charge it until I got home, but just figured that despite the device having said the battery was 99% charged, the guy keeping it unused for a long time might have thrown off the battery calibration. My understanding is that a Li-ion battery has one or more cells, plus circuitry that protects against overcharging and undervoltage conditions, as well as tracking the current charge state. With lengthy non-usage, the circuitry's idea of the current charge can get out of sync with reality, so I figured a few charge-discharge cycles would get it back in shape.
However, the situation after I got home turned out to be a little more complex. If I plug in the device to a power source with enough current (like the charger it came with, or my 2.1A USB outlet by my bed), it will run just fine while plugged in. However, upon unplugging, it would die quickly. Naturally, I assumed the battery was probably shot, so resigned myself to spending $50 on one. This is where it started to get a little weird. It seemed that when I booted into either fastboot or Odin mode, it would stay on much longer than normal, while unplugged. I'm talking hours, rather than between several seconds and several minutes while booted into the OS proper.
This lead me to believe that perhaps it wasn't my battery itself, but rather a glitch in the OS that was causing it to shut down. When I say shut down, I mean an immediate full-off state, not a nice shutdown or one preceded by low battery warnings. It just clicks off like a light that's been turned off. However, trying several different firmwares, including a couple custom ones, has not yielded any improvement. The issue remains.
The device was stock 5.1.1 when I bought it. I tried flashing KitKat (various images downloaded from SamMobile), but for some reason, it would still say it was running 5.1.1. I tried xKat, as in this thread. That results in 4.4.2 with the associated customizations, but the shutdown issue remains. I tried CyanogenMod 13, as instructed here. It works fine, notwithstanding the same issue. In between the stock firmwares (pushed to the device with Odin) and the custom ones, I would do a full wipe through TWRP.
I've popped the back off, disconnected the battery, waited a bit, and reconnected it.
Now my question: does anyone have any idea what's going on? If it's a dying battery, then why does the device say it's got a nearly full charge, and why no low battery warnings? Why would Odin mode or recovery (TWRP now) seem to keep the device powered up so much longer? Sure, they draw less power, but hundreds of times less power? I doubt it. If it's some hardware issue with the chipset/motherboard/etc, then why does it only manifest when running on battery, or a low-current USB connection? If it's an issue with Android itself, then why does nobody else seem to have this issue (googling revealed nothing that matched my symptoms), and why did several different versions exhibit the exact same problem?
I really don't want to spend money on a new battery and wait a few weeks for shipping if there's something else I'm missing that could get my device functional for free and a lot faster.
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off. I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again. For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing. For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Sent from my SM-P600 using XDA Premium HD app
Thanks for your reply.
siralsmooth said:
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off.
Click to expand...
Click to collapse
That's a bit different from my issue. Even when the device reports full charge, if I unplug it, it usually dies within seconds, and always within 2-3 minutes.
siralsmooth said:
I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again.
Click to expand...
Click to collapse
I don't think that's going to make a difference for me. From what I was reading, all it does is delete the batterystats.bin file (hence the root requirement), which doesn't have anything to do with calibration for most devices. It just contains the stats for how much battery drain various things have caused, during this 'running on battery power' session. It's also reset every time the device is charged. Read here for more info.
Furthermore, even if this were not the case, I'd conclude that wiping the system partition (indeed, all partitions except recovery) would have cleared this data.
Still, that said, it's conceivable (though exceedingly unlikely) that some of these calibration apps might do something else, such as talk to the battery circuitry at a low level. Since I've got nothing to lose, I will probably give a few of them a shot. Do you happen to know which one it was that you tried?
siralsmooth said:
For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing.
Click to expand...
Click to collapse
In my case, the values seemed to track pretty closely, and with numerous freshly-flashed versions exhibiting the same issue, I'm pretty sure at this point it's not a software glitch. I've resigned myself to ordering a new battery. I just wish I was certain that it would fix the issue.
siralsmooth said:
For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Click to expand...
Click to collapse
My understanding is that the bootloader doesn't change with flashing. I might be wrong though; is there a way to check the version?
Just a heads up. I ordered a new battery, which arrived yesterday. It seems to have completely solved the issues I was having.
My guess is that Android itself monitors the battery more diligently, and takes a more conservative approach to preserving battery life by shutting down when the voltage drops too low, while recovery mode would just let it run down completely flat (not good for Li-ion cells).
It's a moot point now, because it all seems good.
Hi all,
I have been running my Z1 Compact on 4.4.4 for the longest time, mainly due to sound issues after updating to Lollipop.
Recently, the battery has been dropping randomly from 60 odd percent to 3 or 4 and then shutting down all within a few seconds. The last time it did this, I tried charging it when I got home but the charging light would not stay on, thus it was not charging. All typical signs of battery failure due to age.
Having already replaced the battery successfully on my Z1, I bought a replacement original Sony battery and replaced it. The problem persisted. On first boot, the phone got to the blue waves then black screen, and power off. Charging screen just showed the battery at about 40%.
I risked it and flashed the latest software with Flashtool, having done a complete wipe. The result of this proved no better, but I did get a different message on the charging screen, a message saying the phone had shut down due to overheating. Picture is attached.
The phone is in no way overheating and I've even booted it while sat on a shelf in the fridge to help dissipate any heat generated but with no luck.
So, the old battery maybe did overheat and caused the phone to shut down, I'll accept that as a probability. It may have even damaged something, but I don't think that's likely.
After changing the battery, I would have expected the problem to resolve itself, but it seems like some kind of hardware 'flag' has been raised that is now not allowing the phone to boot in case it overheats again.
Does anyone know of any way to resolve this, reset the 'flag' per se, other than going to Sony? The phone is definitely out of warranty due to its age, never mind me taking the back off lol
It is a shame because it has been a great phone over the years, and I would like to fix it if possible, even if to give it to one of the grandkids. I have my Z3 still (which I won't part with for anything) and I have an XZ too and both are great phones. I would just like to save the XZ1c if I can.
The phone is not, and has never been modified in any way, no rooting, no bootloader unlocking. Only stock roms have ever been flashed, and then only once or twice, to put it back on 4.4.4.
I have tried reflashing just the kernel, or just the system too, to no avail.
In desperation I even left it in the fridge for a few hours in case the temperature sensor was on the fritz, but that did nothing at all.
I just feel like there's nothing actually wrong with the phone, apart from this trigger that won't reset.
Any help greatly appreciated of course.
Thanks,
Mick
Maybe theres lot of consideration:
1. Rom Bugs
2. The Kernel not supported well
3. Battery Issues (But you already change it right)
There are two temperature sensors afaikin our phone. One in the SOC and another one in the battery (hence three pins).
The battery is probably the one giving the high temp report. Try yet another battery.
A bad battery normally heats up very fast inside and the battery temp sensor stops the battery from charging and/or working to protect the phone and the battery.
I changed my battery before when it had symptoms like yours 100-90-0 drop and after replacing with a battery from eBay it was OK. I gave it a full charge then complete discharge and then complete charge to full cycle the battery once and let the phone Guage its full capacity. one year later now my battery is acting funny again (not charging past 30%) and getting so hot when charging it triggers overheat control service in Android.
Any luck?
Apologies for the necro. But did you ever fix this issue, having the same problem
Karter Ires said:
Apologies for the necro. But did you ever fix this issue, having the same problem
Click to expand...
Click to collapse
No, I never did figure it out. I've been loathe to spend more money on another battery when I've got other much newer phones. I really have no idea why it would not reset once the battery was replaced, maybe it's the replacement battery.
Have you tried changing the battery?
I've tried flashing different stock roms, Kit Kat, Lollipop, and it doesn't help.
Short of going to Sony, I'm not sure what else to do.
Okay, now that I'm in the right forum, I have an AT&T M9 converted to Developer edition, S-off, TWRP 3.0.2-0, Firmware version 3.35.617.12 listed in download mode, running ViperoneM9 6.1.0. As the title suggests, if I'm anywhere from 30-60% battery, it will just turn off, and I can't turn it back on without it dying again on boot. If I plug it in, it lists whatever percentage battery it died at, usually 30-60%. I don't want this to turn me away from all of the benefits of root, but it's killing me. I'm not sure where to go from here, and I almost just want to RUU the thing and go back to stock. Someone help me figure out what this is, please.
Another fun bit, any of my color scheme customizations get reset, as well as my font, custom button maps, and general tweaks.
I've experienced this too on my phone, but that was after I replaced the battery with a third party battery. This exact thing happened to me but rather around 80-85%. After reboot it still showed that percentage. After reinstalling the original battery everything worked again. I have returned the other battery to the seller for a possible refund.
A similar thing actually used to happen on my old HTC One (M7) to, but then it was rather at around 50%.
manlavi95 said:
Okay, now that I'm in the right forum, I have an AT&T M9 converted to Developer edition, S-off, TWRP 3.0.2-0, Firmware version 3.35.617.12 listed in download mode, running ViperoneM9 6.1.0. As the title suggests, if I'm anywhere from 30-60% battery, it will just turn off, and I can't turn it back on without it dying again on boot. If I plug it in, it lists whatever percentage battery it died at, usually 30-60%. I don't want this to turn me away from all of the benefits of root, but it's killing me. I'm not sure where to go from here, and I almost just want to RUU the thing and go back to stock. Someone help me figure out what this is, please.
Another fun bit, any of my color scheme customizations get reset, as well as my font, custom button maps, and general tweaks.
Click to expand...
Click to collapse
I'm on the original battery still, but I have had this phone since May 2015. I was thinking that maybe my battery's life was shortened when I flashed viper in the past and got wake locked and 90% system usage on the battery for a couple of days. Is that a thing?
This would be typical behaviour for a dying battery. I've had a similar issue, but it had nothing to do with the ROM in my case. My HTC One X had it, there it was the battery. My girlfriends iPhone 5s as well, again it was the battery.
Does it occur more quickly if you use more power? That would be quite typical of a dying battery. What then happens is that the voltage drops slightly because you apply a load. The voltage then isn't sufficient anymore and the phone concludes its battery is too low and it has to turn off. Maybe try and see what happens if you draw maximum power at 60%. If it then immediately turns off, I would be confident it's the battery.
This is so obvious and I didn't even realize. I going to try it, sorry for the late reply