After the overclocking rumor that was spread a few months ago, I was quite hesitant when I saw another overclocking patch for the Dream\Sapphire. However, being the techie that I am, I couldn’t resist taking a closer look. After a few days of testing on Cyanogen’s recently released 5.0.7-DS (Eclair) builds, I am thrilled to report that it not only works, but it works REALLY well.
A little bit of background on the CPU inside the Dream\Sapphire: It’s a Qualcomm MSM 7201A processor clocked at 528mhz (only if you are rooted, stock T-Mobile builds run at 384mhz to save battery). The previous overclocking rumor stated that the CPU was running at approximately 780mhz, which equates to an almost 47% overclock over the stock speed. If you ignore the fact that the rumor ended up being untrue, a 47% overclock on a mobile CPU would not only destroy our battery life, but also significantly increase the heat output, possibly even to the point of permanent damage.
This new kernel patch, by pershoot, allows you to clock the CPU manually using SetCPU 1.5.2. In essence, we can now dynamically overclock our CPU up to 576mhz (when needed). Many users have attempted to go as high as 600+mhz, however it is not advisable to go above 576mhz due to the possibility of a significant decrease in battery life, increase in heat, and possibility of permanent damage to the chip. That being said, I have been running at 576mhz) for several days without issues, and I notice a nice increase in responsiveness and speed in Cyanogen’s newly released test2\test3 eclair build for the Dream\Sapphire.
WARNING: This mod\hack is forcing your phone’s CPU to run faster than originally intended. Neither myself nor AndroidSPIN are responsible for any issues arising from using this modification (Bricked phones, fires, death, etc). Please read the instructions carefully.
The latest kernel update.zip is available below or on Pershoot’s website as well as instructions for installing and setting up SetCPU 1.5.2. Its quite easy and shouldn’t take more than a few minutes to get everything up and running.
EDIT: Images updated for test3, correction made – Fender MT3G & MT3G 1.2 are not supported
EDIT2 : Updated links again, newer version that includes the hotfix by Cyanogen and Zinx
Huge thanks to Daproy, Dumfuq, coolbho3000 and Pershoot from the XDA forums for getting this working.
Instructions:
- Flash the .zip through recovery (make sure you choose the correct version)
- Install SetCPU 1.52 (by coolbho) – Download Link
- Change the following in SetCPU. Min: 128, Max: 576, onboot, ondemandDo not enable or setup Advanced
Optional: You can setup profiles, but if you receive lag, please be sure that your device is not stuck on a low frequency due to one of the profiles you have set and or due to cpufreq and SetCPU ‘oddness’.
Download the Kernel for your device below: (UPDATED 5/9/2010 )
Overclocked Kernel for 32B: HTC Dream or the Original HTC Sapphire.
- Download: boot-cm_2633.3_ds_32b-oc-uv-fp-050910.zip
Overclocked Kernel for 32A:
- Download: boot-cm_2633.3_ds_32b-oc-uv-xtra-fp-050910.zip
Information can also be found in the XDA Forums.








I have been using SetCPU for a little while now and downloaded this kernel yesterday. I must say that my CM 5.0.7-DS-Test2 runs so much smoother and quicker with this patch. No more lag on the home screen and after phone calls. No force closes because of lag. I would rather run with an overclocked CPU and Compcache or Swap then JIT. (myTouch3g).
I have been using SetCPU for a little while now and downloaded this kernel yesterday. I must say that my CM 5.0.7-DS-Test2 runs so much smoother and quicker with this patch. No more lag on the home screen and after phone calls. No force closes because of lag. I would rather run with an overclocked CPU and Compcache or Swap then JIT. (myTouch3g).
my phone caught fire…
my phone caught fire…
Glad its working out for you, I also prefer a slight overclock to JIT. Regarding the fire…I warned you not to try and compete with those new 1ghz snapdragons :-p
Glad its working out for you, I also prefer a slight overclock to JIT. Regarding the fire…I warned you not to try and compete with those new 1ghz snapdragons :-p
Droids are up to 1.1Ghz and there not catching on fire???!!! Why are we scared to go to 800mhz?
Droids are up to 1.1Ghz and there not catching on fire???!!! Why are we scared to go to 800mhz?
It states to run this on demand any issues with performance mode? Also running failsafe on temp and underclocked on standby/sleep.
I’m currently running on 576/128 performance and its awesome
It states to run this on demand any issues with performance mode? Also running failsafe on temp and underclocked on standby/sleep.
I’m currently running on 576/128 performance and its awesome
So, is anyone else having trouble running this on a myTouch 1.2? I have cyanogen’s 2.1 test 2 on there ATM, and flashing this kernel update leaves me with a phone that goes blank at the splash screen. anyone else?
So, is anyone else having trouble running this on a myTouch 1.2? I have cyanogen’s 2.1 test 2 on there ATM, and flashing this kernel update leaves me with a phone that goes blank at the splash screen. anyone else?
This update doesn’t support the MT3g 1.2 or Fender edition
This update doesn’t support the MT3g 1.2 or Fender edition
Thanks…this has made a world of a difference…currently running at 614 for the past 30 minutes on my 32B Magic. No fire so far
and it is running very very fast (at least as compared to before). Will update on how fast the battery is draining soon…
Running CyanogenMod-5 v5.0.7 test 2
Thanks…this has made a world of a difference…currently running at 614 for the past 30 minutes on my 32B Magic. No fire so far
and it is running very very fast (at least as compared to before). Will update on how fast the battery is draining soon…
Running CyanogenMod-5 v5.0.7 test 2
Quick one…its seems to me that the phone is still running at 576 eventhough I’ve it set to run at 614…any ideas why that might be.
Is it because thats the extent of the processor capabilities or is the software reporting the wrong frequencies ?
Quick one…its seems to me that the phone is still running at 576 eventhough I’ve it set to run at 614…any ideas why that might be.
Is it because thats the extent of the processor capabilities or is the software reporting the wrong frequencies ?
This specific kernel is limited to 576, just for safety and stability reasons. The software is most likely reporting the wrong clock freq. I played around with other kernels that can OC higher, but this one was the most stable.
This specific kernel is limited to 576, just for safety and stability reasons. The software is most likely reporting the wrong clock freq. I played around with other kernels that can OC higher, but this one was the most stable.
Updated w/ newer kernel images. These guys pump out an updated kernel everyday, it seems. Great work from all the devs involved with this project.
Updated w/ newer kernel images. These guys pump out an updated kernel everyday, it seems. Great work from all the devs involved with this project.