-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Please help overclock
- Thread starter -Ax-
- Start date
-
- Tags
- htc evo 4g
JB in AZ
Android Expert
Moved for ya!
An UrgeTo Dance
The Hero of the Winds
You will need a new kernel to go higher, if you want to see which one you are on now it should be in settings>about phone. Sorry i can't suggest any for you I'm not that familiar with AOSP kernels.
WarDamnEagle09
Newbie
I'm using a 2.6.37 SavageZen 0.0.9-BFS-HAVS-WiMAX-GB+ on CM7 it goes to 1190400, some go higher.
However, I've installed some kernels that went higher, I set it higher and checked "Set on Boot" and ended up in a loop where once Set CPU loaded it couldn't handle it and rebooted over and over.... until finally I was fast enough to open Set CPU before it set the CPU so high, and move the CPU lower. Sooo... careful.
I would search CM's website forum and xda to see what people are using. They recommend a bunch, don't remember how I landed on this SavageZen one but someone convinced me and I've been very happy with it.
Happy Flashing.
However, I've installed some kernels that went higher, I set it higher and checked "Set on Boot" and ended up in a loop where once Set CPU loaded it couldn't handle it and rebooted over and over.... until finally I was fast enough to open Set CPU before it set the CPU so high, and move the CPU lower. Sooo... careful.
I would search CM's website forum and xda to see what people are using. They recommend a bunch, don't remember how I landed on this SavageZen one but someone convinced me and I've been very happy with it.
Happy Flashing.
How is your phone actually running right now? If you flash a kernel that allows you to go higher, likely, you won't notice a huge difference between what you're overclocking to now, and what you'll be able to overclock to after. If your phone is running smoothly now, you might want to keep that in mind.
Also, a quick fyi on the bootloop issue due to leaving "set at boot" enabled. You should most definitely uncheck that option before testing the frequency max, as you can easily end up in a bootloop. I've even made that mistake before (more than once
). Anyway, there *is* a fairly quick way out of it. Just boot into recovery, connect your phone to your computer, and mount the sdcard to your computer. Create a file named setcpu_safemode (it can be empty), and copy it to the root of your sdcard. It's basically just a flag file. That means that when the boots up, before the setcpu settings take effect, it will see that file, and disable your custom settings, preventing the phone from locking up.
Also, a quick fyi on the bootloop issue due to leaving "set at boot" enabled. You should most definitely uncheck that option before testing the frequency max, as you can easily end up in a bootloop. I've even made that mistake before (more than once
). Anyway, there *is* a fairly quick way out of it. Just boot into recovery, connect your phone to your computer, and mount the sdcard to your computer. Create a file named setcpu_safemode (it can be empty), and copy it to the root of your sdcard. It's basically just a flag file. That means that when the boots up, before the setcpu settings take effect, it will see that file, and disable your custom settings, preventing the phone from locking up.