Database Develop

*** droid 4 overclocking ***

As some may now, the droid 4 can be overclocked already thanks to TEKAHUNA the link below is a link to his thread. All instructions and download links are there i currently am overclocked to 1388. All vsel controls are available also.
Link
tekahunas thread
After loading the modules you can use quickclock advanced to change ALL values.
Sent from my DROID4 using XDA App

Have you tried OCing higher? Or are you just keeping it at 1388 to be safe?

phrir1 said:
As some may now, the droid 4 can be overclocked already thanks to TEKAHUNA the link below is a link to his thread. All instructions and download links are there i currently am overclocked to 1388. All vsel controls are available also.
Link
tekahunas thread
Sent from my DROID4 using XDA App
Click to expand...
Click to collapse
If you check my Utility I added an Overclock Install option. It also has links to a better video guide to overclocking.

jgardner said:
Have you tried OCing higher? Or are you just keeping it at 1388 to be safe?
Click to expand...
Click to collapse
Yeah i was running 1.4 stable for a little while, but after a while i noticed lag here and there so i just dropped it down to 1388 to be on the safe side. After loading the modules i use quickclock advanced to play with all the settings.
Sent from my DROID4 using XDA App

Hi phrir1, mattlgroff,
Which file should I download for Droid 4? I cannot see it was listed there but only saw Droid 3 only.
BTW, is it no problem to running on stock 2.3.6 rom ?
Million thx!
I kept to use 2.3.6 because of webtop 2.0
Kent

I installed the two zip from recovery, but in the ommand-line, I have no "overclock" directory under /proc/.
Anybody can use that desription?

Adamyno said:
I installed the two zip from recovery, but in the ommand-line, I have no "overclock" directory under /proc/.
Anybody can use that desription?
Click to expand...
Click to collapse
please use the jbx kernel I posted in developers section

lucize said:
please use the jbx kernel I posted in developers section
Click to expand...
Click to collapse
I installed CM 11 Nightly, kernel 3.0, kernel_jbx, moto_init_d, mo_simp_1.5_spyde zip files, but nothing happens, I have no overclock directory

Adamyno said:
I installed CM 11 Nightly, kernel 3.0, kernel_jbx, moto_init_d, mo_simp_1.5_spyde zip files, but nothing happens, I have no overclock directory
Click to expand...
Click to collapse
On CM11 you can only use lucize's jbx kernel or dtrail1's jbx kernel to overclock, you're installing a bunch of things that shouldn't be used on CM11
I've been using stargo's CM11 with dtrail1's jbx kernel with the droid 4 overclocked/undervolted to 1.3ghz and GPU at 384mhz with good stability (certain settings like interactive govenor will make the device unstable though), lucize's kernel is based off dtrail1's kernel and should be more suited for our device.

I use KitKat 4.4.4 slimkat or CM11
and jbx kernel from lucize
to change cpu setting i use no-frills CPU or Trickstar MOD
but in this programs I can't go more then 1,3 GHz
from comand line I don't have /proc/overclock dir
where can I change proper CPU values ?
I only want to check if phone can work with bigger and to have few more point in Atutu :>

jaqjacek said:
I use KitKat 4.4.4 slimkat or CM11
and jbx kernel from lucize
to change cpu setting i use no-frills CPU or Trickstar MOD
but in this programs I can't go more then 1,3 GHz
from comand line I don't have /proc/overclock dir
where can I change proper CPU values ?
I only want to check if phone can work with bigger and to have few more point in Atutu :>
Click to expand...
Click to collapse
You have to use the MPU OC option to get above 1300mhz. Disable "Battery Friend" first otherwise it won't allow you to adjust the MPU setting.
CPU frequency is multiplied by the MPU, adjusting it will effect all CPU steps much like overclocking frontside bus on a PC, stock is 100, so think of the 1300mhz setting as a 13x multiplier, 300mhz as a 3x multiplier, and so on.
A good, easily achievable OC is 108 MPU
100 MPU x 13 = 1300mhz
108 MPU x 13 = 1404mhz
100 MPU x 3 = 300mhz
108 MPU x 3 = 326mhz
and so on... much beyond this you have to fiddle with the voltages a lot otherwise you will get random reboots, I found I needed a MPU voltage of 1420 (1.420v) to get 1404mhz completely stable. The other voltages are pretty generous and I have found they can be undervolted significantly while running 1.4ghz+.
With the phone at 1495mhz I managed to get just shy of 14,000 in Antutu but it was not stable because of voltages... roughly 1450mhz should be safe for a daily driver while maintaining good battery life and low heat once lowest possible stable voltages are worked out, maybe more, still testing it all myself.

