Database Info

Advanced Tricks for Saving Battery (it Works)

EDIT: Last Update: 10th Sep 2011 with New INfo (trick no.7)
Advanced Tricks for Saving Battery
The following tweaks can greatly save battery if you done it right. But bear in mind that risk are relatively higher since its involve those deep system components.
If you know what you're doing, there is not much to worry about.
Note: I will not responsible for the any damage of your device
My Result:
Before: After moderate usage of 20 hours, Battery Left 30% - 35%
After : After moderate usage of 20 hours, Battery left 70% - 75%
Note: Battery Usage is very subjective matter. The numbers here is not trying to give you an exact calculation, it just trying to give you a feel of how the battery saving. But i have try my best to be consistent on the usage pattern, cpu loads and temperature to do this comparison. Of cause, you might discover different result on your device. With different ROM, kernel, radio, usage, screen brightness, all the other factors come into play, the result would varied.
Kindly please post a feedback on how it works on your device>
1. Use Undervolted Kernel / ROM
- Undervolted means that your device will use relatively less battery to give the same CPU frequency
- (e.g. normally CPU run at 1.61ghz @1350mv, after undervolted it may require only 1275mv at the same frequency)
- Tested on my device, it is the most effective tweak to increase battery life (I reduced -100mv at most of the CPU frequency (except 1), give me about 30-35% more battery)
- Because the undervolting value is varied depend on the ROM and kernel, so no point i post all the numbers here. (PM me if you need the list)
- Ask at your respective ROM thread for the availability of undervolted tweak
- If you wanted to try to change the undervolting value, i recommended to use OC/UV beater2 http://forum.xda-developers.com/showthread.php?t=1207546
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Because the tool have ease-to-use interface (no need use terminal emulator), just few taps will do.
- Most importantly, we can test new UV value with "Temp Activate", if the device freeze, just restart and it will go back to the last good state (last best config for you, instead of kernel's default value), and no need to flash the vddreset.zip / other reset.zip
2. Use "GSM auto (PRL) to save more juice while still connecting through 3G
- in the phone setting>wireless and network>MobileNetwork>NetworkMode
we are only allow to choose GSM only/ WCDMA / Auto between two
- but if you use type "*#*#4636#*#*" to phone Information, you can choose more type of networkmode. It is claimed that choose "GSM auto (PRL)" allow you to save more battery (cell standby) while allow you to connect to 3G network.
- This might somehow depend on your carrier / provider
- Please provide feedback on this. THanks
3. Try out different CPU Governor
- nowadays a lot of ROM have advanced CPU governor like Smoothass, Smartass, Interactive, etc.
- Try different combination during wake up and screen off to look for the best setting that let u save more juice
- This are my settings:
Governor during awake = On Demand
Max Wake = 998mhz​ Min Wake = 122mhz​ Governor during Screenoff = PowerSave
Max Sleep = 307mhz​ Min Sleep = 122mhz​ - NOTE: if you put min sleep too low, there is a chance that you device might freeze and won't wake up!
- I personally recommended "DaemonController" from Sybregunne for controlling the CPU governors and frequencies. It is a ease-to-use, yet sophisticated enough for the purpose of OC/UC. It is my favourite OC/UC controller since it released.
- DaemonController is a smart tool that it will bypass virtous daemon, and use direct frequency if we choose governors that is incompatible with the virtuous o/c. Hence, only 1 deamon is run which is more efficiency.
- Refer to the original thread here for more details: http://forum.xda-developers.com/showpost.php?p=16726715&postcount=2
- Quoted from original thread: "It is a Graphical tool that allows users to change andrev_oc/virtuous_oc frequencies and governors without having to reboot their device. Confirmed to work on Android Revolution HD 6.1.0 and a lot more ROMS.
4. Use AutoKiller Memory Optimizer
- This tool is different from other app killer
- It fine tunes android systems inner memory manager to keep your device fast over time.
- As a side effect it also lowers battery consumption.
- At certain free memory level (e.g. 250mb), the android os will automatically close those apps not in use (according to original android os logic)
- The lowMemoryKill level can be modified to suit your style of usage. It is to find a balance point between "not killing the apps you're need" and "sufficient free RAM to avoid sudden out of RAM / Laggy ".
- What i experience before is that these values are set to be too low. It keep most of the apps opened in background. So we can use the apps much faster and consump less cpu. Result: we have lower free RAM. The tradeoff: When I open heavy game, I experienced run out of RAM (it tell me not sufficient RAM to run).
- When the values set too high. It will kill the apps in background faster. So we will spend more cpu, and slower to reopen it. Tradeoff: you will have alot of free RAM back there. But for what?
- Therefore, it is to find the middle point that satisfy both ends. Generally, users with more apps better off with lower lowmemorykill value. Users with less apps (always switch between fews app only), are better off with higher lowmemorykill value.
- MY case: I only have 25+ apps installed. and Only use few apps (other rarely use). THis is my setting (in Pages): 3072, 8192, 16384, 50688, 58368, 76288. I have experimented with many values for 3 months. Just 1 month ago, i found these value suit me very much. It keep balance between the two tradeoff mentioned. Maybe you can try to figure out your own.
- Generally, we play with the last 3 numbers only. The first 3 numbers is related to:
(Foreground app)
(Visible app)
(Secondary server)
Which offer no significant benefits if we kill them.
5. Use Autostart
- Instead of closing them, it would be better if we don't let the app start from the begining
- You can choose to disable those app that u feel unnessary, so that they will not run during your phone startup
5. Check your Battery Consumption
- Download "Current Widget" or "battery monitoring widget" from market
- these apps will monitor your battery usage and recoded in a log file
- This is the normal consumption rate (varied across ROM, kernel and CPUI frequency and other factors)
Sleep/ScreenOff Consumption: 2mv - 8mv
WakeUp Consumption (no wifi, just use local apps, no gaming): 150mv - 250mv
Gaming consumption: about 300 - 400 mv (varied across diff games)
- To be comparable, it is suggest that you try to compare the consumption rate with your friends with same ROM, kernel, radio)
- With the monitoring log, you will able to notice adnormal peak / adnormal high drainage easily
6. Use "Battery History for GingerBreak" to check what running in background (Especially thanks for Saluco for this useful way to check battery drainage )
- this is a free tool can be download from xds forum http://forum.xda-developers.com/showthread.php?p=13328125
- Go to "Partial Wake Usage" to see what apps running when your device is sleeping
- Please "thanks" the developers of the apps for creating and letting us use his useful tool
- Give the screenshot of "Battery History for Gingerbreak" to the community of your ROM, this will give them more clues for them to help you
- For consistency, please monitor your usage for at least 3 hours (@ frequency 1 - 5 minutes) in order to have sufficient data and reliable readings.
7. Disable "Receiver" of application using AutoRun Manager (Really for Advanced User ONLY)
- Receivers are the "condition" where if it is fulfilled, the app will be executed
- For stance, Google Map has 8 receivers. Either 1 of these 8 conditions is met, google map will be open and run automatically.
- Now we actually try to disable this autoRUN by disable the "receiver" = means that even if the condition is met, the app won't run
- TO do this we need donated version of AutoRun Manager (available in market) to do this, go setting enable advanced mode
- Go second tap of the menu (advanced menu) to disable the receiver of particular app
- It is HIGHLY recommended to disable 1 receiver at 1 time, so that you can know the impact and trace back to the receiver
- you might get confused if you disable too many receivers at 1 time
- WARNING: ONLY disable those receiver that you know. DIsable system's receiver will make your system instable. So better only disable the user app.
- WHY IT IS USEFUL? Example: i used "Battery History for Gingerbreak (tip 6) to found out that "Facebook for android" is locking my device from being deep sleep (as it shown as high minute usage in the "partial wake menu"). Then i wanted to disable the feature of the that keep my device awake. THen i disable the "awake service" receive of it. Then it will help to save more battery by preventing those app that run automatically when certain conditions are met (example: Wifi-on, location changed..etc_
<More humble sharing is coming>
<<< Please click on "Thanks" if you found this post helpful, your thanks are very much appreciated >>>
------------------------------------------------------------------------------------------------------------------------------------------------------------
(The content is talking about HTC Desire HD, but the tricks can generally apply to any other smartphones, Hope it help you~)
Well it’s been 7½ days since I reviewed the Desire HD in which I said I didn’t want to comment on battery life until I’ve used it for 10 days. Tomorrow morning at 10am will be the 10th day, but I’m ready 14 hours early!
I’ve seen a lot of talk on the internet about terrible battery life, I’ve even experienced it myself (10% per hour on standby) but not wanting to give it a bad name without being sure, I’ve waited. I can now declare – the Desire HD does not have a battery life issue!
Read on after the break for how you can make yours last 24 hours on one charge!
Let me explain first of all, why I don’t think there is an issue. My Desire HD, last night and today, has shown better battery life than my Samsung Galaxy S and Nexus One ever did. It will probably continue to improve for the next week too.
Yesterday, after 10 hours of medium to light use (screen on was 40 minutes), I was still at 59% battery.
Today, I’ve been off for 12 hours and I’m still at 48%. The screen has been on for 50 minutes, 30 minutes of streaming music via bluetooth, 1 hour of podcasts playing through my earphones and a few text messages. Generally, on standby (and not being used) on 3G while at work, it was only using 2% an hour! I’m not [/B]sure any Android phone has ever managed that low consumption for me.
I don’t know how HTC have managed it from a 1230mAh battery, but if anyone manages to produce an ‘extended’ battery that fits, this thing could last a very long time. As for what the Desire Z might be able to do, wow!
So, what have I done to get this? As well as the usual tips I’ve given, here’s a few more for your Desire HD -
Remove apps you don’t use. You’ll need to root your device with VISIONary and then remove system apps like Flickr, Twitter, Stocks, Peep, Gmail and Friend Stream using Titanium Backup.
Syncing kills! Go to Settings -> Accounts & sync and see what apps are set to sync. For me, a big improvement came from turning off syncing my Facebook ‘Live Feed’ (this seems to turn back on at reboot). Also, only have one of the two Facebook apps syncing at all. For me, I stopped HTC Sense, News and Weather from syncing. If you really want these, maybe just drop their frequency an extra hour or two.
Lower e-mail checks. I have 4 e-mail accounts that K9 Mail checks for me. Like the other syncs, I dropped them from 15 minutes, to 1 or 2 hours, 4 for the less important one. Definitely don’t use the push e-mail setting on K9.
Try different connections. Go to Settings -> Wireless & networks -> Mobile networks and change Network Mode. For me, for some reason on Orange in London ‘WCDMA only’ works the best for me.
Calibrate. After 7 to 10 days use, calibrate your battery and you should be good to go, simple as that!
**ADDITION** Once in a while (if not always) try charging via USB rather than mains. It has been reported this is better for the battery and will actually provide better life from one charge. I can’t necessarily say this claim is true, but I have often seemingly got better life from a USB charge. Try it!
Bear in mind, there are people reporting much better life than I get. Some say they can last over 40 hours on one charge.
Also, make use of the ‘Power Saver’ in Settings. I’ve put mine at 30%. When this kicks in I tend to find battery consumption might even drop to 1% per hour, which means it may be possible you could last for 3 days on one charge! I can’t wait to see what happens when we get proper root and can use custom ROM’s!
(source:http://hemorrdroids.net/htc-desire-hd-battery-life/)
<<< Please click on "Thanks" if you found this post helpful, your thanks are very much appreciated >>>​
Looking for general guideline for your Lithium Ion Battery?
Have a look at this http://forum.xda-developers.com/showthread.php?p=15631703#post15631703

i might have to try this on my fassy

Is it necessary to have one of these threads every other day?
Sent from my HTC Sensation 4G

Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.

DirkGently1 said:
Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.
Click to expand...
Click to collapse
Lol. I have 3 spare batteries, girlfriend has 2. Still chew through em in a day
ADR6300

Not really sure anything here is new information...

Cheers, I'll try a couple of these.

How about putting your phone into Flight mode while at work.
I, for my part, get my mails to my desktop machine anyways and i like the fact, no one can distract me while I'm hacking in a gazzillion lines of code.
If it's important my lazy colleagues can use their legs and walk into my office.

flight mode is as good as switching off your phone

My battery already goes down like 1% every hour when the screen is off. So it's fine to me. It's only when I'm actively using WhatsApp, Facebook and Twitter that it goes down faster.
Main killer of the battery is the screen. The screen with high backlight burns through it. While idle it hardly drains.

thanks for this

servellia said:
How about putting your phone into Flight mode while at work.
Click to expand...
Click to collapse
I would get fired if I do that

I think you just made s regular phone from your smartphone
Sent from my Desire HD using XDA Premium App

Good reminders - thanks.

cooooll thanksss

DirkGently1 said:
Turn off your phone. Battery life will be awesome.
Otherwise carry spare chargers and/or batteries. Simples.
Click to expand...
Click to collapse
niceeeeeeeeeee

Thanks for the tips, although if Google just closed maps instead of having it open all the time!
Bet that would save some battery!

Good one to see... thanks for the post

I´ll try this...
Thanks!

I use Juice defender beta with ultimate features and i did calibrate my battery. It's 1:26 AM and through moderate to heavy usage i'm still at 41%. It still has a lot to do with your CPU speed (over/under clocked), ROM, Radio and kernel. I'm CM7 Lordmod's CFS kernel and the latest Radio from AT&T Stock (I have the Inspire the Desire HD's identical cousin.) and a RIL to match. Oh and I'm Overclocked to ~1.2 GHz using the ondemand governor.

conservative cpu governor up/down thresholds, and their defaults

I did an experiment with some interesting results. It started out as my beginner's attempt to compare two kernels.
It evolved into providing insight (I think) regarding up/down threshhold parameters for the "conservative" cpu governor
If you dont’ want to read the whole thing, jump to the conclusion section posted at the end.
Phone configuration – installed qkster’s UCLB3 with AT&T bloatware removed, added custom kernel, rooted.
To remove variable cpu loads, I turned wifi/data off and turned off the continuously-running programs that I have installed myself (Power Tutor and Tasker).
To create a steady cpu load, I started the program “relax and sleep” (calm background noise program, available for free). I checked one audio channel in the program, and pushed back button to place program in the background, still creating noise. (I think relax and sleep is a good choice of program for cpu testing in general because it allows to check variable number of channels which does put variable cpu load.. although in this case I only used only one channel.. and note that you cannot recreate this experiment if you use mp3 music app instead, because it uses much less cpu than one relax and sleep channel)
Then I started setcpu for monitoring and experimentation. Repeated with several different kernels.
Results with Entropy’s daily driver kernel.
I set the test setup in setcpu to conservative governor, Fmax = 1200, Fmin = 100, i/o scheduler = noop.
The cpu frequency in Mhz now has the following pattern:
800, 1000,800, 1000, repeat ... (frequency changing approx once per second)
Results with with Zen Infusion-Z A/1600 kernel.
I set the test setup in setcpu to conservative governor, Fmax = 1200, Fmin = 100, i/o scheduler = noop (same as before, intending to compare the performance of the kernels).
The cpu frequency in Mhz now has the following pattern:
1200 (constant).
ok. On the surface one might conclude Entropy’s kernel is somehow handling the load better without ratcheting up the frequency. But the story gets more interesting than that:..
Next I tried Zen’s same kernel Infusion Z/1600 with everything the same except change the cpu governor from “conservative” to “on-demand “
The cpu frequency in Mhz now has the following pattern:
200, 400, 200, 400, 200, 400, 200, 400, 200, 400, 200, 400, 200, 400, 200, 400, 1200 repeat
(changing about once per second, mostly 200, 400, pops into 1200 only very infrequently).
But wait! The "conservative" governor is supposed to be better on the battery than the on-demand governor, and yet for the exact same conditions, we’re gettings higher cpu frequency (1200 constant) with conservative than with on-demand (mostly 200/400 with occasionaly 1200). It’s the exact opposite of how it's supposed to be. Surprising, don’t you think!!???!!
So now let’s look at some other governor settings that don't seem to get much attention.
Go to “governor” page of setcpu with “conservative” selected on the main page. The following values appear repeatably after kernel installation for each kernel, so I am ASSUMING these are default values provided in the kernels themselves (open to comment if I have somehow come to the wrong conclusion)
For Zen’s Infusion-Z (A or B, 1600 or 1400)
up threshold = 80
down threshold =20
(also freq step = 5, sampling rate = 78124 although I don’t think these are important for this post)
For Entropy’s DD
up threshold = 50
down threshold =35
(also freq step = 20, sampling rate = 40000 although I don’t think these are important for this post)
(both kernels have sampling down factor = 1, ignore nice load = 0).
I think we can explain my "experimental" results by examining the above up and down thresholds and making some assumptions about the nature of the load (my assumptions are admittedly contrived in attempt to explain these observations, but they seem reasonable to me).
I ASSUME the steady cpu load I have created in my steup varies in the range 350-400 Mhz quasi-steady state (not perfectly constant due to other processes jumping up in the background).
I ASSUME that before the steady cpu load is reached, there is a temporary increase in cpu loading to 700Mhz or more associated with me flipping screens around to get from the relax and sleep appliation to the setcpu application. Within several seconds, this temporary increase will be gone and only the quasi-steady portion 350-400 Mhz remains.
First look at performance of Zen's Infusion-Z A/1600 while in conservative with default settings in the above experiment. That initial spike of 700Mhz load was enough to get us above the up-threshhold of the 800M-hz level (80%*800Mhz = 640Mhz) and push us to 1200M-hz (1200 comes after 800 in progresion for Zen A, which has no 1000). Once we got to 1,200Mhz, we are NEVER going to get down from there until we reach a load corresponding to the down-threshhold of that level which is 240Mhz (20%*1200Mhz = 240Mhz). And with my relax and sleep application running at 350-400Mhz, it won't happen. That is quite a depressing thing to think – I could put my relax and sleep on for an hour as backgorund noise, and my cpu would be buzzing at 1,200Mhz even though the load is only 350-400Mhz.
This seems very undesriable for battery life.
Now lets look at performance of Entropy’s daily driver in conservative/default setings in the above experiment. The postulated 350-400Mhz cpu load occasionally exceeds the up threshhold of 800Mhz (50%*800Mhz = 400) and once in 1000Mhz occasionally drops below dropout setting of the 1000M-hz (35%*1000Mhz = 350). (And now you know why I postulated 350-400). I have two comments about these Entropy results. The first is minor/tangential, the second more important.
1 - First comment (minor/detour) has to do with cycling between different cpu frequencies which is created by the governor (not the load). I don't think it's any problem at all, but this type of cycling is more likely to occur when the diferences between adjacent frequencies are large. For example let’s say the cpu load was rock solid pure steady state (not varying) at 250Mhz. The up threshhold for 400Mhz setting is 200 (50%*200) while the down threshhold for 800Mhz is 280 (35%*800). So we have postulated a situation where the cpu demand is pure steady state (250Mhz), yet the governor will never find a steady state solution... if it’s in 400Mhz it wants to upshift and if it’s in 800Mhz it wants to downshift. Again I don’t think it’s a problem (it's probably ok to let the two frequencies time-share back and forth) but there is a strategy to avoid it if we want to avoid it, as follows. Considering the highest possible ratio between adjacent frequencies (for these kernels) is 2.0, then we should set things so the ratio of (UpThreshold / DownThreshold) > 2.0 in order to avoid this cycling (which is probably not a problem, more later)
2 – Second comment is more important because it relates to battery usage (as I percieve it). Original postulated load that explains this experiment results is 350Mhz-400Mhz. Yet the cpu is running at 800-1000Mhz. Twice as high. That’s wasting some battery I think.
To summarize results so far, it seems to me that Zen’s kernel default thresholds have potential to waste battery due to low down threshhold (20%), which can keep it at high CPU rate forever, even though the load has decreased substantially. In theory we could be setting the cpu almost 5 times as it needs to be in the situation where steady load decreases to just above 20% of the higher level.. The Entropy’s kernel default threshhold have potential to waste battery due to the low up threshold (50%). In theory we can be setting the cpu almost twice as fast as it needs to be in the situation where the steady load increases to just above 50% of the lower level. Entropy's kernel defaults also create the potential for continuos cycling between frequencies even in the presence a of perfectly steady cpu load, since ratio up/down is less than 2 (I don’t think that's a problem, the only reason I mention cycling is because it feeds into my strategy for selecting down threshold - see below).
So what settings should we use for up/down thresholds? Actually I haven't done my complete due diligence in searching before posting this thread, if someone has a good link with recommendations and/or discussion on this subject I'd be interested. I have seen the generic xda thread on governors and I don't think it was covered there in terms of specific recommended values. Here's my thought process fwiw:. Higher is better for battery on both numbers (at some possible expense of performance). I remember seeing on other sites a default up threshhold of 95% (listed, but not discussed). That makes sense to me for battery saving... shift up at the last minute. Perhaps this high value gives small slowing of response to demand increase, but I don’t think it’s much slower (especially for rapid cpu load increase which is the most critical for response...rapid increase means short time to get from 50% to 95%... short time means not a big response penalty difference) and certainly it seems worthwhile to try to strive for an efficient operating point in long-term steady state. Additionally, we're talking about the "conservative" governor which is supposed to favor battery (we can set up a setcpu profile to invoke on-demand or interactiveX in situations when we want more responsiveness and don't care as much about battery, at least these are availble in Zen's). I don’t recall seeing any number for down threshhold, but should be high as possible again to save battery. How high? I don't know. The only way to put a limit I can think of it is to impose an arbitrary (maybe unnecessary) requirement that we don't want any cycling in pure steady state as discussed above. This means we need down threshhold at least a factor of 2 below up. So I pick 95/2, rounded down to nearest round nubmer of 45%. There may be further improvements if we drop that requirement to avoid cycling and allow even higher down-threshhold, but at least we know the down threshhold of 45% would seem to have moved in the right direction for battery from the defaults. So up/down 95/45 is my pick for now.
Using conservative governor with 95% up threshold and 45% down threshhold (still noop i/o) in above conditions on Zen’s kernel, I’m seeing frequency pattern
400, 400, 400, 400, 400, 400, 400, 400, 800, repeat
in other words mostly 400, intermittent jump to 800.
Certainly the up/down 95/45 settings for conservative governor perform better batterywise than the default settings for conservative governor given in both kernels for this one experiment. To me, it seems very reasonable to expect it to also be better batterywise accross a wide range of expected operations, but it's open to comment.
Small detour - why did we do better batterywise on Zen's on-demand default settings than on Zen's conservative default settings for this particular cpu loading?. The settings for Zen's on-demand default include an up threshhold of 95% and no down threshhold. So on-demand governor apparenlty finds some other way to shift down. Since the 20% down threshold that was causing the problem in Zen's conservative governor default settings is not present in the on-demand governor... that probably explains why the on-demand didn't get hung up at the higher level and performed better afterwards. Another thing to note, if 95% up threshhold is responsive enough for the on-demand, it should surely be responsive enough for the for the conservative...supports the previous sugestion to increase conservative up threshhold to 95%.
CONCLUSIONS:
There is only thing in this entire thread that I am completely 100% positive about, and it is that Zen and Entropy know lightyears more about this stuff than me. In fact, that is the very reason that I was extremely careful to record the as-found default settings in order to preserve any intelligence that went into those defaults before I started tweaking.
So I can reach one of two conclusions:
#1 – I am completely misunderstanding how this conservative cpu governor works
or...?
#2 – The developers never intended for the “default” values to be used, instead they envisioned the users would adjust them as needed.
In the event that #2 were correct, then it would seem logical for battery-concious users to tweak these up/down threshhold settings of the conservative governor. My thoughts would be to set them to 95/45 by the logic above.... may or may not be considering all relevant factors. I'm open to thoughts and comments....

In the above analysis, I have assumed that power consumed by the cpu can be predicted from the cpu frequency (for a given voltage setting of course).
I now believe that assumption might be incorrect.
The reason I believe it is false is a result of another experiment I just did.
I set the cpu governor to performance to maintain constant 1200Mhz.
Then I looked at the cpu power usage trace in "Power Tutor" program.
I expected to see power attributed to cpu usage as constant, but it was varying up and down.
And by moving the homescreens around, I could create a dramatic and predictable increase in power usage of cpu (as indicated on Power Tutor).
All of this change in power consumption of the cpu occurred while the cpu governor was in performance mode with cpu frequency constant at1200Mhz.
I didn't expect that. I can't really explain it (can anyone else?). But clearly there is more to the story than I thought (assuming that the cpu power usage reported by the Power Tutor is correct, which I'm not sure of either).
To evaluate the battery friendliness of variouis governor settings, it might be more useful to watch the power tutor results when performing the above experiments, instead of just watching the cpu frequency as I did before.

Over my head...

How does the battery cycle pan out?
It would be nice if you or someone else had a spare phone to test this battery consumption theory.
I would wonder if the report of consumption is also correct.
The bottom line that I would be interested in seeing is how long can the phone, running a certain kernel and governor, last.
For example: Charge to 100%. Take off charger. Wifi off, Cell data off and in Airplane mode (removing signal variable).
Then run kernel with governor - record the battery duration.

e.pete - nice work! I appreciate your empirical approach to this topic.
I can add the following: you have described accurately how the conservative governor works. For OnDemand, the governor behavior results in the CPU at max under load and minimum when idle, with a smaller amount of time being spent at the steps in between based on thresholds. On my phone today with OnDemand, for example, I'm at 1600mhz 6% of the time, 100mhz 5% of the time, and 800mhz 2% of the time. Deep sleep is 83% and the other CPU frequencies are all below 0.5%.
In general use, conservative should be kinder to the battery and to the hardware. The recommendations I have seen for Linux platforms is to use conservative where battery life matters and ondemand when there is a constant external source of power (i.e. PC or server). Of course, actual use determines how the governor performs. Most smartphones have a lot going on even when the screen is off. A good indicator of average CPU use over the course of a day is CPUSpy. This app, combined with a decent battery monitor can help tell the story from a macro/whole system perspective over time. On the "be kind to hardware" topic, conservative should increment and decrement to adjacent frequencies based on load. This behavior might be happening too fast for SetCPU or other realtime monitor to capture..that's where CPUSpy can show what is happening over a larger period of time. These more gradual transitions may result in less wear and tear on the phone hardware, but I have not seen any significant evidence that this is a factor in the usual life span of a smartphone. (On the flip side, setting the governor to performance and OC to max setting...that is NOT recommended and could harm the phone).
That said, the two kernels you tested have the following default characteristics:
Entropy DD - Conservative/BFQ - Optimized for stability and battery life
Infusion (Bedwa/Zen) - OnDemand/CFQ - Optimized for performance
The Infusion kernels do not include optimization settings for conservative. As you surmised, the expectation is that if you are going to change these settings you have some idea of what you are aiming for and will adjust accordingly.
If battery life is your aim, I've found that the best savings are realized in optimizing transition to sleep when the phone is not being used, minimizing the number of apps that attempt to keep the phone awake, and being selective in your use of wifi and data radios (although too much mucking around with this last option can lead to triggering some of the known bugs in these kernels which manifest as a higher than normal Android OS or Dialer/RILD drains - as seen on the standard battery usage screen in Settings).
On this last topic, there's another thread (which I see you have visited) which covers discussion and work on these known battery drain anomalies: http://forum.xda-developers.com/showthread.php?t=1408433
Here is some additional information on governors courtesy of Big Blue... http://publib.boulder.ibm.com/infoc...?topic=/liaai/cpufreq/TheOndemandGovernor.htm
And a bit more info ... https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling

Truckerglenn said:
Over my head...
Click to expand...
Click to collapse
:what: I'm so glad there are people much smarter then myself here. Great work electricpete :thumbup: even if I followed about half of it
Sent from a de-FUNKt Infuse

Pete - Here's a link to a thread that has a lot of information about governors, i/o schedulers, tweaks, scripts, and kernel objects:
http://forum.xda-developers.com/showthread.php?t=1369817

Thanks everyone, a lot of good info.
Especially Zen, very useful info and links.
It was a very interesting comment about certain governor strategies being hardware unfriendly if they jump increase the cpu from min to max.
I never realized that was a factor (only thought the max speed was important).
But it definitely sounds plausible. Maybe (?) the rapid temperature increase causes uneven temperature (cpu gets hot before attached plate gets hot) and therefore uneven thermal expansion, which causes mechanical stresses. I can imagine there are other subtle aspect of the cycling up/down that can be important. If you have any more info or links on the effects of cpu governor strategy upon hardware life readily available, I'd be very interested to hear it. (If not readily available, that's fine too, I will do some googling).
I did find this link which suggested it's better for the hardware life to run at 100% (I guess for us that's 1200Mhz) than it is to cycle up/down. It's not written about phones but about PCs. There might be some differences in the technical aspects. There are of course big differences in the priorities for PCs... they don't care about power usage as much as phones do, and pc users probably expect a longer life than phone users do.
http://www.overclockers.com/overclockings-impact-on-cpu-life/
Thanks again.
I will report back if I get some free time to continue experimenting... maybe this weekend.

Primary consideration (as you've noted) with smartphones is battery conservation. ARM processors are engineered to operate at multiple frequency steps, and to turn off where possible. Without this capability phones would need a much higher capacity battery. As for PCs, current processors include frequency stepping technology to reduce power consumption and heat, and perhaps extend life by keeping temps lower.
The main conclusion of the article you referenced (which is 13 years old, btw, but does contain a wealth of good foundational information) is that heat is the primary enemy. This is a major factor with smartphones as they have limited ability to dissipate heat. An Infuse running at 1200mhz (or 1600mhz OCed) confined to a purse or pocket, or (as reported in these forums a while back) under a pillow gets hot very quickly. This will lead to conditions that will harm the phone. At one time, my phone had an error condition causing the Dialer to go crazy (rild process) and peg the CPU at 100% for an extended period of time, while the phone was also plugged into a charger (thus heat from the charging process too). The end result of this was a temperature that tripped a heat sensor threshold, causing the phone to shut itself off. So there are, at least, limited protections against extreme events.
As I noted above, I've not seen any evidence that the normal (or even OCed) frequency stepping that occurs with smartphones leads to failures within the normal in service period for these devices - 2 to 4 years in most cases. Running at 100% all the time may put your phone's health at risk and will definitely impair your battery life.

Zen - Good points. One thing I do take away from the article (along with your comments) is the cuumulative effect of cycling, So when I settle on up/down threshholds, I may try to avoid putting them too close together in order to avoid extra cycling (keep Max/Min threshhold ratio >2). Although I do realize these particular cycles between two adjacent frequencies are not as bad as bad as the cycle between min and max frequency.

more test results
I have completed some testing using PowerTutor and results reported in attached spreadsheet.
I would say the results only muddy things further. Don’t read any further if you don’t have a tolerance for ambiguity.
SETUP (common to all tests)
In all tests, I had similar setup as in the original post: 1 channel of “relax and sleep” running to create a constant cpu load, and all other continuous-run programs turned off except power tutor.
Some other details common to all tests: Tasker off, Wifi off, data off, Power Tutor on
No uv
Noop I/o governor used throughout.
WHAT CHANGES BETWEEN TESTS:
See the spreadsheet, tab labeled “summary”.
The things that changed between tests are in rows 3 thru 8, labeled “Tested Configuration”
As you can see, between tests, I varied the Up threshhold and Down threshhold. I varied the kernel. I varied the governor (mostly conservative, but performance used).
WHAT WAS RECORDED DURING EACH TEST:
1 – Recorded power usage of CPU, LCD, Audio as reported in Power Tutor over the course of one minute. I converted them to battery %/hr (conversions shown in tab “Notes”) and listed them in rows 12-14
2 – Recorded the actual cpu frequencies seen in setcpu “home” screen, similar to original post and listed these in row 15. I attempted to guess the average frequency over time and put this in row 16.
3 Rows 18-23 are the Quadrant results for the six categories that Quadrant reports (yes, I know people don’t like Quadrant, just recorded as a datapoint)
WHAT PATTERNs EMERGE:
1 – Entropy’s DD and Zen’s Infusion-A use comparable power (as reported by Power Tutor) in this particular experiment.
2 – Zen’s Infusion does better on quadrant score in this particular experiment, when both are set at the same governor configuration (100-1200, conservative), . Not surprising since Zen said he has optimized for performance.
3 – How does the governor frequency affect power usage? This is the muddy part. There is no doubt that if we blindly take the data at face value, then there IS a correlation between cpu frequency and power attributed to the cpu by Power Tutor. However the correlation that emerges from the data is in the opposite direction from what anyone in the world would think: this data suggests that increasing CPU frequency causes decrease in power consumption reported by power tutor. See tab labeled “chart 1” for graphical depiction of this result.
As you can see in the graph, there is not a random spread of results (as would be the case if random unacconted-for errors were at work). There is a definite correlation. What it suggests perhaps is that there can be a systematic error in the way PowerTutor measures power that depends on cpu frequency.... in other words the error itself (between measured and actual) somehow depends on cpu frequency.
So, I am just reporting some results. I am definitely not suggesting anyone overclock to save power (that would be truly bizarre and I’d probably be kicked out of xda for suggesting something so silly).
On the other hand, as stated in the 2nd post of this thread, I’m still very leery of using cpu frequency as an indicator of power that cpu is drawing... because there is just too much going on inside that black box that I don’t know about. For one thing, the cpu itself may draw different amounts of power at a given frequency depending on it’s loading because the registers may not be doing anything at low loads. For another thing, there are a lot of other things in the phone (like RAM, bus) that may draw some power but probably get lumped in with the reported cpu power in Power Tutor and others. Perhaps the cpu is somehow more efficient at interfacing with these others parts of the system when cpu is at high speed, enabling it to reduce the power they draw. The point is, it’s a lot more complicated then I assumed in my first post.

I have heard Entropy mention that before changing kernels we should always reset UV settings (and reboot) and reset other cpu related settings (Fmin and Fmax I assume).
I would like to add another item: always uninstall setcpu before changing kernels and reinstall it after you change.
The reason: I have seen some very weird results of setcpu when I left it installed in between swapping kernels. Like for example cpu running at 1600Mhz even though Fmax is 1200Mhz and there are no profiles allowing 1600. Those weird results are not included in the above data (I observed the frequencies during each trial as reported in the spreadsheet).

Power Tutor has a great interface and very detailed stats available. Seems to have great credentials based on their website.
But I can only conclude we can’t trust it for our particular phone because of results above (power draw goes down as cpu speed goes up) and some other results I have seen (it seems to suggest that power used by my display does not change depending on dark/light backround, and also seems to suggest that power used by the phone does not change when I change the volume of music playing).
So, I’m looking for another way to be able to track power usage closely.
I kind of like qkster’s idea to just watch the battery go down.
I’d like to try to automate that using Tasker. I can write a program which will help me build a log of power usage.
The interface will be:
push a start icon and it prompts me to enter description of conditions that will be tested
wait some period of time (this is the constant-load test period that we're evaluating...may be listening to mp3)
push a stop icon and it prompts me for comments about anything that happened during the test.
At time of pressing the start icon, it will also record from the system:
1 - clock time (in seconds)
2 - voltage in millivolts to 4 digits of resolution (like 3784 millivolts)
3 - battery life remaining in percent to 2 digits of resolution (like 43%)
The same info will be recorded from the system upon pressing the stop icon.
All this info will be appended to a logfile and we can compute drain based on change in battery divided by change in time.
I can get these voltage and % life stats using the method suggested by Brandall’s tutorial here:
http://tasker.wikidot.com/using-linux-shell-with-tasker-for-a-technical-battery-widget
I couldn’t get the grep command to work, but I can still extract the required voltage and percent-life-remaining from the Battery sysdump using the tasker variable splitter command (I’ve already got that part programmed).
No-load voltage has a roughly known relation to battery life, but there’s also the matter of voltage drop accros the internal battery impedance that varies with load at the time of the measurement, so we don’t see no-load voltage, we see something lower which makes the whole thing somewhat variable.
Percent Remaining is the exact thing I want. But it is only given rounded to two digits, (43%). If I wanted to do a trial run listening to a 5-minute MP3 draining something like 12% per hour, the battery drop during that that 5 minutes will be only around 1%... the difference between two kernels or cpu frequency settings will be only a very small fraction of that 1%, so comparing the start and stop values which are both rounded to 1% would introduce an enormous error compared to the thing we're interested in. I can surely reduce that error by working with longer times, but that starts to become a PITA. That may end up being the only solution, but if there's any way to avoid it I'd like to be able to gather data in shorter chunks.
Which leads me to a QUESTION:
Does anyone know whether there is any way to retrieve or estimate “battery % remaining” with greater resolution that two digits (ie 43.26% instead of just 43%)?

unintended consequences from changing up threshhold
I used the following setup for almost a month:
Zen’s Infusion A Kernel (with my stock GB), conservative governor
UpThreshold = 95
DownThreshhold = 45
Only twice during the month, I saw the following:
Received a phone call. I could see the name of the caller. I couldn’t hear the caller. When I finally got hold of them later, they told me they could hear me even though I couldn't hear them.
That was very tough to figure out because it only occurred on two out of probably 30 or 40 phone calls received in a month.
The two phone calls did originate from cell phones in the same geographic area (near my work, an hour away from my home).
Then I had a breakthrough when I set up my work voicemail to automatically call my Android phone. Almost every time it called, the problem appeared (I couldn’t hear the robot voice telling me I had a message).
I kept leaving myself messages to reproduce the problem and narrow it down.
I found out it only occurs when my phone is asleep at time of the call (doesn’t occur if phone is awake at time of the call).
I removed my UV and problem continued.
I adjusted my governor and could make problem go away.
I narrowed it down to the up threshhold.
Repeatable with 95/45 up/down, the problem occurs.
Repeatably with 80/45 up/down, the problem does not occur.
I have gone back and forth between those two settings at least four times and each time it confirms the symptom is directly related to the governor setting.
Exactly why that is I’m not sure. Maybe the cpu is to slow to wake up to handle the call? Sounds kind of hokey, but I guess it doens’t really matter.
The bottom line for me: 80/45 is a great place for me to stay. Eliminates the “can’t hear caller” problem and still does pretty good at preventing cpu from going to high frequency when listening to my relax and sleep program for long periods of time.
If anyone has gone to 95/45 based on my recommendation, you might rethink it, especially if you see unusual behavior.

[APP] Battery Saver [FEATURED ON BEST APPS OF 2012 ON XDA]

I found this on the xda top apps of 2012...a battery saver ...will try and revert back...for thise who want to try:
http://forum.xda-developers.com/showthread.php?t=1947559
For those too lazy to go to the link [some people like me ]
One Power Guard is a unique battery enhancement tool designed to conserve your battery power an increase uptime on rooted Android smartphones/tablets. One Power Guard will decrease your charging time and increase your device performance while also increasing your uptime. One Power Guard will also protect your device from faulty applications that can: cause over-heating (decreasing your battery lifespan); run down your battery; prevent your device from deep-sleeping; and, use unneeded resources such as WiFi and Cell Data. By selecting any one of the six customized power-saving modes, you are able to match your power savings needs to your lifestyle. There is no need to purchase extra batterys or a larger battery, just use One Power Guard.
Features
1. Extends stand-by time and battery life; optimizes charging parameters
2. Optimizes system kernel and CPU usage to improve device performance
3. Six (6) customized power-saving modes to suit different scenarios
4. Proactively guards from power-killer apps and safely shuts down useless power-consuming programs
5. Fast ON/OFF settings for 100% system customization
6. Intelligently switches to/from WiFi/Cell data to preserve battery life
7. Professional Tips on power optimization
AI Mode: Artificial Intelligence Mode. Learns from how you use your device.
By default, this mode uses the Ondemand governor - under increasing system load, the CPU is immediately set to the maximum frequency of the kernel. As system load decreases, the CPU frequency slowly decreases to the minimum frequency of the kernel.
NOTE: If your kernel supports over/under clocking you may want to change the upper/lower frequency bounds to stay within safe limits.
By default, AI Mode uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices. Changing the governor and the I/O scheduler are permitted but, that defeats the benefits of the AI mode. Use Custom mode, if you want to explore different settings.
Powersave Mode: A balance between device usage and power saving.
By default, this mode uses the Powersave governor - keeps the CPU frequency always at the minimum, it is the least power-hungry and the least responsive.
By default, this modes uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices.
Game/Video Mode: Useful mode for playing games and watching video - enjoy smooth operation and a smooth video experience.
By default, uses the Performance governor - sets the min. frequency as max. frequency, this mode is the most power-hungry, but is also the most responsive. If your kernel support overclocking you can set a higher frequency.
By default, this mode uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices.
Daily Mode: Useful for day-to-day operation, featuring responsive and reasonable power usage.
By default, this mode uses the Ondemand governor - under increasing system load, the CPU is immediately set to the maximum frequency of the kernel. As system load decreases, the CPU frequency slowly decreases to the minimum frequency of the kernel.
NOTE: If your kernel supports over/under clocking you may want to change the upper/lower frequency bounds to stay within safe limits.
By default, this mode uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices.
Standby Mode: Useful for maximum battery conservation.
By default, this mode uses the Powersave governor - keeps the CPU frequency always at the minimum, it is the least power-hungry and the least responsive.
By default, this modes uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices.
Custom Mode: You choose everything: the governor, the min and max frequencies, and the I/O scheduler. Do a Nandroid backup first. Have Fun!
Test One Power Guard for yourself?
1. Fully charge your battery before you go to bed. In the morning, check your battery status and note how much is remaining.
2. After installing One Power Guard, fully charge the battery before you go to bed. In the morning, check your battery status, you will be impressed by the power savings!
3. To compare the optimization results, you need to restart the phone so that you have a clean environment.
First of all, what are the common complaints with android smartphone devices? Issues such as: system halted; application crashes; slow booting; and, battery life.
A year ago, I purchased my first android phone and installed CM ROM. Within months, I became very
annoyed that my battery did not last the entire day. I could go to bed, with a full battery charge, and awake in the morning to find that the battery charge had dropped significantly overnight. I found this situation to be unacceptable! To solve this, I downloaded power-saving applications.
Every day I would install a different power saving application, charge the battery to full power before bed, and then check the battery in the morning. After a month of testing power saving applications, I didn't find a satisfactory solution and some of the so-called power saving apps even made the battery drain faster. So, I thought I would create an app for myself, that could tweak system parameters and help save my battery. Nine months ago, I started writing a power tweaking application for myself. I studied the intracies of the android power management mechanism and within a few months I had the basis for an application that could optimize my power management. Everyday, I tweaked the power optimization parameters and tested each night. One morning, I awoke and was thrilled to discover that the battery charge had only decreased by a small amount. So, I turned my personal power saving tweaker into a user-friendly power saving application that anyone could use. I am sharing my application, One Power Guard with you.
If you would like to try One Power Guard, Download from onexuan.com
To save power, One Power Guard do some optimization:
1. Extends stand-by time and battery life; optimizes charging parameters
2. Optimizes system kernel and CPU usage to improve device performance
3. Six (6) customized power-saving modes to suit different scenarios
4. Proactively guards from power-killer apps and safely shuts down useless power-consuming programs
5. Fast ON/OFF settings for 100% system customization
6. Intelligently switches to/from WiFi/Cell data to preserve battery life
7. Professional Tips on power optimization
Why do you need One Power Guard? and Test One Power Guard for yourself.
1. Fully charge your battery before you go to bed. In the morning, check your battery status and note how much is remaining.
2. After installing One Power Guard, fully charge the battery before you go to bed. In the morning, check your battery status, you will be impressed by the power savings!
3. To compare the optimization results, you need to restart the phone so that you have a clean environment.
Why does it run in the background?
We have a "safe clean" technology, primarily in order to protect your battery. Needs to run in the background, to periodically safe clean.
What is a safe clean?
Android has a app process management mechanisms, when a process is killed by third-part applications, the android system will determine whether the process will be run again, if it is, th e process will run, the kill process will repeat thereby creating an infinite loop, resulting in increased power consumption. Therefore, you should consider uninstalling third-party process management software.
Why is my device slow after setting a mode?
I want to talk about this story. One night, a user contacted me about an issue that came up after installing the 2.1 version of One Power Guard. He said his device lagged in Standby mode. I told him that we can work together to solve his problem. After work, I went back to my dorm. I started to write a test interface for him and 1.5 hours later, we started testing. He began to test my ten-step interface - each step ran well. But the issue was not resolved. I asked him to select AI mode - his device lagged. What we found is that his device did not support changing CPU frequencies. So my judgment was that this was an I/O scheduler issue, it was set to "CFQ". I asked him to try changing his I/O scheduler. (His Rom Only support CFQ and Noop). He changed to "Noop" and the lag went away - issue resolved!
Final conclusion: Tweak the settings until your device performs to your satisfaction.
The software allow the common user to gain the benefits without having to understand the technical stuff thus the 6 modes for common uses like gaming. Any "battery saving program" is truly just a front end to tweaks and settings changes that can be done manually. The point is it makes making those changes much easier.

what about a phone without a root...suggest a nyc baatery saver...in need of it??
Sent from my HTC Wildfire S A510e using xda app-developers app

ajiinkya said:
what about a phone without a root...suggest a nyc baatery saver...in need of it??
Sent from my HTC Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
Try juice defender or ds battery saver both are nice and effective
HIt tHnX iF i hElP u
Sent from my GALAXY RoYaL

i wud try it n feedback u soon
Sent from my HTC Wildfire S A510e using xda app-developers app

it works really well! Improved my backup 5x on 10.1 !!
Definitely use it guys

F3niX said:
it works really well! Improved my backup 5x on 10.1 !!
Definitely use it guys
Click to expand...
Click to collapse
Glad I could help!
Nokia 2110-->Sony Ericsson k750i -->Nokia 5233 --> Samsung Galaxy R

It's really nicest, best battery saver
Thanks buddy
Sent from my GT-I9103 using xda app-developers app

thnks for d link buddy:good:
its really works good.

d2dprajesh said:
It's really nicest, best battery saver
Thanks buddy
Click to expand...
Click to collapse
TUSHARKATE007 said:
thnks for d link buddy:good:
its really works good.
Click to expand...
Click to collapse
Friends can some one please tell me what are the setting's you are using because i haven't seen any improvement ....

mj.vikram said:
Friends can some one please tell me what are the setting's you are using because i haven't seen any improvement ....
Click to expand...
Click to collapse
Neither do I. If you already have set up setCPU profiles to automatically adjust the cpu freq and governors according to diff situations then you don't need this, coz essentially its doing the same thing. For those who have never explored setCPU and don't want to manually do things, this is a good alternative. I've always used a combination of SetCPU and tasker to get the most juice out of my battery. I never rely on "Battery Saving Apps" that keep running in the background. Just my opinion.

This app really save's your battery life and here is the proof!!https://www.dropbox.com/s/tk7tx9yi19i5jra/Screenshot_2013-01-21-19-29-38.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
I am using standby mode and 54hrs have completed with out a charge and still 60% is left..
---------- Post added at 08:42 PM ---------- Previous post was at 08:40 PM ----------
The-Droidster said:
Neither do I. If you already have set up setCPU profiles to automatically adjust the cpu freq and governors according to diff situations then you don't need this, coz essentially its doing the same thing. For those who have never explored setCPU and don't want to manually do things, this is a good alternative. I've always used a combination of SetCPU and tasker to get the most juice out of my battery. I never rely on "Battery Saving Apps" that keep running in the background. Just my opinion.
Click to expand...
Click to collapse
[/COLOR]I am using standby mode and 54hrs have completed with out a charge and still 60% is left..

Hi, thanks for this info about your personal battery journey Its super cool. I gots 2 questions,
1. What if a user like me doesn't know what kernel I gots and don't want to damage the phones anything, so I have not a clue about setting to prevent over clocking (never cared about it anyways) should a basic user like myself stay away from this application, if it could damage it somehow?
2. If I want to keep my cell from going into deep sleep because then my tethering application automatically turns off, and no way to stops that. Does this application have the reverse ability to prevent it rather then prevent from preventing it. (You know what I am saying)

[APP][3.0+] Battery Utility - Advance Battery Saver with Advance Android Tweaks

Battery Care : We will keep your Battery safe & Make sure your devices is Fast, Faster,, faster!!!
Playstore link : https://play.google.com/store/apps/details?id=com.blcpk.toolkit.app
Ad-free version uploaded in OP for XDA members....
We have add most important 15 Key features of Android ; We are very sure after using this application your going to Uninstall around 10+ apps..
Advanced stats
Battery History
Wake lack
Battery stats
Battery Alarm
Power saver
Drain test
Wipe
App Permission
CPU Tweak
Game Tweak
Storage Tweak
System Tweak
Sensor Tweak
Sound tweak
[*]Coming Soon [*]App locker, Screen Dimmer, Screen Off
1 Advanced Battery Stats:
This application will help you understand the flow of battery charging and the detailed usage of the battery. You will have a fair idea on how your device is being charged and the reason it is being drained so quickly. This app will be able to help you take the appropriate action in order to take care of your device`s battery.
1 Charge Levels:
Most of us are curious to know how we are charging our battery of our android devices; this application will help us to understand the complete and detailed information, along with a charging level graph to show you trends of your charging and battery usage.
2 Graphical Stats:
This is one of the premiere advanced battery statistics apps, this will help you to understand what is happening on your device and it`s battery, i.e. Awake, Screen On, Charging, Wi-Fi, GPS, Bluetooth etc. So, you can save your battery.
#################################################
App Permission:
It gives you a useful and detailed view of all of your installed apps, you can easily identify unwanted apps that might threaten your privacy, and bloatware as well. You can uninstall those unwanted apps.
1. You will have the option to short it out based on the name of the application
2. You will have the option to short it out based on the score (harmful application)
3. Also, you can short by Permissions
#################################################
Battery Alarms:
One of the most important features which is needed for any device, battery alarms can save energy, health and much more.
Battery Alarms Types:
1 Fully Charged
2 Charge Drop below (Set as required)
3 Charge rise above (Set as required)
4 Temperature rise above (Set as required)
5 Health Fails
#################################################
Battery History Data
You can find out yourself what is happening on your battery, i.e. Charging Level, App usage, Data Usage, Consumption.
1 History Data: This helps you to find out detailed battery history 100 to 0% level of battery what happened on 99%, 25% or 32% or anything as you required.
2 Battery Usage Indicator: This lets you understand the specific app and features that consumes more battery, i.e. Screen, android system, Wi-Fi, Apps, FB etc...
3 Charging History: The battery history data has complete and detailed information about the battery including Power, Volt, Screen, Hardware etc...
Smartphone users would love this app, it will allow you to understand how many times you connected the charger and disconnected it, what the charging level is, current battery level, battery volt, weather you used USB or AC in order to charge your device. You can download the data and share it.
#################################################
Battery Stats:
This will give you battery stats and help you understand what is consuming more battery, Audio, GPS, Wi-Fi, 3G etc... Battery Stats include:
1 Chart View
2 Pie View
3 Stat Views
#################################################
CPU Tweaks:
This will increase the CPU speed of your device and help you control what you are utilizing and how much. So you can speed up your devices as you need... Increasing CPU speed will make your device work more quickly. However not enough speed could damage your device. This app allows you to:
1 Tweak
2 CPU
3 Volt
4 Settings
#################################################
Battery Benchmark Testing
We all love to know how many hours of video, audio or browsing we can do with our beloved android device. This app is really meant for the device optimizers.
The test runs until the battery reaches 15% and at that point the test is complete and test results will get displayed.
This utility tool is used to measure the battery statistics on your Android device with respect to Video & Audio playback and Browsing the internet.
This App will allow you to calculate the battery usage of an audio file with a specific bit-rate or a video file with a particular resolution and see the battery consumption rate/minute ratio. You can also check the battery consumption rate for 10 standard URL's with the browser test:
1 Audio
2 Video
3 Browser
#################################################
Game Tweaks:
All Android gamers love to play without frequent hang ups or crashing. We have made a simple Android tweak which can improve your device with complete performance and great gaming experience. Game Teaks include...
1 Stock Rom – Tweak
2 Custom Rom – Tweak
3 Tweak – Uninstaller
How to install the Tweak:
1. If you are still in Stock OS, you need to download the Stock ROM Tweak; we also have Custom ROM Tweak.
2. Once you completed, turn off your device and reboot into Recovery mode (google on more information on recovery mode)
3. Once your device is rebooted into recovery mode, you will find an option called install ZIP from SD card, you need to select that option, this will install the tweak on your device.
4. Once it’s complete, you need to reboot your device. You will feel the improved device performance.
Please note (Tweaks can damage your device, we are not responsible for any damage)
#################################################
Power Saver:
This is a must have for any Android Device out there, you must define it`s worth for yourself. You can save your battery 2+ times with this power saver. It includes...
1 Night Mode
2 Short Intervals
3 Traffic Limit
4 WiFiWhite list
5 Timeout
Mobile Data Controller: It turns off or Turns on as you needed.
#################################################
Sensors Tweaks:
This will help you to understand weather the sensors are working as expected, you can test all the sensors yourself.
#################################################
Sound Tweak:
Music lovers will love this too, you can increase the pre-sets for the type of music you are interested in listening to.
1 Normal, Classical, Dance
2 Flat, Folk, Heavy Metal
3 Hip Hop, Jazz, Pop & Rock
#################################################
Storage Tweak:
This will help you to understand about your device, CPU, RAM, All the hardware information, you can setup the Nand , SD card memory performance as you need, This will make your device perform better.
You can easily find out yourself, how much your system used, Data, Cache, SD card.
#################################################
System Tweak:
Everyone wants their Android phone to be fast without hanging up or crashing, we have made some simple Android Tweaks which can improve your device`s performance and Save the most amount of battery. They are:
1 Stock Rom – Tweak
2 Custom Rom – Tweak
3 Tweak – Uninstaller
=========================
How to install the Tweak:
1. If you are still in Stock OS, you need to download the Stock ROM Tweak; we also have Custom ROM Tweak.
2. Once you completed, turn off your device and reboot into Recovery mode (google on more information on recovery mode)
3. Once you’re rebooted into Recovery mode, you will find an option called “install ZIP from SD card” you need to select that option, this will install the tweak on your device.
4. Once it’s complete, you need to reboot your device. You will feel the improved device performance.
Please note (Tweaks can damage your device; we are not responsible for any damage).
#################################################
Wake lock Activities:
You can easily find out yourself, which app or hardware is consuming a lot of memory and power.
1 Kernel Wake locks,
2 Partial Wake lock,
3 CPU States
Kernel wake locks: These are low level/hardware wake locks from the kernel. We can only reduce these by modifying the kernel or reducing the usage of a certain feature of the kernel. By researching these we can improve the battery consumption and performance of the Kernel.
Partial wake locks: These are wake locks from apps. These can be reduced by uninstalling or disabling features in software. We can talk about those here too, though it shouldn't be the focus as the answer will be "Uninstall/Disable feature X and talk to the app author". Preferably we should talk about partial wake locks from Google services like maps and latitude.
CPU: The numbers reflect the percentage of the time since the last screen update that the CPU spent in each state. The output for this line requires past history, and it is not shown on the first display that is produced.
Other Weak locks: It is important you find out where your major battery consumption is, Deep Sleep, Awake, Screen On, and Wi-Fi on, Wi-Fi running, Data Connection, or Screen Dark.
Process: You can find out which application consumes the most Battery juice. This is a collection of interrelated work tasks and an initiated response to an event that achieves a specific result for the user of the process.
Networks: This will help you to figure out what is happening on your network connection, what the battery power consumption is, the interval etc...
Others depend on the usage of the application and etc...
#################################################
Battery Wipe
This will wipe battery stats data and allow android OS; it will also regenerate the new battery data file
#################################################
Calibrators: You should use this when you think that your battery is acting weird and performing poorly. Here is how to use Battery Calibration:
1) Charge your device until the battery reaches 100%.
2) Click 'Calibrate!' button.
3) Your battery will be calibrated; you can check the battery performance.
We request you drain the battery for next 3 days after you decide to calibrate your device, 100% - 0% battery. When the third day is up charge your device 0% to 100%. Once you complete the process your battery will be calibrated 100% you will feel the improved battery.
#################################################
Advance Battery Cleaner:
This will kill all the running applications and unwanted processes required. This is how your battery will be saved 2+ times in general.
The battery cleaner will start in Boot-up and start working in the background to save the power.
You can also setup an auto cleaning leave: Safe, aggressive and crazy
You can also setup a security leave to: High, Medium & Low.
Click Thanks Button if you want to support my work

