@Estel As I said before, I'm not epitaphish, it's totally okay, perhaps with our efforts we can further enhace the script. Well then, the best way to figure our ways out is to create a script which monitors the CPU frequency while idle, and then observe the results. I assume most of the time, the CPU will sit on 0, maybe jump to 250 for some time, since the CPU usage with this patch applied is fairly low, 2 to 4 % as a max. I will test this however. I am planning to fully charge my phone, unpatch it, then let it sit idle, and count the days that will pass by, then repeat the test with the patch applied, and see the results. Just to point out, I made the patch very simply to load a KP profile when idle and another one while the device is active as a reply to GigaByte's request, but then I started collecting battery saving scripts scattered here and there into the script, so criticism and testing are certainly the top procedures to take for enhancing the script.
# kernel configuration file generated by /usr/sbin/kernel-config MINFREQ=500 MAXFREQ=900 FREQS="0:30,90 500:39,360 550:42,400 600:45,430 700:50,430 750:54,430 805:54,430 850:57,500 900:60,500 950:65,500 1000:68,500 1100:72,520 1150:72,520" SMARTREFLEX_VDD1=0 SMARTREFLEX_VDD2=0 GOVERNOR=ondemand IGNORE_NICE_LOAD=1 UP_THRESHOLD=90 SAMPLING_RATE=200000 POWERSAVE_BIAS=0