Database Develop

Governors and Schedulers, Explained.

Ok guys, this is going to be a long post but I think in the end, it will put a lot of good information to everyone to help them understand kernels a little better. I may not have a machine to be able to develop but I do know quite a bit of stuff lol. Anyway, here's a thread to inform everyone about the different sections of kernels.
First I would like to give some "thanks."
mtmichaelson - for giving us this badass 1.9gHz kernel to play with and for doing soooooo much for development! We are forever in your debt.
droidphile - for teaching me just about everything I know.
*I'm sure there are more people and if I missed you, let me know!*
First, let's start with "governors."
OnDemand:
The default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as CPU activity is detected to ensure the responsiveness of the system. Effectively, it uses the CPU busy time as the answer to the "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 decides the next target frequency by instant requirement during sampling interval. The instant requirement can respond quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a longer time and it possibly causes frequent changes between highest and lowest frequency.
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 was equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
Smartass2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many people. The governor aims for an "ideal frequency", and ramps 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 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.
Userspace:
Instead of automatically determining frequencies, it lets the user set the frequencies.
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).
Performance:
Sets min frequency as max frequency. Very useful while benchmarking!
Smoothass:
The same as the Smartass “governor” But MUCH more aggressive & across the board this one has a better battery life that is about a third better than stock KERNEL.
Now for the "schedulers."
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 (yes, like a flash drive). Advantage here is that flash drives do not require reordering of multiple I/O requests unlike in normal hard drives.
*Advantages*​1. Serves I/O requests with least number of cpu cycles. (Battery friendly?)
2. Best for flash drives since there is no seeking penalty.
3. Good throughput on db systems.
*Disadvantages*​1. Reduction in number of cpu cycles used is proportionate to drop in performance.
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*​1. Nearly a real time scheduler.
2. Excels in reducing latency of any given single I/O.
3. Best scheduler for database access and queries.
4. Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
5. Like noop, a good scheduler for solid state/flash drives.
*Disadvantages*​1. When the system is overloaded, the set of processes that may miss deadline is largely unpredictable.
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.
*Advantages*​1. Considered to deliver a better balanced i/o performance.
2. Easiest to tune.
3. Excels on multiprocessor systems.
4. Best database system performance after deadline.
*Disadvantages*​1. Some users report that media scanning takes longer 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.
2. Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.
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*​1. Simple, very very reliable.
2. Minimized starvation of requests.
*Disadvantages*​1. Slow random-read speeds on flash drives, compared to other schedulers.
2. Sequential-read speeds on flash drives also not so good.
============================================================
That's about all I have for now lol. If I can think of anymore stuff to post on here, I'll get it as soon as I get a chance. Thanks for reading!

Reserved for more info!

Thanks!!!
Can you also include information about smoothass?

Missed interactive. Fyi stock gov on this thing. Which is odd and the first time I've ever seen that.
Sent from my Transformer Prime TF201 using xda premium

Haro912 said:
Missed interactive. Fyi stock gov on this thing. Which is odd and the first time I've ever seen that.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Blitzed doesn't have Interactive which is why I left it out. Fyi not the default lol
Sent from my Volted Ice Revo using Tapatalk.

spc_hicks09 said:
Blitzed doesn't have Interactive which is why I left it out. Fyi not the default lol
Sent from my Volted Ice Revo using Tapatalk.
Click to expand...
Click to collapse
By on this thing I was hoping everyone would realize that I was on my Prime at the time. It's the default on there

Haro912 said:
By on this thing I was hoping everyone would realize that I was on my Prime at the time. It's the default on there
Click to expand...
Click to collapse
Oh lol sorry I thought you were talking about the Revo.
Sent from my Volted Ice Revo using Tapatalk.

Thanks for taking the time to explain all of that. I learned a few things.
Sent from my Blitzed supercharged Volted Ice Revo

scyther2333 said:
Thanks!!!
Can you also include information about smoothass?
Click to expand...
Click to collapse
I should be adding stuff about smoothass soon.
Sent from my Volted Ice Revo using Tapatalk.

