Hello!
I am a long-time lurker of XDA Forums and had an issue that I could not resolve on my own. I am hoping the community can help me with this issue as it is completely driving me crazy and hurting my business life!
I have upgraded my Xoom 4G to 4.0.4, stock, locked, not rooted. Factory reset recently and have tried everything to my knowledge to fix the following issue.
The mediaserver is in a constant loop. There are no music files, pictures, anything on the device right now. Here are the few logs that have looped (I used OS monitor to find)
Code:
setup_dma
cpcap_audio_configure_power: regulator -> stanb
cpcap_audio_configure_power: regulator -> enable
tear_down_dma
setup_dma
cpcap_audio_configure_power: regulator -> stanb
cpcap_audio_configure_power: regulator -> enable
tear_down_dma
It happens every few seconds and keeps the tablet awake constantly. The battery is in a huge drain. I have no idea why this is happening. Any help would be greatly appreciated.
If anyone has any input I would be greatly appreciative...
Battery in just 4-5 hours has drained 40% with no use because of the keep awake.
After yet another battery cycle:
MediaServer is 3%
Android OS is 61%
Barely any use, screen is at 16%.
Please assist!
I decided to Flash my xoom back to 3.2.3 and do OTA updates all the way back to ICS.
I did not install any apps and went to sleep.
When I woke up I saw a 10% drain and "Android OS" was back to 80% of the battery usage and a keep awake of about 2 hours.
I know people are viewing this thread, but I am surprised no one has chimed in yet. I would appreciate the help.
Hi,
I am half watching the thread as am having a similar issue. I have an Asus Transformer and a HTC One X. On 11th June, my phone was roasting hot and had eaten all of the battery away. That was the first time and it has done it most days since. The Transformer has also done similar things since I noticed it on the phone, so am assuming the two are linked.
One Saturday 16th June, I factory reset the One X and re-installed the apps. In Sunday I re-imported the files from Dropbox. Was fine, like 2% battery use from the whole of Sunday. On Monday, issue returned. Only thing I did different was use it as a USB drive. AM therefore thinking those two are connected, but I don't know how to trace the issue.
I've been playing with LogCat and OS Monitor (following your post), but any advice on a way I can dig around to find what it's actually getting up to would be appreciated.
Wish I could help you tbh.....
Cavey
I am also having same issue with HTC SENSATION, AOKP ROM, Android 4.0.4
I went through this with my sensation as well. It was caused by an odd MP3 on my sdcard. I suggest formatting sdcard and just keeping the bare necessities.
Any details on how you found the "odd MP3." I know this is the cause for me. I needs to know what to do to log or query mediaserver to see what its grinding on.
Related
Hey all
Just wondering if anyone has seen this... I have a touchpad32gb, UK. When I first received it I charged it overnight..
Disabled logging, installed preware and installed the "recommended" tweaks..
Then installed Uberkernel and ran it at 1.5Ghz..
Now Im currently seeing that it seams to run down to 47% and the BOOM 0%..
Bad battery????
I've just restored the rom using webosdoctor and its syncing up the apps...For now Im only going to disable logging.. No preware no Uberkernel.. but whilst its charging and I run another test I thought Id ask people and see if anyone else has seen this....
Angelo
I just had the same thing happen, it went from sitting on 100% for a rather long time, then it had gone down to the low 90's, then suddenly "About to power off" at 0% remaining.
From a full charge to 0% in 2 days of mostly sitting there doing nothing with the screen off isn't promising.
It's charging again now on the touchstone, currently on 5%, hope it's not a stuffed battery
Its not the battery. It's the battery calibration file which is messed up. Hence, the Touchpad is confused about the battery status and thinks its 0% even when it may not be. Charge it a good while even when it reaches 100% and see if it fixes itself over a period of a few charges.
On Android, you can go ahead and do a battery calibration which deletes the file and causes the system to make a new one which is correct but idk where the file would be on WebOS.
It's not your battery though, be sure of that
battery woes
Hi Alienz,
thanks for this comment..
I've reinstalled webos, charged it overnight and its currently sitting next to me discharging nice and slowly, 100% brightness, doing slideshows.. currently at 58%
Lets see what happens at 48% ...
alas, it died again, this time at 50%.... :-(
Any other suggestions? Im gonna call HP now and see if they have any other suggestions
Trade it in for a Joggler powered off a couple of car batteries
Unfortunately I can't help you cause I only have Android experience on fixing this.
However, I suggest you go over to the Palm forums (not on XDA even) or check the CM7 Touchpad development team. They have messed with the operating system enough to be able to tell you where that file may be located and/or how to fix it.
@dwl99 : haha, yeah i suppose I could swap it for a joggler or two! (not!)
@}{Alienz}{ , thanks, but I called HP and they're collecting it for repair... ;-) if its a OS issue I would have thought reimaging using webos would have solved it.....
Ill find out next week!
Hey all,
Just to let everyone know , the touchpads' back and the battery works fine now..
However someone at precentral has pointed out that some preware patches dont get deleted if you do a webos doctor.. I wonder if it was a preware corruption??
Hi everyone,
I am a proud and extremely satisfied owner of a GS3 for two months now. However, I have a very annoying and obtrusive problem I can't seem to be able to fix.
Every time after I charge the phone, I got the habit to always check in betterbatterystats for a partial wakelock, named *overflow* which gets stuck running each and every time after fully charging the phone. I tried stopping various apps with absolutely no success in cutting the *overflow* wakelock. The only way that I know of stopping overflow is by rebooting the phone and after that partial wakelock usage goes back to normal. In case I don't restart the phone and leave the *overflow* process as is the battery will drain in about 9 hours to about 20%
My FW version is XXLFB and this issue started occurring after I upgraded from XXLF2 to this version, before the upgrade I still had this problem, but only once in several charge cycles.
My phone is completely stock and unrooted.
Guys, I would really appreciate any assistance on this, so please help me to figure this out, I have a gut feeling that this is something easily fixable
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
Hello everyone,
I've been following these forums every now and then and was very helpful when I encounter some minor problems so far.
But lately I start having a very strange problem on my mom's phone which is a Samsung Galaxy Win (i8552- stock rom- android 4.1.2) and couldn't really find a decent solution or a good explanation so far. So I decided to ask you guys.
The problem is phone is having a bit poor bettery life overall, especially while in idle. I found out most of the times it is losing 2-3% battery per hour while idling (i.e overnight). Sometimes it's slightly more 1% per hour and sometimes between 0.5-1% (which sounds more normal).
While in idle usually Androis OS seems eating up the battery around 50-60%. I disabled most of the notifications, most of the sync options (especially google ones), all kinds of screen sounds, facebook update intervals, uninstalled Avast and also disabled the location access. But these changes didn't really give a noticable difference. Battery drain inconsistency was still there.
After I noticed this strange battery drain I decided to digging it up a bit more and installed GSM Battery and wakelock detector.
Firs that I noticed in GSM battery is that the phone is awake for like 1.5 hours out of 7-8 hours of overnight idling. And Android OS kernel seemed responsible for this. But couldn't really get more clues.
Then I found more clues on the culprit in Wakelock Detector under "kernel wakelocks" tab. Which is vbus_wake_lock wakelock.
WD shows vbus_wake_lock is awake for almost an hour after the last charge, which was 7 hours ago.
After I found this I googled around a bit but couldn't really found a useful explanation except it might be caused by an apple charger. But I know that mom's using the original samsung charger.
I tried rebooting to see if it helps. It's been almost 4 hours now, phone lost around 2% battery which seems ok-ish but the vbus_wake_lock is still there with 25 minutes of awake.
So any idea. What should I do to hunt this wakelock down?
I don't really want to make her worried about her phone though, she seems happy with it, since she is playing some games and charging it every day so not really having a battery issues. But I know that there's something wrong here and I want to fix it.
So I desperately need your helps guys.
Thanks a lot.
Sorry for my English btw, as it's not my native.
Best,
supertrampp said:
Hello everyone,
I've been following these forums every now and then and was very helpful when I encounter some minor problems so far.
But lately I start having a very strange problem on my mom's phone which is a Samsung Galaxy Win (i8552- stock rom- android 4.1.2) and couldn't really find a decent solution or a good explanation so far. So I decided to ask you guys.
The problem is phone is having a bit poor bettery life overall, especially while in idle. I found out most of the times it is losing 2-3% battery per hour while idling (i.e overnight). Sometimes it's slightly more 1% per hour and sometimes between 0.5-1% (which sounds more normal).
While in idle usually Androis OS seems eating up the battery around 50-60%. I disabled most of the notifications, most of the sync options (especially google ones), all kinds of screen sounds, facebook update intervals, uninstalled Avast and also disabled the location access. But these changes didn't really give a noticable difference. Battery drain inconsistency was still there.
After I noticed this strange battery drain I decided to digging it up a bit more and installed GSM Battery and wakelock detector.
Firs that I noticed in GSM battery is that the phone is awake for like 1.5 hours out of 7-8 hours of overnight idling. And Android OS kernel seemed responsible for this. But couldn't really get more clues.
Then I found more clues on the culprit in Wakelock Detector under "kernel wakelocks" tab. Which is vbus_wake_lock wakelock.
WD shows vbus_wake_lock is awake for almost an hour after the last charge, which was 7 hours ago.
After I found this I googled around a bit but couldn't really found a useful explanation except it might be caused by an apple charger. But I know that mom's using the original samsung charger.
I tried rebooting to see if it helps. It's been almost 4 hours now, phone lost around 2% battery which seems ok-ish but the vbus_wake_lock is still there with 25 minutes of awake.
So any idea. What should I do to hunt this wakelock down?
I don't really want to make her worried about her phone though, she seems happy with it, since she is playing some games and charging it every day so not really having a battery issues. But I know that there's something wrong here and I want to fix it.
So I desperately need your helps guys.
Thanks a lot.
Sorry for my English btw, as it's not my native.
Best,
Click to expand...
Click to collapse
Any ideas? Anyone?
About a week and a half ago, my battery went from draining ten percent in a typical day (hour to an hour and a balf of constant use, browsing Facebook, web, email - if I really went ham I might go down in the 80s) to easily closing in on the 50s if not more.
I've tried several factory resets, gotten the lollipop upgrade that just hit, removed apps, upgraded apps - nothing. I'm on stock and haven't had this phone more than a month. Android System is typically the worst offender for battery usage according to the settings monitor.
Please help. I was so impressed and now I'm at a loss.
If you've done factory resets, then I would say, factory reset again and stay on stock apps. Don't install anything else. Monitor what happens with your battery life. My guess is, if you have installed other apps since doing the factory reset, it's an app that is misbehaving, even though you see android system being the main culprit. More than likely, it could be an app that isn't releasing resources correctly or hasn't been updated to run correctly with LP. That usually points to a sign of improper programming, or they haven't update their app yet to perform correctly under LP.
If things are running fine on stock, start adding your apps back one by one. Install one app, leave it for a few days and see what happens. if battery life stays the same, then move onto the next app. Hopefully, you'll find the app that's giving you issues.
If even with just stock apps you are having the issue, then it might be a hardware issue, possibly even battery. But, if it's been working fine before the LP update, I highly doubt that. My best guess is it's a misbehaving app.
I'm still having problems with nothing else but stock apps, unfortunately. The problem started shortly before the update - does that support that it's more hardware or more software related? The phone is still fairly new and though I know that doesn't rule out a bad battery, still kinda hoping I don't have to deal with Verizon and getting a replacement.
Talked to Verizon, they said "we checked, battery's fine." So... guess its not the battery? They said it "could take a month to normalize after the update."
I would buy a replacement battery and install it, see if that helps. They are cheap and it's good to have one anyway. The Ankers come in a 2-pack with a nice universal wall charger.
Verizon is not even bothering to check really, are they ? Did they even loan you a replacement to prove to you it's not a bad battery ? Doubt it. Do it yourself.
It really sounds like you are having excessive battery drain due to a wakelock problem like with Google's update service. Check around here for threads about how to diagnose and mitigate that.
Sent from my VS985 4G using Tapatalk
I didn't expect Verizon to help, but they definitely impressed with just how little they offered. I'm spending today with Wi-Fi and 4G off, unless browsing, for which I turn the latter on. In my half hour lunch I've noticed much, much better battery usage. Thoughts?
Edit: change of location seems to drain it quicker (school vs McDonalds parking lot - former worse than the latter). Signal was three bars in each, though.
I've looked a bit ino wakelocks but will read up on it more tonight. Problem I've found is how many detectors require root access, and I'm not real interested in rooting.
I just got my G3 last night and rooted it and did a few things to minimize battery drain and today, after almost 12 hours of light to moderate use my battery is still sitting at 81%.
Pretty sure there's a memory leak on stock vs985 lollipop... Or at least from what I had read and experienced