Related
Well imma share this guide, it's from the user droidphile and this is the original post http://forum.xda-developers.com/showthread.php?t=1369817 all the credit its for him cuz he made an excellent post and explanation from governors and I/O Schedulers this is a COPY PASTE from his post but i wanted to share with you guys.
1. GOVERNORS
I) MANUAL:
These are the 17 governors we're talking about.
1) lazy
2) lulzactive
3) lagfree
4) smartassV2
5) ondemandx
6) intellidemand
7) lionheart
8) brazilianwax
9) SavagedZen
10) smartass
11) conservative
12) userspacce
13) powersave
14) ondemand
15) performance
16) Interactive
17) Interactivex
[ Governors 1 to 7 ]
1) 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. Lazy also has a screenoff_maxfreq parameter which can be configured to specify screen-off max frequency.
2) lulzactive:
This new find from Tegrak is based on interactive & smartass governors and is one of our 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.
3) 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.
4) 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 while screen is off and scales up to 500 mhz quickly when screen is on. There's no upper limit for frequency while screen is off (unlike smartass). The motto of this governor is a balance between performance and battery.
5) ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be battery friendly ondemand. When screen is off, max frequency is 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.
6) 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' (rather 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 current 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 not busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
7) lionheart:
Lionheart is a tweaked conservative governor from Knzo. You can simply modify conservative to experience lionheart. Set low up-threshold (60 or something) and lowest possible sampling rate on conservative. Lionheart's motto is extreme responsiveness and performance, at the cost of battery. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand. This could be the reason for lionheart's 'birth'.
This thread by knzo has the explanations for governors 6 to 15. So i will just give 1/2 line briefing on Governors 6 to 15.
6) brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery.
7) SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
8) smartass:
Initial version of smartassV2 with screen-off max frequency limit. Not battery friendly as smartassV2 since screen-on minimum frequency is greater than frequencies used during screen-off.
9) conservative:
A slower ondemand which scales up slowly to save battery. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle.
10) userspace:
Instead of automatically determining frequencies, lets user set frequencies.
11) 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)
12) ondemand:
Default governor in almost all stock kernels. Simply put, Ondemand jumps to maximum frequency on CPU load and decreases the frequency step by step on CPU idle. No suspend/wake profiles. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings.
13) performance:
Sets min frequency as max frequency. Use this while benchmarking!
14) Interactive:
Can be considered a faster ondemand. So more snappier, less battery. Instead of sampling at every interval like ondemand, it determines how to scale up when cpu comes out of idle. It's an intelligent ondemand because of stability optimizations.
15) Interactivex:
This is an Interactive with wake profile. More battery friendly than interactive.
Click to expand...
Click to collapse
3. I/O SCHEDULERS
Q. "What purposes does an i/o scheduler serve?"
A.
Minimize hard disk seek latency.
Prioritize I/O requests from processes.
Allocate disk bandwidth for running processes.
Guarantee that certain requests will be served before a deadline.
So in the simplest of simplest form: Kernel controls the disk access using I/O Scheduler.
Q. "What goals every I/O scheduler tries to balance?"
A.
Fairness (let every process have its share of the access to disk)
Performance (try to serve requests close to current disk head position first, because seeking there is fastest)
Real-time (guarantee that a request is serviced in a given time)
Q. "Description, advantages, disadvantages of each I/O Scheduler?"
A.
1) 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 our flash drives). 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.
2) 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.
3) 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.
4) BFQ
Instead 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.
5) 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.
6) V(R)
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.
7) 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
I hope this helps clarify your doubts about OC and I/O
Thanks, I actually was gonna ask something like this!!!
So what governer+ io scheduler combination would you recommend for extreme performance??
And for equal importance to battery and performance (like for normal daily use)???
Well atm im using this
Rom: Razodroid v1
Governor: OndemandX
I/O: vr
Max: 734 mhz
Min: 245 mhz
And this is my best quadrant score:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its stable but my average its 1,770-1,850
would be nice if other pplz post their results and scores, that way we can learn together.
Enviado desde mi GT-S5670 usando Tapatalk
Thanks
Quite an informational post.
Rom: Razodroid v1.0
Governor: Brazilianwax
I/O: vr
Max: 763 mhz
Min: 245 mhz
lomash said:
Rom: Razodroid v1.0
Governor: Brazilianwax
I/O: vr
Max: 763 mhz
Min: 245 mhz
Click to expand...
Click to collapse
Ooh vr is the most "unstable" of the lot...and with brazilianwax, how much battery life you get???
And I haven't oc'ed yet (I'll do it 2mrw)
Rom: creed's 1.6
Governor: ondemand (or sometimes userspace)
I/o: deadline
I'll post it my qaudrant after moving to creed's 1.7
I just overclocked today, so can't say much about battery life.
Changed to vr for the benchmark while fiddling with the governors. Usually, I keep it on deadline
Getting around 1800 with Ondemand and deadline.
Yeah for score i use vr nut usually i use deadline too
Enviado desde mi GT-S5670 usando Tapatalk
gave me so much knowledge haha
thankssssss
Nice thread..
My favourite setting is :
Max : 748
Min : 245
Gov : Smartassv2
I/O : Sio
Sent from my Galaxy Fit
he mentioned lulzactive as "best governer" many times..
any1 knows how to get it on our fit?
i have tried it on ace, and it certainly is better then any other governor..
Thanks very useful I got cpuspy from market and i am trying to find the best set up for. The phone
Send from my HTC Wildfire S
ROM. Wildchild. v2. 0
-Kernels, Governors and I/O Schedulers-
*OUR GOAL: To EDUCATE ourselves*
(This is a learning experience for me as well)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-PART 1-1) What is a KERNEL, and what does it do for us?
2) What are GOVERNORS, and how can we, the operators, use them to our advantage?
3) What is an I/O SCHEDULER, and how do we use it?
*In order to manually clock your kernel and use I/O schedulers you must be rooted and either using a custom kernel/ROM that supports clocking and the use of schedulers or an application with the same support*
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1) What is a kernel, and what does it do for us?
In short, the Android Kernel is an intermediary that functions between your devices CPU, memory and applications. It is the very base of the Android operating system. Written in linux, your device CANNOT function without a kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In similar terms, a kernel is much like the brain of your device. It controls EVERYTHING. For instance when you adjust the brightness slider, open an application, use your voice search function, you are sending requests to the kernel to perform that specific function. When you tap the volume rocker your device sends a request to the kernel to increase sound output. The kernel then processes the request, and the music gets louder :victory:
Click to expand...
Click to collapse
Kernels come in all different shapes, sizes, colors and flavors. ONLY FLASH KERNELS BUILT SPECIFICALLY FOR YOUR DEVICE! Let it also be known that some developers cannot/will not assist you should you flash a custom kernel over their ROM.
Click to expand...
Click to collapse
2) What are governors, and how can we, the operators, use them to our advantage?
An Android governor controls how the CPU will clock it's frequencies (minimum/maximum) in response to the users demands. It also controls how long the device will hold that specific frequency. Governors, in large, can have a profound effect on the overall performance and battery life of your device
Click to expand...
Click to collapse
Assuming that you will eventually like to tweak your kernel, it is best practice to take note of the last properly functioning settings should your experimentation's go amiss. You have been warned :silly:
Click to expand...
Click to collapse
2) What is an I/O scheduler, and how do we use it?
I/O scheduling, while a bit perplexing, is how your device prioritizes user requests. Processes come in a random order, one after the other, and here is where an I/O scheduler will come in to play. While requests wait to be fulfilled, in a random order as we've said, the I/O scheduler will organize them into the order in which they will be found on the disk, thus reducing seek time and speeding up the process of fulfillment. Requests also have deadlines, and an I/O scheduler can ensure those requests will be met before they reach said deadline. I/O schedulers operate on a first come first serve basis, ensuring your requests are met in the order in which they are received.
Click to expand...
Click to collapse
With the proper combination of a governor and I/O scheduler you can experience OPTIMUM performance (snappiness and fluidity... that buttery goodness) and maximized battery life.These settings are user dependent. What works for me may not work for you! Also note that these settings are included for experimental purposes only, and no developer can be held responsible should you choose to tweak your kernel and something goes wrong.
Click to expand...
Click to collapse
-Kernels, Governors and I/O Schedulers-
CONTINUED
-PART 2-
-GOVERNORS BROKEN DOWN AND EXPLAINED-
With a wide variety of governors from which you can choose, it may seem a bit over whelming. No worries, though. After reading through this reference guide, you will come out well informed and ready to tweak your kernel to you hearts desire :cyclops:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*Tweak at your own risk. I will claim no responsibility for any damages that may occur*
-COMMON GOVERNORS-
1) Ondemand
2) Ondemandx
3) Conservative
4) Interactive
5) Interactivex
6) Lulzactive
7) Lulzactiveq
8) Smartass
9) SmartassV2
10) Intellidemand
11) Lazy
12) Lagfree
13) Lionheart
14) LionheartX
15) Brazilianwax
16) SavagedZen
17) Userspacce
18) Powersave
19) Performance
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*To save myself a few hours of time, all credits for these descriptions go to @droidphile*
1) Ondeman: 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) Lulzactiveq:
Lulzactiveq is a modified lulzactive governor authored by XDA member robertobsc and is adapted in Siyah kernel for GS2 and GS3. Lulzactiveq aims to optimize the second version of luzactive from Tegrak by a) providing an extra parameter (dec_cpu_load) to make scaling down more sensible, and b) incorporating hotplug logic to the governor. Luzactiveq is the first ever interactive based governor with hotplugging logic inbuilt (atleast the first of its kind for the exynos platform). When CPU comes out of idle loop and it's time to make a scaling decision, if load >= inc_cpu_load CPU is scaled up (like original luzactiveq) and if load <dec_cpu_load, CPU is scaled down. This possibly eliminates the strict single cut-off frequency for luzactiveq to make CPU scaling decisions. Also, stand hotplug logic runs as a separate thread with the governor so that external hotplugging logic is not required to control hotplug in and out (turn On and Off) CPU cores in multi core devices like GS2 or GS3. Only a multi core aware governor makes real sense on muti-core devices. Lulzactiveq and pegasusq aims to do that.
8) 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.
9) 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.
10) 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.
11) 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.
12) 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.
13) 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.
14) LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
15) Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery.
16) SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
17) Userspace:
Instead of automatically determining frequencies, lets user set frequencies.
18) 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).
19) Performance:
Sets min frequency as max frequency. Use this while benchmarking!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Each and every one of these governors offer their own benefits and disadvantages. Some will provide better performance at the cost of battery life and vice versa. It is up to you, the user, to determine which governor best suits your needs. No two people use their devices the exact same way. Please, for your own sake, note your original settings and/or any subsequent settings that provided your device with stability.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This one too
just in case
First Custom Kernel for Micromax Canvas Magnus A117
WARNING:
Code:
I or xda is not responsible for any kind of damage to your device. Please use it at your own risk!
FEATURES :
As of now basic features added. Will keep updating new version regularly.
Lots of governors & I/O schedulers added ( Check below for list )
LZMA Compression for zImage and Gzip for ramdisk.
Google Snappy compression mode (v5)
Clean Cache Enabled
MTK Vermagic Hack
Optimized ARM algorithm ( Credits to @faux123 )
NTFS support.
Governors added :
Lulzactiveq
Nightmare
Smartass2
Nightmare
Pegasusq
Sakuractive
Intellidemand
zzmoove
Performance
Powersave
I/O schedulers added :
SIO
Fifo
Fiops
Row
Vr
Zen
Sioplus
Click to expand...
Click to collapse
Use Trickster mod App to change governors. For more detailed review on governors read post #3
Installation instructions :
Copy zip to your Sd card / Internal memory & reboot to recovery
Mount system ( mounts & storage -> Mount system )
Install zip
Reboot :laugh:
DOWNLOADS :
Xtreme Sandy kernel V 1.2
Note
Anyone who wants to include the Kernel in custom ROM's feel free to include after informing me. Also just link back to this thread
Older versions
V 1.0 : http://p.pw/babqRW ( Only compatible with Blu ROM
CREDITS :
@kashifmin for his support and guidance
@Siddhesh.K15 for working with me for months
Screenshots :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel sources :
https://github.com/sandymanu/A117_MT6589_kernel
XDA:DevDB Information
[KERNEL][3.4.5][Xtreme Sandy Kernel ][Smoothness] for Micromax A117, Kernel for the Micromax Canvas Magnus A117
Contributors
Santhosh M
Kernel Special Features:
Version Information
Status: Alpha
Current Stable Version: V 1.2
Stable Release Date: 2014-07-17
Created 2014-07-03
Last Updated 2014-07-23
FAQ's on Kernel :
What is a kernel? Why should I install it?
A: Click here to know the answer.
Will this work on all MT6589 / 6589T Phones?
A: NO
Is this kernel compatible with all ROMs?
A: This kernel works only on Stock ROM as of now. Other ROM's have to replace ramdisk.
Will this work on other clones of these devices such as Blu life One M ?
A: YES. It will work
Is this kernel recommended for daily use?
A: Yes!
What are the best governor+io combinations?
A: Hotplug+cfq, Smartassv2+cfq, Sakuractive+cfq. Read about governors & i/o schedulers & try them and give feedback on the thread so that others can know.
Explanation on Governors & I/O schedulers :
Read the below links for everything
http://forum.xda-developers.com/showthread.php?t=1767797 ( All governors & schedulers explained )
http://forum.xda-developers.com/showthread.php?t=2301294 ( All governors & schedulers explained )
For people who are lazy i have put through some here
Performance governor helps gaming according to people who tried my kernel in A250. I can't confirm the same here since i am not a gamer. So try that for gaming and let people know.
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.
Sakuractive:
This driver mimics the frequency scaling behavior in "on demand" but with several key differences. First is that frequency transitions use the CPUFreq table directly, instead of incrementing in a percentage of the maximum available frequency. Second "sakuractive" will offline auxillary CPUs when the system is idle, and online those CPUs once the system becomes busy again. This last feature is needed for architectures which transition to low power states when only the "master" CPU is online, or for thermally constrained devices
ZZmoove
ZZmove Governor optimized for low power consumption with the screen off, with particular attention to the limitation of consumption applications in the background with the screen off, such as listening to music. It has three settings: battery saver, balanced and performance. In addition to a performance boost, there is also the governor zzmove optimized.
Pegasusq/Pegasusd
The Pegasus-q / d is a multi-core based on the Ondemand governor and governor with integrated hot-plugging.
Ongoing processes in the queue, we know that multiple processes can run simultaneously on. These processes are active in an array, which is a field called "Run Queue" queue that is ongoing, with their priority values arranged (priority will be used by the task scheduler, which then decides which process to run next).
To ensure that each process has its fair share of resources, each running for a certain period and will eventually stop and then again placed in the queue until it is your turn again. If a program is terminated, so that others can run the program with the highest priority in the current queue is executed.
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.
I/O Schedulers :
I/O Schedulers Explained
1: 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 our flash drives). 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.
2: 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.
3: 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.
5: 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.
6: V(R):
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.
I congratulate you on your amazing work. Looking forward to more from you.
Grounded for long; its time now to fly...
Click to expand...
Click to collapse
keep on crossing your limits.. Keep flying my friend .....
Rht555 said:
keep on crossing your limits.. Keep flying my friend .....
Click to expand...
Click to collapse
Thanks a lot bro
Excellent work !!
Android Original development was the only place there was not activity in magnus dashboard, you have unleashed it with the bang. ! Hope it can be used on magnus stock rom in coming days. !! Cheers :cyclops::highfive:
Finally *wipes tears* an awesome work by an awesome dev ! thnkz for all the support.... :good::good::good: keep developing gr8 :highfive:
waiting for more
Was waiting for this thanks a lot
Sent from my Micromax A117 using XDA Premium 4 mobile app
rubenhardy said:
Android Original development was the only place there was not activity in magnus dashboard, you have unleashed it with the bang. ! Hope it can be used on magnus stock rom in coming days. !! Cheers :cyclops::highfive:
Click to expand...
Click to collapse
Hey Did You Checked In Stock ROM And XLD,SLD,PureXpriaZ2 Rom ???
Please make it available for stock rom
Xtreme Sandy kernel V 1.2 released
Now compatible with A117 stock ROM
Changelogs
Compatible with A117 stock ROM
Lulzactiveq and nighmare governors added ( Lulzactive gives great performance. Can be used for gaming )
Xtreme smoothness
DOWNLOADS :
Xtreme Sandy kernel V 1.2
Post feedback &give your suggestions in the thread if you are trying kernel so that others can benefit from it.
Thanks
Santhosh
Can this be used in other custom roms or only for stock?
Sent from my A117 using XDA Free mobile app
Link is not working plz fix
Sent from my Micromax A117 using XDA Premium 4 mobile app
Siddk007 said:
Can this be used in other custom roms or only for stock?
Sent from my A117 using XDA Free mobile app
Click to expand...
Click to collapse
Hope you have read Post #2
vikash118 said:
Link is not working plz fix
Sent from my Micromax A117 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It does work. Checked even now
Santhosh M said:
It does work. Checked even now
Click to expand...
Click to collapse
Link not working! Has been blocked by my ISP (Airtel)
Please give the direct link!
Cant download
Santhosh M said:
Xtreme Sandy kernel V 1.2 released
Now compatible with A117 stock ROM
Changelogs
Compatible with A117 stock ROM
Lulzactiveq and nighmare governors added ( Lulzactive gives great performance. Can be used for gaming )
Xtreme smoothness
DOWNLOADS :
Xtreme Sandy kernel V 1.2
Post feedback &give your suggestions in the thread if you are trying kernel so that others can benefit from it.
Thanks
Santhosh
Click to expand...
Click to collapse
Cant download..............
Santhosh M said:
Xtreme Sandy kernel V 1.2 released
Now compatible with A117 stock ROM
Changelogs
Compatible with A117 stock ROM
Lulzactiveq and nighmare governors added ( Lulzactive gives great performance. Can be used for gaming )
Xtreme smoothness
DOWNLOADS :
Xtreme Sandy kernel V 1.2
Post feedback &give your suggestions in the thread if you are trying kernel so that others can benefit from it.
Thanks
Santhosh
Click to expand...
Click to collapse
I'm glad you got it working on the STOCK ROM. But I do have a request? Can you please add features like Sweep2Wake and all? I know it eats battery, but options can be available. Just a request. Thanks. I appreciate your work, the kernel is really smooth.Can we?
Full Regards.
Geek-DROID said:
I'm glad you got it working on the STOCK ROM. But I do have a request? Can you please add features like Sweep2Wake and all? I know it eats battery, but options can be available. Just a request. Thanks. I appreciate your work, the kernel is really smooth.Can we?
Full Regards.
Click to expand...
Click to collapse
Thanks for the review. Ya s2w is possible. Need to edit touch panel driver codes and it comes to lot of lines. Personally no interest to work on it.
Hello M2 users, y'all probably wondering what did I mean by the thread title above so I'll get straight to the point nice and simple.
Using a stock kernel sucks, any CPU Tuner will go bonkers adjusting frequencies only to see it revert to stock again. So, while browsing for ways to optimise performance and battery in the Xperia, I came across this guide (now updated to this) on our Interactive governor. While it's on a different phone, the explanations are clear enough to tell anyone that yes, this can be adapted so long as you are rooted.
So read the whole post to give yourself an idea on the functions available for you. I use Kernel Adiutor for this as it seems most reliable.
But first, go into your build.prop files and edit this code:
Code:
ro.min_freq_0=300000
Set the frequency to 300000 (300Mhz) and restart or your phone will always be stuck on a higher frequency.
Also in the Kernel Samepage Merging, turn it off. There isn't much of an impact between battery and performance so this function is useless.
So now head into the CPU section, towards Tunables and add the following values according to the screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/img]
This gave me 50% battery usage over 26 hours, with 5 hours of Screen on Time used by chatting, gaming, and web surfing. Pretty good looking at all the times I've run the battery with less usage.
Anyhoo, I hope these settings are useful for y'all and if anyone has any modifications to these settings please do share it with your results. This may perhaps be the only guide where we control the governor on a deeper level rather than taking it as it is, so let's squeeze as much juice out of this phone as possible.
Update: These are the settings I've settled with, no negligible battery life and not much of an impact on performance. The voltage tables for the SD400 looks to be dynamic so you can't get an exact reading and anyone who looks at it will suggest you buy a new phone instead >.>
How do you add multiple values on one settings ?
I can't seem to be able to
FrWhyMe said:
How do you add multiple values on one settings ?
I can't seem to be able to
Click to expand...
Click to collapse
Right now you can only add multiples for above_hispeed_delay and target_load. Just tap the space bar each time you add in new values and the app will auto-arrange it for you. If it still doesn't work, what kernel are you using?
Can you repost the photo or write the values please?
basem_ym said:
Can you repost the photo or write the values please?
Click to expand...
Click to collapse
I'm not using this anymore, Sony's stock setting is fine unless you can somehow change the voltage.
AutumQueen92 said:
I'm not using this anymore, Sony's stock setting is fine unless you can somehow change the voltage.
Click to expand...
Click to collapse
I spent last week trying to study and understand those govenors.
Since yesterday, I was trying and tunning the stock interactive govenor
I didnt notice any major changes in performance but I was surprised by power consumption
Ex: I used to play Solitaire everyday more than 2 times a day, each time I spend like 1 hour and my battery drops like 10%
After tunning the interactive govenor my battery drops like 4-6%
Which means its much better than stock
I'm using EagleExperience rom which come with stock kernel
Anyway I just want to know your tunnables because the photo you posted is not opening
I want to compare them with my numbers
Thank you for this post and sorry for bad english
It's not my first lang.
basem_ym said:
I spent last week trying to study and understand those govenors.
Since yesterday, I was trying and tunning the stock interactive govenor
I didnt notice any major changes in performance but I was surprised by power consumption
Ex: I used to play Solitaire everyday more than 2 times a day, each time I spend like 1 hour and my battery drops like 10%
After tunning the interactive govenor my battery drops like 4-6%
Which means its much better than stock
I'm using EagleExperience rom which come with stock kernel
Anyway I just want to know your tunnables because the photo you posted is not opening
I want to compare them with my numbers
Thank you for this post and sorry for bad english
It's not my first lang.
Click to expand...
Click to collapse
These are my current settings, the 300Mhz and 787Mhz share the same voltage and any higher frequency has the same voltage too so it's more efficient to use Sony's settings. The only difference in here is I used Intelliplug to better control how they ramp up.
AutumQueen92 said:
These are my current settings, the 300Mhz and 787Mhz share the same voltage and any higher frequency has the same voltage too so it's more efficient to use Sony's settings. The only difference in here is I used Intelliplug to better control how they ramp up.
Click to expand...
Click to collapse
In target loads, you have frequencies that aren't supported on stock kernel (1.4GHz)
DavidMKD said:
In target loads, you have frequencies that aren't supported on stock kernel (1.4GHz)
Click to expand...
Click to collapse
That's because my kernel is overclocked.
above_hispeed_delay: 40000 998400:45000 1090400:50000 1190400:55000
boost: 0
boostpulse_duration: 0
go_hispeed_load: 99
hispeed_freq: 787200
io_is_busy_: 0
min_sample_time: 0
sampling_down_factor:1
sync_freq:300000
target loads: 80 600000:80 787200:90 998400:95 1090400:97 1190400:99
timer_rate: 60000
timer_slack: 480000
up_threshold_any_cpu_freq: 0
up_threshold_any_cpu_load: 0
Ksm off , no hotplug min:300 mhz max:1190 mhz
I am using this settings for now. I tried to lock 300-787 mhz for the my daily usage (whatsapp, youtube, cm browser, simple games like fun run) high frequences for heavy games, installing apps.
Is that config fine ? I tried semil's config its battery performance was great but i think it is slow config.
batuskas said:
above_hispeed_delay: 40000 998400:45000 1090400:50000 1190400:55000
boost: 0
boostpulse_duration: 0
go_hispeed_load: 99
hispeed_freq: 787200
io_is_busy_: 0
min_sample_time: 0
sampling_down_factor:1
sync_freq:300000
target loads: 80 600000:80 787200:90 998400:95 1090400:97 1190400:99
timer_rate: 60000
timer_slack: 480000
up_threshold_any_cpu_freq: 0
up_threshold_any_cpu_load: 0
Ksm off , no hotplug min:300 mhz max:1190 mhz
I am using this settings for now. I tried to lock 300-787 mhz for the my daily usage (whatsapp, youtube, cm browser, simple games like fun run) high frequences for heavy games, installing apps.
Is that config fine ? I tried semil's config its battery performance was great but i think it is slow config.
Click to expand...
Click to collapse
I try not to limit my frequencies since the point is to go high performance only when needed. I'm not sure about your config since I never turn off hotplugs.
Update
20180803:
Project WIPE is now OPEN SOURCE.
See: https://github.com/yc9559/cpufreq-interactive-opt/tree/master/project/20180603-2
20180628 (20180603.2):
misc: change input boost strategy, first value of targetloads 80->(3~60) for 2.5s, may reduce jitters while interacting
misc: change dynamic freq lock from 2.0G to 1.9G
template: new template architecture, easy to transplant, easy to read，but a bit abstract
template: check whether parameters have been applied before the script finish
template: add platform name
template: fix hmp parameters chmod error
template: fix ignore_hispeed_on_notif error
template: turn off msm_thermal/core_control
template: fix clusters stuck at the highest freq problem caused by perfd
Supported SOCs
Snapdragon 835, 820/821, 810/808, 801/800/805, 660, 636, 652/650, 625/626
Exynos 8895, 8890, 7420
Kirin 970, 960, 950/955
Helio X20/X25, X10
Atom z3560/z3580
Introduction
Compared to manually tuning interactive governor parameters, can we go further?
YES.
The interactive governor is very popular in Android phones. In the past, there have been projects that have achieved excellent life by tuning its parameters, such as AKT and Helix Engine. This is also true of this project. I used to benefit from @soniCron's tutorial posts, "Advanced Interactive Governor Tweaks". After repeated argumentation, I got a set of suitable parameters to share on the web. But soon I received such replies, "Why scrolling screen is laggy?", "Why the game isn't running smoothly?". After a long period of trying, I realized that you can not have it both ways. This should have a better solution. In order to avoid some misunderstanding of interactive, I try not to rely on understanding from the tutorial posts, in-depth source code to understand the role of each parameter in the process.
Tuning the interactive parameters by our feeling, there are the following problems:
difficulties to have clear feedback
hard to reach the balance of power consumption and performance
complex interactive parameters
This project aims to solve the problems above by creating automated programs as follows:
real world workload capture
interactive governor process simulation
cost function of lag and power comsuption
iteration to obtain local optimum using NSGA2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
S821 Kyro Gold powermodel
The workload sequence captured on Nexus 9
This idea is similar to EAS, which takes into account both performance and power consumption costs through power consumption models and workload sequence, but obviously, EAS has a much lower response time and replaces tuning with decision logic.
Compared to manual tuning parameters, Project WIPE generates parameters that can adapt to multiple styles of workload sequences and produce a suitable combination of parameters for almost all mainstream SOCs.
This project began in July 2017, reached the first version in November 2017, and ended after the completion on June 3, 2018. Previous tests and feedback for improvements were performed on the Coolapk platform and the results were excellent. Now I share this result in the XDA forum.
Profile contains...
This is an executable script file generated by Project WIPE, the Workload-based Interactive Parameter Explorer.
Performance configuration brings four modes:
Balanced: ~1 hour longer on-screen battery life with little performance compromise, recommended
Laggy: ~1.5+ hours longer on-screen battery life, may lag in some scenarios where the load fluctuates dramatically
Power-wasting: ~0.5 hour longer on-screen battery life, balanced profile with quicker response
Low latency: for soft real tasks, butter smooth in tense gamming for a long period
In addition, it also includes other parameter tuning, such as IO scheduler and HMP parameters, to unify the rest of the parameters for a more consistent experience.
Requirements
ROOTED
Deep sleep time exceeds 90% of standby time
No other modifications which may tweak kernel tunables automatically (e.g. Advanced Kernel Tweaks)
Do it by yourself
Download performance configuration corresponding to your phone SOC, and extract it
Move it to "/data", rename it as "powercfg", set the permission of this file to 0755
Use the commands below to apply temporary changes to your system, it will recover after reboot
After applying changes, use `sh /data/powercfg debug` to make sure that it works
Use it with utilities to switch mode according to Top-App, such as Tasker, Magisk, vtool
Switch mode:
Code:
# switch to Balanced
sh /data/powercfg balance
# switch to Laggy
sh /data/powercfg powersave
# switch to Power-wasting
sh /data/powercfg performance
# switch to Low latency
sh /data/powercfg fast
Download
https://github.com/yc9559/cpufreq-interactive-opt/blob/master/20180603-description.md
OR
See the "Downloads" TAB of this thread
Credit
@soniCron: Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
Distributed Evolutionary Algorithms in Python
Comrades who have helpful feedback on the Coolapk platform (in ascending order of time):
Code:
@Fdss45 @yy688go @Jouiz @lpc3123191239 @小方叔叔 @星辰紫光 @ℳ๓叶落情殇 @屁屁痒 @发热不卡算我输 @予北 @選擇遺忘 @想飞的小伙 @白而出清 @AshLight @微风阵阵 @半阳半心 @AhZHI @悲欢余生有人听 @YaomiHwang @花生味 @胡同口卖菜的 @gce8980 @vesakam @q1006237211 @Runds @lmentor @萝莉控の胜利 @iMeaCore @Dfift半島鐵盒 @wenjiahong @星空未来 @水瓶 @瓜瓜皮 @默认用户名8 @影灬无神 @橘猫520 @此用户名已存在 @ピロちゃん @Jaceﮥ @黑白颠倒的年华0 @九日不能贱 @fineable @哑剧 @zokkkk @永恒的丶齿轮 @L风云 @Immature_H @xujiyuan723 @Ace蒙奇 @ちぃ @木子茶i同学 @HEX_Stan @_暗香浮动月黄昏 @子喜 @ft1858336 @xxxxuanran @Scorpiring @猫见 @僞裝灬 @请叫我芦柑 @吃瓜子的小白 @HELISIGN @鹰雏 @贫家boy有何贵干 @Yoooooo @揪你鸡儿
[/SIZE]
XDA:DevDB Information
Project WIPE, Tool/Utility for all devices (see above for details)
Contributors
yc9559
Project: https://github.com/yc9559/cpufreq-interactive-opt/
Version Information
Status: Stable
Current Stable Version: 20180603.2
Stable Release Date: 2018-06-28
Created 2018-06-09
Last Updated 2018-06-09
Reserved
self pop
How to switch profiles by using kernel auditor?
And also to check if the profile is switched?
bagajohny said:
How to switch profiles by using kernel auditor?
And also to check if the profile is switched?
Click to expand...
Click to collapse
Use simulate init.d to execute the shell script.
Check whether the interactive parameters have changed.
well, self-pop again
what is the font used in images tell please
can support exynos 7870 ?
Did someone tried on kirin 970?
Sent from my HUAWEI BKL-L09 using XDA Labs
Want to try this but didn't fully understood the execution part
It seems work on my Mi4LTE, now on see how the performance about a weeks
pokepokepoke said:
what is the font used in images tell please
Click to expand...
Click to collapse
PingFang SC
luuphong559 said:
can support exynos 7870 ?
Click to expand...
Click to collapse
It actually can, but I won't support this soc due to the little market share of it.
Dbj.Dhaval said:
Want to try this but didn't fully understood the execution part
Click to expand...
Click to collapse
Go to this link: https://github.com/yc9559/cpufreq-interactive-opt/blob/master/20180603-description.md
Some pictures on this webpage will help you to understand it.
wkobaint said:
It seems work on my Mi4LTE, now on see how the performance about a weeks
Click to expand...
Click to collapse
I'm looking forward to your reply.
Can you update a version forn Snapdragon 430
Im eager to try. Cuz the Advanced Interactive Governor Tweak too complex for me.
toji12 said:
Can you update a version forn Snapdragon 430
Im eager to try. Cuz the Advanced Interactive Governor Tweak too complex for me.
Click to expand...
Click to collapse
Sorry, S430 is not supported.
yc9559 said:
I'm looking forward to your reply.
Click to expand...
Click to collapse
I've a little bit problem.
Why your script doesn't stick on one of my Mi4c?
I had some setup same as on my Mi4 but it can't stick.
wkobaint said:
I've a little bit problem.
Why your script doesn't stick on one of my Mi4c?
I had some setup same as on my Mi4 but it can't stick.
Click to expand...
Click to collapse
Do not execute the script for s801 on s810 device
yc9559 said:
Do not execute the script for s801 on s810 device
Click to expand...
Click to collapse
just executed the script (balance) for my sd810. debug shows it applied but whenever the script is executed it shows few errors like CPU4 permission denied
powercfg has 755 permission correct
"can't create /sys/devices/system/cpu/cpu4/online: permission denied
can't create /sys/devices/system/cpu/cpu5/online: permission denied
can't create /sys/devices/system/cpu/cpu6/online: permission denied"