Database Develop

[Q] Explanation of different governors

Hi guys.
I would like to know the differences amongst various governors. I googled a bit and both on the net and XDA I found some explanations, but not all the governors I have are properly explained. Some of them are not explained at all.
Is there anybody able to help me?
I found some info here and here
The governors I have with FM1.5 not explained are:
lazy
lulzactive
lagfree
intellidemand
smartassv2
ondemandx
Ok, some of them like lagfree could be self-explanatory, but I would be grateful if somebody could be more clear...
Thanks as usual to all!!

bump.
no one?

Note to myself: answer this thread when you get home...

Not at home? :-D
Sent from my GT-N7000 using Tapatalk

Diamantes said:
Not at home? :-D
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
have you reached home yet? would be glad if you could answer

I was in Prague for a week
Ok, so, to be honest using only Google I found this:
lazy (http://forum.xda-developers.com/showthread.php?t=1276092) - is ondemand but with an added option to stay longer on a certain frequency. This is due to the fact that some CPU's dont like too quick freq changes when sampling rate for decision making is set too low. See link for more.
lulzactive (http://tegrak2x.blogspot.com/2011/11/lulzactive-governor-v2.html) - is basically interactive governor with added smartass bits and variable (as opposed to fixed amout) frequency scaling, based on currently occuring cpu loads. Has, like smartass, a sleep profile built-in. See link for details on exact scaling.
lagfree (http://forum.xda-developers.com/showthread.php?t=1272933) - seems to be ondemand but with a lessend tendency to ramp up to 100% but rather also use steps available in between 0-100%.
intellidemand (freely translated from http://www.android-hilfe.de/root-hacking-modding-fuer-samsung-galaxy-s2/185085-ist-ein-governor.html) - behaves like ondemand when the system is under heavy use, it behaves differently when the system is mostly ideling. That mode is colled "browsing mode" or "browser mode" or whatever. It seems to be some sort of "intelligent" demand sensing/analysing ondemand governor.
smartassV2 - this one should be known. It's the same as smartass(V1) but tweaked. Same code author. I heard one should use smartassV2 instead of smartass when available.
ondemandx - is ondemand with an added sleep profile built-in. I believe all ...X kernels are the default kernels but with an added sleep profile.
Just in case you wonder: I use Savagedzen, I somehow like it best. And I have to get up at 4:20am thats in 2:48h so you may excuse me if I go to bed.

thanks +1

Hope you found the info you were looking for already, if not - take a look at this: http://forum.xda-developers.com/showthread.php?t=1369817

[Q] Which is the most recommended Governor

I'm using emanoN V4 with No-Frills, and since CM7.1 with SetCPU, I always used 'ondemand' as Governor.
But reading other posts on other devices forums about this, some people say SmartassV2 is the best...
So, as each device is different (specially by the ARM version and manufacturer), I decided to begin this conversation here, and listen to what people with the same device as me has to say about it.
So which Governor do you consider the best for SGM?

Im using cm7.2, setting at nofrilis Governor : SavagedZen io : sio and undervolt at cm setting, give more battery life.
Sory for bad english
Squadzone my idols

felipevsw said:
I'm using emanoN V4 with No-Frills, and since CM7.1 with SetCPU, I always used 'ondemand' as Governor.
But reading other posts on other devices forums about this, some people say SmartassV2 is the best...
So, as each device is different (specially by the ARM version and manufacturer), I decided to begin this conversation here, and listen to what people with the same device as me has to say about it.
So which Governor do you consider the best for SGM?
Click to expand...
Click to collapse
sio if u need less laggy n smooth

v-mix said:
sio if u need less laggy n smooth
Click to expand...
Click to collapse
Thanks for the reply, but as I can see on No-Frills, sio is th I/O Scheduler, that is already set. I'm asking here about the Governor.

Ondemand and set noop
Sent from my GT-S5570 using xda premium

on emanonV4 i use Smartassv2 nd i/o noop

I see that people are very divided between ondemand and SmartassV2.
Now with sio and noop as I/O Scheduler.
Anyone else would like to share?

i will say ondemand because cpu will be set at lowest frequency and when you need it it will set at higher frquency which will save your battery and if you want performance then no lag will be good

The principle of the ondemand governor I'd already figured out (and actually didn't like it, very rough).
I would like to hear more about the principle of the SmartassV2, whereas since this morning I'm using SmartassV2 + noop and I noticed my SGM way smoother than with ondemand + sio.
Now is wait and see if the battery is sucked more.

felipevsw said:
The principle of the ondemand governor I'd already figured out (and actually didn't like it, very rough).
I would like to hear more about the principle of the SmartassV2, whereas since this morning I'm using SmartassV2 + noop and I noticed my SGM way smoother than with ondemand + sio.
Now is wait and see if the battery is sucked more.
Click to expand...
Click to collapse
smartassV2 is a re-working of the original smartass governor, it allows for the CPU to scale through all frequencies from the lowest you set to the highest, based on the load occuring. Basically it scales CPU based on realtime needs of the system, saV2 supposedly incorporates some more agressive settings for screen off, and I believe quicker scaling than the original smartass.

dhlalit11 said:
smartassV2 is a re-working of the original smartass governor, it allows for the CPU to scale through all frequencies from the lowest you set to the highest, based on the load occuring. Basically it scales CPU based on realtime needs of the system, saV2 supposedly incorporates some more agressive settings for screen off, and I believe quicker scaling than the original smartass.
Click to expand...
Click to collapse
Thanks a lot, man! And now I think that I had made my choice:
Governor: SmartassV2
I/O Scheduler: noop
Highly recommended!

[Q] Best governor Scheduler combo ?

Which combination of governor and scheduler gives the best performance for ICS Stock ? And which one for better battery life ?

Akilesh said:
Which combination of governor and scheduler gives the best performance for ICS Stock ? And which one for better battery life ?
Click to expand...
Click to collapse
Other said it is pegasus and devs say it is all the same just a little difference.

jonpaslim said:
Other said it is pegasus and devs say it is all the same just a little difference.
Click to expand...
Click to collapse
I was told by the majority it goes in this order:
1) Pegasusq
2) Lulzactive
3) SmartassV2
4) Ondemand
5) Hotplug
6) Interactive
... and the rest.
And for IO Scheduler:
1) VR
2) CFQ
3) SIO
The truth is that, this is a Dual Core Phone with 1GB RAM, and improved Android 4.03+ kernel. So the previous hardware and software limitations NO LONGER applies. Coming FROM the DEVELOPERS of governors and schedulers the best ones seem to be:
1) InteractiveX2
2) HotplugX
3) Ondemand
... then lulzactive ~ pegasusq > smartassV2
And for IO Schedulers:
1) SIO
... then the rest
The truth is you should use the DEVELOPER recommended governor and sio scheduler, for an extensive period (1-2 days) and compare them. Finding what works best for you. After that's done, then you should go further stability testing with Voltage Control. Eg, UC your lowest frequency, OC your highest frequency and UV each step to the NEEDS of your device, each device is UNIQUE and functions DIFFERENTLY.
I think doing so you should extend your battery life by 1 or 1.5hour per cycle, while maintaining or increasing performance.

