Eclipse Overclock + Governor
#1
Posted 08 November 2012 - 07:57 AM
This mod is for all the people who didn't get bumped up to 1200MHz when installing ICS. In addition, I added the 90modules file to run different governors such as Smartassv2. I prefer to run these non-moto governors to help with battery life after using the Overclock mod. Nitro has added a few governors in Eclipse for us to use.
Download this to your phone--
Link:
Using a File explorer app such as Root Explorer or Root Browser...Do the following:
Extract the zip on your phone. You will have 3 files now: 98cpu12, 90modules, and cpu_control.ko
Move 98cpu12 to /system/etc/init.d
Change permissions to: rwxr-xr-x - Screenshot:
Change Ownership to: root-root - Screenshot:
Move 90modules to /system/etc/init.d
Change permissions to: rwxr-xr-x - Screenshot:
Change Ownership to : root-root - Screenshot:
Move cpu_control.ko to /system/lib/modules
Change permissions to: rw-r-r - Screenshot:
Change Ownership to: root-root - Screenshot:
Reboot your phone
Using SetCPU app or anything similar, you will notice your at 1200MHz now and you have more governor options. You can now set which governor you want to use at boot.
**THANKS**
I did not create this mod or make these scripts, so all the thanks goes to the developer(s) that did.
Thanks to timmy10shoes for teaching me this method and everything else.
Thanks to Nitro for Eclipse.
- johnlgalt likes this
#2
Posted 08 November 2012 - 02:13 PM
I have a 4 slot.
The way I overclock is as follows:
I wrote the following script for my preferred overclocking in Rom Toolbox Lite (I have since upgraded to Pro, but lite works fine for this)
as follows:
echo 0 300 1025 > /proc/cpu_control/tweak_cpu
echo 1 600 1200 > /proc/cpu_control/tweak_cpu
echo 2 900 1350 > /proc/cpu_control/tweak_cpu
echo 3 1225 1405 > /proc/cpu_control/tweak_cpu
I click on "set at boot" command built into the Scripter app within Rom Toolbox - you click on your script and the 5th option and bingo, the script runs at boot!
Way easier for a noobish guy like me than the whole init.d thing.
So for you kids out there that want your overclock to survive a boot, use the "Scripter" tool in Rom Toolbox (lite or Pro). the Lite version is free.
but know this. after each line you write in the script, when you enter a carriage return, it appears as though you are on the same line. You are not. when you open the script again, it appears on 4 lines.
Now when I boot, the No frills CPU control (as well as Tweakerz) shows "1225" as the max speed. Yeah!
I have no idea about undervolting.
I use pegasusq and cfq and get great battery life with my zippy overclocked 4 slot.
- samb likes this
#3
Posted 08 November 2012 - 03:59 PM
#4
Posted 08 November 2012 - 04:29 PM
Thanks for this. But does this distinguish between 4 and 5 slot bionics?
I have a 4 slot.
The way I overclock is as follows:
I wrote the following script for my preferred overclocking in Rom Toolbox Lite (I have since upgraded to Pro, but lite works fine for this)
as follows:
echo 0 300 1025 > /proc/cpu_control/tweak_cpu
echo 1 600 1200 > /proc/cpu_control/tweak_cpu
echo 2 900 1350 > /proc/cpu_control/tweak_cpu
echo 3 1225 1405 > /proc/cpu_control/tweak_cpu
I click on "set at boot" command built into the Scripter app within Rom Toolbox - you click on your script and the 5th option and bingo, the script runs at boot!
Way easier for a noobish guy like me than the whole init.d thing.
So for you kids out there that want your overclock to survive a boot, use the "Scripter" tool in Rom Toolbox (lite or Pro). the Lite version is free.
but know this. after each line you write in the script, when you enter a carriage return, it appears as though you are on the same line. You are not. when you open the script again, it appears on 4 lines.
Now when I boot, the No frills CPU control (as well as Tweakerz) shows "1225" as the max speed. Yeah!
I have no idea about undervolting.
I use pegasusq and cfq and get great battery life with my zippy overclocked 4 slot.
Your script is very similar to 98cpu12:
#!/system/bin/sh
busybox mount -o remount,noatime,barrier=0,nobh /system
busybox mount -o remount,noatime /data
busybox mount -o remount,noatime,barrier=0,nobh /cache
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 300 1025 > /proc/cpu_control/tweak_cpu
echo 1 575 1195 > /proc/cpu_control/tweak_cpu
echo 2 800 1320 > /proc/cpu_control/tweak_cpu
echo 3 1200 1388 > /proc/cpu_control/tweak_cpu
echo 4 1270 1400 > /proc/cpu_control/tweak_cpu
- johnlgalt and idivorceyou like this
#5
Posted 08 November 2012 - 04:29 PM
Thanks for the tutorial, works great on my 4 slot.
Welcome!
#6
Posted 08 November 2012 - 05:03 PM
Seriously, thanks for this - I am one of the ones that never got 1.2 GHz (and when I FXZ to .246 final, I bet I won't then either). However, I plan to try something (maybe stupid?) and see if I can get it working or not. But, I think I am also on a 4 slot CPU, and if so, then I know it ain't gonna work....
If not, then at least I'll have this
#7
Posted 08 November 2012 - 06:19 PM
#8
Posted 08 November 2012 - 06:53 PM
Yay! eye-dea is posting here!
Seriously, thanks for this - I am one of the ones that never got 1.2 GHz (and when I FXZ to .246 final, I bet I won't then either). However, I plan to try something (maybe stupid?) and see if I can get it working or not. But, I think I am also on a 4 slot CPU, and if so, then I know it ain't gonna work....
If not, then at least I'll have this
Right on John. You still on .247 and stock? You can get init.d support on stock and overclock, if needed.
#9
Posted 08 November 2012 - 07:06 PM
yea i got 2 4 slot bionics in a row, upsetting but not the end of the world. OC potential is determined by more than just slots, you could have a 5 slot and be unstable at anything beyond 1200 but i currently have a 4 slot that handles 1350 comfortably. at that stability and speed, who the hell cares about an extra slot just run that ::woof:: on performance and pwn noobs ;-)
My slot five hates 1300+ ,so yeah...just because you have a 4 slot doesn't mean it's crippled!
#10
Posted 09 November 2012 - 08:08 AM
My personal "revelation" was using the scripter applet in Rom Toolbox, which for a noobish guy like me made the whole overclocking thing very easy.
I then wrote another script (very simple: just edited my overclock script, inserted stock values, and gave it a new name) I call "clock to stock" which will restore all the stock values (duh).
#11
Posted 10 November 2012 - 01:03 PM
Replaced oc.zip with oc2.zip-
Fixed 90modules script: There was an error in the script that didn't allow sio scheduler to be recognized. If you have the old 90modules and want to use the sio scheduler then edit the 90modules script from sio_iosched.ko to sio-iosched.ko (just replace the _ with a -) and reboot. Or you can download the new oc2.zip, delete the old 90modules, then add the new 90modules (redo permissions and ownership) and reboot.
- Voyeur likes this
#12
Posted 10 November 2012 - 02:29 PM
#13
Posted 10 November 2012 - 04:48 PM
#14
Posted 10 November 2012 - 04:49 PM
Attached Files
- idivorceyou likes this
#15
Posted 10 November 2012 - 04:56 PM
Attached Files
#16
Posted 10 November 2012 - 05:12 PM
Attached Files
- idivorceyou likes this
#17
Posted 10 November 2012 - 09:24 PM
Is this only for the Eclipse Rom or will this work on stock?
Yes, it will work on stock if you have init.d support.
#18
Posted 10 November 2012 - 09:24 PM
Wow!!!
NICE!!!
#19
Posted 18 November 2012 - 01:57 PM
Right on John. You still on .247 and stock? You can get init.d support on stock and overclock, if needed.
I was, until today. I FXZd back to .246 and will see what I have. I'm betting I have a 4 slot CPU....
How does one ascertain the number of available slots?
#20
Posted 18 November 2012 - 03:49 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users