[Q] Random reboots at about 30% battery life - Galaxy Note II Q&A, Help & Troubleshooting

Hi there,
I've got a little problem with my phone recently. It keeps freezing/shutting down every time the battery life hits about 30%. The button light starts to flicker, music begins to stutter and then - a few seconds later - my device turns of or just freezes leaving the screen turned on. When I reboot my phone the battery life drops to 0% or remains at about 30%, that differs from time to time.
I tried everything, installing 4.4.4 and 5.0.2 CM, with and without apps installed, with and without gapps. All constellations result in the same behaviour. I just can't figure out what the problem is. I pulled two logcats (4.4.4 and 5.0.3) and attached them to this post. I begin to believe that it is a hardware related (battery) problem, but perhaps somebody can find something in the logcats, that I've overseen.
Thank you very much in advance!

Related

[Q] Stock Battery Usage app not showing drain..

Searched for this and didn't find it in the forum. My phone is not rooted.
I've had this phone maybe a week after launch and this issue has just started happening in the last 4 days or so. It typically seems to happen after charging and unplugging the phone. The stock battery usage app, Settings--> Applications--> Battery usage, shows no battery drain at all while showing the phone as Awake the whole time and Screen on the whole time.
The reality is that the phone was just sitting on the kitchen counter with the screen off and I hadn't touched it the entire time. Rebooting only sometimes seems to make it snap back to reality, there are times when I'll reboot or pull the battery and nothing happens, it just continues to give a false readings.
Anyone else experiencing/experienced this?

[Q] battery dead at 15% and green led at 90%