it all depends on the ROM + Kernel and more importantly the user and how they use their Note.
For me, I use Performance + Noop.. But ive had good results with pegasusq + sio
The only way to get the best combination is to try them all, But give them time to perform, Dont make a decision after 5 mins of usage, Test them heavily, Do some serious Gaming + Multitasking and chose one that outperforms the rest !

I'll start testing and post results from time to time.
Sent from my GT-N7000 using xda premium

azzledazzle said:
it all depends on the ROM + Kernel and more importantly the user and how they use their Note.
For me, I use Performance + Noop.. But ive had good results with pegasusq + sio
Click to expand...
Click to collapse
But the performance governor never scales down but always runs at maximum frequency. How is battery life with that? Must be horrible?!

Kangal said:
I was told by the majority it goes in this order:
The truth is you should use the DEVELOPER recommended governor and sio scheduler, for an extensive period (1-2 days) and compare them. Finding what works best for you. After that's done, then you should go further stability testing with Voltage Control. Eg, UC your lowest frequency, OC your highest frequency and UV each step to the NEEDS of your device, each device is UNIQUE and functions DIFFERENTLY.
I think doing so you should extend your battery life by 1 or 1.5hour per cycle, while maintaining or increasing performance.
Click to expand...
Click to collapse
I agree, governors even if they have the same stock names(i.e ondemand) has been heavily tweaked by the kernel dev so that you maximize performance and batt life. Start off by using the kernel/scheduler suggested by the kernel dev.
The only thing I care about is running out of juice when I don't have access to something that can charge my phone, as long as i get 10-15hrs off batt life and solid performance I'm good. Still I always bring a wall charger/usb cord with me if i really needed the extra juice.
Remember you can charge the battery but you can't charge performance

Coxeroni42 said:
But the performance governor never scales down but always runs at maximum frequency. How is battery life with that? Must be horrible?!
Click to expand...
Click to collapse
I get around 24 hours from my battery and I'm happy with that, besides I'm always somewhere where I can charge my phone should by battery run out
Sent from my GT-N7000 using Tapatalk 2

