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.

[KERNEL][FROYO][8-07-11] PeanutButta Jelly Time

Here is the initial release of my kernel. I'd like to have some other stuff fixed/working, but for now, this is it. I've made a lot of changes and I tried to list them all below, but I know there is stuff that I missed. Currently, the only issue that I know of is that the boot animation will be out of sync and may skip on boot. I have currently retained the stock boot animation, but custom boot animations are also possible if people would like them.
Also, while this kernel can work for recovery, I currently have not tested it, so recovery will remain what it is (ie. jt1134's CWM). I plan on testing recovery soon and releasing an updated Odin for it, as well as just having the kernel zip re-flash recovery.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0807
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB storage in recovery
0730
Custom boot animation support
Updated recovery
0710
Voodoo Sound V10
Updated CWM Recovery
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Test CWM and flash recovery partition
Smooth out boot animation
Get an overclocking kernel out
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.
Legend
voodoo/novoodoo - voodoo has the lagfix, novoodoo doesn't (I hope this was obvious)

Frequently Asked Questions
How do I install this?
You flash this in CWM. If you need CWM, you can find it here
Can I use ROM Manager to flash this?
If you didn't use Odin to flash CWM, this will not work. Also, ROM Manager is not compatible with CWM when it fully replaces stock recovery.
Can I install this over another Voodoo Lagfix kernel?
Yes. Any kernel that use's supercurio's lagfix can be flashed over any other kernel that uses it.
How do I disable Voodoo Lagfix?
Create a file on the SDCard named disable-lagfix within the voodoo folder (/sdcard/voodoo/disable-lagfix). You can also use the option in the Voodoo Control app (from the market) or the option in CWM Recovery to disable the lagfix.
How do I know if it is installed?
Go to Settings > About Phone and the kernel version should read:
Code:
2.6.32.9
[email protected] #1
Will this work with xxx ROM?
This will work with any currently available ROM that is posted here.
Can I overclock with this kernel?
No. Currently overclocking is not supported. I do plan on looking into implementing this in a future version though.
Can I use SetCPU with this kernel?
You can use SetCPU with this, but do not use profiles. If you have problems and are using profiles, I'm not going to try to fix them as profiles do not work properly on any SGS phone that I've seen.
Does this kernel include xxx feature?
If it is not listed in the first post, probably not. To be sure, check the commits to the source on Github.
Can you add/implement xxx feature?
If you can link to what you want added/changed, I can look into doing so. If you just say something like "I want bigger quadz!" with no information about what you want or where to find it, I'll just disregard your request.
I am having xxx issue, can you fix it?
See the NOTES section above. Failure to provide any steps to reproduce your error, or a log of the issue as it is occurring will not get your problem fixed. I need the output from logcat and/or dmesg to be able to fix problems. Use the following to obtain a log (easiest with ADB).
Code:
adb shell dmesg > dmesg.txt
adb logcat > logcat.txt
Enter one of the commands and attempt to recreate your issue. Logcat will run constantly until you stop it (disconnect the phone, or ctrl+c). Dmesg will dump the current buffer and end. Try to get a logcat first as it will be easier to capture the error. PM me the files once you've collected them and I will look into it. DO NOT POST THEM IN THE FORUM. Logcat and dmesg may both contain identifying information (like your phone number or email address) so PMing them to me will prevent everyone from seeing this info. If you need help, ask or join IRC.
If you would like something added to the FAQ, please post it in the following format:
Code:
[PLAIN][b]Put the question here[/b]
Put the answer here[/PLAIN]

Flash in cwm.
Sent from my SCH-I510 using XDA Premium App

papi92 said:
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yes, added installation instructions to OP

So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App

Blanco954 said:
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
If you have lagfix enabled you just flash the voodoo kernel, or disable lagfix and flash non-voodoo kernel if you want RFS file system

Thanks Hopper. I will give this a try.
Sent from my SCH-I510 using XDA Premium App

Worked like a champ for me...thank you!
Sent from my SCH-I510 using Tapatalk

Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App

Flash, flashed!
Thanks again, imnuts!

confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?

papi92 said:
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
We currently have only one cwm which is jt's, so I don't quite understand what you mean.

froodyo said:
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.

hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
Click to expand...
Click to collapse
Thank you very much.

papi92 said:
Do we disable the lagfix the same way as we do with jts?
Click to expand...
Click to collapse
Yes, lagfix is disabled the same way with any kernel that uses supercurio's Voodoo Lagfix.
froodyo said:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
Kernels are almost always independent of the ROM, so yes, you can install this regardless of what ROM you are running (Stock, debloated, something else). If/When we get a non-TouchWiz based ROM, this may change, but for now, you can use this with anything currently available.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
Click to expand...
Click to collapse
I set up novoodoo to try and avoid issues, so if you were on voodoo and didn't disable, the novoodoo should still work, but why risk it if you don't have to?

So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting

Manjews said:
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Click to expand...
Click to collapse
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.

hey i come from the fascinate and i love your work can't wait until you get voodoo sound working
i will be rooting a friends droid charge soon and then i will set him up with JT cwm voodoo and your kernel
glad to see some devs i already know working on the droid charge

khanfuze said:
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
Click to expand...
Click to collapse
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.

Manjews said:
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Click to expand...
Click to collapse
Good to hear Samsung released broken cpu governors again

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

[Q] VomerTweaks , What it does ?

@zephiK , I installed the VomerTweaks on top of Mahdi rom and Franco kernel from your signature. I flashed it via TWRP , but dont know if its installed or is successfull etc. Can you let me know what exactly this tweak does and any way of finding if its active / installed ? Is there a option which appears in settings ? Thanks !

You didn't have to make a new thread for this.
To verify that the settings indeed have loaded, you need to use a kernel tweaker app (e.g. FKU, Trickster)... if you see that the maximum (fixed) CPU frequency is 1.2GHz then its loaded. A lot of the questions you asked are answered https://192.227.135.147/get/vomertweaks.txt (ignore the warning)
# What is it?
VomerTweaks is a tried and tested set of custom settings and power modes for your device!
The aim is to enable your device to have insane battery life without losing performance (all of us love da juice!)
We develop and test multiple configurations (for different "user types") & share them with the community.
Click to expand...
Click to collapse

Sorry but it's not showing that min. Cpu frequency on my device in fku but the file was installed correctly via twrp and I just checked it is in the correct location. Any other parameters I could check if it's working correctly somehow?

shapethelola said:
Sorry but it's not showing that min. Cpu frequency on my device in fku but the file was installed correctly via twrp and I just checked it is in the correct location. Any other parameters I could check if it's working correctly somehow?
Click to expand...
Click to collapse
Errr whoops, I messed that up. I meant to say Maximium CPU frequency.

zephiK said:
Errr whoops, I messed that up. I meant to say Maximium CPU frequency.
Click to expand...
Click to collapse
LOL. I too was about to post the same question Thanks !! by the way , do i need to flash it everytime OTA arrives ?

You need to reinstall Franco if it's supported yet that's all

dayanandgp said:
LOL. I too was about to post the same question Thanks !! by the way , do i need to flash it everytime OTA arrives ?
Click to expand...
Click to collapse
If you're on a custom ROM, it is not needed since a backup script is included.
If you're on CM11S, then you will need to reflash it on a OTA (Or even remove the script before being able to accept the OTA) since addon.d is not supported in CM11S.
You need to reinstall Franco if it's supported yet that's all
Click to expand...
Click to collapse
No, flashing a newer/older version of Franco does not touch this script at all.

zephiK said:
If you're on a custom ROM, it is not needed since a backup script is included.
If you're on CM11S, then you will need to reflash it on a OTA (Or even remove the script before being able to accept the OTA) since addon.d is not supported in CM11S.
No, flashing a newer/older version of Franco does not touch this script at all.
Click to expand...
Click to collapse
Okay, youre the boss. I just thought installing an ota update from cm11s will overwrite francos kernel and without francos kernel this vomer tweak wont work. What I basically was saying was you need to have a kernel of franco running after you updated your cm11s again.

shapethelola said:
Okay, youre the boss. I just thought installing an ota update from cm11s will overwrite francos kernel and without francos kernel this vomer tweak wont work. What I basically was saying was you need to have a kernel of franco running after you updated your cm11s again.
Click to expand...
Click to collapse
As I said before, CM11S does not support addon.d scripts so therefore it cannot back up the script. Even if the script was allowed to be backed up, the OTA will most likely not work due to changes being made to /system/ unless using a modified upgrade script to the OTA package.
If the user flashed the script without Franco Kernel, then it will simply just not be able to change certain parts since the path is invalid. And I think its pretty obvious that the user needs Franco Kernel for the script to work. The whole point of the script was to be revolved around Franco Kernel and not any other kernel, its not there to discriminate other kernels but kernel developers have their own paths to certain parameters. Its not uniform throughout the phone.

zephiK said:
As I said before, CM11S does not support addon.d scripts so therefore it cannot back up the script. Even if the script was allowed to be backed up, the OTA will most likely not work due to changes being made to /system/ unless using a modified upgrade script to the OTA package.
If the user flashed the script without Franco Kernel, then it will simply just not be able to change certain parts since the path is invalid. And I think its pretty obvious that the user needs Franco Kernel for the script to work. The whole point of the script was to be revolved around Franco Kernel and not any other kernel, its not there to discriminate other kernels but kernel developers have their own paths to certain parameters. Its not uniform throughout the phone.
Click to expand...
Click to collapse
@zephiK i cant find the link to Vomertweaks anymore in your signature. Is somthing wrong ? Did you delete it ?
I wanted to find out how to disable/delete for future , as it is surviving mahdi OTA's

Check this post for download links:
http://forum.xda-developers.com/showthread.php?p=55150676
Sent from the One

dayanandgp said:
@zephiK i cant find the link to Vomertweaks anymore in your signature. Is somthing wrong ? Did you delete it ?
I wanted to find out how to disable/delete for future , as it is surviving mahdi OTA's
Click to expand...
Click to collapse
I removed it since the links were just all over the place. Refer to nikzDHD's link above ^^.
To uninstall, just flash vt_uninstaller.zip

@zephiK sorry to ask this here, but is it possible for someone to build chroma rom for oneplus one? would be great right?

kernel Cleaning

Hey guys, I was just wondering if someone could help me out with a problem.
I put ROMs on my phone at least once every month or so. The question I have is.
If I wanted to make sure I was cleaning up old kernel settings what would be the best steps to take.
Sometimes I just want to change kernel and not ROM. For example, I am on aicp ROM and would like to change
Kernel but I changed settings with kernel tweaker and I don't really know
How to make sure I got rid of settings before flashing next kernel.. Thanks in advance..

Hi edshawn911
There's a boot partition which actually contains the kernel You can wipe it with TWRP as far as I know
Furthermore I'd use the file manager (also available in TWRP) to take a look at your sdcard (internal storage). You might find some config files which were generated by your kernel tweaking app.

Just reflash/dirty flash your ROM then flash your new kernel. Clear data on any kernel apps if you use one. Nothing else.

when you flash a new kernel, itll clear out the old kernel settings automatically. but some kernels still leave behind stuff. most kernels are just kernels, while some add system files as well. you can check places like /etc/init.d and delete whatever is there if a kernel left some files.

experience7 said:
Hi edshawn911
There's a boot partition which actually contains the kernel You can wipe it with TWRP as far as I know
Furthermore I'd use the file manager (also available in TWRP) to take a look at your sdcard (internal storage). You might find some config files which were generated by your kernel tweaking app.
Click to expand...
Click to collapse
Thanks for response..

I usually backup the ROM I'm on with the included/stock kernel before flashing another kernel. When I want to switch, I simply restore the backup beforehand. My current backup has the barebones AOSP kernel.