Develop Bugs

Best cpu governor

Hello...can you post your settings about cpu governor.now my defy is set from 2nd.init at smartass governor and I seems like it is using the higher frequency more time then on-demand governor. I have latest cm7 from quarx and 2 days is the max batt life, but using hsdpa quite often
Sent from my MB525 using XDA App

Well
2 days sounds good. OnDemand works better for me like 5%+ but you need to tweak all the levels after VSEL to see some differences. Try asking, searching for a thread where they tweak all the levels and it's reported to give a boost.

Here's a post I made a few weeks ago regarding the smartass governor:
http://forum.xda-developers.com/showpost.php?p=17032162&postcount=3

i don't use Setvsel...i tweaked vsels from 2nd init.
http://forum.xda-developers.com/showthread.php?t=1065798
question no 15

Best Overclock settings specifically for the Play?

I'm using NoFrills CPU and want to find the right balance between overclocking, performance and battery...
What speeds and governors are everybody using for their Plays?

I'm using 1.2 Ghz max 130 Mhz min with SmartassV2 and sio. All seems okay to me.

I'm using 921mhz-122mhz intellidemand2 with sio governor and everything is smooth + battery is great
Sent from my R800i using xda premium

1401Mhz Max, 180Mhz Min (when Screen On), 785Mhz Max-180Mhz Min (When Screen Off)
Noop + InteractiveX
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
1401Mhz Max, 180Mhz Min (when Screen On), 785Mhz Max-180Mhz Min (When Screen Off)
Noop + InteractiveX

So many different settings!
Was hoping there'd be a 'common' setting that everyone kind of determined was best.
Thank though.
Still interesting, and would like to see what more people are using still.

Mines currently 1.613 Ghz Max, 245 Mhz Min. Virtuous Governor, Noop I/O Scheduler.
On intensive apps I change the max clock to 1.901Ghz however this I don't recommend for most people.
I also only use 1.9Ghz when using Android 2.3.7 with DoomKernel, as only that Kernel seems to allow for voltage changes... Which i apply when using that kind of speed, whereas the default voltages are much higher for that clock than I usually set.
Everyone's Play is different, and not all Plays can sustain high clocks at specific voltages. You need to find your own 'sweet spot'.

Spizzy01 said:
You need to find your own 'sweet spot'.
Click to expand...
Click to collapse
Is there an app for that?

No.
You need to increase your clock little by little until you're happy. Then, if you're on GB using DoomKernel you need to lower the voltage as much as you can without it crashing if you want it perfect.
Most people simply oc though and don't bother with the voltages, but it will reduce power consumption and extend the life of your phone with the OC enabled.. As normally running your CPU past its specification will wear it out faster.
Sent from my R800i using xda premium

As DiKeJ said in his ROM thread:
In my opinion, interactiveX, and frequency of CPU 364.8-1305.6MHz gives awesome stability and performance
Click to expand...
Click to collapse
:good:

TRUE FACT.

you should use a kernel that allows you to undervolt... there was some article with the galaxy S3, where they tested different settings with OC+UV and YES, Under Volting gives better battery life!!
A lot of people here say, that UV will have no effect on battery, but they have no idea how a processor works... so they just should stfu!!

[REF][Super Friendly] Explanation of Governors, I/O Schedulers and Kernels [24-Nov]

