Got to play with a Yoga 2 1050F for the past few days and was absolutely horrified how wakelocks kept the Yoga awake for about 30-50% of the time when it was supposed to be in deep sleep.
The wakelock in question is battery_wake_lock. It's not so much that it is triggered unusually often; rather, deep sleep is prevented by how long the wakelock is held with each trigger.
Lenovo implements the wakelock in the BQ27x00 battery driver that is shipped with the kernel of their Lollipop distribution. In the KitKat distribution, while it was initialized in the source code, it was never actually triggered. In fact, I have looked at multiple other source distributions, and not a single one uses wakelocks in the BQ27x00 battery driver. Thanks Lenovo.
In short, whenever there is a brief resume from deep sleep, for example triggered by an alarm from com.google.android.gms, the battery driver runs the bq27x00_battery_suspend_resume() function, which creates the battery_wake_lock wakelock and adds the battery polling task bq27x00_battery_poll to the kernel workqueue:
Code:
if (suspend_resume == RESUME_STR){
wake_lock(&di->wake_lock);
schedule_delayed_work(&di->work, 0);
}
The polling function bq27x00_battery_poll() would call bq27x00_update() to get new information about the battery, which would then also clear the wakelock.
Since the queued polling task is supposed to be run as soon as possible (delay = 0), the wakelock should be released immediately as well. No problem, right? Well, this would be only true if the polling task wasn't already active in the queue from a previous wakeup!
The person who added the battery_wake_lock didn't consider that bq27x00_battery_poll() adds itself to the kernel workqueue and is then triggered on a defined poll interval (default is 60 seconds as hardcoded in the Lenovo source). What does this mean? It means that it's possible, and highly likely, that when the Yoga briefly resumes from deep sleep, that there is still a queued battery polling job in the kernel workqueue. As a result, the code from above, even though it's meant to be triggered immediately, has to wait until the existing queued job has been executed. And that can take up to 60 seconds or to whatever the polling interval is defined. And that is why we are seeing those nasty long battery_wake_lock wakelocks that keep the device from deep sleep half the time.
Tldr: Each time the Yoga briefly resumes from deep sleep (which is normal and happens frequently - albeit it should be only briefly), the battery drivers adds a wakelock which prevents the device from going back to deep sleep for up to 60 seconds. If you have a total of 20 alarms per hour (not unusual - see com.google.android.gms - and normally not an issue since they are meant to be very brief), it means that Lenovo's battery wakelock keeps your device awake for up to 20 minutes or about 30% of the time!
Why did Lenovo add this wakelock? I am not sure, as I haven't seen it anywhere else implemented. In fact, Lenovo removed all wakelocks again from the battery driver in the Android 5.1 release for the Yoga Tab 3 series.
So what's the workaround?
If you have root, you can reduce the polling interval by modifying the poll_interval driver parameter. For example, I reduced the interval to 20 seconds:
Code:
$ cat /sys/module/bq27x00_battery_x8/parameters/poll_interval
60
$ echo 20 > /sys/module/bq27x00_battery_x8/parameters/poll_interval
$ cat /sys/module/bq27x00_battery_x8/parameters/poll_interval
20
While it seems counterproductive at first to reduce the interval and thus increase the number of battery polls, it makes perfect sense if you consider that it also allows the kernel queue to clear faster. Before it could take up to 60 seconds for the wakelock to be released; now it takes only up to 20 seconds. Ideally, when you have the device on, you'd want to set the interval parameter to a higher number again (your battery status is updated every 20 seconds now instead of every 60 seconds), although I haven't noticed any difference in performance or battery life so that's probably not an issue.
Speaking of battery life, attached you see how well my device was doing over last night. The battery charge went down by 1% - from 73% to 72% - in 8 hours! Not bad, is it?
Lastly, I am currently using the YT2-1050F-USR-S100067_1507101258_WW52_ROW firmware and haven't upgraded to the latest OTA yet. It's possible that Lenovo has fixed the issue, although I highly doubt it judging from the lack of discussions in this regard in the Lenovo forums.
Please Lenovo, fix this.
An interesting read, but for the majority of uses including myself- what does it mean in simple language and how can we put it to use.
Most uses do not have the technical knowledge to use this and even those whose tablets are rooted,will probably not know where to look or even make the changes suggested..
Please remember we are not all competent in programming or technical language,help us by keeping it simple,with easy to follow instructions.
@corasman, first and foremost I hope someone from Lenovo will read this thread and forward it to the team responsible for doing the Yoga firmware upgrades.
Meanwhile, in a practical manner, it all depends if you have root access to your device. If you don't, then I am afraid you cannot do anything to workaround this issue. If you do have root, there are multiple ways. The easiest way is to use an automation app like Automagic or Tasker, and have it dynamically adjust the poll_interval parameter depending on whether the screen is on or off. If anyone is interested I can attach my Automagic "flows" here that will do the job. Again - you need root for this.
doctorow said:
@corasman, first and foremost I hope someone from Lenovo will read this thread and forward it to the team responsible for doing the Yoga firmware upgrades.
Meanwhile, in a practical manner, it all depends if you have root access to your device. If you don't, then I am afraid you cannot do anything to workaround this issue. If you do have root, there are multiple ways. The easiest way is to use an automation app like Automagic or Tasker, and have it dynamically adjust the poll_interval parameter depending on whether the screen is on or off. If anyone is interested I can attach my Automagic "flows" here that will do the job. Again - you need root for this.
Click to expand...
Click to collapse
I'll have a go at this and report back,I am rooted and also have TWRP installed and backed up,If you can attach you "flows" please, I grabbed Automagic- where do I add the flows and execute them.
corasman said:
I'll have a go at this and report back,I am rooted and also have TWRP installed and backed up,If you can attach you "flows" please, I grabbed Automagic- where do I add the flows and execute them.
Click to expand...
Click to collapse
Sounds good! Attached you find the Automagic flows. Make sure in the Automagic preferences to have it "start after boot" and also enable "Root functions (Experimental)".
Btw, my overnight awake time is now ~1%.
doctorow said:
Sounds good! Attached you find the Automagic flows. Make sure in the Automagic preferences to have it "start after boot" and also enable "Root functions (Experimental)".
Btw, my overnight awake time is now ~1%.
Click to expand...
Click to collapse
Sorry, that is way over my head, I have had a look in system\power\wakelock and it is empty so assuming it's not doing anything. I am on the latest update,so could be the reason.
corasman said:
Sorry, that is way over my head, I have had a look in system\power\wakelock and it is empty so assuming it's not doing anything. I am on the latest update,so could be the reason.
Click to expand...
Click to collapse
Where did you see this? As far as I know the default system power manager doesn't show wakelocks. Uhm, the flows should be easy to import. Copy the XML file attached in my post above to your device. Then. when you start Automagic, click on its menu (top right button) -> Manage -> Import Flows/Widgets. There you can point to the xml file. It should be imported and the rest should go automatic. What's important is that you enable root in Automagic, which you can do in menu -> Manage -> Preferences.
doctorow said:
Where did you see this? As far as I know the default system power manager doesn't show wakelocks. Uhm, the flows should be easy to import. Copy the XML file attached in my post above to your device. Then. when you start Automagic, click on its menu (top right button) -> Manage -> Import Flows/Widgets. There you can point to the xml file. It should be imported and the rest should go automatic. What's important is that you enable root in Automagic, which you can do in menu -> Manage -> Preferences.
Click to expand...
Click to collapse
I have saved as an XML file,but when I try to import to Automagic it says invalid file.
I have sorted it,used a different XML programming.
Hopefully have it running---yoga battery fix(2 files running)off and on,is that right.
Thanks for the tip, I implemented it in Tasker. I'm on the latest firmware and confirm that the default timer is still 60 seconds btw.
Though I noticed that the first post's code snippet sets the timer to 20 seconds and the Automagic flow sets it to 1. I assume you tested with both timer settings and the 1 second performed better?
My overnight usage of seven and a half hours is one percent.
That's just shutdown to sleep and nothing else turned off.
iampanis said:
Thanks for the tip, I implemented it in Tasker. I'm on the latest firmware and confirm that the default timer is still 60 seconds btw.
Click to expand...
Click to collapse
Thanks for checking. I will update to the latest firmware eventually but what you could check is if the duration of kernel wakelocks decreases with your firmware when the display is switched off after applying the fix (the total "awake" should go down considerably) . The poll interval itself is not the problem - it's the wakelock that they added to the battery driver which is directly influenced by the polling interval. The fix doesn't remove the wakelock or reduce the number of wakelocks. It reduces the duration because it makes sure that the kernel queue is quickly cleared. It was obviously something the Lenovo developer didn't consider.
I have added the same logic to Tasker and attached the Tasker profiles to this thread. Tested only briefly but seems to do the trick.
Though I noticed that the first post's code snippet sets the timer to 20 seconds and the Automagic flow sets it to 1. I assume you tested with both timer settings and the 1 second performed better?
Click to expand...
Click to collapse
This is correct. It was before I decided to dynamically switch the polling interval depending on whether the device is on or off, and depending on whether it is charging or not. A charging device btw is always awake due to safety issues (you want the battery driver to catch an overheating battery...), meaning there are no suspend/resume calls to the battery driver, meaning the wakelock won't even be initiated.
corasman said:
My overnight usage of seven and a half hours is one percent.
That's just shutdown to sleep and nothing else turned off.
Click to expand...
Click to collapse
Nice.
Hello,
I had the same problem on my 1050F, rooted the tablet, installed Tasker and used your project - it works flawlessly However, I am wondering what are the long-term effects of lowering the poll interval for the battery (if any), do you have any conclusions after testing this workaround for a prolonged amount of time? Is lowering the poll interval to 1 safe or some sort of buffer value (10-20s) should be used instead?
I am no developer, just a regular user, but I'd be happy to get some feedback regarding this issue, especially that Lenovo seems to be non-responsive about the problem.
Anybody knows if this issue has been fixed in the lasts updates?
No, not fixed. I am having issues with Tasker not running the profiles correctly, and it's frustrating to wake up and find the battery flat in the morning given it's not the fastest device to charge !
I had this working fine in tasker until recently and now my yoga in on 30% awake and not sure why the tasker profiles dont seem to be working anymore, nothing else short of a few app updates has changed
Hi to all,
I do not know why, but the script don't work for me, it is in "execute" in automagic but the battery continues to discharge during the night.
I set everything up as described, does anyone know how to solve it?
Thanks
Related
Hey guys,
Just updated to the x10 after my samsung galaxy died on me, so far i am rather happy - except for the lack of root, but that will come.
I have noticed many complaints on the forum about battery life, and have experienced the same thing myself. From my experience, i think this looks like the same issue that was faced on a leak of 1.6 for the galaxy - it was referred to as the "No Sleep Bug".
TBH, the name says it all - for some reason, in many builds of android 1.6, phones were not sleeping correctly. There are many theories as to why, from cpu not being allowed to sleep, to permanent communication with google servers.
Despite all these different theories, one thing seemed to fix the problem - turning off all location services. Some people argue that a different carrier build, turning off just 'share with google' under location, turning off just AGPS etc. would fix it, but from my experience, the only real way to fix the issue was to turn off all GPS usage unless you need it. The once you have used it, reboot your phone.
This fix obviously sucks, and a new fix has recently been released by a veritable android-demigod around the Galaxy.
HERE IS A THREAD ABOUT NO SLEEP ON i7500 GALAXY;
(ok, some stupid rule says i can't post links - can a mod help me out?)
HERE IS THE FIX FOR THAT PARTICULAR BUG;
(ok, some stupid rule says i can't post links - can a mod help me out?)
LINKS ARE IN POST #5 - THANKS TO ONDOTEAM (would still be nice to get them in this original post though)
Now, from my experience, no sleep behave exactly the same way on the x10 as it does on the Galaxy;
1) I turn of all location services, and my battery life at least doubles.
2) After said turning off of services, 'spare parts' no longer says 100% running time under battery usage - in fact it can be as low as 10%.
These two factors are identical to my experience with Galaxy. SO; is there any way drakaz's fix can be applied to our X10's? It seems to me that the files he mods are standard Android system files, not sony/samsung specific.
Now i am no developer, so i dont know it this is possible - the first question that comes to mind for me is "do we need root access, or can this be done through developer tools using the android SDK?"
Can anyone help shed anymore light on this?
Seems to work for me. I disabled all location services. Spare Parts went down from 100% to 7.6%.
I'll just have to enable GPS when I need to use it..
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
n3man said:
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
Click to expand...
Click to collapse
Hello send me a PM with links, I will try to post it
http://androidforums.com/samsung-i7500/61168-no-sleep-has-nothing-do-anything.html
http://androidforums.com/samsung-i7500/78471-no-sleep-bug-fixed-drakaz.html
Links from n3man
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
ronnyuk said:
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
Click to expand...
Click to collapse
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
I can't see "Spare Parts" in About Phone -> Battery Info
tuxStyle said:
I can't see "Spare Parts" in About Phone -> Battery Info
Click to expand...
Click to collapse
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Spare Parts is a standalone Program ...
(i don't know for sure if it is in the market or downloadable as .apk from somewhere here in the forum ...)
Bax
im_iceman said:
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Click to expand...
Click to collapse
You can download it here
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
n3man said:
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
Click to expand...
Click to collapse
14% it's mine value for running time, not 100%. By the way thats 30 minutes of 210 in total :S
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
mimok said:
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
Click to expand...
Click to collapse
Do you have 3G always on?
My phone has no trouble sleeping.
Gps hasn't really been an issue but I keep it off when not needed.
Here's my solid settings:
1) No auto sync
2) No moxier
3) Gps off
4) Restart after using wireless
As long as it's like this my phone lasts 2 days easily
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
Yes, but I made a lot of test with and without 3G enabled and 3G seems not to be a problem for me. I think my problem comes from GPS.
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
3G always on.
n3man said:
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
Click to expand...
Click to collapse
I have been playing with mine for a month to work out what caused mine to not go into sleep, I keep GPS wifi etc on 24/7 but in spare parts I was running 100%, after numerous reinstalls and removing everything i chanced on turning on auto screen brightness, now when i unplug my x10 the running sits at the correct level.
No Geolocation bug here
I have this problem with 100% on and off. Sometimes when I check its under control (~10%), other times its at 100%. I have GPS off, no WiFi, auto brightness... don't know why it sometimes just gets stuck at 100% :/
I starting a bounty for fixing the android os bug.
Anyone that fixes this bug gets the bounty. (not samsung or google tho)
Donations so far:
Doc 30$
dan13l 30$
TML1504 30$
Has anyone checked to see if its google maps chewing it up? It did this on some other phones with the latest update.
neubauej said:
Has anyone checked to see if its google maps chewing it up? It did this on some other phones with the latest update.
Click to expand...
Click to collapse
Keep the discussions in the other threads.
But maps is not the cause.
Switch Wifi sleep policy to "never sleep"
From the page for this issue on Google Code (others have linked to this page already but apparently no one here has bothered to actually read it):
code.google.com/p/android/issues/detail?id=15057
There appear to be two main causes of extreme battery consumption by the Android OS process.
#1 is the Wifi sleep policy of "wifi off when screen off", which is usually the default. If you haven't made a point of changing yours, it's probably still on this setting. In the Wifi settings page (where the SSID list is), press menu, then advanced, then Wifi sleep policy. Change it to "Never". A more blunt-force solution is to keep Wifi switched off all the time.
#2 is some combination of Google Latitude and location services (GPS and Wifi). This one seems to be less common and many people say it's definitely not the problem. It may be related to #1 in that a problem with the Wifi is causing location requests to fail, somehow causing extra processing.
Comment 23:
The increased consumption only occurs, when I have the wifi sleep policy set to "sleep while display is off". In this case the battery consumption is very high while the display is off.
Comment 31:
Only changing Wi-Fi sleep policy to Never from "Never when plugged in" fixed this for me for now.
Comment 40:
I can confirm that "Always on" WiFi policy solves the problem for me
Comment 53:
By putting "always on" to the wifi sleep policy, I'm now at 25% battery after 1 day 7 hours of usage (since last charge)
Comment 54:
The recommendation of changing the wifi sleep setting to 'Never' appears to have worked for me as well.
Comment 88:
Both "always on wifi" as well as "turning wifi off manually" work for me. The heavy battery drain only occurs in combination with the "wifi sleep while screen is off" policy.
Comment 90:
I have 'never sleep' policy for WiFi, and battery life is just fine.
Phone easily can sustain a day with some 40% battery remaining.
Click to expand...
Click to collapse
And so on...
A poll to see whether these solutions work for everyone would be good. I probably can't make it because I just registered.
Disclaimer: I have ordered but not yet received my Galaxy S II. The info in this post is not my firsthand knowledge, just some quick research.
ninewise said:
From the page for this issue on Google Code (others have linked to this page already but apparently no one here has bothered to actually read it):
code.google.com/p/android/issues/detail?id=15057
There appear to be two main causes of extreme battery consumption by the Android OS process.
#1 is the Wifi sleep policy of "wifi off when screen off", which is usually the default. If you haven't made a point of changing yours, it's probably still on this setting. In the Wifi settings page (where the SSID list is), press menu, then advanced, then Wifi sleep policy. Change it to "Never". A more blunt-force solution is to keep Wifi switched off all the time.
#2 is some combination of Google Latitude and location services (GPS and Wifi). This one seems to be less common and many people say it's definitely not the problem. It may be related to #1 in that a problem with the Wifi is causing location requests to fail, somehow causing extra processing.
And so on...
A poll to see whether these solutions work for everyone would be good. I probably can't make it because I just registered.
Disclaimer: I have ordered but not yet received my Galaxy S II. The info in this post is not my firsthand knowledge, just some quick research.
Click to expand...
Click to collapse
These fixes wont cure it for sgs 2.
See attached. It's not the wifi policy.
I too will pledge $30 for a working fix once I've verified that the problem is solved.
Sent from my GT-I9100 using XDA Premium App
dan13l said:
See attached. It's not the wifi policy.
I too will pledge $30 for a working fix once I've verified that the problem is solved.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Nice, i will update 1st post with all the findings so far.
"android os" bug is NOT:
Wifi bug (always on)
Maps bug
Any installed apps bug
Operator bug
Latitude bug
count me in with $30 as well
DocRambone said:
Nice, i will update 1st post with all the findings so far.
"android os" bug is NOT:
Wifi bug (always on)
Maps bug
Any installed apps bug
Operator bug
Latitude bug
Click to expand...
Click to collapse
I had similar issue on SGS, my problem was because aparently I got a faulty modem file, I noticed my signal bar going up and down continously.
Has anyone tried changing modem?? I don't have a SGS2 so I don't really know if there are modems to choose from...
Good Luck Doc.
gtluis said:
I had similar issue on SGS, my problem was because aparently I got a faulty modem file, I noticed my signal bar going up and down continously.
Has anyone tried changing modem?? I don't have a SGS2 so I don't really know if there are modems to choose from...
Good Luck Doc.
Click to expand...
Click to collapse
Getting a good idea now, a first setup on 3g network (no wifi), avoid the dir 655 routers and you be fine.
Wifi policy is set to "never" by default, so I can't see why it would help anyway.
That said with KE1 and a factory reset, although I have higher than would usually be expected AOS usage, my battery drain issue hasn't been all that bad - from a full charge today (7hr 15 on battery) to 83% with maybe 20 minutes angry birds, and the occasional checking of emails, texts and facebook and playing around with it a bit...
Screen on time 31 minutes... Android OS at 20% now and Wifi Sharing(!?) on 13%.
So not too bad, but it could be better IMHO - equates to about one and a half days of light use - definitely room for improvement.
There are so many threads about battery so not sure which one I should post it but..
I saw some strange things in Logcat. I get alot of those errors :
E/lights ( 2701): write_int: path /sys/class/backlight/pwm-backlight/brightness, value 170
E/lights ( 2701): write_int: path /sys/class/leds/blue/brightness, value 0
I don't exactly know what the error means(well they are related to the menu and return backlight I think), but the E/ stands for error in case you didn't knew.
Do you guys get the same kind of errors in logcat?
I've noticed 2 things:
If I wake it up, the cpu frequency doesn't go below 800mHz. (with only 4% load)
Only after I've started an app (not a widget etc.) it went down to 200.
(look at the "Temp+CPU V2" widget on the screenshot)
And the camera seems to run further if you don't go back out.
After a shot in school, I pressed the power button and at home, it felt VERY hot (front and back) and the battery level went down in 3% steps every 1-2 minutes.
But the camera wasn't listed in the battery stats, only Android OS, which was eating 70%.
Screenshot
Android OS Battery bug
Hi!
1. Install SystemPanelLite Task Manager from the market.
2. Run SystemPanel and open settings and check the "System processes" option. Close settings.
3. Scroll down in the process list until you find the process "android.process.media". If you have a CPU usage of more then 10-30s and the process usage gauge to the left moves up and down you probably have the Android OS battery bug.
At this point you can try the following;
- Shut down your phone. (Not just turn it of. The complete shut-down-power-off-thingy)
- Remove your external SD card.
- Start up your phone again.
- When the scan media is complete, do step 3 above again. If you don't see the problem at step 3 your SD card has a corrupt filesystem. And needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Unmount SD card
- Format SD card
- Restore files from your backup.
If the problem persists your internal SD card might have a corrupt filesystem and needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Format internal storage
- Restore files from your backup.
More details; What happens when you have a corrupt filesystem is that android.process.media tries to read a file but fails over and over again. The filesystem might not look corrupt to you. And you can read and write files on the SD card without problems. But at some point the android.process.media failes to read the files and loops like crazy, draining your battery.
I had a corrupt filesystem (FAT32) on my external SD card. I also had Android OS battery usage of 60-70% and a fast draining battery. I hope this can help others.
Best regards,
/Pontus
My android.process.media is 27 secs. Is this in the acceptable range?
Hi!
It's a bit high I'd say. I've got like 2000+ photos and I'm at 9 s after a days use.
Take a look here;
Settings -> Applications -> Battery usage
If Android OS is above 50% then you should consider my suggestions.
Most importans, does your phone get hot and use a lot of battery without heavy use?
Removing your external SD card and rebooting your device isn't that much work. If that gets rid of your problems, then reformat your SD card.
FAT32 isn't the most robust filesystem.
Best regards,
/Pontus
how can i remove the languages which i dont need?
what's causing the battery drain inside Android OS
After doing further investigations with watchdog, the Android OS battery drain is caused in stand-by by:
1. suspend (linux process)
2. events/0 (linux process)
They use heavily the processor while in standby... I've seen alert of up to 80% of CPU in both processes.
Hello everybody! The purpose of this guide is to show you some free ways to greatly increase your battery life on the Droid X. First this guide assumes you have the Gingerbread kernel, root access, and are comfortable with ClockworkMod Recovery. If you have not installed a few roms, SBF’ed, or backed up your phone, learn how to and practice it a few times. I am not responsible if you fubar and have to SBF your phone. This guide is specifically written for the Droid X, but since the Droid 2 uses the same innards, you can probably use this guide interchangeably with that phone. Not all the steps in this guide only apply to the Droid X so I will say something on the steps that can be used on other Android devices.
First I'm going to start with basic things you do not want to do if you plan on saving battery. (All Devices)
Battery Saver Apps: Battery saving apps like Juice Defender are bad ideas. As I will explain later, many apps expect an always on data connection and prevent your processor from going into deep sleep when they are waiting for that data connection to come back on. Not to mention a battery saver is just another app and service that is running in the background potentially using battery.
Wipe Battery Stats: A Google developer has confirmed that the batterystats.bin does not hold battery calibration information. It holds information to compute battery usage information. The same information you see under “Battery Usage” in settings. Wiping this file just wastes your time.
Hungry Apps: Apps that use excessive notifications keep the processor from going into deep sleep. Facebook is the number 1 culprit here. Go into the app settings and turn of notifications. Use your back button to exit apps when you are done.
Automatic Backlight: On the Droid X, the Automatic Brightness setting is useless. Minimum brightness is too high by default. Either turn it off and set brightness manually or take the step I did that comes up later in this guide.
Wifi: Wifi when you are in range of a router uses less power than your 3G connection and is faster anyways. Wifi when you are not in the range of a router is a battery killer and should be avoided. Use your notification toggles if you have them. Get a widget if you don’t.
GPS: GPS should be turned off at all times unless you are actively using it. Nobody cares where you were when you posted on Facebook.
App killers: App Killers are good for hunting down and killing an app once in a while but are usually pointless. Android automatically loads apps into free memory for quicker starts. Why have your app killer wake up the phone from its idle, kill all of your apps to free up memory, and then have Android automatically reload most of those apps back into memory?
Bluetooth: Bluetooth headsets are best left in the car where you have your phone on a charger. If you need to use one off the charger, don’t forget to turn off your Bluetooth when you are done.
Charging: Charge as often as possible. Follow the same battery saving strategies you usually do when your phone is off the charger. It makes your phone charge faster. Keep in mind the mA rating on the charger. The stock one is 850mA. Do not exceed this rating. USB is ~500mA depending on other devices attached to the computer. The higher the rating, the faster the charge. Do not let the battery get very hot. Do not let your battery level drop below 10 very often. Low charge levels on Li-Ion batteries can damage them. Alternately, do not reputedly plug and unplug your phone once your battery shows 100. Android charges to 100 and lets it use up battery for a few percentages before it starts charging again. This is to prevent overcharging and damaging your battery. If you plug and unplug it repeatedly, it tricks Android into charging it more and more. Keep in mind that li-ion batteries lose capacity over time whether you use them or not. Replace them when they are no longer keeping you happy.
Step 1. Selecting a Rom
Liberty 3 forum topic: http://forum.xda-developers.com/showthread.php?t=1368049
Really for the purpose of this guide the only rom worth picking is Liberty 3. This rom is based on Motorola code which is known for good battery life and has init.d support baked in. It also has the power toggles in the notification bar and has pretty good customization. The 2nd-init roms that have init.d will work too but have issues with battery life. From this point forward I am going to assume you are going to be using Liberty 3 but the steps should work the same for other roms as long as there is init.d support.
Step 2. Installing the Rom
Use CWM to install the rom like you normally would. Start up and follow the usual setup wizard. Once you are able to get to settings, click on Liberty Settings, then Performance, then Start-up Tweaks, then uncheck everything except "Enable start-up tweaks." These settings interfere with the next step and are going to be duplicated by the next step.
Step 3. Install jakebitesmod
Jakebitesmod forum topic: http://rootzwiki.com/topic/3435-mods-jakebitesmods-v18-for-d2-ota-gb-kernel-all-roms-mods/ (Please consider donating to this developer as this script helps a lot of people.)
Jakebitesmod has some good scripts to optimize many things in Android. Pretty much anything that speeds up Android can have a small improvement on your battery life. We are specifically going to use his script to under volt the processor and set the governor at boot without using an app. Copy the linked file to your SD card and boot into CWM again to flash this. Restart your phone like normal.
Step 4. Configure jakebitesmod
Open Terminal Emulator and type “su”. This should prompt Superuser for root permission. Allow the permissions and move on. Type “modcentral”. This should bring up a little text menu of things to do. The menu option we are gonna be looking for is “1”. Read the safety issues and if you want to move forward press “Y”. From here we are going to select “1”. This option will leave you with the stock processor speeds but change the voltages on the processor to lower settings. This is generally safe because lower voltages should only cause problems with freezing and crashing, but should not physically be harmful to the processor. Voltage also makes much more of a difference on power than clock speed so this should save us a good chunk of battery. Push “Y” to continue and set the voltages and speeds at boot. Press enter a couple times and it should tell you it succeeded. Yay. From here we want to go to menu option “3”. Governors control when the processor jumps up or down in speed based on some magic formula that takes into account how much work your processor is expected to be doing. Personally I agree with jakebites and I chose interactiveX. It jumps up in speed fast enough not to appear like the phone is laggy and drops back down fast enough to save battery. It also automatically drops down to the lowest speed while the screen is off. After you have made your choice push “Y” and enter a few more times. Once we are back to a menu we can just hit the back button and exit the Terminal Emulator.
Step 4. Adjusting the Backlighting (All Devices)
The Droid X’s backlight settings is a real pain. The lowest brightness setting it will dip down to is 20. This is way too bright for darkness. You know what I mean if you have browsed at night in bed. Luckily there is an app for that. Download “Custom Auto Brightness” from the Market and install it. It ends up being called LogGraph in the app drawer for some odd reason. Open this and hit you menu key and then select “Preferences”. Select calibrate sensor and follow the directions on the screen. Then go to check brightness range and follow the directions on the screen. Then back out to the main screen and make sure “Demonstrate….” is checked. Push the left “Select sensor reading” and observe the line on the graph move. These are the levels of light the ambient light sensor are going to report at. So say you have the sensor reading slider set to 10. You move the bottom slider to a value of 2. This means that your backlight will be at its lowest level when your sensor says the light in the room is at a level of 10. You can adjust these to what you prefer, but for the best battery savings turn your readings at 1 and 10 to a value of 2. This will keep your backlight nice and low while you are in a dark room but still let your backlight jump up while you are outside. Once these are set head back into the preferences and make sure that all of the checks are enabled except “Foreground mode” and “Bypass hysteresis”. Once that is done hit the back button until you close the app and then turn your screen off and on. If you brightness is way lower than it was before you are golden. If not double check the guide.
Step 5. Install Your Normal Apps (All Devices)
The next steps require your normal apps to be installed and signed into those apps like normal.
Step 6. Set Your Sync Times (All Devices)
Install the app “AutoSync Account Activator” from the Market. Open and accept the agreement. Now you should see some apps listed. I get “Google” and “Facebook” but yours may vary depending on what you have installed. The process should be similar for each app. First off, click on “Google”. The first page called “Connections” lists you connections. Click on connections you would like your account to be able to sync on. Cellular is an obvious one but really you should have your wifi on and have it activated in this while you are home. The next screen, “Periodic Sync”, controls how often your apps sync. Unless you use your Google Calendar often, set that to “1 day”. Contacts should also be “1 day”. Gmail should be set accordingly to how often you care about your email. Others may show up. Set them to according to your judgment. Just keep in mind the more often you sync, the more battery you will use. If you do not use the service at all you can select “No period”. If you have one set to no period you should also set it in the next page to “Always off”. All of the rest should be set to auto.
Step 7. Observing What You Apps Are Doing and What to Do About It (All Devices)
This step is subdivided for the benefit of your eyes.
XDA Edition BetterBatteryStats forum topic: http://forum.xda-developers.com/showthread.php?t=1179809 (The link is at very bottom of 2nd post. Please purchase from the developer on Market if you use this more than a few times.)
A. This final step will ultimately probably figure out why you were getting bad battery. Android’s power management relies on what are called “wake locks”. Wake locks are things apps can create to tell Android’s power management to prevent the phone from going into deep sleep. Deep sleep is a state your processer goes into to basically shut itself off. A good example of a wake lock is when you are playing an mp3 and your screen is off. Normally when your screen is off your device wants to get into deep sleep asap. The audio service creates a wake lock to prevent your processor from entering deep sleep, because this would stop the mp3 playback. Most of the naughty apps out there use wake locks to keep data connections alive and use them to keep updating and keep notifications going. They tend not to give up that wake lock when they should and keep your phone from going to sleep. Apps that shut off your data connection, like Juice Defender, will cause even good behaving apps to freak out and keep their wake locks active while they wait for the data connection.
B. To look for these wake lock hogs we have a couple apps to get. The first one is from the link. It’s the XDA Edition of BetterBatteryStats. The second is CPU Spy from the Market. To use BetterBatteryStats just dump it on your sd card, use a file explorer to open it, enable Unknown Sources, and install it. Then open it, plug in your phone, unplug your phone, and use it like normal for a few hours. When you are ready, open the app, click on the first drop down, and select “Partial Wakelock”. Make sure the second drop down says “Since Unplugged”. Whatever apps are listed at the top are the apps that are keeping your phone from sleeping. My top 3 are DownloadManager (I was using Market and turned off my screen.), PowerAMP scan, and the PowerAMP service, but only the DownloadManager used any significant time. CPU Spy can be used to see how often your processor is going into deep sleep. Once you find your bad apps, you can look around in them and see if there are any settings in there to either turn off notifications, increase the time between updates, or anything else you may think is keeping the app busy.
C. If there is nothing there you can change, you can consider preventing it from starting. If you do not have ROM Toolbox Lite, download it. Open it and click on “Auto Start Manager”. Then scroll the screen sideways to get to the menu that says “Applications”. Click on apps and you will see two actions that we will be looking at. They are “boot completed” and “connectivity changed”. Apps like games, media players, internet radios, Facebook, etc, do not need to be started at boot and do not need to be started when connectivity has changed. Unselecting these will keep apps like Facebook from starting when you turn your phone on and when you switch from 3G to wifi.
D. If you ultimately can’t figure out why an app is keeping its wake lock for so long you may have to consider if the app is worth the lost battery life. Unfortunately there are just those apps out there that are poorly written. Consider sending an email to the developer explaining your problem and ask what you can do to fix it. If they don’t replay politely give them some poor feedback with a good explanation in the Market. They may look into the problem and correct it.
In Closing...
Thanks to everyone for reading, or at least skimming, my guide. I really hope this helps and saves time for a lot of people. If there are any issues anybody runs into I’ll try to help and explain the best I can. I apologize for any mistakes, errors, or bad sentence structure. If anybody has anything to add I will definitely consider adding it as long as it is free, easy to do, and produces results. If I broke any forum rules please notify me before deleting this topic. I’ll be happy to fix the issue.
About wake locks: http://forum.xda-developers.com/wiki/Wakelocks
Li-Ion batteries: http://en.wikipedia.org/wiki/Lithium-ion_battery#Battery_charging_procedure
Batterystats.bin information: http://www.androidcentral.com/wiping-battery-stats-doesnt-improve-battery-life-says-google-engineer
(Edit 1: Added instructions to delete default init.d scripts installed with Liberty. They seem to conflict with jakebitesmod's voltage settings. They didn't want to stick through reboots. All of the script's functions are duplicated by jakebitesmod anyways.)
(Edit 2: Turns out that deleting the init.d scripts isn't needed. Instructions updated.)
Really great advice. I don't even have a Droid X. I have a One X but this is still very relevant.
Thank you
Great guide. You should include CPU Governor such as BoostedASSv2. It helped me get good battery life (as so others).
Uhh, I cannot post this in development as I am still a newby :-(
However:
Hello,
I came from Symbian (Nokia C7-00) and liked the phone very much. Everything worked the way it should. (I was especially interested in office functionality.)
Now I bought a Galaxy Note and I really love the hardware.
But I discovered that it uses much energy and it doesn't like to sleep as often as it could. (I already returned to Android GB, which gives a better experience, but there still is room for improvement.)
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
corcovo said:
Uhh, I cannot post this in development as I am still a newby :-(
However:
Click to expand...
Click to collapse
Which is handy, because this thread has nothing to do with development and thus saved you from some abuse!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
But I already know how to click the "thanks" button
corcovo said:
But I already know how to click the "thanks" button
Click to expand...
Click to collapse
Doesn't matter.
Development, if you did not create IT, then it does not belong in development. Remember that. Otherwise you will get flamed.
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones. Android acts like a computer and, if you keep a computer running Crysis 2 for example, it would burn more power than a computer just playing some music off of iTunes.
In terms of improving your battery, check your brightness. You can download widgets to adjust the brightness right from the home screens. I use these to set my brightness to its lowest whilst at home (perfectly adequate for night and indoor use away from sunlight) and turn it onto automatic when I go outside. This has saved my a bunch of battery.
If you are running a stock Samsung ROM, turn on power saving mode. I always leave it on and, frankly, I have no idea as to what it actually does. I haven't noticed a performance drop in the slightest, but if it saves a bit of battery it is worth it. Also, you could try Juice Defender or some other battery saving apps which work for some people - others not.
Finally, ensure you haven't left GPS, Bluetooth or WiFi on when not needed. Try downloading CPU Spy to check your phone deep sleeps, yet mine even without it ever deep sleeping gets around 16 hours of battery life which is still the best I have ever gotten on a smart phone. Bettery Battery Stats can show you wake-locks (apps that are keeping your phone active) also.
Brad387 said:
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones.
Click to expand...
Click to collapse
I see. Well it might be a nice feature if one could add an "now be a cell phone"-option for energy enhancement, which means: if screen if off, sleep.
c.
corcovo said:
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
Click to expand...
Click to collapse
There are some legitimate needs for keeping the CPU from sleeping for a short period of time - such as finishing a sync operation (otherwise, the radio power spent beginning the sync is wasted). Unfortunately, some poorly written applications (Facebook for example) abuse the wakelock mechanisms and hold wakelocks when it is not justified.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
Click to expand...
Click to collapse
This is not something I have ever encountered myself. "push" relies on the server to trigger something - in airplane mode, this trigger can't happen.
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
Click to expand...
Click to collapse
Android is well optimized for cell phones - However, it assumes that third-party applications follow Google's recommendations for power management. Unfortunately, many of them do not. The number of IM applications which choose to use their own proprietary and poorly optimized network protocols (such as Skype, it's atrocious) as opposed to Google C2DM (optimized and efficient) is astonishing.
An interesting note was that I believe much of the focus at Google I/O was on reminding app developers that they need to play nice with the system and other apps.
There are some cases where there are device-specific nonoptimalities. Compared to most Nexus devices, Exynos devices have an absurdly long time to resume from wake (1000 milliseconds), and during that resume cycle CPU frequency is locked to 800 MHz and cpuidle is disabled. This is one of the #1 causes of power drain on our device. This is also exclusively a Samsung kernel/hardware architecture problem that does not affect the Nexus S (similar CPU, but completely different modem interface) or the Galaxy Nexus (different CPU/modem interface).
In the case of our device, the modem is hung off of the CPU on a USB bus - this makes for very long resume times.
Here are obvious reasons the CPU should occasionally turn on when the screen is off:
1) MP3 playback in the background
2) Handling of background syncs - e.g. when an email or Google Talk IM comes in, wake the CPU, handle it, and pop a notification sound, then go back to sleep. Normally, this means the CPU sleeps while waiting for an interrupt from the WLAN chipset or the cellular radio. Unfortunately, some apps drive incoming data to the device far too frequently. (See my above rant about Skype's network protocols being crap compared to Google's C2DM protocol.)
3) Handling of scheduled wakeups (alarms, calendar events, etc) - these are rare and almost never consume power
Most power drain is from item 2, with third-party apps frequently behaving extremely poorly compared to Google's own application suite and sync protocols.
Now this an extensive answer which is very informative and helpful for me since insights are always soothing. Love it. Thanks!
not much to add after Entropy, but if you feel the need to get some control over battery usage you could try betterbatterystats app (and the thread) to identify battery eaters, besides that, there are few apps to check what is going on with your system when it sleeps:
- CPU Spy to show cpu states time
- Autorun Manager or Autostarts to disable triggers causing apps like FB to run without reason (those which you will find with betterbatterystats)
- Battery Monitor Widget, to check battery current consumption (mA) - this app is generally not recommended, because Note's hardware does not report the actual current, so the readings are highly estimated and because when poorly configured it can drain your battery faster, BUT otoh with refresh rate set at 5 minutes or more, it can give you some approximate orientation on how much battery you lose (better than counting %/hour by yourself) at negligible battery usage
- also, if you feel the need to disable net and sync during night, you could automate it using "lama", which is free, and in my experience does not eat much battery by itself
- and last but not least, avoid taskillers, those apps may have adverse effect, i.e. self restarting apps (by the triggers mentioned above), will get killed then restarted and so on and so on, leading to much higher battery drain
Ayo mates.
So who doesn't have battery problems? Probably everyone has. Even if you don't you'd want more ? huh ?
So after owning the phone for almost 3 months I had serious variations in battery life from 10 hours screen on to 7 hours screen on (*cough* 4.1.2) and back to 10 hours with xxdmb6 (YEAH!)
Also the screen off consumption.
So I am gonna talk about wakelocks in this thread. So what can use battery when you aren't using your phone... can also use the battery when you are using it. So fixes or possible fixes should improve the total battery life as well.
This thread is divided into 3 parts - basic tips , wakelock fixes and advanced fixes.
Install BetterBatteryStats. This is gonna monitor the wakelocks and the elements that drain the battery.
Tip 1 - (Install CurrentWidget) If you keep charging the battery even after it has reached 100% you will see that the battery continues to accept charge. This is true. If you charge the battery till it stops accepting power(by monitoring it through currentwidget) you will see that 100% lasts for a long time. i mean that suppose your phone uses 1% battery per 10 minutes, now if you just unplug and start using the phone, it will stay at 100% for a long time.
But this may even damage your battery. I am not sure. I do it considering how much technology has advanced.
Tip 2 - So from wanam's thread -
wanam said:
Disable auto sync for accounts if you don't need it
Disable GPS (and wifi gps) when not in use
Disable auto backup of Google account
Set brightness level to automatic
Disable motion if you don't use it
Check your apps settings and disable useless background sync
Disable useless animations
Click to expand...
Click to collapse
List of general Wakelocks -
PowerManagerService - It is a sum up of partial wakelocks.
MultiPDP - This indicates a high network usage(2g/3g/4g).
AlarmManager -
AlarmManager provides access to the system alarm services. These allow you to schedule an application to be run at some point in the future. When an alarm goes off, the Intent that had been registered for it is broadcast by the system, automatically starting the target application if it is not already running. Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted. The Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. This guarantees that the phone will not sleep until you have finished handling the broadcast.
Click to expand...
Click to collapse
These are the findings of asksven, so have been quoted. So it is a sum up of different wakelocks again
AudioOut_2 - When apps run in the background that use sounds, this wakelock is always there.
deleted_wake_locks - A wakelock that is no more, generally when you turn wifi or data or gps on and off. But it still reflects wifi wakelock. You can sum it up as a wifi wakelock and some other wakelocks.
network-location - This is a gps wakelock.
wlan_rx - Wifi wakelock
wlan_wake - Wifi wakelock
mediaserver - when something uses media files or may even when you play heavy games like real racing 3 which uses data on internal sd card
l2_hsic - A possible explanation is unplugging the charger while phone is asleep.
I have attached a pic. You can see the difference
Wakelock Fixes
AudioOut_2 - AudioOut_2 is a major wakelock on many devices. The solution is simple. Before turning the screen off. remove all recent apps and in task manager , go to ram tab and hit clear memory. Then close task manager and swipe it away from recent apps as well. Then lock the phone. Alternatively you can download advanced task killer. (Viber seems to cause this on many devices.)
MediaServer - Flash the attached fix via a custom recovery. Someone posted this and said that he got from alliance rom ota app. I asked the Dev and he said that I can use it but it may cause a boot loop. So keep nandroid a ready. Credits go to comnam90.
Other fixes could be to download Rescan Media Root. This app fixes wakelock but it might still come up sometime.
If you are comfortable with decompiling try this.
l2_hsic - This wakelock is incorrigible. But possible fixes are in thread. I will jot down what works for me.
NetworkLocation/SignalCollector Hierarchy - Many wakelocks happen due to this maps app. This is because maps app try to update the location of the device. Modify the settings according to the image attached. But better is to disable all location services. This will also decrease AlarmManager wakelock.
But if you really don't use maps then best is to Freeze local app, maps app, navigation app. This wouldn't harm the phone as they can also be downloaded from play store which means android os can cope without it.
Processes - There are many user apps which are a necessity but eat up the battery. We can't freeze it nor uninstall it due to the need. What can we do about 'em ? This is where Greenify comes in. Don't let the uber simple UI fool you. The app is simple and self explanatory. I have greenified almost all the apps and this app doesn't eat up your battery !
I will be adding more as I find more...
Advanced Fixes
These aren't very advanced if you know what you are doing.
Try another kernel. (like perseus, uneak, redpill). I find almost similar results but it may vary as we move to the next parts
Undervolt(CPU). Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 800mV.
Thanks!
One of the best things I did to save battery is to remove Facebook and Viber.
Now I'm trying to Greenify Facebook. I hope it will not do any wake locks.
Nice article Utkarsh.
Those are general wakelocks, but there are others as well, like in the attached pic.
Btw- What's that wakelockfix.zip?
'Swyped' from my GT-N7100
jujuburi said:
Nice article Utkarsh.
Those are general wakelocks, but there are others as well, like in the attached pic.
Btw- What's that wakelockfix.zip?
'Swyped' from my GT-N7100
Click to expand...
Click to collapse
That wakelock is generic with exchange services. Remove it to get rid of it.
Well that will probably fix media server. It did for me but I will see if it comes up again.
Sent from my GT-N7100
UtkarshGupta said:
That wakelock is generic with exchange services. Remove it to get rid of it.
Well that will probably fix media server. It did for me but I will see if it comes up again.
Sent from my GT-N7100
Click to expand...
Click to collapse
Yeah, I know. But I use that on daily purpose. No question of removing it
'Swyped' from my GT-N7100
jujuburi said:
Yeah, I know. But I use that on daily purpose. No question of removing it
'Swyped' from my GT-N7100
Click to expand...
Click to collapse
Well you gotta try hampering with update settings. I am a student and not in business so email delay is not gonna hurt me at all.
It would hurt business men(that's what I derive of you) or someone whose most work is done through mails.
Nice thread, but I'd like to chime in that wakelocks aren't necessarily an absolute evil. You will always have some wakelocks, and it's supposed to be that way. Network, wifi, location services and some apps won't work properly without being able to wake the phone from time to time. It's when these wakelocks sum up to a considerable ratio of your uptime that you should begin to worry.
Might I also suggest you add greenify to your list of countermeasures.
Sent from my GT-N7100 using Tapatalk 2
UtkarshGupta said:
Undervolt. Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 900mV.
Click to expand...
Click to collapse
Is this for cpu or gpu? Thanks for the guide.
gyxter said:
Is this for cpu or gpu? Thanks for the guide.
Click to expand...
Click to collapse
Thanks should have mentioned. It is CPU.
Sent from my GT-N7100
adytum said:
Nice thread, but I'd like to chime in that wakelocks aren't necessarily an absolute evil. You will always have some wakelocks, and it's supposed to be that way. Network, wifi, location services and some apps won't work properly without being able to wake the phone from time to time. It's when these wakelocks sum up to a considerable ratio of your uptime that you should begin to worry.
Might I also suggest you add greenify to your list of countermeasures.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Greenify is already there. Check in 2nd post processes part.
Sent from my GT-N7100
UtkarshGupta said:
These aren't very advanced if you know what you are doing.
Try another kernel. (like perseus, uneak, redpill). I find almost similar results but it may vary as we move to the next parts
Undervolt(CPU). Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 900mV.
Click to expand...
Click to collapse
Hi, just one question, why not go below 900mV? Is there any reason for that? I´ve got my Note 2 uVd to these values (762, 775, 800, 825, 850, 875, 925, 950, 1000, 1050, 1075, 1125, 1150, 1175, 1250) for the frequencies from 200Mhz to 1600Mhz, I don´t think it wil harm it as I´ve been running these settings with RedPill Kernel and STweaks app for a couple of months now and I haven´t had any freezes at all or any issues, could you explain why it´s not recommended to go below 900mV? Is it just for the different tolerance to uV every chip has? Thank you anyway for your marvelous post and for the greenify app, looks promising, I´ll report how it goes since I´ve just started using it today, thanks.
thecrab93 said:
Hi, just one question, why not go below 900mV? Is there any reason for that? I´ve got my Note 2 uVd to these values (762, 775, 800, 825, 850, 875, 925, 950, 1000, 1050, 1075, 1125, 1150, 1175, 1250) for the frequencies from 200Mhz to 1600Mhz, I don´t think it wil harm it as I´ve been running these settings with RedPill Kernel and STweaks app for a couple of months now and I haven´t had any freezes at all or any issues, could you explain why it´s not recommended to go below 900mV? Is it just for the different tolerance to uV every chip has? Thank you anyway for your marvelous post and for the greenify app, looks promising, I´ll report how it goes since I´ve just started using it today, thanks.
Click to expand...
Click to collapse
Well I read somewhere. But I will update the op.
Sent from my GT-N7100
Deep sleep results....
Sent from my GT-N7100
how about just use the power-saving mode...
thanks for guide...
fly2dheaven said:
thanks for guide...
Click to expand...
Click to collapse
Welcome but plz use thanks button. It isn't about no of thanks but it helps prevent clogging of threads
Sent from my GT-N7100
Audio out 2 for me has been causing an annoying battery drain. Turns out viber is causing it for me. Yesterday it was the best part of two hours.
Today I quarantined viber and my audio out 2 dropped to 6 seconds after the phone being on for 6 hours. Half an hour ago I re started viber and my wakelock now reads 22 minutes. So I have now uninstalled viber.
How this info helps others.
arjunr24724 said:
how about just use the power-saving mode...
Click to expand...
Click to collapse
Well this doesn't hit performance.
Sent from my GT-N7100