Able to move the slider only one time then it freezes everything so bad I have to pull battery. Any ideas on fixes?
95% chance that you are jacking up the frequency too high - nothing to do with the installation at all. That's why the phone froze.
Some phones can be OC'ed very high (in excess of 800 Mhz), and some can not - the frequency at which each individual phone goes unstable is different.
The instructions (scattered all over the web) for SetCPU tell you to do a couple of things:
- Start your OC tests at a low frequency - say 710 Mhz, and
SLOWLY increase the max frequency. What is meant by "slowly" is this: set it to a given max value, and then use the phone
for a day or two before you increase it again. You should NEVER have a spontaneous OS crash or phone freeze in that period for that (max) frequency to be judged acceptable.
- Never set the toggle "Set on Boot" until after you have run the phone for a long time - maybe as much as a week - at your new highest (max) frequency. The reason for this is that if you set it too high, and then turn on "Set on Boot", your phone could crash immediately when it boots - and that will prevent you from going in and turning off "Set on Boot".
If you are the impatient type, you can try the following to figure out what your "never-go-this-high" max frequency is:
First, back up your phone with a Nandroid backup before you begin. Crashing your phone, or yanking the battery is never good for the health of the filesystems in NAND memory - so you better have something to restore in case your "speed testing" wrecks your file systems.
Go in to SetCPU and:
1 turn off profiles. (Don't delete them, just turn them off)
2 Make sure "Set on Boot" is unchecked.
3 Set the min speed in the Main tab to 528, and the max speed to 710.
4 Set the Scaling governor to "performance"
5 Bump up the max frequency ("Main" tab) by one notch
6 Go into the "Info" tab and run a "Stress Test" for 30 seconds.
7 If the phone didn't crash or freeze during the stress test (or before), repeat steps 5 and 6
Eventually the phone will crash or freeze doing this. Clearly, you don't want your clocking to
ever be this high, because you got a crash immediately.
This procedure does NOT guarantee that the next lower setting is safe. The reason for this is because the maximum speed your phone can be clocked for stable operation depends on battery voltage and temperature of the unit - so all this test tells you for sure is that you need to back off from this frequency, as it is impossible to use - you need to go lower than this, and possibly quite a bit lower to insure stable operation at all temperatures and battery charge states.
After the battery pull/reboot, go back into SetCPU and change the Scaling governor back to "ondemand" - and drop the max speed back to something reasonable. (If starting up SetCPU manually freezes the phone right away, reboot the phone, go in to Settings -> Applications -> Manage Applications -> SetCPU, and "Clear data", uninstall SetCPU, and then reinstall it).
One more thing - setting aside issues of stability, overclocking is dangerous from a thermal perspective. The Eris was designed "thermally" to operate at 528 Mhz. When you overclock, especially continuously, you run the risk of literally "burning out" your phone.
You might be tempted to say, "well, I'm only overclocking to 729 Mhz" - that's only a 38% increase." But you would be wrong, because the supply voltage to the CPU is increased when the frequency is stepped up, and the amount of power which is dissipated compared to the baseline
grows faster than in proportion to the clock frequency.
We had a contributor to AF burn his phone out in less than a week.
Not only that, but because you are burning up a lot of power at higher clock speeds - faster than the increase due to clock speed - you will eat through your battery life rapidly. You will find out that even if your phone can be operated at 806 Mhz, you won't want to do that anyways, because your battery life will suck.
Hope that helps
eu1
) nowadays and that this post was never updated. It also might only apply to his kernel...don't know if other ROMs are built with Zanfur's, but I suspect they are.
