• 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

Remove the setscaling.sh file. You're going to have to find the settings correct for you. I would reboot at 1.15/34, so i changed it to 1.1/34 in the setscaling file and im running GREAT now.
So your saying remove the setscaling file. Then just go into terminal and just iinput a new freq. And volt. Will that create a new setscaljng file in the phone
 
So your saying remove the setscaling file. Then just go into terminal and just iinput a new freq. And volt. Will that create a new setscaljng file in the phone

no you can edit the setscaling.sh either on your computer or in Root Explorer and then overwrite the old one

I recommend using Notepad++ for editing the file on your computer
 
It is necessary to have a setCPU profile set up to go along with the overclocking? This is pretty new to me so I really not sure how to set up a profile.
 
If you press the Menu and Home buttons at the same time, it brings up a display of your most recent apps, making switching between RE, terminal emulator, SetCPU and your browser quick and easy...

I think you are referring to holding the home button, you don't have to hold menu also
 
LOL.... i'm new to android... not new to *nix... Operating Systems of the Unix variety for the n00bs... maybe i should take the android tutorial... lol
 
I am doing EVERYTHING to the T (as far as I know)

I run it through ADB, when I reboot--the OC doesn't stick. I look on my SD card via root explorer and I see both the setscaling and install recovery files....

When I am done step 3 (adb) do I just shut it off without exiting out of cmd prompt? Or do I have to write in a specific command before I shut off the phone to try the reboot.


I am in charge mode and I have tried it in mass storage mode, but when I did the latter, the install recovery and setscaling files didn't stick onto the SD card after removing the phone from my computer.
 
I am doing EVERYTHING to the T (as far as I know)

I run it through ADB, when I reboot--the OC doesn't stick. I look on my SD card via root explorer and I see both the setscaling and install recovery files....

When I am done step 3 (adb) do I just shut it off without exiting out of cmd prompt? Or do I have to write in a specific command before I shut off the phone to try the reboot.


I am in charge mode and I have tried it in mass storage mode, but when I did the latter, the install recovery and setscaling files didn't stick onto the SD card after removing the phone from my computer.

First try doing it in Pc mode that is what I did
 
Assuming everything went well with just setting up the overclocking part yes you can start at step 2

Yea it did, because I tested it by just doing it the original way and not the save for reboot way---and my setcpu showed an increase to 1.1ghz.

Ok, testing in PC mode, brb.
 
Yea, same thing...reboot and nothing--attached is a copy of my command line, not sure if you can see if anything is wrong with it or not. I am confused because I am almost positive I am doing everything correctly, but clearly I am not.


Picasa Web Albums - bosox2k1

Just make sure you zoom in using the magnifier, otherwise it's too small.
 
Yea, same thing...reboot and nothing--attached is a copy of my command line, not sure if you can see if anything is wrong with it or not. I am confused because I am amost positive I am doing everything correctly, but clearly I am not.


Picasa Web Albums - bosox2k1

Just make sure you zoom in using the magnifier, otherwise it's too small.

can you open up the install-recovery.sh you are using and make sure there are two lines at the bottom of it. The first one starts with insmod and the second one with setscaling are those there
 
Looks like it's there...That's what is in my sdk/tools folder...


#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:37dc5be28fe8cdeb61eae1347fdccf2e201af07e; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:4194304:0c459f9fab93d51a3b09516c415f63352ec9eb02 MTD:recovery 22727909bf9e1f0f844f41484d2a9cf9b6cc49ee 5242880 0c459f9fab93d51a3b09516c415f63352ec9eb02:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi

insmod /system/lib/modules/overclock.ko
setscaling.sh
 
Okay thats there
You already have overclock.ko and .sh installed

Tell me what happens when you do
adb shell
su
cat /system/bin/setscaling.sh
 
using terminal emulator

typing in

busybox rmmod overclock

when i enter the command i receive this

rmmod: chdir(/lib/modules): No such file or directory

am I missing a file? (Because I dont remember downloading any files every named busybox or rmmod) OR is there more to the command? im confused i want to fine tune my overclock on my Droid X.

Please help me out my knowledgeable friends.
 
Okay thats there
You already have overclock.ko and .sh installed

Tell me what happens when you do
adb shell
su
cat /system/bin/setscaling.sh

wish i could cut and paste, haha

echo 1150000 > /proc/overclock/max_rate
echo 1 400000000 22>
echo 2 600000000 26
echo 3 900000000 30
echo 4 1150000000 38
echo 0 1150000000


etc etc
Obviously I left out a lot, let me know if you need exactly what happened.
Does that mean it worked?
 
using terminal emulator

typing in

busybox rmmod overclock

when i enter the command i receive this

rmmod: chdir(/lib/modules): No such file or directory

am I missing a file? (Because I dont remember downloading any files every named busybox or rmmod) OR is there more to the command? im confused i want to fine tune my overclock on my Droid X.

Please help me out my knowledgeable friends.

See if typing in "su" first helps
 
Back
Top Bottom