Related
Can u guys share ur set CPU profile. I need profiles with great performance and less battery consumption. My profile is as followed :-
Charging AC/full 748 Max 480 min
Screen off 245 max 122 min
Performance n battery don't come together ..... I use ondemand 729/425 ... nothing different for screen off .... works really smooth n decent battery also
Sent from my LG-P500 using XDA App
But I Also need to manage my batteries...
My setup's kinda similar to yours,
480/720 ~ on demand ~ when charging/full
Otherwise 240/320 when screen is off. BTW How long does yours last?
Hey !
That's for me :
Charging/full : 729 - 245 / ondemand
Screen off : 320 - 245 / conservative
Battery < 40 : 600 - 245 / ondemand
Battery < 20 : 480 - 245 / conservative
I don't have many profiles, just 1.
245min / 748max
Battery's life is kinda good, usually I have to recharge one time a day. It's not a problem for me.
Toshir0 said:
Hey !
That's for me :
Charging/full : 729 - 245 / ondemand
Screen off : 320 - 245 / conservative
Battery < 40 : 600 - 245 / ondemand
Battery < 20 : 480 - 245 / conservative
Click to expand...
Click to collapse
I even used battery less than profile but it slows the phone too much....
Well It also depends on which ROM you have on your phone.
Mik_os CM7 port actually EATS the battery and It runs out of juice in less than 24 hours with a normal usage. A bit better with devoid v5, but I feel like openOptimus is the best one out of the three.
I use only one profile: battery < 101% @ 729/122 smartass
great advice so i must be changing my rom as soon as andy releases his new build!
729 max 480 min smartass
I use:
Main 729 max 320 min smartass
Charging 600 max 245 min ondemand
Battery < 40% 600 max 245 min conservative
Battery < 25% 480 max 122 min conservative
I used to keep a screen lock profile at 245 max but my phone lagged while receiving calls when the screen was locked and sometimes while playing music.
I use devoid.franco and
729/480 interactive
Screen off: 600/240 ondemand
What is that of smartass? My SetCpu havent got that mode :/
have someone got a guide or something that explain each mode (ondemand, interactive...)
Using stock ROM.
Normal: 729 max, 245 min, conservative
Charging: 768 max, 245 min, ondemand
Battery < 20%: 600 max, 122 min, conservatve
Battery life greatly depends on my usage. But, generally, I come home after classes (where I use it for internet, music, games etc.) with 30-40% battery left.
Javi V12 said:
I use devoid.franco and
729/480 interactive
Screen off: 600/240 ondemand
What is that of smartass? My SetCpu havent got that mode :/
have someone got a guide or something that explain each mode (ondemand, interactive...)
Click to expand...
Click to collapse
i wish if some one had a guide on it but optimus users like u and me are recommended to use ondemand (no i am not a noob).
Devil_Dude said:
i wish if some one had a guide on it but optimus users like u and me are recommended to use ondemand (no i am not a noob).
Click to expand...
Click to collapse
Look at this
http://forum.xda-developers.com/showpost.php?p=9272248&postcount=1
i got dis man
Program for controlling CPU frequency on Android in order to increase productivity or increase battery life.
Of the features worth noting customizable profiles.
Description of modes:
* Interactive - an interactive mode, driving frequency of the CPU in real time, almost always at full productivity.
* Smartass - a regime based on Interactive. Has a more rapid decline in frequency in a simple, but also lowers the frequency to a minimum at a turned off screen.
* Conservative - operates at a very low incidence of possible CPU and increases incrementally, as needed.
* Userspace - allows you to change the frequency of the CPU, either manually or dynamically, at the discretion of the software.
* Powersave - reduces the frequency of the CPU to the lowest possible level.
* Ondemand - operates at a very low incidence of possible CPU and increases the maximum reaches values of CPU usage - 100%.
* Performance - sets the maximum frequency of the CPU, not allowed to change frequency downward.
Recommend some good overclocking number for p500. Mine is 710/480
Sent from my LG-P500 using XDA App
hellodzulz said:
Recommend some good overclocking number for p500. Mine is 710/480
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
It is not a static value across devices. Test it out yourself and use the one which is stable for you. Some guys have it stable even at 806 while my phone freezes at anything above 768.
hellodzulz said:
Recommend some good overclocking number for p500. Mine is 710/480
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
My o1 freezes at abt 800Mhz...
If you want to play safe, keep it under 720... after this it starts becoming unstable....
Press Thanks If I helped...
i would not set anything more than 768
and i like to set it one level below the max I think I can go.
so i set it at 480/748, and it is stable
varies...im pretty stable at 480/844
Depends on your Hardware
Try frequencies from 729 to 806 , but remember to uncheck the "Set on boot" option. (Just in-case to avoid boot loops)
I've set mine at 787
Thanks guys! I will try!
Sent from my LG-P500 using XDA App
What about the lower end of the freq?
I see some people cost 245 while some post 480.
I'm thinking 245 give it a better battery life since its lower but I've also read somewhere that 245 is too low and it causes the cpu to ramp up and down.
My phone gradually increases the chance of receiving a kernel panic starting at 768 MHz.
geeyoupee said:
What about the lower end of the freq?
I see some people cost 245 while some post 480.
I'm thinking 245 give it a better battery life since its lower but I've also read somewhere that 245 is too low and it causes the cpu to ramp up and down.
Click to expand...
Click to collapse
I've been reading a lot about battery saving in our P500 and it seems that power consumption is the same for frequencies of 480 mhz and below, so in the end, the phone sleeping at 245 consumes the same battery as when it's sleeping at 480.
With that in mind, it's much more convenient to set the clock at 480 mhz at it's minimun since it provides a better response and wakes the phone faster, ending up in less processing time with same battery consumption.
I using 320\748 SmartassV2
480/600 and im still sometimes getting random shut downs and KP's...
I use 480/864 running smartassV2
729/480 onDemand
Kernel: fserve 18c
Governor: minmax
Min: 480
Max: 600
Is my screen too bright, or am I just too ASIAN?!
I forgot to say my chipset config.
I am currently using Franco Kernel along with Andy's Phoenix ROM.
Max 748 MHz
Min 480 MHz
Governor SmartassV2
Used SetCPU for this matter. I'm actually getting an awesome battery life and excelent performance. I'm usually exigent, but this time I can say I'm satisfied.
InfiniteRisen said:
Kernel: fserve 18c
Governor: minmax
Min: 480
Max: 600
Is my screen too bright, or am I just too ASIAN?!
Click to expand...
Click to collapse
Probably, for me it looks too bright at 40% and I had to put it to 25%.
729(max) and 480(min) with SmartassV2 governor is the best
Sent from my LG-P500 using XDA App
NonCrowd said:
I use 480/864 running smartassV2
Click to expand...
Click to collapse
which rom and kernel are you using...
I'm pretty noob at making overclocks. How do I know the overclock I'm using is crashing/bugging/killing my phone? I'm using mik Cyanogenmod 6.6.1 480/748.
Hey guys!
I was wondering if anyone can give me some info on the differences between the governors with doomkernel and the schedulers.
Thanks!
Cheers,
This was posted by DooMLoRD, i just copied the post not all governors are there:
2. Governors In the Linux Kernel ================================
2.1 Performance ------------------------------
The CPUfreq governor "performance" sets the CPU statically to the highest frequency within the borders of scaling_min_freq and scaling_max_freq.
2.2 Powersave ----------------------------
The CPUfreq governor "powersave" sets the CPU statically to the lowest frequency within the borders of scaling_min_freq and scaling_max_freq.
2.3 Userspace ----------------------------
The CPUfreq governor "userspace" allows the user, or any userspace program running with UID "root", to set the CPU to a specific frequency by making a sysfs file "scaling_setspeed" available in the CPU-device directory.
2.4 Ondemand ---------------------------
The CPUfreq governor "ondemand" sets the CPU depending on the current usage. To do this the CPU must have the capability to switch the frequency very quickly. There are a number of sysfs file accessible parameters:
sampling_rate: measured in uS (10^-6 seconds), this is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more.
show_sampling_rate_(min|max): the minimum and maximum sampling rates available that you may set 'sampling_rate' to.
up_threshold: defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
ignore_nice_load: this parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilisation' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation. This is useful if you are running a CPU intensive calculation on your laptop that you do not care how long it takes to complete as you can 'nice' it and prevent it from taking part in the deciding process of whether to increase your CPU frequency.
2.5 Conservative -------------------------------
The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour more suitable in a battery powered environment. The governor is tweaked in the same manner as the "ondemand" governor through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be increased and decreased smoothly by. By default the cpu frequency will increase in 5% chunks of your maximum cpu frequency. You can change this value to anywhere between 0 and 100 where '0' will effectively lock your CPU at a speed regardless of its load whilst '100' will, in theory, make it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand" governor but for the opposite direction. For example when set to its default value of '20' it means that if the CPU usage needs to be below 20% between samples to have the frequency decreased.
2.6 Interactive ------------------------------
The CPUfreq governor "interactive" is designed for low latency, interactive workloads. This governor sets the CPU speed depending on usage, similar to "ondemand" and "conservative" governors. However there is no polling, or 'sample_rate' required to scale the CPU up.
Sampling CPU load every X ms can lead to under powering the CPU for X ms, leading to dropped framerate, stuttering UI etc..
Scaling the CPU up is done when coming out of idle, and like "ondemand" scaling up will always go to MAX, then step down based off of cpu load.
There is only one tuneable value for this governor:
min_sample_time: The ammount of time the CPU must spend (in uS) at the current frequency before scaling DOWN. This is done to more accurately determine the cpu workload and the best speed for that workload. The default is 50ms.
2.7 MinMax ------------------------------
The CPUfreq governor "maxmin" tries to minimize the frequency jumps by limiting the selected frequencies to only two frequencies: either the min or the max frequency of the current policy. The frequency is raised or lowered according to the current load and the 'up_threshold' and 'down_threshold'.
Its parameters and implementation are similar to that of conservative.
It does not have the freq_step parameter as it jumps right from min to max and vice-versa.
The sampling_down_factor, unlike conservative, will count the minimal number of samplings since the last time we saw the 'up_threshold' load on the CPU. Hence it is set to higher default and acts as a limiter not to do too many frequency jumps without hurting the performance.
Thanks sorry, didnt see it for some reason. Ignore my questions.
Cheers,
oppiee said:
Thanks sorry, didnt see it for some reason. Ignore my questions.
Cheers,
Click to expand...
Click to collapse
One thing to note pal. All chipsets have different tolerances so whereas interactive works best for me, it may not be good for u. Just test em and use CPU spy/ ur own judgement to c which suits ur phone best.
Sent from my X10i using XDA App
Yup I am currently fiddling around with the different settings. The main thing I want to accomplish is not to have lag when im scrolling and opening up basic apps such as dialer and browser. I dont really play games. I hate the fact that the phone lags up sometimes. So far Its ok, but getting some WLOD on super high freq.
Any suggestions?
oppiee said:
Yup I am currently fiddling around with the different settings. The main thing I want to accomplish is not to have lag when im scrolling and opening up basic apps such as dialer and browser. I dont really play games. I hate the fact that the phone lags up sometimes. So far Its ok, but getting some WLOD on super high freq.
Any suggestions?
Click to expand...
Click to collapse
Can u post a screenshot of CPU tuner or whatever u use of freqs u use? Also are u using doomkernel fs version as I think some handsets can't even boot up oc kernel.
Sent from my X10i using XDA App
Any good programs to take screen shots? I am using the highest OC kernel by DL, and using doomkernel wolfbreak V7b6.
Not mean to sound patronising pal but just type screen shot into android market theres plenty
Edit: ur phone prob can't handle the overclock. Read the kernel thread it says this pal.
Sent from my X10i using XDA App
Oh i think there might has been some misunderstanding. My phone is running fine, just doing some testing. at 1.229 Mhz I tend to get WLODs, using minmax with SIO.
At 1.114 and 245, using min max with SIO. everything is fine so far. I just thought you wanted to know for your own purposes.
Cheers
Sorry buddy I misunderstood
Sent from my X10i using XDA App
thers some missing from the top
lagfree
scary
brazilianwax
savaged zen
what do theese do
also whats the best settings from all of them from your opinion
I have:
Brazilianwax
Smoothass
Lagfree
Smartassv2
SavagedZen
Scary
Smartass
Minmax
Interactivex
Interactive
Conservative
Userspace
Powersave
OnDemand
Performance.
Not used them all but lagfree is (as suggested free from lag & smooth. Brazilianwax didnt work for me very laggy. Scary was quite good also, along with interactive. Not really tested the others enough to pass comment to be honest
Ok I'm hoping this post sticks, because no one has this listed anywhere it seems. I have compiled a list of commonly recognized cpu governors and frequencies that the EVO 3D processor and different kernels recognize. The max frequency depends on the kernel you flashed.
Ok so the Evo 3D processor only changes in intervals of 54 so I
researched. No one seems to have a guide on the net that gives those
numbers. The OC Daemon on ViperRom tells you all your options when
you go into terminal to change it, and it also gives you all the
processor governor options too. Where as with MeanRom and Anthrax
Kernel it gives you the minimum and maximum but shows nothing
inbetween, both with governors and frequencies.
starting with minimum:
192000
216000
270000
324000
378000
432000
486000
540000
594000
648000
702000
756000
810000
864000
918000
972000
1026000
1080000
1134000
1188000 Stock max, not quite 1.2 Ghz
1242000 A true 1.2 Ghz
1296000
1350000
1404000
1458000
1512000
1566000
1620000
1674000
1728000 Zedomax says this is most stable max freq. for him on ViperRom
1782000
1836000
1890000
1944000 Only read of one person having stability with this
Governor settings:
Ondemand - when you need it
Powersave - obviously
Conservative - straight forward
Interactive - sounds cut and dry
Performance - I guess hardcore gaming
Userspace - not sure what this one does
Auto - Uses kernel to determine
The userspace governer is basically a legacy thing (see: http://www.thinkwiki.org/wiki/How_to_make_use_of_Dynamic_Frequency_Scaling) that allows you or an application/module that resides in userspace to manually adjust the CPU frequency.
This can be used in an android world by allowing an app to modify the CPU frequency without relying on root access, if I remember correctly. It's basically useless though since I don't think any applications aside from maybe setcpu would use such a feature since most applications automatically assume you aren't rooted thus are using the typical default cpu governor.
Good post.
umm.. i think this is in the wrong spot??? maybe im wrong?? should be in the general...
evod3 said:
umm.. i think this is in the wrong spot??? maybe im wrong?? should be in the general...
Click to expand...
Click to collapse
Then how do I move it? Honest question. This is my first true post/thread that I started.
It's just when I go looking for answers for my phone I go directly to the CDMA section. Only after I can't find my answer there do I branch out and search the whole site. I usually dont think of the EVO 3D as a GSM phone. I mean generally speaking the EVO 3D is more on sprint than any other network world wide.
Other than that does anyone else have the problem of not being able to change voltages? I mean the SetCPU app shows it as a tab but when you purchase and download it there's no tab for votages. I dont wanna pay for another app and not have what it advertises. I emailed the devs of setcpu and never heard back. so I feel like I waisted my money on the dern thing.
I want to be able to truely undervolt and overclock my cpu for power saving reasons. Come on. My stock battery life was like 4 hours, 5 tops, with moderate use. ViperRom changed that to 18+ with moderate use. Now Im using MeanRom with the Anthrax kernel, overclocked to 1.3 GHz and im getting a little more than 36 hours with moderate use.
I'm betting with undervolting we could get a lot more battery life.
SketchyStunts said:
You can run viperROM.....it comes with the Tiamat kernel & has vipercontrol/vipermod baked in & can undervolt your heart out. I believe the it come with voltages -100 from stock. Had mine -125 & the most stable ROM i've ran yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24325646
This is from another thread I found earlier. Not sure what is meant buy -100. Is that mV V MV or what?
stephangardner said:
Then how do I move it? Honest question. This is my first true post/thread that I started.
It's just when I go looking for answers for my phone I go directly to the CDMA section. Only after I can't find my answer there do I branch out and search the whole site. I usually dont think of the EVO 3D as a GSM phone. I mean generally speaking the EVO 3D is more on sprint than any other network world wide.
Other than that does anyone else have the problem of not being able to change voltages? I mean the SetCPU app shows it as a tab but when you purchase and download it there's no tab for votages. I dont wanna pay for another app and not have what it advertises. I emailed the devs of setcpu and never heard back. so I feel like I waisted my money on the dern thing.
I want to be able to truely undervolt and overclock my cpu for power saving reasons. Come on. My stock battery life was like 4 hours, 5 tops, with moderate use. ViperRom changed that to 18+ with moderate use. Now Im using MeanRom with the Anthrax kernel, overclocked to 1.3 GHz and im getting a little more than 36 hours with moderate use.
I'm betting with undervolting we could get a lot more battery life.
http://forum.xda-developers.com/showthread.php?p=24325646
This is from another thread I found earlier. Not sure what is meant buy -100. Is that mV V MV or what?
Click to expand...
Click to collapse
That was from awile back when I had the EVO 4g & used vipermod to undervolt on AOSP. I used to get insane battery life. Miss that. Lol
Wait, maybe not can't remember. Stuck in 1x hell at the moment so can't check the link. Grrrrrr
Sent from my PG86100 using xda premium
I disagree. Because this has to do with frequency clocking, I'd say this is very much good to have stuck here.
Perhaps adding further information about undervolting would be even better?
LiquidSolstice said:
I disagree. Because this has to do with frequency clocking, I'd say this is very much good to have stuck here.
Perhaps adding further information about undervolting would be even better?
Click to expand...
Click to collapse
I hope we get some more insight.
I rooted for the sole purpose of getting better battery life. I read about undervolting, overclocking and underclocking to save battery. Then I find I can't change voltages like I thought. I know its out there just gotta get the right dev to respond to this thread.
Sent from my PG86100 using xda premium
stephangardner said:
I hope we get some more insight.
I rooted for the sole purpose of getting better battery life. I read about undervolting, overclocking and underclocking to save battery. Then I find I can't change voltages like I thought. I know its out there just gotta get the right dev to respond to this thread.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Best of luck to you, I'm sure many will thank you for this
stephangardner said:
. Then I find I can't change voltages like I thought..
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
What rom are you running? in system tuner pro click the "cpu" button you'll come to the screen where you set clock speeds, at the very top is a tab labled "voltage" hit that and there you can set your voltages. be careful though some phones dont play well with some setting, thats why i dont preset voltages in my ROM.
Originally Posted by stephangardner
. Then I find I can't change voltages like I thought..
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
What rom are you running? in system tuner pro click the "cpu" button you'll come to the screen where you set clock speeds, at the very top is a tab labled "voltage" hit that and there you can set your voltages. be careful though some phones dont play well with some setting, thats why i dont preset voltages in my ROM.
Click to expand...
Click to collapse
+1 for System Tuner Pro, love that app! I, too, hope this thread sticks cause I've been looking for PRECISELY this info to no avail recently!
Subscribed! Howdy folks!
Relevant to Dev. This stays here....
Nice work getting this here, OP.
Here is a great thread with a TON of useful information about kernels, govenors,I/O schedulers, kernel modules and a lot more... Very informative.
http://forum.xda-developers.com/showthread.php?t=1369817
Sent from my PG86100 using Tapatalk 2 Beta-5
steal25 said:
What rom are you running?
Click to expand...
Click to collapse
First Rom was viperRom then I added the rc remix kernel. Second Rom was the meanRom then a few hours later added the anthrax kernel
Sent from my PG86100 using xda premium
droidphile said:
1. GOVERNORS
I) MANUAL:
These are the 18 governors we're talking about.
1) Ondemand 2) Ondemandx 3) Conservative 4) Interactive 5) Interactivex 6) Lulzactive 7) Smartass 8) SmartassV2 9) Intellidemand 10) Lazy 11) Lagfree 12) Lionheart 13) LionheartX 14) Brazilianwax 15) SavagedZen 16) Userspacce 17) Powersave 18) Performance
1) Ondemand: Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.
2) Ondemandx: Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
3) Conservative: A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
4) Interactive: Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle. The governor has the following advantages: 1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling. 2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed. Interactive It's an intelligent Ondemand because of stability optimizations. Why?? Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc. Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle. When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks. If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.
5) Interactivex: This is an Interactive governor with a wake profile. More battery friendly than interactive.
6) Lulzactive: This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites. Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency. New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down. When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down. Example: Consider inc_cpu_load=70 pump_up_step=2 pump_down_step=1 If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800. If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
7) Smartass: Result of Erasmux rewriting the complete code of interactive governor. Main goal is to optimize battery life without comprising performance. Still, not as battery friendly as smartassV2 since screen-on minimum frequency is greater than frequencies used during screen-off. Smartass would jump up to highest frequency too often as well.
8) SmartassV2: Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
9) Intellidemand: Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors ) To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
10) Lazy: This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
11) Lagfree: Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
12) Lionheart: Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. See here. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks: sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe). up_threshold:60 down_threshold:30 freq_step:5 Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
13) LionheartX LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
14) Brazilianwax: Similar to smartassV2. More aggressive ramping, so more performance, less battery.
15) SavagedZen: Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
16) Userspace: Instead of automatically determining frequencies, lets user set frequencies.
17) Powersave: Locks max frequency to min frequency. Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).
18) Performance: Sets min frequency as max frequency. Use this while benchmarking!
So, Governors can be categorized into 3/4 on a high level: 1.a) Ondemand Based: Works on "ramp-up on high load" principle. CPU busy-time is taken into consideration for scaling decisions. Members: Ondemand, OndemandX, Intellidemand, Lazy, Lagfree. 1.b) Conservative Based: Members: Conservative, Lionheart, LionheartX 2) Interactive Based: Works on "make scaling decision when CPU comes out of idle-loop" principle. Members: Interactive, InteractiveX, Lulzactive, Smartass, SmartassV2, Brazilianwax, SavagedZen. 3) Weird Category: Members: Userspace, Powersave, Performance.
Click to expand...
Click to collapse
Good explanations as to what the OP was trying to relay.
gunfromsako said:
Here is a great thread with a TON of useful information about kernels, govenors,I/O schedulers, kernel modules and a lot more... Very informative.
http://forum.xda-developers.com/showthread.php?t=1369817
Click to expand...
Click to collapse
I'll have to read this one when I'm on a computer. Way to much info for the app.
steal25 said:
in system tuner pro click the "cpu" button you'll come to the screen where you set clock speeds, at the very top is a tab labled "voltage" hit that and there you can set your voltages.
Click to expand...
Click to collapse
Brownie points for this guy. Downloaded that app now and loving it. I'm gonna start with a 10 mV decrease on all voltages then do like 2 mV increments till I have issues then I'll report back.
dimebagdan65 said:
+1 for System Tuner Pro, love that app!
Click to expand...
Click to collapse
+2
By the way guys and gals does anyone else here have dyslexia? I didn't think I could get into all this because of it but I find it kinda soothing. Like working on cars helps with my ADHD. I feel like Jessie from The Fast And The Furious. Ha ha
Sent from my PG86100 using xda premium
oohaylima said:
Good explanations as to what the OP was trying to relay.
Click to expand...
Click to collapse
Same post I linked right above you...
I wipe till it bleeds...
gunfromsako said:
Same post I linked right above you...
I wipe till it bleeds...
Click to expand...
Click to collapse
I know. All I did was quote the author of the section that pertains to the governor in which the OP was trying to break down in the beginning.
I'm a big fan of keeping things under one thread for easy fluidity of related information.
gunfromsako said:
Same post I linked right above you...
I wipe till it bleeds...
Click to expand...
Click to collapse
Oh... my... GOD! I friggin love your sig! My sides hurt! I'm totally with ya! Never want problems? Always start with a clean slate! Duh... ^_^
I always keep my phone undervolted -50mv @ 1.5GHz intellanthrax. That's the farthest I can go without problems.
sent from America...F__k Yeah!
Comin again to save the motherf**kin day yeah!
Only one question... Rockin out or ballad style? XD
Siyah kernel + Checkrom...
Tried Voltage control, setcpu....
So, for specific frequency under performance governor, i can set any voltage...
Under all other governors it work ok...
Please help.
Sent from my GT-I9100 using XDA
mad_max911 said:
Siyah kernel + Checkrom...
Tried Voltage control, setcpu....
So, for specific frequency under performance governor, i can set any voltage...
Under all other governors it work ok...
Please help.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Performance governor uses only one single frequency (min freq = max freq) and is only useful for testing (benchmarks).
Do not use this governor for daily usage.
Select another governor, such as Ondemand.
You can still set min freq = max freq, if you want your phone to run on only one single frequency.
Thank you. Very good point to use, let say ondemand and min/max at same frequency... why didnt i think of that??... About performance governor, it does feel "snapier" in day to day usage, deep sleep still works and battery is not much worse as screen still uses 60% of battery.... only time when performance governor uses much more battery is if u are using gps or some background task that is preventing phone from going to sleep while screen is off...
Sent from my GT-I9100 using XDA
UPDATE: After some more research i conclude: problem is NOT due performance governor or kernel... Same think happens on any kernel and governor if you set min and max frequencies same(custom voltage set in any program will not apply). Solution is to have minimun 2 steps( for example 1200 min and 1400 max mhz in my case). Further, you can use setcpu profiles for "screen off" etc., and battery loss due this performance governor imitation gets minimal....
Sent from my GT-I9100 using XDA