I send you an email. For beta tester

Count me in

Niceee, im always interested in new beta apps, especially when its a battery saver ^_^
Verstuurd vanaf mijn SM-G900F met Tapatalk

I send you an email.

Already Send ...
Sent from Mighty S5 G906s

Reserved

Live
Any clue about play store live Date ?

jacksparao said:
Any clue about play store live Date ?
Click to expand...
Click to collapse
I need more feedback to hit this application in play store. Please give me some feedback dude.

I send u an email

Application published in Google playstore...

Up
Finally Play store link is up..

Please try the application and give a feedback...

woooow, what are you doing with the system tweak dude? in order to save more juice, i tweak my CPU Max Freq UV to 960 MHZ and doin some tweaks on the CPU Gov. Of course by doing this i sacrifice the performance. But then i installed your system tweaks and then boom! all of the scrolling home screen performance become very fast? this including the three navigation bar delay-in-pressing and application opening also now become fast.
I corious, then i open my cpu governor ...maybe you enter an init.d script on it to change the value, but i see there the value is still the same with my "battery saving mode". then i open the animation and scrolling speed, also still the same setting.
is this tweak really increase performance without sacrifice more battery?

Thanks
I will compare with DU battery. ^^

All the CPU/kernel/system tweaks are available only in the pro version. Can't you make them available in the free version even for a while to test?

