I didn't have this problem for quite some time now, but now it appeared again. I am on stock sense with Android 4. Neither s-off nor root. It seems as if the media scanner server ran for some minutes and drained the battery heavily. As you can see on the second screenshot, the screen was turned off while the device remained active. Has anyone experienced this yet, and what is the reason? On top of that I had to retype my PIN. So the gprs connection must have been disconnected while the display was turned off.
That large drop looks like a reboot. I do have times occasionally when the phone is active with screen off, so nothing seems out of the ordinary there.
A reboot could have occured, which I would regard as critical already since I didn't do it myself and my phone was subsequently disconnected from cellular network for quite some time after. But still: What happened afterwards seems to be even worse: I think it must have been the 17 minutes of MediaScannerService being active that caused the massive drain.
It's a reboot, there's no way in hell you dropped 30+% in a split second
Sent from my Evo 3D CDMA using xda app-developers app
i have a similar battery issue, every time i do a reboot my battery goes down dramatically, on different roms and kernels. any way to fix or subjestion?
ink-red-ible said:
i have a similar battery issue, every time i do a reboot my battery goes down dramatically, on different roms and kernels. any way to fix or subjestion?
Click to expand...
Click to collapse
I noticed rebooting again sets you back to normal, but that's just me
I would guess the battery readout is wrong if you have it in deep sleep for a longer period of time. But for me the problem isn't the wrong reading but the cause for the high drain and the reboot. And I think it is a wakelock issue.
Dnst said:
I would guess the battery readout is wrong if you have it in deep sleep for a longer period of time. But for me the problem isn't the wrong reading but the cause for the high drain and the reboot. And I think it is a wakelock issue.
Click to expand...
Click to collapse
According to your stats its definitely not wakelock
Sent from my PG86100 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1909996 this might help if you were rooted
Ok I think it's this: http://minixforums.com/threads/andr...ia-hogging-my-cpu-50-load-all-the-times.1231/
MediaScannerService => android.process.media
Related
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
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
First and foremost I'm stock rooted and unlocked (bootloader). Got an Anker 6200 mah battery and recently cycled it for the first time with great results. Used the app battery calibration to wipe stats after charging to 100%. Unplugged the phone and turned on the tether. Noticed it went from 100% to 80% ridiculously fast. Opened up betterbatterystats and realized I had some wlan wakelocks and the top offender was mdm_hsic_mp0 kernel wakelock.
I've found a FEW references to this but not many and still not sure what exactly it is. Nothing unusual pops up in the dump log file. Sure I have a few sync partial wakes but nothing over 4 to 5 seconds. This mdm_hsic_mp0 has been kernel wakelocking for 2 hours. Now, I did turn on my hotspot tether during that time, but strange I never noticed this wakelock prior to this seemingly increased battery drain.
So my question to you all is, what is this wakelock. I've disabled almost all my syncs, no location services on, etc. Trying to eliminate every possible source and build my way back up.
I hate wakelocks about as much as I hate politicians.
Thanks for any help you can give me.
Okay left the phone on the charger all night and got her back up to 100%. Now checking BBS this mdm_hsic_pm0 wakelock is still happening. I have not used tether/hotspot what so ever and wifi is off. However I have noticed that when I go to the stock battery stats screen w/in android settings it appears my data is shutting off. Almost like a fast dormancy is taking place to conserve battery. I didn't think Verizon supported fast dormancy. But I do not see any references of "fast dormancy" in BBS.
Any ideas?
I used to have that issue on an old version of cleanrom... I turned off multi windows and that seemed to help it... Not sure if that is it though... Could be a coincidence
Sent from my SCH-I605 using Tapatalk 2
Thank you for your input.
Installed Beans build 8 and have it (the wakelock) but I've got it figured out and now it's not wakelocking when nothing is going on. Prior to flashing Beans rom however it was still wakelocking w/out what I think is the cause.
It's for the verizon mobile hotspot app. I timed how long I had it on and roughly was the same amount of time that the wakelock was occuring. Phone has no problems going into deep sleep as it's been in deep sleep for 9 hours on this cycle. So I'm content w/ what's happening now.
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?
Hey, I've been using stock 4.1.2+ExperiencedKernel for a long time, it always worked great, but a few days ago I installed an icon pack for KKLauncher, and since then my battery consumption got really bad, around 15-20% per hour when the display is off! I've tried deleting the icon pack, but it's the same, I'm even checking BetterBatteryStats for details, but it doesn't show anything suspicious, although I'm using the app for the first time, so maybe I overlooked something. I have also reflashed the rom+kernel with full wipe, but no luck. Can anyone tell me what can cause this mess, or what should I upload from BetterBatteryStats for someone to check the problem? Thanks in advance.
btw it goes to deep sleep well, so it's not an app that wakes it up constantly (I use greenify too). also the phone itself is very hot, don't know if it's just the battery or the whole thing... but the phone functions correctly.
LilProphet said:
Hey, I've been using stock 4.1.2+ExperiencedKernel for a long time, it always worked great, but a few days ago I installed an icon pack for KKLauncher, and since then my battery consumption got really bad, around 15-20% per hour when the display is off! I've tried deleting the icon pack, but it's the same, I'm even checking BetterBatteryStats for details, but it doesn't show anything suspicious, although I'm using the app for the first time, so maybe I overlooked something. I have also reflashed the rom+kernel with full wipe, but no luck. Can anyone tell me what can cause this mess, or what should I upload from BetterBatteryStats for someone to check the problem? Thanks in advance.
btw it goes to deep sleep well, so it's not an app that wakes it up constantly (I use greenify too). also the phone itself is very hot, don't know if it's just the battery or the whole thing... but the phone functions correctly.
Click to expand...
Click to collapse
If you don't have any wakelocks keeping it awake and you've reflashed the ROM, kernel and did a full wipe and the battery drain still exists... Then I'd say your battery is failing, especially if it's getting hot. My L9 never gets hot, even under heavy use.
The only other thing you could really try is flashing back to stock and see if the problem is still there... Really though, I'm pretty sure it's your battery.
xdrc45 said:
If you don't have any wakelocks keeping it awake and you've reflashed the ROM, kernel and did a full wipe and the battery drain still exists... Then I'd say your battery is failing, especially if it's getting hot. My L9 never gets hot, even under heavy use.
The only other thing you could really try is flashing back to stock and see if the problem is still there... Really though, I'm pretty sure it's your battery.
Click to expand...
Click to collapse
Hi, thanks for your answer. The problem is, the phone gets really hot on the upper side of it, near the camera. The battery never gets hot at all. Is it possible, if it's battery problem?
LilProphet said:
Hi, thanks for your answer. The problem is, the phone gets really hot on the upper side of it, near the camera. The battery never gets hot at all. Is it possible, if it's battery problem?
Click to expand...
Click to collapse
I thought you meant that the battery was getting hot. The last time I had a battery go out, it was getting hot and it was draining fast. Shortly after that it wouldn't take a charge anymore.
It is possible that it's a hardware issue. WiFi, GPS or the camera could cause it to get hot also.
You can also try and boot the phone into "Safe Mode" and run it like that for a day or two and see if the problem still exists. If it problem disappears while in Safe Mode then you have a rogue app or something that's causing the issue.
Then to narrow it down you could try downloading Wakelock Detector and see if something is keeping it awake, making it hot and drain the battery.
Monitor it with Better Battery Stats and Wake lock Detector. Post some screen shots of BBS and Wakelock Detector here too. That way we can see if something is going on.
This is one of those issues that will take a process of elimination to figure out.
xdrc45 said:
I thought you meant that the battery was getting hot. The last time I had a battery go out, it was getting hot and it was draining fast. Shortly after that it wouldn't take a charge anymore.
It is possible that it's a hardware issue. WiFi, GPS or the camera could cause it to get hot also.
You can also try and boot the phone into "Safe Mode" and run it like that for a day or two and see if the problem still exists. If it problem disappears while in Safe Mode then you have a rogue app or something that's causing the issue.
Then to narrow it down you could try downloading Wakelock Detector and see if something is keeping it awake, making it hot and drain the battery.
Monitor it with Better Battery Stats and Wake lock Detector. Post some screen shots of BBS and Wakelock Detector here too. That way we can see if something is going on.
This is one of those issues that will take a process of elimination to figure out.
Click to expand...
Click to collapse
I've been using BBS, it shows that the phone is in deep sleep in most of its off time, no app wakes it up. Also, wifi seems to lose its signal very often, even though it's strong (there wasn't any problem with that before).
I'm using the phone now without SD and SIM cards, it doesn't seem to be that hot than it used to, but charging and draining are still very weak. I'm gonna try safe mode as you suggested, and also using the phone without wifi turned on, if that is the issue. Thanks for your tips.
So, the phone cooled down after I turned off wifi, then I rebooted to safe mode, and it became hot once again, but after the media scanning, it cooled down once again. So I guess it may be the CPU? I've been trying to get a picture of the phone's circuit board with no luck, because the phone is only warm in the upper 1/3, the other parts seem to be cooled down all the time.
I'm gonna return it to T-Mobile on Monday, hopefully they won't notice the unlocked bootloader.
LilProphet said:
So, the phone cooled down after I turned off wifi, then I rebooted to safe mode, and it became hot once again, but after the media scanning, it cooled down once again. So I guess it may be the CPU? I've been trying to get a picture of the phone's circuit board with no luck, because the phone is only warm in the upper 1/3, the other parts seem to be cooled down all the time.
I'm gonna return it to T-Mobile on Monday, hopefully they won't notice the unlocked bootloader.
Click to expand...
Click to collapse
Yeah it might be the CPU. Also if it's dropping and/or scanning a lot for WiFi, then it will definitely get hot and kill the battery quickly.
I don't think that T-Mobile will notice that it's unlocked. As long as you flash back to stock ROM before taking it in, then they probably won't notice. They would have to be purposely looking for it to be unlocked.
You might want to flash back to stock anyway and see if the problem is still there... It very well could be a ROM/kernel issue causing the problem.
xdrc45 said:
Yeah it might be the CPU. Also if it's dropping and/or scanning a lot for WiFi, then it will definitely get hot and kill the battery quickly.
I don't think that T-Mobile will notice that it's unlocked. As long as you flash back to stock ROM before taking it in, then they probably won't notice. They would have to be purposely looking for it to be unlocked.
You might want to flash back to stock anyway and see if the problem is still there... It very well could be a ROM/kernel issue causing the problem.
Click to expand...
Click to collapse
I have flashed back stock one I've been using (cwm flashable), of course I will remove root and any suspicious apps. I appreciate your help.
Sent from my LG-P760 using xda premium