[KERNEL][64 BIT]PMSKernel_v1[MARSHMALLOW ROMS](2016/06/10)[STABLE]

[KERNEL][64 BIT]PMSKernel_v1[MARSHMALLOW ROMS](2016/06/10)[STABLE] - YU Yureka Original Android Development

PMSKernel
Now to Kernels Section,
Hello YU Clan. Now time to release PMSKernel. Now without wasting time, lets move to features.
PMSKernelv1 is compiled from latest sources from CM Sources and latest UBER Toolchain. So the kernel is STABLE and there are no bugs and issues.
Coming to Features:
CPU TAB:
I haven't touched frequencies. No Underclocking or Overclocking as it makes kernel unstable.
Governors:
1) Lionfish.
2) Darkness.
3) Intellidemand.
3) Interactive.
4) Ondemand.
5) Userspace.
6) Powersave.
7) Performance.
THERMAL TAB:
1) Core Control.
2) VDD RESTRICTION.
3) Temperature Throttle.
GPU:
For GPU as well no UC or OC.
GOVERNORS:
1) Powersave.
2) Performance.
3) Simple_Ondemand.
4) Userspace.
5) msm-adreno-tz.
5) cpu-freq.
SCREEN:
Kcal is included.
Glove Mode.
WAKE CONTROLS:
1) All Wake controls are included considering Double Tap to Wake.
BATTERY:
Thundercharge is included. Se custom battery charging rate as per your needs.
IO SCHEDULERS:
1) Noop.
2) Deadline.
3) Row.
4) cfq.
5) bfq.
6) fiops.
Tune your Scheduler as per your needs.
Low Memory Killer:
Adaptive Low Memory Killer.
MISC CONTROLS:
1) Dynamic Fsync.
2) Vibration Strength.
3) TCP Congestion Algorithm.
Colour Enhancement is present.
I have tuned the kernel so that you get best Battery Backup on your favourite ROM and you can enjoy Performance as well.
I have tuned all the parts under .config so that the phone will heat least, you will get Juice and Performance at its best.
No Hotplugs present as of now. I don't use them as well. Will add in Future Builds.
Instructions for Flashing:
1) Download the PMSKernel_vx_20xx_xx_xx.zip.
2) Reboot to Recovery.
3) Clear Cache and Dalwik.
4) Flash the zip file.
5) Reboot and Enjoy.
NOTE;
MY KERNEL IS BASED ON LATEST SOURCES. SO IF YOU FLASH ON ROMS BASED ON OLD SOURCES, YOUR CAMERA WON'T WORK.
Use Kernel Auditor to play with my Kernel.
DOWNLOADS:
PMSKernelv1-Stable
TO DO:
Add Hotplugs.
Add more Governors.
Tune the kernel more.
Credits:
 @Shoaib05 
 @Sushant More
@Hriday Sharma
@Bishnu Prasad
Thanks a Lot Guys. I could not come up to kernel section without you all. _/_
 @Vams 
 @srvroxstar 
 @shubhojit
@Meet Gohil
@anupamdmoran
Thanks a lot to you all as well. You all help me a lot in testing.
Cheers:
Prathamesh.
XDA:DevDB Information
PMSKernel, Kernel for the YU Yureka
Contributors
PrathameshMS
Source Code: https://github.com/PMS22/PMSKernel_cyanogen_msm8916
Kernel Special Features:
Version Information
Status: Testing
Current Stable Version: v1
Stable Release Date: 2016-06-10
Created 2016-06-14
Last Updated 2016-06-14

Recommended Settings:
Make three Profiles in Kernel Auditor.
================BATTERY SAVER================
CPU TAB:
BIG:
Min Freq: 200 MHz
Max Freq: 533 MHz
Governor: Darkness.
Little:
Min Freq: 200 MHz
Max Freq: 800 MHz
Governor: Darkness.
BATTERY TAB:
Set Custom Charging Rate to 1500mA.
Don't worry, it doesn't damage or do any **** with your phone or charger.
GPU TAB:
Min Freq: 220 MHz
Maz Freq: 465 MHz.
Governor: Powersave.
IO Sched:
Internal:
Scheduler: Noop.
Read-ahead: 512kb
External:
Scheduler: Noop.
Read-Ahead: 896 kb.
Everything else to Default.
================BALANCED================
CPU TAB:
BIG:
Min Freq: 200 MHz
Max Freq: 800 MHz
Governor: Darkness.
Little:
Min Freq: 200 MHz
Max Freq: 998 MHz
Governor: Interactive.
BATTERY TAB:
Set Custom Charging Rate to 1500mA.
Don't worry, it doesn't damage or do any **** with your phone or charger.
GPU TAB:
Min Freq: 220 MHz
Maz Freq: 550 MHz.
Governor: Simple_ondemand.
IO Sched:
Internal:
Scheduler: fiops.
Read-ahead: 512kb
External:
Scheduler: Noop.
Read-Ahead: 896 kb.
Everything else to Default.
================GAMING================
CPU TAB:
BIG:
Min Freq: 200 MHz
Max Freq: 1497 MHz
Governor: Interactive.
Little:
Min Freq: 200 MHz
Max Freq: 1113 MHz
Governor: Interactive.
BATTERY TAB:
Set Custom Charging Rate to 1500mA.
Don't worry, it doesn't damage or do any **** with your phone or charger.
GPU TAB:
Min Freq: 220 MHz
Maz Freq: 550 MHz.
Governor: msm-adreno-tz.
IO Sched:
Internal:
Scheduler: fiops.
Read-ahead: 512kb
External:
Scheduler: fiops.
Read-Ahead: 896 kb.
Everything else to Default.

Reserved for Future Updates and Changelogs.

error : delete this comment plz

ptr347 said:
error : delete this comment plz
Click to expand...
Click to collapse
It doesn't for now. Will do it in next update.
Sent from my AO5510 using Tapatalk

Weew... New Kernel For our beloved Yu Yureka..!

Related

cpufreq on Nexus 4? (cpufreq drivers?) [Running Ubuntu Touch]