Introduction
"It takes few hours to make a thread but it doesn't even take few seconds to say Thanks"- arpith.fbi
Click to expand...
Click to collapse
Code:
Don't be afraid to ask me anything.
I won't bite, but I might lick you.
Just thank me for this super brief thread.
Give credits to this thread by linking it if you're using any of my info.
Thank you to you too
Have you unlocked your bootloader of your current device ? If so, read it ! If not, learn the benifits ! :victory:
What is this thread about ? It is a very brief explanation of every governors and schedulers to let you find the best combo for your device.
I've been searching a lot about informations about Kernels, Governors, I/O Schedulers and also Android Optimization Tips. No matter its Google or XDA or other android forums. I will go into it and try the best I can to find these infos. So I thought of sharing it to here for the Xperia S, Acro S, and Ion[COLOR] users.
My main reason to share this is to benefit users for better knowledge about Kernels, Governors, I/O Schedulers and Tips on Android Optimization. I'm not aware of whether where this should be posted, its related to kernels, governors and schedulers so I think it would be best if I share it to here. Yes, I wrote it word by word with references.Happy learning. :angel:
After months on XDA, no matter its in a development forum or Off Topic forum. Users kept on asking what's this what's that. And I'm sure that not all members will understand what is it until they bump into my thread
FAQs regarding on :-
-I/O Schedulers
-Kernel Governers
-Better RAM
-Better Battery
-FAQs
*Will add more when I found something useful.
Click to expand...
Click to collapse
I do a lot of asking by PM, to learn, it doesn't matter whether its a stupid one. (People who know me understands)
With my experience and lots of asking. I managed to find a lot of infos that we can use to optimize our phone.
I will try to explain as clear as I can.
Governors :-
-Smoothass
-Smartass
-SmartassV2
-SavagedZen
-Interactivex
-Lagfree
-Minmax
-Ondemand
-Conservative
-Brazilianwax
-Userspace
-Powersave
-Performance
-Scary
-Lulzactive *
-Intellidemand *
-Badass *
-Lionheart *
-Lionheartx *
-Virtuous *
* Not enough information about it, will add it later on.
Explanation
OnDemand
Brief
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, OnDemand will rapidly scale the CPU up to meet the demand, then gradually scale the CPU down when it isn't needed.
Click to expand...
Click to collapse
Review
Brief says all. By a simple explantion, OnDemand scales up to the required frequency to undergo the action you are doing and rapidly scales down after use.
Conservative
Brief
It is similar to the OnDemand governor, but will scale the CPU up more gradually to better fit demand. Conservative governor provides a less responsive experience than OnDemand, but it does save batter
Click to expand...
Click to collapse
Review
Conservative is the opposite of Interactive; it will slowly ramp up the frequency, then quickly drops the frequency once the CPU is no longer under a certain usage.
Interactive
Brief
Available in latest kernels, it is the default scaling option in some stock kernels. Interactive governor is similar to the OnDemand governor with an even greater focus on responsiveness.
Click to expand...
Click to collapse
Review
Interactive is the opposite of Conservative; it quickly scales up to the maximum allowed frequency, then slowly drops the frequency once no longer in use.
Performance
Brief
Performance governer locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task. After that it returns the CPU to extremely efficient low-power state.
Click to expand...
Click to collapse
Review
Good at gaming, Really good. Disadvantages are it may damage your phone if too much usage.
Powersave
Brief
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
Click to expand...
Click to collapse
Review
Set it to your desired minimum frequency and you won't have to look for your charger for once in a while.
Scary
Brief
A new governor wrote based on Conservative with some Smartass features, it scales accordingly to Conservative's way. It will start from the bottom. It spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as Conservative right now.
Click to expand...
Click to collapse
Review
Hmm.. Overall I don't see any difference. After I understand its main objective. I was very curious and decided to use it again. Results are the same.. No difference. Report to me if anyone has tested this.
Userspace
Brief
Userspace is not a governor pre-set, but instead allows for non-kernel daemons or apps with root permissions to control the frequency. Commonly seen as a redundant and not useful since SetCPU and NoFrills exist.
Click to expand...
Click to collapse
Review
Highly not recommended for use.
Smartass
Brief
It is based on the concept of the Interactive governor.
Smartass is a complete rewrite of the code of Interactive. Performance is on par with the “old” minmax and Smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Click to expand...
Click to collapse
Review
Smartass is rather the governer that will save your battery and make use of your processor for daily use. Like the brief explantion said " Smartass will spend much more time on lower frequencies." So logically you don't need for sleep profiles anymore.
SmartassV2
Brief
Theoretically a merge of the best properties of Interactive and OnDemand; automatically reduces the maximum CPU frequency when phone is idle or asleep, and attempts to balance performance with efficiency by focusing on an "ideal" frequency.
Click to expand...
Click to collapse
Review
This is a much favourite to everybody. I believe almost everyone here is using SmartassV2. Yes, it is better than Smartass because of its speed no scaling frequencies from min to max at a short period of time.
Smoothass
Brief
A much more aggressive version of Smartass that is very quick to ramp up and down, and keeps the idle/asleep maximum frequency even lower.
Click to expand...
Click to collapse
Review
In my personal experience, this is really useful for daily use. And yes, I'm using it all the time. It may decrease your battery life. I saw it OC itself to 1.4 gHz when I set it to 1.2. Good use. Recommended.
Brazilianwax
Brief
Similar to SmartassV2. More aggressive scaling, so more performance, but less battery.
Click to expand...
Click to collapse
Review
Based on SmartassV2. But its advantage is a much more performance wise governor.
SavagedZen
Brief
Another SmartassV2 based governor. Achieves good balance between performance & battery as compared to Brazilianwax.
Click to expand...
Click to collapse
Review
Not much difference compared to SmartassV2. But it is a optimized version of it.
Lagfree
Brief
Again, similar to Smartass but based on Conservative rather than Interactive, instantly jumps to a certain CPU frequency after the device wakes, then operates similar to Conservative. However, it has been noted as being very slow when down-scaling, taking up to a second to switch frequencies.
Click to expand...
Click to collapse
Review
Used it before. Like the name of the governor, I didn't experience any lag whatsoever. Another governor based on performance, but not battery efficient.
MinMax
Brief
MinMax is just a normal governor. No scaling intermediate frequency scaling is used.
Click to expand...
Click to collapse
Review
Well.. it's too normal that I can't really say anything about it..
Interactivex
Brief
InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to optimize the balance of battery vs performance. InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
Click to expand...
Click to collapse
Review
A better understanding from the brief to you users, this is an Interactive governor with a wake profile. More battery friendly than Interactive.
Due to current kernels doesn't have these governors. I will be delaying the explanation, its very interesting. If you want it ASAP, post below
-Lulzactive *
-Intellidemand *
-Badass *
-Lionheart *
-Lionheartx *
-Virtuous *
**********************************************************************************************************************************************************************
I/O Schedulers(thanks to droidphile)
Deadline
Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.
Advantages:
Nearly a real time scheduler.
Excels in reducing latency of any given single I/O.
Best scheduler for database access and queries.
Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.
Disadvantages:
When system is overloaded, set of processes that may miss deadline is largely unpredictable.
Click to expand...
Click to collapse
Noop
Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data. Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.
Click to expand...
Click to collapse
Anticipatory
Based on two facts
i) Disk seeks are really slow.
ii) Write operations can happen whenever, but there is always some process waiting for read operation.
So anticipatory prioritize read operations over write. It anticipates synchronous read operations.
Advantages:
Read requests from processes are never starved.
As good as noop for read-performance on flash drives.
Disadvantages:
'Guess works' might not be always reliable.
Reduced write-performance on high performance disks.
Click to expand...
Click to collapse
BFQ
nstead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.
Advantages:
Believed to be very good for usb data transfer rate.
Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
Considered an accurate i/o scheduler.
Achieves about 30% more throughput than CFQ on most workloads.
Disadvantages:
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.
Click to expand...
Click to collapse
CFQ
Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.
Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.
Click to expand...
Click to collapse
SIO
Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.
Advantages:
Simple, so reliable.
Minimized starvation of requests.
Disadvantages:
Slow random-read speeds on flash drives, compared to other schedulers.
Sequential-read speeds on flash drives also not so good.
Click to expand...
Click to collapse
VR
Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
Advantages:
May be best for benchmarking because at the peak of it's 'form' VR performs best.
Disadvantages:
Performance fluctuation results in below-average performance at times.
Least reliable/most unstable.
Click to expand...
Click to collapse
Credits
-droidphile
-kokzhanjia