Elanzer said:
You have to use the MPU OC option to get above 1300mhz. Disable "Battery Friend" first otherwise it won't allow you to adjust the MPU setting.
CPU frequency is multiplied by the MPU, adjusting it will effect all CPU steps much like overclocking frontside bus on a PC, stock is 100, so think of the 1300mhz setting as a 13x multiplier, 300mhz as a 3x multiplier, and so on.
A good, easily achievable OC is 108 MPU
100 MPU x 13 = 1300mhz
108 MPU x 13 = 1404mhz
100 MPU x 3 = 300mhz
108 MPU x 3 = 326mhz
and so on... much beyond this you have to fiddle with the voltages a lot otherwise you will get random reboots, I found I needed a MPU voltage of 1420 (1.420v) to get 1404mhz completely stable. The other voltages are pretty generous and I have found they can be undervolted significantly while running 1.4ghz+.
With the phone at 1495mhz I managed to get just shy of 14,000 in Antutu but it was not stable because of voltages... roughly 1450mhz should be safe for a daily driver while maintaining good battery life and low heat once lowest possible stable voltages are worked out, maybe more, still testing it all myself.
Click to expand...
Click to collapse
Thanks! 400 Points more on first try and still testing.
Could you share yours daily use cpu parameters ?
For example
1300 x MPU 108 1420
1100 x MPU 108 1380
.....
or just print screens from trickstar mod or any other cpu app.
I'm curies about battery level too.
Other thing on mys Milestone2 i have only 4 CPU Frequency step with custom changeable example: originaly was 1000,800,600,300 best for my 1200,900,500,300
On Droid 4 apps shows that I have more then 10 on Lucid Kernel
Does cpu governors use all of that steps ?
If there are only few of them can I and should I change those steps ?

jaqjacek said:
Thanks! 400 Points more on first try and still testing.
Could you share yours daily use cpu parameters ?
For example
1300 x MPU 108 1420
1100 x MPU 108 1380
.....
or just print screens from trickstar mod or any other cpu app.
I'm curies about battery level too.
Other thing on mys Milestone2 i have only 4 CPU Frequency step with custom changeable example: originaly was 1000,800,600,300 best for my 1200,900,500,300
On Droid 4 apps shows that I have more then 10 on Lucid Kernel
Does cpu governors use all of that steps ?
If there are only few of them can I and should I change those steps ?
Click to expand...
Click to collapse
These are my current settings. I'm still working on them because I adjust them then use the phone for 2 full days / charges to test the stability, not every stepping is adjusted completely down - I adjusted/tested the middle voltages in groups and only adjusted the top/bottom voltages individually. There's no quick way to test them because they'll test perfectly in a CPU stress test app then within 5min of browsing the device will reboot. These particular settings have been stable for a few days. I could not get even 1443mhz stable what so ever, even after adding +75 to all voltage steps, so maybe 1.4ghz is closer to a realistic limit.
Also the voltages on this device/kernel seem to have a limit of how low you're allowed to set it. I'm not sure if this is an artificial limit or a limit of the hardware, but 952 is the lowest voltage available for 300mhz even though the device could likely undervolt far more at this frequency. Since 100 and 200 also use the same 952 voltage, there is zero point in setting the minimum frequency to anything lower than 300, as they all use the same voltage.
I'm not allowed to post a link directly because I don't have 10 posts yet (this rule is stupid), but here you go: hxxp://i.imgur.com/01xb0Wp.png
The CPU govenor uses all steps provided you're using ktoonservative. I found I couldn't use most other governors because they would freeze the device (ie: switching CPU governor Interactive would freeze the device, switching the I/O governor from deadline to sioplus freezes, etc). There is lots to adjust in the ktoonservative governor for performance/battery life.
I'm currently using these settings right now with good results as a balance between battery life and performance:
up_threshold 80
up_threshold_hotplug 85
down_threshold 30
down_threshold_hotplug 25
sampling_down_factor 10
sampling_rate 35000
sampling_rate_screen_off 30000
freq_step 1
disable_hotplugging 0
freq_step decides how much the CPU ramps up, a setting of "1" ensures it uses all frequencies. If you use "20" it'll increase the frequency to the closest 20% each time instead of closest 1%. Set to 100 and the governor works identical to the "ondemand" govenor (ie: CPU will go straight from lowest to highest speed). The thresholds have to do with how much % the CPU utilization has to be at before it will increase or decrease the frequency, so lower numbers can increase responsiveness by having the CPU increase it's speed quicker.

