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

FreeWELL said:
It might work as-is. If not, someone will need to do the Milestone Overclock Disassembly Process and find out what the three memory addresses are.

A start would be running the following in terminal/adb:

Code: 
# busybox grep omap2_clk_init_cpufreq_table /proc/kallsyms
c00489e0 T omap2_clk_init_cpufreq_table

Do you get c00489e0 as well? If so, the module should work as-is. If not, someone will need to do the disassambly process completely.

If someone with a D2 is serious about getting this running, PM me and I'll help out.
Click to expand...

Thanks, Im just a basic user, but I did those commands in terminal and i got c00489e0 denied error :(
 
ljbaumer said:
Will something like this work on the droid 2 also or will we need a whole new strategy to overclock it?
Click to expand...

Do this:

$ su
# busybox dd bs=1 count=180 skip=3221522876 if=/dev/kmem of=/sdcard/omap2_clk_init_cpufreq_table

Then pm me the file that is created at /sdcard/omap2_clk_init_cpufreq_table

I'll see what I can do...
 
WalCs said:
Thanks, Im just a basic user, but I did those commands in terminal and i got c00489e0 denied error :(
Click to expand...


I'm sorry, you were only supposed to do the first line... My bad. Another AF member has ran this for me and also the next step which I posted above...

But to verify... try running only the first line.... do you get c00489bc?

Gotta run take my son to the park, then handle some other business. I will put it all together this evening.
 
thefamousmoe said:
What exactly are your setting? I am restoring to my fission rom from rubix just to try this out. Are you running 1.0 fission or 1.1?
Click to expand...

Fission 1.0 and I will post my whole setscaling when I get to my computer. Im wondering if.mine will do 1.4. The last.guy to.get.it.stable. can u post ur volts(or whatever it.is) to match the 1.4ghz frequency
 
JrzDroid said:
weird. Such inconsistency with the OMAP chips
We should try to figure out who can run what and what other variables could affect inability to run above a certain limit.

-Who is on the leak and can't go past 1.15
-Who is on the OTA and can't go past 1.15
Click to expand...

I'm on the OTA running rubiX focused 1.0 and im using your config and thus far its stable and running fine. if anything changes ill update
 
just for a tiny boost here are my settings

echo 64 > /proc/overclock/max_vsel
echo 1195000 > /proc/overclock/max_rate
echo 1 400000000 27 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 50 > /proc/overclock/mpu_opps
echo 4 1195000000 64 > /proc/overclock/mpu_opps
echo 0 1195000 > /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
 
FreeWELL said:
I'm sorry, you were only supposed to do the first line... My bad. Another AF member has ran this for me and also the next step which I posted above...

But to verify... try running only the first line.... do you get c00489bc?

Gotta run take my son to the park, then handle some other business. I will put it all together this evening.
Click to expand...

Ran the first line, PM result, ran the other one too, I PMed you a link to 4shared to dl the file :D
 
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
 
Had some decent luck with undervolting so thought I would try OC a bit.

Having an issue though. Every time I try to execute setscaling.sh via adb/terminal my results are the same as the origional setscale I used with the max at 1.1Ghz. I am trying to do 1.2/1.3 but its a no go. I have to manually execute each line. Are you supposed to have to reboot between running setscaling.sh? Either way that doesn't help either.

Anybody got some answers?
 
jonathanmsims said:
So im.stable at 1.4 ghz with at vsel of 68. Hope that doesn't kill my battery. Anyone know?
Click to expand...

Same here, used Fab's other settings for the lower speeds and it seems to be screaming along and the battery is doing well. Will see here in a little while as the girls have been playing angry birds for over an hour on it.
 
Stable at 1.4 ghz... surprisingly... tried dropping vsel down to 65... didn't work. So I stuck it back at 68. Anyone know if this will hurt my Droid X? I know overclocking usually doesn't, but do you think at 1.4ghz it will? I know incredibles go there all the time with no problem...

Code: 
echo 68 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 400000000 28 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /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
snap20101019_192221.png


snap20101019_193202.png
 
Wonder if its rom and or app related? There has to be some pattern. I know, I'm crazy just typing. OH and I haven't even tried it yet, this is pure curiosity on my part.

I will probably try later. just rely on my phone too much at this point to get into it deeply
 
jonathanmsims said:
So im.stable at 1.4 ghz with at vsel of 68. Hope that doesn't kill my battery. Anyone know?
Click to expand...

As a fair warning to everyone, this was not stable on my phone. I pushed it to 1.3GHz with a vsel of 65, but 1.4GHz was just too much for my phone to handle.

If someone wants to start compiling ROMs and speeds, I am running RubiX 1.0 with 2.2OTA kernel.
 
Having a stripped down ROM might be helping... I don't know... seems that 1.4 is stable while its loaded... but won't boot... gonna have to nandroid restore... oh well... well as I type that it comes up... guess its not too stable... might back it down to 1.35, can I just set my setscaling.sh again? or do I have to rename install-recovery.sh, then setscaling again, then rename install-recovery back, then chmod 755 it?
 
yea those setting did not work for me either, 1.4 i mean. I'd like to get it up to 1300 somehow though. 1225 might be the best I can do. Still messing around, will update if I can find a good combo.
 
jonathanmsims said:
Having a stripped down ROM might be helping... I don't know... seems that 1.4 is stable while its loaded... but won't boot... gonna have to nandroid restore... oh well... well as I type that it comes up... guess its not too stable... might back it down to 1.35, can I just set my setscaling.sh again? or do I have to rename install-recovery.sh, then setscaling again, then rename install-recovery back, then chmod 755 it?
Click to expand...

Yeah I've found that 1.4 seems totally fine and stable until you really push it then it crashes hard. I'm really thinking that a happy medium will be 1.3. Though, I was unable to get 1.3 going at 60 vsel like some claim to have. Thusly I am jealous.
 
You must log in or register to reply here.
Back
Top Bottom