[Samsung Galaxy S 5 Unified Development] justjr:
Awesome, that was fast! I can uninstall ex kernel manager again now.

I think I'm on the right track now with Alucard. I think the best option would be MPDecision without the throttling, but I realize that MPD is a pain.

Last configs I sent without hotplug was waaaay to agressive, but was the minimum I found that the device responded properly without lags.

Configs with Alucard will be much lower.

edit: there's a bug introduced on cpu governors (only tried interactive), where the settings are saved but don't reflect immediately on the app, I have to kill it and when I open it again, the changes were made.

edit2: forget, it seems to be reflecting right away now...

edit3: try these, both cpu and cpuhotplug tweaks together, and turn VDD restriction OFF:

chmod 644 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo 'interactive' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

chmod 644 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo 'interactive' > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

chmod 444 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

chmod 644 /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor

echo 'interactive' > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor

chmod 444 /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor

chmod 644 /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

echo 'interactive' > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

chmod 444 /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

echo '0' > /sys/devices/system/cpu/cpufreq/interactive/io_is_busy

echo '80000' > /sys/devices/system/cpu/cpufreq/interactive/timer_slack

echo '100000' > /sys/devices/system/cpu/cpufreq/interactive/sampling_down_factor

echo '0' > /sys/kernel/cpu_input_boost/enabled

echo '0' > /sys/devices/system/cpu/sched_mc_power_savings

chmod 644 /sys/devices/system/cpu/cpu1/online

echo '1' > /sys/devices/system/cpu/cpu1/online

chmod 444 /sys/devices/system/cpu/cpu1/online

chmod 644 /sys/devices/system/cpu/cpu2/online

echo '1' > /sys/devices/system/cpu/cpu2/online

chmod 444 /sys/devices/system/cpu/cpu2/online

chmod 644 /sys/devices/system/cpu/cpu3/online

echo '1' > /sys/devices/system/cpu/cpu3/online

chmod 444 /sys/devices/system/cpu/cpu3/online

echo '258600' > /sys/kernel/alucard_hotplug/hotplug_freq_1_1

echo '0' > /sys/kernel/alucard_hotplug/hotplug_freq_2_0

echo '258600' > /sys/kernel/alucard_hotplug/hotplug_freq_2_1

echo '0' > /sys/kernel/alucard_hotplug/hotplug_freq_3_0

echo '258600' > /sys/kernel/alucard_hotplug/hotplug_freq_3_1

echo '0' > /sys/kernel/alucard_hotplug/hotplug_freq_4_0

echo '1' > /sys/kernel/alucard_hotplug/hotplug_load_1_1

echo '0' > /sys/kernel/alucard_hotplug/hotplug_load_2_0

echo '1' > /sys/kernel/alucard_hotplug/hotplug_load_2_1

echo '0' > /sys/kernel/alucard_hotplug/hotplug_load_3_0

echo '1' > /sys/kernel/alucard_hotplug/hotplug_load_3_1

echo '0' > /sys/kernel/alucard_hotplug/hotplug_load_4_0

echo '0' > /sys/module/lazyplug/parameters/lazyplug_active

echo '1' > /sys/kernel/alucard_hotplug/hotplug_enable

echo '652800' > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

echo '20000 652800:60000 883600:40000 1497600:20000' > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay

echo '45000' > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time

echo '30000' > /sys/devices/system/cpu/cpufreq/interactive/timer_rate

echo '80' > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

echo '98 246800:75 300000:12 422400:30 652800:40 729600:12 883200:50 1036800:8 1190400:70 1267200:6 1449700:75 1574400:5 1728000:70 1958400:75 2265600:80 2457600:95' > /sys/devices/system/cpu/cpufreq/interactive/target_loads

Nice and fast work on the app, core control back to business.

Some comparisons on clock usage:

Without Hotplug, yesterday settings:

Now with alucard, more efficient governor settings:

TWEAKS ARE NEVER FINISHED!

There are some tunables on interactive (for me) that I never seen on any of my devices kernels, single_enter_load, multi_enter_load, single_exit_load and multi_exit_load. I can't find nothing on them. Would love to... it seems to control something about CPU clusters, which the klte don't have.