I use yours governors conifg
and
MPU 108
1404 Mhz - 1302
1296 Mhz - 1300
1188 Mhz - 1275
1080 Mhz - 1275
972 Mhz - 1255
864 Mhz - 1210
756 Mhz - 1160
648
540
432 Mhz - 1117
324
216
108 Mhz - 952
those are my stable for now
but the battery isn't so good I can only dream about 2 days
It is how your say benchmark pass but open some app and chance for reboot is 50/50
Is there a way to see current voltage ?
Because phone shouldn't work on 1404Mhz x 1302v and i think that I miss something.

jaqjacek said:
I use yours governors conifg
and
MPU 108
1404 Mhz - 1302
1296 Mhz - 1300
1188 Mhz - 1275
1080 Mhz - 1275
972 Mhz - 1255
864 Mhz - 1210
756 Mhz - 1160
648
540
432 Mhz - 1117
324
216
108 Mhz - 952
those are my stable for now
but the battery isn't so good I can only dream about 2 days
It is how your say benchmark pass but open some app and chance for reboot is 50/50
Is there a way to see current voltage ?
Because phone shouldn't work on 1404Mhz x 1302v and i think that I miss something.
Click to expand...
Click to collapse
I am 3 days uptime on these current settings at 111 MPU with heavy use:
Code:
hxxp://i.imgur.com/17iPAZL.png
The phone rebooting is generally caused by voltage being too low. 1302 is way too low for 1404mhz and is probably why you're getting the reboots. The "1302" value translates to "1.302v" which is a perfectly normal CPU voltage, but it's really low and I can't imagine that being stable for you since I need "1390" for 1404. There isn't a way of checking the current voltage other than looking at the current frequency.
I have not further reduced the 1332 and 1221mhz settings yet as I found reducing them was causing my issues getting above 109 MPU. Probably in a week or two so of use and adjustments I'll post my final tuned settings after I squeeze all I can out of it, I just require a few days of solid uptime to verify stability because I can't seem to find a stress testing program that ensures total stability. it's just that I test each setting over a period of days. My settings might not work for you since all CPUs aren't identical in quality, but it should give you a ballpark of settings.
If you want to improve battery further try looking at adjusting the automatic screen brightness, I'm currently using these settings, although you could easily further reduce brightness:
Code:
hxxp://imgur.com/D3sKAIn

hey guys, just imported 2 droid 4s to the uk.
an amazing device still today i think.
Can anyone suggest how to get mpu oc to stick after reboot? It always seems to reset to 100.
The frequency oc sticks but drops to 1300 due to mpu not sticking.