Excellent thread hicks, thanks for the info!
Sent from my VS910 4G using XDA App

thanks a lot...
don't mean to add more work for you but i think it would be great if you could give an overview of governors and schedulers and how/why they work in android

scyther2333 said:
thanks a lot...
don't mean to add more work for you but i think it would be great if you could give an overview of governors and schedulers and how/why they work in android
Click to expand...
Click to collapse
Lol that's pretty much exactly what this thread is.

I second that
Obsidian_soul said:
Thanks for taking the time to explain all of that. I learned a few things.
Sent from my Blitzed supercharged Volted Ice Revo
Click to expand...
Click to collapse
Thanks from me too... very informative.... and appreciated.
St3vi3

Can we get an explanation of smoothass please? I can't seem to find much with a standard google search, well except for some things I'd rather not mention lol
Thanks hicks
Sent from my VS910 4G using XDA App

OP updated with the "short and sweet" descriptive of "Smoothass."
scyther2333 said:
thanks a lot...
don't mean to add more work for you but i think it would be great if you could give an overview of governors and schedulers and how/why they work in android
Click to expand...
Click to collapse
corypwrs said:
Can we get an explanation of smoothass please? I can't seem to find much with a standard google search, well except for some things I'd rather not mention lol
Thanks hicks
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
^ This made me laugh my ass off haha. I just pictured someone sitting at maybe a library or some public computer and innocently trying to find info on the "smoothass" governor hahahahaha!

spc_hicks09 said:
^ This made me laugh my ass off haha. I just pictured someone sitting at maybe a library or some public computer and innocently trying to find info on the "smoothass" governor hahahahaha!
Click to expand...
Click to collapse
I wasn't really thinking about it much until the search results came up. Luckily I was on my laptop at home or else it would've been awkward for me lol
Sent from my VS910 4G using XDA App

Just curious, why does, smartass2 and smoothass only utilize stock cpu speeds?
Sent from LG Revo Gingervolt 2.0, Hack the Planet. Using XDA App

SnoeDogg said:
Just curious, why does, smartass2 and smoothass only utilize stock cpu speeds?
Sent from LG Revo Gingervolt 2.0, Hack the Planet. Using XDA App
Click to expand...
Click to collapse
It doesn't. It uses all speeds that I included.
Sent from my VS910 4G using xda premium

mtmichaelson said:
It doesn't. It uses all speeds that I included.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
+1
Most of the descriptions here are for a stock Gingerbread kernel.
Sent from my Dread Ginger Revo using Tapatalk.

I figured it out. Im using CPU Master and i had to set thru the program and then thru the widget for some reason. Thanks
Sent from LG Revo Gingervolt 2.0, Hack the Planet. Using XDA App

