[DEV] For CM11 users, here's how you can use AOSP(Non CAF) kernels again - Nexus 5 Android Development

Since CM11 changed to CAF, here's a zip to be able to use AOSP kernels again. There's really only one note to adhere - You MUST use the kernel ramdisk from CM's kernel as there is stuff in there that is needed, so if you just flash a AOSP kernel that is built as a boot.img, IT MAY NOT BOOT. Special Note - For Franco's kernel(and others maybe) all you need is to do is use the CM(or mod his) init.d to get it working properly, using the full CM ramdisk may cause the phone not to sleep(high Android OS usage in battery stats)
Now for those that want to know the specifics, these 10 libs are what control it
Code:
hw/gralloc.default.so
hw/gralloc.msm8974.so
hw/hwcomposer.msm8974.so
hw/memtrack.msm8974.so
libexternal.so
libmemalloc.so
libmemtrack.so
liboverlay.so
libqdutils.so
libqservice.so

---

This is neat. Haven't tried CM11 yet, but when I do, this will be good.
Sent from my Nexus 5 using Tapatalk

---

So for a CAF based rom my best bet for running a third party kernel would be to let the rom boot with its ramdisk, flash this fix (Thank you by the way.)
Let that boot,
Then while in recovery flash the custom kernel?
Would it do any justice to unzip the Decaf build, replace the boot.img with a third party kernel boot.img and just flash that in recovery?
Sent from my Nexus 5 using Tapatalk 2

---

melbourne408 said:
So for a CAF based rom my best bet for running a third party kernel would be to let the rom boot with its ramdisk, flash this fix (Thank you by the way.)
Let that boot,
Then while in recovery flash the custom kernel?
Would it do any justice to unzip the Decaf build, replace the boot.img with a third party kernel boot.img and just flash that in recovery?
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Well it's not going to boot with 3rd party kernel so you flash the non CAF zip immediately after flashing the nightly. Then flash the custom kernel. Then reboot.
Sent from my Nexus 5 using Tapatalk

---

Was able to flash elemental kernel on latest cm nightly with this. Works great

---

Tikerz said:
Well it's not going to boot with 3rd party kernel so you flash the zip immediately after flashing the kernel. Then boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Fasho.
Fiddle time tonight!
Sent from my Nexus 5 using Tapatalk 2

---

melbourne408 said:
Fasho.
Fiddle time tonight!
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
You like to fiddle , your mom told you to stop.
Sent from my Nexus 5 using Tapatalk

---

unforgivenmercy said:
You like to fiddle , your mom told you to stop.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hahaha you got me.
Saw I, Frankenstein with the family.
Haven't felt my heart race in years. Really enjoyed it. Screw ripened potatoes.
Sent from my Nexus 5 using Tapatalk 2

---

anyone try with Franco yet?

---

dmo580 said:
anyone try with Franco yet?
Click to expand...
Click to collapse
Yes, it works. Flash CM11, flash non CAF zip, then last flash the custom kernel. You'll have to do this for each nightly until CM breaks it again.
Sent from my Nexus 5 using Tapatalk

---

Can someone point me to the source, where was changed to CAF? Thanks.

---

Tikerz said:
Yes, it works. Flash CM11, flash non CAF zip, then last flash the custom kernel. You'll have to do this for each nightly until CM breaks it again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Is volume control an issue though? I believe certain apps like Play Music or whatever fail to allow volume to be properly controlled with Franco. I will test now and report back.
Edit: Volume control works but then you lose custom color settings

---

Any tried this on latest nightly 29/7??

---

dmo580 said:
Is volume control an issue though? I believe certain apps like Play Music or whatever fail to allow volume to be properly controlled with Franco. I will test now and report back.
Edit: Volume control works but then you lose custom color settings
Click to expand...
Click to collapse
Is this why all my music and alarms were at max volume at all times before?

---

rockingondrums said:
Is this why all my music and alarms were at max volume at all times before?
Click to expand...
Click to collapse
Are you on Franco? Starting Nightly ~0118 or so, the conflict started due to the audio commits and as a result the volume control for media started spiraling out of control on Franco kernel. I'm not sure about alarms because I already use 6/7 volume which is pretty loud, so 7/7 probably wouldn't be noticeable unless I did a heads up comparison.
But basically, while this non-CAF patch allows you to gain control of the volume back, a lot of Franco kernel features will be broken. Basically CM and Franco commits are in conflict right now, so unless Franco decides to support CM's latest moves or someone cherry picks commits for Franco kernel, it's gonna be hard to get the best of both worlds.

---

dmo580 said:
Are you on Franco? Starting Nightly ~0118 or so, the conflict started due to the audio commits and as a result the volume control for media started spiraling out of control on Franco kernel. I'm not sure about alarms because I already use 6/7 volume which is pretty loud, so 7/7 probably wouldn't be noticeable unless I did a heads up comparison.
But basically, while this non-CAF patch allows you to gain control of the volume back, a lot of Franco kernel features will be broken. Basically CM and Franco commits are in conflict right now, so unless Franco decides to support CM's latest moves or someone cherry picks commits for Franco kernel, it's gonna be hard to get the best of both worlds.
Click to expand...
Click to collapse
Yeah, I was. I've got an itch to switch (again) anyway. I'm the opposite of you; I always have media at max, but my alarm fades in. It took me a few rude awakenings to figure out why.

---

rockingondrums said:
Yeah, I was. I've got an itch to switch (again) anyway. I'm the opposite of you; I always have media at max, but my alarm fades in. It took me a few rude awakenings to figure out why.
Click to expand...
Click to collapse
I personally just want color control. To me, features are more important so CM comes first unless there's a very similar AOSP-ROM that offers some key features I need. So I'll try to run CM and just ditch Franco if necessary Thank goodness the colors on the N5 aren't as bad as the stock N4. I just powered on my N4 and almost barfed.

---

dmo580 said:
I personally just want color control. To me, features are more important so CM comes first unless there's a very similar AOSP-ROM that offers some key features I need. So I'll try to run CM and just ditch Franco if necessary Thank goodness the colors on the N5 aren't as bad as the stock N4. I just powered on my N4 and almost barfed.
Click to expand...
Click to collapse
I just want to get rid of mp decision. BTW, I used this patch with Trinity's latest beta on cm nightly and audio in the alarm stream broke again, as well as torch.

---

One thing you can't do is just can't flash whatever kernel you want when it's built as a boot.img onto a ROM like CM, as the ramdisk for CM & AOSP are different, so you will have issues. To get them to work, decompile it, see if the kernel has specific kernel related changes in the ramdisk, decompile a CM kernel and pull the CM ramdisk, mod the ramdisk with the changes of the kernel that you want and rebuild the boot.img with the CM modded ramdisk with the kernel zImage of the kernel you want, that's basically what I do for Franco's kernel that's in my thread, it's Franco's kernel with a CM ramdisk that was modified to include all the changes he usually does.

---

I haven't really get the point. So if i want to use CM based rom and wanted to use AOSP kernel (non caf) i need to flash the CAF kernel and then flash the non caf zip?
Confused here
Sent from my Nexus 5 using Tapatalk