Database Info

[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.
Click to expand...
Click to collapse
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.
*View attachment 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.
*View attachment damage537.zip* 537mhz is the default.. scalable to 768 if you use an OC'ing app
*View attachment damage768.zip* 768mhz default clock speed -read below
*View attachment 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?

mattshaver said:
So does this mean we can get the real AOSP dialer on Damaged's ROM?
Click to expand...
Click to collapse
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) , 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.

mattshaver said:
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) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
Click to expand...
Click to collapse
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

jeremysterling said:
i'm running ic3rom and in the process testing it out
Click to expand...
Click to collapse
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

I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)

schmooo said:
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
Click to expand...
Click to collapse
It doesnt effect jit at all. It only adds a few files and changes your boot.img.

schmooo said:
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
Click to expand...
Click to collapse
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.

Jus10o said:
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.
Click to expand...
Click to collapse
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#

Re: [KERNEL] Toast-godmode .29 source for DamageControl
So I can flash this and oc icerom? Etc....
-------------------------------------
Sent via the XDA Tapatalk App

mattshaver said:
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
Click to expand...
Click to collapse
Haha well you are right sorta on what the kernel does, but all cdma htc heros use the same kernels but it depends on what android version you are using. 1.5 uses .27 kernel, and 2.1 can use a edited .27 kernel but something things wont work, like camera. What toast did was made his own .29 kernel based on other sources and what we already have then we use for our 2.1 roms. The 2.1 roms that come from sprint use a .29 kernel that work, but we cant edited anything within the kernel until they release the source to the kernel. You must have source to the kernel to be able to change anything with in it. You cant download a rom from xda and take the kernel out and change the files and put them back. You have to already have the files to the kernel, change what you want, make your own kernel and then put it on the rom. Cuz once you compile the kernel its not able to be opened back up.
In a boot.img there are 2 parts, the kernel and a ramdisk. The ramdisk CAN be opened back up and changed. But if its trying to call something within the kernel it has to already be there, since you cant add anything to it. If you start with all the kernel files and compile your own like what toast did, then you can add the special things like overclocking frequencies.
I know I really suck at explaining things. I only know the basics of how it all works.

jeremysterling said:
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Click to expand...
Click to collapse
And you have the compcache.. or the newer one i posted?

Jus10o said:
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
Click to expand...
Click to collapse
Decad3nce said:
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Click to expand...
Click to collapse
sweet im gonna give it a try

Jus10o said:
And you have the compcache.. or the newer one i posted?
Click to expand...
Click to collapse
i downloaded and flashed damage1.zip with compcache

jeremysterling said:
i downloaded and flashed damage1.zip with compcache
Click to expand...
Click to collapse
Ok thanks.. yea compcache and swap arent working. Ill work on it.
But overclocking and everything else is. So its not gunna make a noticeable difference.

Deleting files from old kernel

I remember reading somewhere that when you flash a new kernel, some of the old tweaks are left on your phone and slow it down.
I'm trying to switch from trinity to Franco but I'm not sure if trinity left anything behind.
Is this true? Or am I imagining things.. -_-
Sent from my Nexus S using XDA App

baolongn said:
I remember reading somewhere that when you flash a new kernel, some of the old tweaks are left on your phone and slow it down.
I'm trying to switch from trinity to Franco but I'm not sure if trinity left anything behind.
Is this true? Or am I imagining things.. -_-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
The only thing that could get left would be some kernel modules placed under system....this has no effect on your system.
Sent from my Nexus S using xda premium

What is 99 tweak, 99 complete, and 95 dimmer in my init folder?
Sent from my Nexus S using XDA App

baolongn said:
What is 99 tweak, 99 complete, and 95 dimmer in my init folder?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
init scripts someone bundled with whatever update.zip you flashed. They are numbered to determine the order of execution by the init script in boot.

