bumblebee CPU governor: a modified version of the smartass CPU governor by Erasmux, I changed the latency/timing code to suit the OMAP 3430 (Droid) CPU and will be expanding the code to further performance and expose the control aspects (screenon/off minimum speeds, up/down ramp timing, etc..etc) through an android application. The bumblebee CPU governor currently sets the screenoff maximum to 400/450mhz depending on if your running stock deprimed slots or 'primed', the screenon minimum is set to 250mhz.
What happens to the screen off values if I were to change the values? My speed settings are currently 250, 400, 500, 600, 700, 800, and 900. Would the screen off value still be 400? What would happen if my values were say, 250, 500, 600, 700, 800, 900, 1000?
In any case, test 26 worked great for me and I'm currently installing test 27.