Database Users

CPU Governors explained

Thanks to deedii for posting this in another forum:
http://forum.xda-developers.com/showpost.php?p=26884865&postcount=2
Android CPU governors explained
What is a governor?
A governor is a driver for the regulation of CPUFreq - CPU frequency. As the name suggests, we, the Governor of the decision, when at full capacity, the MaxFreq - will be achieved or how fast the minFreq - - maximum frequency is reached minimum frequency or center frequency. He decides when, how and how long the CPU and still responds battery saving is still soft and still works.
There are many types of governors. Some are for single-core processors and some designed for dual-core processors. In stock kernel, there are five governors and quasar kernel, there are a lot more.
1: OnDemand
2: OndemandX
3: Performance
4: Powersave
5: Conservative
6: Userspace
7: Min Max
8: Interactive
9: InteractiveX
10: Smartass
11: SmartassV2
12: Scary
13: Lagfree
14: Smoothass
15: Brazilianwax
16: SavagedZen
17: Lazy
18: Lionheart
19: LionheartX
20: Intellidemand
21: Hotplug
22: Wheatley
23: Lulzactive
24: AbyssPlug
25. BadAss
26. Ktoonservative
27. AssWax
28. Sleepy
29. Hyper
30. Zen
31. Dyninteractive
32. SmartassH3
33. Smartmax
34. Pegasusq
35. Nightmare
36. Darkness
1: OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.
OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.
This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.
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: Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
4: Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
5:Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.
The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.
6: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.
7: Min Max
well this governor makes use of only min & maximum frequency based on workload... no intermediate frequencies are used.
8: Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.
9: InteractiveX Governor:
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
10: Smartass
Is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
11: 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.
12: Scary
A new governor wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
13: 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.
14: 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
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: 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.
18: Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source.
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.
19: LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
20: 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.
21: Hotplug Governor:
The “hotplug” governor scales CPU frequency based on load, similar to “ondemand”. It scales up to the highest frequency when “up_threshold” is crossed and scales down one frequency at a time when “down_threshold” is crossed. Unlike those governors, target frequencies are determined by directly accessing the CPUfreq frequency table, instead of taking some percentage of maximum available frequency.
The key difference in the “hotplug” governor is that it will disable auxillary CPUs when the system is very idle, and enable them again once the system becomes busy. This is achieved by averaging load over multiple sampling periods; if CPUs were online or offlined based on a single sampling period then thrashing will occur.
Sysfs entries exist for “hotplug_in_sampling_periods” and for “hotplug_out_sampling_periods” which determine how many consecutive periods get averaged to determine if auxillery CPUs should be onlined or offlined. Defaults are 5 periods and 20 periods respectively. Otherwise the standard sysfs entries you might find for “ondemand” and “conservative” governors are there.
Obviously, this governor is only available on multi-core devices.
22: Wheatley
in short words this govenor is build on “ondemand” but increases the C4 state time of the CPU and doing so trying to save juice.
23: Basically interactive governor with added smartass bits and variable (as opposed to fixed amout) frequency scaling, based on currently occuring cpu loads. Has, like smartass, a sleep profile built-in. See link for details on exact scaling.
24: Abyssplug governor is a modified hotplug governor.
25. BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 918Mhz and therefore stay cool and will use less power. To trigger a frequency increase, the system must run a bit @ 918Mhz with high load, then the frequency is bumped to 1188Mhz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 1-2 seconds, depending on the load your system is experiencing)
Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1188Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
26, Ktonnservative
Ondemand scales to the highest frequency as soon as a load occurs. Conservative scales upward based on the frequency step variable which means for the most part will scale through every frequency to achieve the target load thresholds. What this practically means is ondemand is prone to wasting power on unneeded clock cycles. Ondemand also features something called a down differential, this variable determines how long the governor will remain at the given frequency before scaling down. Conservative does not have this, but instead relies on having a down threshold which insures that as soon as the load drops below a given variable it scales down as fast as the sampling rate allows. The result to this is a governor which attempts to keep the load level tolerable and save you battery! Now ! Ktoonservative Is that but in addition contains a hotpluging variable which determines when the second core comes online. The governor shuts the core off when it returns to the second lowest frequency thus giving us a handle on the second performance factor in our CPUs behavior. While by default conservative is a poor performer it can be made to perform comparably to even performance governor. Here are some settings to discuss and start with. They are slightly less battery friendly under a load but very very well performing.
27. AssWax
So far, all I have found about this Governor is that it belongs in the interactive family. I'll update this when I find more
28. Sleepy
The Sleepy (formerly known as Solo) is an attempt to strike a balance between performance and battery power to create. It is based on the getweakten Ondemand of Arighi and is optimized for the SGS2. It may include imoseyon's Ondemandx with some tweaks Down_sampling and other features that set by the user through the sysfs of "echo" call. Sleepy is the behavior of Ondemandx when he is in action, very similar.
29. Hyper
The Hyper (formerly known as kenobi) is an aggressive smart and smooth, optimized for SGS2 getweakt and, based on the Ondemand, which was getweakt of Arighi and was equipped with several features of Ondemandx suspend imoseyon. (Added by sysfs, the settings suspend_freq and suspend Imoseyon's code) is the behavior of the hyper Ondemand if he is in action, very similar. He also has the Arighi's fast_start deep_sleep and detection features. In addition, the maximum frequency is in suspend mode 500Mhz.
30. Zen
Well, the question that was asked above led me to an analysis of V(R ), deadline, and some others. I already knew, but realized "this is the main feature of V(R), but wait it has no benefit to us smartphone users." So I thought about adjusting the way V(R ) handled requests and how it dispatched them (I chose V(R ) because i'd rather not tinker with a scheduler thats official and widely supported). Then I was looking over it, and realized I might as well just write a new one I don't need any of this stuff. So I came up with something awfully similar to SIO, although its a bit simpler than SIO (closer to no-op) and works just slightly different.
- It's an FCFS (First come, first serve) based algorithm. It's not strictly FIFO. It does not do any sorting. It uses deadlines for fairness, and treats synchronous requests with priority over asynchronous ones. Other than that, pretty much the same as no-op. (Credit bbedward http://forum.xda-developers.com/showthread.php?p=33327389)
31. Dyninteractive
All I can find about this governor is that the DynInteractive seems to behave perfectly in terms of frequency ramping so far and keeps the system running mostly on low clock speeds, unless really needed (games, heavy browsing, etc).
32. SmartassH3
The SmartassH3 governor is designed for battery saving and not pushing the phones performance, since doing that drains battery and that's the one thing people keep asking for more of.
33. Smartmax
This is a new governor which is a mix between ondemand and smartass2 By default this is configured for battery save - so this is NOT a gamer governor! This is still WIP!
34. Pegasusq
Read This: Pegasusq Governor
35. Nightmare
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery.
In addition to the SoD is a prevention because it usually does not hotplug.
36. Darkness
It's based on nightmare but more simple and fast, basic configs but very complex structure. * Alucard updated nightmare gov and improved stability, so far what stable in tests
Credits goes to:
http://icrontic.com/discussion/95140/android-cpu-governors-and-you-setcpu-system-tuner-tegrak
http://forum.xda-developers.com/showthread.php?t=1369817
What is a scheduler?
In a multitasking operating system, there must be an instance, the processes that want to run, CPU time and allocates it "goes to sleep" after the allotted time (timeslice) again. This instance is called the scheduler, such as opening and closing applications. that is, how fast they are open and how long they are kept in RAM.
I / O scheduler can have many purposes like:
To minimize time searching on the hard disk
Set priorities for specific process requests
To regulate a particular portion of the bandwidth of the data carrier to each running process
To guarantee certain process requests within a certain time
Which scheduler are available?
CFQ
Deadline
VR
Simple
Noop
Anticipatory
BFQ
Sio
Row
Anticipatory:
Two important things here are indicative of that event:
- Looking on the flash drive is very slow from Equip
- Write operations while at any time are processed, however, be read operations preferred, ie, this scheduler returns the read operations a higher priority than the write operations.
Benefits:
- Requests of read accesses are never treated secondarily, that has equally good reading performance on flash drives like the noop
Disadvantages:
- Requests from process operations are not always available
- Reduced write performance on high-performance hard drives
CFQ:
The CFQ - Completely Fair Queuing - similar to the Dead Line maintains a scalable continuous Prozess-I/O-Warteschlange, ie the available I / O bandwidth tried fairly and evenly to all I / O requests to distribute. He created a statistics between blocks and processes. With these statistics it can "guess" when the next block is requested by what process, ie each process queue contains requests of synchronous processes, which in turn is dependent upon the priority of the original process. There is a V2 and the CFQ has some fixes, such as were the I / O request, hunger, and some small search backward integrated to improve the responsiveness.
Benefits:
- Has the goal of a balanced I / O performance to deliver
- The easiest way to set
- Excellent on multiprocessor systems
- Best performance of the database after the deadline
Disadvantages:
- Some reported user that the media scanning would take this very very long time and this by the very fair and even distribution of bandwidth on the I / O operations during the boot process is conditioned with the media scanning is not necessarily the highest should have priority
- Jitter (worst case delay) can sometimes be very high because the number of competing with each other process tasks
Deadline:
This scheduler has the goal of reducing I / O wait time of a process of inquiry. This is done using the block numbers of the data on the drive. This also blocks an outlying block numbers are processed, each request receives a maximum delivery time. This is in addition to the Governor BFQ very popular and in many well known kernels, such as the Nexus S Netarchy. He was indeed better than the BFQ, but compared to the VR he will be weaker.
Benefits:
- Is nearly a real-time scheduler.
- Characterized by reducing the waiting time of each process from - best scheduler for database access and queries.
- Bandwidth requirements of a process, eg what percentage does a CPU is easy to calculate.
- As the Governor-noop ideal for flash drives
Disadvantages:
- If the system is overloaded, can go a lost set of processes, and is not as easy to predict
SIO:
It aims to achieve with minimal effort at a low latency I / O requests. Not a priority to put in queue, instead simply merge the requests. This scheduler is a mix between the noop and deadline. With him there is no conversion or sorting of requests.
Benefits:
- It is simple and stable. - Minimized Starvations (starvation) for inquiries
Disadvantages:
- Slow random write speeds on flash drives as opposed to other schedulers. - Sequential read speeds on flash drives, not as good
Noop:
The noop scheduler is the simplest of them. He is best suited for storage devices that are not subject to mechanical movements, such as our flash drives in our SGSII's to use to access the data. The advantage is that flash drives do not require rearrangement of the I / O requests, unlike normal hard drives. ie the data that come first are written first. He's basically not a real scheduler, as it leaves the scheduling of the hardware.
Benefits:
- Adds all incoming I / O requests in a first-come-who-first-served queue and implements requests with the fewest number of CPU cycles, so also battery friendly
- Is suitable for flash drives because there is no search errors
- Good data throughput on db systems
Disadvantages:
- Reducing the number of CPU cycles corresponds to a simultaneous decline in performance einhergehendem
VR:
Unlike other scheduling software, synchronous and asynchronous requests are not handled separately, but it will impose a fair and balanced within this deadline requests, that the next request to be served is a function of distance from the last request. The VR is a very good scheduler with elements of the deadline scheduler. He will probably be the best for MTD Android devices. He is the one who can make the most of the benchmark points, but he is also an unstable schedulers, because his performance falter. Sometimes they fluctuate below the average, sometimes it fluctuates above the average, but if above, then he is the best.
Benefits:
- Is the best scheduler for benchmarks
Disadvantages:
- Performance variability can lead to different results
- Very often unstable or unzverlässig
Simple:
As the name suggests, it is more of a simple or simple scheduler. Especially suitable for EMMC devices. He is reliable, maybe not as good as the VR, when this time has a good day, but he is despite all this very performance-based and does his best. At the moment it is the default scheduler in quasar kernel.
Advantages: - not known
Cons: - not known
BFQ:
Instead requests divided into time segments as the CFQ has, on the BFQ budget. The flash drive will be granted an active process until it has exhausted its budget (number of sectors on the flash drive). The awards BFQ high budget does not read tasks.
Benefits:
- Has a very good USB data transfer rate.
- Be the best scheduler for playback of HD video recording and video streaming (due to less jitter than CFQ Scheduler, and others)
- Regarded as a very precise working Scheduler
- Delivers 30% more throughput than CFQ
Disadvantages:
- Not the best scheduler for benchmarks - higher budgets that were allocated to a process that can affect the interactivity and bring with it increased latency.
Row:
Q: What is the ROW I/O scheduler?
A: ROW stands for "READ Over WRITE"
The ROW IO scheduler was developed with the mobile devices needs in
mind. In mobile devices we favor user experience upon everything else,
thus we want to give READ IO requests as much priority as possible.
In mobile devices we won’t have AS much parallel threads as on desktops.
Usually it’s a single thread or at most 2 simultaneous working threads
for read & write. Favoring READ requests over WRITEs decreases the READ
latency greatly.
How can I change the governor and scheduler?
There are two ways to change the governor and schedulers, as well as the settings for the Governorn. Either manually, in which you use a file manager like Root Explorer and then knows how to / sys / devices / system and then change the files to his wishes, provided you what you're doing, or via a graphical interface or by phone as SetCPU Voltage Control. These are the most prominent apps when it comes to adjusting the governor and / or scheduler.
- SetCPU are, besides the possibility of the clock speed of the CPU, setting profiles in certain situations, only to change the way the governor. The scheduler can not change it.
- Voltage control can alter both the governor and the scheduler, but has no way to adjust behavior profiles. While you can set various overclocking, Governor and scheduler profiles manually, but nothing more. Nevertheless, I prefer the VC, since it is simple and gives me the opportunity to change the scheduler.
Credit goes to [url="http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html]Tinzdroid[/url]

Damn learn something new today. Bookmark this page....
that dude drives a A-Team van. yeah that's right, I'm working on it. Z.R.T.

hey hip kat which are you running?

SmartassV2.
Seemed like the best mix of performance vs. battery life from what I was reading.

link to Wheatley:
http://forum.xda-developers.com/showpost.php?p=21864389&postcount=75
link to lulzactive:
http://tegrak2x.blogspot.com/2011/11/lulzactive-governor-v2.html

good reading hipkat..... thanks for the info

Nice info, thx mate

This was really helpful, thanks!

Dude thank you for this writeup. Extremely helpful. OndemandX works great on Sense ROMs IMO

Thanks for the info .

I'm gonna sticky this as the info is great to have for users. The only thing I ask is that along with credits you attach a link to the original thread please.
xda moderator/recognized contributer

Thank you, Papa!!!
I'll go look for it and get the link in here asap
I'll update it, too, as I learn about the newer governors that come out, etc.

thanks for the info

Thanks, now how about schedulers noop or bfq

jasonwojo75 said:
Thanks, now how about schedulers noop or bfq
Click to expand...
Click to collapse
Good idea, plus there are newer governors coming out that I need to get added to the OP

Wow man, summed it up pretty damn good. I was curious as to what differences there were between all the governors out there.
Well written and in-depth, this helped my understanding of them a great deal, you are thanked.

Performance Governor
I thought too that running at "Performance" governor was a crazy idea, and I just tried setting it on my HD2 at around 1:10 PM today, little over an hour ago. I'm on NexusHD2-ICS-4.0.4-CM9-HWA V2.3 ( tytung_HWA_r3), BDW. I'm running gmail, Skype and other "push" apps on the background all the time, and WiFI is constant ON.
To my surprise, after looking at SystemPanel history, the battery has been flat for almost an hour! (See screenshot attachment)
So I guess the theory is correct, where the variable bitrate (up/down scaling) consumes more cpu and battery that just runing full speed while processes demand it, and then fast fall time to low power. So fast rise/fast fall seems to be best battery saver and performance.
More tests need to be done, but so far, I hadn't seen my battery consumption this good, with any other governor!
Cheers

I totally agree with that, that scaling up and down puts more of a load on the cpu. Think about a car motor. Idling, vs revving it over and over

Awesome thread! This helps a lot on which gov to use! +1

Nice thread. I personally like SavagedZen. 2nd choice is Wheatley.

HTC One Kernel AGK

Hi there,
i have made my own Kernel for AOSP based Romz and add some features, but i cant post it. (-10 threads)
AGK-Kernel Features:
CPU UC/OC von 162 mhz - 2106 mhz
CPU Volt Controll
GPU UC/OC von 128 mhz - 487 mhz
CPU Governor:
-smartmax
-interactive
-conservative
-ondemand
-userspace
-powersave
-Lionheart
-performance
-badass
-intellidemand
-intelliactive
-smartassV2
-lagfree
Scheduler:
-noop
-deadline
-row
-cfg
-fiops
-sio
Wake:
-sweep2wake
-flick2wake
-flick2sleep
-doubletap2wake
-home2wake
-pick2wake
-pocket detection
-logo2menu
-Zimage is XZ compressed
-Add some Bluetooth driver
-Add Generic Dynamic Voltage and Frequency Scaling (DVFS) support
and more...
if you are interestet, pm me! Kernel is stable
greets Anta

is it possible to place the download here?

Good！How about the battery life?

paully520 said:
Good！How about the battery life?
Click to expand...
Click to collapse
The maximum i have seen was 2 days, but try it by yourself to see how it works for you!

Download link
Please try and give a responce please!
https://mega.co.nz/#!xAZj3TTY!ank00V45CaZkIikTBkLIo2JTvg2X0IUYHiYfUo4UQ8k

I tried this out on both C-Rom 6.6 and Paranoid Android RC2. Both experience random reboots, I did what you said with TricksterMOD, but still experienced a reboot, on PA. On C Rom, the problem resolved itself after around 10 reboots, randomly. I'm currently on PA, and the problem occurs sporadically. Also, when I used the double tap to wake, the screen is black, and I have to reboot by long pressing the power button for like 14 seconds. I also have Xposed installed and I use XBlast.

Make sure you post a link to the proper kernel source code on Github

[GUIDE][ROOTED][FRIENDLY] Battery Guide - CM Based/Stock Based ROMs.

A replacement for SONY's STAMINA MODE. Also a SMARTER GUIDE.
YOU DON'T NEED TO BLOCK WAKELOCKS, USE BATTERY SAVERS, XPOSED, AMPLIFY, etc.
Recommended for:
CM Based ROMS/Custom kernel users/Wifi users.
For those who want high SoT.:angel:
I am not going ask you for a beer or a cup of coffee, only read this guide and thanks me later. [emoji14]
(Recommended) CLEAN FLASH only ROM first, then proceed.
This guide is divided into 2 parts
Moto G 2014 Index of Threads. Thanks @Mister Magister (Easy to search all roms for G 2014).
1. CM based roms.
2. Stock based roms.
KERNELS -
Halogen - Battery/ Balanced/ Performance.
Spirit - Performance.
Optimus - Balanced.
decipher_simple - More battery/Balanced.[I prefer this]
BLOATWARE REMOVAL.
CM Based: Use ES Explorer. Grant SU permission (Root Explorer). Migrate to root.
OR use the Debloat Script. Supports all devices.
In SYSTEM/APP, delete these folders:
Basic Dreams, Browser, CellBroadcastReceiver, CM File Manager, Dash Clock, Eleven, Email, Exchange2, Galaxy4, HoloSpiralWallpaper, LiveWallpapers, LiveWallpaperPicker, NoiseField, PhaseBeam, PhotoPhase, PhotoTable, VisualizationWallpapers, WAPPush/WhisperPush.
Reboot the phone immediately.
BLOATWARE REMOVAL ZIP ADDED: Flash it through TWRP immediatedly after clean flashing the ROM. It will also clear the dalvik.
Now flash Minimal/Pico GAPPS for first time and kernel. (I prefer DECIPHER KERNELL- His own-my.zip recommended)
This kernel is simple one without useless tweaks and hence recommended for more juice saving!
Also flash L SPEED MOD @Paget96. Really working like a charm!! High savings!
YOU CAN UNDERCLOCK WITH L MOD INSTALLED! IT'S TOTALLY LAG FREE!
Stock Based: Rooted
Delete LIVE WALLPAPERS the same way. You can use Juice Defender Ultimate (Don't grant it SU permission).
FOR STOCK, ONE HAS TO USE XPOSED FOR AMPLIFY AND POWERNAP. There are too many wakelocks.
Basic Settings(Common for both)
Settings:
1. Wifi > Advanced - Scanning always available - OFF, Keep wifi on during sleep - Never.
2. Mobile networks: 2G (Wifi users).
3. Display - Sleep - 30 seconds, Daydream - Off.
4. Sound&Notifications - Other sounds - All OFF (your choice).
5. Battery : Turn on bat. saver - NEVER.
6. Location - OFF.
7. Keyboard - Popup, Sound, Vibrate - OFF.
8. Lockscreen -Display Music Visualizer - OFF.
9. Developer Options - Window, Transition animation scale - 0x (or 0.2x) and Animation Duration Scale - 0.2x
These settings should be tuned according to your needs.
If you wish keep AMBIENT DISPLAY to OFF and DOUBLE TAP TO SLEEP on nav bar.
For RESURRECTION ROM or any other cm based rom -
Don't use BATTERY BAR, SLIM RECENTS/ OMNI SWITCH, SLIM PIE, CLEAR ALL BUTTON, SUPERUSER INDICATOR, RR LOGO.
Keep it clean. Default animations.
Now the interesting part, TWEAKS
Recommended Apps - Drive Link below.
1. Kernel Adiutor.
2. SetCPU.
3. Greenify.
4. SDMaid Pro.
Start with
SET CPU;
Install the app, open it, grant SU permission.
Go to PROFILES tab, add a new profile.
My PROFILES BACKUP given in DRIVE LINK. Place it in root of internal storage and restore from SET CPU. {Updated}
Use min freq of kernels flashed! Either 96MHz or 300Mhz.
1. Turn this profile on when - Screen Off.
CPU Governor: On Demand
Min: 96Mhz Max: 600MHz
Priority: 100, EXCLUSIVE
2. Add a new profile - Battery Saver.
Turn profile on when - Battery 5%
CPU Governor: zzmove
Min: 96MHz Max: 787MHz
Notificaton: Persistent, Battery.
Priority: 99, EXCLUSIVE.
3. Again a new profile
Turn profile on when - Any of these are true. ( in it, add your CAMERA apps)
CPU Governor: Interactive.
Min: 96MHz Max: 1190MHz
Priority: 97, EXCLUSIVE.
4. New one
Turn profile on when - Screen ON.
CPU Govenor: zzmove (2).
Min: 96MHz Max: 1190MHz
Priority: 96, NOT EXCLUSIVE.
Below this priority you can add per app profiles as per your wish.
GRANT SU permission to SET PROFILES (UID)
KERNEL ADIUTOR
Settings for HALOGEN KERNEL, DECIPHER_SIMPLE (Do this after setting up SET CPU)
Open app,
CPU -
Min: 96MHz Max: 1190MHz
CPU Governor: Don't change. It will be as per SET CPU.
Multicore Power Saving: Enabled (Not Aggressive).
CPU Boost -Interval (Both) to 40ms.
Input Boost Freq: 787MHz
CPU Hotplug
Intelliplug -OFF.
MSMHotplug -OFF.
Alucard Hotplug -ON.
You can use INTELLIPLUG Balanced/ Eco Conservative/ Strict(1 core) Halogen too.
GPU
Max: 320MHz (if you are not a gamer or else 450)
Governor: Simple_OnDemand. (Gaming - Performance or msm-adreno_tz)
Save this profile. Allow the phone to rest for 15 mins.
Change the governor to IMPULSE and save another profile for performance. Use widget for applying.
Note - CPU Governors in SET CPU and Kernel Adiutor should match. Don't change the CPU Governor from Kernel Adiutor. Do it from Set CPU Profiles. Also you need to apply the profile after reboot.
GREENIFY - Root Mode.
Add all apps except Set Cpu, Kernel adiutor.
.
Don't use Xposed. It runs everytime you start module app., after all you are using custom rom.
Google Backup off, and all tracking services of GOOGLE PLAY SERVICES should be off.[emoji14]
No wakelock blocks. Auto Sync OFF after syncing - This does more saving.
With above tricks, I have achieved 0% percent drain. ( At night too.), 6hrs SoT :fingers-crossed:
If your phone reboots on unlocking, it means you have something wrong. Then change Set CPU SCREEN OFF profile governor to zzmove.
Code:
[U]CPU Governor Tunables[/U]-
* currently available profiles by ZaneZam and Yank555:
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (1)'def' -> Default -> will set governor defaults -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (2)'ybat -> Yank Battery -> a very good battery/performance balanced setting -
* - DEV-NOTE: highly recommended! -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (3)'ybatext'-> Yank Battery Extreme -> like yank battery but focus on battery saving -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (4)'zzbat' -> ZaneZam Battery -> a more 'harsh' setting strictly focused on battery saving -
* - DEV-NOTE: might give some lags! -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (5)'zzbatp' -> ZaneZam Battery Plus -> NEW! reworked 'faster' battery setting -
* - DEV-NOTE: recommended too!:) -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (6)'zzopt' -> ZaneZam Optimized -> balanced setting with no focus in any direction -
* - DEV-NOTE: relict from back in the days, even though some people still like it! -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (7)'zzmod' -> ZaneZam Moderate -> NEW! setting based on 'zzopt' which has mainly (but not strictly only!) 2 cores online -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (8)'zzperf' -> ZaneZam Performance -> all you can get from zzmoove in terms of performance but still has the fast -
* - down scaling/hotplugging behaving -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (9)'zzinz' -> ZaneZam InZane -> NEW! based on performance with new insane scaling active. a new experience! -
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (10)'zzgame' -> ZaneZam Gaming -> NEW! based on performance with scaling block enabled to avoid cpu overheating during gameplay -
* ------------------------------------------------------------------------------------------------------------------------------------------
* profile_number 0 means that you can tune the tunables according to your own liking. ;)
Thanks to zakee94. :good:
SDMaid Pro
Check all boxes in Corpse finder settings, and scan and remove all corpse. ( LEFTOVER Dalvik of removed bloatware).
For Stock Based roms/ Stock rooted: Use STELLAR Kernel
zzmove is preconfigured in all kernels above.
If you face lag using zzmove post in here.
RECOMMENDED APPS:
These are best apps
MUSIC PLAYER - Phonograph.
CAMERA - Open Camera. (Better than CM Camera)
NOTE MAKING - Google KEEP.
FILE EXPLORER - ES Explorer.
INSTALLER- Easy Installer.
CLOCK- Timely.
CALENDAR - Sunrise.
Disable this apps: Clock, Google App, Google Calendar Sync, Google Partner Setup, Market Feedback Agent, OTA (if you wish), PICO tts, Print Spooler.
Force Stop this apps at night: Calendar , Calendar Storage, Google Contacts Sync, Google Play Store, Key Chain, Location Services, Themes Provider. (For 0% drain also switch to FLIGHT MODE at night)
Use PICO GAPPS.
No BETTER BATTERY STATS, WAKELOCK DETECTOR, AMPLIFY, and BATTERY SAVERS.
Power Cycle - Charge from 5% to 100% and 10 min more to 100. Give up using phone while charging.
Thanks to all Devs for their support to G 2014. @zakee94 @-decipher-
Next time if anyone says that G 2014 has got 2070mAh battery only. Just reply them that " Since Motorola is grandtechy company they have certain quotas to maintain device ergonomics, so there's odd numbered 2070mAh battery!"
Any SUGGESTIONS will be appreciated. Hit thanks.
Thanks @Azmat Roomi for suggestion of L Speed Mod.
Link to DRIVE.
For OTHERS PHONES you can use the profiling and settings, set cpu.
HIT THANKS and ANSWER THE POLL if YOU have LIKED the THREAD!
Latest screenshot - 8hrs SoT:highfive:
ROM: cm-12.1-20151102-NIGHTLY-titan.zip
KERNEL: Decipher's Drive - [151101]my.zip
No Battery Savers, Xposed, Wakelock Blocker, L Speed Mod etc.
Only GREENIFIED some GCM apps, not all apps. This works. You shouldn't FORCE STOP apps unless they aren't responding. Reloading them takes more battery and memory. Only force stop apps with GCM and the ones you don't use.
Drain was 0% - Since it was 3%, the CPU governor was POWERSAVE. It may be 2-3% at night.
Attached- New SET CPU profiles backup - In the Drive.
Code:
[B]Kernel Adiutor Settings[/B]:
[B]CPU[/B] :
Min - 300MHz.
Max - 1190MHz.
[B]CPU Hotplug[/B] :
MPDecision - Max Cores - 2.
[B]GPU[/B] :
Max - 200MHz.
Governor - simple_ondemand.
[B]Virtual Memory[/B] :
dirty ratio - 70 .
dirty background ratio - 9.
dirty expire centisecs - 350.
dirty writeback centisecs - 500.
min free kbytes - 2857.
over commit ratio - 50.
swapiness - 90.
vfs cache pressure - 130.
[B]TCP Congestion Algorithm[/B] : westwood.
I don't know about the settings. I tried certain combinations and got good results.
Default zzmove profile was 8 - zzperf.
All other settings were at default.
DISABLE PER-APP PROFILES in BATTERY SETTINGS. Recommended.
Minimize HEAVY APPS before screen goes off - If you face lag while unlocking the phone with set cpu profiles screen-off active.

Nice guide and awesome battery life. Thank's for sharing.

-decipher- said:
Nice guide and awesome battery life. Thank's for sharing.
Click to expand...
Click to collapse

Very Nice Guide.I normally use to get 3-4hrs SOT.But after following this guide i am now easily getting 5-6hrs SOT.Guys give it a try it works like charm.

Azmat Roomi said:
Very Nice Guide.I normally use to get 3-4hrs SOT.But after following this guide i am now easily getting 5-6hrs SOT.Guys give it a try it works like charm.
Click to expand...
Click to collapse
Thanks for the review.:highfive:

@Abhishek Bhagwat Alucard seems to keep only one core active the whole time. What do you think about using MSM Hotplug instead?
Also ZZMOVE is a little bit sluggish for me, do you recommend any other governor for screen on?

godoy.rafa said:
@Abhishek Bhagwat Alucard seems to keep only one core active the whole time. What do you think about using MSM Hotplug instead?
Click to expand...
Click to collapse
One core is economy.
Also it delivers smooth performance with zzmove if you have followed the guide as above.
You can try INTELLIPLUG with STRICT profile since it uses 1 core.

Abhishek Bhagwat said:
One core is enough. Smooth performance on zzmove profile 2.
MSM Hotplug in Halogen R7 plugs 4 cores . Could be a bug. So I use Alucard!
Click to expand...
Click to collapse
This is what happens in my device:
Hotplugs:
- Intelliplug plugs only 2 cores, not more os less than that, so I don't use it
- Alucard only plugs one core, and it makes apps like Facebook to become very slow
- MSM Hotplug plugs 1, 2, 3 or 4 cores depending on my usage, and it seems to be the best hotplug in my case
Governor
- ZZMOVE gives my device a very slow response, seems like I am using a much older device, and apps become slow as well
- INTERACTIVE might use more CPU, but makes the device very smooth, fast and responsive. I understand that it might use more battery

@godoy.rafa
The above GUIDE is to give smoothest performance while using ZZMOVE.
In my device -
- Intelliplug plugs
1 Core - Strict , 2 Cores - Eco Conservative/Eco Performance, 3 Cores - Tri, 4Cores - Balanced.
-MSM Hotplug
Variable plugs, mostly 2,3,4 cores.
-Alucard
1 Core.
Try IMPULSE instead of zzmove or interactive. But I won't guarantee BATTERY SAVINGS on it.

Two questions: how do I disable Google backup and Google Play Services' tracking stuff services?
Also, I plan to install Resurrection Remix. The animations which should be kept as default are the ones you change at developer settings?

One question, after clean install ~ we woudn't have the es file explorer without play store right?Then how is it possible to delete those things then flash gapps?

theserpent said:
One question, after clean install ~ we woudn't have the es file explorer without play store right?Then how is it possible to delete those things then flash gapps?
Click to expand...
Click to collapse
Take the backup of es file explorer apk to your sd card.After flashing cm based rom you will get cm file manager just install es file explorer through it and remove bloatware:good:

josfr4ncisco said:
Two questions: how do I disable Google backup and Google Play Services' tracking stuff services?
Also, I plan to install Resurrection Remix. The animations which should be kept as default are the ones you change at developer settings?
Click to expand...
Click to collapse
1. Pause all ACTIVITIES in Google Play Services App.
Ex. Web History, Youtube History, etc.
2. Settings/Backup and Restore - Untick Backup.
Note: This will delete all the backups except that of CONTACTS, KEEP, etc.
3. All animations should be default at DURATION SCALE of 0.2x.

theserpent said:
One question, after clean install ~ we woudn't have the es file explorer without play store right?Then how is it possible to delete those things then flash gapps?
Click to expand...
Click to collapse
Right answer by @azmat!

Awesome guide bro
Cheers

Thanks for the review!
Did it work for you? @Vatsal

Abhishek Bhagwat said:
Thanks for the review!
Did it work for you? @Vatsal
Click to expand...
Click to collapse
Yes bro it did quiet a lot

Why is this thread closed? It was a
Nice guide...

ishubhamsingh said:
Why is this thread closed? It was a
Nice guide...
Click to expand...
Click to collapse
No feedbacks [emoji28]

Abhishek Bhagwat said:
No feedbacks [emoji28]
Click to expand...
Click to collapse
Dont expect feedbacks on huge basis. But ppl do follow this guide.
Guys share ur feedback on regular basis in order to keep thread alive and people wil have solutions for problems in their battery life
Sent from my Moto G 2014 using XDA Free mobile app

Lightning kernel profile workshop(insane battery life)

hello i have created some profiles for my kernel to get the best out of our device there will 2 to 3 versions of profile of the same governor
bal-balanced profile which will have a mix of performance and battery life
bat-battery profile which will give good battery life with smooth ui but not for gaming
exbat-extreme battery profile which is tuned for maximum battery life with slight lags in ui good for light usage
INSTRUCTIONS TO APPLY THE PROFILES
use es,root or mix explorer
Paste the files in initd folder system/etc/initd tick all the permissions(rwx rwx rwx) then go to kamod initd section and execute the profile you want you will get a confirmation message that the profile has been applied please keep only one set of governor profiles in intit folder to avoid problems
SMARTMAX GOVERNOR QUAD PROFILES
based on @Stylo King
in these profiles all the cores will be online all the time except 1 in sleep if you have late wake up problem try increasing suspend max frequency in msm limiter and suspend_ideal_frequency in smartmax tunning you can also edit the file and make permanent changes so you dont have to change again and again
SUICORE-QUAD
by @iDorkKnight
SUI stands for Smartmax_eps, Umbrella_core and Interactive. Suicore-quad-v1 is a profile based on 3 governors behaving differently(in a very specific way) in order to preserve battery and maintain performance.
Lightning-impulse profiles
These profiles are based on advanced interactive tweaks thread by @soniCron for best frequency usage for each task like videos,scrolling and also ramps down to idle minimum frequency fast and the ui is smooth without using too much input boost
will add more asap so stay tuned

RESERVED

Let the games begin

You sir are a hero for all your work

Thankyou for your work ,I'm using the bat profile and the stats look pretty promising on NOS 7.1.1 latest
I'm running only the profile ,all background processes are running normally (No Doser )
Will try it out and let you know

Is there a chance for screenshots from KA of each profile? Thanks

plantator said:
Is there a chance for screenshots from KA of each profile? Thanks
Click to expand...
Click to collapse
You can see the values in the file as it can be edited easily cause its time consuming to upload so many ss thanks

Which ROM would you say will work smoothly with these profiles.
Sent from my A0001 using XDA-Developers Legacy app

jasi275 said:
Which ROM would you say will work smoothly with these profiles.
Click to expand...
Click to collapse
Any ROM

big thanks,

SUICORE-QUAD-v1 PROFILE
SUICORE-QUAD v1:
SUI stands for Smartmax_eps, Umbrella_core and Interactive. Suicore-quad-v1 is a profile based on 3 governors behaving differently(in a very specific way) in order to preserve battery and maintain performance.
Instructions:
1)Unzip the suicore-quad-v1 file(DO NOT FLASH).
2)Copy the unzipped suicore-quad-v1 to system/etc/initd.
2)Grant all the permissions (rwx rwx rwx) to the file.
3) Go to CPU section of Kernel Auditor Mod app > Enable the "Enable per core control" option.
4) Go to the initd section of the Kernel Auditor Mod app and execute the suicore-quad-v1 script. You will receive a confirmation message.
DOWNLOAD: Google Drive Link
Some screenshots are attached that show the battery stats obtained using suicore-quad-v1
PS: On stock, I cannot go beyond 4h30m. On suicore-quad, well, the screenshots speak for themselves.

