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?
Hi Guys!!!
Please help me editing performance profiles..
Everytime i edit the
1. Power save
2. Balanced
3. Performance
profiles through performance setting above the developer options it gets reset to default. My settings dont save.
Presently im on CM11 RC20...
and i have read about the touch boost(the min and max frequency are same)
so everytime i set max and min value. The min value changes and goes equal to max value.
Can i change this behaviour. Because due to this the frequency getting stick to only max(which i set) and its not going down.
Please help me in editing(min and max values plus governor) these profiles to my choice and save them for permanent.
Thank you in advance.
Just tick the option of 'Set on Boot' and reboot.
Thank you for your reply...
I want to change all the profiles to my choice.
Like i want the below.
1. Balanced profile - from 300mhz to 998mhz governor- ondemand
2. Power Save profile - from 300mhz to 600mhz governor - powersave
3. Performance profile - from 300mhz to 1497mhz governor - ondemand
By setting on boot it is going to default. I want to manual edit them.
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
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.
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