chickentuna said:
Remember you can charge the battery but you can't charge performance
Click to expand...
Click to collapse
This sentence doesn't make sense at all.
Unless you mean you can change or recharge the battery, which is straight-forward.
But you can "change" (increase) the performance. Just clear all background tasks, go to Voltage Control and overclock the cpu frequency upto 1.704GHz (with +1400mV) and keep it at that frequency by using the Performance governor. Also overclock your gpu upto 400MHz (with +1,000mV).
Though I don't recommend that, stability issues, warming issues and possible physical damage to your processor. But use the same concept, just not Overclock too much!
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
azzledazzle said:
I get around 24 hours from my battery and I'm happy with that, besides I'm always somewhere where I can charge my phone should by battery run out
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
That's simply NOT true.
Otherwise you have your phone in deep sleep/idle far more than the average user, barely using your phone.
Other possibility is that you've severely underclocked your maximum frequency, and have a long time in idle.
Performance governor = Always on maximum frequency.
NOTE's maximum frequency uses 1300+ mV. The NOTE's battery size is 2,500 mAh. Simple maths will tell you 24hrs is impossible ; )

But it is true I'm not saying my phone will be awake for 24 hours I'm saying I charge it roughly every 24 hours, I know performance keeps the phone at max speeds but I am human I will sleep for about 8-9 hours, so in result so will my phone.
And I don't use my phone every minute of the day I do have work to do so my battery life is what I say it is. What I consider 'average use' might be absolute minimal use to you so maybe that's why you doubt me,
I personally don't mess with voltages and things cause I don't understand them but I use note core kernel which is highly tweaked and one of the best kernels for battery life
Sent from my GT-N7000 using Tapatalk 2

My recommendation is lulzactive.

i use hotplug+sio on maclaws slim bean,, awesome battery life

Best governor and io scheduler for a smooth performance

Hello everyone
As the title says
For anyone who has enough knowledge to advice us about this topic.
Which governor and io scheduler to use for a smooth performance and good battery life.

xhamadeex said:
Hello everyone
As the title says
For anyone who has enough knowledge to advice us about this topic.
Which governor and io scheduler to use for a smooth performance and good battery life.
Click to expand...
Click to collapse
I have found Interactive to be a good balance of performance and battery life, it is the stock governor actually. Conservative can be good as well but I like the slightly better response from Interactive. My kernel has deadline as the default and I haven't messed with it.

nathanchance said:
I have found Interactive to be a good balance of performance and battery life, it is the stock governor actually. Conservative can be good as well but I like the slightly better response from Interactive. My kernel has deadline as the default and I haven't messed with it.
Click to expand...
Click to collapse
I'm on elemental X and it provides its own governor.
I think I should stick with the governor that is provided by the kernel...

xhamadeex said:
I'm on elemental X and it provides its own governor.
I think I should stick with the governor that is provided by the kernel...
Click to expand...
Click to collapse
each kernel provides many governors for you to use.. why do i have to use the governor thats default to the kernel when the governor that i use is much better in performance and battery??? you should use whichever one you like, provided that you know what you are doing. btw, i use ondemand governor with deadline scheduler.

simms22 said:
each kernel provides many governors for you to use.. why do i have to use the governor thats default to the kernel when the governor that i use is much better in performance and battery??? you should use whichever one you like, provided that you know what you are doing. btw, i use ondemand governor with deadline scheduler.
Click to expand...
Click to collapse
Agreed?

blu active governor and cfq scheduler

HUGE RENDERING, FPS and SMOOTHNESS improvement on OOS.

I don't know if it works on OOS versions but it does, on the OB12. You need to be rooted to be doing this.
Lower the input boost to 1036 on the big and 556 on the small first. Now, change the governor of the big cluster to conservative and the small to ondemand or conservative , benefit!
To see the improvement in FPS, you need to go to developer options and switch on profile GPU rendering. For those who didn't understand this: lower the graph is, higher the fps. Hit thanks if helped

Where to change these settings?

Any kernel manager would do. I'd recommend kernel aduitor

chinmai560621 said:
Any kernel manager would do. I'd recommend kernel aduitor
Click to expand...
Click to collapse
Just change the option of GPU GOVERNER to simple_on demand one from the above mentioned app. It will work smooth.. works for me..:good:?

ashokspidy said:
Just change the option of GPU GOVERNER to simple_on demand one from the above mentioned app. It will work smooth.. works for me..:good:?
Click to expand...
Click to collapse
I'd recommend to leave it on msm-adreno.

What if I'm on RR 5.8.2 and ElementalX? I have ondemand governor option for little but don't have conservative for big cluster.