iDorkKnight said:
SUICORE-QUAD v1:
SUI stands for Smartmax_eps, Umbrella_core and Interactive. Suicore-quad-v1 is a profile based on 3 governors behaving differently(in a very specific way) in order to preserve battery and maintain performance.
Click to expand...
Click to collapse
it works with alucard hotplug with all cores on am I right?

Glad @nikhil18 is keeping the development alive for OnePlus One. Just checked my mentions and couldn't resist to post my thoughts here. Good job guys, Keep those profiles coming.

plantator said:
it works with alucard hotplug with all cores on am I right?
Click to expand...
Click to collapse
Works with alucard but if you have sudden lags or delayed wakeups, I suggest you shift to MSM hotplug with min_cores as 4.

iDorkKnight said:
SUICORE-QUAD v1:
SUI stands for Smartmax_eps, Umbrella_core and Interactive. Suicore-quad-v1 is a profile based on 3 governors behaving differently(in a very specific way) in order to preserve battery and maintain performance.
Instructions:
1)Unzip the suicore-quad-v1 file(DO NOT FLASH).
2)Copy the unzipped suicore-quad-v1 to system/etc/initd.
2)Grant all the permissions (rwx rwx rwx) to the file.
3) Go to CPU section of Kernel Auditor Mod app > Enable the "Enable per core control" option.
4) Go to the initd section of the Kernel Auditor Mod app and execute the suicore-quad-v1 script. You will receive a confirmation message.
DOWNLOAD:Google Drive Link
Some screenshots are attached that show the battery stats obtained using suicore-quad-v1
PS: On stock, I cannot go beyond 4h30m. On suicore-quad, well, the screenshots speak for themselves.
Click to expand...
Click to collapse
What ROM are you using?