I am running Ubuntu Touch on Nexus 4 and I have tried to install cpufrequtils to be able to control frequencies of each 4 cores on the system.
The problem is that when try to run parallel applications on Ubuntu Touch, I don't achieve any speedups to their sequential counterparts (for example running bzip2 and pbzip2).
I am trying to do some performance analysis of sequential and parallel applications (such as gzip, pigz, bzip2, pbzip2) on Nexus 4.
---------------------
Below is what I get when I try to install and run cpufrequtils:
Installation..............
Code:
Unpacking cpufrequtils (from .../cpufrequtils_008-1_armhf.deb) ...
Processing triggers for ureadahead ...
Setting up cpufrequtils (008-1) ...
* Loading cpufreq kernel modules... [ OK ]
* CPUFreq Utilities: Setting ondemand CPUFreq governor...
* CPU0...
* CPU1...
* CPU2...
* CPU3... [fail]
And when I try to execute cpufreq-into.............
Code:
[email protected]:~/test$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: msm
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 0.00 ms.
hardware limits: 384 MHz - 1.51 GHz
available frequency steps: 384 MHz, 486 MHz, 594 MHz, 702 MHz, 810 MHz, 918 MHz, 1.03 GHz, 1.13 GHz, 1.24 GHz, 1.35 GHz, 1.46 GHz, 1.51 GHz
available cpufreq governors: interactive, ondemand, userspace, powersave, performance
current policy: frequency should be within 384 MHz and 1.51 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 384 MHz.
cpufreq stats: 384 MHz:89.53%, 486 MHz:0.56%, 594 MHz:0.42%, 702 MHz:0.05%, 810 MHz:0.02%, 918 MHz:0.02%, 1.03 GHz:0.02%, 1.13 GHz:0.01%, 1.24 GHz:0.01%, 1.35 GHz:0.01%, 1.46 GHz:0.01%, 1.51 GHz:9.34% (21486)
analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 0.00 ms.
analyzing CPU 2:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 0.00 ms.
analyzing CPU 3:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 0.00 ms.
So it seems there is a missing cpufreq driver which prevents utilization of all 4 cores.

[KERNEL] [xx/xx] [3.4.62] ★ AK ★ [v.0xx]

{
"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 am not responsible for any damage to your phone.
Read before downloading or posting in the thread:
Proceed with caution if you have no experience.
[4.3] STABLE KERNELS
NB: NEW ANYKERNEL FORMAT:
- Flash base Kernel of your rom before using this new version!
STOCK
stock Kernel: JSS
stock Kernel: JWR
JWR ED.
ak kernel: AK.JWR.25+
Features: Link
Github Kernel: Link
JSS ED.
ak kernel: AK.JSS.25+
Features: Link
Github Kernel: Link
[4.3] EXPERIMENTAL KERNELS
JWR ED.
ak kernel:
Github Kernel:
JSS ED.
ak kernel:
Github Kernel:
THANKS:
Faux
Stratosk
Mathkid
Francisco
Morfic
RamGear
BytecodeMe
Eng.stk
Jlink38
Boype
Thracemerin
Motley-git
Showp1984
Myfluxy
Androlinroot
Hellsgod
Zyonee
All RC, RD and RT
DON'T FORGET THANKS, RATE AND DONATE BUTTON:

Kernel Features
AK FEATURES
* Baseline:
4.3 JWR and JSS
Linux 3.4.62+
Compiled with Latest Linaro 4.8.2 Toolchain
-O3 Optimizations
SELinux Security Inside
* Wifi Drivers:
New Prima wlan drivers: v3.2.3.92a
* Governors:
Ondemand (Default)
Ondemandplus
Interactive
Conservative
Intellidemand
Wheatley
Hyper
Smartmax
* Hotplug Governors:
Mpdecision (Default)
auto hotplug:
2 core min online with screen on
1 core online with screen off
720mhz max freq screen off - 384mhz mix screen off
boosted and married with interactive
intelli plug
* Schedulers:
deadline (Default)
cfq
noop
sio
bfqv2r6
Fiops
Row
* Read Ahead Buffer Size:
256/32 (Default)
* Cpu Freqs Range:
270Mhz
378Mhz
384Mhz
486Mhz
594Mhz
702Mhz
810Mhz
918Mhz
1026Mhz
1134Mhz
1242Mhz
1350Mhz
1458Mhz
1512Mhz
* Gpu Freqs with Boost Support:
Boost:
128Mhz
200Mhz
320Mhz (Default)
400Mhz
487Mhz
533Mhz
Freqs:
128Mhz
200Mhz
320Mhz
400Mhz
487Mhz
533Mhz (Default)
* Gpu Governors with min power enabled when into deep sleep:
Ondemand (Default)
Simple
Performance
* Thermal Drivers:
Qualcomm thermal (Default)
Faux Intelli thermal
* Sweep on phone:
sweep2wake, sweep2slip
* TCP Congestion:
Westwood (Default)
Cubic
Bic
Htcp
Hstcp
Hybla
Vegas
Scalable
Lp
Veno
Yeah
Illinois
Reno
* Others Features:
Fully merged with cm10.2
OTG support
A lot of Cpu IDLE patches
Enhanced squre root algorithm
Asyn IO latency optimized
LZ4 Compressor/Decompressor for ZRAM
Random and Entropy fixes
CGROUP Timer slack
PA Halfbreed color by defaultStrips a lot of debugsDisabled CRC software control
New Codel NetScheduler
Topology Features
Scheduler Power SavingBattery life Extender (BLX)
Added SQLB Allocator
Optimized ARM RWSEM
Optimized Lib string and memcop
Added optimized AES and SHA1 routines
Hotplug Control
Touch Filter Control
Led triggers Control
SAI Control
Wakelock Stats enhanced
Fast Charger
Eco Mode (2 core only)
Snake Charmer (Freq capped)
C0,C1,C2,C3 Deep sleep State Control
Dynamic Fsync
Vibration control
Faux Gamma control
Faux Sound control v3
Stratosk Voltage control
Temperature Toggle
Added Charger Notify

Other Features
AK OPTIMAL SETTINGS:
CPU Control
Min clock = 270 MHhz
Max clock = 1.512 GHz
CPU Governor = Hyper
Mpdecision = Off
Auto Hotplug = On
1 core min - 2 core max
screen off max 702Mhz
screen off min 270Mhz
I/O Scheduler = noop
SOC Control
C0 - On
C1 - On
C2 - On
C3 - On
NB:
(Note: N4 AP modem is very sensitive to some of the deeper sleep states,
if you experienced Green/Yellow AP Modem Watchdog Bark screens,
I recommend disabling C2/C3 states).
Voltage Control
Boost Voltages = Off
Undervolt based on CPU type (slow, normal, fast or fastest)
GPU Control
GPU Governor = Simple
GPU Clock = 400 MHz
GPU Vsync Toggle = On
Misc Control
Dynamic File Sync = On
TCP Congestion Control = Westwood
Vibration Control = 70
Screen Color
Factory Presets - LG Presets
Color Adjustments - R, G, B 255, 250, 245
Gamma Amp Adjust 0 - R, G, B 13, 20, 22
Gamma Amp Adjust 1 - R, G, B 0, 2, 3
Z-Control
Set On Boot - On for both
ZRAM Disk size - 150~200 Megabytes (or 50 MB when disabled)
ZRAM Enable/Disable - Enable if you mult-task often
Clear VFS Cache After Boot - On
Auto FS Writeback Delay Mode - On
Swappiness - 100% if ZRAM enabled, 0% if disabled
VFS Cache Pressure - 100% if ZRAM enabled, 150% if disabled
Dirty Ratio - 20% for both
Dirty Background Ratio - 5% for both
HOW POST PROBLEMS BY FAUX
1. To report all random reboots with associated /proc/last_kmsg
2. To provide feedback on errors or bugs with detail phone information such as ROM, kernel version, and apps
3. Participate in Forum discussions (all is beta here) with others without FLAMING or post useless information such as:
a) Phone doesn't boot (without providing any additional information, ROM versions etc)
B) phone is too hot (without providing any additional information, ie OC freq, UV etc)
AK SUPPORT FAUXCLOCK:
you can view chagelog directly from APP
you can download official and beta releases
Thanks a lot to Faux who created this great application!
THE OPEN BETA
The Open Beta system is designed to have the community help each other and the developers.
This way, all potential bugs are flushed out so the final released version will be stable and error free.
The more actively you participate in Beta Testing the better the final product will be
(you are really helping yourself to create a better community software).
Faux123

