[KERNEL][CAF]WhitePugKernel for the Nexus 5[7.1.2] - Nexus 5 Android Development

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
WhitePugKernel by joe2k01​
This kernel is only for CAF 7.1.2 ROMs
How to install:
Download the flashable zip
Boot in TWRP
Flash zip
Reboot and you're done
Compiled using Linaro 6.3.1 and full upstream to Linux 3.4.113​
Feautures:
XZ kernel compression
ZRAM support
Colors control
Vibration control
Wakelocks control
USB fast charging
BFQ I/O scheduler
zen I/O scheduler
Z-RAM
MSDOS fylesystem support
NTFS filesystem support
NTFS writing support
zen I/O scheduler
More to come
Donate to IARC or SaveTheChildren
https://www.iarc.fr/en/about/donations.php
http://www.savethechildren.org
Downloads:
V1: Download
V2: Download
XDA:DevDB Information
WhitePugKernel for the Nexus 5, Kernel for the Google Nexus 5
Contributors
joe2k01
Source Code: https://github.com/joe2k01/WhitePugKernel-lge_hammerheadcaf
Kernel Special Features:
Version Information
Status: Stable
Created 2017-09-12
Last Updated 2017-10-12

---

Reserved

---

Oh my god this is working great thanks man

---

Interesting. Gonna try.

---

Good to see a new CAF kernel.
Keep it up.
Saluti dall'italia

---

how so

---

zx604176460 said:
how so
Click to expand...
Click to collapse
Maybe you flashed a non CAF ROM by mistake. The installer checks that the device code name is hammerheadcaf

---

joe2k01 said:
Maybe you flashed a non CAF ROM by mistake. The installer checks that the device code name is hammerheadcaf
Click to expand...
Click to collapse
I am using AOSPA CFA ROM

---

zx604176460 said:
I am using AOSPA CFA ROM
Click to expand...
Click to collapse
Okay it looks like AOSPA kept device name to hammerhead instead of hammerheadcaf. You can wait for me to push a new zip or you can open the current one and add a hammerhead to the devices list, behind hammerheadcaf
--- EDIT ---
I've uploaded a new zip. You shouldn't encounter any problem now

---

joe2k01 said:
Okay it looks like AOSPA kept device name to hammerhead instead of hammerheadcaf. You can wait for me to push a new zip or you can open the current one and add a hammerhead to the devices list, behind hammerheadcaf
--- EDIT ---
I've uploaded a new zip. You shouldn't encounter any problem now
Click to expand...
Click to collapse
It is now his job thank you

---

ohh CAF is alive again, can u merge with TrueSight?
D820 @ crLOS 14.1

---

santi1993 said:
ohh CAF is alive again, can u merge with TrueSight?
D820 @ crLOS 14.1
Click to expand...
Click to collapse
No. TrueSight's dev has a different concept of how I want to manage my new kernels. I want to keep them minimal with only some tweaks to improve battery and performance. This kernel has a full upstream to Linux 3.4.113, while TrueSight is stuck at 3.4.0. So no, I won't merge TrueSight stuff

---

santi1993 said:
ohh CAF is alive again, can u merge with TrueSight?
D820 @ crLOS 14.1
Click to expand...
Click to collapse
Just curious... crLOS ?

---

joe2k01 said:
No. TrueSight's dev has a different concept of how I want to manage my new kernels. I want to keep them minimal with only some tweaks to improve battery and performance. This kernel has a full upstream to Linux 3.4.113, while TrueSight is stuck at 3.4.0. So no, I won't merge TrueSight stuff
Click to expand...
Click to collapse
Thanks for sharing ur concepts!
Well, then can we suggest some cherrypicking? One thing id loved on CAF with custom Kernel is the ability to amplify speaker beyond limits, it was called speaker volume on adiutor
D820 @ crLOS 14.1
---------- Post added at 10:23 AM ---------- Previous post was at 10:22 AM ----------
daedric said:
Just curious... crLOS ?
Click to expand...
Click to collapse
im at crdroid! it has CAF n NON CAF, since first build to 3.4 i was on CAF, but then TS kernel got outdated and i had no clue on goin to AOSP
D820 @ crLOS 14.1

---

joe2k01 said:
No. TrueSight's dev has a different concept of how I want to manage my new kernels. I want to keep them minimal with only some tweaks to improve battery and performance. This kernel has a full upstream to Linux 3.4.113, while TrueSight is stuck at 3.4.0. So no, I won't merge TrueSight stuff
Click to expand...
Click to collapse
Hi joe,
which CAF base rom do you suggest to use with your kernel?
Thanks

---

Pjotr91 said:
Hi joe,
which CAF base rom do you suggest to use with your kernel?
Thanks
Click to expand...
Click to collapse
I like to use halogenOS, it's a really nice ROM with a really nice team. But I may have something in the bakery for the ROM scene too, who knows

---

Running good here, thanks for developing caf kernel. :highfive:

---

Trying it now, so far so good... Thanks for your effort!
Inviato dal mio Nexus 10 utilizzando Tapatalk

---

Hello!
I want to try to build unofficial AICP CAF with your kernel.
What string should I add into "aicp_manifest.xml" file in ".repo/local_manifests/" folder to make it possible?

---

Update: I appreciate your effort and I thank you for the time you have devoted to the development of the kernel, but I believe you prefer me to be sincere and not declare wonders when things are somewhat different. Therefore, I must say that, even if your kernel is stable, still it appears to be on par with lineage stock kennel, and still not up to TrueSight, which provides better performance, much better battery life, especially during standby, yet worse audio quality-speakerphone for example is unusable.
If I could express my opinion, I would suggest you pick up True Sight, fix audio, update it with latest security patches and we would have THE perfect kernel for CAF. Just my two cents!
Anyway, thanks again for your time and your dedication!
Inviato dal mio Nexus 10 utilizzando Tapatalk