Thanhtho96 said:
What ROM are you using?
Click to expand...
Click to collapse
The screenshots were taken on Hyper Unicorns.

Lightning-impulse profiles
These profiles are based on advanced interactive tweaks thread by @soniCron for best frequency usage for each task like videos,scrolling and also ramps down to idle minimum frequency fast and the ui is smooth without using too much input boost

nikhil18 said:
Lightning-impulse profiles
These profiles are based on advanced interactive tweaks thread by @soniCron for best frequency usage for each task like videos,scrolling and also ramps down to idle minimum frequency fast and the ui is smooth without using too much input boost
Click to expand...
Click to collapse
Holy ****!! which rom is this and kernel version and what other tweaks, you have applied??

aqilsoomro said:
Holy ****!! which rom is this and kernel version and what other tweaks, you have applied??
Click to expand...
Click to collapse
That's idprophecy ROM latest version 38 lightning with no tweaks like greenify,naptime only undervolted heavily and turned of google services wakeup in privacy guard that sot was on impulse exbat profile

nikhil18 said:
That's idprophecy ROM latest version 38 lightning with no tweaks like greenify,naptime only undervolted heavily and turned of google services wakeup in privacy guard that sot was on impulse exbat profile
Click to expand...
Click to collapse
Is that undervolting part of profile? Or we have to manualy do it?