Techincal infos
* PLEASE NB:
Many of the documents and informations are taken by other threads,
so to prevent someone PM me with ...., I want to avoid saying:
"all credit to the authors".
Thanks a lot.
C STATE POWER CONTROL
DOCs:
Faux123 - Manual for SOC power Control
Faux123 - SOC C-States demystified
Bigeyes0x0 - About C State
C0 (WFI) - Shallowest Sleep (default enabled)
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/wfi/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/wfi/idle_enabled
C1 (Retention) - slightly deeper sleep
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled
C2 (Stand Alone Power Collapse) - deeper sleep
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/idle_enabled
C3 (Power Collapse) - deepest sleep
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled
UNDERVOLTING USERSPACE
DOCs:
Stratosk - About Undervolting
Stock kernel uses a paramater boost_uV.
By default, is added in voltages but it can be disabled.
The value of boost_uV is 0 for Slow bin chips and 25000 uV = 25 mV
for Nominal, Fast and Faster.
The boost_uV may be disabled using this command:
(= undervolting by 25000 uV in Nominal, Fast and Faster)
echo n > /sys/module/acpuclock_krait/parameters/boost
3 more paramater that handle undervolting:
- lower_uV: undervolting value for lower frequencies
- higher_uV: undervolting value for higher frequencies
- higher_khz_thres: above this frequency (default 1350000KHz) higher_uV will be used.
Else lower_uV will be used.
Undervolting value is subtracted from stock voltage. The final voltage for each frequency is calulated:
Vdd(final) = Vdd(core) + boost_uV - uV
So, to undervolt frequencies 384000-1242000 by 25mV and the other frequencies by 12.5mV use these command:
echo 25000 > /sys/module/acpuclock_krait/parameters/lower_uV
echo 12500 > /sys/module/acpuclock_krait/parameters/higher_uV
The higher_khz_thres maybe changed using this command (for example to use higher_uV from 981000KHz):
echo 918000 > /sys/module/acpuclock_krait/parameters/higher_khz_thres
Debugfs file (acpuclk/acpu_table) to show the acpu table frequencies and voltages.
For example to get the information about the current status use this command:
cat /sys/kernel/debug/acpuclk/acpu_table
CPU PVS: Fast
Boost uV: 25000
Boost uV enabled: No
Higher KHZ threshold: 1350000
Lower under uV: 37500
Higher under uV: 25000
CPU KHz VDD(stock) VDD(final) Difference
384000 875000 812500 -62500
486000 900000 837500 -62500
594000 925000 862500 -62500
702000 950000 887500 -62500
810000 1000000 937500 -62500
918000 1025000 962500 -62500
1026000 1050000 987500 -62500
1134000 1100000 1037500 -62500
1242000 1125000 1062500 -62500
1350000 1150000 1100000 -50000
1458000 1162500 1112500 -50000
1512000 1175000 1125000 -50000

Nice. Gonna try it soon.

Yesssss
Sent from my Nexus 4 using Tapatalk 4

Word
Sent from my Nexus 4 using xda premium

So the party begins :fingers-crossed:

Fantastic
Sent from my Nexus 4

hell yeah! flashing now. it'll charge tonight, and I'll report back tomorrow with performance

Man this kernel is nice. Pretty smooth.
Sent from my Nexus 4 using Tapatalk 4

deleted

And the party started :thumbup::thumbup::thumbup: rated 5 stars as always
"using the search button won't get you killed"

w00t :victory:

ranasrule said:
TricksterMod is still the preferred app for changing kernel settings/parameters ?
Click to expand...
Click to collapse
Would like to know also. I prefer faux, but don't know if it will play nice.
Sent from my Nexus 4 using Tapatalk 4

Was waiting this kernel for my 4.3 baby....Thanks AK !

Whats is the difference between intelli hotplug and dynamic? Which is better?

TricksterMod is the preferred way to change kernel settings/parameters ?

Yes, it's in my eyes the best mod for kernel tweaks
GT-I9505 / Nexus⁴ Tapatalk

Just installed! Will come back with results as soon as I get them.

[KERNEL] EOL Twisted-V7.1 {DOL1-COF8 Sources} [GRAPHITE,Ofast,Frandom] April 3, 2016

