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

At the top of the setscaling.sh what is the top echo value? The on that isn't paired with anything? Is it the highest voltage? I have always made that value and the one paired with my highest frequency the same. Am I wrong?
 
At the top of the setscaling.sh what is the top echo value? The on that isn't paired with anything? Is it the highest voltage? I have always made that value and the one paired with my highest frequency the same. Am I wrong?

As far as I know it should be that same as the other 2 highest value settings. Mine is that way and it's been fine all day.
 
can sum1 plz explain how to do this? i installed it. and ended up running it without changing anything. then went back to the setscaling.sh (located on sdcard) changed the numbers as sum1 else had. then ran it in terminal. is something suppose to happen?
 
Just a thought, those of you who are running at 1.3 ghz and above, did you ever do the official ota 2.2 or are you still on the leaked kernel?
 
This whole thing seems like an exercise in how to make your phone unstable for nothing more than a better benchmark score. :-)
I mean you can crash your phone so many different ways with this for basically nothing it makes wonder why ??...Which means I'll be trying it out as soon as I get this new rubix fission ROM running good.
 
This whole thing seems like an exercise in how to make your phone unstable for nothing more than a better benchmark score. :-)
I mean you can crash your phone so many different ways with this for basically nothing it makes wonder why ??...Which means I'll be trying it out as soon as I get this new rubix fission ROM running good.

My X is even faster than ir was before, it made a noticeable difference.

How well is that 1.4 @ 65 working for you?

No reboots in about 4 hours time and I've been using it all day to test it.
 
This whole thing seems like an exercise in how to make your phone unstable for nothing more than a better benchmark score. :-)
I mean you can crash your phone so many different ways with this for basically nothing it makes wonder why ??...Which means I'll be trying it out as soon as I get this new rubix fission ROM running good.

Being at 1.3 has made a real difference for me beyond benchmarks. Benchmarks is just the easiest way to relay that in this thread. Once you find a setting that is stable for you there really isnt any downside to this.
 
i installed according to instruction. and ran it. then realized i was on stock settings. went into .sh file on sdcard and changed the values. and removed by # rmmod overclock.ko. then ran run instructions and ended like this

$ su
# insmod /system/lib/modules/overclock.ko
# setscaling.sh
#

is somethign suppose to happen? did i edit the wrong setscaling.sh located on sdcard>?
 
Do you have to be running a different ROM, or does it work just as well on a rooted phone without any custom ROM's installed on it?

Next question, is it possible to set up different profiles in SetCPU so that you could set up a super snappy profile for those times when you want it to be super snappy and are around a charger so it doesn't really mateer.... but then say when you're heading out for the evening and want to conserve the battery you could switch over to a 'saver' profile that is less thirsty. Is that possible? Or would you have to go in and reset the value's every time you wanted to change the performance of the clock?
 
for those of you who are running 1.3 and above, what exactly are your setscaling numbers? I dont know what any of these numbers mean really, I'm just trying other people's setting to see if they work for mine.
 
for those of you who are running 1.3 and above, what exactly are your setscaling numbers? I dont know what any of these numbers mean really, I'm just trying other people's setting to see if they work for mine.

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
 
Do you have to be running a different ROM, or does it work just as well on a rooted phone without any custom ROM's installed on it?

Next question, is it possible to set up different profiles in SetCPU so that you could set up a super snappy profile for those times when you want it to be super snappy and are around a charger so it doesn't really mateer.... but then say when you're heading out for the evening and want to conserve the battery you could switch over to a 'saver' profile that is less thirsty. Is that possible? Or would you have to go in and reset the value's every time you wanted to change the performance of the clock?

If you were running something like 300/700/1000/1300, you could setup your profiles to only do 1300 when connected to the charger... then you could just disable your profiles and 1300 would come in when needed... That is one way you could achieve what you are asking for.
 
Thank you sir. I know there are a few other apps that do basically what SetCPU does, maybe I'll check them out and see if any of them offer different profile settings. That would be super cool.

I will report back if I find anything.
 
Thank you sir. I know there are a few other apps that do basically what SetCPU does, maybe I'll check them out and see if any of them offer different profile settings. That would be super cool.

I will report back if I find anything.

what app?
 
Just a thought, those of you who are running at 1.3 ghz and above, did you ever do the official ota 2.2 or are you still on the leaked kernel?

Fab I cannot for the life of me get above 1.15 either (which runs great), I am on the leaked kernel. Wonder if this is why?
 
for those of you who are running 1.3 and above, what exactly are your setscaling numbers? I dont know what any of these numbers mean really, I'm just trying other people's setting to see if they work for mine.

echo 60 > /proc/overclock/max_vsel
echo 1300000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1300000000 60 > /proc/overclock/mpu_opps
echo 0 1300000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
 
Back
Top Bottom