Basic Tuning for Hardrock kernel (Noob freindly Guide)

ok , I am writing this guide to help those users who are not able to configure kernel tweaks themselves...(Just summarized way).Depend upon preferences, users need to adjust settings.I am not going in details but just what everyone need to adjust for battery, performance or balanced profiles.
All these settings is for Hardrock kernels so dont ask for other kernel related settings.
First of all to adjust settings you need Kernel auditor or similar tools. You can download from playstore
Lets get started(I am taking into consideration Hardrock kernel governors, io schedulers , gpu settings etc):
** one more thing is even If I am sharing, the experience or thoughts might be different from person to person.so I am just providing some initial ideas for tweaks
1) For Battery related settings (sorted from best) :
select anyone of these cpu governors:
a) ZZmove (add from cpu tunables profile no 2)
b) smartmax EPS
c) ondemand
d) conservative/powersave
cpu clock frequency :
set cpu frequency min 480 mhz and max 2.4 ghz
set gpu governor to ondemand
I/o scheduler : Noop
2) For Extreme Battery realted settings :
a) ZZMOVE (Profile no 3)
b) smartmax eps
set cpu frequency min 480 mhz and max 2.2 ghz
set gpu governor to ondemand
I/o scheduler : zen
3) For balanced profile settings :
a) InteractiveX
b) Interactive pro
b) Intelliactive
c) Impulse
d) cultivation
min cpu frequency 480 and max 2.4 ghz
I/o scheduler : maple or zen
4) For performance settings:
a) InteractiveX
b) Performance
c) Hyper
d) blue active
set min freq 650 mhz and max 2.8 ghz
set I/O scheduler to Fiops or BFQ
5) For gaming settings :
a) InteractiveX
b) Performance
c) Ironactive
d) Intelliactive
e) on demand
set min freq 650 mhz and max 2.8 ghz
set Gpu min frequency 100 and max 999 mhz and select adreno gz or ondemand
set I/O scheduler to Deadline
6) For completely insane beast settings
a) Performance
b) InteractiveX
c) Intelliactive
d) nightmare
min frequency 1036 mhz and max 2.8 ghz
set gpu min 100 and max 999 mhz and select adreno-gz or ondemand
set I/O scheduler to Fiops
7) For Multitasking settings
a) Interactive
b) interactive_pro
min frequency 650 mhz and max 2.8 ghz
Open governor tunables and change the following(if You can't find those settings then leave it):
* boostpulse_duration = 80000
* go_hispeed_load = 95
* hispeed_freq = 499200
* input_boost_freq = 960000
* min_sample_time = 100000
** target_loads = 98 422400:15 729600:30 1190400:35 1344000:40 1497600:55 1574400:60 1651200:65 1728000:75 1958400:85 2035200:90 2265600:95 2496000:98
set I/O scheduler to CFQ OR BFQ
Remember I am not focussing on gpu since if its idle then it wont drain, it will only pump up once you are into game.so select either ondemand or msm adreno gz gpu governor for any kind of settings..
For I/o schedulers, I/O Read Ahead Buffer is dependent on the size of your flash storage (internal/external). Below is the recommended settings for the given size that will yield the best performance .
Less than 8GB - 128KB
8GB - 512KB
16GB - 1024KB
32GB or above - 2048KB
please set this as read ahead for internal or external storage depending on volume size..
and please do not touch other kernel settings , just leave them as it is..
** and try to read more from google.It will be big help instead of asking again and again

Something like this was much needed, keep tweaking this as and when any changes made to the kernel in future..

awesome........simply awesome........ thank you

Xiaomi4X said:
Something like this was much needed, keep tweaking this as and when any changes made to the kernel in future..
Click to expand...
Click to collapse
Yeah will be posting or updating this thread once I am having something new to offer

Friend I don't know what I did , but your profile zip V3 worked
Hard_Rock83 said:
ok , I am writing this guide to help those users who are not able to configure kernel tweaks themselves...(Just summarized way).Depend upon preferences, users need to adjust settings.I am not going in details but just what everyone need to adjust for battery, performance or balanced profiles.
All these settings is for Hardrock kernels so dont ask for other kernel related settings.
First of all to adjust settings you need Kernel auditor or similar tools. You can download from playstore
Lets get started(I am taking into consideration Hardrock kernel governors, io schedulers , gpu settings etc):
** one more thing is even If I am sharing, the experience or thoughts might be different from person to person.so I am just providing some initial ideas for tweaks
1) For Battery related settings (sorted from best) :
select anyone of these cpu governors:
a) ZZmove (add from cpu tunables profile no 2)
b) smartmax EPS
c) ondemand
d) conservative/powersave
cpu clock frequency :
set cpu frequency min 480 mhz and max 2.4 ghz
set gpu governor to ondemand
I/o scheduler : Noop
2) For Extreme Battery realted settings :
a) ZZMOVE (Profile no 3)
b) smartmax eps
set cpu frequency min 480 mhz and max 2.2 ghz
set gpu governor to ondemand
I/o scheduler : zen
3) For balanced profile settings :
a) InteractiveX
b) Interactive pro
b) Intelliactive
c) Impulse
d) cultivation
min cpu frequency 480 and max 2.4 ghz
I/o scheduler : maple or zen
4) For performance settings:
a) InteractiveX
b) Performance
c) Hyper
d) blue active
set min freq 650 mhz and max 2.8 ghz
set I/O scheduler to Fiops or BFQ
5) For gaming settings :
a) InteractiveX
b) Performance
c) Ironactive
d) Intelliactive
e) on demand
set min freq 650 mhz and max 2.8 ghz
set Gpu min frequency 100 and max 999 mhz and select adreno gz or ondemand
set I/O scheduler to Deadline
6) For completely insane beast settings
a) Performance
b) InteractiveX
c) Intelliactive
d) nightmare
min frequency 1036 mhz and max 2.8 ghz
set gpu min 100 and max 999 mhz and select adreno-gz or ondemand
set I/O scheduler to Fiops
Remember I am not focussing on gpu since if its idle then it wont drain, it will only pump up once you are into game.so select either ondemand or msm adreno gz gpu governor for any kind of settings..
For I/o schedulers, I/O Read Ahead Buffer is dependent on the size of your flash storage (internal/external). Below is the recommended settings for the given size that will yield the best performance .
Less than 8GB - 128KB
8GB - 512KB
16GB - 1024KB
32GB or above - 2048KB
please set this as read ahead for internal or external storage depending on volume size..
and please do not touch other kernel settings , just leave them as it is..
** and try to read more from google.It will be big help instead of asking again and again
Click to expand...
Click to collapse
I was messing with my device , and I backed up my device with twrp recovery , and then installed China miui developer ROM just to see the difference in China and global ROM, when I returned to global ROM , by restoring the backup I made , I booted my device and just uninstalled the kernel adiutor ,
Then I tried to follow this guide and tried creating profile in kernel adiutor, when one profile I created is shown in the list.. I thought let's try flashing the zip of profiles by @Hard_Rock83
And falshed the V3 profile zip, and it worked all profiles are in the list removing mine..that I created