I have a question,
Say i am using a rom with a custom kernel, Not the one that came with the ROM, If i reflash the rom (without wiping data), Then i get Rom's default stock kernel, But will that remove the files and scripts that came with the custom kernel. Or do i need to do a fresh install to remove all the files of that kernel.
Also 95dimmers, 99 tweak and 99 complete come with the trinity kernels. It's advisable to remove them because they might cause issues when you install another kernel.

saranyan said:
I have a question,
Say i am using a rom with a custom kernel, Not the one that came with the ROM, If i reflash the rom (without wiping data), Then i get Rom's default stock kernel, But will that remove the files and scripts that came with the custom kernel. Or do i need to do a fresh install to remove all the files of that kernel.
Also 95dimmers, 99 tweak and 99 complete come with the trinity kernels. It's advisable to remove them because they might cause issues when you install another kernel.
Click to expand...
Click to collapse
It won't remove what is in /system/modules or /system/etc/init.d unless explicitly told to do so in the updater-script (I don't recall if it still supports delete off of the top of my head). The init scripts you should probably toast.
As your new kernel will write any modules it uses (wifi at a minimum) the modules are a non issue, but unused modules could be removed as well if desired.

Dont delete 99Complete. Rom wont boot then

snandlal said:
Dont delete 99Complete. Rom wont boot then
Click to expand...
Click to collapse
A full stock rom on a custom kernel shouldn't have any issues (going back to a stock kernel / ramdisk / boot image) as init.d scripts aren't used. A custom rom though is a different story.

Depends on the ROM package. Most (in fact all) of the ROMs I have tried, flash a native Kernel to avoid any initial boot-up/setup issues.

Just delete everything in init.d then reflash your desired kernel zip. It will replace anything that is supposed to be there. You should check your ROM zip for anything and copy that too.
Sent from my obnoxious finger using Swype

Kernel Cleaner Script for Nexus 5?

Used to be on galaxy nexus, I remember there's a script .zip which can be used to clean the existing kernel to prepare for a new kernel so ensure there wont be any conflict or incompatibilities there. Does anyone have something like it for Nexus 5? Can anyone sic? TIA!

anyone knows anything?

The only time that you need kernel cleaners are if the kernel creator modified the system binaries.
To my knowledge all custom kernels present are modifying only the boot.IMG so there is no need for a cleaner.
Usually of a Dev make a kernel that needs a cleaner. They will provide one for you.
Sent from my Nexus 4 using xda app-developers app

Yup, as above you only need a cleaner if a modified ramdisk was used.

4 months later... it would be useful now

Primokorn said:
4 months later... it would be useful now
Click to expand...
Click to collapse
They flash init.d scripts with different names and modify unknown system files, I can't see how this could be achieved without knowing what was modified Best way is to reflash ROM first

rootSU said:
They flash init.d scripts with different names and modify unknown system files, I can't see how this could be achieved without knowing what was modified Best way is to reflash ROM first
Click to expand...
Click to collapse
Yes but I hoped that each kernel developer who modifies the ramdisk provides the zip cleaner.
Dirty flashing the rom is a solution but sometimes it requires to put some stuff back like new system apps, custom dpi, xposed framework...

Primokorn said:
Yes but I hoped that each kernel developer who modifies the ramdisk provides the zip cleaner.
Dirty flashing the rom is a solution but something it requires to put some stuff back like new system apps, custom dpi, xposed framework...
Click to expand...
Click to collapse
It would be a case of asking each kernel developer to do this. I doubt they're reading this thread.
I have a single zip that I flash after my rom that does all my mods.. Deletes audio files, changes LCD Density in build prop, replaces boot animation etc. I haven't looked at adding Xposed in detail yet but it would be handy....
You could look into that

CTT mod improve performance eliminate lag updated 7/6

