[KERNEL][INTL][TW5.0][06/22/2015] KT-SGS6 - OE3 - KTweaker - Galaxy S6 Original Android Development

[KERNEL][INTL][TW5.0][06/22/2015] KT-SGS6 - OE3 - KTweaker - Galaxy S6 Original Android Development

Ktoonsez presents:
{
"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"
}

KT-SGS6 kernel features
•Must have a S6 model G920F and G920I and G920S and G920T and G920W8 and G925F and G925I and G925S and G925T and G925W8
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•Over Clocking
•Under Clocking
•KTweaker app for kernel control
•KTweaker Widgets
•KTmonitor app to watch your cpu cores current speed
Click to expand...
Click to collapse
KTweaker Shop and profile help, plus previous versions can be seen here (thanks to LuigiBull23):
http://forum.xda-developers.com/tmo...nel-kt-sgs6-builds-variants-ktweaker-t3107867
Touchwiz Lollipop 5.0 VERSION:
06.22.2015: http://bit.ly/1Jf6B2n
Click to expand...
Click to collapse
Sources can be found here:
https://github.com/ktoonsez/KTSGS6
What you can expect to get benchmark wise with a good CPU OC'd:

Go to my original thread to view Change logs:
http://forum.xda-developers.com/showpost.php?p=60180784&postcount=2

ktoonservative explained:
Any item with the word cycle in it refers to how many sampling_rate's have occured. A 22 ruffly equates to 1 second for a sampling_rate of 45000
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.
button_boost_screen_off_core_1 = 1
When this item is a 1, it will turn on the core #1 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_1 = 1
When this item is a 1, it will turn on the core #1 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_2 = 1
When this item is a 1, it will turn on the core #2 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_2 = 1
When this item is a 1, it will turn on the core #2 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_3 = 1
When this item is a 1, it will turn on the core #3 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_3 = 1
When this item is a 1, it will turn on the core #3 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_4 = 1
When this item is a 1, it will turn on the core #4 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_4 = 1
When this item is a 1, it will turn on the core #4 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_5 = 1
When this item is a 1, it will turn on the core #5 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_5 = 1
When this item is a 1, it will turn on the core #5 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_6 = 1
When this item is a 1, it will turn on the core #6 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_6 = 1
When this item is a 1, it will turn on the core #6 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_7 = 1
When this item is a 1, it will turn on the core #7 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_7 = 1
When this item is a 1, it will turn on the core #7 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
cpu_load_adder_at_max_gpu = 0
When set to higher than zero, this will add to the actual CPU load to create a perceived higher load when an app is using alot of GPU but not CPU.
cpu_load_adder_at_max_gpu_ignore_tb = 0
When set to 1, this will ignore cpu_load_adder_at_max_gpu during touch/button boost. When set to 0 cpu_load_adder_at_max_gpu will be used all the time.
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 = 40
A percentage of CPU utilization that needs to occur before the core #1 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 core #2 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_3 = 50
A percentage of CPU utilization that needs to occur before the core #3 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_4 = 55
A percentage of CPU utilization that needs to occur before the core #4 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_5 = 60
A percentage of CPU utilization that needs to occur before the core #5 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_6 = 65
A percentage of CPU utilization that needs to occur before the core #6 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_7 = 70
A percentage of CPU utilization that needs to occur before the core #7 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 core #1 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_2 = 40
A percentage of CPU utilization that needs to occur before the core #2 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_3 = 45
A percentage of CPU utilization that needs to occur before the core #3 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_4 = 50
A percentage of CPU utilization that needs to occur before the core #4 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_5 = 55
A percentage of CPU utilization that needs to occur before the core #5 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_6 = 60
A percentage of CPU utilization that needs to occur before the core #6 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_7 = 65
A percentage of CPU utilization that needs to occur before the core #7 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_hotplug_screen_off_core_1 = 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_hotplug_screen_on_core_1 = 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_hotplug_screen_off_core_2 = 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_hotplug_screen_on_core_2 = 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_hotplug_screen_off_core_3 = 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_hotplug_screen_on_core_3 = 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_hotplug_screen_off_core_4 = 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_hotplug_screen_on_core_4 = 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_hotplug_screen_off_core_5 = 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_hotplug_screen_on_core_5 = 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_hotplug_screen_off_core_6 = 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_hotplug_screen_on_core_6 = 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_hotplug_screen_off_core_7 = 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_hotplug_screen_on_core_7 = 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_changes_when_boosting = 0
If this value is 1, all CPU changes to all cores will be ignored while executing a touch/button boost. If 0 all cores will be allowed to scale and hotplug.
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_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.
touch_boost_cpu_cl0 = 1200000
The Mhz that you want the online CPU's to jump to when the screen is touched for the the LITTLE CPU (Cluster 0).
touch_boost_cpu_cl1 = 1600000
The Mhz that you want the online CPU's to jump to when the screen is touched for the the BIG CPU (Cluster 1).
touch_boost_core_1 = 1
When set to a 1, this option turns on the core #1 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_2 = 1
When set to a 1, this option turns on the core #2 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_3 = 0
When set to a 1, this option turns on the core #3 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_4 = 0
When set to a 1, this option turns on the core #4 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_5 = 0
When set to a 1, this option turns on the core #5 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_6 = 0
When set to a 1, this option turns on the core #6 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_7 = 0
When set to a 1, this option turns on the core #7 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_gpu = 424
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 = 55
A percentage of CPU utilization that needs to occur before the core #1 is put online while screen is OFF.
up_threshold_screen_off_hotplug_2 = 60
A percentage of CPU utilization that needs to occur before the core #2 is put online while screen is OFF.
up_threshold_screen_off_hotplug_3 = 65
A percentage of CPU utilization that needs to occur before the core #3 is put online while screen is OFF.
up_threshold_screen_off_hotplug_4 = 70
A percentage of CPU utilization that needs to occur before the core #4 is put online while screen is OFF.
up_threshold_screen_off_hotplug_5 = 75
A percentage of CPU utilization that needs to occur before the core #5 is put online while screen is OFF.
up_threshold_screen_off_hotplug_6 = 80
A percentage of CPU utilization that needs to occur before the core #6 is put online while screen is OFF.
up_threshold_screen_off_hotplug_7 = 85
A percentage of CPU utilization that needs to occur before the core #7 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 = 50
A percentage of CPU utilization that needs to occur before the core #1 is put online while screen is ON.
up_threshold_screen_on_hotplug_2 = 55
A percentage of CPU utilization that needs to occur before the core #2 is put online while screen is ON.
up_threshold_screen_on_hotplug_3 = 60
A percentage of CPU utilization that needs to occur before the core #3 is put online while screen is ON.
up_threshold_screen_on_hotplug_4 = 60
A percentage of CPU utilization that needs to occur before the core #4 is put online while screen is ON.
up_threshold_screen_on_hotplug_5 = 60
A percentage of CPU utilization that needs to occur before the core #5 is put online while screen is ON.
up_threshold_screen_on_hotplug_6 = 60
A percentage of CPU utilization that needs to occur before the core #6 is put online while screen is ON.
up_threshold_screen_on_hotplug_7 = 60
A percentage of CPU utilization that needs to occur before the core #7 is put online while screen is ON.