Nice music but app crashes. Do you need root?
Galaxy Tab S stock 4.4.2
I am trying it now on my SGS 4, rooted, Wanam Lite, Android 4.4.2

Do you need a tester and Russian translator? PM me if you are

The app started up with music, even though I have my phone set to vibrate only. Please make sure that the app is respecting the audio settings of the phone.

Force close on note 10.1
On the 3rd introduction splash screen can see if i can grab log
Running 4.4.2 stock sammy

Performance governor switch

Why I have to use governors that save power, this is not phone, and radiator on this tablet is finally made as it supposed to be (actually present now not absent duh), so throttling and heat is not there. Conditions have changed and we should use performance governor! After overclocking my desktop and knowing that i just put it on max frequency all the time knowing that it will be the best performance (though it auto changes power profile in inactivity)
I decided why didn't I do the same with the tablet.
I changed to performance governor and set tresholds up/down 10 points lower/higher in ex kernel for big cluster and everything running smoother, i didn't find any measurable battery toll, not that i would care about it. Though i can see it pulls significantly more current when reloading browser pages like 2000mAh. I automated this kernel profile change with franko kernel m., because I am not sure yet if to put it on permanently if it will causes standby drain, it shouldn't but it can. I find that it noticably faster with heavy tasks, not huge difference, but I I feel it, and higher amperage and seeing larger cores loaded more confirms it.
You can try and share how did it go. Anybody has other advices how to tune this kernel for performance.