I've converted my CTT mod for the lg g3 to work with the nexus 7 this is now the official version as I've just been using it on a stock ROM with elementalx kernel and no problems so far so good should work with most ROMs.
Instructions,- Make a backup of your ROM and move your thermal files to a safe place. Then delete the originals Then boot into recovery flash mod and wipe caches reboot and enjoy
Right now these have only been tested on stock based ROMs but should work with any ROM
thermal mod 75 for stock kernel-
https://www.androidfilehost.com/?fid=24052804347769758
thermal mod 75 for elementalx kernel OC'd to 1.62 -
https://www.androidfilehost.com/?fid=24052804347769759
thermal mod 75 for elementalx kernel OC'd to 1.94 -
https://www.androidfilehost.com/?fid=24052804347769760
Please let me know what you think the more feedback the more improvement I can make
Thank Rob
Also here's the link to the original mod for the lg g3 to read up on what it does
http://forum.xda-developers.com/lg-g3/development/thermal-mod-t2907363?nocache=1

I want to try this with the new clean rom when it's released. I use your 75 mod on my g3. Can't wait.

What does the one for elementalX does?
I have elementalx's kernel but I just OC one step
Also, thanks for this mod, I have a G3 and have been following your mod since almost the start, and its been awsome, and also the fps unlock mod.
So glad your working on N7 too

Papote3 said:
What does the one for elementalX does?
I have elementalx's kernel but I just OC one step
Also, thanks for this mod, I have a G3 and have been following your mod since almost the start, and its been awsome, and also the fps unlock mod.
So glad your working on N7 too
Click to expand...
Click to collapse
there you go I made one for elemental x oc'd to 1.62 which should suit you in the op

Robshr said:
there you go I made one for elemental x oc'd to 1.62 which should suit you in the op
Click to expand...
Click to collapse
Thanks, will try and let you know

Robshr said:
there you go I made one for elemental x oc'd to 1.62 which should suit you in the op
Click to expand...
Click to collapse
Working great so far... What app do you use for displaying cpu frequency and temp on status bar?

Papote3 said:
Working great so far... What app do you use for displaying cpu frequency and temp on status bar?
Click to expand...
Click to collapse
I just use CPU temperature it has an overlay to display CPU in the status bar but only that I think I just open the app to see both the cpu temps and frequency as well as the battery temps

Is it necessary to clear Dalvik Cache after flashing this mode? It takes ages to complete that process, so I tend to avoid it as much as possible.
Also, isn't copy & pasting your modified thermal.conf file (after deleting the stock file) & then rebooting the device would be just fine?

Diljinder said:
Is it necessary to clear Dalvik Cache after flashing this mode? It takes ages to complete that process, so I tend to avoid it as much as possible.
Also, isn't copy & pasting your modified thermal.conf file (after deleting the stock file) & then rebooting the device would be just fine?
Click to expand...
Click to collapse
No it's not necessary and yes copying and pasting then rebooting would work
I just like to clear everything for good measure just to make sure there's nothing hanging around that would cause the mod not to work properly

Is it possible to unlock fps in this device?

I'm facing some weird unexpected issues with this mod.
I, first, copied & pasted the modified thermal file manually & rebooted the device. The device booted up normally but i experienced severe lag while using it. Normal operation like swiping through home screens etc seemed like at 5fps.
Thankfully, I had backed up before, so I restored it after proper clean up. Device worked normally. But I thought of giving it another chance, this time by following proper guide.
So I flashed the zip file, wiped Dalvik Cache/cache. But I experienced same issue as before. The device just got bogged down to crawl.
What exactly is causing this behaviour? Just to let you know, I use xposed on this device. Device is running Stock ROM with Stock Kernel & I used zip for Stock Kernel.

Just checked out the thermals in marshmallow and they have changed them to almost the same as my mod

Robshr said:
Just checked out the thermals in marshmallow and they have changed them to almost the same as my mod
Click to expand...
Click to collapse
Wow...if it was me, I wouldn't know if I'd be pleased or pissed off.........?

Deleted

Old thread.

You're the best, mate

minimale_ldz said:
You're the best, mate
Click to expand...
Click to collapse
Much appreciated and hope you all find it usefull to use. Just saw soniCron released a new script called "hawktail" based on a total different technique using an extreme low timer_rate. Shall try to translate that also next week and if it works ill add this in the thread.