hello mates,
I have rooted my htc desire and installed redux 1.2 ROM(gingerbread) with a ManU kernel...When charging the LED changes to green precisely at 90% (which i dont have a major problem with as it will go all the way to 100% if kept on charge)..also the phone will die at 10-15% of battery...I have read other threads regarding this same problem and am wondering if its a calibration error or is the problem with gingerbread ROMs as someone pointed out...Otherwise the battery is fine...and gives me a decent 1-2 days of use with moderate usage...its jus the problem abt the 15% n going dead which is a lil troublesome as the fone has died on me many a time for that last important msg, call or IM...any help appreciated...cheers..
That's not really a problem. The green LED at 90% is normal for android (try to fix it with battery calibration, helps sometimes) and the shutdown at 10-15% is also normal. Just take the last one how it is, all batteries are different. Some phones shut down at 5%, others at 20%.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
noticed this on ICS dev rom too but also had it on my old G1
wipe cache,battery stats try diffrent kernel
stupidflanders1 said:
hello mates,
I have rooted my htc desire and installed redux 1.2 ROM(gingerbread) with a ManU kernel...When charging the LED changes to green precisely at 90% (which i dont have a major problem with as it will go all the way to 100% if kept on charge)..also the phone will die at 10-15% of battery...I have read other threads regarding this same problem and am wondering if its a calibration error or is the problem with gingerbread ROMs as someone pointed out...Otherwise the battery is fine...and gives me a decent 1-2 days of use with moderate usage...its jus the problem abt the 15% n going dead which is a lil troublesome as the fone has died on me many a time for that last important msg, call or IM...any help appreciated...cheers..
Click to expand...
Click to collapse
You should try calibrating your battery for the 10-15% dying problem.
And as for the 90% LED changing to green, all AOSP ROMs do that, so no worries there
What worked for me was charging it while the phone is on, when the LED turns green, power it off and charge it again till it turns green.
Repeat this twice and then reboot.
galdel said:
What worked for me was charging it while the phone is on, when the LED turns green, power it off and charge it again till it turns green.
Repeat this twice and then reboot.
Click to expand...
Click to collapse
This is to calibrate the battery. Some people find it useful to run a program called BatteryRepair, in my case I noticed a clear improvement on battery performance.
To avoid calibration problems with the battery, remember to unplug your phone when you flash a new rom!
Tapatalking
Turning off at 15% of battery with Supernova 2.4 ROM
I am using Supernova Xtreme 2.4.0.0 ROM, and my phone turns off at 15% of battery. My battery is freshly calibrated and this problem did not occured with LeeDroid ROM and with the stock ROM neither. On the Droidzon page I have found some info in FAQ section, which says the following:
Question: Recently I let my battery go completely flat. When I switched my handset back on I was bombarded with forced close messages.
This has been reported once previously, but could not be reproduced under Sibere’s extensive testing under similiar conditions. For the same reason, unfortunately, we dont have a solution too. The OS is supposed to prevent a complete drain, and to shutdown at 15% and then 5%. The shutdown at 5% is supposed to be forced too. If it shutdowns, then this issue shouldnt occur. Data2SD depends on a normal shutdown to prevent data corruption. Once Data corruption has occured due to untidy shutdown, data is not unmounted cleanly, and then the issue can recur on every subsequent boot, which would require a complete reinstall.​
So it seems to be normal, connected to the ROM, and NOT connected to my battery (it is calibrated).
My question is (which goes to Droidzone firstly), what should I do, if I want to use this ROM, but I do not want it to turn off at 15% rather I want it to turn off my phone at 2%?
Sofokles_ said:
I am using Supernova Xtreme 2.4.0.0 ROM, and my phone turns off at 15% of battery. My battery is freshly calibrated and this problem did not occured with LeeDroid ROM and with the stock ROM neither. On the Droidzon page I have found some info in FAQ section, which says the following:
Question: Recently I let my battery go completely flat. When I switched my handset back on I was bombarded with forced close messages.
This has been reported once previously, but could not be reproduced under Sibere’s extensive testing under similiar conditions. For the same reason, unfortunately, we dont have a solution too. The OS is supposed to prevent a complete drain, and to shutdown at 15% and then 5%. The shutdown at 5% is supposed to be forced too. If it shutdowns, then this issue shouldnt occur. Data2SD depends on a normal shutdown to prevent data corruption. Once Data corruption has occured due to untidy shutdown, data is not unmounted cleanly, and then the issue can recur on every subsequent boot, which would require a complete reinstall.​
So it seems to be normal, connected to the ROM, and NOT connected to my battery (it is calibrated).
My question is (which goes to Droidzone firstly), what should I do, if I want to use this ROM, but I do not want it to turn off at 15% rather I want it to turn off my phone at 2%?
Click to expand...
Click to collapse
I'm afraid this is not similiar to the issue in the FAQ. Your issue is that phone shutsdown at a level earlier than expected. The Data corruption issue is because the phone did not shutdown at the expected level and went down to as far as zero level of the battery, which resulted therefore in an untidy shutdown with no sync or clean unmount of data2sd partition, and hence ext4 errors. The 15% shutdown level is a normal soft shutdown prompt (which was missing in case of the issue reported by the user). The shutdown at 2% is the normal forced shutdown by OS.
As I said previously, your issue seems to be due to a poorly calibrated or defective battery, and it would help to do a calibration as per guides on XDA. If this fails, have the battery checked. To reiterate, it's not a rom issue and not something like a bug in the rom.
Thanks. So normally the phone with Supernova ROM should turn off at 15%. After that I have to be able to turn it on again, and use it till it drains to 2%, and shuts down finally.
For me it just shuts down at 15% and then when I switch it on and it boots up, the battery level shows 0% and it shuts down immediately.
Sofokles_ said:
Thanks. So normally the phone with Supernova ROM should turn off at 15%. After that I have to be able to turn it on again, and use it till it drains to 2%, and shuts down finally.
For me it just shuts down at 15% and then when I switch it on and it boots up, the battery level shows 0% and it shuts down immediately.
Click to expand...
Click to collapse
No, a normal rom would popup a warning at 15%, asking the user to shutdown. If he doesnt, it would continue, and then give additional warnings, and finally do a forced shutdown at 2%. If it shutsdown before that forcibly, it's something peculiar to your hardware.
Ooops, so Supernova ROM should behave exactly the same way as a stock ROM (or any other) does in terms of warnings and shutdows.
I might try to do something with battery calibration. Should I do it before or after flashing Supernova? Or it does not matter? If I flash a new ROM, does it delete battery logs or it stays as it was before flashing?
Sofokles_ said:
Ooops, so Supernova ROM should behave exactly the same way as a stock ROM (or any other) does in terms of warnings and shutdows.
I might try to do something with battery calibration. Should I do it before or after flashing Supernova? Or it does not matter? If I flash a new ROM, does it delete battery logs or it stays as it was before flashing?
Click to expand...
Click to collapse
Correct. For all intents and purposes, Supernova is exactly like a Stock rom. Difference is only in where internal apps are stored.
The so called calibration is just a file at /data, which means it will be wiped when you do a wipe for rom install.
[Update] Problem solved. I flashed UOT battery MOD after first boot (not before). Now it works perfectly.
A flashed the ROM again, did the battery calibration several times, but the phone keeps turning off at 15%. I checked battery voltages at different levels of battery, and I experienced that at 16% it is 3635 mV, then it turns off below 15%. When I turn it on, battery level is 0% and the voltage is 3390 mV, and when it is charged up to 1% it is 3723 mV, which is higher than it was at 16%. What is wrong here? Actually I use UOT kitchen battery MOD, can this confuse the system somehow?

