Related
I was wondering if the speed mod kernel for the international galaxy s is compatible with the Samsung vibrant
Sent from my SGH-T959 using XDA App
Any Kernel recommended for a stock Froyo Vibrant?
I need good battery life and CWM
mozXegX said:
Any Kernel recommended for a stock Froyo Vibrant?
I need good battery life and CWM
Click to expand...
Click to collapse
any should work i think, overstock always had decent battery for me or try bali uv
Try this. If you get any crashes, reduce all millivolts back -25 each until it's perfectly stable.
Bali-X 1.2 found here: http://forum.xda-developers.com/showthread.php?t=1043947
Get SetCPU off the Market and use these settings:
Conservative Governor
100 - 1200 frequency
1200 at -25mv
1000 at -50mv
800 at -75mv
400 at -125mv
200 at -150mv
100 at -175mv
Screen Off Profile of 100 - 800 Conservative
If you want to tweak out a little more energy savings, though at the cost of some performance, you can set the typical frequency to 100 - 1000, or even 100 - 800.
Be sure to calibrate your battery (charge to 100%, unplug, re-plug, charge to 100%, unplug, re-plug, charge to 100%, unplug, replug, charge to 100%, then either delete the batterystats setting with Root Explorer, or use the Battery Calibration mod from the market once you're done bump charging, but don't bump charge too many times, as it's not healthy for the battery in the long term.) after installing Bali X and setting the voltage tweaks.
Still, the best battery saver of all has to do with your display, as it uses far more juice than anything else. Since it's an AMOLED display, lighter colors burn more juice than darker colors. Use a dark themes for your commonly used programs like Googles http://www.blackle.com/ as well as your messenger, and use black wallpaper.
I'm currently debating buying WidgetLocker, but I'm a bit skeptical since I'm not sure how bad it will lag with my current sleep profile. Can any WidgetLocker users possibly shed some light if they think it will lag on my phone? I'll put my profiles below.
Code:
Temp > 38.6C, Priority: 100, 480 max 160 min, ondemand
Charging/Full, Priority: 75, 710 max 245 min, ondemand
Battery < 25%, Priority: 50 ,480 max 245 min, ondemand
Screen Off, Priority: 25, 245 max 160 min, ondemand
If my sleep profile would make it lag, would bumping it up to 245 max 245 min help any?
Profile recommendations are welcome as well if theres anything that could be done to improve performance without sapping an excessive amount of battery. I have noticed my phone lags waking up sometimes and occasionally just when it's being used.
I would put your sleep profile at either the 2nd or 3rd highest priority - either right after the overtemp profile, or after the "on charger/full" profile.
my profiles usually look something like this (ordered from highest to lowest priority) :
- temperature (can have more than one; highest (over-)temp has highest priority)
- charging/full
- screen off
- battery (can have more than one; lowest battery % has highest priority)
- battery < 101% (this is the sort of like the "off charger, not overtemp, screen on state)
If the "screen off" profile has a higher priority than all the battery conditions, then all the "battery" conditions certainly can only be effective when the screen is on. (Note that the way you have it now, your < 25% battery condition always "wins" over the screen-off profile)
Also, note that your profiles don't contain anything matching the "off charger, 25% < battery < 101%" condition as they stand - what is controlling that, the default profile?
I'm not sure that there are big gains to be had by ratcheting down the min/max cpu frequency for low battery conditions: when you have the display on, it could well be drawing more power than the CPU - so, if your goal is to save battery, it would make sense to have whatever it is you want "computed" to show up on the screen as quickly as possible - so that you can shut the screen off that much quicker.
For the same reason, if most of the time the phone is on you are just "staring at the screen", and nothing is going on in the background, allowing the rate governor to drop to a low frequency saves you only a little bit (if the screen is really the dominant juice-user in that scenario.)
My GSB v1.6 Eris reports using only 2-3 % overnight - it's screen off profile is set to 160/245 - and I seem to be using the "interactive" governor on all profiles ... but I also use Toggle2G with a 10-minute sleep onset delay.
( Probably that means that I don't get email notifications as soon as I could, but that doesn't bother me much - I get them as soon as I unsleep the phone. If you are the type of person that needs to look at their phone every time your facebook updates, then Toggle2G perhaps isn't for you.)
I can't prove it, but so long as you don't peg your CPU minimum frequency too high, and rely on the rate governor to do it's job, most power savings are likely to come from managing the radio state and the screen brightness.
bftb0
What percentages do u recommend bftb0
Sent from my Ginger Tazz using Tapatalk
bftb0 said:
I would put your sleep profile at either the 2nd or 3rd highest priority - either right after the overtemp profile, or after the "on charger/full" profile.
my profiles usually look something like this (ordered from highest to lowest priority) :
- temperature (can have more than one; highest (over-)temp has highest priority)
- charging/full
- screen off
- battery (can have more than one; lowest battery % has highest priority)
- battery < 101% (this is the sort of like the "off charger, not overtemp, screen on state)
If the "screen off" profile has a higher priority than all the battery conditions, then all the "battery" conditions certainly can only be effective when the screen is on. (Note that the way you have it now, your < 25% battery condition always "wins" over the screen-off profile)
Also, note that your profiles don't contain anything matching the "off charger, 25% < battery < 101%" condition as they stand - what is controlling that, the default profile?
I'm not sure that there are big gains to be had by ratcheting down the min/max cpu frequency for low battery conditions: when you have the display on, it could well be drawing more power than the CPU - so, if your goal is to save battery, it would make sense to have whatever it is you want "computed" to show up on the screen as quickly as possible - so that you can shut the screen off that much quicker.
For the same reason, if most of the time the phone is on you are just "staring at the screen", and nothing is going on in the background, allowing the rate governor to drop to a low frequency saves you only a little bit (if the screen is really the dominant juice-user in that scenario.)
My GSB v1.6 Eris reports using only 2-3 % overnight - it's screen off profile is set to 160/245 - and I seem to be using the "interactive" governor on all profiles ... but I also use Toggle2G with a 10-minute sleep onset delay.
( Probably that means that I don't get email notifications as soon as I could, but that doesn't bother me much - I get them as soon as I unsleep the phone. If you are the type of person that needs to look at their phone every time your facebook updates, then Toggle2G perhaps isn't for you.)
I can't prove it, but so long as you don't peg your CPU minimum frequency too high, and rely on the rate governor to do it's job, most power savings are likely to come from managing the radio state and the screen brightness.
bftb0
Click to expand...
Click to collapse
Never a post that isn't enlightening from you.
Yes my default clock profile (710 max 160 min, might bump it up to 245 min) is the one managing the clock rate when the phone is off the charger. As for Toggle2G that might not be a bad idea, I keep my phone on Airplane Mode most of the time I'm at school (horrible signal = battery draining out the wazoo) but it might not be a bad idea to have for when I'm not at school. Of course I'm not sure I would need it though since I have an extended battery, maybe something to experiment with.
As for profiles, something like this?
Code:
Temp > 38.6C, Priority: 100, 480 max 160 min, ondemand
Screen Off, Priority: 75, 245 max 160 min, ondemand
Charging/Full, Priority: 50 ,710 max 245 min, ondemand
Battery < 25%, Priority: 25, 480 max 245 min, ondemand
If you are already using Airplane Mode because of poor signal conditions, Toggle2G won't help much - the battery will drain just looking for voice/1xRTT service (not to mention 3G). I have a pretty good signal where my phone spends most of it's time, including overnight ( -70 dBm to -80 dBm )
ToastPwnz said:
As for profiles, something like this?
Code:
Temp > 38.6C, Priority: 100, 480 max 160 min, ondemand
Screen Off, Priority: 75, 245 max 160 min, ondemand
Charging/Full, Priority: 50 ,710 max 245 min, ondemand
Battery < 25%, Priority: 25, 480 max 245 min, ondemand
Click to expand...
Click to collapse
Seems OK. I have a couple of battery profiles where I slowly drop the max frequency, and make the default condition explicit by using a "battery < 101%" profile, as in:
Pr Min/Max Governor Condition
90 245/480 interactive Temp > 50.0 C *audible alarm
80 245/604 interactive Temp > 45.2 C
70 528/710 interactive Charging
60 160/245 interactive Screen Off
50 160/480 interactive Battery < 15%
40 160/528 interactive Battery < 25%
30 245/604 interactive Battery < 40%
20 480/710 interactive Battery < 67%
10 480/729 interactive Battery < 101%
I'm not sure this really produces much effect in terms of battery savings, though - for instance, it runs counter to my suggestion (above) that it might actually hurt to slow things down with reduced battery reserve because you just end up with the screen on longer.
I'll also mention that for a period of time I was actually convinced that using setCPU was causing random freeze-ups when used with certain combinations of the CFS kernel, governor choice, and min frequency - and so I didn't even have it installed on my phone. I only recently put setCPU back on my phone because I was noticing that CPUboost settings did not seem to be sticking even within the same session (perhaps I was misinterpreting something, I'm not sure). No random freeze-ups lately.
Because some of the things which actually drain the battery - cell radio, screen time on & brightness, 3G activity level, etc., are so highly variable, I'm not sure that any of the reports on this forum (including mine) can be regarded as particularly meaningful. It takes real dedication to the task (creating reproducible signal conditions and compute/activity workloads) to be able to produce quality data about battery usage. Most folks need to use their phones throughout the day (moving continuously from place to place with widely varying signal levels), so they can't set their phones aside to do such things; their usage is not repeatable, so it is hard to believe them, whether they are saying "great battery life", or "battery life sucks!".
Heck, even at night, when my phone isn't "doing anything", (which you would think would be sort of "reproducible") if I move it 8 inches one way or another on the nightstand, my signal level can change by 10 dBm. That means that if I don't use Airplane Mode overnight, it is really not too meaningful to compare "configuration X" to "configuration Y" on successive nights - because the battery usage by the radio is not reproducible.
I guess the bottom line is - if you can get a full day out of the phone, be happy with that; it's just about what the phone was designed to do.
bftb0
bftb0 said:
If you are already using Airplane Mode because of poor signal conditions, Toggle2G won't help much - the battery will drain just looking for voice/1xRTT service (not to mention 3G). I have a pretty good signal where my phone spends most of it's time, including overnight ( -70 dBm to -80 dBm )
Seems OK. I have a couple of battery profiles where I slowly drop the max frequency, and make the default condition explicit by using a "battery < 101%" profile, as in:
Pr Min/Max Governor Condition
90 245/480 interactive Temp > 50.0 C *audible alarm
80 245/604 interactive Temp > 45.2 C
70 528/710 interactive Charging
60 160/245 interactive Screen Off
50 160/480 interactive Battery < 15%
40 160/528 interactive Battery < 25%
30 245/604 interactive Battery < 40%
20 480/710 interactive Battery < 67%
10 480/729 interactive Battery < 101%
I'm not sure this really produces much effect in terms of battery savings, though - for instance, it runs counter to my suggestion (above) that it might actually hurt to slow things down with reduced battery reserve because you just end up with the screen on longer.
I'll also mention that for a period of time I was actually convinced that using setCPU was causing random freeze-ups when used with certain combinations of the CFS kernel, governor choice, and min frequency - and so I didn't even have it installed on my phone. I only recently put setCPU back on my phone because I was noticing that CPUboost settings did not seem to be sticking even within the same session (perhaps I was misinterpreting something, I'm not sure). No random freeze-ups lately.
Because some of the things which actually drain the battery - cell radio, screen time on & brightness, 3G activity level, etc., are so highly variable, I'm not sure that any of the reports on this forum (including mine) can be regarded as particularly meaningful. It takes real dedication to the task (creating reproducible signal conditions and compute/activity workloads) to be able to produce quality data about battery usage. Most folks need to use their phones throughout the day (moving continuously from place to place with widely varying signal levels), so they can't set their phones aside to do such things; their usage is not repeatable, so it is hard to believe them, whether they are saying "great battery life", or "battery life sucks!".
Heck, even at night, when my phone isn't "doing anything", (which you would think would be sort of "reproducible") if I move it 8 inches one way or another on the nightstand, my signal level can change by 10 dBm. That means that if I don't use Airplane Mode overnight, it is really not too meaningful to compare "configuration X" to "configuration Y" on successive nights - because the battery usage by the radio is not reproducible.
I guess the bottom line is - if you can get a full day out of the phone, be happy with that; it's just about what the phone was designed to do.
bftb0
Click to expand...
Click to collapse
Hm, I might try those profiles with a few tweaks, or I might just end up bumping up my screen off profile in terms of priority, not sure yet.
Another question, what do you suggest as far as governors go? I seem to have the most success with ondemand, but I've never tried interactive. I learned the hard way that smartass lags my phone horribly, not sure why.
With my extended battery, I've gone roughly 65 hours total uptime with about 45% battery left with moderate use. I guess I should be proud of that.
ToastPwnz said:
I'm currently debating buying WidgetLocker, but I'm a bit skeptical since I'm not sure how bad it will lag with my current sleep profile. Can any WidgetLocker users possibly shed some light if they think it will lag on my phone? I'll put my profiles below.
Code:
Temp > 38.6C, Priority: 100, 480 max 160 min, ondemand
Charging/Full, Priority: 75, 710 max 245 min, ondemand
Battery < 25%, Priority: 50 ,480 max 245 min, ondemand
Screen Off, Priority: 25, 245 max 160 min, ondemand
If my sleep profile would make it lag, would bumping it up to 245 max 245 min help any?
Profile recommendations are welcome as well if theres anything that could be done to improve performance without sapping an excessive amount of battery. I have noticed my phone lags waking up sometimes and occasionally just when it's being used.
Click to expand...
Click to collapse
Wow you actually set a max of 480 for merely being over 38.6C??? I think that's a bit extreme. Other than that your profiles aren't that different than what I use (using Conap's CPUBoost tool, what are you using?).
I love WidgetLocker, and yes it's one of the only two apps I've actually purchased. Lag or not I wouldn't trade it.
The only "issue" (not necessarily WL's fault) is that using the Theme Chooser under GB ROMs, at least with the Speedometer Battery theme, definitely causes WL to lose what widgets are on it between reboots, although not always every reboot, but most of them.
It's confirmed that the solution is to not use Theme Chooser, at least with the Speedometer Battery theme. I don't know for sure if other themes cause it as well, but it's easily reversed (go back to the stock theme) if it does.
roirraW "edor" ehT said:
Wow you actually set a max of 480 for merely being over 38.6C??? I think that's a bit extreme. Other than that your profiles aren't that different than what I use (using Conap's CPUBoost tool, what are you using?).
I love WidgetLocker, and yes it's one of the only two apps I've actually purchased. Lag or not I wouldn't trade it.
The only "issue" (not necessarily WL's fault) is that using the Theme Chooser under GB ROMs, at least with the Speedometer Battery theme, definitely causes WL to lose what widgets are on it between reboots, although not always every reboot, but most of them.
It's confirmed that the solution is to not use Theme Chooser, at least with the Speedometer Battery theme. I don't know for sure if other themes cause it as well, but it's easily reversed (go back to the stock theme) if it does.
Click to expand...
Click to collapse
I'm still using SetCPU.
Yes I do knock it down that far, my phone heats up like crazy while I'm at school (terrible signal) and once it reaches 100F I could use the phone as a hand warmer and if I take off the back I can smell burning plastic. Maybe thats normal for the Eris, but I use it just as a precautionary measure.
ToastPwnz said:
Another question, what do you suggest as far as governors go? I seem to have the most success with ondemand, but I've never tried interactive. I learned the hard way that smartass lags my phone horribly, not sure why.
Click to expand...
Click to collapse
I haven't spent much time trying to figure out the "best" governor - I tend to use either "ondemand" or "interactive" without giving it too much thought. I tried smartass for a while, and remember being not happy with it for some reason or another; but I don't remember what those reasons were. ( It might have been nothing more than "choppiness" of scrolling behaviors. )
bftb0 said:
I haven't spent much time trying to figure out the "best" governor - I tend to use either "ondemand" or "interactive" without giving it too much thought. I tried smartass for a while, and remember being not happy with it for some reason or another; but I don't remember what those reasons were. ( It might have been nothing more than "choppiness" of scrolling behaviors. )
Click to expand...
Click to collapse
Now my curiosity is getting the best of me. Whats the difference between ondemand and interactive? (Sorry for all my questions <.<)
ToastPwnz said:
Now my curiosity is getting the best of me. Whats the difference between ondemand and interactive? (Sorry for all my questions <.<)
Click to expand...
Click to collapse
I don't know for sure...
... but I can tell you that the exact answer to your question is right here.
bftb0 said:
I don't know for sure...
... but I can tell you that the exact answer to your question is right here.
Click to expand...
Click to collapse
Hidden within that garbled mess.
I kid, I think I found the explanation you had in mind, and from what I can find the only major difference is that interactive is more aggressive then ondemand. I'm not sure if I should take that governor for a test run or not, I do notice that my phone lags when waking up occasionally. It kind of sounds like switching to interactive might help that.
ToastPwnz said:
I'm still using SetCPU.
Yes I do knock it down that far, my phone heats up like crazy while I'm at school (terrible signal) and once it reaches 100F I could use the phone as a hand warmer and if I take off the back I can smell burning plastic. Maybe thats normal for the Eris, but I use it just as a precautionary measure.
Click to expand...
Click to collapse
You probably have your reasons, but when you're at school, why don't you put it in Airplane mode and just take it off it between classes to check emails and such? Save your battery and the heat of your Eris a bunch.
Or do you and you just use the temperature profile as a fallback in case you forget to put it back in Airplane mode?
roirraW "edor" ehT said:
You probably have your reasons, but when you're at school, why don't you put it in Airplane mode and just take it off it between classes to check emails and such? Save your battery and the heat of your Eris a bunch.
Or do you and you just use the temperature profile as a fallback in case you forget to put it back in Airplane mode?
Click to expand...
Click to collapse
You are quite correct sir. That and my I bump my phone occasionally, and I think two days ago it turned on and I didn't notice, and when I checked it I noticed over the course of about 2-3 hours it lost 14% and was at around 95ish F.
I do keep it in Airplane Mode when I'm not using it (and it's off as well), but the profile is pretty much just a precautionary measure.
I got 12% battery drain in 17 hours, standby. I'm not a pro at android but I might give a little tut. on how to save battery life to the max. Atleast, it works for my P500 so it should work for you & for any other android device as well.
Uninstall every unnecessary app, including system apps (those apps, that does not mess up with the system stability - If you uninstall Email app, you will not solve your problems with Gmail app).. same with Messaging. That said, leave as minimum apps in the background as you can. App killer does not solve this problem, it just closes bg apps - they restart after some time. I'm using ATK (Advanced Task Killer), It usually kills 1 - 3 apps, so.. I have a minimum of apps running in the bg.
Basic stuff.. turn off your 3G, wifi, bg sync, gps when not in use. If you need to check your email, use 2G network only option, not 3G. Use 2G always when you don't need 3G speed. Screen brightness is not that important if you set it to anywhere below 70%. It should not drain the battery that fast.
Setcpu - profiles - governors--
My profiles are as follows
Charging - 480min - 748max
Battery <90% - 245min - 600max
Battery <70% - 245min - 600max (U can live with one profile for the battery, I have 2 in case I want to change the 2nd profile)
Screen off - 122min - 245max -- This is what saves my battery in standby.
The governors are ondemand for usage & conservative for screen off.
I'm using Void.echo rom with tapps & gapps modules, uninstalled everything I don't need.
I hope this helps If anyone has a better idea on how to save battery life, please share yours as well.
Thanks for your post, but actually most background apps don't drain battery. I have made lots of experiments (removing system aps, preventing autorun etc., and I don't see any major difference in battery life. So now, I'm on stock 2.2 and I'm now at 80% after almost 30h use: about 20 min talk, 10-15 min wi-fi (mail), 10-15 min EDGE. The latter by the way drains battery more than wi-fi. So instead of messing with system apps I recommend putting the phone in airplane mode during the night and as mentioned in the above post - not using 3G when not needed (EDGE has decent speed).
thats the why linux works !!! use all the memory u possibly can...These Microsoft *****es have changed the way computers were supposed to be used not reinstalling windows and other crapware all the time..Switch to Debian while its still time
And i use these settings
screen off 245-245 powersave (otherwise phone gets hot Its summer in india)
600-245 ondemand otherwise
kopchev said:
Thanks for your post, but actually most background apps don't drain battery. I have made lots of experiments (removing system aps, preventing autorun etc., and I don't see any major difference in battery life. So now, I'm on stock 2.2 and I'm now at 80% after almost 30h use: about 20 min talk, 10-15 min wi-fi (mail), 10-15 min EDGE. The latter by the way drains battery more than wi-fi. So instead of messing with system apps I recommend putting the phone in airplane mode during the night and as mentioned in the above post - not using 3G when not needed (EDGE has decent speed).
Click to expand...
Click to collapse
If there are many apps running in the bg, phone runs out of ram, so it tries to free up some space constantly. I think that drains battery, not the apps themselves. As well as the more cpu power is used, the faster it drains battery. Airplane mode shuts off any connection, so either that or you could just shut down the phone during night. Hmm you could tell me how to prevent app autorun, i have not looked into that.
btw juicedefender does wonders with the phones battery i had a 2% percent over night normal mode (not airplane) no 3g/Edge/Wifi/Bluetooth active and just sleeping
sarfaraz1989 said:
thats the why linux works !!! use all the memory u possibly can...These Microsoft *****es have changed the way computers were supposed to be used not reinstalling windows and other crapware all the time..Switch to Debian while its still time
And i use these settings
screen off 245-245 powersave (otherwise phone gets hot Its summer in india)
600-245 ondemand otherwise
Click to expand...
Click to collapse
True about windows & linux hehe. You havent tried 122-245mhz on screen off? Ofcouse, it lags even when i receive an sms, it's something like this - the screen turns on, then after 2 sec. i hear a notification, then after 1 sec. i see the sms but that does not make any problems for me, it's extreme powersaving
I don't get the point of airplane mode while you're sleeping.
If you don't want to get calls while sleeping, shouldn't it be better if you turn off the phone?
I had a good experience with JuiceDefender until now too. Last night my phone was 100% and no airplane mode while sleeping. It drained only 3%.
SoundTone said:
If there are many apps running in the bg, phone runs out of ram, so it tries to free up some space constantly.
Click to expand...
Click to collapse
From what I've read, Android doesn't swap. It'll just kill the background apps on it's own. I don't think there even is a swap unless you root, rom and create one on your uSD.
rapharias said:
I don't get the point of airplane mode while you're sleeping.
If you don't want to get calls while sleeping, shouldn't it be better if you turn off the phone?
I had a good experience with JuiceDefender until now too. Last night my phone was 100% and no airplane mode while sleeping. It drained only 3%.
Click to expand...
Click to collapse
It's more convenient, because the on/off process is quite slow...in contrast - airplane mode on/off is 3-4 secs. In airplane mode you can still use wi-fi. Last night the battery drained only 1%
i read somewhere that changing the CPU speed doesnt change the voltage, thus it does not affect battery life... anyone can confirm this???
As far as I can remember from school, a logic gate uses more power when switching, thus a higher frequency would also mean higher power drain (higher frequency = more switching of the logic gates), without voltage modification.
Voltage is changed in order to keep stability - higher voltage means a more stable logic signal, and a faster switching gate, and thus people reccomend using a higher voltage for higher frequencies/lower voltage for lower frequencies.
Thus, a CPU with so many logic gates does not operate just like a simple resistor. In fact it is worse, because when you use higher voltage AND higher frequency power drain is increased much more.
On the other hand, most modern CPU's simply deactivate CPU regions when idling, so, in case of our hardware (constant voltage) there should not be such a great difference when idling (most of the CPU is powered down). The only thing is for the phone to be REALLY idling (no background tasks eating too much of the CPU when screen off).
Basically, what this means is that if you want extreme power saving use a governor with 128MHz minimum and have as few background services as possible (or at least the ones that are there should be optimized for the least CPU usage).
Now I use the standard governor (248 - 600) and I thing my idle power drain is OK.
I guess I will test a governor that is plain 600MHz and one wit 320 or 480 as a minimum, in order to see if power drain is higher when using a lower lag configuration.
And, just as a guess, if background tasks are triggered by timers, a governor with just 600MHz (or 320 - 600 or 380 - 600?) could (just a wild guess) mean that background tasks take less time to execute, and leave the CPU to si more in IDLE mode, causing a very similar power drain as an extreme power saving governor. But this is just a guess, i have not tested it yet. And it also depends on what apps you have (what the apps do when phone is sleeping).
Basically, my best advice would be to watch the apps (after you install a new app, wait for a night to see if the new app causes a higher drain; if it does, search for another app that does the same thing)
spaic said:
As far as I can remember from school, a logic gate uses more power when switching, thus a higher frequency would also mean higher power drain (higher frequency = more switching of the logic gates), without voltage modification.
Voltage is changed in order to keep stability - higher voltage means a more stable logic signal, and a faster switching gate, and thus people reccomend using a higher voltage for higher frequencies/lower voltage for lower frequencies.
Thus, a CPU with so many logic gates does not operate just like a simple resistor. In fact it is worse, because when you use higher voltage AND higher frequency power drain is increased much more.
On the other hand, most modern CPU's simply deactivate CPU regions when idling, so, in case of our hardware (constant voltage) there should not be such a great difference when idling (most of the CPU is powered down). The only thing is for the phone to be REALLY idling (no background tasks eating too much of the CPU when screen off).
Basically, what this means is that if you want extreme power saving use a governor with 128MHz minimum and have as few background services as possible (or at least the ones that are there should be optimized for the least CPU usage).
Now I use the standard governor (248 - 600) and I thing my idle power drain is OK.
I guess I will test a governor that is plain 600MHz and one wit 320 or 480 as a minimum, in order to see if power drain is higher when using a lower lag configuration.
And, just as a guess, if background tasks are triggered by timers, a governor with just 600MHz (or 320 - 600 or 380 - 600?) could (just a wild guess) mean that background tasks take less time to execute, and leave the CPU to si more in IDLE mode, causing a very similar power drain as an extreme power saving governor. But this is just a guess, i have not tested it yet. And it also depends on what apps you have (what the apps do when phone is sleeping).
Basically, my best advice would be to watch the apps (after you install a new app, wait for a night to see if the new app causes a higher drain; if it does, search for another app that does the same thing)
Click to expand...
Click to collapse
I don't know about CPU's as much as u, but simple logical thinking helps here.. Low frequency + minimum of bg tasks = great power saving, I have now used the phone for 36hours without charge, 61% battery left. That is not only idling, i write about 50 to 150 sms a day & use the phone for other stuff too. So, those governors & frequencies i mentioned earlier in this post, helps a lot.
fransisco.franco thinks otherwise read the his post that contains the link to his rom devoid.francov6(ROM is cool btw and unfortunately i have a slow sdcard )
I think the first post is by far the best I have seen so far.
Sent from my LG-P500 using Tapatalk
Wow, only 1% all night?
I'll take a deeper look at your tips!
I use devoid.franco with franco.kernel v12. From all ROMs I've isntalled, it's the best: great performance and long battery life.
I get 5% battery drain in 7:30 hours (at night), without doing anything special, without running a custom ROM and without uninstalling apps. I just make sure GPS, Bluetooth, WiFi and data are off before going to bed.
I've install Rom Toolbox,
and i saw there is a "CPU slider" where i control the clock speed.
i've put it to 1000MHz instead of 1200MHz and tested it for several days
i really dont feel any difference in performance.
browsing seems same, games like asphalt is equally smooth.
heating is similar, equally warm.
the only difference is quadrant benchmark.
1200MHz scores 3200-3400
1000MHz scores 2600-2900
frankly speaking, i'm not sure if there's any difference in battery life.
is there any way to accurately test whether the clock speed affects the battery life?
i've seen other threads, where there are very different opinions.
some say it will improve battery life, and some say its worst.
http://forum.xda-developers.com/showthread.php?t=726019
Quote: (SetCPU doesn't make a difference in battery life, it can only shorten it. The kernal already has the best settings for CPU speed built in.)
http://forum.xda-developers.com/showthread.php?t=1305465
Quote: (if you are able to stand the side effects of underclocking, it will surely boost your batery life.)
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it). If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
slig said:
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it).
If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
Click to expand...
Click to collapse
HI, thanks for replying. I understand what you mean. the phone dont operate at 1200MHz all the time. but when using browser, and playing games, such as asphalt, it runs at max CPU usage almost the entire gaming duration.
Anyway.....
the real question is whether the clock speed is directly proportional to the battery consumption.
while reading your post, i thought of a brilliant ideal how to verify this.
the CPU slider not only allows you to set the max CPU speed,
you can set the min CPU speed as well.
So, i thought of an experiment, lets set the min & max CPU to 1200MHz,
this way, the phone will be running constantly at max CPU even when its idle.
let the phone be turn on till it run out of battery, record the time, T1.
then repeat again with max and min CPU set to 1000MHz.
record the time it is turn on till it run out of battery, record time as T2,
then compare T1 & T2, this could certainly work.
it would be nice if any member here happens to have 2 sgs2, and tried them ;-)
There are two more things to consider
1. CPU is not the only element that consumes power.
2. SGS2's Exynos is always clocked at 200MHz when the screen is off - check if this minimum slider affects that too.
Please let know how your experiment goes.
Regards
when the screen is off, the phone will be in "deep sleep" state. i think thats less than 200MHz.
anyway, i wont be doin this experiment any time soon.
you see, this is my only phone, i need to use it.
i dont have much oportunity to leave it and wait for it to run out of juice.
still, i'll try it when i have the chance.
Hey guys,
I did an experiment not a long time ago. I have my old phone with 4.1.2 Android and I went on a trip for a few days. Typically my phone discharges after 12-15 hours even without using anything (old battery) with smartassv2 or just conservative mode. Before going on the trip, I've set the minimum clock to the lowest possible and set the mode to powersaving (always using the minimum). And after 3 days the battery still was at 86%.
So what's the problem with the Android OS itself? Or have I just gotten some magical experience? Why does it use such a large clock rate for the processor when it's locked and using any preference script apart from power saver?
Thanks a bunch!
First of all, battery life depends on your battery type and capacity.
Second of all, when you underclock your cpu to the minimum frequency, battery consumption will decrease a LOT but using this frequency for apps use is practically impossible.Also, display causes less battery life.
Hope i helped !
Forgot about this topic. Yes, mate, I understand that, but the minimum frequency is enough when I don't have any apps running in the background. Seems like android still has a lot of power managment programming to be done under standby.
Maybe I wasn't clear enough, but if you just use any governor (with minimal frequency set at the lowest) apart from "powersaving", it will use more power on standby, then powersaving with the minimal frequency set.