[KERNEL][TMO][TW5.0][06/22/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 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...nel-kt-sgs6-builds-variants-ktweaker-t3107867
Sources can be found here:
https://github.com/ktoonsez/KTSGS6
What you can expect to get benchmark wise with a good CPU OC'd:

Change Log 05.18.2015
1. Add some more protection on hotplugging for phones that are not fully shutting down screen and still register touch while screen is off, causing reboots.
2. Making unified version now, so pay attention that the file name is now changed. There is still seperate version for the S6 and S6 Edge, and also Sprint needs a special due to radical differences from the GSM versions.
3. KTweaker: Added new 3 options prompt when restoring a profile. Instead of a yes/no question to apply, it now gives you the 3 options of: "Apply restored profile with its voltage", "Apply restored profile with my voltage", "Do not apply it"
Change Log 05.12.2015
1. The wait is over for ktoonservative governor!!!!!!!!!!!!!!!!!!!!!!!!
2. ktoonservative governor supports hotplugging for some amazing battery life and still smoooooooooth.
3. Shorten internal kernel name so Antutu wont crash on some phones.
4. LED Fade mode code added.
5. LED fade mode fade up time to set how long it takes to fade in.
6. LED fade mode fade down time to set how long it takes to fade out.
7. Disable LED start hour to allow a start time of when LED are NOT active.
8. Disable LED stop hour to allow a stop time of when LED are NOT active.
9. Disable LED always option to disable LEDs all together.
10. Built with Linaro official 4.9 with -O3 optimizations
11. Added ktoonsified v1 profile made by myself and Luigibull, you can get it in the KTweaker shop in KTweaker app. BE SURE TO LOAD YOU STOCK VOLTAGE TABLE AFTER APPLYING!!!!!!!
Change Log 05.02.2015
1. Added UC and OC steps for both CPU's. Little now ranges from 200-1600 and big ranges from 200-2496. Be sure to adjust voltages accordingly, the UC and OC steps may not work properly for your binned CPU without tweaking the voltage!!!!!!!!!!!!!!!!!
2. Included patch to insure deep sleep is NOT lossed
2. KTweaker 9.3
3. Cleaned up some FC issues
4. GPU screen is now fully functional for all items
5. "Get Phone Information" screen was pretty'd up and added CPU "Time in State" gride for both little and big cpus including Deep Sleep and Total up Time items.
6. OTA is now functional.
7. KTweaker Shop for Profiles is now functional. Only 1 profiles which is the stock settings.
8. Change Log item in KTweaker is now functional.
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.
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!!!!!!!!!!!!!!!

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.

Can I test?

mikeyinid said:
Can I test?
Click to expand...
Click to collapse
Here you go man. This is just a test of mostly stock kernel, we are testing for Cell service, Wifi and deep sleep since that seems to be a common problem for anything custom on this device, so make sure you are getting deep sleep first before flashing:
Also, I really need that post your snuck on, lol. U know how to let me take that post over?
http://bit.ly/1ESQRPi

haha crap, i didnt realize you had just posted. i think a mod can switch it over to you, or just delete it.

mikeyinid said:
haha crap, i didnt realize you had just posted. i think a mod can switch it over to you, or just delete it.
Click to expand...
Click to collapse
All taken care of by my good friend @kennyglass . Flash the kernel and let me know what happens please

ktoonsez said:
All taken care of by my good friend @kennyglass . Flash the kernel and let me know what happens please
Click to expand...
Click to collapse
Flashed it, phone is deep sleeping. WiFi works, data works, usb works. no issues stand out yet.

mikeyinid said:
Flashed it, phone is deep sleeping. WiFi works, data works, usb works. no issues stand out yet.
Click to expand...
Click to collapse
Awesome. Use my app called KTweaker and open it up. Its a slide menu app like Play Store so slide from far left to the right to open the menu and click on "Utilities" then "Generate a dmesg" and post the file for me so I can kill all the dmesg spam and speed this beeach up

thanks man, glad to see you here i remember using your kernel during my s4 days
flashed it and its working great! just one thing. KTweaker is crashing upon starting the app

guaneet said:
thanks man, glad to see you here i remember using your kernel during my s4 days
flashed it and its working great! just one thing. KTweaker is crashing upon starting the app
Click to expand...
Click to collapse
Thanks man. Do you have root? Do you know how to get dmesg's and logcat's from your PC so I know whats crashing it if there is root installed already?

It crashes for me as well, flashed it with the XtreStroLite ROM.
Edit: Just noticed this page.
Yes, I do have root.
No, I don't know. Mind telling me how? I do have Windows and Ubuntu.
Edit2: No longer crashes after flashing the latest kernel.
Thanks!

Paradoxumical said:
It crashes for me as well, flashed it with the XtreStroLite ROM.
Click to expand...
Click to collapse
That doesnt help, look at my post above.

ktoonsez said:
Thanks man. Do you have root? Do you know how to get dmesg's and logcat's from your PC so I know whats crashing it if there is root installed already?
Click to expand...
Click to collapse
yeah i have the devices root with twrp, I wiped cache as well. i forgot how to get dmsg and logs from PC sorry. let me do some research and see what i can muster up

guaneet said:
yeah i have the devices root with twrp, I wiped cache as well. i forgot how to get dmsg and logs from PC sorry. let me do some research and see what i can muster up
Click to expand...
Click to collapse
Try redownloading, just updated source to OCV and changed a few flags, not sure if it will KTweaker, probably not but worth a shot.

wow, awesum to see you over here, man!
I'd be glad to test, but I have the s6Edge, not the S6, and the phones are just a bit different, and I've already bricked my phone once this week!

wase4711 said:
wow, awesum to see you over here, man!
I'd be glad to test, but I have the s6Edge, not the S6, and the phones are just a bit different, and I've already bricked my phone once this week!
Click to expand...
Click to collapse
Lol, ya, completely different phone :highfive:

ktoonsez said:
Awesome. Use my app called KTweaker and open it up. Its a slide menu app like Play Store so slide from far left to the right to open the menu and click on "Utilities" then "Generate a dmesg" and post the file for me so I can kill all the dmesg spam and speed this beeach up
Click to expand...
Click to collapse
I'll be glad to test this for you on the stock ROM with no mods and Deep Sleep *working*. I've searched everywhere for the stock kernel to revert back to in case of issues... No luck, any tips where to find it besides Samsung Opensource?
Edit nevermind, I'll make a backup, duh...

So I just flashed the file from the OP
"KT-SGS6-LP5.0-TW-G920T-04.17.2015.zip"
And it seems like it didn't actually flash. The kernel under info is still 3.10.61-4351281 built on March 27th.
Anybody else seeing this too? Looked in the ZIP and there's a boot.img, along with two modules. The update script looks right. Any ideas?
EDIT: redownloaded, this time the file is a different one, larger 13.5MB vs 11.9MB - this file includes KT Monitor and Tweaker. However, the kernel version is still the same as the old file (with a build date of 3/27)

Yep, I flashed the same OP link and check under about phone, same thing as stated above but the ktweaker app is installed sooo?? Assuming this is expected, I don't see any change in voice calling, wifi, lag etc.. Feels exactly the same so thats good.
Now, everytime I try to open Ktweaker it closes,cleared cache/data etc but no luck..??

[KERNEL][INTL][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

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.

Great to see you here mate.
Do you know where I can find my chip ASV / bin?
Sent from my SM-G925F

ktoonsez said:
Ktoonsez presents:
​
Sources can be found here:
https://github.com/ktoonsez/KTSGS6
Click to expand...
Click to collapse
great to see you here 2 great kernels here in dev section just need some great roms now

Welcome

skivnit said:
Great to see you here mate.
Do you know where I can find my chip ASV / bin?
Sent from my SM-G925F
Click to expand...
Click to collapse
Here is your answer for wifi:
CHANGE
ro.securestorage.support=true
TO
ro.securestorage.support=false
In your build.prop
To get you BIN, reboot, get a dmesg and search for "ASV-GROUP=". The first set you hit in the log will be your BIN for BIG CPU, the second set with be LITTLE CPU.

Thank you man, can't wait to see ur kernel fully operational as i'the s5
Sent from my SM-G925F

Hell yeah!! Was rocking this great kernel on my old GS4. Glad to see the Edge getting some dev support now, was starting to think I had made a mistake getting it over the regular S6! I don't want a phone I can't tinker with.

I'm attaching my logs there's a lot of ASV http://1drv.ms/1ORUUld
Sent from my SM-G925F

skivnit said:
I'm attaching my logs there's a lot of ASV http://1drv.ms/1ORUUld
Sent from my SM-G925F
Click to expand...
Click to collapse
Not sure if we got a language barrier or not here so Ill try to explain again:
Open the dmesg file
Search for "ASV-GROUP="
the first set of 24 or so is your BIG CPU
the second set of 19 or so is your LITTLE CPU (there will be a gap of other types of log info in between the BIG CPU logs and the LITTLE logs entries)

Hehe no language barrier just got confused with the ASV as it shows 0 then 8 that's why I attached if you can have a look. If you don't have time no worries
90% sure it's 8 for both
Sent from my SM-G925F

Kernel works perfekt and fast only litten Problem restart KT app Coming this.

skivnit said:
Hehe no language barrier just got confused with the ASV as it shows 0 then 8 that's why I attached if you can have a look. If you don't have time no worries
90% sure it's 8 for both
Sent from my SM-G925F
Click to expand...
Click to collapse
I tried to download when u posted it but it says read-only with a zip file and I clicked it and did nothing so could not view it :good:

cobra11111 said:
Kernel works perfekt and fast only litten Problem restart KT app Coming this.
Click to expand...
Click to collapse
That feature is not implememted yet, read the change log for options I have implememted:good:

ktoonsez said:
I tried to download when u posted it but it says read-only with a zip file and I clicked it and did nothing so could not view it :good:
Click to expand...
Click to collapse
[spolier] SET ASV INFO: ASV-TYPE=0, RCC-VALUE=0, INDEX=1
< 1>[ 0.245720] [6: swapper/0: 1] SET ASV INFO: ASV-TYPE=0, ASV-SUB-IDX=0, ASV-GROUP=8, INDEX=1
< 1>[ 0.245730] [6: swapper/0: 1] SET ASV INFO: ASV-TYPE=0, VOLT-VALUE=1075000, INDEX=2
< 1>[ 0.245741] [6: swapper/0: 1] SET ASV INFO: ASV-TYPE=0, RCC-VALUE=0, INDEX=2
< 1>[ 0.245751] [6: swapper/0: 1] SET ASV INFO: ASV-TYPE=0, ASV-SUB-IDX=0, ASV-GROUP=8, INDEX=2
[/spoiler]1]
This is it right?
Sent from my SM-G925F

Any chance of a TMO/W8 build? Kernel works great but there's no in-call audio similar to all other F/I/S based kernels.

skivnit said:
[spolier] SET ASV INFO: ASV-TYPE=0, RCC-VALUE=0, INDEX=1
< 1>[ 0.245720] [6: swapper/0: 1] SET ASV INFO: ASV-TYPE=0, ASV-SUB-IDX=0, ASV-GROUP=8, INDEX=1
< 1>[ 0.245730] [6: swapper/0: 1] SET ASV INFO: ASV-TYPE=0, VOLT-VALUE=1075000, INDEX=2
< 1>[ 0.245741] [6: swapper/0: 1] SET ASV INFO: ASV-TYPE=0, RCC-VALUE=0, INDEX=2
< 1>[ 0.245751] [6: swapper/0: 1] SET ASV INFO: ASV-TYPE=0, ASV-SUB-IDX=0, ASV-GROUP=8, INDEX=2
[/spoiler]1]
This is it right?
Sent from my SM-G925F
Click to expand...
Click to collapse
That is the entry types yes, you do have to pull it as soon as you boot or things get over-written. Here is an example of one of my testers logs:
http://pastebin.com/4gGK46ZS
In lines 245-314 you can see the BIG CPU (his is a 5)
In lines 343-397 you can see the LITTLE CPU (his is a 9)

