Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Nafiganado said:
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Click to expand...
Click to collapse
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
es0tericcha0s said:
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
Click to expand...
Click to collapse
Hi,
yes, i've used Wakelock detector app as well as its advanced colleague - BetterBatteryStats. So that's how I've found out about "s5p-ehci" wakelock. And I can see there is no other reason of phone insomnia, besides s5p-ehci.
All other apps and processes consume CPU moderately. When s5p-ehci activity is moderate - phone sleeps well. When it gets berserk and is active during several hours - phone does not sleep at all during whole this time (deep sleep is 0%), instead works on minimal frequency (300MHz), however, it's about 40% of battery draining per night.
If it's a hardware issue - I wonder who can help me with that investigation. Services do not deal with such cases, since there is no permanent problem signs. In my case the process can behave properly during a day. Then, all of a sudden, it's getting active and some its activity lasts hours! Then it's getting back to normal again. I've looked at kernel log and system log. There is a lot of various events happening there: something is going on, then device sent to sleep, then again something is going on, then wakeup, in various cases wakeup reasons are different, I was unable to find some relevant info... I would send this log to anyone who could help me to find source of the problem.
I've rolled back to Android 4.1 firmware and installed custom kernel.
Here situation is better, but what I have discovered:
phone seems not to detect when it's being plugged off from charger - no matter, USB cable from computer or wall socket wire. s5p-ehci does not go away and sucks off my battery. What only helps is manually resetting EHCI power: setting 0 in ehci_power file. As a result, something is reset, ehci power is on again, but this sucker goes away and after that everything is fine until next charge. But I need to find a root of the problem!
Going on investigation - too view info in Internet...
Related
Hi all!
I'm working on a cool University project here in Russia.
We have to make a mobile device that works for about a month without any charging.
Device should only wake up every day at 23:55 and send POST request to server to tell that "I'm doing science and I'm still alive.".
We've started with an Android device, ZTE racer and installed Cyanogen firmware.
We've made an application that:
enables AIRPLANE_MODE
asks AlarmManager to wake up at 23:55 every day
at 23:55 it disables AIRPLANE_MODE for a minute, aquires a wake lock for a minute
then sends "I'm doing science and I'm still alive." to server
and enables AIRPLANE_MODE again to save battery.
Right now we are getting 5-10 days of battery life.
I suppose that we could extremely increase battery life by:
removing some applications from firmware including "phone" and others
shutting down some services right in kernel sources. (In fact, we just need gprs and nothing else. We don't need Wifi, eccelerometer, GPS, ...)
decreasing CPU speed from application
I have couple of questions:
Is it theoretically possible to have 1 month of bettery life for an Android device? (I know that Kindle have more than 2 months of battery, so why we can't?)
Does anybody have an Android-based book reader? How long could it live in sleep mode and wifi turned off?
If device has no 3rdparty application installed, and it's sleeping in AIRPLANE_MODE... Who could possibly eat battery at that time?!!
Could you please give any kind of advice for our problem?
Thank you very much in advance!
I'd say yes it's possible to get that much battery life... Some suggestions from the top of my head:
Undervolt and/or underclock the processor (like you said), but do this from the kernel, rather than an application.
uninstall any unecessary system apps/turning off services (like you said)
Assuming your script/application is checking the system time of the phone to know when to wake, try having it just run an internal timer instead... I don't know how much battery life that would take, but I imagine that checking against its own timer would save battery vs requesting the time from the phone itself.
Assuming you haven't already, Try having so the display NEVER TURNS ON without physical input (i.e. pressing a button on the phone). The screen is a massive battery drain.
Hi everyone,
I've done very much try and erroring to find out which app is draining my battery and if it's really neccessary.
As you can see on the attachment, it looks really nice already. The only thing which drives me crazy are those long and often "Aktiv" (Awake) parts. I couldn't find any information on the SDK pages.
My Phone seems to be very often Awake while in standby. I can't understand why it has to wake up that often. Am I right, that this "Awake" means, that the cpu is running (not in sleep mode)?
Is there any way to log which software is waking the device up?
Greetings
Chris
Yep, "awake" means that cpu is running. Try Badass Battery Monitor, it has a list called AppSucker, that lists the apps by battery consumption
Thanks. That is exacly what I was looking for.
Now I'm still sure, that there is somethink wrong with the battery consumtion. As you can see on the attachment, "Android-System" takes 2 hours(!) for some stupid things.
These are the datas for one night (it was a short one ) The phone wasn't used at all. Is that normal? I mean, thats nearly 30% of the time. Okay, the total capacity loss seems okey, but the phone hast absolutly nothing to do. Except for some interrupts of from the baseband and some cronjobs maybe. But that doesn't need 2 hours.
Any suggestions what courses these long awake times? Or another way to debug this?
Thanks
Chris
Android-system, huh? Seems like you have a wrong config, or a service is keeping awake the CPU...
Sorry, I dunno other way to debug it, but you already tried to calibrate your battery? (let that your battery runs out, charge it fully and, without unplug the charger, go to Recovery >Advanced >wipe battery stats. Unplug and reboot).
Yep, that was the first ding I did.
I'm running IceColdSandwich - 7.4 - AOKP STRIPPER EDITION. Maybe this is some kind of bug.
Maybe someone have another idea how I can debug this. Nevertheless thanks for helping.
You should check to see if Sync is turned on. This will cause the phone to wake up to contact any accounts you have set up to sync... I would suggest setting sync to off unless wifi is available.
On my rom (Gingerbread base) the wifi is turned of when the screen is off, which will make sure that google will never try to sync while the phone is idle.. The downside you will have to wake the phone in order to receive emails and stuff via wifi, and if not on wifi you will have to check your email manually.
I think I found it. Badass Battery Monitor showed that "Google Backup Transport" is part of Android-System, so I removed it. I didn't use it anyway.
My phone is not crashing, I still runs smoothly. The keep-awake time shrinked to 30m during 7h (including short uses). That seems totally legit for me.
Thanks for helping
Chris
Hi.
I've got a problem with a sudden drop in the battery work time of my phone. Deep sleep not working or working for a while. I checked all applications and did not find any guilty app. Somehow, after a few days, I came to that, the deep sleep stops working after phone contact with a USB cable. It makes no difference whether it's plugged to the charger or the computer.
I checked in BetterBatteryStats, what could be wrong - it's kernel wakelock: musb_wake_lock, which is probably not allowing the handset to go sleep, so I need everytime to reboot my phone. I did factory reset, reflashed phone few times (stock ROM's, CM9) - it did not help.
Do you have any suggestions?
I have exactly the same problem with the exact same kernel process name taking up cpu with the exact same scenario too!
So, bump?
Hi,
I'm having battery issues with OPX again, first it was a faulty battery, but now it looks like the there's something wrong with the settings. The device loses about a third of it's battery overnight, but when I look at the stats I can see that WiFi is always on and the device is always awake!
I have installed naptime as well and told it to ignore sensors (not that it matters as the device is not moving overnight) and to sleep even if connected to a charger etc. No matter what I try the device is always awake.
Is there a way to find out what is keeping it awake?
When I look at usage since last full charge there's nothing unusual there, just regular apps and single digit percentage numbers.
Thanks for your help!
System version?
I'm on Android Marshmallow, using Resurrection Remix ROM.
I'm not quite sure how to use the wakelock blocker, but I just installed Wakelock detector and it shows TripAdvisor as #1 on the list. I have it blocked in notifications, but I can't find anything related to TripAdvisor in wakelock blocker.
Is there any way to prevent apps from keeping the system awake, or should I just unintall TripAdvisor completely?
Not sure if I'm on the right track, but something is keeping the system awake and I need to find out what
OS3 with google back up turned off I get zero drain. Maybe 2-3℅ max over night. Also turned off automatic updates playstore. With just those two things off dont see drain anymore might just be lucky.
Well I think I'm back on normal drain. I uninstalled TripAdvisor, not using it except when I'm on holidays. I disabled the option to keep WiFi on even during sleep.
I used wakeblocker to block all weather/facebook entries, and I have two gmail accounts, one which is use a lot and one which I don't - so I blocked all wakelocks from syncing the account I don't use often.
Battery history confirms device is now correctly going to sleep and turning off WiFi. Automatic updates are still on.
I probably blocked too much, but I don't care anymore, I have 30% more battery every morning and that's good enough for me
crótach said:
Hi,
I'm having battery issues with OPX again, first it was a faulty battery, but now it looks like the there's something wrong with the settings. The device loses about a third of it's battery overnight, but when I look at the stats I can see that WiFi is always on and the device is always awake!
I have installed naptime as well and told it to ignore sensors (not that it matters as the device is not moving overnight) and to sleep even if connected to a charger etc. No matter what I try the device is always awake.
Is there a way to find out what is keeping it awake?
When I look at usage since last full charge there's nothing unusual there, just regular apps and single digit percentage numbers.
Thanks for your help!
Click to expand...
Click to collapse
Which ROM and recovery do you use?
Hello forum,
background info:
I have a rare Pansonic Android 5.0.2 phone (DMC-CM1) with an excellent camera, what is the reason why I want to keep this device.
There are NO custom roms available and no info about key combinations on how to get into stock recovery mode. I can go there with adb of course.
I found a key combination to get into fastboot, but Wiping cache/data to reset the device apparently did nothing, even if wating for hours. It seems as well as if Panasonic tampered with the stock bootloader :/ This is why I had to send it to service (adb was not enabled before).
They reflashed the device with 4.4.4 and I installed the updates to 5.0.2 OTA. Everything seemed fine until...
present problem:
...now I have a strange battery drain. Bevor I sent it it, I had about 2-3 days usage time with average usage, a little messageing, a few fotos. I do not use the phone much.
Now I get a maximum of around 16-20 hours out of it while it is just resting on the table. It also gets warm.
what have I done so far:
- I rooted the device and installed better battery stats from the forum here. It shows around 8-10% usage per hour. Before the problem showed, I had 1-2% usage.
- I uninstalled EVERY own installed app and even booted into safe mode -> same problem
- I disabled all google app packages -> same problem, but improved it a little
When I check the battery via android settings, it is telling me that "android-system" is using >20% of the battery. In active apps I can see this app is running the fast dormancy service. When I kill this service and force the complete app to stop, it gets _a little_ better, around 5-6% usage.
I recently killed forced stop on all services that where not qualcom or seemed essential to me and disables wifi and bluetooth and over night usage dropped to <1%/h, which seemed the problem could lie somewhere with services.
However using adb shell and pulling "top" info, I dont see a process using much CPU.
What else have I noticed, which might be unrelated:
-After charging I see a 100% wakelock from qpnp-charger, that disappears only after rebooting. Might indicate that something with qualcom is "wrong".
-I set wifi to be _never_ be running in sleep mode. Better battery stats is telling me, that wifi is 100% of the time running, even if I can see the symbol for wifi is not showing and comes up a few seconds after I wake the phone
You can see, I might need help on how to identify the problem here.
Any hints, tips, advice?
Please excuse my "messy" english, it is not my native language.
regards
Stefan