Reserved for kernel info

Many thanks for sharing your knowledge on all of this! You made it very easy to understand
Sent from my LT26i using xda app-developers app

Thank u very much!

Thanks a lot !
Sent from my Xperia S using xda premium

Thanks for gathering all this info, it is a very handy guide.
You may want to add that this all works on locked bootloader as well. The big difference is you only get the stock kernel choices & no over clock. I use conservative & cfq thru 'cpu master' my locked ION
~Jaramie
Sent from my ION

how about hotplug - pegasusq ??????? can u explain this governors ?????

Segarys said:
Many thanks for sharing your knowledge on all of this! You made it very easy to understand
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
davidbar93 said:
Thank u very much!
Click to expand...
Click to collapse
Xecutioner_Venom said:
Thanks a lot !
Sent from my Xperia S using xda premium
Click to expand...
Click to collapse
ToledoJab said:
Thanks for gathering all this info, it is a very handy guide.
You may want to add that this all works on locked bootloader as well. The big difference is you only get the stock kernel choices & no over clock. I use conservative & cfq thru 'cpu master' my locked ION
~Jaramie
Sent from my ION
Click to expand...
Click to collapse
Thanks
saberamani said:
how about hotplug - pegasusq ??????? can u explain this governors ?????
Click to expand...
Click to collapse
Yeah, i will add it along with other unexplained governors
Thanks for reminding..

