Latest SiyahKernel with stock rooted ICS 4.0.3.
Now, this has happened twice in the last week. I unplug the phone from my charger and place it under my pillow for the alarm to wake me up, and go to sleep. I disable both data and wifi so that twitter won't update and wake me up prematurely. Then, I oversleep about two hours, and what wakes me up is the phone that's EXTREMELY hot. The alarm doesn't go off and the battery is completely drained.
I have no idea what drained the battery and why the phone was that hot (I couldn't hold the phone for more than two seconds before I started experiencing pain). I've tried searching, but there were no topics like this one. So does anyone know how I can fix this?
~November
http://cow.neondragon.net/index.php/how-to-resolve-poor-battery-life-battery-issues-on-android
Thanks for the answer, but even after doing everything there I have the same problem.
A few days ago, I was able to "intercept" the process.
I had just used the phone, and put it away. Then after no more than ten minutes, I noticed it getting extremely hot. When I tried unlocking the screen, the phone had frozen, so I had to pull out the battery to turn it off. When I put the battery back in again and turned it on, the battery level was down from around 80% to around 60%. The battery graph showed like vertical drop, so it was clear that it had happened within those 10 minutes.
Is there really noone who has had this problem before?
November13 said:
Latest SiyahKernel with stock rooted ICS 4.0.3.
Now, this has happened twice in the last week. I unplug the phone from my charger and place it under my pillow for the alarm to wake me up, and go to sleep. I disable both data and wifi so that twitter won't update and wake me up prematurely. Then, I oversleep about two hours, and what wakes me up is the phone that's EXTREMELY hot. The alarm doesn't go off and the battery is completely drained.
I have no idea what drained the battery and why the phone was that hot (I couldn't hold the phone for more than two seconds before I started experiencing pain). I've tried searching, but there were no topics like this one. So does anyone know how I can fix this?
~November
Click to expand...
Click to collapse
Try N.E.A.K ICS kernel. I had some really good results with aokp rom. It's compatible with Samsung rom as well I think. Check it out
Sent from my GT-I9100 using Tapatalk 2 Beta-5
I'd be more worried about it setting my pillow alight
Steps.you could try:
- Wipe all data (Optional maybe an app conflicting with something)
- Update kernel or change rom to CM9 or any other stock
- If none of those work try an different battery
*I believe its an well wakelock had this when i was using siyah 3.1 Rc 1-5*
~Blizz™;
I had roughly the same problem. I did a full wipe and installed a custom from and changed the kernel... everything works perfect then. One of my friends finds taking his battery out every few days works best. Try both and see what results you get.
Sent from my GT-I9100 running ics resurrection v1.4 using xda app
I would have to guess that it's either the kernel or the battery calibration. Are you using a third party battery? I think with the original samsung batteries, this must not be as much of a problem (I have never owned an original samsung battery for my S2, sadly). I know that with my fake Chinese super-cheap "2150mah" battery, which somehow is small enough to fit in the original cover which makes me think it's more like 1350mah, I have gotten horrible battery drain problems for basically no reason. But, after following the thread where it was explained to charge to 100% and then take the battery out, wait three minutes, and put it back in, I've had the phone stay at 100% for over four hours, with wifi, syncing, and all that turned on.
I should mention that I sometimes also have had this problem where it seems to be charged, then for some reason it drops to 20%.
If your battery is third party, make sure you calibrate it. I've also noticed that the more roms I flash, the worse my battery life is, so I'm trying to resist the temptation of flashing something new every twenty minutes.
Good luck.
/proc/last_kmsg
Use it.
You could try downloading Better Battery Stats and hope to identify the wakelock or app that's draining the battery. If it's not either of those and you haven't always had an issue with it under your pillow, I'd say it's time to try a wipe and new rom and if the problem persists even after that...hardware problem.
Have you been able to leave it under the pillow previously? Part of me is wondering if the overheating itself is affecting the battery and causing it to degrade though I doubt it should happen so quickly and in such an odd fashion as you're experiencing.
After a bit more tinkering and testing, I'm almost 100% certain that it's the kernel, as it was the only thing "constant" in my testing. I reflashed over and over. I also think it has something to do with the wifi, since when wifi's off, my phone is fine and doesn't get touched by the described bug. So right now, I'm waiting for SiyahKernel 3.1 to be released while keeping wifi off.
On the changelog for RC6, it says that the "battery drain issue" is fixed, and on the changelog for 3.1, it says "new wifi drivers", so I'm assuming it'll be ok once the 3.1 is released. Thanks for all your replies and help.
November13 said:
After a bit more tinkering and testing, I'm almost 100% certain that it's the kernel, as it was the only thing "constant" in my testing. I reflashed over and over. I also think it has something to do with the wifi, since when wifi's off, my phone is fine and doesn't get touched by the described bug. So right now, I'm waiting for SiyahKernel 3.1 to be released while keeping wifi off.
On the changelog for RC6, it says that the "battery drain issue" is fixed, and on the changelog for 3.1, it says "new wifi drivers", so I'm assuming it'll be ok once the 3.1 is released. Thanks for all your replies and help.
Click to expand...
Click to collapse
I had best results with Siyah RC6. You could check results on my thread and use as reference if you want. Link on my. Sig.
Sent from my GT-I9100 using Tapatalk 2
Related
Hello all,
I purchased a Galaxy S2 at the end of July, I live in the US, so it was from Amazon. The phone has been phenomenal, an amazing piece of technology.
I rooted the phone and flashed Lite'ning Rom 6.1 XXKH3. Still worked great, with no problems at all.
However, starting about a week ago, I am getting an extremely fast battery drain. Since then, I have spent hours looking at threads trying to figure out what was going on. I updated the rom to UltraToxic Rom v8.0 XWKK5, still no change.
I used Titanium Backup to freeze many widgets and app processes, still no change. I am currently using better battery stats to monitor wake locks, however after managing the wake locks, still no change.
I then bought a replacement battery thinking that the battery may have been bad, sadly, there was no change.
I have been trying to find a solution to this and had tried many other suggestions in other threads to no avail. As of now I have come to the conclusion that the device might have some type of malfunction that is causing this.
Am I going crazy or am I missing something obvious? Any help would be greatly appreciated.
Thanks
I have also re-calibrated the battery, still no positive changes.
Seeing the battery graph, you have your screen on a lot of time. Screen sucks battery a lot, so there might be one of the causes of battery draing.
Also you seem to have all day enabled 3G/WiFi, that also sucks some battery with it.
You can try JuiceDefender and see if it can help you extend a little your battery.
change kernel
Try flashing hardcore's "SpeedMod Kernel" and you will never complain about your battery life.....
After flashing this kernel my worse battery life was 1day and 12h with 3.5h screen on and wifi 85% ON.
http://forum.xda-developers.com/showthread.php?t=1182498&highlight=speedmod+kernel
AzureusPT said:
Seeing the battery graph, you have your screen on a lot of time. Screen sucks battery a lot, so there might be one of the causes of battery draing.
Also you seem to have all day enabled 3G/WiFi, that also sucks some battery with it.
You can try JuiceDefender and see if it can help you extend a little your battery.
Click to expand...
Click to collapse
Lol.... It's obvious he has some kind of battery problem, he is not using the phone much, and galaxy S 2 should have at least 5-6 hours screen on time and the phone lasted 3 hours.
Sent from my GT-I9000 using xda premium
Since I had all data on the phone backed up, I did a factory reset. I also flashed the UltraToxic Rom v8.0 XWKK5 as well as the suggested SpeedMod Kernel. When the battery was at 100%, I calibrated the battery. I tried to leave the phone idle as much as possible, I did use the internet for about 10 minutes to check e-mail, news, etc. So now the phone is essentially "empty" in terms of apps downloaded, I got rid of all widgets on all home screens.
There was still no positive change, I do really like the SpeedMod Kernel though, I do notice faster responsiveness from the phone.
I am beginning to think that the problem may be the hardware and not the software or battery.
I've got similar problems here. I am suspecting a hardware problem (I damn well hope it isn't coz i got mine from hong kong) because my phone never goes into deep sleep mode for more than 50% while the screen is off. I've tried at least half a dozen different kernels and roms and nothing helps, this is even in airplane mode i.e. with pretty much everything turned off. I've tested wakelocks and dont get anything more than a couple of seconds. I had my battery charged to full at 6:30am this morning, went to work and got home and it was dead after just under 12 hours with being idle 75% of the time. This is worrying as most people's battery lasts at least a whole day.
So I know it can't be the kernel, I know it cant be wakelocks, I know it cant be wifi or 3g data or anything of that nature so the only thing it comes down to now is hardware...
Funnily enough I've had exactly the same issue since about a week ago. Even when I take it off charge it's almost immediately down to around 80%. It's lasting around 4-5 hours, even when I'm not using the phone much, plus it gets really hot.
A couple of times Social Hub has appeared high up on the list of battery draining apps, although I don't use it. It doesn't always show up though. I switched to the CF-Root kernel and started using GO Launcher EX recently and wondered if that (or one of it's addon widgets) could be the cause.
It's really bugging me now!
SOLVED!
After days and days of trying to fix the issue of the phone not sleeping (and therefore draining excess battery whilst idling) I have finally fixed it!!!!!
First i noticed that along with the sleep problems, I was getting the problems with car mode popping up randomly, the phone going into mtp connection mode, and thinking its charging when it was unplugged. After looking into these issues (and i thought it was a longshot) I decided to do what people were saying and CLEAN THE MICRO USB PORT.
Now you're probably thinking I am a crazy man, but now im just crazy happy that I don't have to send my phone back to Hong Kong!
Instructions:
1. Get a clean, dry, soft-bristled toothbrush.
2. Take any case you have off the phone.
3. Gently insert the bristles into the port and "flick" it out softly.
4. Repeat this about 10-15 times
No matter what ROM, what kernel, what modem i tried flashing, my phone was always sitting on no more than 50% deep sleep mode when idle and had no wakelocks or "rogue apps".
I am now getting 90% - 98% DEEP SLEEP MODE!
I obviously can't guarantee that it will work for everyone, heck how it solved the issue is a mystery to me, one which probably an electronically-minded/computer systems person could answer. What I can say though is I searched high and low online for about a week. I tried different kernels, I tried different ROMs, I tried "re-calibrating" the battery, I used BBS to check for partial wakelocks. If you too have tried all this and have had no success please PLEASE try this and see if you have success!!
Thanks for reading!
....
Or if you didnt...
TL;DR: If you're having battery drain problems clean the micro USB port with a soft toothbrush.
The phone never sleeps when charging, the CPU idles at 200 MHz, whatever was in your USB port was probably making contact with the pins that tells the phone it is connected to a charger when it actually is not, so it was idling at 200 MHz and was not receiving power, that's the only explanation I could fathom
Do two things:
Install CPU spy and show us what the deep sleep percentages are,
and try disabling wifi. Also, what is the router?
I have a battery drain issue; but its kind of screwey as i will reboot my phone and lose about 20% of the phones charge. If i turn it off and leave it off for an hour the charge comes back. Its random as well; only happens once a week. I have had this problem on different roms. You might have a similar problem to me. Possible the hardware that detects battery state is knackered.
Sent from my GT-I9100 using Tapatalk
try to reduce screen brightness it might help, and when on wifi turn off data plan might help too
kamazaki said:
try to reduce screen brightness it might help, and when on wifi turn off data plan might help too
Click to expand...
Click to collapse
Since you didn't seem to realize, I thought I'd tell you. This thread was 5 months old before you posted in it...
lol
And im not sure what to do. I need some advice because I just cant find the issue! This morning was the final straw, my phone was at 100% charged and all i did was take about a 3 hour nap woke up to an over heated phone and the battery at 10%. WTH?? I use cpu spy and juice defender and nothing. I barely have any apps other than a wellsfargo one and 3g watchdog. Im running [ROM]<=TASK650's ICS'd OUT! V5 right now and i just switched over from cm7 because i thought maybe that would've been the problem? I dont know if its a deep sleep issue because ill look over at it sometimes and the screen just turns on out of nowhere and ill have to press the sleep button for it to turn back off. It also like to randomly turn off as it please. AHH THE FRUSTRATION .
Anyway enough rant can someone help? Or at least give some advice on what I should try or do? Thanks.
Your screenshots are inconsistent with your stated behavior... Loss of 20-30%/hour and an overheated phone says the thing is stuck at 1200 MHz and full load - but your CPUSpy graph shows only 9% at 1200, and a total of maybe 40-50 minutes since reset.
Also the battery graph in your first shot has a major discontinuity... It drops from 100% to 10% instantly. I've seen glitches of 20-30% jumps at a time after a fuel gauge reset, but never anything like that.
So then what your saying is I should kill it with fire and then return it and grab another one? lol I dont know anyone else with this type of situation. Im not just one to go and ask a question because im too lazy to search. I swear i looked and googled EVERYWHERE for some type of solution but i just haven't found someone with this type of problem.
as Entropy mentioned, that jump in the first screenshot makes no sense. You should probably recalibrate the fuel gauge.
Looking at the 2nd screenshot, a lack of deep sleep seems to be the culprit. You'll need to track down what's keeping your phone awake. I've read something about exporting the wakelock log but perhaps there's already an app for that...
Also, clicking on the graph (in the first SS) will show you a more detailed burn down which might help isolate the issue.
Lastly, did you change kernels as well?
Im sorry im fairly new at this. It just has the kernel that the rom came with. I recalibrated the fuel gauge like you said and retook some screen shots that ill just leave here. It keeps over heating and Shutting off on me every half hour or so. On top of that The battery just drains in a mater of 3 to 4 hours. I think the problem is just the phone itself. Im going to try and put the original stock rom on it later this week when i have time (Finals are driving me crazy) and then Im going to try and send it back and get another one. I might need a usb jig thingy tho. Its very frustrating this phone isn't even a month old and like i said before i googled for a full hour and a half and I just couldnt find a solution to this.
mmmk this just happened.
That certainly doesn't look normal. When it takes those sharp dives is the phone rebooting? Also when you flashed your new ROM did you wipe all data in cwm first?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
I had a similar problem (phone got extremely hot) when i first flashed to UnNamed but after re-calibrating the fuel gauge a few times everything was all good.
melissa_smalls said:
mmmk this just happened.
Click to expand...
Click to collapse
Suggest running better battery stats from a full charge and when you get that instant drop go into bbs look at partial wake locks.
Also have you done any
oc/uc ?
Running ICScrewD ROM
twiggums said:
That certainly doesn't look normal. When it takes those sharp dives is the phone rebooting? Also when you flashed your new ROM did you wipe all data in cwm first?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Yes it shuts off every half hour or so and when i realize it and turn it back on the battery is drained significantly and yes i wiped all the data in cwm.
jivy26 said:
Suggest running better battery stats from a full charge and when you get that instant drop go into bbs look at partial wake locks.
Also have you done any
oc/uc ?
Running ICScrewD ROM
Click to expand...
Click to collapse
Ok Ill definitely give that a try the moment I have a chance and report back here the results. I haven't done any oc/uc either. Thank you guys for taking the time to help me figure this out.
I would try a CWM Backup. Then Factory Reset, Cache Wipe. Then install a fresh copy of Task v6. If that doesn't fix it, restore back to your backup you did.
I was having fun with undervolting myself (would crash my phone). Every battery pull I did, I lost 20-50% battery life. JUST turning the phone back on! Though in my case the phone would stick at this percentage for a long time, then when it caught up, eventually draining. I would assume the battery was not calibrated, but people keep telling me "this battery does not need calibration" (Whatever).
It seemed to fix itself for me though, after letting it drain down a bit more. I let it fully charge this time with the official wall charger. This was with Task & Siyah. Has not happened since.
I hope your battery works itself out!
melissa_smalls said:
Yes it shuts off every half hour or so and when i realize it and turn it back on the battery is drained significantly and yes i wiped all the data in cwm.
Click to expand...
Click to collapse
kk so I'd guess your battery really isn't that low, it's just reading low after those reboots. For whatever reason sometimes the phone will show a significant loss after a reboot, but really didn't lose that much. However something still isn't rite obviously. I'd suggest redownloading your ROM and clearing/wiping everything in CWM. And do a fresh install. Someone might be better able to help, but if I was getting random power downs that's probably what I'd try. (I might be wrong, but I don't see how wakelocks would be causing it to power down)
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Thanks for the input everyone. I just got back from class now and my phones dead no surprise there but Im gonna let it charge back up and ill repost some screen shots of cpu spy and betterbatterystats since i just got that running on the phone. Afterwards Im going to try to just wipe everything on cwm reinstall a rom and see what happens from there. I bought a usb jig that should be coming in by the end of the week just in case all else fails and i'll just send it to att and have them ship me a new one. Thanks for all the feedback you guys are awesome!
OH I forgot to mention I dont think the phone actually shuts off because I was talking on it for a bit but i was talking through my bluetooth headset. I went to check if i had a text message and the screen wouldn't power on but I was still able to talk on the phone WTF? Makes no sense to me.
Really starting to wonder if your CPU has voltages it can't handle...
Hi, I got a very annoying problem.
Since a few weeks ago, flashed a ROM and when I've tried to use the phone, it keeps turning off randomly, sometimes after a few minutes, sometimes after hours. So, I tried to take it back to the clean original 2.3.3 ROM, but it keeps happening. ¿Any idea? ¿Any solution? Please, help me.
Oh, something else, it only happens when the phone's used with the battery, when it's attached to my laptop and used as modem, the problem doesn't appear.
I had the same problem, it said android system shutting down. I just bought new battery and it works.
Sent from my Xperia X10 using xda premium
I think, it's the most logical option, but I was trying to get some feedback first. Thanks.
Maybe calibrating the battery.
Sent from my Xperia X10 using xda premium
go back to stock and see if it helps! try to troubleshoot the problem! Also, don't install any apps!
There are instructions on how to calibrate your battery in the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=1489214&highlight=calibrate+battery
If the problem is the battery, you might find that after calibration that the battery drains faster than expected, and still shuts down, only this time it warns you that it's gonna shut down. This would then be the true battery drain. If that is the case, you might just need to buy a new one anaway.
Otherwise, I don't know what else could be causing those symptoms. (Other than an electrical fault, from accumulated damp or something)
kZard said:
There are instructions on how to calibrate your battery in the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=1489214&highlight=calibrate+battery
If the problem is the battery, you might find that after calibration that the battery drains faster than expected, and still shuts down, only this time it warns you that it's gonna shut down. This would then be the true battery drain. If that is the case, you might just need to buy a new one anaway.
Otherwise, I don't know what else could be causing those symptoms. (Other than an electrical fault, from accumulated damp or something)
Click to expand...
Click to collapse
thanks so much..............
What happens it's that the phone shuts down suddenly, the message appears for a seconds and it's off. Wait for a few seconds, try to turning on again and sometimes works for some minutes, and sometimes it's keeping turning off, and off, and off. But, the battery level seems to be correct, I mean, when I turn on the phone after one of these sudden shutdowns, only drains the logical ammount of battery for starting use the phone.
I think... if the problem never appears when it's attached to the laptop and charging constantly, and magically appears when I used the phone with the battery, it's probably just a battery issue, right?
I have a similar problem to this, my phone randomly shuts down after showing the 'Android System shutting down' message but sometimes loses ALOT of battery. Last night it went from 78% to 8% after shutting down :/ I noticed it happened more often when im playing games or taking a video, things that take up more battery. When i keep it plugged in it keeps awake so the problem stops but i cant keep it in all day every day. I dont really want to buy a new battery until i really really have to, but I have had the phone and battery since the x10 first came out about 2 years ago, so anyone any other ideas? Thanks
danielk0302 said:
I have a similar problem to this, my phone randomly shuts down after showing the 'Android System shutting down' message but sometimes loses ALOT of battery. Last night it went from 78% to 8% after shutting down :/ I noticed it happened more often when im playing games or taking a video, things that take up more battery. When i keep it plugged in it keeps awake so the problem stops but i cant keep it in all day every day. I dont really want to buy a new battery until i really really have to, but I have had the phone and battery since the x10 first came out about 2 years ago, so anyone any other ideas? Thanks
Click to expand...
Click to collapse
Try wiping battery stats then charge to 100% (it may help, not sure)
Sent from my X10S using XDA
laneyofdeath said:
Try wiping battery stats then charge to 100% (it may help, not sure)
Sent from my X10S using XDA
Click to expand...
Click to collapse
Yeah tried that but it didnt seem to work :/
could it be hardware problem like broke battery or bad connection on motherboard?
Could be pal are u within your warranty (sony (Ericsson) it has a 2 year global warranty but u need to ring ur network provider and ask them to put u through to se
Sent from my X10S using XDA
Yeah this happened to me before about 6 months ago, so i went to my provider (3) and they sent it away to Sony Ericsson and they sent me a whole new phone but I didnt want to do that again really, but i may have to. When im not using WiFi or 3G then it works fine, and when its plugged in to the charger it works so i guess its a case of not usuing the internet when im not near a charger
I have the same problem.
My X10 reboot random when using 3G (Wifi is still OK) and Gaming. Now i'm on Stock 2.3 and stock kernel and....wait. (Flash some ROM and change the new battery....but not solved )
Anyone help us !!! Plizzzzzzzzzzz
Maybe your solution
I had the same problem sometimes with original kernel after 1 year of using my phone.
Then i tried to install a new rom, and i was thinking the problem was solved. But it was not...
I finished by trying the X10S (v7) rom with DoomLord kernel (1113mhz) and this problem was solved...
I tried some kernels and this one was stable with a good battery life and no shutdown problem. With some other kernels i had this problem back.
So I think that kernel could be the problem.
Infortunately, with the rom X10S v8, Doomlord kernel cause issues with wifi (unable to get ip adress). So now i use kCernel-SE-stock-mod-v1 and no shutdown problem anymore.
*Maybe the solution is*
Try to change your kernel with one of thoose :
- kCernel here (in "2. kCernel-SE-stock-mod-v1")
- DoomLord (search fo x10_gb_DooMKernel-v06-1113_wifi.zip)
Note :
- With this two kernels, you'll have to download appropriate wifi patch and install it from SDcard via xRecovery
- don't try to install X10S v8 if your bootloader is locked
So, try to flash your X10 using flashtool with Doomlord kernel
Tell us if it worked, i hope it solved your problem as it do it for me.
voltage
Hi,
I have had this issue too, for the last few months. No matter what ROM/Kernel, batt stats cleared, etc, still the same. Can idle all day, but as soon as I use 3G, GPS, or use any intensive app, she shuts down.
As an experiment I installed a battery monitor that plots graphs of % charge, temp, voltage, etc over time.
I had a close look at my logged graphs and have noticed that just before each reboot, the voltage seems to dip drastically. Battery charge is fine, does not seem to matter. but a sharp drop in voltage occurs. Increased draw for the more complex tasks (3G, GPS, etc) seems to be tripping it up.
As the Battery is now 2 years old, I figured it is just starting to fail? And iv noticed lots of people are suddenly coming out and complaining about this issue.
I just ordered a few new Batteries from 'Ebay', will see how we go!...
peace.
[INFO / SOLUTION] Suddenly shuts off with red LED.
Good to know:
The X10i/a have now reached an age, where battery failures is very common nowadays. Specially if one got the device early on or just after the launch.
Symptoms of a failing battery:
* Device suddenly shuts off, even when the battery have several percent remaining.
* Device drains fast, even when not used.
* Device might just shut off for no whatsoever reason when doing something that draws a lot of power, and will restart just fine.
* Device has a surprisingly fast charge time from empty to full.
When the device shuts off all of a sudden, it's followed by the indicator LED blinking red, rapidly three times, and might repeat this at restart attempts.
Sometimes it takes several tries before the device starts up again. Battery just needed a few minutes/an hour of "rest".
There's nothing wrong with the device.
Just get a fresh replacement battery and it'll work just fine again.
But beware:
There are many fake batteries out on the market, claiming that they have higher capacity, yet very slim in size.
There's a simple rule when it comes to battery capacity:
More capacity = larger in size, which might need a special back-cover. There's no escape from that.
If one would happen to find a such incredible slim battery with super capacity, the battery security circuits and/or chemical makeup probably have been circumvented/changed, and have a high risk of catching fire and/or explode when charging/discharging.
Yeah thanks for all the advice and sharing your problems. My phone does reboot alot when im using 3G or taking a video. Recently my battery would reboot, drop alot of percentage and then increase percentage without charging...magic I dont really want to buy a new battery because my new contract starts in june i think, but maybe il have to. Good luck for everyone else dolving there problems
Also, [email protected], i am on doom kernel and i still get reboots :/
danielk0302 said:
Yeah thanks for all the advice and sharing your problems. My phone does reboot alot when im using 3G or taking a video. Recently my battery would reboot, drop alot of percentage and then increase percentage without charging...magic I dont really want to buy a new battery because my new contract starts in june i think, but maybe il have to. Good luck for everyone else dolving there problems
Also, [email protected], i am on doom kernel and i still get reboots :/
Click to expand...
Click to collapse
I've too had the same problem. solved it by replacing battery
Now everything's alright
I'm running dixperia rom with stock kernel
EDIT: but now I have a small problem. Hope someone can solve it. Sometimes, suddenly, the hardware keys light and backlight turns on, without doing any thing and this drains my battery I have to turn on the screen and turn it off back to switch off that backlight and hw keys light
Sent from my Xperia x10 using my fingers
Im getting a new battery soon I hope so I will hopefully get my problem solved
Can anyone help me with this problem here?
I have been trying various roms on my Vibrant, but didn't spend a ton of time on the ones before Paranoid Android because they seemed unstable. So I can't fully tell you if I was having this issue before, but I will say that the battery drain didn't seem as extreme.
I noticed that I was having extreme battery drain the night after I flashed PA (it was plugged in overnight). I was trying to charge it before I went out, and here's something weird - I was talking on the phone plugged into *AC* power (NOT usb!) and the battery drained during the call! That kind of threw me because it's never something that's happened on AC for me. By the time I went outside, it was down to almost nothing, drained about 5% in 3 minutes walking to the bus stop and died. I recharged it again, swapped in my extra battery in case it was a battery problem, and noticed that also it took a couple of hours of basically not using the phone to drain to 0. I have no signal issues in my area.
I noticed that in BBS that a wakelock ste-gps-interface was taking up a TON of time. I am not using GPS that much. I figured it may be Google now, so I actually froze the app. That didn't seem to help, so I turned of Google location services as much as I could to still use maps - basically everything short of turning GPS off itself. I still got the wakelock! This shows up in the battery settings as making "Android OS" jump to 50% when this is happening.
So since whatever is triggering this wakelock causes the phone to not go into deep sleep and idle at 100mhz, I'm getting bad battery drain. I tried several things such as updating the Semaphore kernel, reflashing the GPS data, using an AGPS app to reset the cache, and tweaking the CPU governor/IO settings. For some reason I seemed to get some relief after reflashing the GPS data once and then clearing cache/dalvik cache, but the issue has come back again.
I couldn't find any informative posts on it, but interesting the posts that I did find were Vibrant specific. If anyone has any ideas past turning GPS off completely please let me know. One thing I have not tried is kernels other than Semaphore, but I've heard that Semaphore is a good match with PA. Thanks!
Edit: I may be wrong because this seems odd, but even turning the GPS off in location preferences doesn't seem to be stopping the wakelock!
Have you calibrated your battery? You should always calibrate after flashing a new rom. I'm not sure about the wake locks you speak of since I have never flashed a PA rom. Someone else may have some insight on that, in the meantime definitely calibrate your battery. I recommend this app https://play.google.com/store/apps/details?id=com.nema.batterycalibration. You must be rooted, I'm assuming you are...
Sent from my SGH-T959 using Tapatalk 2
Thanks, but since this is a wakelock issue with CPU processes running amok I'm afraid battery calibration won't help but to get a few more seconds out of it before it dies in an hour :/
I do think I have found the issue for now, but it's confusing that it's related, so if anyone could shed some light on it, that'd be great. If not, hopefully others who search for it will be able to look for similar issues on their phone.
In the past on other phones, I used the CPU Editor mod that you can find on XDA. I was partial to it because I got good results with the battery saver profile, and unlike other apps on the market that kept a running process, this one was all on the command line. For some reason when I set the profile through the command line and exit the app, as long as it's enabled, the ste-gps-interface wakelock flares up and drains the battery in a matter of hours since the device cannot idle. It was a tough connection to make because I had even disabled GPS entirely and was still getting the wakelock, so I'm still not sure what the connection could be. I did notice that putting CPU Editor into sticky mode caused the device to bootloop, so I wouldn't suggest this script for PA in my experience.
I have since switched back to just using Semaphore Manager to handle CPU and governor settings to keep stuff simple, which I probably should have done in the first place Sort of ironic that trying to squeeze some more battery out of that device caused the wakelock bug. I'd ask the author of the script about it, but it seems to be kind of dead - yet another reason to move on. Smartassv2 is good enough for my purposes!
I'm now having problems with this as well. Rebooting doesn't help and neither does a data wipe. I've been on CM 10.1 nightlies for the last couple weeks and this started on Saturday. Won't allow phone to go into deep sleep. I tried the Greenify method but it doesn't seem to be working from another post... Anyone have any more info?
Welp, I think its a hardware problem unfortunately... The phone went into Safe Mode last weekend when it got damp from rain. Probably due to that.
I've tried everything... I've reverted to stock and wiped everything via odin and it still wont sleep. Time for a new phone! Been a good (almost) 3 years.
Did you try to full formatting to FAT 32 (by USB connection with a PC) both the sdcard and emmc?
selmandeli said:
Did you try to full formatting to FAT 32 (by USB connection with a PC) both the sdcard and emmc?
Click to expand...
Click to collapse
Just did and no go... Still occurring.
Possible Fix
Kind of digging up an old thread but since there was no solution posted, I thought I'd post this for anyone else having this issue and happen to stumble upon this thread.
I had the same issue with SlimBeans where ste-gps-interface was keeping my device awake. I just flashed the gps fix below and initial results show that my phone is going into deep sleep, hopefully this remains to be the case.
http://forum.xda-developers.com/showthread.php?t=2089338
Edit: So after a day's worth of testing, I can say that it worked for me.
Apparently the Insert Image function doesn't work as I expected... so here's a link to the image:
http://ctrlv.in/192705
Hey guys.
It seems like almost everyone with battery drain issues has Android OS at the top of their battery stats.
I just want to share my experiences with this particular Bug.
Maybe it will help anyone. Please share if it also helped with your problem.
I had the Android OS bug since I dropped my phone a few months ago and had the screen replaced. The guy who replaced it (official Vodafone shop employee) said that they didn't just replace the screen and that something else was also damaged (they didn't say what) so they also replaced the rest. Well, that's when the Android OS problems started. I tried many ROMs and many Kernels. Sometimes the problem went away for an hour or so, but it always came back.
Then I finally decided to use BetterBatteryStats two days ago (I really should have done this earlier, I know...). I came to the conclusion that I had some sort of the well-known "fuel_alerted" bug, since fuel_alerted was the service that kept my phone from going into Deep Sleep.
This bug should have been fixed long ago but for me it somehow still persists, even on stock JB.
It didn't only drain a lot of battery (I had 8-10h maximum without doing much), it also used up a lot of CPU time, effectively slowing down the whole system to the point that I wasn't able to use Spotify on my phone without severe stuttering.
Well. I found a solution to the fuel_alerted bug.
The procedure is: turning airplane mode on, shutting phone off, taking out battery, putting it back in after a few minutes, turning phone back on.
This solved the problem. No more Android OS draining the power. Phone goes into Deep Sleep again. Only 2% drain after an hour. Spotify runs smoothly again. Yeah!
BUT well... It seems like the problem comes back randomly for me, today I had to replace the battery 5 times...
Now I am trying to strictly follow another "rule" to keep the problem from coming back: Always waking and unlocking the phone before plugging it in or out of power. I never did this before so it could have been the cause of the bug. Now let's see how long it stays bug-free.
If it still doesn't help, I guess I have to conclude it's some kind of hardware problem, which could only be solved by Samsung...
EDIT: Nope. Problem still there. So not really a fix, but maybe still helpful for somebody.
Okay, what ROM are you on?
Sent from the little guy
gastonw said:
Okay, what ROM are you on?
Sent from the little guy
Click to expand...
Click to collapse
It's the up-to-date stock Samsung ROM I guess. See attachment for infos.
Damn, it seems like the problem just came back without me doing much. I only checked BetterBatteryStats every 30 minutes or so and recieved 1 SMS just a minute ago. Seems like the bug started 20 minutes ago, when battery was around 78%. Now it's draining battery like hell again, Spotify stutters, Deep Sleep won't work...
Guess I'll have to pull the battery again.
Since I'm pretty new to all this: What kind of information would be useful to narrow down the source of the problem?
I can provide my BetterBatteryStats screenshots and logcat/dmesg files as well as my Android Battery Stats screenshots.
Is there anything else I could post?
Yeah, screen shots of partial and kernel wakelocks.
Sent from the little guy
I just rebooted the phone, waited for a few minutes and took screenshots.
Here they are.
Okay, this is what you need to do now, drain it empty, charge it (while phone off) till 100 %. Remove the battery, wait for 90 sec or so, put it back and power on.
It's a placebo, but it might work.
Sent from the little guy
Okay, I will try and do the charging overnight. Thanks!
derSchmiddi said:
Okay, I will try and do the charging overnight. Thanks!
Click to expand...
Click to collapse
Good luck man.
Sent from the little guy
I don't know much about kernel and ROM stuff, but I was just wondering...
As far as I understand, the fuel_alerted thing turns on if the battery charge goes below a certain threshold. The old bug with it was that, when recharging, the fuel_alerted thing would sometimes still stay on, even if battery charge is no longer critical.
Could it somehow be possible that this threshold is not set to 15% for me, but something around 80% due to some horrible bug?
This would explain why it suddenly turned on at around 80% when everything was fine before.
We're trying to adjust your fuel gauge and sort of calibrating your battery.
Sent from the little guy
Okay, I did exactly what you recommended.
Everything went well for about 2.5 hours.
Then the fuel_alerted process began again, but this time only for a short while apparently.
It took about 5 minutes kernel wakelock time in a 30 minutes measurement.
Way less than usual and when I check now, it's no longer active.
So. The problem might still be there, or it might not.
Do you recommend going through a few more recharge cycles to get the gauge set properly or do you think this won't make it better?
By the way, thanks for your quick responses!
derSchmiddi said:
Okay, I did exactly what you recommended.
Everything went well for about 2.5 hours.
Then the fuel_alerted process began again, but this time only for a short while apparently.
It took about 5 minutes kernel wakelock time in a 30 minutes measurement.
Way less than usual and when I check now, it's no longer active.
So. The problem might still be there, or it might not.
Do you recommend going through a few more recharge cycles to get the gauge set properly or do you think this won't make it better?
By the way, thanks for your quick responses!
Click to expand...
Click to collapse
Not really.
Now, when it gets to 15% or so plug it in (while phone ON), get battery calibration from play store.
Run the app, when it gets to 100 % hit calibrate. Plug off the device. Turn off.
Take out the battery for 90 sec again, reinsert it and power it on.
That calibration app is another placebo but as I said before, placebos sometimes work.
Sent from the little guy
Since the battery calibration app requires Root access, I flashed a Dorimanx kernel a few hours ago. Then I did a factory reset and the battery-removal thing. 5 hours have passed now without the bug, 3h of which were without wireless access (maybe it correlates with that).
I'll now let the battery (slowly) drain below 15% and then recharge it with phone on overnight. I will use the battery calibration tomorrow and will inform you about the results later.
Thanks man!
Good to know
Sent from the little guy
I did the battery calibration. Bug is still there, no changes
Post you battery details and a couple of BBS screens.
Sent from the little guy
Okay, here are some screenshots.
From the graph you can clearly see when the bug started.
Is it normal to have >26 kworker processes running?
Something else that concerns me: >2h without or with unknown signal. The whole day I was in an inner city area where the signal should be good...
Can you conclude anything from the screenshots?
I will now try something which I also should have tried earlier
I have a spare battery (not original samsung, less capacity) which I just put into the phone.
I'll let it fully charge with phone off and then I will try if the problem persists even with the other battery.
If it doesn't, the problem might come from the battery itself...
Is this a good idea?
No it's not.
You gotta post detailed info there, we can only guess what's draining your battery.
Sent from the little guy
Okay... I posted the screenshots you asked for...
What more should I post?