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

major97702 said:
I'm doing the same as you man. Not very far into it. so far @ 400mhz/ 18(nvm 18 crashed) as lowest clock.

But what do you guys use as a stress test? Just the one built into SetCPU? bunch of quad runs? Daily use? I'm curious.

Thanks.
Click to expand...

Combination of all that and some graphics heavy snesoid roms.
 
Yeah, I've got a launch day one, and can't get it past 1.1 either. Running 2.2 OTA Rubix 1.0. I got it to be "stable" at 1.15, but was actually getting lower scores than 1.1 in Linpack and Quadrant. Oh well I guess, just the little increase has added the responsiveness I was looking for.
 
Just got a 2156 quad on 1.45ghz


edit:
attachment.php
 

Attachments

  • CAP201010202349.jpg
    CAP201010202349.jpg
    138.7 KB · Views: 533
Im stable at 1.35 with Rubix blurry .3 but the best stress test seems to be running angry birds. I cant seem to run it more than few minutes.
 
so far im running nicely stable at 1.45ghz. seeing if i can squeeze a higher quadrant out. if not itll be time to increase the heat so to speak (see what i did there? lol)


by the way can any1 explain how i use setcpu? i got it but dont really know how to use it. lol
 
Anyone have a idea why if I run SetCPU @ stock settings, with a min/max the same @300mhz. It locks up after just a couple minutes... Yet if I OC to 400mhz I can get about 10mins out of it...

Seems stock is less stable than a undervolted OC...
 
It appears that at 1.6 the dx becomes a super turtle.. Lulz

finding a stable point for 1.5ghz right now.
 
Is this vsel ok as long as the phone doesn't get too hot?

echo 84 > /proc/overclock/max_vsel
echo 1425000 > /proc/overclock/max_rate
echo 1 500000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 40 > /proc/overclock/mpu_opps
echo 3 1000000000 64 > /proc/overclock/mpu_opps
echo 4 1425000000 84 > /proc/overclock/mpu_opps
echo 0 1425000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 500000 > /proc/overclock/freq_table
 
^
only 1 way to find out and thats testng it out


EDIT: RUNNING AT 1.5GHZ...REAL SNAPPY BUT CANT SEEM TO GET BENCHMARK TO WORK PROPERLY WITH THIS. KEEPS FORCE CLOSING
 
cjdecarl said:
Is this vsel ok as long as the phone doesn't get too hot?

echo 84 > /proc/overclock/max_vsel
echo 1425000 > /proc/overclock/max_rate
echo 1 500000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 40 > /proc/overclock/mpu_opps
echo 3 1000000000 64 > /proc/overclock/mpu_opps
echo 4 1425000000 84 > /proc/overclock/mpu_opps
echo 0 1425000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 500000 > /proc/overclock/freq_table
Click to expand...

84 is getting pretty high up there, so keep a close eye on things. If your battery temperature goes above 120 F, you're getting into the danger zone where damage may start to occur. Personally I'm trying to keep the max vsel below 70. With those settings you've got, your battery consumption is probably going to be pretty high during active use. Let us know how it goes.

I recommend reading http://www.droidforums.net/forum/rescue-squad-guides/47871-overclocking-101-a.html
 
Didn't try max oc really. But got 1.45ghz /75. Stable enough to run quad a couple times(didn't do any stability tests). score was like 1825(stock 2.2).

my stable 24/7 seems to be about 1.2ghz /60. With a min speed of 500 /30.

Still testing for most performance to voltage ratio.
 
jr1125 said:
Currently oc'd to 1470mhz (1.47ghz) and have my min to 400mhz.
Click to expand...

I'm almost the same. I'm at 1450mhz and 400 min. But I have my min cranked down at 20vsel. So I'm hoping it offsets the battery consumption of my 76vsel to keep 1.45 stable.
 
Fabolous said:
I'm so jealous. Anything highet than 1.15 for me and my phone goes into turtle mode. I used 68 vsel and couldn't even get to 1.2. My D1 was such a champ, looks like my DX is a dud :(
Click to expand...


Don't feel too badly, Fab. I couldn't even run setscaling100.sh on mine w/out it immediately locking and rebooting. After it reboot back to stock it's running "normally" again.

~
 
thefamousmoe said:
was able to find a stable 1.225, linpack 16.35 (first run) 17.074 (second run), quadrant 1721(first run) 1717 (second run)

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
Click to expand...

These settings have been working for me for going on 12 hours. Noticeably quicker. But quadrant scores only in the upper 1500s (not such a big deal to me).

Running Droid X 2.2 OTA with RubiX Focused 1.0 ROM
 
I'm going to try this on my launch day DX later... I'm probably going to be really disappointed with the results.

I've contemplated trading it for a Droid Incredible or Fascinate... which one should I do? or should I wait for a new phone to come out?
 
Here are my settings (thanks to thefamousmoe). I have had them running for about 2 hours now. It survived a couple rounds of Tank Recon 3d.

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

1686 on Quadrent. Going to leave it like this for a few days and see how it does.
 
Quick question. The only time you have to enter in
insmod /system/lib/modules/overclock.ko
setscaling100.sh
is if your phone reboots correct?

For example, if I'm just changing values and it hasn't rebooted, there is no need to open command prompt and enter that command?
 
You must log in or register to reply here.
Back
Top Bottom