Make a donation link. We love you.

Hi guys! And thanks for your work, @Sickaxis79!
A noob question here. Could these scripts be applied to another governor? Precisely, impulse which is supposed to be similar to interactive?
Sent from my XT1562 using Tapatalk

stazz83 said:
Hi guys! And thanks for your work, @Sickaxis79!
A noob question here. Could these scripts be applied to another governor? Precisely, impulse which is supposed to be similar to interactive?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Im afraid that ain't possible. Impulse governor use some different tunables, but you can for example use one interactive script for the big or small cpu and use impulse governor for the other cpu.

Applied the two profiles with latest squids kernel and cm13. Working Great so Far. I guess i have to manually disable touchboost everytime?

Leni_YO said:
Applied the two profiles with latest squids kernel and cm13. Working Great so Far. I guess i have to manually disable touchboost everytime?
Click to expand...
Click to collapse
Yes, its best to disable touchboost. Touchboost is a kernel/rom extra feature. Im also using latest squid kernel with stock rom and dont have this feature and forgot to disable it by default. I will check if i can update the script so its also disables touchboost. Im used to create and edit init.d scripts, but json files k.a. uses are a total different language, but ill try.

Master Mike, how are these scripsts working with optimized init.qcom.post_boot.sh you posted once. Should it be restored to default/stock one or can it all work together? Thanks

minimale_ldz said:
Master Mike, how are these scripsts working with optimized init.qcom.post_boot.sh you posted once. Should it be restored to default/stock one or can it all work together? Thanks
Click to expand...
Click to collapse
No problem. Post_boot script contains the stock settings and applies them first when the phone startup.

Sickaxis79 said:
No problem. Post_boot script contains the stock settings and applies them first when the phone startup.
Click to expand...
Click to collapse
Is KA changing them after boot anyway if it's got some scripts applied?

minimale_ldz said:
Is KA changing them after boot anyway if it's got some scripts applied?
Click to expand...
Click to collapse
Reboot reverts all stock settings unless you enable the checkbox "on boot". It will always first launch your normal stock settings and after the phone finished starting up it will launch the k.a. scripts.In the settings menu you can set the timer how many seconds after boot the scripts will launch.
You can always launch them manually when you dont want to apply them on boot. Just tap on the 2 scripts you imported and it will ask to launch them and finished.
Edit: K.a. overwrites the normal stock settings after youre phone booted temporarily.

Sickaxis79 said:
Reboot reverts all stock settings unless you enable the checkbox "on boot". It will always first launch your normal stock settings and after the phone finished starting up it will launch the k.a. scripts.In the settings menu you can set the timer how many seconds after boot the scripts will launch.
You can always launch them manually when you dont want to apply them on boot. Just tap on the 2 scripts you imported and it will ask to launch them and finished.
Edit: K.a. overwrites the normal stock settings after youre phone booted temporarily.
Click to expand...
Click to collapse
Got it, thanks

Can't import ghostpepper profiles, k.a. says the file is malformed. Great work btw, keep it up.

too bad i have the free version ...

thanks for your work, the script works very well in resurrection rom and optimus kernel, can someone upload the stopperfd script? the KA doesnt work for me creating the script

I've reached over 7hrs SOT on the first run after applying the profiles with 75% Charge left. Good job!

zenez said:
thanks for your work, the script works very well in resurrection rom and optimus kernel, can someone upload the stopperfd script? the KA doesnt work for me creating the script
Click to expand...
Click to collapse
You can also do this using a terminal emulator
Type: "su" (root permission) and "stop perfd".

Sickaxis79 said:
No problem. Post_boot script contains the stock settings and applies them first when the phone startup.
Click to expand...
Click to collapse
Thanks for answering for me.

ViperX85 said:
Can't import ghostpepper profiles, k.a. says the file is malformed. Great work btw, keep it up.
Click to expand...
Click to collapse
BUMP