That was absolutely very helpful information that I will def use in the future.
From the sounds of it here is where I am. I am running Nexus Evolution that comes stock with an experimental LK so the kernel should use its own ramdisk, then i flashed TK which used system ramdisk, but then when I flashed back to LK it seems like a setting stuck in the system ramdisk that is over riding only the I/O scheduler for some reason. Even after dirty flashing the ROM and Kernel again?
I guess what I am asking is how do I go from existing (or system?) Ramdisk to a boot.IMG kernel without wiping the whole system(clean flash)? Or is that not possible?
Sent from my Galaxy Nexus using xda app-developers app
One easy way to tell if the kernel uses boot.img is as said above. There will be a file called boot.img when you open the zip. An anykernel zip (one that takes the existing ramdisk already on the phone and replaces the kernel - zImage) will have a kernel folder with a zImage file in it and no boot.img file.
I don't believe your issue is a bug with either LK or TK or a combination. It could be a script the dev had loaded or an app in the ROM that is interfering. See if you can check with the ROM dev about the I/O scheduler not sticking and if anyone else had this issue. I don't know if wiping will solve it but you should never need to wipe data to deal with swapping kernels. Reinstalling the ROM will reset the kernel and ramdisk back to what came with the ROM. A dirty flash is more than sufficient and it always wipes system so any custom init.d scripts will be removed and you'll only have the ones with the ROM. It's also possible the ROM dev tweaked the boot.img. What does the I/O scheduler get set to at boot? Trickster should be able to change it. LK defaults to deadline I believe.