• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[KERNEL][TMO][TW 4.4][12/08/2014] KT-NOTE4 - NIH - KTweaker

Search This thread

ktoonsez

Inactive Recognized Developer
Nov 3, 2011
16,263
43,219
Tempe
Ktoonsez presents:
ab2a64c561764.png


KT-NOTE4 kernel features
Must have a Note 4 model N910T or N910P or N910W8
Must have a Touchwiz Rooted ROM
Must have CWM/TWRP based recovery installed
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
KTweaker app for kernel control
KTweaker Widgets
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•exFAT for Touchwiz

4fb98c4be2161.png

Touchwiz Kitkat 4.4 VERSION:
11.11.2014: http://goo.gl/IG2O5Q

Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik



Post #2 will be reserved for change logs

Post #3 will be reserved for MY Settings, Extras and FAQ's

Sources can be found here:
https://github.com/ktoonsez/KTNOTE4
 
Last edited:

ktoonsez

Inactive Recognized Developer
Nov 3, 2011
16,263
43,219
Tempe
Change Log 12.08.2014
1. Added some Profiles to the KTweaker Shop, thanks to @zman2107 for helping out
2. Some tweaks to ktoonservativeq
3. Added Trinity Colors, thanks to @twistedumbrella for porting in the code
4. Added Bluetooth Min Mhz control
5. Added Music/Media Min Mhz control
6. Added bfq scheduler

Change Log 11.13.2014
1. Rebase kernel source on N910F
2. NOW Working on F and G models!!!!!!!!!!!!!!!
3. Make ramdisk universal so its working on all Qualcomm variants
4. Add Fast Charge from my S4/S5 code
5. Increase bandwidth fro OC steps from @twistedumbrella
6. Removed a butt load of dmesg spam

Change Log 11.11.2014
1. Initial release
2. Based on Samsung source from N910T model
3. Added multi compatibility for multiple models
4. Removed root restrictions from kernel
5. Made selinux permissive
6. Added voltage control
7. Added OC to 3072 Mhz
8. Added KThermal
9. Added KT Hotplug
10. Lots more stuff to come!!!!!!!!!!!!!!!!!!!!!!!!
11. Linaro -O3 compiled plus Make file opto's
12. Added bfq scheduler
13. There is lots of stuff in KTweaker not enabled yet so only use the stuff that is listed in this change log!!!
 
Last edited:

ktoonsez

Inactive Recognized Developer
Nov 3, 2011
16,263
43,219
Tempe
ktoonservativeq explained:


***** NOTES *****
Any item with the word cycle in it refers to how many sampling_rate's have occurred.
Examples:

A "boost_hold_cycles" of 22 and a sampling_rate of 45000 equates to 1 seconds of holding your Mhz at the boost level.
A block_cycles_offline_screen_on of 11 and a sampling_rate of 45000 equates to a half of a second block before it takes cores offline.

***** NOTES *****


block_cycles_offline_screen_off =1
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is OFF.

block_cycles_offline_screen_on = 11
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is ON.

block_cycles_online_screen_off = 11
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is OFF.

block_cycles_online_screen_on = 3
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is ON.

block_cycles_raise_screen_off = 11
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is OFF.

block_cycles_raise_screen_on = 3
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is ON.

boost_2nd_core_on_button_screen_off = 1
When this item is a 1, it will turn on the 2nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.

boost_2nd_core_on_button_screen_on = 1
When this item is a 1, it will turn on the 2nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.

boost_3rd_core_on_button_screen_off = 0
When this item is a 1, it will turn on the 3nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.

boost_3rd_core_on_button_screen_on = 0
When this item is a 1, it will turn on the 3nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.

boost_4th_core_on_button_screen_off = 0
When this item is a 1, it will turn on the 4nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.

boost_4th_core_on_button_screen_on = 0
When this item is a 1, it will turn on the 4nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.

boost_hold_cycles = 22
How many sampling_rate cycles need to occur before going out of CPU/GPU boost mode

disable_hotplug = 0
When this item is a 1, it disables hotplugging so all cores stay on full time. 0 lets all cores turn on and off when needed.

disable_hotplug_bt = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while paired to a bluetooth device and doing bluetooth activities like playing music, transfering files.... 0 doesn't do anything extra to the cores when doing bluetooth functions.

disable_hotplug_chrg = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while charging the device. 0 doesn't do anything extra to the cores while charging.

disable_hotplug_media = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while playing music or movies. 0 doesn't do anything extra to the cores while music or movies are playing.

