[Sprint Samsung Galaxy S III] freeza:
For those who are having "lag" problems with the cpu scaling script, I can rewrite it to work with whatever kernel/governor you're using.

It's a lot better to use a script than it is to use an app to do these things. Scripts run at a higher priority if you will, than apps.

If you fine tune it to your usage patterns, it can prove to be a very very awesome thing. I've been using the cpu script since the EVO 3D and refuse to ever go back to an APP when the script can do the same thing.

If you would like to have the script rewrote for you, just PM me the following information:

What governor and speed you would like it to run at when plugged into a charger

What governor and speed you would like it to run at when the screen is turned off and on battery

What governor and speed you would like it to run at when the phone is on battery and is between 85-100%

same goes for 75-85, 65-75, 50-65, 40-50, 25-40, and from 0-25.

By default it is set to run at max (1.51, 1.89, or 1.99GHz depending on kernel) frequency when plugged in so you should experience no lag. It is also set to hotplug CPU1 (dual core) and leave it on at all times when plugged into a charger, which means turning off mpdecision, but is set to turn mpdecision back on and leave dual core to the system to control when the charger is removed. You should not have to remove any files from /system/bin in any case. That's just bad for the system. Other files rely on mpdecision being present, the camera library being one of them.

The script is also set to scale down the frequency as your battery depletes so that you can maximize battery life. I tweaked the scaling frequency to be at the highest while maintaining the same voltage. IE some 1.2 and 1.1GHz use the same voltage, so I keep each frequency step at the highest for that voltage table. Also, I came to the conclusion that 702 MHz (which is the lowest it drops the CPU down to while screen is on and battery drops below 25%) is the lowest speed you can go to while having the least bit of lag.

However, the governors used are OnDemand and MSM-DCVS (Dynamic CPU Voltage Scaling) and Intellidemand for custom kernels (ktoonz).

As you can see, there are plenty of parameters you can tweak. Just let me know. Any lagginess you experience is more than likely due to the CPU having to change governors and ramp up speed when first powering it on while on battery. If you let it sit for a second or two after you turn it on, the lag should go away.

On a side note: The msm-dcvs governor is wonderful for stock kernels because it dynamically changes voltage and cpu freq based on certain parameters. It has very few values that can change but it is a good governor to use if you want the benefits of 'undervolting' on a stock kernel. It's actually just a great governor and I use it exclusively. A lot of developers when they include governors they either tweak them to their liking, or just include way too many with too few differences between them. Most of them are based on either conservative or OnDemand anyway. If we could get PegasusQ to work properly with this phone, that would be my governor or choice, but for now MSM-DCVS is what I use.