karliyo said:
What if I'm on RR 5.8.2 and ElementalX? I have ondemand governor option for little but don't have conservative for big cluster.
Click to expand...
Click to collapse
This is exclusive for OOS. In fact, the interactive is supposed to be better than the rest but it's not the case on OOS which is why I made this thread.

chinmai560621 said:
This is exclusive for OOS. In fact, the interactive is supposed to be better than the rest but it's not the case on OOS which is why I made this thread.
Click to expand...
Click to collapse
Oh alright. Little governor ondemand seems quite fine right now.
By the way, are both governors interactive by default?

karliyo said:
Oh alright. Little governor ondemand seems quite fine right now.
By the way, are both governors interactive by default?
Click to expand...
Click to collapse
Has to be. Unless you use blu_spark kernel. It uses blu_activ.

How do these changes affect the battery life?

chinmai560621 said:
Has to be. Unless you use blu_spark kernel. It uses blu_activ.
Click to expand...
Click to collapse
You mean interactive and not blu_active?
I do recommend you guys taking a look at AKT.. There are alot of peformance oriented and balanced profiles that are already better with smoothness then stock.. Also Franco has some magic with stock settings!

chinmai560621 said:
I don't know if it works on OOS versions but it does, on the OB12. You need to be rooted to be doing this.
Lower the input boost to 1036 on the big and 556 on the small first. Now, change the governor of the big cluster to conservative and the small to ondemand or conservative , benefit!
To see the improvement in FPS, you need to go to developer options and switch on profile GPU rendering. For those who didn't understand this: lower the graph is, higher the fps. Hit thanks if helped
Click to expand...
Click to collapse
Hi friend, shall I change both values of big and small? I mean maximum and minimum?

Same, cant find where to change the input values for those two.

rOck4n said:
Same, cant find where to change the input values for those two.
Click to expand...
Click to collapse
You'll see input boost in the bottom section of CPU in kernel adiutor. Core 1- 1036, core 3 -556 is what you've to do. It'll be 1324 default on both. I'm suggesting that for slightly better battery life

MarcTremonti said:
How do these changes affect the battery life?
Click to expand...
Click to collapse
Lower SOTs are obvious, but to what degree is what matters. As far as I see, it's not that much.

GUYS, I recommend not to use this anymore. Oneplus has a reason to not release the kernel with conservative on . This is because conservative is not optimized for battery while interactive is. If interactive weren't optimized for battery, it'd be better than conservative for sure. I get only 4 hr sot on conservative but 5.5 on interactive. Though this is not placebo, it has a negative impact on SOT .

When I change big cluster to conservative, those cores will always stay above 2 GHz, as shown in Kernel Adiutor.

chinmai560621 said:
GUYS, I recommend not to use this anymore. Oneplus has a reason to not release the kernel with conservative on . This is because conservative is not optimized for battery while interactive is. If interactive weren't optimized for battery, it'd be better than conservative for sure. I get only 4 hr sot on conservative but 5.5 on interactive. Though this is not placebo, it has a negative impact on SOT .
Click to expand...
Click to collapse
The thread is about more performance and you're discussing battery life....of course it will have a lower battery life, the question is are you happy when your quad-core phone stutters....

chinmai560621 said:
You'll see input boost in the bottom section of CPU in kernel adiutor. Core 1- 1036, core 3 -556 is what you've to do. It'll be 1324 default on both. I'm suggesting that for slightly better battery life
Click to expand...
Click to collapse
Got it, thank you. I did notice a slightly battery improvement after two cycles.

Little investigation..
chinmai560621 said:
GUYS, I recommend not to use this anymore. Oneplus has a reason to not release the kernel with conservative on . This is because conservative is not optimized for battery while interactive is. If interactive weren't optimized for battery, it'd be better than conservative for sure. I get only 4 hr sot on conservative but 5.5 on interactive. Though this is not placebo, it has a negative impact on SOT .
Click to expand...
Click to collapse
Good you realised that.. I did a little investigation on your tweak.. Apparently setting governor to conservative locks the frequency of big cluster to max possible, usually above 2 ghz and it will step down slowly ( by slow I mean really slow like 1-2 seconds). Thus causes you to have very less render times on gpu profile as shown in the xda portal post.. I opened up ex kernel manager and observed same freq in higher range.
After some time I just changed governor to interactive and changed minimum freq of big cluster to 2 ghz.. I observed the same render times as situation as time when conservative was set as governor...
So this tweak is nothing but type of placebo since ramping up freq can lead to faster processing
Edit.: Couple of people on xda portal have said the same.. I didn't check it..