• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [How-to] Overclock that survives a reboot

Lol... yes... I'm a noob. Figured I couldn't screw it up with one button. really only rooted so I could overclock, wireless tether (which I'm guessing verizon can't detect) and to apply the bad a$$ revo theme.
 
jonathanmsims said:
its asks me if I want to "overwrite the overclock.ko" once I paste in step 15. Do I want to do that?
Click to expand...

Yeah you do and when it asks you about the overclock.sh do that too. Since you already have those files installed it is doing them again the RE guide is from no overclock to overclock that survives a reboot. I will change the OP to reflect that and tell people which step to start on if they already have overclocking.
 
So I had my overclock set at 1.1 / 60 and was getting quadrants of 1300+. Now I did the steps in the OP and I am getting in the low 1200's and I'm clocked at 1.15 / 40. Wondering what I did wrong. Did the files in the OP overwrite my previous overclocking? I follow instructions very well, just don't know whats going on sometimes till someone actually explains it.
 
jonathanmsims said:
Wow... such random quadrant benchmarks... just did one and got 1334. Rebooted about 2 hours ago.
Click to expand...

Quadrant is pretty random... I've had back to back runs go from just under 1200 to just over 1350...

Did you ever get everything working right? What you need to do is edit your setscaling.sh with settings that work for you. Here is what it looks like in my setscaling.sh:

Code: 
echo 44 > /proc/overclock/max_vsel
echo 1122000 > /proc/overclock/max_rate
echo 1 400000000 23 > /proc/overclock/mpu_opps
echo 2 700000000 28 > /proc/overclock/mpu_opps
echo 3 900000000 33 > /proc/overclock/mpu_opps
echo 4 1122000000 44 > /proc/overclock/mpu_opps
echo 0 1122000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

Code: 
Editings setscaling.sh in Root Explorer:
1. Open Root Explorer
2. Navigate to /system/bin
3. Mount R/W
3. Long press on setscaling.sh
4. Scroll to the bottom of the list and "Open in Text Editor"
5. Edit as needed.
6. Hit the Menu Button
7. Select Save

Now, if you did everything else in the RE Guide from the OP, your setscaling.sh should run at boot with the settings you edited in.
 
FreeWELL said:
Quadrant is pretty random... I've had back to back runs go from just under 1200 to just over 1350...

Did you ever get everything working right? What you need to do is edit your setscaling.sh with settings that work for you. Here is what it looks like in my setscaling.sh:

Code: 
echo 44 > /proc/overclock/max_vsel
echo 1122000 > /proc/overclock/max_rate
echo 1 400000000 23 > /proc/overclock/mpu_opps
echo 2 700000000 28 > /proc/overclock/mpu_opps
echo 3 900000000 33 > /proc/overclock/mpu_opps
echo 4 1122000000 44 > /proc/overclock/mpu_opps
echo 0 1122000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

Code: 
Editings setscaling.sh in Root Explorer:
1. Open Root Explorer
2. Navigate to /system/bin
3. Mount R/W
3. Long press on setscaling.sh
4. Scroll to the bottom of the list and "Open in Text Editor"
5. Edit as needed.
6. Hit the Menu Button
7. Select Save

Now, if you did everything else in the RE Guide from the OP, your setscaling.sh should run at boot with the settings you edited in.
Click to expand...

So if i noticed that my droid likes a little more voltage. Could i edit ur file with a few volts higher. And if i edit that file it will change the overclock once i reboot, correct?
 
jonathanmsims said:
So if i noticed that my droid likes a little more voltage. Could i edit ur file with a few volts higher. And if i edit that file it will change the overclock once i reboot, correct?
Click to expand...

Yes, I just used root explorer to go in and change the settings in my setscaling file and once I rebooted the changes were evident.
 
Figured it out. Had to set my overclock again. Then i went in and changed the setscaling file to the correct voltages and frequencies that i just set the max overclock to. Sitting at 1355 on the quadrents now. Also had to open setcpu.api and set it to max once i rebooted. Weird.
 
jonathanmsims said:
So if i noticed that my droid likes a little more voltage. Could i edit ur file with a few volts higher. And if i edit that file it will change the overclock once i reboot, correct?
Click to expand...