{
"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"
}
Welcome to the Twisted Kernel. Most of you know me for my roms all the way back to the S4. So, I figured it was time to step
up my game and give building kernels a shot. Well, here is the outcome....................
*****************************************************************************
FEATURES
Built with DOL1 and patched COF8 Sources
Unification Commits making it "universal"
Compiled w/ GRAPHITE Optimazations
LowMemoryKiller Tweaks
Cache Tweaks
CPU OC/UC
A53 UnderClockable To 200Mhz Oc To 1600Mhz
A57 UnderClockable To 200Mhz Oc To 2400Mhz
Voltage Optimizations
Enabled LZ4 Compression
Enabled DCACHE Word Access
Enabled HMP Boosting On Initial Touch Level
Entropy Tweaks
Enabled Frandom
Optimized CPU Idle Time
11 I/O Schedulers
22 CPU Governors
Deep Sleep Fix
I/O Latency increased 34%
Dynamic CPU Hotplug tweaks
Linux Updated to 3.10.95
Memory Leak Patches
VMA Caching
Optimized GPU Thermal
Memory Leak Fixes
Injects SU through ramdisk
and a crap load of other Optimizations (I"m not typing all of that...)
*****************************************************************************
CPU Governors:
Darkness
Nightmare
Wheatly
Smartass2
Ondemandplus
Bluactive
Intellimm
Pegasusq
Hyper
Preservative
ConservativeX
Alcuard
Wave
Ktoonservative
Dancedance
Conservative
Ondemand
Userspace
Lionheart
Bioshock
Interactive
Performance
*****************************************************************************
I/O Schedulers
Noop
Deadline
CFQ
BFQ
Sioplus
Tripndroid
Fiops
Sio
Fifo
Zen
VR
*****************************************************************************
WARNING
I am NOT responsible for ANYTHING you do to your phone. This kernel has been tested and ran by several of my users....
Credits to the following who made this possible
@G.lewarne
@ktoonsez
@ShinySide
@Xileforce
@hrtkernel
and to many others
*****************************************************************************
Special Notes
To control the kernel you MUST use 3C Toolbox from the Play Store. There is a free version as well as a pro version.
Both will work just fine. Now, IF there are any questions on how to use this app, OR any kernel related questions, then
by all means ASK............
****************************************************************************
Code:
April 3
Release of V7.1
Fixed ktoonsevative gov
Fixed reboot issues
Compiled with GRAPHITE
Compiled with Ccache
LowMememoryKiller Tweaks
Enabled Frandom
and more crap.....
DOWNLOADS
Twisted-Kernel-V7.1
XDA:DevDB Information
Twisted-Kernel, Kernel for the T-Mobile Samsung Galaxy S6
Contributors
The Sickness
Source Code: https://github.com/The-Sickness/DOL1-S6.git
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2016-03-07
Beta Release Date: 2016-02-23
Created 2016-03-08
Last Updated 2016-03-29

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!
Continued in next post

For performance:
Single-core:
- Performance - Best
- Min Max - Great
Multi-core:
- Performance - Best
- Min Max - Great
For battery life:
Single-core:
- Conservative - Best
- Powersave - Good
Multi-core:
- Conservative - Best
- SLP/Sleepy - Great
- Perfomance may cry (PMC) - Best
- Powersave - Good
- Ktoonservative(Q) - Great
- Smartmax - Best
- ZZMove/ZZmanX - Requires tuning, use battery plus or battery profile
For balanced battery saving and performance:
Single-core:
- Interactive/Intelliactive - Best
- Ondemand/OndemandX - Stock, Best
- SmartassV2 - Great
Multi-core:
- MSM DCSV - Great, not common
- LulzactiveQ - Good
- Intelliactive - Good
- Interactive/InteractiveX - Great
- Ondemandplus - Great
- Darkness - Great
- Nightmare - Great
- Yankactive - Great
- Ondemand/OndemandX - Stock, Best
- Pegasus(q/d) - Best
- SmartassV2 - Great
- Wheatley - Good
- Hotplug/HotplugX - Good
- NeoX - Great
- HYPER - Best
- ZZMove/ZZmanX - Requires tuning, use optimized or default profile
- Dancedance - Good
For gaming:
Single-core:
- Interactive/InteractiveX - Best
- Performance - Great
- Ondemand/OndemandX - Great
- SmartassV2 - Best
Multi-core:
- Lionheart/LionheartX - Best
- Dancedance - Great
- Intelliactive - Great
- Yankactive - Good
- NeoX - Great
- Interactive/InteractiveX - Best
- SmartassV2 - Great
- Pegasus(Q/D) - Best
- Ondemand/OndemandX - Great
- HYPER - Best
- Performance - Great
- LulzactiveQ - Best
- Intellidemand - Good
- ZZMove/ZZmanX - Requires tuning, use gaming or performance profile
Other CPU Governors not mentioned in the recommended section are either not used by people anymore or they are not suited for most people or have been removed from kernels.
Why change your phones I/O Scheduler?
Most phone manufacturers keep your phones I/O Schedulers locked so users are unable to modify any values which could change the performance of your phone. However, once your phone is rooted, you can change these values allowing the potential to boost your phones performance and even slightly increase battery life. Here is a thorough guide on all of the common i/o schedulers.
What is an I/O Scheduler:
Input/output (I/O) scheduling is a term used to describe the method computer operating systems decide the order that block I/O operations will be submitted to storage volumes. I/O Scheduling is sometimes called 'disk scheduling'.
I/O schedulers can have many purposes depending on the goal of the I/O scheduler, some common goals are:
- To minimise time wasted by hard disk seeks.
- To prioritise a certain processes' I/O requests.
- To give a share of the disk bandwidth to each running process.
- To guarantee that certain requests will be issued before a particular deadline.
Which schedulers are available?
CFQ
Deadline
VR
Noop
Anticipatory
BFQ
FIOPS
SIO (Simple)
Row
ZEN
Sioplus
FIFO
Tripndroid
Descriptions:
Anticipatory:
Two important things here are indicative of that event:
- Looking on the flash drive is very slow from boot
- 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 noop.
Disadvantages:
- Requests from process operations are not always available
- Reduced write performance on high-performance hard drives
- Not very common in most kernels (or even phones these days)
CFQ:
The CFQ - Completely Fair Queuing - similar to the Dead Line maintains a scalable continuous Process-I/O, the available I / O bandwidth is fairly and evenly shared to all I / O requests to distribute. It creates a statistics between blocks and processes. With these statistics it can "guess" when the next block is requested by what process, each process queue contains requests of synchronous processes, which in turn is dependent upon the priority of the original process. There the V2 version has some fixes, such as I / O request improvements, hunger fixes , and some small search backward integrated to improve responsiveness.This is the default IO scheduler for Samsung smartphones.
Benefits:
- Has a well balanced I / O performance
- Excellent on multiprocessor systems
- Easiest to tune.
- Best performance of the database after the deadline
- Regarded as a stable I/O scheduler
- Good for multitasking
Disadvantages:
- Can make your phone lag when multitasking between intensive applications
- Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
- Jitter (worst case delay) 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, it is very popular and is in many well known kernels.
Benefits:
- It is nearly a real-time scheduler.
- Excels in reducing latency of any given single I/O
- Best scheduler for database access and queries.
- Does quite well in benchmarks
- Like noop, it is a good scheduler for solid state/flash drives
- Good for light and medium multitasking workloads
Disadvantages:
- If the phone is overloaded, crashing or unexpected closure of processes can occur
- Bad battery life if doing a lot of multitasking
ROW:
ROW stands for "READ Over WRITE"which is the main requests dispatch policy of this algorithm. 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.
The main idea of the ROW scheduling policy is: If there are READ requests in pipe - dispatch them but don't starve the WRITE requests too much. Bellow you'll find a small comparison of ROW to existing schedulers. The test that was run for these measurements is parallel read and write. It is sometimes used by default for custom roms and custom kernels
Benefits:
- Faster UI navigation and better overall phone experience
- Faster boot times and app launch times
- Possibly better battery life
Disadvantages:
- Slower write speeds
- Not a scheduler for benchmarking
- Some intensive applications like games could slow down your phone
SIO (Simple):
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. There is no conversion or sorting of requests.
Benefits:
- It is simple and stable.
- Reliable I/O scheduler
- Minimized starvation for inquiries
- Good battery life
Disadvantages:
- Slow random write speeds on flash drives as opposed to other schedulers.
- Sequential read speeds on flash drives are not as good as other IO schedulers
Noop:
The noop scheduler is the simplest of them. It is best suited for storage devices that are not subject to mechanical movements, such as our flash drives in our phones use to access the data. The advantage is that flash drives do not require rearrangement of the I / O requests, unlike normal hard drives. the data that come first are written first. It's basically not a real scheduler, as it leaves the scheduling of the hardware.
Benefits:
- Serves I/O requests with least number of cpu cycles.
- Is suitable for flash drives because there is no search errors
- Good data throughput on db systems
- Does great in benchmarks
Disadvantages:
- Reducing the number of CPU cycles corresponds to a simultaneous decline in performance
- Not the most responsive I/O scheduler
- Not very good at multitasking
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. It is a very good scheduler with elements of the deadline scheduler. It is the best for MTD Android devices. Vr can make the most of the benchmark points, but it is also an unstable scheduler. Sometimes the scores fluctuate below the average, sometimes it fluctuates above the average.
Benefits:
- Generally excels in random writes.
Disadvantages:
- Performance variability can lead to different results (Only performs well sometimes)
- Very often unstable and unreliable
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. BFQ has received many updates to the scheduler and the performance is consistently improving.
Benefits:
- Has a very good USB data transfer rate.
- 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
- Being constantly updated
- Good for multitasking, more responsive 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.
- Slower UI navigation
ZEN:
Based on the VR Scheduler. 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.
Benefits:
- Well rounded IO Scheduler
- Very efficient IO Scheduler
- More stable than VR, mainly because it doesn't really behave like VR.
- Relatively battery friendly
Disadvantages:
- Not found in all kernels
Sioplus:
Based on the original Sio scheduler with improvements. Functionality for specifying the starvation of async reads against sync reads; starved write requests counter only counts when there actually are write requests in the queue; fixed a bug).
Benefits:
- Better read and write speeds than previous SIO scheduler
- Good battery life
Disadvantages:
- The same as SIO scheduler
- Not found in all kernels
FIOPS:
This new I/O scheduler is designed around the following assumptions about Flash-based storage devices: no I/O seek time, read and write I/O cost is usually different from rotating media, time to make a request depends upon the request size, and high through-put and higher IOPS with low-latency.
Benefits:
- Achieves high read and write speeds in benchmarks, usually performs the best
- Faster app launching time and overall UI experience
- Good battery life
- Low impact to system performance
Disadvantages:
- Not very common in most kernels
- Not the most responsive IO scheduler (Lags in UI)
- Not good for heavy multitasking
FIFO (First in First Out):
A relatively simple io schedulers that does what has been described. It is also known as FCFS (First come first serve) but this really isn't true. It does basic sorting; sorting the processes according to the appropriate order and nothing else. In other words, it is quite similar to noop.
Benefits:
- Serves I/O requests with least number of cpu cycles.
- 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
- Not very good at multitasking
Tripndroid:
A new I/O scheduler based on noop, deadline and vr and meant to have minimal overhead. Made by TripNRaVeR
Benefits:
- Great at IO performance and everyday multitasking
- Well rounded and efficient IO scheduler
- Very responsive I/O scheduler (Compared to FIOPS)
- Relatively battery friendly
Disadvantages:
- Not found in all kernels
- Performance varies between different devices (Some devices perform really well)
Recommended IO schedulers:
For everyday usage:
- SIO (My personal favourite)
- NOOP
- CFQ (Forth choice)
- Deadline
- ROW
- Tripndroid (Third choice)
- ZEN (Second choice)
For battery life:
- SIO (Third choice)
- FIOPS (Second choice)
- NOOP (First choice)
- Tripndroid
- ROW (Forth choice)
- FIFO
For gaming:
- Deadline
- CFQ
- SIO (First choice)
- Tripndroid (Second choice)
- ZEN (Third choice)
- BFQ
- ROW
- FIOPS
For performance(Benchmarking):
- NOOP
- Tripndroid (Third Choice)
- SIO
- Deadline (Second choice)
- FIOPS (First choice)
For multitasking:
- BFQ (First choice)
- Deadline (Second choice)
- CFQ (Second choice)