beingtejas said:
I was messing with my device , and I backed up my device with twrp recovery , and then installed China miui developer ROM just to see the difference in China and global ROM, when I returned to global ROM , by restoring the backup I made , I booted my device and just uninstalled the kernel adiutor ,
Then I tried to follow this guide and tried creating profile in kernel adiutor, when one profile I created is shown in the list.. I thought let's try flashing the zip of profiles by @Hard_Rock83
And falshed the V3 profile zip, and it worked all profiles are in the list removing mine..that I created
Click to expand...
Click to collapse
I just want to say lol:laugh:
I never trust miui..it behaves strange or weird always..

What is the difference of this one from the V3 profile?

fgaurano said:
What is the difference of this one from the V3 profile?
Click to expand...
Click to collapse
lol I am just guiding here, whoever having issues flashing profiles.. its all same...

Where can i find profile file?
As i using free version of kernel audiutor i need twrp flashable zip file.
Can anyone help me?

MiladHashMan said:
Where can i find profile file?
As i using free version of kernel audiutor i need twrp flashable zip file.
Can anyone help me?
Click to expand...
Click to collapse
Lol you need to open your eyes and find the profile v3 thread.. https://forum.xda-developers.com/mi-max-2/development/kernel-profiles-hardrock-kernel-v1-t3804630

Hi, thanks for your work, is there any guide on how to prevent aggressively killing of this kernel? After apllied this kernel on MIUI 10 v8.8.23, apps that's supposed to be running all the time like whatsapp, gsam, etc keep getting killed aggressively.

Nice..thanks for the info

Thanks Hard_Rock83.
Anybody knows how to port this over to Xiaomi Note 4/4x which has Snapdragon 625 as well?

Updated THread for multitasking..PLease check OP.

I've only just discovered this thread, thanks for putting all the information together!

Nice tips
Sent from my MI MAX 2 using Tapatalk