That'll work... if you have Terminal Emulator you can:

$ su
# setscaling.sh

And your changes will take effect without a reboot... but do a reboot to be sure that they take effect that way as well.... if not then you would need to make sure /system/etc/install-recovery.sh is loading overclock.ko and setscaling.sh at boot.
 
jonathanmsims said:
Figured it out. Had to set my overclock again. Then i went in and changed the setscaling file to the correct voltages and frequencies that i just set the max overclock to. Sitting at 1355 on the quadrents now. Also had to open setcpu.api and set it to max once i rebooted. Weird.
Click to expand...

Cool... if you change your frequencies, you will need to adjust setcpu accordingly. Probably best to run an Speed Autodetect in setcpu after frequency changes.
 
this all sounds like a lot of work for .1 difference. I'm probably going to wait until the process becomes much more simple with a custom/more stable kernel. I'm hoping we can OC this thing to 1.3 or 1.4 like with the hummingbird processor of the Galaxy S series.
 
jreed2560 said:
this all sounds like a lot of work for .1 difference. I'm probably going to wait until the process becomes much more simple with a custom/more stable kernel. I'm hoping we can OC this thing to 1.3 or 1.4 like with the hummingbird processor of the Galaxy S series.
Click to expand...

Yeah I agree but it is good experience for working with adb and I am really hoping we can get that high
 
yeah, for people who are new to command line and adb this would be good practice. I'm pretty familiar with it so thats why I'm holding off. Getting a custom kernel is really where this road is headed if you really want to push this thing anyway.
 
jreed2560 said:
yeah, for people who are new to command line and adb this would be good practice. I'm pretty familiar with it so thats why I'm holding off. Getting a custom kernel is really where this road is headed if you really want to push this thing anyway.
Click to expand...

Hopefully birdman's work can also get us custom kernels
 
So i finally got a stable overclock at 1.1ghz / 60 with quadrents of 1300+ consistantly. With the following setscalling.sh config:
Code: 
 echo 60 > /proc/overclock/max_vsel
 echo 1100000 > /proc/overclock/max_rate
 echo 1 400000000 45 > /proc/overclock/mpu_opps
 echo 2 600000000 50 > /proc/overclock/mpu_opps
 echo 3 900000000 55 > /proc/overclock/mpu_opps
 echo 4 1100000000 60 > /proc/overclock/mpu_opps
 echo 0 1100000 > /proc/overclock/freq_table
 echo 1 900000 > /proc/overclock/freq_table
 echo 2 600000 > /proc/overclock/freq_table
 echo 3 400000 > /proc/overclock/freq_table

Here's the latest quadrant.
CAP201008172115.jpg
 
I posted this in the other "overclock" thread but figured it should be here also. Here is what the stock scaling is:

10000000 66
8000000 57
6000000 44
3000000 32
 
I could use some help with this. I was successful overclocking with the given example and ran well for a day with heavy use. I did step 2 (and all the rest), and after a reboot its back to the original settings. Do I just start all over from step one?
 
Rockee said:
I could use some help with this. I was successful overclocking with the given example and ran well for a day with heavy use. I did step 2 (and all the rest), and after a reboot its back to the original settings. Do I just start all over from step one?
Click to expand...

No you should still have the overclock.sh and .ko files there so just try doing the survive the reboot portion again
 
humungus said:
Thanks for this. Where'd you find it?
Click to expand...

Before I started messing around with the setscale.sh set up I was just using overclock.sh to try different settings. To check to see if the voltage was changing I used "cat /proc/overclock/mpu_opps" in the terminal emulator to see the settings.
 
droider13 said:
No you should still have the overclock.sh and .ko files there so just try doing the survive the reboot portion again
Click to expand...

Thanks, I must be missing something simple. No errors, reboots (knock on wood), but its maintaining the default settings. Are there any commands or anyway to make sure everything is set up right?
 
Rockee said:
Thanks, I must be missing something simple. No errors, reboots (knock on wood), but its maintaining the default settings. Are there any commands or anyway to make sure everything is set up right?
Click to expand...

reboot and see if its still there
 
You must log in or register to reply here.
Back
Top Bottom