[KERNEL]Toast-godmode OC .29 kernel for DamageControl/based roms

---

Please Read
This will not change anything on your phone that would prevent you from ever flashing a new rom or nandroiding back to a working one. Everything this update will do can completely be erased with a wipe or nandroid. Also flashing any rom, clean install or not, will preplace the boot.img this update.zip puts on your phone. So dont blame these downloads for your simple user errors of not being able to flash a new rom or nandroiding.


This is an overclocked kernel from toastcfh godmode .29 source. The kernel was actually pulled from Fresh Toast
This works on DamageControl and roms based off of his, it will not effect any of DC mods, including the Dconig app.

UPDATE

6/6/10- This should be working on the newest damagecontrol 2.09. Please report (if overclocking has worked in the past for you) if you have a problem on the newest release.

I made an attempt to get compcache to work, so it might or it might not. Someone with more experience might want to double check it.

Both include setcpu.txt for Setcpu OC app.. Select "custom" at the very bottom for device. Do not select hero. Or you can select "Auto Detect" at the top, this does not need the setcpu.txt.

*damage710v2.zip* THIS IS A TEST KERNEL FOR THE NEWEST DAMAGECONTROL 2.09.. It is the exact same as damage710 but with a newer ramdisk, this is in hope of fixing any problems anyone is having with 2.09 and OC kernel. There might not even be a difference in the new ramdisk between the old one. I didnt have time to check. Sooo ya.

*damage537.zip* 537mhz is the default.. scalable to 768 if you use an OC'ing app
*damage768.zip* 768mhz default clock speed -read below
*damage710.zip* 710mhz default clock speed -read below
Both can be scaled from 19.2 to 768mhz..
DAMAGE710--The damage710 will default 710mhz, you must use an OC app to scale it to 768. Use damage710 if your phone can not boot the 768mhz. And dont scale any higher then 710mhz or your phone might reboot.
DAMAGE768--If your phone can boot the 768mhz then either download will work. But if you dont want to use an OC'ing app then the damage768 will scale to 768mhz.

This IS a flashable update.zip.. This will only replace your boot.img of your phone. So it is not a full rom. This is applied on top of your rom.

ALWAYS MAKE A NANDROID BEFORE FLASHING.


You Do Not Need A Partition On Your Sdcard For Overclocking


THIS IS A MUST FOR SWAP/compcache
To get swap working, you must have an ext partition on your sdcard. This will format you sdcard erasing everything, so do the following. Back up everything from your sdcard to your computer(exp- In a folder on your desktop named Sdcard). In recovery, select partition sdcard, use all default values, 32mb swap, 512mb ext partition, the rest fat32. Then when its finished change ext2 to ext3. Then reboot the phone. And then move all the files you backed up to the computer back to your sdcard.

If thanking me for putting this together. You should also give an even bigger thanks to Toastcfh for this kernel.
Thanks also goes to flipzmode, cuz i pulled the kernel from his boot.img in fresh toast.
Also darchstar for the defaulting clock speed tip.

So does this mean we can get the real AOSP dialer on Damaged's ROM?

Originally Posted by mattshaver

So does this mean we can get the real AOSP dialer on Damaged's ROM?

No.. this just adds overclocking and the few extra things that come along with it in the kernel. Has nothing to do with AOSP.

you rock

10 char

Excuse my ignorance on this topic.

But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) :P, so what is the difference?

My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.

If anyone wants to know how to do this, follow this guide starting at Step 8.

Essentially just extract the kernel you want from the right boot.img, extract the ramdisk from the other boot.img, then use mkbootfs and makebootimg to put them back together.

PM me if you need help.

Originally Posted by mattshaver

Excuse my ignorance on this topic.

But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) :P, so what is the difference?

My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.

I dont mind, ask anything here. Its how we learn

But that was the issue with all 2.1 roms. Toastchf cracked the code (in a way, not literally). And was able to give us a working source for .29 kernel. That kernel can then be used to work on any cdma hero 2.1 rom. But there are different things you have to do to get it to work on Darchdroid AOSP rom, he has already done that and its in his newest release. This one I posted above is just to work with damagecontrol roms or ones based off of it.

To get the AOSP dialer working you would have to have a rom based on AOSP, which darchdroid is the only rom so far. All the other roms are based on htc framework or just something different then AOSP. But im pretty sure theres AOSP dialers for damagecontrol. Go check the apps and themes section.

EDIT: the dialers are also completely separate from the kernel. Its based on what the rom is.

i'm running ic3rom and in the process testing it out

Originally Posted by jeremysterling

i'm running ic3rom and in the process testing it out

If you downloaded the compcache one, can you go into terminal and type

adb shell
free

Tell me if it says "swap" in what comes up and that it doesnt have all 0's.

ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help