I left my Note overnight to test the battery drain and lost 40%. I used CPU spy to see what was happening and the phone never really went into Deep Sleep. Android OS was the biggest battery drain.
What's the best way/app to see what is keeping my phone from going into deep sleep? I am not rooted.
Please try a search you will get lots of good answers.
http://forum.xda-developers.com/showthread.php?t=1516565
And get Better Battery Stats to find out what is triggering you out of sleep if the above thread does not help.
Sent from my SGH-I897 using XDA
jpeg42 said:
Please try a search you will get lots of good answers.
http://forum.xda-developers.com/showthread.php?t=1516565
And get Better Battery Stats to find out what is triggering you out of sleep if the above thread does not help.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I don't need to be told to do a search. That's the first thing I do before I post a thread. The subject of that particular thread didn't seem to apply.
factory reset should take care of andriod os eating battery more then screen.dont install any app for few hours.only install cpu spy.
Thanks for the suggestion, but I'd rather not have to do a factory reset every time a rogue app is draining my battery. Reinstalling everything all over again is a pain (not rooted, so Titanium backup is not an option) and that's like telling a user to reinstall Windows every time they see a little performance degredation.
I'm pretty sure there has to be a better way. I'll try betterbatterystats and see if it can help me narrow down the problem.
yeh i have an unrelated problem, will resetting device fixes it, but definately not a viable solution
but on topic in better battery stats look under 'partial wake locks',and see what programs are listed first (and the time spent on the apps)
that should normally tell you whats making the phone not got to sleep
u not gone find anything with battery stats.one of ur app is causing this issue.
u can give battery stats a try.when u.have a virus in windows, dont have have to do full recovery instead buying a virus program and trying to fix it.
greyhulk please try that solution Jpeg42 linked to.
Thursday I was down to 30% when I left work(10 hours). Friday I turned on the screen before unplugging and I was at 25% with 2 hours of screen on time and 21 hours since I unplugged.
Unplugging the phone with the screen off seems to prevent deep sleep. Give it a try.
If all else fails, it might be the battery itself. Hardware issue.
-On another NOTE, Samsung goes 5.3"
mintu123 said:
u not gone find anything with battery stats.one of ur app is causing this issue.
u can give battery stats a try.when u.have a virus in windows, dont have have to do full recovery instead buying a virus program and trying to fix it.
Click to expand...
Click to collapse
Your post is virtually incoherent, however, I will say you seem to be saying BetterBatteryStats won't help, and it most certainly will. What there is no need for is a factory reset, that's like nuking a planet to kill a flea.
Pops_G said:
greyhulk please try that solution Jpeg42 linked to.
Thursday I was down to 30% when I left work(10 hours). Friday I turned on the screen before unplugging and I was at 25% with 2 hours of screen on time and 21 hours since I unplugged.
Unplugging the phone with the screen off seems to prevent deep sleep. Give it a try.
Click to expand...
Click to collapse
Yeah, reading the thread over, that's exactly what I did last night: Took it off the charger with the screen off. I skipped over that thread originally because the title lead me to believe that it had to do with battery drain while plugged in.
I'll give it another test tonight and see if that makes a difference.
I just wanted to post my experiences with deep sleep.
I was getting some pretty bad drain, and I couldn't figure out why. Thanks to the search engine and running into this thread, I tried what you all tried here.
I am running Launcher Pro, and I wasn't going to deep sleep at all. Did the trick posted, even rebooted without it plugged in and it still wasn't sleeping at all.
I cleared the defaults and went back to the default launcher. It went to deep sleep just fine. I cleared the defaults again, then set the launcher back to launcher pro. It is now deep sleeping with the launcher pro as the default.
I then put the phone on the charger, woke it up, unlocked it and unplugged it. Its still deep sleeping. Really weird how it acted, and I figured for everyone else's sake in case they run into that issue again, it could be your launcher that is causing the issue.
A reboot with the phone, after the launcher switch, as the launcher pro as the default, resulted in no deep sleep. Launching the stock launcher while LauncherPro is still the default launcher resulted in no deep sleep.
After a reboot, with no default launcher, launching the stock launcher resulted in, it does not deep sleep.
After a reboot with no default launcher, launching LauncherPro, no deep sleep.
Some really goofy stuff going on...
I am using the overclock kernel but I am not overclocking. I installed it to lower the cpu to 192mhz instead of 384mhz.
I noticed that my phone (Lenovo P700i) barely goes into deep sleep. At the minimum, it always runs at 250 mhz.
Is this considered a deep sleep problem even though BetterBatteryStats shows that there don't seem to be any significant wakelocks?
there's two build props that will make your device enter sleep instanly...If you understand how to edit them..you may want to search for deep sleep build prop tweaks..hope this helps..
Does this app can fix the issue: http://forum.xda-developers.com/showthread.php?t=2030696 ?
Related
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...
I'm having issue with my 4g lte. Happens randomly - my phone just discharges. Last night I had it on charger for up to 85% and I woke up this morning my phone was dead. No wifi or bluetooth on. No new apps installed. I cant find a pattern why and when is doing that. Any ideas ? is there some kind of app that can record what is happening to the sys and battery so I can review later on ?
Yes install BetterBatteryStats (available for free on the devs thread). It will show you what is keeping the phone awake since that is probably the cause of your battery being drained. Install it and let it standby for a while without touching. Update the thread with the statistics BBS gives you.
Also you should try posting questions in the Q&A forum next time
thanks and sorry
which on should I post ?
other, partial wakelocks, kernel wakelock, alarms or process ?
i have that app.. i just dont know like whats bad and whats not?? my battery seems ok but i just wish i knew how to use the app..
With no wifi on you are going to drain quick if you have spotty service. You can even go to settings, battery, and then see what is using your battery.
I also have this problem somedays I will have great battery life around 20 hours and other times I get around 12 hours, today for example my phone been of charger 2 hour about ten min of screen time and battery already at 80 percent, I do have better battery stats and have never seen a wakelock or anything like that.
so i should go under partial wakelocks and what do i look for>>??? i have mad stuff under it.. what do i look for >???
evo401 said:
so i should go under partial wakelocks and what do i look for>>??? i have mad stuff under it.. what do i look for >??? :confused
I am not an expert on the app it I believe you look for anything that says wakelock, well atleast that's what I do from my understanding a wakelock means the phone was woken up by a certain app someone please correct me if I am wrong here
Click to expand...
Click to collapse
I have had similar issues, even went to bed before at 50% to wake up turned off from dead battery and all my data syncing stops at night based on schedules I have set.
Few things I have noticed.
I have plugged my phone in a few times, battery light turn orange like it's charging but the battery icon not move (as if is not charging) and when I went at power it says (discharging) yet when not plugged in it just says (not plugged in) and when charging it says (charging). A simple unplug and plug fixes it but odd that it randomly happens. I hope is sw bug and not something hardware on my phone.
Also once got my phone in diag mode by mistake playing with the ## menus. When that is on the battery was about 50% of what it normally is and you never know it's on unless you see the screen on reboot. Turned it back off and all was better again.
Still have the random days it drains fast though and the random times it won't charge though light is orange.
On the right days though, it is great. I can get over a day on my normal use and that is with 5 email accounts (some push exchange and some imap) and some texting and web and light browsing.
I had the same issue for a while, I finally found out what is was. It was "Sync Internet". It was constantly running. Go to Settings >> Accounts & Sync >> Your Google Account(s) and see if "Sync Internet" has the sync icon next to the checkbox. It never stopped syncing and so it was draining my battery. I unchecked it and battery is working like a champ!
The *whole* internet??
vandon1 said:
The *whole* internet??
Click to expand...
Click to collapse
Lol !
The only battery issues I've had with mine are when I disabled a ton of apps.
Sorry I posted that and then went to bed here's what you do:
Set it to detect 'since unplugged' and then let the phone idle for a nice amount of time to get good data. Then check under kernel wake locks and take a screen shot then just switch to partial ones and do the same. I'll look at them and try to help. I'm not an expert on it but it did help me back when I had a similar issue with my 3D.
Sent from my Evo 4G LTE
Hello,
I wanted to get your guys opinion as I believe my phone may have turned defective and I really don't want to go down the Warranty Route as I'll loose the phone for weeks. And willing to try anything suggested.
So here's the problem:
Battery Draining at very high rates. On stock battery, I am draining about 12% an hour, after 6 or so hours my 15% battery capacity left warning turns on. I figured it was the battery, so bought a double capacity 4200mAh Hyperion Battery. Now my battery drain is at 6% an hour (which is equivalent to the factory battery considering the double capacity).
I am currently on XXELKC 4.1.2 Stock ROM. When I first noticed the problem, I was on 4.1.1. Figured I would ODIN, Wipe all cache's, and start clean. This has made no affect on battery life.
Here's what I've tried:
- 4.1.1, 4.1.2 Stock ROMs from Wipe - High Drain
- Airplane Mode with Location Services Disabled - High Drain, but 4.5% an Hour instead of 6% an Hour.
- Disabled all Samsung Apps - seemed to have little impact
- Disabling Google Now has made zero impact on battery life.
- 4.1.1 BBS revealed nothing - may need to try again on 4.1.2
Any ideas? Or is this sounding like the phone? Is it possible after a wipe the phone, when I re-enter my Google Credentials it is restoring some data which is defunct and causing high drain?
Note: Screen shots are with the double capacity battery taken right after a clean Odin upgrade to 4.1.2. Only ran Android Activation and thats it.
It looks like your phone isnt going to sleep properly. Try a custom rom/kernel.
Have you done a full whipe ?? If not, do so, and don't forget to make a back up first. It worked for me !
Sent from my GT-I9300 using xda premium
I had similar issues, I factory reset worked, and I also download rescan media root app to disable the media scanner which was my main battery killer.
WHen you do the factory reset make sure your phone is connected to the internet, so it will prompt google to store the apps you have and remote install when you sign back into the phone.
I have performed a full wipe but that had minor impact on battery life but I wounder if the Google Restore possibly restored an invalid setting. I will try this again without entering my credentials and see if there is a link with a restored setting. I will have to give the rescan media app a try as well.
5kops said:
It looks like your phone isnt going to sleep properly. Try a custom rom/kernel.
Click to expand...
Click to collapse
Any specific kernel in mind. From what I've been reading no kernel seemed to stand up to magically solve battery issues without voltage drop or cutting services like Google now from the rom.
use better battery stats app to determine what is causing those wake locks.
Sent from my GT-I9300 using Tapatalk 2
beaver2233 said:
use better battery stats app to determine what is causing those wake locks.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I have attached a run with BBS for 1 hour. Nothing is really standing out. The phone was in deep sleep for all but 2 minutes. I did have Google Now and Location Services Disabled as that was eating away an impressive 10 minutes / hour from deep sleep. But my battery life only increased from 6% an hour to 4.5% an hour. An improvement but weak IMO considering the larger battery.
Results from BBS is attached.
I once had that kinda issue too
What I did was Factory Reset and that did the trick for me
How about trying the app CPU sleeper?
Sent from my GT-I9300 using xda premium
I've had this issue before on the i9100 Galaxy S II, where it didn't seem to matter what I did, it chewed battery just as soon as I put my Google account back onto the handset. I believed it was caused by the Samsung calendar bug. So absolutely; try it without putting your Google account onto the device.
Also, your WiFi signal looks low, although this has less of a difference compared to having low mobile coverage...
DaRacerz said:
I have attached a run with BBS for 1 hour. Nothing is really standing out. The phone was in deep sleep for all but 2 minutes. I did have Google Now and Location Services Disabled as that was eating away an impressive 10 minutes / hour from deep sleep. But my battery life only increased from 6% an hour to 4.5% an hour. An improvement but weak IMO considering the larger battery.
Results from BBS is attached.
Click to expand...
Click to collapse
your first post has a huge amount of wakeocks that arent going to be reflected with an hours run on BBS. If i were you id charge it to 100%, unplug just before going to bed and then show us the BBS log in the morning so people can see whats happening over an 7-8 hour peroid
DaRacerz said:
Hello,
I wanted to get your guys opinion as I believe my phone may have turned defective and I really don't want to go down the Warranty Route as I'll loose the phone for weeks. And willing to try anything suggested.
...
Click to expand...
Click to collapse
Have you tried flashing a custom ROM?
DaRacerz said:
I have attached a run with BBS for 1 hour. Nothing is really standing out. The phone was in deep sleep for all but 2 minutes. I did have Google Now and Location Services Disabled as that was eating away an impressive 10 minutes / hour from deep sleep. But my battery life only increased from 6% an hour to 4.5% an hour. An improvement but weak IMO considering the larger battery.
Results from BBS is attached.
Click to expand...
Click to collapse
It looks like the same problem I was having. Your WIFI is always on.
http://forum.xda-developers.com/showthread.php?p=35813539
Also leaving your Bluetooth On all the time is going to drain the battery pretty quickly.
pinguy1982 said:
It looks like the same problem I was having. Your WIFI is always on.
http://forum.xda-developers.com/showthread.php?p=35813539
Also leaving your Bluetooth On all the time is going to drain the battery pretty quickly.
Click to expand...
Click to collapse
its not wifi always on, my wifi is always on too and i lose 2% over an 8 hour standby period.
Its more what apps are using the wifi connection and waking the phone up, thats what the op needs to look into
I have to say ive had pretty bad battery lately aswell. If op doesnt mind I might post my bbs log tomorrow sometime
tapp'd on my S3
MRDOCA said:
I have to say ive had pretty bad battery lately aswell. If op doesnt mind I might post my bbs log tomorrow sometime
tapp'd on my S3
Click to expand...
Click to collapse
More information can't hurt. Post in and Maybee there is a correlation.
OK. So I went ahead with your suggestions and did the following
Factory Wipe again from Settings Menu
Went back to factory Samsung battery for consistency in reports to other users
Took out both my sim and sdcard to eliminate those possibilities
Put into airplane mode
Disabled a bunch of apps (ss on next post)
Still bismal results but better than before. 7 percent an hour drain. Attached all the files. Ideas? Google says phone is awake but bbs doesn't seem to shed any clues for me...
And here are the disabled and installed apps
your phone isnt going to sleep at all....something is keeping it awake..try a stock rom ( any will do) with full wipe. Dont restore anything with titanium backup. Disable auto sync on everything. Set wifi sleep policy to always. See if the problem persists.
5kops said:
your phone isnt going to sleep at all....something is keeping it awake..try a stock rom ( any will do) with full wipe. Dont restore anything with titanium backup. Disable auto sync on everything. Set wifi sleep policy to always. See if the problem persists.
Click to expand...
Click to collapse
That last run posted was stock 4.1.2 XXELKC firmware and Factory Wipe from Settings Menu. I also performed Wipe and Cache Wipe in the Bootloader (Power Up + Center + Power). All I did was install bbs and never put in Google or Samsung credentials and disabled some stock apps from running.
If your not referring to factory Wipe, can you please explain further? Thanks.
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?