Yep that's what I got, it's 8 on both, is there a table of the max UV values we can apply depending on the bins? The one on Anand shows few freqs and asvs
Sent from my SM-G925F

skivnit said:
Yep that's what I got, it's 8 on both, is there a table of the max UV values we can apply depending on the bins? The one on Anand shows few freqs and asvs
Sent from my SM-G925F
Click to expand...
Click to collapse
There is no guidline for OCing, its trial and error, here is a link to the code with the table in it:
https://github.com/ktoonsez/KTSGS6/...m64/mach-exynos/include/mach/asv-exynos7420.h
Line 1307 is where it starts for the big, 1339 for the little. The ASV8 column is yours since you said your an 8, and you can see the other columns ASV0 thru ASV15

Any tweak to restrict cpu speed in order to avoid overheating?

I can't use my vr gear for more that 10 minutes before the overheating message appears on the phone.
Has anyone found a fix for this?
I wouldn't do the cooling fan mod on the gear, too much hassle.

On my note 4 I undervolt and set the cpu governor to 1100mhz max. I believe the VR is more dependent on GPU than CPU so undervolt and limiting the cpu speed keeps it cooler.

jedisurfer said:
On my note 4 I undervolt and set the cpu governor to 1100mhz max. I believe the VR is more dependent on GPU than CPU so undervolt and limiting the cpu speed keeps it cooler.
Click to expand...
Click to collapse
Do you mind sharing your voltage and clock settings?
How much additional time you achieve with your setup?
Thanks!

