new set speed script for bugless!

0.2 will overwrite the installation of the script (but you can just install it again). The new version of pete's startup script does properly detect and automatically uses the minimum and maximum supported CPU speeds (and it WILL automatically update the speed when you change kernels, now). It's using the same method my script used, but doesn't allow you to modify the speed - it only uses the minimum and maximum supported. Previously, the speed was being hard-coded, and the new maximum speed was being included in the kernel update. Was I Pete's inspiration for this change?

The script in the first post should still work, however, if you want to customize your min/max speed.

I am also working on a new script in a different format:

setmax XXX
setmin XXX
setgov xxxxxxxxx

When you type any of those by itself, it will list off all the available speeds (or governors), including the virtual speeds of "max" and "min". When you set one, it will take effect immediately and be applied on reboot. I'll have that posted tomorrow sometime for people that are interested in customizing their speed.

For now, the script in the original post should still work fine!

 

Try the "uninstall" option on setspeed - or manually erase files out of /system/xbin (setspeed, setmin, setmax, setgov, speed*)

Sorry, that's my fault - I had an old version in the original post. I just updated it to version 3.0 - it should no longer be using "speed600" and have JUST "setspeed" (with links created for setmax, setmin, and setgov). Run the installer again with that new file, and then type "setspeed reinstall" and it should clear it all up for you.

 

Do the install for the latest copy as listed in the first post (run sh /sdcard/setspeed.txt).

Then type "setspeed reinstall" to force it to wipe out and reinstall all remnants of old versions.

It's a mess, I know. I think in the future I will just release things in the update.zip format and have them install themselves directly in /system/xbin without needing any of this self-install stuff.

 

Not sure why that is. I use busybox mount, so that could be part of it.

Interesting. It's doing that for me, too. It used to NOT allow that - any invalid number you put in would just be ignored, so when you read it back out, it will be valid. That's the error checking that I was using.

When I manually set frequencies, it does the same thing. Odd. It will still work with the wrong frequency in there, it just won't make much sense. If you have slots at 600,700,800 and set your max to 799, you will only get a max of 700. Try typing "setmax" without any parameter to get the list of available frequencies.

It does still catch frequencies outside of the valid range, though, and I don't think it will cause any problems.