[Q] Battery Drain Issue

Hi all,
I have been using ARHD ROM for a while now, version 5 for a few weeks and noticed the issue on there first and it still occurs after updating to 6.1 over the w/e. I was not aware of the issue before I went to ARHD but was not using/rebooting stock often enough to find out.
I don't think this is ROM related but am not really sure how to go about working out exactly what is causing it.
Normal working is excellent and battery drain is very low - seems to be about 2mA when idle with no WiFi or Data connections.
After a random amount of time - could be 3/4 days or less than 1 day the battery drain increases noticeably. For me it means that after an average days use the battery would be down to 20% or less rather than 40-50%.
I downloaded "better battery stats" to try and identify if possible what was causing it and it seems to be that the "LocationManagerService" is getting stuck with a "Partial Wake Lock". This prevents the phone from going into "Deep Sleep" so I can see on CPU Spy that the 51Mhz time starts increasing considerably and the Deep Sleep stops increasing completely.
A reboot solves the problem for another random amount of time.
After reboot under normal operation the "LocationManagerService" does not seem to register at all for several hours and when it does operate normally it stays towards the bottom of the "better battery stats" list with about 1s of use, even after a couple of days. When it gets stuck in partial wakelock it moves to the top of the list and refreshing shows constant updates indicating that it is maintaining a partial wakelock.
I have tried searching on Google but cannot see any mention of anyone experiencing a similar problem and as I am sure many applications use the "LocationManagerService" I am at a loss as to how I try and work out whether this is a bug in the service or an application that is causing it.
Apart from rebooting every time I notice this I am not sure how to troubleshoot any further, so was hoping one of you knowledgable guys/devs could perhaps make some suggestions as to how I can identify exactly what is causing this?
I would also be interested to find out if anyone else on any other ROM can see the same issue?
Thanks

Very strange restart, please check it UPDATED

Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
yap, I have two gnexs both have had this problem.
I can get a screenshot with vol-down + power
but the screen is totally black.
Yeah I've had this screen of death issue too. I've been trying forever to diagnose what is causing the problem. It happens on any kernel including stock. I factory reset, flashed stock images, everything.
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
i not have restaert using apk franco updater and set :good:
The sudden battery drop is normal when you pull out the battery. Basically, the phone loses it's calibration on the battery capacity. And that " auto charge" is your phone slowly trying to get a better estimate of your phone battery capacity.
Sent from my Galaxy Nexus using Tapatalk 2
I believe that SODs are a common problem faced by many on 4.2 i personally havn't faced it yet =] running arhd with ak kernel
I was able to reproduce this using Velis Auto Brightness https://play.google.com/store/apps/...SwxLDEsImNvbS52ZWxpcy5hdXRvLmJyaWdodG5lc3MiXQ
After messing with the brightness it wents black screen.
I'm sure this has to do with the autobrigtness!
Best regards
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
klobkelosh said:
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
Click to expand...
Click to collapse
I think you just helped me pin it on animation off. I have had the black screen happen to me 3 times in the 3 days that I disabled animations (stock rooted ROM, developer options). I kept trying to find an app that caused it but the animation off matches the start of my problem.
EDIT: Well, animation off isn't the cause since I just had another black screen.
simms22 said:
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
Click to expand...
Click to collapse
Totally agree with you!happened to me many times too,especially when crashing after tweaking\benchmarking.

Phone turns off randomly with low battery warning

Hello everyone! Recently my Note II started to behave differently. Whenever I charged it completely, the battery abruptly fell to sometimes 60% sometimes 40% immediately followed by low battery warning indication and shutting down. I tried changing ROM and calibrating the battery again but nothing worked. Finally I replaced the battery with a new one and also clean flashed another ROM in a hope to see if the problem is gone or still there. But to my surprise the problem is still intact. Now, when I turn on the phone the battery is 90% and when I keep using it, it drains normally, but as soon as I put it idle it turns off randomly. When I turn the phone back on the battery is still at the same percentage level at which is turns off. I believe there is not an issue with the battery. Please help me what to do, I am using TWRP recovery that doesn't gives the battery stats wipe option too. Should I flash a new ROM again? I would greatly appreciate if someone please helps me in sorting this problem.
What I have already done!
1. Replaced the battery
2. Changed the ROM
3. Re-calibrated the battery

Categories

Resources