Good luck brother...been a long time coming... v3 is a beast

VERY NICE!!!
Downloading now and will definitely follow this thread!! Looking forward to this and future updates!!

What what downloading now and will let you know how this beast rides!

slickrick54 said:
What what downloading now and will let you know how this beast rides!
Click to expand...
Click to collapse
Better strap in bro

Downloading, flashed, ready to play! Is cache clear necessary or should I be good?

Nice....been off the charger for bout an hr or so

So far, so TWISTED. Will report in battery life later today.

Running awesome here! Getting good battery life even with all the testing I've been doing with schedulers and governers. Once it settles in I bet battery life will get even better.

Already working on V4....

Hey bro,
I'm still in a crazy amount of sim training right now fighting V1 cuts and engine fires, so still haven't had time to flash your new rom, but I found time to flash this kernel on top of Sick As Hell V7 (yeah, that's out of date too lol). All I can say is, wow. This time of day my battery is usually around 45%, and since flashing this kernel, it's currently at 71%. Battery life is back baby!!
Loving the speed and response time as well. Once again man, you've breathed new life into my phone I'll keep you posted as soon as I'm able to flash some Twisted back onto my phone, and report on that as well! I'm looking forward to it!!

Ummm....the other 40 or so who downloaded my kernel....could I get maybe a "little" feedback? Or something....

The Sickness said:
Ummm....the other 40 or so who downloaded my kernel....could I get maybe a "little" feedback? Or something....
Click to expand...
Click to collapse
My bad bro been running it for 2 days now and wow it's even better than V2 and my battery life is great as well! :good:

The Sickness said:
Ummm....the other 40 or so who downloaded my kernel....could I get maybe a "little" feedback? Or something....
Click to expand...
Click to collapse
Good luck

The Sickness said:
Ummm....the other 40 or so who downloaded my kernel....could I get maybe a "little" feedback? Or something....
Click to expand...
Click to collapse
My fault man. I have been running V3 for about 3 days now and my phone has been silky smooth with great battery life. I have not tweaked the settings at all either just the stock settings. Great job @TheSickness.

I was beginning to wonder if I should continue with building V4....there hasn't been a kernel posted here for close to a year.
But....we'll see.

I installed v3 and noticed that the governor options were far far fewer than what was originally outlined in the first post. I'm guessing that is because a lot of them were/are no longer being used.
Prior to installing, I was running Unikernel v9.1 and getting about 4 hours Screen On Time.
The settings and what have you for the Twisted kernel in the 3C Toolbox seem to be a bit over my head.
I'd like to utilize the Kernel but could use a bit of guidance in setting it up.
Let me know if any of you can provide some minor support.
Thanks

The first post shows exactly how many governors are in V3. Post #2 shows governors as a whole, not what's in V3...
I have the best battery settings set as default. You can get more battery if you use Wheatly....

[KERNEL]Huawei Ascend P6S / P7 K-Tuned Kernel

Ascend P6S / P7 K-Tuned KernelHello! Finally I decided to make a new thread for kernel with description of all features.
So, here they are:
CPU Governors:
PegasusQ
AbyssplugV2
Optdemand
Interactive
Impulse
Pwrctrl_hotplug default
I/O Schedulers:
CFQ
Deadline
ROW
Noop
FIOPS default
TCP Congestion:
HTCP
Reno
BIC
CUBIC
Westwood+ default
Upstreamed to 3.0.101 version
SELinux permissive for 5.1.1
LZ4 kernel & ramdisk compression
Backport random from kernel 4.0 branch
ExFAT version updated from 1.2.5 to 1.2.9
F2FS support
Fixed 5.1.1 GPU performance regression bug
USB Fast Charge
Intelli-Plug
Asynchronous Fsync
CPU overclock: enabled 1996MHz CPU frequency and 1795MHz for P6S
CPU undervolting
GPU overclock: enabled 700MHz GPU frequency for P6S
GPU undervolting
Adjusted stock CPU & GPU governor thresholds for better performance
DoubleTap2Wake
Sweep2Sleep
init.d support
set_immutable binary removed from ramdisk for 4.4.2
Speed up system startup
Now more detail about some features:
Governors
PegasusQ
Governor from Samsung with hotplug support. Perhaps, the most tunable and flexible one.
Parameters description:
sampling_rate: the interval with which governor will be carried out. Less value - better responsiveness, but at the same time, more load for CPU by governor itself.
sampling_down_factor: amount of iterations governor will stay at highest frequency before go down.
up_threshold: load threshold in % above which CPU frequency will be increased.
up_threshold_at_min_freq, freq_for_responsiveness: at frequency lower than freq_for_responsiveness will be used up_threshold_at_min_freq threshold - provided for better responsiveness.
down_threshold: load threshold in % below which CPU frequency will be decreased.
freq_step: step of frequency encrease in % from maximum frequency.
hotplug_freq_*: high and low frequency thresholds for making decision about hotplug of each core.
For clarity, it looks like this:
Code:
static int hotplug_freq[4][2] = {
{0, 1596000},
{208000, 1795000},
{416000, 1996000},
{624000, 0}
};
In this array left column is frequency at which core will be disabled; right column - frequency at which will be enabled next core.
hotplug_rq_*: analogous parameters set (array), defining queue task length for making decision about hotplug of each core.
Code:
static int hotplug_rq[4][2] = {{0, 50}, {50, 100}, {100, 150}, {150, 0}};
For example, second core will be disabled after reaching 208MHz frequency and amount of tasks must be less than 50;
third core will be enabled after reaching 1795MHz frequency by second core and amount of tasks more than 100.
cpu_up_rate: amount of governor iterations cpu should stay at defined frequency for enabling next core.
cpu_down_rate: amount of governor iterations cpu should stay at defined frequency for disabling last active core.
down_differential: defines load in % which must be less than up_threshold to go to lower frequency.
hotplug_lock: lock amount of active cores.
min_cpu_lock: limits min value of enabled cores.
max_cpu_lock: limits max value of enabled cores.
up_nr_cpus: defines how many cores to enable at a time.
AbyssplugV2
Based on Conservative, has hotplug support. Pluses: pretty simple, hence doesn't load CPU by himself. Frequency increases sequentally, after reaching max frequency - enables next core. And vice versa. Minuses: often enables / disables cores (what in itself is energy intensive).
Distinctive parameters:
up_threshold_hotplug: load threshold in % above which will be enabled next core.
down_threshold_hotplug: load threshold in % below which will be disabled last active core.
boost: load threshold above which frequency will be increased through step (for exaample., from 208000 immediately on 624000)
Optdemand
Governor by Hisilicon, based on Ondemand. Backported from Honor 4X/4C. Distinctive feature is each frequency has its own thresholds to go to higher or lower frequency.
Distinctive parameters:
go_hispeed_load, hispeed_freq: after exceeding go_hispeed_load threshold, CPU goes immediately to hispeed_freq frequency.
up_thresholds, down_thresholds: above and below load thresholds for each frequency. For clarity:
Code:
static unsigned int operating_points[7][3] = {
/* kHz up_threshold down_threshold */
{208000, 60, 0},
{416000, 60, 30},
{624000, 70, 40},
{798000, 80, 50},
{1196000, 85, 50},
{1596000, 90, 60},
{1795000, 95, 70},
{1996000, 100, 80},
};
For example, for frequency 624MHz, if load will go below 30%, will be calculated new lower frequency according to new load value; if load will go above 70% - frequency will be increased.
boost: frequency will be increased to hispeed_freq
bostpulse_duration: duration of boost in microseconds.
Interactive
Google's gold standard governor. Updated to 3.4 kernel branch
Impulse
Based on Interactive governor. Good responsiveness.
USB Fast Charge
Increases charge current when connected to USB. It has sense only when connected to USB 3.0
Can be enabled by writing "1" into /sys/kernel/fast_charge/force_fast_charge file or by third party applications.
Disabled by default
Intelli-Plug
Hotplug driver for governors not supporting hotplug.
Activated and deactivated automatically depending on chosen governor.
Parameters are in /sys/module/intelli_plug/parameters
nr_possible_cores: max cores affected by driver.
nr_run_profile_sel: has several profiles :
0: balance default
1: performance
2: conservative
3: eco
4: eco extreme
screen_off_max: max frequency at screen off.
touch_boost_active: enables additional core at screen touch disabled by default
CPU undervolting
Undervolting values can be set for each frequency individually. Regulator has step 8mV starting from 700mV. I've got such stable values:
{
"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"
}
But you should start from higher values. I've made a test: CPU locked at frequency 1795MHz, RAR creates archive with 4 threads in 10 minutes. Average CPU temperature during this time was 56.124 degrees, with undervolting average temperature became 51.119 degrees. I.e. average temperature became lower for 5 degrees which means less power consumption.
Comparative graph:
GPU undervolting
Since I couldn't find any common used sysfs interface and applications supporting it, you can make it using script (see init.d spoiler).
My stable values are:
Code:
160: 860 -> 700
266: 860 -> 732
355: 876 -> 764
533: 956 -> 860
700: 1052 -> 924
But most probable, you will have troubles with such values, try to find suitable for your own.
3DMark Ice Storm Extreme showed average temperature decrease from 61.587 to 55.502 degrees.
Comparative grapth:
DoubleTap2Wake
Screen on by double tap on it. Has two parameters in /sys/android_touch
doubletap2wake: enables dt2w. Possible values are:
0: disabled default
1: active at all screen
2: active at top half
3: active at bottom half
4: active at navbar
dt2w_duration: Since I couldn't implement waking up device from deep sleep by irq from touch panel, so kernel doesn't go to deep sleep when dt2w is active, I added parameter defining how long dt2w stays active after screen off. After this duration dt2w becomes inactive and kernel can go into deep sleep.
Sweep2Sleep
Swipe on navbar for screen off. Can be enabled by writing "1" into /sys/android_touch/sweep2sleep file. Disabled by default.
s2s_length: swipe length in dots. By default, equal to 25% of screen width.
init.d
For executing scripts at startup, put them in /system/etc/init.d folder and set permissions to 0755
Several scripts examples (doubletap2wake, sweep2sleep, fast_charge, gpu_undervolting): View attachment scripts.rar
Scores
For correct governors switching I recommend to use Kernel Adiutor
It also lets to manage IO schedulers, TCP congestion, fast charge, CPU undervolting.
Requirements:
Unlocked bootloader
TWRP
Installation:
Just install zip-archive from TWRP
Download:
View attachment K-Tuned_kernel-4.4.2.zip
View attachment K-Tuned_kernel-5.1.1.zip
Source: Github
Updates:
31.10.2016
CVE-2016-5195 "Dirty COW" fixed.
Now CPU voltage values take effect right after frequency changes.
30.07.2016
Adjusted voltages for overclocked frequencies due to cases of appearing stability issues on some devices.
15.05.2016
Removed GPU undervolting applying at booting due to some users had stability issues. Now for GPU undervolting use init.d script individually.
Adjusted governor thresholds.
Reduced min online CPUs from 3 to 2 when screen is on for stock pwrctrl_hotplug governor.
Regards,
Kostyan_nsk

Battery is better from stock kernel??
Version lollipop compatible?

roxkiller said:
Battery is better from stock kernel??
Click to expand...
Click to collapse
for me it is the same if you set dt2w to 3 minutes
roxkiller said:
Version lollipop compatible?
Click to expand...
Click to collapse
just download K-Tuned_kernel-5.1.1.zip
if someone want to set dt2w and s2s without init.d can use this apk made by Printusrzero http://forum.xda-developers.com/asc...ap-to-wake-t3036327/post62542196#post62542196

Thank you so much! I've been waiting for ages for a kernel which isn't only for emui 2.3

I'd installed kernel 5.1.1 ktuned on my P7 B852 and it's continuously restarts. Anyone had a kernel stock for TWRP?

What is your preferred setting?
Mine:
GOVERNOR: Impulse
CPU : maximum frequency 1596mhx
I/O : fiops with 128kb readahead
INTELLIPLUG :disabled
I discovered that with Intelliplug enabled, my phone has some glitches.....
With the settings above i get 50-60% battery when i go home, 8-10 pm
What are your settings ?

leleallof said:
I'd installed kernel 5.1.1 ktuned on my P7 B852 and it's continuously restarts. Anyone had a kernel stock for TWRP?
Click to expand...
Click to collapse
Someone else tried it on P7?

Installed with cwm on B861. Working, but I see no difference.

@Kostyan_nsk kernel comes overclocked, when I try to select the default clock and start the cell with the standard clock is not, always coming back to overclock, so I went back to stock kernel

@roxkiller, just set "Apply on boot" in Kernel Adiutor after limiting max. cpu frequency and enable Kernel Adiutor in Startup Manager, so KA will aplly your settings after reboot.
And btw, if you didn't notice, cpu voltage at 1996MHz is the same as at 1795MHz, therefore I doubt that power consumption will noticably increase relatively to 1795Mhz frequency...

I have set the cpu undervolting according to your recommandation. Today , i received a message on whattsap , when i picked up the phone to read it, the phone was already rebooting. It enter the system but saying no root available !!!
Rebooted the phone again, all ok.

kye04 said:
I have set the cpu undervolting according to your recommandation.
Click to expand...
Click to collapse
It is not a recommendation, it's just my stable values as "play around" point.

@Kostyan_nsk it would be possible to compile a version without overclock ? I and perhaps most people do not like under / overclock the device, just heating up ... or pack the kernel to the option selected remain in next boot?

Kostyan what are you settings?

Updated version and details in first post.

Kostyan_nsk said:
Updated version and details in first post.
Click to expand...
Click to collapse
Thank you for the update. Has the screen glitches bug found in the P7 been resolved in this release?

jordi-chant said:
Thank you for the update. Has the screen glitches bug found in the P7 been resolved in this release?
Click to expand...
Click to collapse
+1
I really want to try it on my p7

As my memory serves me right, this issue was solved a few months ago. But you better have to ask P7 owners about it.

I thought the problem was solved for 720p but with 1080p there were still glitches?

720p never had glitches at all.

[KERNELS]{W8,T} Twisted V11.5 [6.0.1 MM] SynaspeSaberMod 7.0OC/UC* 12/14/16

{
"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"
}
OK folks......This thread will contain TWO kernels. Let me repeat that "TWO KERNELS". One for the S6 Flat,
and one for the S6 Edge. MAKE SURE you download the right kernel for your phone. Or you will have some very
serious issues.
Both of these are built from the same source, just different config files. Both have ALL of the same features, tweaks, etc.
These kernels are for the T-Mobile S6 and Edge ONLY. If you flash this to a different device then you are on your
own. If some brave soul flashes this to anything but a T-Mobile S6 Flast or Edge, let me know and I can make a list
of compatibility.......
This kernel has alot of tweaks that can be adjusted by YOU. In order to change any of the kernel parameters you need use a kernel app. Both kernels
support Synaspe....
I want to remind the Edge users........I built this for YOU, not me. I have NO USE for a Edge kernel. So it may be a good idea to at
least tell me Thank you for the time I had to spend just for yall. Lack of appreciation will bring Edge development to a halt on my end.
***FEATURES***
EPD1, EPH2, EPK5 Ramdisk
Synaspe Support
Built with Sabermod 7.0 Toolchain (optimized)
Compiled with Graphite
Linux 3.10.104
Injects Root via SuperSU "systemless"
-A53 UnderClockable To 200Mhz OC to 1704Mhz
-A57 UnderClockable To 200Mhz OC to 2304Mhz
VMA Caching
Sleep/Suspend Patches
22 CPU Governors
11 I/O Schedulers
and a ton of other crap........
SYNASPE
OC/UC
CPU Voltage
GPU Voltage
GPU Overclock
HMP Threshold
Power Aware Scheduling
Live CPU Stats
Input-Booster
Thermal Control
HMP Voltage
I/O Tunables
LMK Profiles
UKSM
Dynamic FSYNC
Dynamic Dirty Page Writeback
Virtual Nand Swap
ZSwap Memory Pool
Kernel Entropy
Gentle Fair Sleepers
Arch Power
Google Play Services Battery Drain Fix
Wakelock Control
Audio Control (ie EQ)
Live Battery Stats
Battery Settings
LED Control
And more........
Keep in mind that this is a work in progress. Which means I will be adding more improvements for
our phones. Your job is to participate in my thread, my job is to give you have kick azz kernel.
Flashing either kernel is pretty easy. Go into recovery and flash.....Do not wipe anything. Modules
are now built into the kernel and not separate like back in the day.
***DOWNLOADS***
Twisted-Kernel-Flat-V11.5
Twisted-Kernel-Edge-V11.5
I have done my part. Now its YOUR turn...........
XDA:DevDB Information
Twisted Kernel 6.0.1, Kernel for the T-Mobile Samsung Galaxy S6
Contributors
The Sickness
Source Code:https://github.com/The-Sickness/Twisted-MM
Kernel Special Features: G920T/G925T
Version Information
Status: Stable
Stable Release Date: 2016-05-11
Beta Release Date: 2016-05-09
Created 2016-05-12
Last Updated 2016-07-12
XDA:DevDB Information
Twisted-Kernel, ROM for the T-Mobile Samsung Galaxy S6
Contributors
The Sickness
ROM OS Version: 6.0.1 MM
Version Information
Status: Testing
Created 2016-10-29
Last Updated 2016-10-29

My man doing big things bro! Thank you so much we edge users desperately needed this.... :good::good::good:

Thanks bro...for all u fkin do for us

Nice, you managed to fix the ram issue? Ah I see you've added extra tcp, muh westwoods

EDGE USERS THANK YOU!!
Edge users....please make sure you thank this man for his help. He spent a lot of time getting this thing to work for us. He had to use testers since he doesn't have the edge to test on, and believe me, it was flash and pray.
He stuck with us when he didn't have to, so let's show some appreciation here since he's pretty much the only one working on kernels for our devices.
Sent from my SM-G925T using Tapatalk

You're awesome man! Gonna flash this as soon as I can, Thank you for your hard work for us Edge users!

Nice work bro.
That is dedication making a kernel for a device you don't even own.
Let's see some appreciation here people. This guy is making things happen!

Damn awesome of you to do this! I'll be hooking up on V2 hopefully tomorrow as well as this!

Glad everyone is happy. I'm currently building V2....
Sent from my SM-G920T using XDA-Developers mobile app

The Sickness said:
Glad everyone is happy. I'm currently building V2....
Left you a Double Thanks on the Edge Forum. Will be checking in here from now on. Thanks again
Click to expand...
Click to collapse

The Sickness said:
Glad everyone is happy. I'm currently building V2....
Sent from my SM-G920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey bro what app do you use for xda?

slickrick54 said:
Hey bro what app do you use for xda?
Click to expand...
Click to collapse
XDA Premium
Sent from my SM-G920T using XDA-Developers mobile app

The Sickness said:
Glad everyone is happy. I'm currently building V2....
Sent from my SM-G920T using XDA-Developers mobile app
Click to expand...
Click to collapse
You are the man a lot of dedication for all u do for us users especially the edge users being u don't have the device and it was fast lol hope they appreciate it I'm gonna still say thanks bro Bro is this the same kernel in your rom ? @The Sickness

Wow. Just flashed on xtresto tmobile edge and am now permissive. Great s**t.

genuine55 said:
You are the man a lot of dedication for all u do for us users especially the edge users being u don't have the device and it was fast lol hope they appreciate it I'm gonna still say thanks bro Bro is this the same kernel in your rom ? @The Sickness
Click to expand...
Click to collapse
No...a little different. I changed some voltage tables that were causing reboots for some folks.
Sent from my SM-G920T using XDA-Developers mobile app

The Sickness said:
No...a little different. I changed some voltage tables that were causing reboots for some folks.
Click to expand...
Click to collapse
Cool thanks

This one is even more different...
Sent from my SM-G920T using XDA-Developers mobile app

The Sickness said:
This one is even more different...
Click to expand...
Click to collapse
Lol thanks for the tease i know it's loaded lol :highfive:

Database Develop

welcome