Touchwiz Lollipop 5.0 VERSION:
04.19.2015: http://bit.ly/1D1onyj
Click to expand...
Click to collapse
Change Log 04.19.2015
1. First build, things are just getting started
2. Min/Max will look weird upon open KTweaker the first time, just slide the Min and Max bars to what you want, this is only setup for the SMALL CPU.
3. So far you can only control the SMALL CPU which is the cpu that ranges from 400-1500Mhz
4. Control over Scheduler.
5. Control over governor for SMALL CPU.
6. Kernel is setup for SELInux Permissive
7. Lots of dmesg spam removed.
8. Dont bother setting other items in KTweaker just yet since things are just getting started.
9. As with all custom kernels since the S4, you may need to find "securestorage" line in build.prop and change from true to a false if you have trouble with wifi remembering your password after reboots.
10. If you have trouble with S-Health after installing custom kernels, Force Stop it and clear cache/data for the app, that will usually take care of it.
11. Please post a "dmesg" after running the kernel for 10-15 minutes and you have let the phone go into deep sleep at least once so I can remove more dmesg spam.
12. ENJOY the awesome!!!!!!!!!!!!!!!
13. All other G920 variants are welcome to try but G920F is the only one I have confirmation of so far.
14. No this will NOT work on any of the G925 variants since its a totally different device.

Awesome! One more reason for me to get the GS6 when it's available here.

Great and thanks for starting.
Sent from my SM-G920F

Sweet! A kernel already I was wondering about the max clock showing just 1.5 ghz instead of 2.1. It seems that way on stock too already. Surprisingly it actually seemed to hold a lower speed cap I set @ 1296 mhz. Usually stock is like screw you hippie, I do what I want. lol.
I'll give it a try in a day or two on my G920T Tmobile. I have to make a backup first.

Just flashed on my G920W8 and will confirm for those hesitant to flash that deep sleep is happening. Editing securestorage to false is needed to bring back wifi remembering on boot
Edit: No call audio >.>

mrapp said:
Just flashed on my G920W8 and will confirm for those hesitant to flash that deep sleep is happening. Editing securestorage to false is needed to bring back wifi remembering on boot
Edit: No call audio >.>
Click to expand...
Click to collapse
Try the one in the tmobile section and let me know.

ktoonsez said:
Try the one in the tmobile section and let me know.
Click to expand...
Click to collapse
Just realized you posted a T variant right before you posted. The T variant is tested and works perfectly with deep sleep and call audio on my W8

mrapp said:
Just realized you posted a T variant right before you posted. The T variant is tested and works perfectly with deep sleep and call audio on my W8
Click to expand...
Click to collapse
Awesome, I will add W8 to the OP as compatible.

Got any plans to make a sprint compatible version?

nflwideout86 said:
Got any plans to make a sprint compatible version?
Click to expand...
Click to collapse
Had 1 for 2 weeks now but you guys have no deep sleep with custom recovery or root or when you flash a kernel so I saw no point in it

ktoonsez said:
Had 1 for 2 weeks now but you guys have no deep sleep with custom recovery or root or when you flash a kernel so I saw no point in it
Click to expand...
Click to collapse
Hmm...we have deep sleep now since samsung finally released our stock firmware......? Personally i have trwp with deep sleep.

nflwideout86 said:
Hmm...we have deep sleep now since samsung finally released our stock firmware......? Personally i have trwp with deep sleep.
Click to expand...
Click to collapse
You also need root or KTweaker wont work. Ill PM u a link, your welcome to try.

ktoonsez said:
You also need root or KTweaker wont work. Ill PM u a link, your welcome to try.
Click to expand...
Click to collapse
Awesome man i'll try it out. I rooted with the tmo auto root and it seems to be working so far, all my other root apps work as they should
---------- Post added at 11:00 PM ---------- Previous post was at 10:12 PM ----------
ktoonsez said:
You also need root or KTweaker wont work. Ill PM u a link, your welcome to try.
Click to expand...
Click to collapse
So i just tested it out and everything seems good, the device deep sleeps just fine. :good:

Hi @ktoonsez congrats on your first S6 release!
Here you have an better dmesg log of an 10 minute run including deep sleep.

@ktoonsez thanks a lot, I'll try soon.
There's a small error in the op, it says "KT-SGS5 kernel features" instead of KT-SGS6
Good luck for the development

Question what is the difference between this kernel and the one you posted yesterday for the 920f ?

edgarf28 said:
Hi @ktoonsez congrats on your first S6 release!
Here you have an better dmesg log of an 10 minute run including deep sleep.
Click to expand...
Click to collapse
How did you get that log? KTweaker closes itself instantly for me?

Related

[Overclocking] Boot Menu CPU Settings