Gaming I/O and Governers Tweaks

I score 3028 after benchmarking with Quadrant after these small changes in CPU stuff and i thought i wanna share it ...
I tried all kinds of things to make gaming faster and after experimenting... I got 1950+ score for 3D perfomance and these are the overall results after changing the governor and I/O:
1st try: 3128 :laugh:
2nd try: 3209 :victory:
3rd try: 2977
4th try: 3028 :laugh:
Heres how...
You only need No-CPU frlls or CPU Master or any other APP capable of changing clock speeds eg. SetCpu... :good:
Set your devices Governor to smartassV2 and i/o scheduler to vr... Clock your CPU speed to the max frequency that is stable... Mine is 1.8GHz, but can OC to 2Ghz which can make my device boiling hot.... Minimum frequency you wanna set is 600 mhz and below... And thats about it...
DO NOTE! Only some kernels can use the SmartAssV2 Governor and vr I/O scheduler... if none of them is there, I recommend you use Ondemand Govern' and Noop I/O...
Again, not all kernels are gonna have that score..
If i made a great mistake, don't be afraid to correct me especially Pepoluan ...
BTW i'm using REMICS v1.7 by sparta20 and Forvivos kernel...

TiTAN-O-One said:
I score 3028 after benchmarking with Quadrant after these small changes in CPU stuff and i thought i wanna share it ...
I tried all kinds of things to make gaming faster and after experimenting... I got 1950+ score for 3D perfomance and these are the overall results after changing the governor and I/O:
1st try: 3128 :laugh:
2nd try: 3209 :victory:
3rd try: 2977
4th try: 3028 :laugh:
Heres how...
You only need No-CPU frlls or CPU Master or any other APP capable of changing clock speeds eg. SetCpu... :good:
Set your devices Governor to smartassV2 and i/o scheduler to vr... Clock your CPU speed to the max frequency that is stable... Mine is 1.8GHz, but can OC to 2Ghz which can make my device boiling hot.... Minimum frequency you wanna set is 600 mhz and below... And thats about it...
DO NOTE! Only some kernels can use the SmartAssV2 Governor and vr I/O scheduler... if none of them is there, I recommend you use Ondemand Govern' and Noop I/O...
Again, not all kernels are gonna have that score..
If i made a great mistake, don't be afraid to correct me especially Pepoluan ...
BTW i'm using REMICS v1.7 by sparta20 and Forvivos kernel...
Click to expand...
Click to collapse
AFAIK, governor's clock speed will be "locked" to the highest possible clock when you are running benchmark. let's take lulzactive as an example. look at this line
DEFAULT_INC_CPU_LOAD 70
Click to expand...
Click to collapse
, 70 means when processor's load is reaching 70% , the clock speed will be increased some steps. in benchmarking, cpu load is always high >>90%(i'm not sure so CMIIW) that means your clock speed will always be locked in that highest possible value no matter what your governor is (even conservative). the only difference is how long they need to get up to the next level of clock speed
so personal experience will be better to get your right value rather than benchmarking. every governor has difference time to reach higher level of clock speed which is not be able to be experienced in benchmarking. this is contrary to personal experience(daily use) which you can feel how your phone react toward a command. let's take example of the most battery saving(conservative) and highest performance(performance). you can feel that conservative is rather slow in executing command while performance will give nice personal experience. both of them didn't give any significant difference in benchmarking score but both of them can give significant difference in personal experience
i hope you get my point here
CMIIW