Rayan said:
Do you mind sharing your voltage and clock settings?
How much additional time you achieve with your setup?
Thanks!
Click to expand...
Click to collapse
I can run it pretty much indefinitely I think, at least an hour. I usually stop every 30 min because my eyes get strained.
I have emotion kernel 21, running rapture rom using synapse to undervolt and underclock. I have the 805 variant so there is core 0, 1, 2, 3. Under hotplug I also disable core 3. It runs perfectly fine and does not jitter even with the cpu set that low and core 3 offline(the 4th core since it starts at core 0)
I run -100mv through all the speed steps (that's the most it will let me undervolt global if I want to go lower I have to manual set it for each speed)
268mhz - 600mv
300mhz - 605mv
345 - 610
422 - 615
499 - 625
576 - 635
652 - 645mv
729 - 655mv
etc each step I usually go up 10mv
1113 - 705mv
1190 - 715
1267 - 725mv
1344 - 745mv
my pvsX
qcom speed2-pvs13-bin-v1 I believe I got lucky with a high pvs13 your undervolts will vary. So please go slowly and don't try -100mv right away. I'd go -20, -40, -60 etc to test stability first. I also run it without the back cover just because I hate my chips heating up too much.

jedisurfer said:
I can run it pretty much indefinitely I think, at least an hour. I usually stop every 30 min because my eyes get strained.
I have emotion kernel 21, running rapture rom using synapse to undervolt and underclock. I have the 805 variant so there is core 0, 1, 2, 3. Under hotplug I also disable core 3. It runs perfectly fine and does not jitter even with the cpu set that low and core 3 offline(the 4th core since it starts at core 0)
I run -100mv through all the speed steps (that's the most it will let me undervolt global if I want to go lower I have to manual set it for each speed)
268mhz - 600mv
300mhz - 605mv
345 - 610
422 - 615
499 - 625
576 - 635
652 - 645mv
729 - 655mv
etc each step I usually go up 10mv
1113 - 705mv
1190 - 715
1267 - 725mv
1344 - 745mv
my pvsX
qcom speed2-pvs13-bin-v1 I believe I got lucky with a high pvs13 your undervolts will vary. So please go slowly and don't try -100mv right away. I'd go -20, -40, -60 etc to test stability first. I also run it without the back cover just because I hate my chips heating up too much.
Click to expand...
Click to collapse
Funny I just did the same thing to my a10 7870k rig. Lowered vcore and over clocked gpu. Runs much better those a10s don't need 1.45 volts lol. I'm not sure if I could do that to my s6 tho as I'm nervous to root because of jump program.
Sent from my SM-G920T using Tapatalk

Battery drain on CM13 based ROMs

A finding and a question:
1. ksmd is consuming CPU cycles. If I disable ksmd, the loadavg drops dramatically.
Code:
echo 0 > /sys/kernel/mm/ksm/run
It helps reduce battery usage.
2. I am seeing Gmail is consuming a whole lot of CPU cycles and its triggering a media scan. Is anyone else seeing this?
Code:
User 7%, System 36%, IOW 0%, IRQ 0%
User 5 + Nice 11 + Sys 76 + Idle 119 + IOW 0 + IRQ 0 + SIRQ 0 = 211
PID PR CPU% S #THR VSS RSS PCY UID Name
887 1 31% S 4 8564K 2952K fg media_rw /system/bin/sdcard
30426 0 21% S 71 1251556K 132212K bg u0_a123 com.google.android.gm
6735 0 4% R 1 2968K 1180K fg root top
Obviously, killing the process does not help because its system service and will pop right back up.

devsk said:
A finding and a question:
1. ksmd is consuming CPU cycles. If I disable ksmd, the loadavg drops dramatically.
Code:
echo 0 > /sys/kernel/mm/ksm/run
It helps reduce battery usage.
2. I am seeing Gmail is consuming a whole lot of CPU cycles and its triggering a media scan. Is anyone else seeing this?
Code:
User 7%, System 36%, IOW 0%, IRQ 0%
User 5 + Nice 11 + Sys 76 + Idle 119 + IOW 0 + IRQ 0 + SIRQ 0 = 211
PID PR CPU% S #THR VSS RSS PCY UID Name
887 1 31% S 4 8564K 2952K fg media_rw /system/bin/sdcard
30426 0 21% S 71 1251556K 132212K bg u0_a123 com.google.android.gm
6735 0 4% R 1 2968K 1180K fg root top
Obviously, killing the process does not help because its system service and will pop right back up.
Click to expand...
Click to collapse
Cool.. that's good to know. Thanks for the info! Would you say disabling that kernel process reduces battery usage a great deal?
One thing that I have noticed with CM 13/marshmallow builds in general, is that sometimes my device just *will not* connect to the mobile network; sometimes I will get lucky and it will connect just fine, but other times it cannot make a connection to save its soul. When it cannot connect, it persistently tries to connect, over and over again-- even if I'm on Wi-Fi-- and the battery is drained at a very rapid rate. However, when it does connect to the LTE network with no issues, battery drainage becomes a non-issue.
(I'm on Verizon, btw)

devsk said:
A finding and a question:
1. ksmd is consuming CPU cycles. If I disable ksmd, the loadavg drops dramatically.
Code:
echo 0 > /sys/kernel/mm/ksm/run
It helps reduce battery usage.
2. I am seeing Gmail is consuming a whole lot of CPU cycles and its triggering a media scan. Is anyone else seeing this?
Code:
User 7%, System 36%, IOW 0%, IRQ 0%
User 5 + Nice 11 + Sys 76 + Idle 119 + IOW 0 + IRQ 0 + SIRQ 0 = 211
PID PR CPU% S #THR VSS RSS PCY UID Name
887 1 31% S 4 8564K 2952K fg media_rw /system/bin/sdcard
30426 0 21% S 71 1251556K 132212K bg u0_a123 com.google.android.gm
6735 0 4% R 1 2968K 1180K fg root top
Obviously, killing the process does not help because its system service and will pop right back up.
Click to expand...
Click to collapse
I turned the KSM off in the Kernel Auditor and the loadav dropped significantly. It should be removed because it serves no purpose really and changing it every boot is a pain As for the gmail service, I just limited it's wakelocks because it was too damn frequent. But what I am wondering is, how is your loadavg 0.8? mine is 2.28 1.93 2.12 4/1437 4960 ... I think I have a major problem somwhere The lowest it has ever been is 1.60

Sinistersky said:
I turned the KSM off in the Kernel Auditor and the loadav dropped significantly. It should be removed because it serves no purpose really and changing it every boot is a pain As for the gmail service, I just limited it's wakelocks because it was too damn frequent. But what I am wondering is, how is your loadavg 0.8? mine is 2.28 1.93 2.12 4/1437 4960 ... I think I have a major problem somwhere The lowest it has ever been is 1.60
Click to expand...
Click to collapse
The loadavg depends on the apps you run. I have noticed that it spikes whenever gmail is doing the email sync or I am running videos from whatsapp etc.
So, don't worry about a larger value if you have been using the phone. The loadavg for idle phone should be close to 0, but it rarely is, because our phones are always doing something in background. The lowest I have seen it drop is 0.08, and then gmail brings it up whenever it does a sync. I have several accounts linked in gmail (yahoo, hotmail, google, work), so its understandable.
One thing you can do to monitor is to see which processes are eating up the CPU with:
Code:
ps | sort -n -k5 | tail -n 5
top -m 3 -s cpu -n 2 -d 2 | grep -v "^$" | tail -n 6
It will show 5 top memory consumers and 3 top CPU consumers. Put it in a shell script and run it periodically to collect some stats.
I have noticed dhd_dpc taking up CPU cycles. But I need the wifi... So, unless and until someone comes along and optimizes the kernel driver for wifi on M7, that's what we got! I don't think anybody would touch the driver code for m7. So, some things will never get fixed for m7.
On the other hand, the cycles eaten by system_ui and system_server are inexcusable! They can be fixed by CM/Google in non-device specific code. May be that will happen as CM13/Marshmallow matures.

devsk said:
The loadavg depends on the apps you run. I have noticed that it spikes whenever gmail is doing the email sync or I am running videos from whatsapp etc.
So, don't worry about a larger value if you have been using the phone. The loadavg for idle phone should be close to 0, but it rarely is, because our phones are always doing something in background. The lowest I have seen it drop is 0.08, and then gmail brings it up whenever it does a sync. I have several accounts linked in gmail (yahoo, hotmail, google, work), so its understandable.
One thing you can do to monitor is to see which processes are eating up the CPU with:
Code:
ps | sort -n -k5 | tail -n 5
top -m 3 -s cpu -n 2 -d 2 | grep -v "^$" | tail -n 6
It will show 5 top memory consumers and 3 top CPU consumers. Put it in a shell script and run it periodically to collect some stats.
I have noticed dhd_dpc taking up CPU cycles. But I need the wifi... So, unless and until someone comes along and optimizes the kernel driver for wifi on M7, that's what we got! I don't think anybody would touch the driver code for m7. So, some things will never get fixed for m7.
On the other hand, the cycles eaten by system_ui and system_server are inexcusable! They can be fixed by CM/Google in non-device specific code. May be that will happen as CM13/Marshmallow matures.
Click to expand...
Click to collapse
Thanks for the info. I'll try to collect some stats on my device to see what is putting a strain on the battery so much. As for the system, it has always been that way ever since lollipop came. Nobody bothers to fix it, and I am beginning to think that maybe they didn't notice the numbers or the switch from 5.0 to 6.0 happened so fast they just went "meh, we'll leave it and maybe fix it later if we remember". I never understood why most of the ROM and kernel makers try to add more new stuff without even fixing and optimizing the things that are the core of the new optimizations and add-ons. It just makes no sense to try to push something new on a broken foundation to begin with. The M7 is a great phone even now, and I had it for 3 years now. Naturally, the battery is very old now and the moment i start using the screen it drops 20% in an hour or so, making me have at most 3 hours of screen time. But with background usage restriction I get by on a daily basis just barely. Fixing the system cycles would be heavenly for me, but alas, maybe it will never happen, sadly