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

Root Droid X 2.2 Overclock (Kernel Module w/Instructions)

Jump to latest Follow Reply
Sort by date Sort by votes
#253
OK, a few quick questions.

(I've gotten everything working before. Got up to 1.4GHz for about 5 minutes)

Is there a way that I dont have to do this part everytime is reboots:

Code: 
$ su
# cd /sdcard/extracted/droidx_22_oc (or wherever you extracted the files to)
# mount -o rw,remount -t ext3 /dev/block/mcblk1p21 /system
# cp overclock.ko /system/lib/modules/overclock.ko
# cp setscaling.sh /system/xbin/setscaling.sh
# chmod 644 /system/lib/modules/overclock.ko
# chmod 755 /system/xbin/setscaling.sh

It gets really obnoxious after a while. (Having to redo it every time)

I also had something wierd happen.. I ran 1.1 fine, got up to 2.2 fine. jumped to 1.4, and an semi-instant crash.. did it again, it ran longer. I tried 1.3, and it was an instant crash as well. (trying to get into setCPU) Is it odd that 1.4 worked longer than 1.3?

Also, can someone maybe do a quick write up on the setscaling script? I get what is the GHz and whats the Voltages, but can someone explain a little more indepth how they interact, and what changing them will do? (obvoiusly lower V is more batterly life, but more in depth?)
 
Upvote 0
#254
Airmaxx23 said:
Your setscale script. You can use root explorer to change the values, the setscale.sh file is in system/xbin. Once you've edited it press on it and select "execute".
Click to expand...

Ok so I just have to edit the setscaling100.sh (for me anyways others might have the setscaling.sh) then execute. Once I think it's stable I can do the other -recovery command to make it stick on reboot?

What's the best way to test stability? using setcpu? and where do I find what speed my phone is currently running at?

If I use setcpu autodetect and I check "set on Boot" will these setting stick? It seems to be reading the setting I've given it so I assume that would work?
 
Upvote 0
#255
Ok i've got a question. My phone is stable at around 1.225 with these settings
echo 65 > /proc/overclock/max_vsel
echo 1225000 > /proc/overclock/max_rate
echo 1 400000000 27 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1225000000 65 > /proc/overclock/mpu_opps
echo 0 1225000 > /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

Now if I just change to 1300,without changing anything else it starts to turtle. never reboots just goes really slow. If i were to tweak my settings should I raise or lower the voltages of the other echoes? Whats the difference? What i'm asking is, if your phone turtles does that mean you should raise voltage? Or is it all just crossing your fingers?
 
  • Like
Reactions: w8-4-me
Upvote 0
#256
joe772 said:
OK, a few quick questions.

(I've gotten everything working before. Got up to 1.4GHz for about 5 minutes)

Is there a way that I dont have to do this part everytime is reboots:

Code: 
$ su
# cd /sdcard/extracted/droidx_22_oc (or wherever you extracted the files to)
# mount -o rw,remount -t ext3 /dev/block/mcblk1p21 /system
# cp overclock.ko /system/lib/modules/overclock.ko
# cp setscaling.sh /system/xbin/setscaling.sh
# chmod 644 /system/lib/modules/overclock.ko
# chmod 755 /system/xbin/setscaling.sh
It gets really obnoxious after a while. (Having to redo it every time)

I also had something wierd happen.. I ran 1.1 fine, got up to 2.2 fine. jumped to 1.4, and an semi-instant crash.. did it again, it ran longer. I tried 1.3, and it was an instant crash as well. (trying to get into setCPU) Is it odd that 1.4 worked longer than 1.3?

Also, can someone maybe do a quick write up on the setscaling script? I get what is the GHz and whats the Voltages, but can someone explain a little more indepth how they interact, and what changing them will do? (obvoiusly lower V is more batterly life, but more in depth?)
Click to expand...

The only commands you need to run each time are:
insmod /system/lib/modules/overclock.ko
setscaling.sh

You can use the gscript app to save the commands and then just one press will execute them for you.
 
Upvote 0
#257
thefamousmoe said:
Ok i've got a question. My phone is stable at around 1.225 with these settings
echo 65 > /proc/overclock/max_vsel
echo 1225000 > /proc/overclock/max_rate
echo 1 400000000 27 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1225000000 65 > /proc/overclock/mpu_opps
echo 0 1225000 > /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

Now if I just change to 1300,without changing anything else it starts to turtle. never reboots just goes really slow. If i were to tweak my settings should I raise or lower the voltages of the other echoes? Whats the difference? What i'm asking is, if your phone turtles does that mean you should raise voltage? Or is it all just crossing your fingers?
Click to expand...


raise the voltage first.
 
Upvote 0
#259
Airmaxx23 said:
It's been running for 24 hours now with no reboots. Here is the scale that I've using.

echo 65 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 1000000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 65 > /proc/overclock/mpu_opps
echo 0 1400000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
Click to expand...

fuuuuuuu wish i cud get these settings to work
 
Upvote 0
#260
OK I am confused, and new to the adb or terminal thing.

These commands, are they entered on the phone, or are they entered by computer connected to the phone. What do I need on the phone and on the computer?

is there terminal emulator on the phone itself? I suppose the build props work the same way. I had trouble loading those last night too.
 
Upvote 0
#264
Code: 
echo 68 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 400000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 68 > /proc/overclock/mpu_opps
echo 0 1400000 > /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

Stable for 19 hrs now with no reboots. Battery life is awesome with moderate to heavy use for about 4 hrs yesterday. Started with 80% and sitting at 30% now.
 
Upvote 0
#267
Airmaxx23 said:
It's been running for 24 hours now with no reboots. Here is the scale that I've using.

echo 65 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 1000000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 65 > /proc/overclock/mpu_opps
echo 0 1400000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
Click to expand...

You've increased your voltage by 11% at the bottom end and by 16% at the top. That with the 40% overclock at the top end (and the fact that the processor spends nearly all it's time at either the top or bottom, I'm wondering how this'll translate into battery life. Since you're our intrepid pioneer here, let the rest of us know how it's working out, will you?
 
Upvote 0
#268
humungus said:
You've increased your voltage by 11% at the bottom end and by 16% at the top. That with the 40% overclock at the top end (and the fact that the processor spends nearly all it's time at either the top or bottom, I'm wondering how this'll translate into battery life. Since you're our intrepid pioneer here, let the rest of us know how it's working out, will you?
Click to expand...

I bumped up to 1.45 GHz this morning and so far so good (3.5 hours). I charge my phone at night when I go to bed so as long as it can make it through a 16ish hour period I'm happy with it. The battery life has been fine so far.

Edit: 1.45 just crashed, back to 1.4 for now.
 
Upvote 0
#269
joe772 said:
Is there a way that I dont have to do this part everytime is reboots:

Code: 
$ su
# cd /sdcard/extracted/droidx_22_oc (or wherever you extracted the files to)
# mount -o rw,remount -t ext3 /dev/block/mcblk1p21 /system
# cp overclock.ko /system/lib/modules/overclock.ko
# cp setscaling.sh /system/xbin/setscaling.sh
# chmod 644 /system/lib/modules/overclock.ko
# chmod 755 /system/xbin/setscaling.sh

It gets really obnoxious after a while. (Having to redo it every time)
Click to expand...

I've noticed that when using cmd, all of the commands in adb get saved. This makes is really easy to repeat the code to try out different settings. This is what I do:

  • 'adb shell'
  • Follow the steps in the OP using whichever settings you prefer.
  • Unplug the phone and keep cmd open. (or you can just hit 'exit' twice, however you prefer to get out of shell.)
  • Once you are ready to try a different setting out, plug the phone back in. (if you chose to unplug it.)
  • Do 'adb shell' again..
  • Once you are there, hit the up button repeatedly and it will scroll up through all of the commands... Once you get to 'su', hit enter.
  • Now you can press down, enter, down, enter, etc, to run through the commands easily.
  • After the second run, unplug the phone again. (or 'exit' twice.)
  • From now on, as long as you keep cmd open (from the third time on), after you are in 'adb shell', just press the down button and it will run through (you won't have to scroll up through the commands anymore.)
This will let you run through the entire thing without having to copy all that again.

One important thing to note is that if you don't reboot the phone, you will have to throw in the command 'rmmod overclock.ko' otherwise you will get an error saying it already exists.. I enter this in right above 'insmod /system/lib/modules/overclock.ko'. Do this the first time to make it easy on yourself. It WILL give you an error the first time, just ignore this and keep going, this way it is saved for the rest of your attempts.

Hope this helps.. I'm sure there are easier ways, but if you are using adb, it will make it a breeze. (This is all Win 7, dunno if that matters.)
 
Upvote 0
#270
Airmaxx23 said:
The only commands you need to run each time are:
insmod /system/lib/modules/overclock.ko
setscale.sh

You can use the gscript app to save the commands and then just one press will execute them for you.
Click to expand...

So even though it resets the setscale every reboot, it saves all of the copies from the other commands? So i can just push a new set scale to my /xbin/ and then run insmod and the script? Sweet. Thanks.
 
Upvote 0
You must log in or register to reply here.

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones

Best Android Phones

See All
  1. Google Pixel 8 Pro Check Price
  2. Samsung Galaxy S23 Ultra Check Price
  3. Samsung Galaxy Z Fold5 Check Price
  4. Google Pixel 8 Check Price
  5. Samsung Galaxy S23 Check Price

Upcoming

See All
  1. Samsung Galaxy S24 Early Access

Best iPhones

See All
  1. Apple iPhone 15 Pro Max Check Price
  2. Apple iPhone 15 Pro Check Price
  3. Apple iPhone 15 Plus Check Price
  4. Apple iPhone 15 Check Price
  5. Apple iPhone SE (2022) Check Price

Upcoming

See All
  1. Apple iPhone 16 Early Access

Tablets

Best Tablets

See All
  1. Samsung Galaxy Tab S9 Ultra Check Price
  2. Apple iPad Pro (2022) Check Price
  3. Apple iPad Air (2022) Check Price
  4. Apple iPad Mini (2021) Check Price
  5. Microsoft Surface Pro 9 Check Price

Upcoming

See All
  1. Apple iPad Air 6 Early Access
  2. Apple iPad Fold Early Access

Laptops

Best Laptops

See All
  1. Apple Macbook Pro Check Price
  2. Apple Macbook Air (2023) Check Price
  3. Dell XPS 13 Check Price
  4. Acer Chromebook Spin 714 Check Price
  5. Dell Alienware m18 (2022) Check Price

Upcoming

See All
  1. Microsoft Surface Laptop 6 Early Access
  2. Microsoft Surface Pro 10 Early Access

Televisions

Best TVs

See All
  1. Samsung The Frame TV Check Price
  2. Samsung Neo QLED 4K QN90C Check Price
  3. LG G3 OLED Check Price
  4. LG A2 OLED Check Price
  5. ROKU Plus Series Check Price
  6. Samsung S90C OLED Check Price
  7. SunBriteTV Veranda 3 Check Price

Upcoming

See All
  1. Hisense 110UX ULED X TV Early Access

Game Consoles

Best Game Consoles

See All
  1. Nintendo Switch OLED Check Price
  2. Microsoft XBOX Series X Check Price
  3. Sony Playstation 5 Check Price
  4. Microsoft XBOX Series S Check Price
  5. Nintendo Switch Lite Check Price

Upcoming

See All
  1. Nintendo Switch 2 Early Access

Wearables

Best Wearables

See All
  1. Oura Ring 3 Check Price
  2. Apple Watch Series 9 Check Price
  3. Google Pixel Watch 2 Check Price
  4. Samsung Galaxy Watch 6 Classic Check Price
  5. Fitbit Inspire 3 Check Price
  6. Amazfit Amazfit Band 7 Check Price
  7. Apple Watch SE Check Price
  8. Apple Watch Ultra 2 Check Price

Upcoming

See All
  1. Samsung Galaxy Watch 7 Early Access

Smart Home

Smart Home Tech

See All
  1. Amazon Echo (4th Gen) Check Price
  2. Schlage Encode Smart Lock Check Price
  3. Amazon Blink Smart Cameras Check Price
  4. Google Nest Thermostat Check Price
  5. Phillips Hue Smart Lights Check Price

Upcoming

See All
  1. Apple Homepod Vision Early Access

Similar threads

JayzTwoDimes
Root How to get KitKat + Overclock + working vibration + camfix for ov5693 cam/12b [UPDATE NOV. 14 2015]
Replies
10
Views
8K
Smartphones
JayzTwoDimes
JayzTwoDimes
scary alien
Rooting, OTAs, and Bootloops (oh my! :)
Replies
5
Views
11K
Rooting
scary alien
scary alien
mrg666
Root [KERNEL] MiRaGe - SPH-M950/icon optimized for stock JB MD6/MI2 - 10222013
Replies
204
Views
27K
Smartphones
saddam1
S
mrg666
Root [KERNEL] MiRaGe - for HTC stock ICS ROM - 3.0.101 - 10222013
Replies
286
Views
25K
Smartphones
mrg666
mrg666
F
Root Droid 2 Overclock(Kernel Module+Instructions)
Replies
94
Views
30K
Smartphones
DeadDude
D
Top Bottom
Back
Jump to latest Follow Reply
Jump to latest Follow Reply