I found this in another site (originally written in Russian by user fibik @ se900.ru):
(http://translate.google.com/transla...//www.se900.ru/forum/index.php?showtopic=9180)
Acceleration
Status: [Enable] - status of overclocking is enabled or disabled
Load all modules: [Enable] - load modules for overclocking
Scaling: [Ondemand] - automatic CPU frequency scaling
Clk1: [300] - the frequency of the first stage of the frequency in MHz
Clk2: [600] - the frequency of the second stage of the frequency in MHz
Clk3: [800] - the frequency of the third stage of the frequency in MHz
Clk4: [1100] - the frequency of the fourth stage of the frequency in MHz, works only on official firmware firmware 2.3 and its modes
Vsel1: [20] - voltage at the first stage of frequency
Vsel2: [32] - voltage at the second stage of frequency
Vsel3: [42] - voltage at the third level of frequency
Vsel4: [65] - voltage at the fourth stage of the frequency
con_up_threshold: [80] - system load in% above which increases the CPU frequency? Bus?
con_down_threshold: [20] - system load in% above which lowers CPU speed? Bus?
con_freq_step: [5] - frequency step?
con_sampling_rate: [160 000] - interval (in milliseconds) between polls of the state of the system. In fact, the intervals between shifts the frequency of the processor? Times in 160 seconds?
int_min_sampling_rate: [50 000] - the minimum interval (in milliseconds) between polls of the state of the system. In fact, the intervals between shifts the frequency of the processor? Every 50 seconds?
ond_up_threshold: [86] - CPU in% above which increases the CPU frequency.
ond_sampling_rate: [50 000] - the second one? interval (in milliseconds) between polls of the state of the system. In fact, the intervals between shifts the frequency of the processor? Every 50 seconds?
smt_min_cpu_load: [40] - CPU in% above which decreases the frequency of the processor
smt_max_cpu_load: [85] - CPU in% above which increases the CPU frequency
smt_awake_min_freq: [30 000] - The minimum frequency of waking up?
smt_sleep_max_freq: [30 000] - CPU frequency during sleep?
smt_up_min_freq: [1200000] - How much to increase the frequency at a time?
smt_wakeup_freq: [1200000] - Frequency of waking up. It is important to not lose calls.
smt_ramp_up_step: [250 000] - on how to increase the frequency at a time?
[Set defalut (* req reboot / don 't save!!)] - Reset all settings to
[Save] - save the settings
con_ = conservative
ond_ = ondemand
int_ = interactive
smt_ = smartass (?)
That is, this is all profile names, one from which to choose.
sampling_rate - in Hertz likely, but not in milliseconds
awake_min_freq - the minimum frequency of not sleeping
Click to expand...
Click to collapse
Any volunteers confirm or even to play with the settings?
This could be useful to monitor the frequencies: https://market.android.com/details?id=com.bvalosek.cpuspy

very helpful ..Thx

i use setvsel at 32-300,42-600,52-1000 and its safe and no FC

Can any one suggest, to how to tweak other boot cpu setting other than clk and vsel.

Whitch option is the frequence on a call?

[Kernel][AOSP][2.02 | November 2nd] Plasma kernel

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I. Thanks!
.
Disclaimer: I take no responsibility for any damage that might occur to your device. You proceed strictly at your own risk. This is a work in progress.Thank you for your interest in Plasma kernel, I hope you enjoy it. I've poured hundreds upon hundreds of hours of work into putting together a kernel that best showcases our hardware. Plasma kernel would not be possible without super-smart people like AndreiLux, DerTeufel, temasek, googyanas, faux123, and the regular contributors to the official cm kernel repositories. Please donate to them to support their hard work!.
II. Features
CPU frequency range: 100MHz to 2.16GHz
ZZMoove, PegasusQ, performance (with support for multiple cores), and LulzactiveQ CPU governors
Zen, noop, deadline, row, cfq, sio, vr schedulers
Experimental Wolfson AND Voodoo Sound support (choose one or the other on the Audio tab of STweaks, then REBOOT!)
CPU voltage control
Linux 3.0.101
AndreiLux: Screen color calibration with mdnie-control
GPU over/underclock and over/undervolt
Control the frequency and voltage of all 5 GPU steps
Support for GPU clocks from 54MHz to beyond 800MHz
Control GPU governor sampling rate
Built with 4.8 toolchain
Built with -O3 and other optimizations
Extra panel brightness (<299)
Faux123: Dynamic fsync control (v1.2)
AndreiLux: Charging control
Support for STweaks
Control screen refresh rate (can be reduced to save battery)
AndreiLux: Memory/internal voltage control interface
AndreiLux: Adaptive Body Bias (ABB) control
AndreiLux: Digital brightness control/reduction (better than ScreenFilter)
LED control (with some color mixing adjustments by me)
Touchwake support, including touchkeys (enable in Screen tab of STweaks)
Multi-touch kernel-based gesture engine
Proportional Rate Reduction for TCP
Joe's RCU
Temasek: Frandom module (enable on the Memory/Internal tab of STweaks and REBOOT!)
S-Pen settings on the S-PEN tab of STweaks
zCache
Support for 4x parallel "Turbo ZRAM" (settings are on the "I/O / RAM" tab of STweaks)
UKSM
Enhanced Touchwake/Slide2Wake functionality
Arc-swipes to turn your phone on with one hand (Screen tab of STweaks)
Long-tap-off to turn your device off with one hand (Screen tab of STweaks)
Power off gesture: tap the top of the screen and a touchkey at the same time to trigger suspend
Change your power manager (PM) CPU lock frequency
Press the home button 4 times to toggle the screen negative
Press the home buttom 3 times as fast as you can to toggle the screen into nightmode (red)
exFAT support
For more, take a look at the commits
.
III. What's NewDon't forget to check out what was new in 2.0b7 and 2.0b12!
[ZRAM Total Disk Size]: By default ZRAM is setup as four (4x) swaps operating in parallel at equal priorities. Set this to the TOTAL amount of RAM you wish to dedicate to ZRAM, and STweaks will automatically divide it evenly by four.
[UKSM Enable]: Enable the UKSM daemon that will continuously scan memory for duplicate data.
[UKSM Daemon Sampling Rate]: How often the daemon checks for duplicate data.
[UKSM CPU Usage Limit]: How much system load (CPU usage) the daemon will use.
[Long-tap-off Always On]: Found in its own section under the Touchwake section. When enabled Longtapoff will always work, regardless of how you woke your device. Takes effect immediately.
[Many ZZMoove settings]: Many ZZMoove settings on the newly created "ZZMoove Scaling" and "ZZMoove Hotplug" tabs. Descriptions coming soon.
.
IV. Download / Donate
Support the development of Plasma kernel by DONATING if you find it useful!
AOSP 4.3.x only!
Plasma kernel v2.02 for AT&T Note 2 (i317)
Plasma Gesture Pack
Support the development of Plasma kernel by DONATING if you find it useful!
.
V. Changelog
v2.02 (November 2nd, 2013)
Tracked audio/media skipping bug to disabled loggers (thanks pappschlumpf!) By default logging is now enabled. While you can still disable it, it will always be reset upon reboot.
Changes to write-back caching (thanks temasek)
Support for switching touchkey backlight driver from ROM/kernel (bottom of Screen tab in STweaks) (thanks Yank555-lu)
Some bug fixes for Slide2Wake
i317: Hopefully fixed the weird root issues
.
VI. Archived Changelogs
2013-10-29 | v2.00
Linux 3.0.101 (thanks temasek)
Hopeful bugfixes for untouchable screen, and taps on top triggering suspend
Should you encounter a problem like that, cycling on and off (power button) should now reset any state variables
Fix FC issues. Works with more ROMs, including the latest AOSP nightlies
Allow pm_idx_freq to be set as high as 1600 MHz, theoretically could slightly speed up waking from deep sleep. Set on "Plasma Tuneables" tab of STweaks
Added several new tuneable ideas to zzmoove
Added "ZZMoove Scaling" and "ZZMoove Hotplug" tabs to STweaks. The descriptions are still a work in progress
Moved mDNIe controls to their own "Color" tab
Greatly enhanced the longpressoff feature's reliability and ease of use (by upgrading to scheduled_work)
Slide2Wake and arc swipes now trigger CPU and memory frequency locks to speed up waking
Slide2Wake and arc swipes no longer accidentally send input in the milliseconds after the screen comes on, but before you finished your gesture
Added option to Screen tab of STweaks to enable Longtapoff always, regardless of how the device woken
Expanded the trigger areas for slide2wake and arc swipes
ZRAM/swap is working and compatible with "Turbo ZRAM" (4x parallel ZRAM swaps for quad core devices) (thanks googyanas)
ZRAM settings in STweaks now allows you to set one total size of RAM that will be divided into 4x ZRAM swaps. Setting to 0 disables all swaps. Changes are applied instantly. No need for any other ZRAM/swap apps or init.d scripts.
UKSM (Ultra KSM (Kernel Samepage Merging)) enabled, with settings on the "I/O / RAM" tab of STweaks. Mostly just a novelty, but what it does is continuously checks RAM for duplicate pages to save space
zCache enabled and always running
Cleancache enabled
Frontswap enabled
Enabled LOWMEM_CHECK (thanks googyanas)
Enabled SPEEDUP_KEYRESUME as discussed in temasek's thread (Placebo effect? Maybe. Better ask Brian Molko. A cookie for you if you understand that reference) (thanks googyanas)
Added my own wake-speed ideas (2-second max-CPU-speed lock, and 2-second max-bus/RAM-speed lock on KEY_POWER press)
Permanently fixed (hopefully) the laggy, skippy, media bug
Toggle negative screen mode by taping the home button 4 times quickly (but NOT as fast as you can) (based on a commit by gokhanmoral)
Toggle nightmode (red) screen mode by pressing the home button 3 times VERY quickly (pretty much as fast as you can) This is purposely designed to be a dim red, as searing bright 255 red isn't particularly easy on your eyes in the dark. Fun fact: this (and the negative one described above) are functional even during boot...triple tap to see your bootscreen turn red
CPUFreq bug fixes/commits (thanks DerTeufel)
Permanent TRIM (thanks googyanas)
Added shell scripts to quickly and easily see statistics with as little typing as possible. Open a command prompt on your device, type "su" and press enter to ascend to root. Now you can type "szc" and press enter to see zCache statistics (szc = show zcache). Or type "ssw" to see swapfile/zRAM statistics (ssw = show swap). Note: Some statistics don't fully populate until a few minutes after boot
Experimental: Set ZZMoove governor for battery savings by obtaining a root shell as described above, then typing "zzb" and pressing enter (zzb = zzmove battery). Does not reapply after reboot.
Compiler optimizations

.
VII. SourceSource for Plasma kernel can be found on my github.
XDA:DevDB Information
Plasma kernel, a Kernel for the AT&T Samsung Galaxy Note II
Contributors
ffolkes
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 2.02
Stable Release Date: 2013-11-02
Created 2013-10-29
Last Updated 2013-11-02

Reserved
FAQ:
Q: I have no earpiece volume!
Be sure to choose Voodoo Sound or Sound Controls on the Audio tab of STweaks, then reboot.Q: I can stably run this kernel. How can I use the screen-off settings so I can save battery?
You will have to intentionally crash your system to find your lowest value, and should definitely make a nandroid first. Then be sure to turn off dynamic fsync on the bottom of the I/O tab of STweaks, as this being enabled could cause data loss from a crash. When you are done with that, the first thing will be to lower the PM Lock Frequency. Try 600MHz, press Apply, then put your device to sleep, give it a few seconds, and see if it wakes. Be sure it's going into deep sleep! If it wakes up instantly, it wasn't in deep sleep. After booting, things like mediascanner can take minutes to finish and release their partial wakelocks. If you are sure it went into deep sleep, repeat with a lower frequency until you cannot wake. Pull the battery and reboot. Once it boots up, go into STweaks and set PM Lock Frequency to the last stable frequency. You must do this before the screen goes off, or else it'll crash again when it enters deep sleep!
Now, once you are sure of your stable PM frequency, move on to the next step. Set CPU Screen-Off Max Frequency to 200MHz. Use your device for a few minutes or hours or whatever. If you find music skips too much, or calls are slow to wake up the phone, set this to 300MHz, but now be prepared for a possible SOD if your device cannot handle scaling that low. If you experience one, leave this setting at 300MHz, and enable "Keep sleep max frequency fixed" and set CPU Screen-Off Fixed Max Frequency to 200MHz. If your phone was slow to wake at 200MHz before, try setting this to 300MHz.
Err, a bit of a vestigial tail here...don't forget to set Screen-Off Frequency For Responsiveness (it's higher up in the PegasusQ Scaling tab) to whatever your lowest screen-off frequency is. It isn't needed anymore and I should have taken it out probably. Like its waking counterpart, it is a threshold below which aggressive upscaling is used. Basically, it's the frequency the CPU will want to hover at, in this case, while the screen is off.Q: Explain the PegasusQ screen-off settings.
CPU Screen-Off Max Frequency - This becomes the effective policy max as soon as you press the power button. Setting this too low may cause slow waking, or choppy music. Ideally this is just like normally setting the max policy; i.e. the governor will try to get frequencies as low as possible without going over this. This means if you get skips in your music at 200MHz, you can set this to 300MHz and the governor will be able to grab that extra power if it needs it. The problem is, some devices get finicky when they're bouncing around between sub-PM Lock frequencies and will crash. That's where the Fixed Sleep Frequency setting comes in. Read on.
Up Threshold While Screen-Off - This becomes the effective Up Threshold value as soon as you press the power button. Setting this higher will make the CPU more reluctant to scale higher (go faster).
PM Lock Frequency - This typically hardcoded value normally overrides the governor to throttle the CPU to 800MHz every time the system itself is unsuspended. This means it happens thousands of times a day, and can significantly add up after a few hours. I found different devices could handle different frequencies, so I made this is adjustable and added an interface to lulzactiveq and zzmoove. 500MHz works very stably for me.
After Boot Delay - Gives your device a grace period after booting during which none of the screen-off policies will be enforced so your start up tasks can be completed quickly.
Enable Fixed Sleep Frequency - This is where things get sorta confusing. If your device can't scale while sleeping, most likely it will be able to tolerate just sticking to one low frequency. But this has a downside...you disable the scaling logic of the governor, so you either have to suffer degraded screen-off performance (skips in your music) with a battery-saving frequency, or set this higher, but then that means you'll be pegging this higher frequency now even though you just needed it occasionally. But yay, I had an idea to put a one-way toggle in there. Read on.
CPU Screen-Off Fixed Max Sleep Frequency - So here's the thing. All devices can handle low scaling just fine, as long the screen is merely off (e.g. listening to music, etc). Once the system falls into deep sleep, that's when stability issues arise. So I had an idea... When you play music, you usually interact with the screen then turn it off, but it never actually goes into deep sleep until it's done playing. So I made it so the above Screen-Off Max Frequency will be used, including scaling, until deep sleep is called for. Then from that point on it will become fixed to this setting's frequency until you turn the screen back on, then the toggle gets reset.
v1.60 Release Notes
Control your panel refresh frequency - This is inspired by and based on AndreiLux's commits last year. Samsung includes a driver called "lcdfreq" that allows for scaling of panel refresh frequency to save power. It toggles between two states: limited and unlimited. Not all devices actively use this feature in stock builds, but it is possible to enable nonetheless. When in limited mode the panel's refresh rate is reduced from 60Hz (58 actual) to 40Hz (41 actual). I went a step further and made it so the limited mode's panel divider can be set manually (25, 27, 29, 31, 34, 37, 41, 45, 50, 60 fps). I also made it so the limited mode can now be forced, effectively allowing you to adjust the default refresh rate of your panel to save battery. Not everyone needs/wants 60fps. How much battery will this save? I don't know yet, but if you want to find out, the option is on the Screen tab of STweaks. Be sure to check the force checkbox. Very low rates will introduce flickering to some eyes (remember, this is a refresh rate being adjusted, not just fps).
Lcdfreq in PegasusQ - Note: This is irrelevant if you have decided to lock your refresh rate as described above. AndreiLux implemented this last year, and I modified it a bit and added more tunables. When enabled, PegasusQ will try to control the state of lcdfreq based on CPU load. Some of you may know AndreiLux abandoned this due to problems with flickering, but I have taken a different approach. His goal was to provide 60Hz as quickly as possible, which ended up frequently alternating between the two states. I'm aiming for the opposite - to stick with limited as long as possible and only boost it during heavy use (like a game). When bounced around between limited and unlimited too rapidly, there can be visible flickering and tearing, and different frequencies seem to slightly affect the color balance, which makes it even more noticeable. Quite possibly why Samsung doesn't use this on Note 2's.
lcdfreq_kick_in_down_delay - When PegasusQ decides it wants to call for the panel to be kicked down (into limited mode) it will have to ask this many times before actually doing it.
lcdfreq_kick_in_up_delay - When PegasusQ decides it wants to call for the panel to be boosted (into unlimited mode) it will have to ask this many times before actually doing it.
lcdfreq_kick_in_freq - Before PegasusQ will consider limiting the refresh rate, the CPU must be running at this frequency or below.
Boost lcdfreq on touch - Immediately boosts to the unlimited state, regardless of what PegasusQ calls for. A commit by AndreiLux. At some point I may add to this to make it time based (i.e. hold the boost for x amount of seconds after a touch).
Control the touchy backlight - On the Screen tab of STweaks. For ROMs that don't provide this support natively, otherwise it may be unreliable.
v1.65 Release Notes
Control your GPU - Over/underclock your GPU! Over/undervolt your GPU, too! Settings explained on the GPU tab of STweaks. Support for frequency, voltage, up/down threshold and GPU governor sampling rate.
Lock/Limit your GPU - You can lock your GPU to a specific step, or limit it to a definable maximum number of steps (e.g. 2 or 3)
Control S-Pen booster - Control/disable the S-Pen CPU booster. Stock is 800MHz, but I find that overkill.
S-Pen X,Y Axis Offset - For some reason Wacom sets this to like 30,30 depending on handedness. I have no idea why, I prefer 0,0. For most users I recommend checking the box on the S-Pen tab in STweaks and leaving the sliders at 0,0.
S-Pen Box Filter - Depending upon what you use your S-Pen for, this makes it much easier to draw shapes, but harder to do finer things, like writing. Think of it as "snap to grid".
Gestures! - Be sure to scroll down to the FAQ section to read how to use them.
Q: How do gestures work?
Flash the gesture pack and reboot. This places the action and handler scripts in /etc/init.d to be run on boot. The available gestures are listed on the Gestures tab of STweaks. You may customize the scripts, but be warned that flashing the zip again will overwrite them.
Some gestures will require you to hold down a touchkey while performing them. Be sure to have a Touchkey Modifier Delay set in STweaks (Screen tab). 100-200ms works well. Now any time you touch and hold a touchkey and then touch the screen within the delay you just set, you will activate gesture-only mode, during which the touchscreen will no longer send touch events to the operating system, only the gesture engine. This means you won't get any bleed through of gesture draws into the foreground app. It's also a safety of sorts, to prevent critical gestures from being accidentally triggered. The downside is, you can't have your cake and eat it...well, not without some delay at least. If the touchkey modifier was simply piggybacked onto the touchkey driver that would be nice, but it would also mean every time you used it, it would also report the touchkey (Menu/Back) event. Or, if you blocked it always, well then obviously your touchkeys wouldn't work anymore. So a compromise is using a very short delay, and after that delay is up, the touchkey driver checks to see if the screen has been touched and the touchkey is still down. If it has been touched, then gesture-only mode is set in the touchscreen driver until all fingers are up. If the screen has NOT been touched after the delay, then the touchkey driver assumes it's just a normal touchkey press and reports it like normal. This may seem like an insanely small delay, but it's meant for you to touch the touchkey and start drawing with another finger *simultaneously*.
tl;dr: Flash the gesture pack, go to the Screen tab and set the Touchkey Modifier Delay to 150ms or so, then apply it. Now test it. First swipe from near the bottom-left corner, up towards the middle-right side. Nothing should happen. Now repeat, this time putting a finger down on the touchkey and holding, while *at the same time* starting to drawing this simple gesture. Aim to have both fingertips touch down at the same time. If it goes well, the virtual power key will be pressed and it will go into suspend. If you have trouble, increase the delay until you get more practice. Eventually you'll be able to do this gesture one-handed by touching the touchkey with the side of your thumb, and sliding/flicking your index or middle finger outward in an arc..
Useful Apps (no affiliation):
BetterBatteryStats XDA / Play
Awesome tool that lets you see both kernel and partial wakelocks, as well as the average percent battery drain.CPU Spy XDA / Play
Provides a GUI to CPU time-in-state data.Micro CPU Monitor Play
One of my favorite apps ever, this puts a very small 1px bar across the top of the screen for each core. It can be set to come from left or right, the background can be set transparent, and the bar thickness and color are adjustable. Very useful for quickly (and discretely) noticing abnormally high CPU usage.top Play
Provides a GUI to the linux command 'top'. Provides a very reliable way to see what processes are using the most CPU time.System Monitor Play
This app makes monitoring CPU history easy, and makes it especially easy to see the effects of hotplugging tweaks because of the way it clearly displays the state of each core..
Notes:
How to use the mdnie-control interface:
AndreiLux and Slimer777 have gone to great lengths to create an extremely accurate internal color profile using a spectrophotometer. The color accuracy is terrific. Most computers and tech use a very unnaturally cool color temperature (blue tint to white), so many people are taken by surprise when they see how yellow reality actually is. You need some time to get used to the new colors, but if you are still not pleased with the result, AndreiLux has setup MANY options for you to tweak in STweaks. Personally, I recommend increasing the chroma saturation weight.
Settings can easily be configured in the STweak app now. Download it from the Play Store.
A bit about body bias:
To summarize this feature: When we traditionally change voltages (SetCPU, Performance Control, etc), we are changing the gate voltage of the transistors. This can be a difficult concept to grasp, so here's a super-simple analogy to help: Imagine a light switch instead of a transistor. You reach your finger out to flick it. The force your finger applies would be analogous to the gate voltage. However transistors also have a body voltage, which can be thought of as the resistance behind the switch. By applying a positive difference between the gate and body, (which usually, but not always, equates to reducing the body voltage) we can make the proverbial switch "looser" so it's easier to flip, but now that it's looser, it's starting to leak a small amount of current as a result. So why would we want to do this if it will be leaking more? Because now that the switch is looser, we'll hopefully need less gate voltage (aka finger pressure in the analogy) which would save more power than was lost with that leakage. Or, for someone overclocking instead of undervolting, the "loose" switch will be easier to flip, and you may achieve an overclock not possible by merely ramping up the gate voltage (brute force) in your voltage control app of choice. Basically like the old saying "two steps forward, one step back" - we get something good, but have to sacrifice a little power lost through leakage. But how about the opposite scenario? What if in the analogy you have a really strong finger? Then you're leaking power for no reason because you don't need a "loose" switch. So, we can take advantage of that fitness and tighten it up by applying a negative body bias (also called a Reverse Body Bias, or RBB). This will make the transistor harder to switch, but plug up the leak and therefore increase power efficiency.
Ok, so why does all this exist? Why not just have an enormous negative bias (RBB) from the factory and save all that power lost through leakage? Because not all chips are equal, and not all transistors on the same chip are even equal. Temperature, manufacturing techniques, a few atoms of contamination, etc can make the chip less "fit" and unable to switch as easily as others. So how do they help these weakling transistors from getting the entire chip sent to the factory garbage can? Well, on one hand the gate voltage can be increased, but that is a last resort since it would waste too much power. Before it comes to that, they get a crutch in the form of a positive body bias (also called a Forward Body Bias, or FBB), which hopefully you'll remember was the subject of the first scenario above. And remember what that does? It makes them easier to switch, but at the cost of slightly decreased power efficiency. This offers better power savings when compared to increasing the gate voltage.
Samsung knows all this, and bins their chips according the ASV level, which can be thought of as the "quality" of the chip. The higher the ASV number, the better the chip, and the less power it needs to do its job. At the factory they mix increased gate voltages with varying body voltages to end up with a table of stock body biases. Long story short, this is how they deal with less-than-perfect chips. It's a lottery for the buyer. But since their values aren't tailored to your chip - the hope is that maybe you can scrape by with a bit less power than Samsung thought a chip of that grade could. So what AndreiLux has done is implemented new scaling logic/control code that lets you adjust the body voltage, and thus the body bias. Thanks to him, we now have another tool to help us squeeze a little bit more power out of our chips.
Calculating your body bias is incredibly simple: bodybias = gatevoltage - bodyvoltage. If you know the voltage of a given frequency, you can calculate your body bias by taking the gate voltage (what it says for that frequency in your usual voltage adjustment app) and then subtracting the value of the slice that corresponds to the range the example frequency was in on the ABB tab of STweaks. This can get tricky, because people forget that "body bias" is a difference between two values. If you start off with a stock negative body bias, that is to say that your body voltage is higher than your gate voltage, increasing your body voltage will actually be increasing your bias and you'll be needlessly wasting more power. However if you start off with a positive stock body bias, adding to the body voltage will actually be decreasing your bias since it will be bringing you closer to the gate voltage.

Mine...
Sent from m

Gonna give this one a try, hopefully it plays nice with Trickster Mod.
Thanks dev.

Will this work with international model? Looks very awesome!

Had it intalled for almost 10 minutes but I already noticed that there is almost NO LAG when waking the screen. Awesome!!!

jibust said:
Had it intalled for almost 10 minutes but I already noticed that there is NO LAG when waking the screen. Awesome!!!
Click to expand...
Click to collapse
Are you getting good deep sleep? The only time the Note 2 screen wakes quickly is if it is not deep sleeping, at least from my personal experience.

BigBake88 said:
Are you getting good deep sleep? The only time the Note 2 screen wakes quickly is if it is not deep sleeping, at least from my personal experience.
Click to expand...
Click to collapse
Like a baby,
What I have noticed is an increase in the battery drain. From the screen shot, you will notice it is not actually scaling, it is either in deep sleep or at 1600 when using pegasusq. I haven't touched most of the settings so I may need to tune it a little more.
Changed to zzmove to see how it performs.

jibust said:
Like a baby,
What I have noticed is an increase in the battery drain. From the screen shot, you will notice it is not actually scaling, it is either in deep sleep or at 1600 when using pegasusq. I haven't touched most of the settings so I may need to tune it a little more.
Changed to zzmove to see how it performs.
Click to expand...
Click to collapse
I don't know why this is happening at the moment, but I do see what's causing this. In PegasusQ, up_threshold is getting set to 0. By default it should be 82. Use SetCPU or something to change the up_threshold to 82 while the PegasusQ governor is active. Or save 82 to "/sys/devices/system/cpu/cpufreq/pegasusq/up_threshold" via your favorite file manager.

ffolkes said:
I don't know why this is happening at the moment, but I do see what's causing this. In PegasusQ, up_threshold is getting set to 0. By default it should be 82. Use SetCPU or something to change the up_threshold to 82 while the PegasusQ governor is active. Or save 82 to "/sys/devices/system/cpu/cpufreq/pegasusq/up_threshold" via your favorite file manager.
Click to expand...
Click to collapse
Done, I will report back in a while. Thanks :good:

that was a great read
looking to try your kernel soon

I ran this on pacman and carbon today, losing superuser / root on both occasions.
Good work, though!
Sent from my GT-N7105 using Tapatalk 4

SwimDrewid said:
I ran this on pacman and carbon today, losing superuser / root on both occasions.
Good work, though!
Sent from my GT-N7105 using Tapatalk 4
Click to expand...
Click to collapse
No issues with root on AOKP. I flashed the supersu zip after flashing the kernel

jibust said:
No issues with root on AOKP. I flashed the supersu zip after flashing the kernel
Click to expand...
Click to collapse
Ah. Mind sharing that zip?
Sent from my GT-N7105 using Tapatalk 4
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
SwimDrewid said:
Ah. Mind sharing that zip?
Sent from my GT-N7105 using Tapatalk 4
Click to expand...
Click to collapse
Physician, heal thyself
http://forum.xda-developers.com/showthread.php?t=1538053
Will try and report back
Sent from my GT-N7105 using Tapatalk 4

SwimDrewid said:
Ah. Mind sharing that zip?
Sent from my GT-N7105 using Tapatalk 4
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
Physician, heal thyself
http://forum.xda-developers.com/showthread.php?t=1538053
Will try and report back
Sent from my GT-N7105 using Tapatalk 4
Click to expand...
Click to collapse
LOL, beat me to it.

jibust said:
LOL, beat me to it.
Click to expand...
Click to collapse
Gave you a thanks anyway
Zip did the trick on carbon, thanks!
Sent from my GT-N7105 using Tapatalk 4

SwimDrewid said:
Gave you a thanks anyway
Zip did the trick on carbon, thanks!
Sent from my GT-N7105 using Tapatalk 4
Click to expand...
Click to collapse
No problem, I actually always flash it. I prefer SuperSU

Amazing read ...and an amazing kernel I'm sure..
I've just downloaded ..and will flash the build shortly..
Wow...I'm baffled by the overwhelming amount of tweaks and customizations this kernel contains...
It's a true marvel ...and one I'm thoroughly going to enjoy I'm sure...
Many thanks to you..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

gregsarg said:
Amazing read ...and an amazing kernel I'm sure..
I've just downloaded ..and will flash the build shortly..
Wow...I'm baffled by the overwhelming amount of tweaks and customizations this kernel contains...
It's a true marvel ...and one I'm thoroughly going to enjoy I'm sure...
Many thanks to you..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check out the STweaks apps, it's a fuc**ng encyclopedia.
---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------
ffolkes said:
I don't know why this is happening at the moment, but I do see what's causing this. In PegasusQ, up_threshold is getting set to 0. By default it should be 82. Use SetCPU or something to change the up_threshold to 82 while the PegasusQ governor is active. Or save 82 to "/sys/devices/system/cpu/cpufreq/pegasusq/up_threshold" via your favorite file manager.
Click to expand...
Click to collapse
Wanted to let you know that it seems the up_threshold for zzmove is 82 instead of the default 70. Could there be a mix up between the zzmove and pegasusq up_threshold values?

jibust said:
Check out the STweaks apps....
Click to expand...
Click to collapse
Uh....
It's gonna take me a week to figure out how to run this beast ....(headache starts now)...LOL
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

CPU Frequency (Text) Widget : error calculation and other

Hii to All for first...
Nexus 5
I created a widget with the CPU frequency:
- The widget always displays the maximum frequency: that is, in 2265;
- The value is not updated
- By measuring programs of the CPU the true value is lower than that displayed by the widget.
How can you have a true value?

Jazz__75 said:
Hii to All for first...
Nexus 5
I created a widget with the CPU frequency:
- The widget always displays the maximum frequency: that is, in 2265;
- The value is not updated
- By measuring programs of the CPU the true value is lower than that displayed by the widget.
How can you have a true value?
Click to expand...
Click to collapse
Just to clear up a possible source of error: which variable did you use to output the CPU frequency? There are three available in Zooper: #SCPUMIN# = Minimum Frequency, #SCPUMAX# = Maximum Frequency, #SCPUCUR# = Current Frequency.
Also keep in mind that Zooper only updates its widget data every few seconds, so there might be always be a little lag between the real and the displayed data.

I only use #SCPUCUR# = Current Frequency
Upsate are set to less possible!!

[KERNEL][SPR][TW5.0][05/28/2015] KT-SGS6 - OE3 - KTweaker

Ktoonsez presents:
{
"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"
}

KT-SGS6 kernel features
•Must have a S6 model G920P
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•Over Clocking
•Under Clocking
•KTweaker app for kernel control
•KTweaker Widgets
•KTmonitor app to watch your cpu cores current speed
Click to expand...
Click to collapse
Touchwiz Lollipop 5.0 VERSION:
05.28.2015: http://bit.ly/1HVHhuV
Click to expand...
Click to collapse
Sources can be found here:
https://github.com/ktoonsez/KTSGS6
What you can expect to get benchmark wise with a good CPU OC'd:

Go to my original thread to view Change logs:
http://forum.xda-developers.com/showpost.php?p=60180784&postcount=2

Hell yeah

thank you ktoon:good::good::good:

It's on!!! thanks ktoonsez ✌

Nice KT, good to see you here brotha. Did you pick up an S6,or are you just building blind?

reverepats said:
Nice KT, good to see you here brotha. Did you pick up an S6,or are you just building blind?
Click to expand...
Click to collapse
Blind building. Still no announcement of a Verizon version yet. They r soooooooo slow

ktoonsez said:
Blind building. Still no announcement of a Verizon version yet. They r soooooooo slow
Click to expand...
Click to collapse
Ahh i see. Wait, Verizon does have the S6 available for purchase yet?

reverepats said:
Ahh i see. Wait, Verizon does have the S6 available for purchase yet?
Click to expand...
Click to collapse
No dev version and barely anyone with the Kmart version has one yet.

Thanks for this. Im rooted and ready!

reverepats said:
Nice KT, good to see you here brotha. Did you pick up an S6,or are you just building blind?
Click to expand...
Click to collapse
Nice to see you here, like your themes.

Firmware OCF
ktoonsez said:
Ktoonsez presents:

Sources can be found here:
https://github.com/ktoonsez/KTSGS6
Click to expand...
Click to collapse
Does this "version" work with lollipop 5.0.2?
Thanks.

Yes I've been running since posted.

Touchwiz Lollipop 5.0 VERSION:
04.29.2015: http://bit.ly/1DCZND4
Click to expand...
Click to collapse
Make sure you delete the KTweaker folder on your sdcard before flashing the new one!!!!!!!!!!!
Change Log 04.29.2015
1. Add voltage control for little and BIG CPU's. Thanks to AndreiLux for pointing me to the right files.
2. Added ondemand and conservative governor.
3. Added CPU Min/Max control for BIG CPU
4. Added ability to tweak governor adjustments.
5. GPU governor selection is working, dont mess with Min/Max yet.

ktoonsez said:
Make sure you delete the KTweaker folder on your sdcard before flashing the new one!!!!!!!!!!!
Change Log 04.29.2015
1. Add voltage control for little and BIG CPU's. Thanks to AndreiLux for pointing me to the right files.
2. Added ondemand and conservative governor.
3. Added CPU Min/Max control for BIG CPU
4. Added ability to tweak governor adjustments.
5. GPU governor selection is working, dont mess with Min/Max yet.
Click to expand...
Click to collapse
Ktoonsez just reporting that I flashed the new version and it hangs in the sprint spark screen. Ps I deleted the KTweaker folder after flashing the kernel

DR0IDMANIAC said:
Ktoonsez just reporting that I flashed the new version and it hangs in the sprint spark screen. Ps I deleted the KTweaker folder after flashing the kernel
Click to expand...
Click to collapse
Works on all my testers, sounds like u might have a bad download or running a ROM that needs its own kernel maybe

ktoonsez said:
Works on all my testers, sounds like u might have a bad download or running a ROM that needs its own kernel maybe
Click to expand...
Click to collapse
Ok, will try again, thanks

Works fine for me.

Working great now, was a bad download I think

[KERNEL][TMO][TW5.0][06/22/2015] KT-SGS6E - OE3 - KTweaker

Ktoonsez presents:
{
"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"
}

KT-SGS6 kernel features
•Must have a S6 model G920F and G920I and G920S and G920T and G925F and G925I and G925S and G925T
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•Over Clocking
•Under Clocking
•KTweaker app for kernel control
•KTweaker Widgets
•KTmonitor app to watch your cpu cores current speed
Click to expand...
Click to collapse
KTweaker Shop and profile help, plus previous versions can be seen here (thanks to LuigiBull23):
http://forum.xda-developers.com/tmo...nel-kt-sgs6-builds-variants-ktweaker-t3107867
Touchwiz Lollipop 5.0 VERSION:
06.22.2015: http://bit.ly/1Jf6B2n
Click to expand...
Click to collapse
KTweaker Shop and profile help, plus previous versions can be seen here (thanks to LuigiBull23):
http://forum.xda-developers.com/tmo...kernel-kt-sgs6e-builds-ktweaker-shop-t3107937
Sources can be found here:
https://github.com/ktoonsez/KTSGS6
What you can expect to get benchmark wise with a good CPU OC'd:

Go to my original thread to view Change logs:
http://forum.xda-developers.com/showpost.php?p=60180784&postcount=2

Thank You!!!

Lovely restoring 5.0.2 backup now. Will you add support for 5.1.1 or do you need source?

ktetreault14 said:
Lovely restoring 5.0.2 backup now. Will you add support for 5.1.1 or do you need source?
Click to expand...
Click to collapse
There is no source released by Samsung, will probably take them a few weeks before they post

thanks for making this work on our t mobile edge!:good:

Ktoonsez does it again!
Bravo!
Pp.

NICE!! Your work is all i used back when i was on S4! good things are coming to the s6 edge i see!
thanksss!
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
Question, will this kernel fix the deep sleep bug when having custom recovery installed?
thnaks again bro!

cris_epic said:
NICE!! Your work is all i used back when i was on S4! good things are coming to the s6 edge i see!
thanksss!
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
Question, will this kernel fix the deep sleep bug when having custom recovery installed?
thnaks again bro!
Click to expand...
Click to collapse
Thanks man. It should but cant be sure. I did my part in the kernel so when flashing my kernel you dont loose deep sleep.

So W8 and Tmobile are kind of same device?

brar.arsh said:
So W8 and Tmobile are kind of same device?
Click to expand...
Click to collapse
Yes those 2 are. That's about it for all the different variants.

ktoonsez said:
Yes those 2 are. That's about it for all the different variants.
Click to expand...
Click to collapse
Thanks, will try this.. Can I also install leaked 5.1.1 then if they are same?

Awesome to have you been using ur kernels for a o couple of years now lol. time to flash woot woot
Btw download link seems to be down atm any other mirrors ?

brar.arsh said:
Thanks, will try this.. Can I also install leaked 5.1.1 then if they are same?
Click to expand...
Click to collapse
You can try and let us know. I will see if I can flash the Canadian Videotron 925W8 ROM to my 925T tomorrow. All I want is to sim unlock the damn phone bypassing the T-Mobile unlock app.

Thank you for taking the time to make this kernal on T-mobile. Super stoked!

Thanks a lot for the kernel ktoonsez! Exactly what I wanted to see, especially in the app. I know there are many more things to come. Don't know if you remember me from the sgs3 days, we worked together on some small kernel issues with a couple other devs. I developed roms on the sgs3 and hope to jump into the scene with sgs6e.
Sent from my SM-G925T using XDA Free mobile app

Running smooth. Really glad for something to flash on this bad boy. Thanks.☺
Word

Best battery life yet! Thanks for the kernel. Just came from the Oneplus One ( I know I know.. Hehe ) and ran your kernel on that since day one. Glad to have you supporting the s6 edge! Thanks!

Touchwiz Lollipop 5.0 VERSION:
05.04.2015: http://bit.ly/1QgSQQZ
Click to expand...
Click to collapse
Change Log 05.04.2015
1. Add all the TCP congestion option from my S5
2. Added BFQ scheduler
3. Added FIOPS scheduler
4. Fix permissions issues with interactive tunables
5. Fix some set on boot issues where certain options were not getting set.
6. KTmonitor now shows all 8 cores
7. Added "ASV Info" to KTweaker->Get Phone Information screen so you can see your CPU "bin"
8. There was some other stuff I cant remember, enjoy the awesome

Develop Bugs

welcome