down_threshold_screen_off = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is OFF.

down_threshold_screen_off_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the 2nd core is taken offline while screen is OFF.

down_threshold_screen_off_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the 3rd core is taken offline while screen is OFF.

down_threshold_screen_off_hotplug_3 = 55
A percentage of CPU utilization that needs to occur before the 4th core is taken offline while screen is OFF.

down_threshold_screen_on = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is ON.

down_threshold_screen_on_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the 2nd core is taken offline while screen is ON.

down_threshold_screen_on_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the 3rd core is taken offline while screen is ON.

down_threshold_screen_on_hotplug_3 = 55
A percentage of CPU utilization that needs to occur before the 4th core is taken offline while screen is ON.

freq_step_lower_screen_off = 8
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is OFF.

freq_step_lower_screen_on = 2
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is ON.

freq_step_raise_screen_off = 1
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is OFF.

freq_step_raise_screen_on = 5
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is ON.

ignore_nice_load = 0
If this value is "1," the system will ignore "Nice" processes when deciding to scale up or down. Nice processes are used by the IO scheduler to designate a low-priority process. Ignore nice load basically tells a governor to disregard processes with higher nice values.

lockout_2nd_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.

lockout_2nd_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.

lockout_3rd_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.

lockout_3rd_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.

lockout_4th_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.

lockout_4th_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.

no_extra_cores_screen_off = 1
When set to a 1, this option keeps all extra CPU cores offline while the screen is OFF. 0 lets it hotplug them on and off as needed

sampling_down_factor = 1
NOT USED!

sampling_rate = 45000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is ON.

sampling_rate_min = 10000
READ-ONLY value that specifies the lower value that "sampling_rate" and "sampling_rate_screen_off" will accept.

sampling_rate_screen_off = 45000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is OFF.

super_conservative_screen_off = 0
With the screen OFF: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items.

super_conservative_screen_on = 0
With the screen ON: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items to create a smooooooth UI experience.

sync_extra_cores_screen_off = 0
With the screen OFF: When set to a 1, all online cores will be sync'd to the same speed as core 0. When set to a 0, all cores will operate at speeds independant of each other.

sync_extra_cores_screen_on = 0
With the screen ON: When set to a 1, all online cores will be sync'd to the same speed as core 0. When set to a 0, all cores will operate at speeds independant of each other.

touch_boost_2nd_core = 1
When set to a 1, this option turns on the 2nd core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.

touch_boost_3rd_core = 0
When set to a 1, this option turns on the 3rd core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.

touch_boost_4th_core = 0
When set to a 1, this option turns on the 4th core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.

touch_boost_cpu = 1804800
The Mhz that you want the online CPU's to jump to when the screen is touched.

touch_boost_cpu_all_cores = 0
When set to a 1, this option sets the current Mhz on all online cores to the selected touch_boost_cpu value.

touch_boost_gpu = 462400
This value specifies what Mhz the GPU should jump to when the screen is touched.

up_threshold_screen_off = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is OFF.

up_threshold_screen_off_hotplug_1 = 58
A percentage of CPU utilization that needs to occur before the 2nd core is put online while screen is OFF.

up_threshold_screen_off_hotplug_2 = 68
A percentage of CPU utilization that needs to occur before the 3rd core is put online while screen is OFF.

up_threshold_screen_off_hotplug_3 = 78
A percentage of CPU utilization that needs to occur before the 4th core is put online while screen is OFF.

up_threshold_screen_on = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is ON.

up_threshold_screen_on_hotplug_1 = 58
A percentage of CPU utilization that needs to occur before the 2nd core is put online while screen is ON.

up_threshold_screen_on_hotplug_2 = 68
A percentage of CPU utilization that needs to occur before the 3rd core is put online while screen is ON.

up_threshold_screen_on_hotplug_3 = 78
A percentage of CPU utilization that needs to occur before the 4th core is put online while screen is ON.




Other Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
 
Last edited:

Misterjunky

Senior Member
Jan 18, 2011
9,455
6,717
Bakersfield, California
Android Wear
  • Like
Reactions: em0ney14

em0ney14

Senior Member
Apr 1, 2014
576
375

mocsab

