Quote:
Originally Posted by The Matrix
|
Ive been clocked at 1.2Ghz since last night, It works Perfectly.
Needs to be reloaded/set on boot, but thats no issue for me
EDIT:
Ok,
KernelModule - milestone-overclock - How to use the kernel module - Project Hosting on Google Code gives a lot more information on what you can do with this.
By default, with just the app installed, it will NOT re-initiate the OC on boot, but you can script it to do so by adding something like
Quote:
/system/bin/insmod /system/modules/overclock.ko
echo 62 > /proc/overclock/max_vsel
echo 800000 > /proc/overclock/max_rate
|
To the mot_boot_mode file, (the app places overclock.ko in /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko, I haven't tried changing this to reflect the default location)
But if that scares you, dont try it unless you're confident. Personally, I like not having itset on boot, but that just me, but I figured I would at least confirm that it works.
Also, where i did say i was running at 1.2Ghz, That was purely to see the extremes of effects on battery life and tempterature. Now, i'm running it at 800Mhz happily, And ive found 1000Mhz to be wonderfully smooth.
I remember reading that the OMAP3430 chip in the phone is designed for and tested up to 800Mhz, but remember, any boost in Voltage, and to a lesser degree, frequency, WILL lower cpu life.
I recommend using SetCPU (or similar) in conjunction to this, as it allows quite a lot more control with the profile settings and such but it isn't strictly necessary, For example, right now, i run at 800Mhz only when plugged in, and whilst not sleeping, Which essentially has no effect on batterylife in the long run whilst still giving me performance at home/in the car. If you use setCPU, be sure to autodetect settings (via menu key), and adjust profiles if necessary whenever you change Max clock