Thanks alot But according to personal experience, I nvr felt any lag whatsoever... In gaming like shadow gun, didn't feel that much lag compared to the stock kernel from Samsung...
Thanks for correcting me anyway! I appreciate it
Sent from my GT-I8150 using xda app-developers app

ElementalX kernel - what's the fuss about

Hey guys
Before rooting my tablet I want to know something. Whats the fuss about this specific kernel? I literally see it everywhere ( well done to the dev )
I kinda want to overclock my nexus too 1.7ghz but Im not sure that kernel can do it? I also want amazing battery life I get around 7.5 already so by no means is it bad
J
Sent from my Nexus 7 using xda app-developers app

I've got elementalx on my nexus 7 2013 : it works perfectly on 1.7ghz... And this kernel has some cool features like double tap to wake... For the battery, you can underclock but while you overclock just a bit, the battery life will be OK
So, flash it ! ?
Térence
Sent from my Nexus 7 using xda app-developers app

JackHanAnLG said:
Hey guys
Before rooting my tablet I want to know something. Whats the fuss about this specific kernel? I literally see it everywhere ( well done to the dev )
I kinda want to overclock my nexus too 1.7ghz but I'm not sure that kernel can do it? I also want amazing battery life I get around 7.5 already so by no means is it bad
Click to expand...
Click to collapse
I didn't know there was any kind of a fuss! I think that we are all lucky in the sense that we have multiple good choices for kernels on the Nexus devices and most others in general.
It goes without saying that any custom kernel is going to give you the ability to overclock and it just boils down to what the max MHz is that any specific device can handle. Not that I've tried it but I've seen claims of 1.9 MHz and higher (ElementalX) running fine but each device is going to be different and I personally don't see the point of overclocking that high. I've had mine at 1.7 and 1.8 MHz to run some benchmarks, try different governors (elementalX & ondemand) and get an idea about battery life at those frequencies. Did all that so I can get a comparison to what I see running 1.6 MHz which is what I use everyday, that plus the gpu is set at 450 MHz while using the ondemand governor for both cpu and gpu. I do have to say that my N7 ran very well at 1.7 and 1.8 MHz but "my" goal is to get the best combination of performance and battery life, for my use. I generally see 7- 10 hrs of screen on time which includes watching video and some gaming. Not using any third party apps to control the kernel, mostly default settings when using the aroma installer, slight undervolt for 384 MHz, I don't use DT2W or S2W,. Basically... it's just too easy to install the ElementalX kernel, not worry about having to dial it in and still see a noticeable improvement in performance and battery life. No fuss, no muss!

What are your settings?
!PimpedOutNexus7!

shaolinz said:
What are your settings?
!PimpedOutNexus7!
Click to expand...
Click to collapse
Aroma installer;
Set each core separately = no
Max Cpu Frq = 1620Mhz
L2 cache and bus = elementalx
Undervolt = 850 min
Thermal = run hot. Mine never gets hot at 1.6 MHz and this way you don't have to worry about thermal throttling.
Max GPU = 450 MHz
Gpu governor = ondemand
i/o scheduler = deadline.
Sleep/wake settings = None
Other settings = use stock ondemand settings. enable max screen freq, enable usb fastcharge, disable magnetic screen off, disable fsysnc, all other options unchecked,
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
You can use the elementalx governor which does a great job and does improve battery life. In the other settings page leave "use ondemand governor' unchecked and check the box for "gboost." For gaming I personally like to leave mine set up with the ondemand governor, seems just a little bit smoother with less frame drops. You can try both to see which works better for you.

Thanks a lot in will let you know how it goes ....great help +1
!PimpedOutNexus7!

Hmmm feels like its running hot
!PimpedOutNexus7!