• 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

n0m0n said:
Can you give me some examples?
I wouldn't know what to change them to.
Is there a standard?

Also after I edit how do I put it back in?
Click to expand...

If you are at 1.15 and 34
-if you want to keep the same speed, raise the voltage to 66
-if you want to keep the same voltage, lower the speed to 1 ghz

to put it back

-"adb push setscaling.sh /sdcard"
-"adb shell"
-"su"
-"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
-"cp /sdcard/setscaling.sh /system/bin"
-"chmod 755 /system/bin"
-"mount -o ro,remount -t yaffs2 /dev/mtd/mtdblock4 /system"
 
droider13 said:
If you are at 1.15 and 34
-if you want to keep the same speed, raise the voltage to 66
-if you want to keep the same voltage, lower the speed to 1 ghz

What will 11.5 66, or 1g 34 give me in respect to performance, and or battery?

Thanks
Click to expand...
 
n0m0n said:
droider13 said:
If you are at 1.15 and 34
-if you want to keep the same speed, raise the voltage to 66
-if you want to keep the same voltage, lower the speed to 1 ghz

What will 11.5 66, or 1g 34 give me in respect to performance, and or battery?

Thanks
Click to expand...

1.15 slightly better performance, probably not noticeable. 1 ghz at 34(low voltage) should give you better battery life. Personally I would get as high as I could go with keeping 34 voltage. So for me I am at 1.15 with 34
Click to expand...
 
A stupid question: you cant install a kernel via update.zip and go into bootloader with something like Quickboot?
 
1150000 at 38 is working very nicely for me.

has ANYONE stabilized 1200000 or something greater than 1.15ghz? if so what clock rate and voltage?
 
auracle2g said:
1150000 at 38 is working very nicely for me.

has ANYONE stabilized 1200000 or something greater than 1.15ghz? if so what clock rate and voltage?
Click to expand...

I would say that I was very close to doing it
I only got two reboots the whole day with 1.2 ghz at 34
I am guessing that if I raised the voltage to 66 then it would be stable
 
n0m0n said:
OK so I reconnected my device to my USB cable.
Connections is PC Mode
entered: "adb shell"
got a: "$" entered "SU"
Looked at my device notifications and there was no request for permission.

Do I start with adb shell?
Is PC Mode correct?
Where should I find the request?
Click to expand...

SU is not su... all command line interactions are case sensitive and must be typed in exactly as shown....
 
n0m0n said:
was able to overclocking part, and setup the survive a reboot.
So I guess I did both part, right?
Click to expand...

So you are good.
Then edit the setscaling.sh file with notepad ++ and then push it back with the commands I gave you and then reboot
 
Got it to work using the root explorer method.haha go figure. Thanks all.



edit-changed some typos due to swype!
 
Can anyone tell me how I can revert to the default clock?
I followed the instructions earlier in full and every reboot (yes every) returns me to the overclocking input. (11.5 34).
I deleted the files that i put on the SDCard but after a reboot its still the overclock spec's.

My problem is hat my device is constantly rebooting ever few minutes and it started when after I overclocked.
Maybe my device doesn't like the changes.

Anyway how can I get back to where I started form?

Thanks
 
n0m0n said:
Can anyone tell me how I can revert to the default clock?
I followed the instructions earlier in full and every reboot (yes every) returns me to the overclocking input. (11.5 34).
I deleted the files that i put on the SDCard but after a reboot its still the overclock spec's.

My problem is hat my device is constantly rebooting ever few minutes and it started when after I overclocked.
Maybe my device doesn't like the changes.

Anyway how can I get back to where I started form?

Thanks
Click to expand...

Delete the overclock.ko and .sh files also then reboot
 
n0m0n said:
I did that I deleted the 2 files on the SDCard and when I went back into setCPU its not changing.
I tried the auto config option in setCPU and its still 11.5
Click to expand...

delete the setscaling.sh and the install-recovery.sh one also
 
n0m0n said:
Did that and its still 11.5 after reboot.
Click to expand...

when you say 11.5 do you mean 1.15 ghz that could cause a problem

And I would say just try running Fab's part of the guide again and then run

adb shell
su
overclock.sh 1000000 66
 
droider13 said:
when you say 11.5 do you mean 1.15 ghz that could cause a problem

And I would say just try running Fab's part of the guide again and then run

adb shell
su
overclock.sh 1000000 66
Click to expand...

When I read the setscaling.sh with root explorer its the over clock file.
11.5 900 and so on and next to each # it says overclock
 
does this backup the stock setscaling.sh somewhere?
I want to go back tot he stock file how do I do that?
 
You must log in or register to reply here.
Back
Top Bottom