• 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)

Again just for kicks...stagefright on so not real but still fun to see it get past 3000.

Running 1.5GHz @ 80. Going to turning it back down to 1.2GHz. Really don't see a need for the extra power.

5102440457_c809447528.jpg

I was using 1.4 GHz but the voltage needs to be higher than I'd like so I'm sticking with 1.32 GHz which I can run with a 60 vsel. I'm not noticing much of a boost in performance going from 1.32 to 1.4 so I'm staying there, for now.
 
likewise. the quadrant is kinda annoying now cuz u have to run it a couple times just to get high 1900 and mid 2000.

hey max what would be considered a high voltage?
 
likewise. the quadrant is kinda annoying now cuz u have to run it a couple times just to get high 1900 and mid 2000.

hey max what would be considered a high voltage?

I had to use 74ish to keep 1.4 GHz stable. On 2.1 the stock voltage was set to 66 so going above that (even though I know it ok to go slightly higher) just makes me a little nervous and I was happy with the battery life on 2.1. I'm really not noticing a difference between 1.4 and 1.32.
 
what r ur settings now? im on 1.47 with a max of 76. and trying to see how i can go about tweaking the low end and middles.
gets annoying at times to when trying to run quadrant and it goes to the quad homescreen in the middle of a test.

p.s: that quad of 2156 on 1.45 felt good. lol

also watching batt temp to on setcpu
 
mine is being a real b#$h about overclocking. 1.2 works but isn't stable (tried vsel from 70 to 78) 1.85 is real good and quadrant scores of a little under 1700. Trying 1.95 right now LOL
 
what r ur settings now? Im on 1.47 with a max of 76. And trying to see how i can go about tweaking the low end and middles.
Gets annoying at times to when trying to run quadrant and it goes to the quad homescreen in the middle of a test.

P.s: That quad of 2156 on 1.45 felt good. Lol

also watching batt temp to on setcpu

1320 - 60
900 - 48
700 - 38
300 - 26
 
what r ur settings now? im on 1.47 with a max of 76. and trying to see how i can go about tweaking the low end and middles.
gets annoying at times to when trying to run quadrant and it goes to the quad homescreen in the middle of a test.

p.s: that quad of 2156 on 1.45 felt good. lol

also watching batt temp to on setcpu

what are your low end #s on the 1.47?
i've been playing around with 1.45 and got a stable scaling, but battery drain sucks

<< who likes my new avatar =]
 
ok. now question.

say i went to bump to 1400. what values would YOU change. how much would u bump each.?

i.e. 1400 - 64
900 - 50
700 - 38
300 - 28

I'd try 1400 - 65 first and then turn on the "performance" setting with setCPU so that it's running on the highest setting during testing.
 
I'd try 1400 - 65 first and then turn on the "performance" setting with setCPU so that it's running on the highest setting during testing.

what about 400, 700, and 900?

im still tryna learn this cuz everytime i up the max i tend to up everything else.
 
what about 400, 700, and 900?

im still tryna learn this cuz everytime i up the max i tend to up everything else.

If you're not experiencing problem with those settings I would just leave them alone. The phone is usually running at the lowest or highest part of the scale.
 
OK I did everything in the instructions, then I was using notepad++ to edit the setscaling.sh file with some of the settings other people are using. After that i use the rootexplorer to replace the one in the system xbin then execute and I can see the changes in setCPU... it still maxes at 1GHz... what am I doing wrong? help please?
 
Random reboots here and there what's wrong guys and if my phone can't handle the standard oc of 1.38 can anyone help me out on changing it??
 
OK I did everything in the instructions, then I was using notepad++ to edit the setscaling.sh file with some of the settings other people are using. After that i use the rootexplorer to replace the one in the system xbin then execute and I can see the changes in setCPU... it still maxes at 1GHz... what am I doing wrong? help please?

Sorry, I can't help you with your problem though I wan't to say thanks for helping me with mine. Turns out, I was editing the wrong file and you saying you edited the one in system/xbin made me realize that.
 
Sorry, I can't help you with your problem though I wan't to say thanks for helping me with mine. Turns out, I was editing the wrong file and you saying you edited the one in system/xbin made me realize that.
Well I am glad I can be of assistance... let me know how it works out for you:)
 
If you're not experiencing problem with those settings I would just leave them alone. The phone is usually running at the lowest or highest part of the scale.

ok i see. i was just about to ask how do i know if im experiencing problem with a certain setting
 
OK I did everything in the instructions, then I was using notepad++ to edit the setscaling.sh file with some of the settings other people are using. After that i use the rootexplorer to replace the one in the system xbin then execute and I can see the changes in setCPU... it still maxes at 1GHz... what am I doing wrong? help please?


Run this command with Terminal Emulator and see if it reports the correct settings.

Code:
cat /proc/overclock/mpu_opps
 
After I type # setscaling.sh I get
Directory Nonexistentreate /proc/overclock/max_vsel
a bunch of others like this
and
setscaling.sh: cannot create /procoverclock/freq_table: directory nonexisten

Can anyone help, I'm using Terminal Emulator and yeah I'm a noob at this, lol
 
Ok, I had it working up to 1.225 Ghz at 65 then I dropped the voltage down to 60 and after about 10 minutes, it reboot and now it is telling me that I can't edit the files because they are read only.

After I type # setscaling.sh I get
Directory Nonexistentreate /proc/overclock/max_vsel
a bunch of others like this
and
setscaling.sh: cannot create /procoverclock/freq_table: directory nonexisten

Can anyone help, I'm using Terminal Emulator and yeah I'm a noob at this, lol

You need to type
Code:
$su
#insmod /system/lib/modules/overclock.ko
before you type that.
 
Yeah, I do that, lol
I went back and tried again and still get the list of:
Directory Nonexistentreate /proc/overclock/max_vsel
and a bunch of other directory nonexistentreate
Not sure what's going on. I've tried it a couple times,
I did # rmmod overclock.ko
killed the directory and recreated it and started over, still get the same thing
 
If you're using terminal emulator a lot give GScript Lite a try, you can save command lines so you don't have to type things out every time.
 
Is GScript Lite better than the donate version or something?

If I use the Terminal App everything works fine and I've hit 1814 with Beesleys .zip file installed. But as soon as I try to use GScript to turn if off and then back on again I get that message that the directory doesn't exist. Do you have to run a $ su command in GScript before it will recognize the insmod? I didn't think so because there is a checkmark in the box that says, 'needs SU'? that I figured would take care of that.

Or does that need to be unchecked?
 
Back
Top Bottom