Related
Hi
I'm looking for kernel with "smartass" scaling to my LG GT540 Swift/Optimus. I've already kernel 0.3.1 by Quarx, but there are only performance, powersave and ondemand scaling profiles available in SetCPU. I want to save my battery as much as possible with good level of performance and I think that "smartass" scaling is exactly what I want
Anyone can help?
Many of us don't know what is CPU Governor's and which suites them perfectly, so after doing some Googling i am writing these.
What is a CPU governor?
A CPU governor in Android controls how the CPU raises and lowers its frequency in response to the demands the user is placing on their device. Governors are especially important in smartphones and tablets because they have a large impact on the apparent fluidity of the interface and the battery life of the device over a charge.
NOTE: You cannot change your CPU governor unless your phone is rooted and you have a ROM or app that lets you make a change. Also, different kernels (the intermediary software between your phone's hardware and the operating system) offer different sets of governors.
S/W or App's for using these features:
1. SetCPU.
2. No-frills CPU.
3. Tegrak Overclock.
1. Smartass: Performance is on par with the “old” minmax and smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 it will cap it to your min frequency).
2. 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 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.
3. SavagedZen: Another smartassV2 based governor. Achieves good balance between performance & battery.
4. Ondemand: which would instantly go to max frequency once it detects cpu activity and then scales down as the requirement decreases.
5. Performance: It has the same min and max frequency so I guess your phone will heat up and throttle really quick, although if you want to benchmark this would give you the best result.
6. Interactive: 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.
7. InteractiveX: 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.
8. Pegasusq: 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.
9. Abyssplug: from what I have read is a modified hotplug which is simillar to ondemand but has the ability to turn off a core when it is not needed and is a little more precise in scaling down cpu performance.
10. 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.
11. Powersave: This is opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
12. Lagfree: This 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.
Now you decide it on your own which will suite you ....
Hope this helped you .......
Source
Thanks mj for the wonderful explanation... Learnt some stuff..
Sent from my GT-I9103
Well done. Great work.
This is good work.:good:
I found this thread and this. It explains many more governers.....if any one is interested!:good:
If anyone is interested to know about I/O schedulers...a term that is very commonly used along with CPU governors, refer this
Could you also explain on how to use it ??
I m completely noob...are these governors bundled with kernel or thru some app ??
Sent from my GT-I9103 using Tapatalk 2
vipul12389mehta said:
Could you also explain on how to use it ??
I m completely noob...are these governors bundled with kernel or thru some app ??
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
NOTE:
You cannot change your CPU governor unless your phone is rooted and you have a ROM or app that lets you make a change. Also, different kernels (the intermediary software between your phone's hardware and the operating system) offer different sets of governors.
Quoted from here
Good job. Can you please add a source of this information?
Thank You OP ! Im now using abyssplug and it saves my battery so much !! Also with a good performance while gaming too !!
Sent from my GT-I9103 using xda app-developers app
what does save most battery for our galaxy r ?
Sent from my GT-I9103 using xda premium
vipul12389mehta said:
Could you also explain on how to use it ??
I m completely noob...are these governors bundled with kernel or thru some app ??
Click to expand...
Click to collapse
These Governor's are related to Kernel, when Kernel is developed these will be coded into kernel and we can select them by using App's like "Set CPU" or "No frill CPU".
"No frill CPU" is free and similar to set CPU...
Eg: In Horsepower kernel developed by fuss132 for Galaxy R we are having most of these Governor's...
m.kochan10 said:
Good job. Can you please add a source of this information?
Click to expand...
Click to collapse
Source added to OP...
Birki96 said:
what does save most battery for our galaxy r ?
Click to expand...
Click to collapse
As rhodrhi said you can try abyssplug or Powersave ( I forgor about this i will add it to OP) and Under clock the CPU will save some power....
Eg: When screen is off i will set it to max 780 and min 256 ( Presently i don't have mobile with me so i don't remember exactly the frequency's)....
Can some one tell me how the lagfree governer works on sgr? I am actually getting good smooth response on this governer and also it does not eat too much of battery...
How about others?
Sent from my GT-I9103
bhargav143 said:
Can some one tell me how the lagfree governer works on sgr? I am actually getting good smooth response on this governer and also it does not eat too much of battery...
How about others?
Click to expand...
Click to collapse
Lagfree: This 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.
I will add this to OP.
mj.vikram said:
7. InteractiveX: 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.
Source
Click to expand...
Click to collapse
How does DEEP SLEEP mode play into all of this?
Does this governor prevent DEEP SLEEP when the phone screen is off since it locks it at the lowest speed?
Neo3D said:
How does DEEP SLEEP mode play into all of this?
Does this governor prevent DEEP SLEEP when the phone screen is off since it locks it at the lowest speed?
Click to expand...
Click to collapse
+1
Sent from my GT-I9103 using xda premium
Neo3D said:
How does DEEP SLEEP mode play into all of this?
Does this governor prevent DEEP SLEEP when the phone screen is off since it locks it at the lowest speed?
Click to expand...
Click to collapse
drarunmmc said:
+1
Click to expand...
Click to collapse
Deep sleep is basically your phone going into a low CPU state and it's most likely enabled in all the kernel's by default irrespective of all Governor's ....
Install the app CPU Spy which will let you know the Time spent in each CPU frequency including deep sleep also....
Thnx
Great explaination :good:
Well done. Great work.
Thanks
..very informative! thank you very much for this info, it helps me a lot :good:
mj.vikram said:
Many of us don't know what is CPU Governor's and which suites them perfectly, so after doing some Googling i am writing these.
What is a CPU governor?
A CPU governor in Android controls how the CPU raises and lowers its frequency in response to the demands the user is placing on their device. Governors are especially important in smartphones and tablets because they have a large impact on the apparent fluidity of the interface and the battery life of the device over a charge.
NOTE: You cannot change your CPU governor unless your phone is rooted and you have a ROM or app that lets you make a change. Also, different kernels (the intermediary software between your phone's hardware and the operating system) offer different sets of governors.
S/W or App's for using these features:
1. SetCPU.
2. No-frills CPU.
3. Tegrak Overclock.
1. Smartass: Performance is on par with the “old” minmax and smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 it will cap it to your min frequency).
2. 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 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.
3. SavagedZen: Another smartassV2 based governor. Achieves good balance between performance & battery.
4. Ondemand: which would instantly go to max frequency once it detects cpu activity and then scales down as the requirement decreases.
5. Performance: It has the same min and max frequency so I guess your phone will heat up and throttle really quick, although if you want to benchmark this would give you the best result.
6. Interactive: 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.
7. InteractiveX: 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.
8. Pegasusq: 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.
9. Abyssplug: from what I have read is a modified hotplug which is simillar to ondemand but has the ability to turn off a core when it is not needed and is a little more precise in scaling down cpu performance.
10. 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.
11. Powersave: This is opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
12. Lagfree: This 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.
Now you decide it on your own which will suite you ....
Hope this helped you .......
Source
Click to expand...
Click to collapse
Thanks man this helps me understand a little ore of configuring a nandroid. :highfive:
"No-Frills CPU control/Pimp my Rom" for different speed governors and I/O schedulers
The custom Kernel for A110 is coming. But till then, you can try out some different clock settings to get you more speed when on games and experiment with speed governors and I/O schedulers with the stock kernel.
Install No-frills CPU control or use Pimp my ROM to change the Min clock(limited to 250 MHz) or Max clock (limited to 1.001 Ghz now) and 5 governors (ondemand, userspace, powersave, hybrid, performance). For optimal battery and speed use ondemand with 1Ghz/250Mhz and noop scheduler. For games, try performance governor. Those who want maximum battery life can try powersave governor....
pradipsoman said:
The custom Kernel for A110 is coming. But till then, you can try out some different clock settings to get you more speed when on games and experiment with speed governors and I/O schedulers with the stock kernel.
Install No-frills CPU control or use Pimp my ROM to change the Min clock(limited to 250 MHz) or Max clock (limited to 1.001 Ghz now) and 5 governors (ondemand, userspace, powersave, hybrid, performance). For optimal battery and speed use ondemand with 1Ghz/250Mhz and noop scheduler. For games, try performance governor. Those who want maximum battery life can try powersave governor....
Click to expand...
Click to collapse
lol..its useless on stock kernel.bdw each and every kernel can be underclocked.
Dj_cool said:
lol..its useless on stock kernel.bdw each and every kernel can be underclocked.
Click to expand...
Click to collapse
I think you have not read the post correctly. See the heading...Its not for changing clock speeds...Its for changing governors and I/O schedulers and there is no way you can do that on stock ROM without an external application as there is no settings for that in the stock ROM. And I am not taking anything about overclocking dude And many of the end users are beginners who do not even know these things...
I have clearly mentioned that the highest freq is capped. And it is not useless. We can play with the governors and the I/O schedulers. Read before you comment pal
but all are useless in stock kernel.ask varun if u have any doubt.
Dj_cool said:
but all are useless in stock kernel.ask varun if u have any doubt.
Click to expand...
Click to collapse
You are totally wrong dude..Get your info right. I have been playing with android right from 2010 and have used a multitude of phones Am not a beginner...I do not have to ask Varun on this...Default kernels come with limited speed governors and I/O schedulers that I have listed above, and THEY DO WORK...When you modify the kernel using sources, you can add many more governors and schedulers and also add other functionalities like over-clocking. Think before you post pal
http://forum.xda-developers.com/showthread.php?t=1369817
Read this dude....
And for your knowledge. The default governor and scheduler that our A110 comes set with is hybrid/cfq. That gives the maximum quandrant score of 3000 and above. Try to change it and you will see the difference in performance. The quadrant scores will go down. The settings DO WORK and to get better battery you can compromise on the performance.
Cheers....
m also not new in android..i also used too many android phones.
pradipsoman said:
You are totally wrong dude..Get your info right. I have been playing with android right from 2010 and have used a multitude of phones Am not a beginner...I do not have to ask Varun on this...Default kernels come with limited speed governors and I/O schedulers that I have listed above, and THEY DO WORK...When you modify the kernel using sources, you can add many more governors and schedulers and also add other functionalities like over-clocking. Think before you post pal
http://forum.xda-developers.com/showthread.php?t=1369817
Read this dude....
And for your knowledge. The default governor and scheduler that our A110 comes set with is hybrid/cfq. That gives the maximum quandrant score of 3000 and above. Try to change it and you will see the difference in performance. The quadrant scores will go down. The settings DO WORK and to get better battery you can compromise on the performance.
Cheers....
Click to expand...
Click to collapse
You mallu?
same here, expand what you are trying to say?
o/c not possible in stock kernel, but yes we can set clock values depending on the stock clock values between 0 - 1ghz (min 250mhz / maxx 1ghz), and even set governers, we need root for doing such actions na? but not possible without root!!!
deadlyindian said:
You mallu?
same here, expand what you are trying to say?
o/c not possible in stock kernel, but yes we can set clock values depending on the stock clock values between 0 - 1ghz (min 250mhz / maxx 1ghz), and even set governers, we need root for doing such actions na? but not possible without root!!!
Click to expand...
Click to collapse
Yes, you need to be rooted
pradipsoman said:
Yes, you need to be rooted
Click to expand...
Click to collapse
so can you give me a clean explanation of everything u said on the 1st post?
Yup..plz explain dude.:angel:
in the stock rom/kernel , what settings in "no frills cpu control" is the best for performance and battery respectively ?
the options seen are governors ( userspace , ondemand,hybrid, powersave , performance ) and I/O scedulers (cfq , deadline, noop) ..
will changing these options be effective in the stock 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"
}
I'm not going to make a colorful thread on this. Just going to run down the basics......
To start off, I do NOT own a Note 5. I have a S6. I built this kernel for @tdunham just to see
if I could without having the device. And it was a success. It has been tested by @tdunham
personally, so I know its good to go.......
There are not alot of features. But it is very stable like stock. In the future when I have time
I will add more features and tweaks. Alot of that depends on YOU.....I built a kernel for a
device I dont have, so some appreciation will go a long ways. A simple Thank you is free,
and goes a long ways with me.......
*FEATURES*
Built with Sprint BPL1 Sources
Compiled with UBERTC 5.3 Toolchain (optimized)
Linux 3.10.101
Set to Permissive
Deep Sleep Fix
Compiled with Graphite Optimizations
21 CPU Governors
11 I/O Schedulers
Optimized I/O Read Speeds
13 TCP Congestion Algrorithms
and more......
Flashing this is pretty simple. Download the zip, go into recovery and flash. There
is no need to wipe. Modules are now built into the kernel. So all that you are flashing is a
boot.img. If for some reason when you flash and it goes back into recovery, let me
know and I will provide a different zip (has different updater-script).
Like I stated above......All I ask is some participation in my thread. A dead thread
gets no attention from me at all. I have 2 kernels and a rom to worry about besides this
thread. Other than that........Enjoy.
Note-5-Kernel-V1
Note-5-Kernel-V2
Note-5-Kernel-V3
Twisted-Note
Code:
May 15
Initial Release
May 16
Fixed reboot issue
June 4
Compiled with UBERTC 6.0 Toolchain
Added 21 CPU Governors
Added 11 I/O Schedulers
Added 13 TCP Congestion Algrorithms
Optimized Read Speeds
June 7
Fixed reboot issue by compiling w/ UBERTC 5.3
August 19
Updated to latest source BPG1
UberTC 5.3
Feb 12
Updated to latest BPL1 source
Added ROW scheduler
All features from previous builds added
*Issues*
See post #13 for the WiFi fix for remembering your password
XDA:DevDB Information
Stock Sprint Kernel, Kernel for the Sprint Samsung Galaxy Note5
Contributors
The Sickness
Source Code: https://github.com/The-Sickness/Note-5---BPL1
Kernel Special Features:
Version Information
Status: Testing
Stable Release Date: 2016-05-14
Beta Release Date: 2016-05-14
Created 2016-05-15
Last Updated 2016-05-14
UPDATED [KERNEL] *Stock 6.0.1 V2* [Permissive] UBERTC 5.3 [GRAPHITE] BPC3 6/04/2016
Moderator Edit - Second post for additional information
Here is a list of governors (not all are in my kernel) and what they do......
CPU Governors
OnDemand
OnDemandX
Performance
Powersave
Conservative
Userspace
Min Max
Interactive
InteractiveX
Smartass
SmartassV2
Scary
Lagfree
Smoothass
Brazilianwax
SavageZen
Lazy
Lionheart
LionheartX
Intellidemand
Hotplug
Badass
Wheatley
Lulzactive
PegasusQ\PegasusD
HotplugX
Abyssplug
MSM DCVS
Intelliactive
Adaptive
Nightmare
ZZmove
Sleepy
Hyper
SmartassH3
SLP
NeoX
ZZmanX
OndemandPlus
DynInteractive
Smartmax
Ktoonservative\KtoonservativeQ
Performance may cry (PMC)
Dance Dance
AbyssPlugv2
IntelliMM
InteractivePro
Slim
Ondemand EPS
Smartmax EPS
Uberdemand
Yankactive
Impulse
Bacon
Optimax
Preservative
Touchdemand
ElementalX
Bioshock
Bluactive
Umbrella_core
ConservativeX
Hyrdxq
DevilQ
Yankasusq
Darkness
Alucard
Descriptions:
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 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.
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. 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. 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.
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 performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."
22. BadAss Goveronor:
Badass removes all of this "fast peaking" to the max frequency. To trigger a frequency increase, the system must run a bit with high load, then the frequency is bumped. 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.
23. Wheatley:
Building on the classic 'ondemand' governor is implemented Wheatley governor. The governor has two additional parameters. Wheatley works as planned and does not hinder the proper C4 usage for task where the C4 can be used properly. So the results show that Wheatley works as intended and ensures that the C4 state is used whenever the task allows a proper efficient usage of the C4 state. For more demanding tasks which cause a large number of wakeups and prevent the efficient usage of the C4 state, the governor resorts to the next best power saving mechanism and scales down the frequency. So with the new highly-flexible Wheatley governor one can have the best of both worlds.
Wheatley is a more performance orientated governor as it scales more aggressively than ondemand and sticks with higher frequencies.
24. Lulzactive:
It's based on Interactive & Smartass governors.
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.
25. Pegasusq/Pegasusd The Pegasus-q / d is a multi-core based on the Ondemand governor and governor with integrated hot-plugging. It is quite stable and has the same battery life as ondemand. However, it is less stable than HYPER on some devices like the S2 (before the PegasusQ governor was updated). 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 will run 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.
26. Hotplugx It's a modified version of Hotplug and optimized for the suspension in off-screen
27. AbyssPlug It's a Governor derived from hotplug, it works the same way, but with the changes in savings for a better battery.
28. MSM DCVS A very efficient and wide range of Dynamic Clock and Voltage Scaling (DCVS) which addresses usage models from active standby to mid and high level processing requirements. It makes the phone's CPU smoothly scale from low power, from low leakage mode to blazingly fast performance.Only to be used by Qualcomm CPUs.
MSM is the prefix for the SOC (MSM8960) and DCVS is Dynamic Clock and Voltage Scaling. Makes sense, MSM-DCVS
29. IntelliActive Based off Google's Interactive governor with the following enhancements:
1. self-boost capability from input drivers (no need for PowerHAL assist) 2. two phase scheduling (idle/busy phases to prevent from jumping directly to max freq 3. Checks for offline cpus and short circuits some unnecessary checks to improve code execution paths. Therefore, it avoids CPU hotplugging.
This is a more performance oriented CPU governor but isn't that much different from interactive (in terms of code).
30. Adaptive This driver adds a dynamic cpufreq policy governor designed for latency-sensitive workloads and also for demanding performance. This governor attempts to reduce the latency of clock so that the system is more responsive to interactive workloads in lowest steady-state but to reduce power consumption in middle operation level, level up will be done in step by step to prohibit system from going to max operation level.
31. 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.
32. ZZmove
The ZZmove Governor by ZaneZam is optimized for low power consumption when the screen off, with particular attention to the limitation of consumption applications in the background with the screen off, such as listening to music. ZZmoove is not a good gaming governor as it aims to save battery. This governor is still a WIP as the developer is constantly giving updates! Here are the available profiles:
33. 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 Ondemand. It includes some tweaks like the Down_sampling variable and other features that set by the user through the sysfs of "echo" call. Sleepy is quite similar to Ondemandx.
34. Hyper
The Hyper (formerly known as kenobi) is an aggressive smart and smooth governor based on the Ondemand and is equipped with several features of Ondemandx suspend profiles. It also has the fast_start deep_sleep variable and detection features. In addition, the maximum frequency is in suspend mode 500Mhz. This is a more smoothness oriented governor which means that it is good for performance, without sacrificing much battery life.
35. 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. Based on SmartassV2.
36. SLP
It is a mix of pegasusq and ondemand. Therefore, it has a balance between battery savings and performance.
37. NeoX
An optimized version of the pegasusq governor but with some extra tweaks for better performance. This means more battery drainage than the original PegasusQ.
38. ZZmanx
ZZmanx is exactly the same as ZZmove, but it has been renamed because DorimanX made it into his own version (possibly better performance) . However, it still suffers from below average gaming performance. (Refer to ZZmoove description for guide on profiles)
39. OnDemandPlus Ondemandplus is an ondemand and interactive-based governor that has additional power-saving capabilities while maintaining very snappy performance. While the interactive governor provides a modern and sleek framework, the scaling logic has been been re-written completely. Reports have found that users find ondemandplus as a more battery friendly governor. In ondemandplus, the downscaling behavior from ondemand is only very slightly modified. However, the upscaling has been modified to not scale up to maximum frequency immediately.
40. DynInteractive A dynamic interactive Governor. This Governor dynamically adapts it's own CPU frequencies within your parameters based off the system(s) load.
41. Smartmax
This is a new governor which is a mix between ondemand and smartassv2. By default this is configured for battery saving,so this is NOT a gamer governor! This is still WIP!
42. Ktoonservative\KtoonservativeQ
A combination of ondemand and conservative. Ktoonservative contains a hotplugging 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.
43. Performance may cry (PMC)
A governor based on Smartmax except it's heavily tweaked for better and maximum battery life. This is not a gaming governor!
44. Dance Dance
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 is a performance focused governor but also blends with some battery savings.
45. AbyssPlugv2
AbyssPlugv2 is a rewrite of the original CPU governor. It also fixes the problem where the governor is set only for the first core, but now governs all cores right from whatever utility you use. There have been comments on the lack of stability with this governor.
46. IntelliMM
A rewrite of the old Min Max governor and has 3 cpu states: Idle, UI and Max. Intelliminmax (intellimm) governor is designed to work with the newer SOCs with fixed voltage rails (ie MSM8974+ SOCs). It is designed to work within those fixed voltage ranges in order to maximize battery performance while creating a smooth UI operations. It is battery friendly and spends most of the time at lower frequencies.
47. Interactive Pro
A newer (modified) version of interactive which is optimized for devices such as the One Plus One. It is a more efficient than the original Interactive because it continuously re-evaluates the load of each CPU therefore allowing the CPU to scale efficiently.
48. Slim
A new governor from the cm branch and the slimrom project. This is a performance optimized governor and has been tuned a lot for newer devices such as the One Plus One.
49. Ondemand EPS
Once again, a modified version of Ondemand and is optimized for newer devices. It is based on the Semaphore Kernel's Ondemand which is more optimized for battery life and better performance than the traditional ondemand governor.
50. Smartmax EPS
A newer smartmax governor that has been slightly optimized for newer devices.
51. Uberdemand
Uberdemand is Ondemand with 2-phase feature meaning it has a soft cap at 1728 MHz so your cpu won't always go directly to max, made by Chet Kener.
52. Yankactive
A slightly modified interactive based governor by Yank555.lu. It has battery tweaks added onto it so expect better battery life! Based on user reports, this governor behaves more battery friendly than the original interactive governor without sacrificing performance.
53. Impulse
An improved version of interactive modified by neobuddy89. Impulse aims to have a balance between battery and performance just like interactive but has some tweaks to save battery.
54. Bacon
This is nothing but polished interactive governor branded as "bacon" since it was adapted from bacon device thanks to neobuddy89. Most of the tweaks are for performance/latency improvements
55. Optimax governor
This is based on ONDEMAND, like almost all governors that have arisen from XDA. It contains some enhancements from LG, particularly to freq boost handling so it will boost to a set level, almost like HTC's governor. It has different tunables to the HTC governor but it behaves pretty similar, the tunables it comes with default are a bit more conservative.
It originates from Cl3kener's Uber kernel for Nexus 5, where it has quite a reputation for battery life
56. Preservative governor
This is based on the idea that the CPU will consume a lot of power when it changes frequency. It is based on the conservative governor. The idea is that it will stay at the step specified (702MHz selected by the creator Bedalus) unless needed. You will notice it will hover around 702 a lot, and not go above too much, and only to min freq when NOTHING is happening at all. This is most beneficial when you are doing something like reading; the screen is static or playing light games that won't need boosting any more
The governor comes from Moob kernel for nexus 4
57. Touchdemand
Touchdemand is based on the ondemand cpu governor but has been modified for the Tegra 3 chip (tablet only) and has additional tweaks for touchscreen responsiveness.
58. ElementalX
If you are an owner of a nexus device, you probably have heard of a governor named ElementalX. Named after the kernel, elementalX is based on interactive but with some additional performance tweaks. This governor focuses on performance and not battery savings!
59. Bioshock
Not the game, but rather the CPU governor developed by Jamison904. A mix of ConservativeX and Lionheart. Good balance between battery savings and performance.
60. Blueactive
A new cpu governor based on interactive with tweaks to improve battery life. This governor is heavily focused in battery savings while performing decent in multitasking. Not a recommended gaming governor.
61. Umbrella_core
A new cpu governor based on interactive that is focused on battery life and not performance. It will still ramp up to a set frequency but will not stay at high frequencies for long. Users have reported weird behavior with this governor
62. ConservativeX
Essentially, it is a less aggressive version of conservative. More battery life, less performance.
63. HydrxQ
Simply a lulzactiveq governor with tweaks to performance (thanks to tegrak).
64. DevilQ
An aggressive pegasusq governor which keeps the hotplugging at max 2 cpu cores to offline). This is pretty much a more optimized pegasusq for phone's with quad core processors.
65. YankasusQ
Yankasusq is another modified pegasusq but with including screen off freq tunable and some other modifications as well. Possibly better battery life.
66. Darkness
It's based on nightmare but more simple and fast, basic configs but very complex structure. It is an updated nightmare gov and improved stability, so far it is quite stable in tests
67. Alucard
A favourite choice and one of the original governors that Alucard_24 made. Alucard is based on ondemand but has been heavily tweaked to bring better battery life and performance. It has been known to be battery friendly without sacrificing much performance.
Thanks to poondog for some of his governor descriptions!
Got it ?
Sent from my SM-N920P using XDA-Developers mobile app
Awesome man! Downloading now and about to refresh my rom. This came at the perfect time! Thank you so much!
Ill try it out ....thanks man
Sent from my SM-N920P using XDA-Developers mobile app
Thank you my good sir.
Sent from my SM-N920P using XDA-Developers mobile app
I assume it's booting up for everyone....if it wasn't I'm sure I would know by now
Sent from my Samsung Galaxy S6 using XDA Labs
Boots and works perfect, thanks again
Sent from my SM-N920P using XDA-Developers mobile app
The Sickness said:
I assume it's booting up for everyone....if it wasn't I'm sure I would know by now
Sent from my Samsung Galaxy S6 using XDA Labs
Click to expand...
Click to collapse
Working for me! Thank you for putting in the extra time, If I had the know how, I would love to help.
Sent from my SM-N920P using XDA-Developers mobile app
Thanks for doing this for us! I really appreciate your time.
Thanks,
Chaz187
Boots up fine and run butter smooth. Excellent work man. I haven't had an issue all night/ this morning. :good:
Thanks bro ??
Sent from my SM-N920T using XDA-Developers mobile app
Known issue:
Forgetting wifi after a reboot.
Here is a wifi fix for this awesome kernel.
(This is the build.prop from the Moar 3.2 MM build so if you are running an earlier version don't be fooled... just saying )
The change/fix was to modify this line in build.prop:
Code:
ro.securestorage.support=[COLOR="Blue"]false[/COLOR]
Credit @The Sickness for the fix and of course the custom kernel as well. :good:
good kernal so far testing battery drain now. will report back in a couple days . the only thing that i can see so far is Vudu do not play on any kernel that i flash, even this one. but it do play on stock Rom thu. so i dont know if it a rooted phone problem or a kernel problem .
Thanks for sharing ! Awesome work!!
Sent from my SM-N920P using Tapatalk
smiley45 said:
good kernal so far testing battery drain now. will report back in a couple days . the only thing that i can see so far is Vudu do not play on any kernel that i flash, even this one. but it do play on stock Rom thu. so i dont know if it a rooted phone problem or a kernel problem .
Click to expand...
Click to collapse
I cant say. I just installed this and breezed through a couple free tv episodes of something to test it and it seems to be fine.
I want to say Thank you to the person who donated to me....THANK YOU
Sent from my Samsung Galaxy S6 using XDA Labs
tdunham said:
Known issue:
Forgetting wifi after a reboot.
Here is a wifi fix for this awesome kernel.
(This is the build.prop from the Moar 3.2 MM build so if you are running an earlier version don't be fooled... just saying )
The change/fix was to modify this line in build.prop:
Credit @The Sickness for the fix and of course the custom kernel as well. :good:
Click to expand...
Click to collapse
Thanks Charles & The Sickness
I want to say Thank You to another donation. I really do appreciate it.
Yall make the S6 forums look real bad lol...
Sent from my Samsung Galaxy S6 using XDA Labs
Introduction
This kernel is based on Smartpack kernel by @sunilpaulmathew. The kernel has undergone many changes to further improve both battery life and performance from already what was an excellent kernel for the S5.
Features
CPU Governors - yankactive, impulse, ondemandplus, adaptive, smartmax, smartmax_eps, wheatley, nightmare, alucard, intellidemand, intelliactive, zzmoove, interactive, conservative, ondemand, powersave, lionheart, performance
IO Schedulers - zen, sioplus, deadline, cfq, bfq, tripndroid, vr, row, noop, fifo
GPU governors - simple_ondemand, msm_adreno_tz and more
Hotplugs - mpdecision, intelliplug
TCP algorithms- All enabled. Westwood default for best performance.
Franco Sound Control
Dynamic Hotplug
Dynamic Fsync
LCD notifier
Disabled CRCs for performance
Linaro 7.2 Toolchain
Supported Variants
klte: SM-G900F, SM-G900V, SM-S902L
kltekor: SM-G900K, SM-G900L/SM-G900S
kltedv: SM-G900I ,SM-G900P
klteduos: SM-G900FD, SM-G900MD
No other variants are supported
Download
AFH - https://www.androidfilehost.com/?w=files&flid=240642
How to install
1. Ensure you are not running a custom kernel already (can conflict)
2. Flash my kernel
3. Wipe dalvik/cache
4. Reboot
Credits
Sunilpaulmathew - For kernel base and scripts
Linus Torvalds - For linux kernel
Lord Boeffla - For many tweaks and patches
nathanchance - For Linaro TC
faux123 - For intell* governors/hotplugs
alucard12 - For alucard hotplug
haggertk - For LOS14.1
franciscofranco - For franco sound control
Source:
Github - https://github.com/gsstudios/LOS-plus-kernel
Changelogs
See github page
Kernel Adiutor Suggestions
Battery Savings
CPU Governor - Nightmare
Hotplug - Intelliplug
IO sched - ZEN
GPU governor - simple_ondemand
Performance
CPU Governor - Ondemandplus
Hotplug - Intelliplug
IO sched - ZEN
GPU governor - msm_adreno_tz
You can change around these settings or add your own if you like
What app do I use to tune this kernel?
I highly recommend Kernel Adiutor. It's free, open-source and is on the Google Playstore.
When will feature xyz be added?
I'll add it if I think everyone will benefit from this change, and that also means that I must find this feature to be useful.
Donations
While I am glad people want to help with the development through donations, I am generally opposed to accepting any form of donation.
Microphone not working?
Make sure the microphone gains in the sound section of KA is > 0. Alternatively, ensure that apply on boot has been unticked.
How do I use intellithermal?
In the CPU hotplug tab in KA, disable the two sliders underneath the slider for intellithermal. Then you may switch on intellithermal.
How can I help with development?
If you see or encounter any issues, let me know on github or on an XDA post. If you want to help develop, you can easily fork this project on github, add your own changes, then submit a pull request.
I'm back into kernel development after taking a long break since maintaining Dorimanx kernel for the S5. :highfive:
I've just released my first build (v1) which I've tested for some time now. Please let me know if there are any issues with the usual bug report format (dmesg + logcat + description of issue).
I just like a give another special thanks to @sunilpaulmathew for allowing me to use his kernel as base and for being open to the opensource community
Enjoy
Good to see you back to Kernel development... :good:
It will be a good deal for our S5 users
and hope you will still be active in my thread...
Saber said:
I'm back into kernel development after taking a long break since maintaining Dorimanx kernel for the S5. :highfive:
I've just released my first build (v1) which I've tested for some time now. Please let me know if there are any issues with the usual bug report format (dmesg + logcat + description of issue).
I just like a give another special thanks to @sunilpaulmathew for allowing me to use his kernel as base and for being open to the opensource community
Enjoy
Click to expand...
Click to collapse
I'll try it, I just want perf fixes
Further testing has reveal that Faux sound control values don't stick after setting them in KA. This issue will be resolved in the next build.
Regards, Saber
Is this the kernal that was going to help with the RR issues? Thanks for this kernal.
BadToThePhone said:
Is this the kernal that was going to help with the RR issues? Thanks for this kernal.
Click to expand...
Click to collapse
If you mean the performance issues with Smartpack + RR, then yes. However, it will take some tweaking it get it "buttery smooth".
Saber said:
If you mean the performance issues with Smartpack + RR, then yes. However, it will take some tweaking it get it "buttery smooth".
Click to expand...
Click to collapse
already noticing a HUGE difference in performance. It's phenomenal. Howcome I/O for internal is missing in KA
Does Faux audio interfere with V4A?
GeTex said:
already noticing a HUGE difference in performance. It's phenomenal. Howcome I/O for internal is missing in KA
Does Faux audio interfere with V4A?
Click to expand...
Click to collapse
I guess you mean internal IO scheduler? Works fine on my end. Maybe reflash kernel or try one of the modded KA apps.
As for faux sound control and V4A, I think you can have both, as long as you don't tune the values for faux sound (which BTW is broken until the next release).
Saber said:
I guess you mean internal IO scheduler? Works fine on my end. Maybe reflash kernel or try one of the nodded KA apps.
As for faux sound control and V4A, I think you can have both, as long as you don't tune the values for faux sound (which BTW is broken until the next release).
Click to expand...
Click to collapse
Internal I/O is missing from menu's, kernel clearly is flashed
good to know
GeTex said:
Internal I/O is missing from menu's, kernel clearly is flashed
good to know
Click to expand...
Click to collapse
Odd, I would imagine it would be an issue with KA unable to detect the paths required for IO tuning. Maybe problems with permissions? Any logs because I'm running out of ideas...
@Saber and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
BadToThePhone;75181281 [user=5811506 said:
@Saber[/user] and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
Click to expand...
Click to collapse
There's many ways to go about it, I cannot comment immediately and I'd rather work with @Saber first on a good configuration but so far I can recommend this
Change CPU gov to ondemandplus
Change CPU hotplug to intelliplug, change hytersis value to 4, change screen of freq to 10xx MHz, use profile balanced and touch boost on
Change internal I/O to sio or sioplus, readahead to 1024, external I/O to noop and readahead 2048, change swappiness to 30 and vfs cache pressure to 130, or keep 100 for neligable benefits, turn on KSM with an interval of 1000 or 500 for slightly better performance at cost of minor battery, make sure Zram is set to 420mb or less. Turn off the thermal drivers and use intellithermal on defaults
With a brand new battery I have 4hr10 screentime and 1d standby, that is with alot of background stuff such as 20 minute GPS pings and weather updates, wifi and data and GPS always on
Battery life isn't up to date yet, will need to test a few more days
I was previously using these settings. Do any of these still apply? Thanks
Cpu governor: nightmare
Cpuhotplug: intelliplug
Touchboost: on
Cpu threshold: 1250
Thermal: intellithermal on, vdd and corecontrol off
Gpu: adreno idler
I/o scheduler: zen
Sleep between scans: 1000ms
Power suspend mode: autosleep
Fast charge on
Fsync On
BadToThePhone said:
I was previously using these settings. Do any of these still apply? Thanks
Cpu governor: nightmare
Cpuhotplug: intelliplug
Touchboost: on
Cpu threshold: 1250
Thermal: intellithermal on, vdd and corecontrol off
Gpu: adreno idler
I/o scheduler: zen
Sleep between scans: 1000ms
Power suspend mode: autosleep
Fast charge on
Fsync On
Click to expand...
Click to collapse
No adreno idler in this kernel. Best to use power suspend mode hybrid for better battery life (uses display state + kernel sleep).
Edit: Also no UKSM. You can enable KSM if you like, but I personally don't need it.
BadToThePhone said:
@Saber and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
Click to expand...
Click to collapse
Please read my second post. Main goal of my profile is good battery + performance balance without that "lag" in RR. Change around the profile if you like to suit your taste (e.g. zzmoove instead of ondemandplus).
Saber said:
Please read my second post. Main goal of my profile is good battery + performance balance without that "lag" in RR. Change around the profile if you like to suit your taste (e.g. zzmoove instead of ondemandplus).
Click to expand...
Click to collapse
Is following your suggested settings plus what @GeTex recommended doing too much? Thanks alot
BadToThePhone said:
Is following your suggested settings plus what @GeTex recommended doing too much? Thanks alot
Click to expand...
Click to collapse
It's a little more extra compared to my recommendations, but either is fine for good balance.
When turning on intellithermal do I have to turn off vdd and corecontrol? Also do I have to turn off mpdescion?