Hi all.
I'm running Maclaw's CM10.2 and it's mostly great. I'm getting random reboots, which nobody else seems to be talking about. I've narrowed it down as far as possible. For a reboot to happen:
Phone must be on battery
I must be actively using the phone
The reboot goes right back to the Samsung boot screen. Most of the time, it enters a boot loop unless I attach power. I usually hear two "low battery" sounds during boot at this point, regardless of how well charged the battery was before. If I attach power during boot, it is fine, though it shows the battery as nearly empty.
The reboots don't happen when the phone is plugged in to power, which also means I can't reproduce them when connected to ADB.
Has anyone else seen this behaviour? Can anyone suggest how I can capture logs or debug these reboots?
Dan.
djs52 said:
Hi all.
I'm running Maclaw's CM10.2 and it's mostly great. I'm getting random reboots, which nobody else seems to be talking about. I've narrowed it down as far as possible. For a reboot to happen:
Phone must be on battery
I must be actively using the phone
The reboot goes right back to the Samsung boot screen. Most of the time, it enters a boot loop unless I attach power. I usually hear two "low battery" sounds during boot at this point, regardless of how well charged the battery was before. If I attach power during boot, it is fine, though it shows the battery as nearly empty.
The reboots don't happen when the phone is plugged in to power, which also means I can't reproduce them when connected to ADB.
Has anyone else seen this behaviour? Can anyone suggest how I can capture logs or debug these reboots?
Dan.
Click to expand...
Click to collapse
Read my FAQ here, to see how to take logcats.
mauam said:
Read my FAQ here, to see how to take logcats.
Click to expand...
Click to collapse
Awesome, thanks. I knew about logcat, but didn't know about last-kmsg. Now, of course, I can't reproduce the problem
Interesting. The last thing that happens is the AB8500 driver decides to shut down:
Code:
[37032.798461] ab8500-fg ab8500-fg.0: Low bat Interrupt occured, now waiting for power off condition
[37032.798522] ab8500-fg ab8500-fg.0: Capacity : 14 Voltage : 3070mV
[37032.798553] ab8500-fg ab8500-fg.0: KDG_DATA] 215mAh/1500mAh 14% (Prev 216mAh 14%) 3070mV -246mA -295mA -1639 0 0 5 1 1 130 10 0 0 0
But no proper shutdown happens -- it just reboots.
I can see in the log the battery capacity dropping smoothly from 38% at time 34403 (43 minutes earlier), but the battery monitor shows the reading dropping off a cliff (see attached). It looks like the last value the battery monitor could see was about 40%. Any ideas?
Also in the logs, "Shut down pending..." at 36955.787566 (a minute and a half earlier), but I didn't get any notification on the screen. And 15% capacity seems a bit high to be forcing a shutdown?
Related
im new to rooting, and i apologize if this is the wrong forum, but i believed it to be best.
my issue is that ever since installing the latest cyanogen mod, my battery is terrible, after about an hour i am down to 65-70 percent battery with minimal usage (no calls or programs, perhaps a text or 5)
i tried using the trouble shooting on the wiki which states
Code:
Battery recalibration
If you're experiencing higher than normal battery drain, try the following:
1. Charge the phone to full battery; power off and let it keep charging until the light is green.
2. Boot to recovery mode and go to console (or adb shell) and type:
mount -a
rm /data/system/batterystats.bin
1. Reboot the phone and use it normally, but don't charge until it shuts off.
2. Recharge the phone completely and then use as you normally would.
but when i tried the mount -a command i get various errors pertaining to "not found" i still typed in the rm command but i got no notification that it worked.
any ideas? im loving the mod, and the root community as a whole and i would hate to go back to the original rom
also another oddity i noticed... my battery will drain down to 20 or so percent, and ill plug in the charger for 10min and then itll say 97 percent? (not exact just round abouts of percentage) whats going on?
also ill reboot my phone or start it back up after it shut down to low power and itll be at 50% or way higher then it said it was when it shut down/rebooted
I dont believe it's a problem with the rom itself, it might just be the battery. I had that problem, and solved it simply by replacing my battery.
Did you overcharge your battery? If so, that's probably why your battery is unable hold a charge, or is giving off false percentages. (one way of knowing if you did is if the battery is bulging out)
there does seem to be a miniscule bulge on the battery, as i often left it plugged in even when it was at a 100percent. even so i did not have the severity of the problems i am having before i switched over to cyanogen
Same problem
My G1 has been shutting off at 70% battery, too. I tried to do the charge, mount -a, rm /data/system/batterystats.bin bit, and while I could mount -a, when I put in the rm command, the console returns that there's no such file or directory. My battery also has the tiniest bulge; is the next step to just get a new battery? I was not having this problem before Cyanogen Mod, either.
gooberguy said:
im new to rooting, and i apologize if this is the wrong forum, but i believed it to be best.
my issue is that ever since installing the latest cyanogen mod, my battery is terrible, after about an hour i am down to 65-70 percent battery with minimal usage (no calls or programs, perhaps a text or 5)
i tried using the trouble shooting on the wiki which states
Code:
Battery recalibration
If you're experiencing higher than normal battery drain, try the following:
1. Charge the phone to full battery; power off and let it keep charging until the light is green.
2. Boot to recovery mode and go to console (or adb shell) and type:
mount -a
rm /data/system/batterystats.bin
1. Reboot the phone and use it normally, but don't charge until it shuts off.
2. Recharge the phone completely and then use as you normally would.
but when i tried the mount -a command i get various errors pertaining to "not found" i still typed in the rm command but i got no notification that it worked.
any ideas? im loving the mod, and the root community as a whole and i would hate to go back to the original rom
Click to expand...
Click to collapse
I rooted my phone for the first time and am using CM5.0.7. My battery is acting weird. Tried using the console and typing those commands above, but I get the error message as well. Does someone know the answer?
Thanks.
To all the posters that are having problems getting access to the file... You might want to try switching your recovery to Amon_RA's latest recovery. He has a menu option which removes the battery configuration file for you. I believe the option is under the wipe menu.
Additionally, make sure you follow the steps for recalibrating the battery outlined in the troubleshooting section of cyanogenmod's wiki because just deleting the batterystat file will not help with the battery drain unless you follow the steps.
in addition to all of this, the battery life issues on 5.0.7 is a known bug that cyanogen publicized on twitter through his own testing. it's currently being looked into. so far, wiping battery stats has had no measurable effect beyond what is percieved to be slightly longer life by the user.
my suggestion: stick it out until the fix comes, which will be prior to a "stable" CM5 release.
my suggestion: stick it out until the fix comes, which will be prior to a "stable" CM5 release.
Click to expand...
Click to collapse
Good advice also. That is what I will be doing. I wanted to stick with this ROM so I tried the recalibration technique but I do confirm that it is having little effect.
yeah, there are people claiming that it's having miraculous effect, and then in the next sentence saying "oh, but i'm also not running any apps, have wifi, bluetooth, data and the screen turned off and it's been plugged in for half the time". you cant rely on results like that. if cyanogen says himself that theres a battery problem, i'd tend to take that as gospel. the man kinda knows what hes talking about on a massive scale.
try this
this was an issue with an old cyanogenmod. 3.8.1
I posted a workaround in the 5.0.7 thread. this worked for me, but YMMV.
add this to your userinit.sh file now located int /sd-ext/
Code:
echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
or run command in the terminal (not recovery's console)
check it with
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
before and after if you run it in terminal.
alternatively, set this value in setCPU. under advanced.
my values:
Code:
sampling rate : 2000000
up threshold: 60
ignore nice load: 0
power save bias: 200
this gives me about 10%-15% less battery life than the last build. which is better than I was getting friday.
AroundTheWorld said:
I dont believe it's a problem with the rom itself, it might just be the battery. I had that problem, and solved it simply by replacing my battery.
Did you overcharge your battery? If so, that's probably why your battery is unable hold a charge, or is giving off false percentages. (one way of knowing if you did is if the battery is bulging out)
Click to expand...
Click to collapse
I beg to differ, I'm having the same issues on the Evo 4G and have tried three different batteries. All batteries drain rather quickly and take FOOOOOREEEEEVVVVVEEEERRRRRRRRRRRRRRRRR to charge. Plugged in over night for over six hours only reaching 63% battery capacity?! Absurd! Does not happen with any of the Stock ROMs.
i have the same problem with a LG GT540f ... i installed cyanogenmod 7 and the battery life is extremly unestable... 1 hour and my cel gets OFF ....
no solutions yet?
The battery life on my NC is absolutely horrible. I average 3 hours unplugged, 1 hour if I'm using it. It doesn't seem to charge up all the way -- after plugging it in the light on the Nook cord is orange for about 10 minutes then goes green even though the screen still stays "Not enough power to turn on - Try again in 15 minutes".
I've tried using software like juicedefender and other battery mon apps that are supposed to be able to predict when you're going to lose your power -- but they appear to be useless. Often I'll get the "Your Battery is Getting Low" message at the very same time as the "Shutting Down" dialog appears -- almost like there was a very sudden dramatic drop in available power.
I am beginning to wonder if it's the result of faulty hardware.
Has anyone else experienced problems like these? Or should I restore back to stock and send it in for warranty?
That definitely sounds abnormal. I'd probably restore it back to factory and if it's still acting like that, you'll know it's not due to any modifications.
Yeah, I second that. Mine drains pretty quickly, I go from 100% to about 60% in a day with normal usage. I use Wifi Auto Toggle to turn Wifi off when the screen turns off. So far I have to recharge every other day or so. But what the OP has going on sounds pretty extreme.
What ROM are you using?
What programs have 'keep screen alive' do you run?
How bright is your screen?
Screen/wifi burn most of the power in this - so minimizing them helps battery life considerably.
I had one game (HexDefense) that prefers to run in maximum brightness and burned through the battery very quickly. Nook was the warmest I've ever seen it and the temperature on my battery monitor actually moved for the first time ever.
SO if you're getting 3 hours doing nothing, that's bad. If you're getting 3 hours running a really processor/graphic intensive game, that's good.
If you can get it back to stock and still have low battery life, consider talking to the manufacturers about it.
OverDrive33 said:
The battery life on my NC is absolutely horrible. I average 3 hours unplugged, 1 hour if I'm using it. It doesn't seem to charge up all the way -- after plugging it in the light on the Nook cord is orange for about 10 minutes then goes green even though the screen still stays "Not enough power to turn on - Try again in 15 minutes".
I've tried using software like juicedefender and other battery mon apps that are supposed to be able to predict when you're going to lose your power -- but they appear to be useless. Often I'll get the "Your Battery is Getting Low" message at the very same time as the "Shutting Down" dialog appears -- almost like there was a very sudden dramatic drop in available power.
I am beginning to wonder if it's the result of faulty hardware.
Has anyone else experienced problems like these? Or should I restore back to stock and send it in for warranty?
Click to expand...
Click to collapse
You really question this? Something is wrong with your NC, cable, or charger.
I love the Angry Team rom v3.6 no issues whatsoever. But now after flashing Angry ROM v4.2 I am feeling certain issues which are very isolated incident (not reported by any of the users so far, i guess). And the bugs are
1. The charging has just gone mad. I would charge it for 100% but once rebooting the phone says that there is absolutely no power or very less (~10% - 15%). Actually I tried to wipe the battery stats, but I could not able to find that option in Philz's Kernel. Can any of the techies help me on how to wipe the battery stats and how can I get the proper stats and correct battery level again. This is very annoying for me, because I dont know even if I see the phone is fully charged, it still may not be so actually.
2. My Note phone mysteriously flickers and automatically shuts down as such flickering intensifies. If I try to connect the phone immediately to charge the flickering stops and be stable for the next 30 mins. This flicker happens even when there is sufficient charge in the phone.
3. At times I see the phone gets hanged.
3. Contacts have a horizontal stripe at top making it difficult to read the recent dialed numbers. (Probably an issue in ROM or something needs to be changed).
Any help is greatly appreciated.
Your battery is dead.. Buy a new battery
Sent from my GT-N7000 using Tapatalk 2
it seems to happen only when it gets high load (high app usage..).. when some cpu intensive app is running, 3G is on, etc..
it shuts off (does't restart automatically), and when I turn it on again, the battery meter is always awful lower than before.. it does NOT happen if it's charging or plugged in usb cable..
I've made some tests with it already, before posting:
- it happens with stock kernel and with cocore 6.8 or 6.2 (I think), so I think it doesn't matter the kernel
- it happens with stock ddul? firmware and dxamd1 (pure vanilla), so I think it doesn't matter the rest of the SO
- it ALWAYS happens while stress testing with AnTuTu with less then 80% battery
- it won't happen while charging, no matter what. (AC or USB)
- it happens a lot less if POWER SAVING mode is on... (I think it's because it won't let cpu goes to 1ghz, sucking less energy from battery)
so.. MY verdict is: my battery is failing.. right? have to replace it, right? 13 months of use only... any tests I could do before buying a new one? is there any really trustable site where I can buy a good one? fake battery are ALL AROUND and they SUCK
This is absolutely normal because this is a function of android. It automatically shuts down when the cpu high loads to avoid hardware breaking.
Inviato dal mio GT-I9070 con Tapatalk 2
What? so is it normal to turn the phone off IN MY FACE whenever I try open foursquare and instagram at the same time?
it should restart normally.. not shutdown..
it defeats its purpose as a phone when auto shutdown..
I think I'm missing something here.. why are you both saying the phone SHOULD restart or shut off itself? of course it shouldn't. There IS something wrong.
And today, after like 6 consecutives shutdowns, I put it on the charger.. and suddenly from 6% of battery it got to 60% !
I've read about battey discalibration.. and it sometimes fit.. but not the sudden shut off.
I've tried the method of trying to turn it on many times till it can't even display the logo.. (MANY times it displayed the logo, tried to boot, but shut down afterwards).. then I fully recharged it.. boot, recharge, boot, recharge, boot recharge.. but no success..
Whenever the battery is lower than 80%, any heavy app I try to use (like foursquare), it just shut offs in my face. It's like I pulled the battery off!
edit: today it happened again.. the battery was 20%.. I was using it normally.. then suddenly POOF: black screen on my face! When I turned it on again, it said 5% battery.. and 5 seconds after that: black screen on my face!
maybe is there any LOGS about what is going on .. ??????
I don't think it's about the battery. Maybe something's wrong with the device. Try taking it to the service centre.
I wonder if you can provide me a dmesg log?
In Terminal Emulator, you can try:
su
dmesg > /sdcard/dmesg.log
"All lights must fade, all hearts return to darkness."
here.. just after a crash.. I turned it on and plugged in usb cable for adb shell ..
I would recommend you completely go back to stock and test. If it does work, you know where the problem lies. If it doesn't, it's time to use your warranty
Sent from my air conditioner
CallMeVentus said:
I would recommend you completely go back to stock and test. If it does work, you know where the problem lies. If it doesn't, it's time to use your warranty
Sent from my air conditioner
Click to expand...
Click to collapse
I downloaded I9070XXLQG_I9070ITVLQ3_ITV.zip and installed via odin (on PDA section).. it seems that nothing has changed..
In "About", every version is XXLQG but it continues to crash if I use it for more than 10-20 minutes (without the charger/usb plugged in)... lol
and I don't have warranty...
fbs said:
I downloaded I9070XXLQG_I9070ITVLQ3_ITV.zip and installed via odin (on PDA section).. it seems that nothing has changed..
In "About", every version is XXLQG but it continues to crash if I use it for more than 10-20 minutes (without the charger/usb plugged in)... lol
and I don't have warranty...
Click to expand...
Click to collapse
If that's the case, your phone is suffering from a terminal illness. I wish you the best of luck.
CallMeVentus said:
If that's the case, your phone is suffering from a terminal illness. I wish you the best of luck.
Click to expand...
Click to collapse
don't you think it's "just" the battery? it seems it's not charging enough never.. it says 100% but it doesn't handle the load.. also, is there a way to REALLY reset everything? even a "factory reset" keeps many files on /sdcard.. and "re-partition" on Odin crashes it
ps.: pardon me but don't you think your signature is too big? you waste half the forum's page with it..
fbs said:
don't you think it's "just" the battery? it seems it's not charging enough never.. it says 100% but it doesn't handle the load.. also, is there a way to REALLY reset everything? even a "factory reset" keeps many files on /sdcard.. and "re-partition" on Odin crashes it
ps.: pardon me but don't you think your signature is too big? you waste half the forum's page with it..
Click to expand...
Click to collapse
Have you tried changing the battery then?
ps: I've not been notified by anyone saying that my sig is huge, I've added hide tags for a reason
CallMeVentus said:
Have you tried changing the battery then?
ps: I've not been notified by anyone saying that my sig is huge, I've added hide tags for a reason
Click to expand...
Click to collapse
I'll try to find someone with S Advance to borrow the battery for 1 day then... maybe it is compatible with other models? ..
ps.: http://i.imgur.com/09KE3DQ.jpg
Sure thing, I'll change my sig.
Sent from my air conditioner
If anyone step by this topic.. I found a solution to my problem.. I replaced my battery..
it was "swollen".. I thought it was kinda normal to be like that but IT ISN'T. If your battery isn't *completely* FLAT, you'll have to replace it...
I have the phone for a week now and more and more it's shut down when I want to switch it on. I then have to press the power button a bit longer and it will then restart normally.
And there is something else that I think is strange (I just found out while testing because of the other issue). When I press the power button multiple times then sometimes it doesn't switch on again. After a wait of a few seconds and another press it switches on again.
Anyone else has these issues? Can I track why it switches off? Is there a log to see what happend before?
Only when it's cold
I noticed that the random shutdowns are not so random. It only happens when the phone is cold. I can put it 3-4 minutes outside (a bit below 0 degrees celsius) and it switches off every time.
When it's warm - it never happens.
Anyone else have this problem? what's the temperature range which it should work in? I never had that with another phone and it's really not that cold.
Not me, but it's not that cold here.
But it is coldest time since i have z3c and i noticed that in camera when switching from superior auto to manual, or anything it lags a bit when it's cold.
I couldn't find operating range for our battery but it looks like that most Li-Po batteries suffer when temps go below the 0C
I'm going to assume that's your case.
Standby phone = no heat being generated = available current dropping = phone shutting down
Info
chaelli said:
I noticed that the random shutdowns are not so random. It only happens when the phone is cold. I can put it 3-4 minutes outside (a bit below 0 degrees celsius) and it switches off every time.
When it's warm - it never happens.
Anyone else have this problem? what's the temperature range which it should work in? I never had that with another phone and it's really not that cold.
Click to expand...
Click to collapse
weird
thr s always process in background so the phone temp will be always above 0 C
unless the environment temp be too below 0C (like -20C)
contact service center and tell the story and please inform us here what s their response
:good:
Thanks for the inputs. I know that there is a limit on lower temperature for the batteries. But as I easily was able to restart the phone and it showed no strange value for the battery-power, I don't think it can be only this. Also - we had 5 other phones with us and they all worked in the same environment. I'll keep you posted what the service center answers...
I have been in low-temperature environments(-18,+4,0 C) I did not stay too long, but phone survived without any hassle
I am having a very similar issue. Since day 1, my phone randomly reboots especially during the night every 20 minutes or so, and i usually find it switched off in the morning when i wake up. I even had to go work late the first morning because I use the alarm of the phone to wake up and since the phone was switched off, the alarm didn't work.
Last week i went to ski. Up in the mountain, the phone was almost completely useless ( Tempererature was just below 0 C ). It was constantly rebooting in my pocket and shutting down every 5 minutes. Whenever i wanted to use it, the screen opened and as i unlocked the phone it rebooted, however if i continue to use it afterwards ( opened mobile data and gps, talking, etc. ), it did not reboot. So i thought that it might be due to battery getting too cold. Also, i realized the rebooting happens more frequently when i put the phone in a very low power usage state like Ultra Stamina or flight mode. ( I also put the phone in flight mode during the night when i go to sleep )
I have contacted Xperia Care. They assumed this might be a software malfunction and suggested resetting my phone using PC Companion. I played along and reset my phone but it didn't fix anything. I will call them again tomorrow. I am suspecting the battery itself is faulty or the background task that is supposed to heat up the battery is not working properly.
Update: : Appaerently the phone was in fact faulty. They changed it with a new one which is working pretty fine