[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

[POLL][Zeus][UV] which is your max uv?

Hi all,
Since Zeus v6.39 it is possible to undervolt our OB's. I am curious till what level you all can undervolt your OB. Please test the maximum undervolt level at least for a day or so before reporting, so we can be reasonably sure it is stable. And to make comparison possible, keep other settings standard please, so CPU 300 - 1000 MHz, DVFS enabled.
Personally my OB is currently running stable @ the -5 voltage level. -7 gave me an SOD while the screen was off within a few hours and @ -6 parts of my wallpaper went black (GPU problem?).
Happy polling!

I vote for -7. When I enable DVFS I have some lag so I disabled it. In 1.5 days of usage battery gone empty. (some surf on Wifi, some calling, playing some games etc.) I played Max Payne without any lags and got no SODs so far.
AFAIK, DVFS is dynamic voltage and frequency scaling and setting contstant voltage level when it is activated is something not suitable for it's nature. So I don't use bot of them at the same time.

i can't really feel the difference.. stock freq, dvfs enabled, smartassv2 and sio.
voltage now on -7 for a few hours but i can't notice any difference.

Didn't see difference in performance which is a good sign and battery life fulfill my needs : DVFS enable, freq 100-1000, UV -7, smartass2 and SIO. Never got any SOD since its release (and using LG lockscreen).
Sent from my LG-P970 using xda premium

My phone is fully stable at -7 (100-1000mhz). Need more undervoltage. Battery life is more important than cpu perfomance (imho).

I_SBerg said:
I vote for -7. When I enable DVFS I have some lag so I disabled it. In 1.5 days of usage battery gone empty. (some surf on Wifi, some calling, playing some games etc.) I played Max Payne without any lags and got no SODs so far.
AFAIK, DVFS is dynamic voltage and frequency scaling and setting contstant voltage level when it is activated is something not suitable for it's nature. So I don't use bot of them at the same time.
Click to expand...
Click to collapse
Where did you get this information about DVFS from? It sounds plausible because of the name, but I cannot find such information in the Zeus thread. A different possibility is that with the voltage tweaks in Zeus you only change the sort of average voltage of the OB and DVFS dynamically adjusts this to the needs of what you are doing. But this is all guessing for me.
Although I feel it might eat some battery (I don't know for sure) I like DVFS on because I feel a heavy game like Angry Birds Space becomes more responsive with it.

-7, 100-1200

On zeus 6.39O stable with -5 300 - 1200 mhz. +5 to -5 gave about the same score in quadrent.
Battery usage is quite good
-6 gives me lag..
Sent from my LG-P970 using xda premium

dflt said:
-7, 100-1200
Click to expand...
Click to collapse
what are you trying to say here?
Verstuurd van mijn LG-P970 met Tapatalk

I have 100-1100mhz and -3 very well battery and good Performance
Sent from my LG-P970 using xda app-developers app

KC Boutiette said:
Where did you get this information about DVFS from? It sounds plausible because of the name, but I cannot find such information in the Zeus thread. A different possibility is that with the voltage tweaks in Zeus you only change the sort of average voltage of the OB and DVFS dynamically adjusts this to the needs of what you are doing. But this is all guessing for me.
Although I feel it might eat some battery (I don't know for sure) I like DVFS on because I feel a heavy game like Angry Birds Space becomes more responsive with it.
Click to expand...
Click to collapse
Searched net. eg: http://www.emo.org.tr/ekler/035226640b6b89f_ek.pdf

I have 100-1350mhz with -7 stable .

-7, 1350
Sent from my LG-P970 using Xparent ICS Tapatalk 2

I_SBerg said:
Searched net. eg: http://www.emo.org.tr/ekler/035226640b6b89f_ek.pdf
Click to expand...
Click to collapse
Hey thanks for the info! That clarifies a lot to me about what they mean with DVFS.
However, I still dont believe setting the voltage level and DVFS dont go well together. To be more precise I dont believe you make the cpu voltage constant by setting the voltage level in Zeus Tweaker. I believe you make the CPU voltage constant by disabling DVFS.
In a different way: setting the voltage level to 0 would be the original 'stock' level right? So why would LG include DVFS on our OB if it would not work?

KC Boutiette said:
Hi all,
Since Zeus v6.39 it is possible to undervolt our OB's. I am curious till what level you all can undervolt your OB. Please test the maximum undervolt level at least for a day or so before reporting, so we can be reasonably sure it is stable. And to make comparison possible, keep other settings standard please, so CPU 300 - 1000 MHz, DVFS enabled.
Personally my OB is currently running stable @ the -5 voltage level. -7 gave me an SOD while the screen was off within a few hours and @ -6 parts of my wallpaper went black (GPU problem?).
Happy polling!
Click to expand...
Click to collapse
Hmmmmmmm.... scratch that -5. My OB was acting funny, could not take a screenshot and all the power toggles in the notifications area were on one screen all of the sudden. Reboot and I am back to -4 now, cant change the poll however, can I?

-3, 100-1100 works well for me, good battery life too :fingers-crossed:

is anybody comparing with the stock settings?
i monitor with battery monitor widget and so far i haven't found any setting that gives a better battery usage then stock setting.

Post your SetCPU / No Frills Settings (governor, min/max frequency, i/o scheduler)

Post your SetCPU / No Frills Settings (governor, min/max frequency, i/o scheduler)
Share your SetCPU or No Frill CPU settings .. You can share the following things..
Minimum and Maximum frequency
Governor used
I/o scheduler used
Profiles (if any)

I, myself am using...
Governor = SmartassV2
Max freq. = 806 MHz
Min freq. = 122Mhz
Scheduler - sio
Profiles = None

added a heat profile which turns on when the temp is over 35°C and sets the MHz to 320-600
Had some reboots because of the heat these days :S
Sent from my HTC Desire C using xda app-developers app

I have no schedule and no profiles
Sent from my HTC Desire C using xda premium

smoza said:
I have no schedule and no profiles
Sent from my HTC Desire C using xda premium
Click to expand...
Click to collapse
Pon de mínimo 320-480

Perfect balance..
Max 700
Min 100
Smartassv2
Max 850 while playing games
And a heat profile
Using cm10 and NOPE

aashay960 said:
Perfect balance..
Max 700
Min 100
Smartassv2
Max 850 while playing games
And a heat profile
Using cm10 and NOPE
Click to expand...
Click to collapse
What is a heat profile?

LaKsHaY1997 said:
What is a heat profile?
Click to expand...
Click to collapse
If battery temperature more than 39 C, max frequency to 400..
Thats what I use

aashay960 said:
If battery temperature more than 39 C, max frequency to 400..
Thats what I use
Click to expand...
Click to collapse
If battery temp is over 39 C I shove it in the freezer !!
I've always insisted performance/sio is best . After being literally forced screaming and kicking to try his preferred settings I now like interactive/row for daily and performance/deadline for benching

whoamigriffiths said:
If battery temp is over 39 C I shove it in the freezer !!
I've always insisted performance/sio is best . After being literally forced screaming and kicking to try his preferred settings I now like interactive/row for daily and performance/deadline for benching
Click to expand...
Click to collapse
I use these settings for daily use not for benchmarking (which I RARELY do). So according to you what should be a comfortable temperature to set? Also, does the country make a difference? If it does, the climate in india is very hot right now
Performance/sio = Bad battery life + Frequent overheating?? Is this true?

aashay960 said:
I use these settings for daily use not for benchmarking (which I RARELY do). So according to you what should be a comfortable temperature to set? Also, does the country make a difference? If it does, the climate in india is very hot right now
Performance/sio = Bad battery life + Frequent overheating?? Is this true?
Click to expand...
Click to collapse
I imagine country has an awful lot to do with the cpus temp . I'm in the UK and I really don't recall ever going over 38 degrees C (more like 36)
And yes performance/sio will be bad battery life cos if its my phone its ramped to 828min /828 max and being tortured for 12 hours at a time
as I said in the uk I've never had issues with overheating

whoamigriffiths said:
I imagine country has an awful lot to do with the cpus temp . I'm in the UK and I really don't recall ever going over 38 degrees C (more like 36)
And yes performance/sio will be bad battery life cos if its my phone its ramped to 828min /828 max and being tortured for 12 hours at a time
as I said in the uk I've never had issues with overheating
Click to expand...
Click to collapse
I've tried different settings and 39 is the point where it starts to 'feel' hot. So then setcpu works its magic and i stop working if its not impotant, screen off, and then I'm back

I live in Ireland and today for the first time ever I got a SetCpu notification because of overheating ha, although it was a hot day
Sent from my HTC Desire C

DillaDawg said:
I live in Ireland and today for the first time ever I got a SetCpu notification because of overheating ha, although it was a hot day
Sent from my HTC Desire C
Click to expand...
Click to collapse
SetCpu gives notifications? Didn't knew that.

This has been my setup for a while now:
SetCPU:
Min/Max: 75/750 MHz
Governor: Lulzactive
I/O Scheduler: row
Profiles:
a) 100 priority: Screen Off: 200 Min-300 Max: Lulzactive: row
b) 99 priority: Charging: 600 Min-750 Max: Lulzactive: row
My CPU can't handle over 750 Mhz... but I really don't need much CPU speed anyway

i'm quite new to these things with the no-frills app. I need someone who can tell me which options are best for saving up battery while still being able to do some basic stuff without any effort from the device (and to play some games from time to time ). I have no idea what all of the schedulers do
here they are if someone can explain what each does :
abyssplug
ondemandq
lagfree
lazy
smartassv2
interactivex
pegasusq
hotplug
conservative
userspace
powersave
lionheart
ondemand
performance
and the things at the right :
noop
deadline
row
cfg
btw today I flashed goldenkernel v2 on my s3 mini (mainly because of the ability to have more battery life), but don't know what setup to make in no-frills in order to save battery and keep my phone with good performance.
Please HELP !!

koragg97 said:
i'm quite new to these things with the no-frills app. I need someone who can tell me which options are best for saving up battery while still being able to do some basic stuff without any effort from the device (and to play some games from time to time ). I have no idea what all of the schedulers do
here they are if someone can explain what each does :
abyssplug
ondemandq
lagfree
lazy
smartassv2
interactivex
pegasusq
hotplug
conservative
userspace
powersave
lionheart
ondemand
performance
and the things at the right :
noop
deadline
row
cfg
btw today I flashed goldenkernel v2 on my s3 mini (mainly because of the ability to have more battery life), but don't know what setup to make in no-frills in order to save battery and keep my phone with good performance.
Please HELP !!
Click to expand...
Click to collapse
READ HERE: http://bit.ly/1dwdKpf
By the way, next time post in your device's forum, this is for HTC Desire C.

atomomega said:
READ HERE: http://bit.ly/1dwdKpf
By the way, next time post in your device's forum, this is for HTC Desire C.
Click to expand...
Click to collapse
thanks and sorry about the post but i completely forgot to check out if this article is for my s3 mini. when i found it i was so happy that i could ask my question here that forgot about everything else

my config
i am using xperia m dual(C2004) below are my config

karthikgoud said:
i am using xperia m dual(C2004) below are my config
Click to expand...
Click to collapse
Actually this is a desire c forum.. But I'll post mine too (as a old desire c user)
Xperia sp (c5303) on cm11
Sent from my C5303 using XDA Free mobile app

Battery life and CPU

Although this might seem as a question. It really isnt.
What kind of battery life do you get on the First? Screenshots would be nice, but what is like the max time and min time you got and what kind of setting do you use, voltage, clock speed, usage etc.
Also has anyone been using the MSM-DCVS (dynamic clock and voltage scaling) CPU Governer? And if yes then have you gotten better battery life? I will do a test tomorrow and see how it goes.
My best stats.
Well before i got into cpu governors, by default the phone uses on-demand and i could max out 14 hours with variable usage. screen on maybe 50% of the time the phone was on and minimal gaming. texting. I dont have data so that didnt take any battery (i hear 4g and 3g take away lots of juice, is that true?).

Okay. So just did a quick test with msm-dcvs.
Basically for 5 minutes I tested each governed doing the same stuff.
Msm-dcvs utilizes deep sleep ALOT more. Almost 8 times more than on demand. And doesn't really use anything in between. So it goes from deep sleep to minimum 300mhz to get it going and then jumps to the max of 1.4ghz and if the screen is on it uses 700mhz.
So using deep sleep it saves batter.
On demand on the other hand tends to use 300mhz instead of deep sleep. It also jumps around a lot between all the various clock speeds using just about anything it can. So i guess on demand will get worse battery life but I will report my findings in a few hours seeing bow battery life goes with dcvs.
Sent from my HTC first using XDA Premium 4 mobile app

Just a quick update. On demand is crap. Performance is really good and dcvs is performance just more intelligent
Sent from my HTC first using XDA Premium 4 mobile app

My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick

abrahammmmmmm_ said:
My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick
Click to expand...
Click to collapse
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app

russian392 said:
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What app do you use for this? All the ones I've tried don't make any custom settings stick

abrahammmmmmm_ said:
What app do you use for this? All the ones I've tried don't make any custom settings stick
Click to expand...
Click to collapse
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app

russian392 said:
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?

It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.

G00fY2 said:
It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.
Click to expand...
Click to collapse
Wow that's great battery life.
I'm yet to test dcvs in my first and see how long that lasts me. I have Wi-Fi on all day. So I can get up to 14 hours max.
Sent from my HTC first using XDA Premium 4 mobile app

abrahammmmmmm_ said:
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?
Click to expand...
Click to collapse
No I have yet to figure out io bit tinkering with voltage isn't a good idea since the battery is specifically set to a voltage the phone needs.
Sent from my HTC first using XDA Premium 4 mobile app

Okay I have some new findings. Idk about the custom kernel...bit with stock you only get 3 I/o schedulers. Noop, deadline, and cfq. Noop is first come first serve. Deadline reorders the task sequence and does what it thinks should come first...good for like gaming. And cfq. Which evenly distributes the power amongst all tasks. If you are using cfq make sure you kill unused tasks all the time. If you use a lot of things on your phone and multitask a lot use deadline. Noop is pointless unless you don't use your phone for anything. And cfq is just an alternative to deadline. So I/o won help much.
Then in CPU master. Go to advanced. And press "disable perflock". It will explain what it does. Hit set on boot. And reset you clock settings. Now we shall see what we get.
Sent from my HTC first using XDA Premium 4 mobile app

Okay guys. I used deadline to see if that would change anything. With the same dcvs setting with deadline I got 15% batter down in 2 hours. That's pretty good. That's 7.5% an hour.
And this is with screen on and wifi on about 70% of the time.
Sent from my HTC first using XDA Premium 4 mobile app

Okay this is my final say on how to get the most out of your battery life.
There are two set ups
1. Lag free/ smooth set up
Min 384mhz, Max 1080mhz
Governer: Performance
i/o Scheduler: Deadline
-This set up will save battery why? Because 1. You don not need your max 1.4 ghz to keep the phone running lag free, and in performance mode, the phone is LOCKED into 1.4ghz until you dim the screen and it goes into deep sleep. no inbetween. So clocking down will help save EVEN MORE battery. So unlike dcvs you will not have lag when you turn your screen on. It will jump from zero to 1ghz in a few milliseconds.
2. Inteligent
Min: 432mhz, Max 1.4ghz (default max. Dont over clock)
Governer: MSM-DCVS
i/o Scheduler: CFQ
-This set up will save battery, i go down about 1% every 6-20 minutes depending on usage. (6 being max usage and 20 meaning iddle). Once you turn the screen on your device will lag slightly and then will work just fine. This set up is good for those people who dont ALWAYS need max performance. Example: Reading an email doesnt require your phone to be locked at max frequency all the time so it will down clock the device. It simply takes time for it to rev the engine.
3. On Demand
Well this is simply absoule minimum to absolute maximum with NOOP as the i/o. This is the ultimate ondemand set up as it will do what you are currently doing first then do the rest while constantly changing clock speed.
Also...btw changing clock speed takes battery that is why performance saves batter not uses it. Its either deep sleep or max and thats it.
I will add screenshots to this soon once im done with all my tests.

Battery life today on msm-dcvs
I should be at 30% right now bit pretty good battery tight now
Sent from my HTC first using XDA Premium 4 mobile app

Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).

Hulo_ said:
Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).
Click to expand...
Click to collapse
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!

russian392 said:
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!
Click to expand...
Click to collapse
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions

abrahammmmmmm_ said:
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions
Click to expand...
Click to collapse
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app

russian392 said:
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I should add that the optimized battery life for LTE is only true tho for new snapdragon CPU's including Apple's processors as well. I'm not aware of tegra or any exynos at the moment.