On several occasions, after applying bstats.zip when at 100%, my phone shows only 60% battery afterr applying the zip.
Is this normal?
Also, as you might guess, having some general battery problems:
Rapid loss of battery reserve
Phone running "hot" when no visible programs are running
Difficulty getting phone back to 100%, even after several hours of charging.
Are there any suggestions on utilities to show
1) whether battery is holding a charge,
2) what programs are using up battery?
Badger51 said:
On several occasions, after applying bstats.zip when at 100%, my phone shows only 60% battery afterr applying the zip.
Is this normal?
Also, as you might guess, having some general battery problems:
Rapid loss of battery reserve
Phone running "hot" when no visible programs are running
Difficulty getting phone back to 100%, even after several hours of charging.
Are there any suggestions on utilities to show
1) whether battery is holding a charge,
2) what programs are using up battery?
Click to expand...
Click to collapse
This is definitely not normal. There are several things to try:
1)in terminal emulator, type"su" then hit return to get superuser access, then run the command "dumpsys power". near the bottom is a command "mLocks.size=0"
This will list any wake locks, which drain battery by preventing the phone from going into deep sleep. (In the example, 0 means no wake locks)
2)try a different kernel, maybe an undervolted one. I recommend imnuts' 50uv pbj kernel found here:
https://sites.google.com/a/imnuts.net/android/kernels
(try the 4th one down in the list)
thanks
will give that a try...
wake locks
The following is captured from the emulator screen, there is more above it, but this appeared to be the section on wake locks:
mLocks.size=3:
PARTIAL_WAKE_LOCK 'MAIL_SERVICE' activated (minState=0, uid=10212, pid=2731)
PARTIAL_WAKE_LOCK 'CoreReceiver getWakeLock' activated (minState=0, uid=10092, pid=2731)
PARTIAL_WAKE_LOCK 'NetworkLocation Check Location' activated (minState=0, uid=1000, pid=2731)
Not sure if it's good news or bad news..
Working to install the other kernel, as well.
It looks like you might be using an email client other than the stock one that is keeping your phone awake. If so, try uninstalling or disabling it for 24 hours and use your phone.
Related
Being fed up with the random wakelocks that Dialer produced on my Gingerbread P500, I spent a while searching for the cause. It turned out to be DataTracker-FD (found out using the amazing BetterBatteryStats app - http://www.cri.ch/sven/doku.php/computing/android/betterbatterystats ), which deals with Fast Dormancy (http://www.computerworld.com/s/article/9191759/Fast_dormancy_to_improve_smartphone_networking_and_battery_performance_ ).
Now, in theory, Fast Dormancy should be a great feature! But, if your network does not support it, DataTracker-FD will still drain a lot of battery through the wakelock. The SGSII secret code for deactivating it doesn't work on the P500, and neither does the nwk_info.db method. Luckily, you can deactivate (or change its timeout) through the LG hidden menu...
1. Dial 3845#*500#.
2. Go to Modem Setting > PDP Setting > [0] Set Fast Dormancy
3. Select your desired timeout (or "Disabled"). You should now be done! (will look at Battery Usage in a little bit, to see if a reboot/Dialer FC is also needed)
Optional step 4. If you still see no difference, set your desired timeout (or "Disabled") a few more times.
Hope it helps.
/* Edit: It doesn't seem to help, we might be back to square one. Does anyone have any idea on how to completely disable Fast Dormancy? We might need a dev to look at the source code of Dialer and make some modifications... Right now, if your phone stays awake after using Data, the only current workaround is FCing Dialer from Applications. */
EDIT 2: A SECOND TEST, USING THE ABOVE METHOD TO DISABLE FAST DORMANCY, YIELDS POSITIVE RESULTS! THE WAKELOCK IS NOT THERE ANYMORE, EVEN AFTER SEVERAL RECONNECTIONS TO HSDPA!
It needs way more testing though, I will reconnect to data and leave the phone idle (screen off), then see what happens, and I will reboot the phone to see if the setting persists.
EDIT 3: Yes, the setting persists, and the wakelock is still not running! The final test will be done after it has completely charged, because there still is a small possibility that the wakelock is so far not active just because the phone was charging.
Edit 4: Straight after unplugging the phone, DataTracker-FD started running, without being connected to HSDPA (I was in a phonecall). In 17 minutes (of mostly talking on the phone) it drained 1% of the battery - so, it should last for about 29 hours with the same usage. Now I have started HSDPA and left the phone idle for 10 minutes, to see how much it drains and how much it drains after I turn data off. It just might be that, while the phone is still awake, it doesn't drain a large amount of battery. If it actually still drains a lot, this tweak definitely only /seems/ to work while charging (maybe BetterBatteryStats was reporting false data or FD just doesnt' work when charging).
Edit 5: Here's a pleasant surprise. Right after connecting to HSDPA and putting the phone to sleep, the Awake bar in Battery Usage faded out. In 5 minutes of idling with data activated, the phone drained another 1% battery - not sure how well that is, since it amounts to 8 hours of data on a full charge, but it's better than 12 hours of idling with no data on a full charge. Currently repeating the test. Just got an email on Yahoo pushed, I'll get to see the influence on awake time of that as well.
Edit 6: After 10 minutes of idling with data ON, a bit over 1% of the battery is gone. This is a fantastic value, and the Awake bar is only dotted in this period of time. DataTracker-FD seems to be running a bit in the background during the data connection, but stopped once I turned it off. It might just be me, though, because aLogCat still can't find any entries for Fast Dormancy. Now leaving the phone idle with no data for a while to look at the evolution of Awake time.
Edit 7: After about 45 minutes of complete idling, the battery went down 2%. This would mean the battery would last for about a day and a half, which is meh, considering I OC'd the phone to 730 and don't really use a task manager.
The conclusion: YES, disabling Fast Dormancy does work using the above method, and it does help battery life!
Edit 8: After another unrelated reboot, DataTracker-FD is once again awake after using data, but this time it draws significantly less battery. The Battery Usage graph shows no difference between sleep times and awake-because-of-FD times.
Edit 9: During the night, the phone drained 30% battery, once again because of some random action of DataTracker-FD. This is still not a definite fix.
"Connection problem or invalid MMI code" when I dial that number..
I remember that long ago I dialed the number and everything was fine.
Well you shouldn't literally call it, just type it in Dialer and it should open the hidden menu.
metalboy94 said:
Well you shouldn't literally call it, just type it in Dialer and it should open the hidden menu.
Click to expand...
Click to collapse
When I just type it in dialer, nothing happens.
I see. It might not work on CM.
Updated the OP a couple of times, you might want to read it.
Considering I am still on Froyo v2.2.2, could this be of interest for me too? There's no abnormal battery drain on my phone, but if I can improve the battery life by tweaking this setting, I'd gladly do it.
masteryx said:
Considering I am still on Froyo v2.2.2, could this be of interest for me too? There's no abnormal battery drain on my phone, but if I can improve the battery life by tweaking this setting, I'd gladly do it.
Click to expand...
Click to collapse
I didn't have such problems on Froyo either. It MIGHT help, but as you can see from the numerous edits to the OP, it's not a clear win yet.
So it need to be disabled twice to stop working?
I've been looking for this service since using that Battery App but theres not much information of that in the web.
I'm not sure just how many times, but it took about 3-4 times for me until I was completely sure the wakelock stopped running and the phone went into deep sleep each time I locked it.
Yeah I think I got it doing it twice, FC phone and rebooting, btw maybe you can check system/etc/flex/flex.db and flex.xml there are fast dormancy settings there
@metalboy94 I mailed LG regarding Fast Dormancy and the reply i got was that P500 does not support fast dormancy. My phone does not switch from H to 3G. I tried enabling it many times using secret menu but it does not work.
I asked him if GB ROM/Baseband supports fast dormancy, he replied saying GB hasn't been released for India
Roqu3 said:
Yeah I think I got it doing it twice, FC phone and rebooting, btw maybe you can check system/etc/flex/flex.db and flex.xml there are fast dormancy settings there
Click to expand...
Click to collapse
There are? Thanks a bunch, gonna try those methods as well!
@atulalvenkar: Well, it still draws power from the battery, so at least they could have done something to the Dialer if it's not supported at all.
Edited the OP once again.
Are you guys checking on GB or Froyo ROM ? I can't see flex.db or flex.xml in froyo ? Stock or CM7
atulalvenkar said:
Are you guys checking on GB or Froyo ROM ? I can't see flex.db or flex.xml in froyo ? Stock or CM7
Click to expand...
Click to collapse
Stock GB. I found it, but you have to fill in the info for your operator if it's not on that list. Guess which is my situation.
metalboy94 said:
Stock GB. I found it, but you have to fill in the info for your operator if it's not on that list. Guess which is my situation.
Click to expand...
Click to collapse
Yeah my operator isn´t there also (I´m on a custom V20g ROM and I´m not from Romania) but i got the flex files from the Froyo stock so im going to try using that information to replace one of the V20g operators.
Also tried putting the Froyo ones on GB but get a lot of FC
Updated the OP again...
I tried to change the FD settings in the hidden menu, but the setting does not "stick", so I don't know if it's actually OFF or not.
However, I found that DataTracker-FD only keeps the phone awake when Wifi is on. If I'm always on 3G, FD seems to work and keep the phone asleep. Overnight with wifi off and 3G on, it only drained 2% battery.
I'm on official GB2.3.3 with PaoloM's kernel v5.
Strange.
hey maybe let´s try this:
Code:
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,
have to put that on the build.prop then restart, the values must be changed to your carriers code, you can get that code from adb typing
Code:
adb shell
getprop gsm.operator.numeric
Then the system should show the number
tsuda said:
I tried to change the FD settings in the hidden menu, but the setting does not "stick", so I don't know if it's actually OFF or not.
However, I found that DataTracker-FD only keeps the phone awake when Wifi is on. If I'm always on 3G, FD seems to work and keep the phone asleep. Overnight with wifi off and 3G on, it only drained 2% battery.
I'm on official GB2.3.3 with PaoloM's kernel v5.
Strange.
Click to expand...
Click to collapse
But did you see how many MBs the phone used? Cause if it's too much, people will definitely prefer just turning the phone off.
@Roqu3: I think I tried that before and it didn't seem to make a difference.
Worth a shot tho.
I'll try both of your methods if I still have the issue when I get my phone back from the service center.
Sent from a crappy rebranded Huawei using my hands
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 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...
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