Senior Member
Aug 16, 2011
3,723
1,371
West Milwaukee
www.shimmeringglass.com
WOOT WOOT (I never understood why it is WOOT WOOT - versus WHOOO WHOOO - ? I never heard anyone ever go WOOT WOOT and prounce the T when they are really happy - more like WOO HOO - or something along those lines - well regardless The point is the same - and the sentiment is obvious - I am really glad to see you here - and just as glad to see you are brining us a new kernel -

Looking forward to flashing this and getting some ktnoonze kernel goodness on my NOTE 4 - thanks!

PS - who came up with the WOOT - versus the WOO ? Inquiring minds want to know.
 

ktoonsez

Inactive Recognized Developer
Nov 3, 2011
16,263
43,219
Tempe
Cant seem to get cpu to go past 2649. I have it set with ktweak to 3000 but it stops at 2649

Sent from my SM-N910T using XDA Free mobile app

What app r u using to see what spees its hitting? My KTMonitor app? Are you running a benchmark app to push the CPU?
 

chrisgto4

Senior Member
Dec 17, 2009
609
121
Dallas
What app r u using to see what spees its hitting? My KTMonitor app? Are you running a benchmark app to push the CPU?

Im using ktmonitor. I tried the most cpu intensive apk i have. Video to gif.....it runs the cpu at avg 75-100% cpu usage. Then changed the governor to performance and set min/max to 3000. Still stayed at 2649. Other than that very impressed with kernel. Nice work

Sent from my SM-N910T using XDA Free mobile app
 

mocsab

Senior Member
Aug 16, 2011
3,723
1,371
West Milwaukee
www.shimmeringglass.com
Cant seem to get cpu to go past 2649. I have it set with ktweak to 3000 but it stops at 2649

Sent from my SM-N910T using XDA Free mobile app

Click main settings - CPU Settings - then select - enable OC settings - then set your CPU to what you want to set it to - I did these steps and had no issues.

Some things are not working yet - but I know it is very early in this kernel's life - more good things are sure to be coming soon.
 

ktoonsez

Inactive Recognized Developer
Nov 3, 2011
16,263
43,219
Tempe

Top Liked Posts

  • There are no posts matching your filters.
  • 62
    Ktoonsez presents:
    ab2a64c561764.png


    KT-NOTE4 kernel features
    Must have a Note 4 model N910T or N910P or N910W8
    Must have a Touchwiz Rooted ROM
    Must have CWM/TWRP based recovery installed
    •Samsung open source
    •Optimized kernel configuration
    •unsecure root adb
    •Voltage interface
    KTweaker app for kernel control
    KTweaker Widgets
    •Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
    •GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
    •exFAT for Touchwiz

    4fb98c4be2161.png

    Touchwiz Kitkat 4.4 VERSION:
    11.11.2014: http://goo.gl/IG2O5Q

    Always do the following AFTER installing the kernel:
    1. Clear cache
    2. Clear dalvik



    Post #2 will be reserved for change logs

    Post #3 will be reserved for MY Settings, Extras and FAQ's

    Sources can be found here:
    https://github.com/ktoonsez/KTNOTE4
    29
    4fb98c4be2161.png


    Change Log 03.02.2015
    1. Not sure if u guys have Lollipop yet but here is one based on 910F
    2. Lollipop test kernel version
    21
    Change Log 12.08.2014
    1. Added some Profiles to the KTweaker Shop, thanks to @zman2107 for helping out
    2. Some tweaks to ktoonservativeq
    3. Added Trinity Colors, thanks to @twistedumbrella for porting in the code
    4. Added Bluetooth Min Mhz control
    5. Added Music/Media Min Mhz control
    6. Added bfq scheduler

    Change Log 11.13.2014
    1. Rebase kernel source on N910F
    2. NOW Working on F and G models!!!!!!!!!!!!!!!
    3. Make ramdisk universal so its working on all Qualcomm variants
    4. Add Fast Charge from my S4/S5 code
    5. Increase bandwidth fro OC steps from @twistedumbrella
    6. Removed a butt load of dmesg spam

    Change Log 11.11.2014
    1. Initial release
    2. Based on Samsung source from N910T model
    3. Added multi compatibility for multiple models
    4. Removed root restrictions from kernel
    5. Made selinux permissive
    6. Added voltage control
    7. Added OC to 3072 Mhz
    8. Added KThermal
    9. Added KT Hotplug
    10. Lots more stuff to come!!!!!!!!!!!!!!!!!!!!!!!!
    11. Linaro -O3 compiled plus Make file opto's
    12. Added bfq scheduler
    13. There is lots of stuff in KTweaker not enabled yet so only use the stuff that is listed in this change log!!!
    20
    Everybody be sure to give @em0ney14 a big "THANKS" for the countless hours of testing the kernel while I spent countless hours doing the programming :D :D :D :D :D :D :D