[KERNEL][MM][CM/AOSP][angler] ZigZag Kernel [R6][14-6-16]

[##W4TCH0UT##]

ZigZag Kernel​

Disclaimer:

#include 
/* 
 * Your warranty is now void
 *
 * I am not responsible for bricked devices, dead SD cards, thermonuclear
 * war, or the current economic crisis caused by you following these
 * directions. YOU are choosing to make these modificiations, and
 * if you point your finger at me for messing up your device, I will
 * laugh at you.
 */

Features:

• Zipped using anykernel2 by @osm0sis
• Latest linux patches
• -O3 Optimizations
• a57/a53 optimizations
• CDROM emulation drive support (DriveDroid support)
• CPU Overclock
• Wake Gestures: doubletap2wake, sweep2wake
• UKSM(Ultra Kernel Samepage Merging)
• KCAL Color control
• F2FS
• Frandom
• Zram, Zsmalloc, and Zpool
• UFS ICE driver
• Advanced TCP Congestion controls
• Kexec Hardboot Support
• Franco Sound Control
• Governors: ElementalX, ZZMoove, Impulse and the usual
• I/O Schedulers: BFQ, SIOPlus and the usual
• Many, many fixes to many stuff from CAF
• More fixes to stuff, check git

Downloads: ZigZag builds

Note: Builds with '-exp' in the suffix are not meant for daily users! Try at your own risk!

Credits:
Google
@faux123
@flar2
@franciscofranco
@Imoseyon
@savoca
CAF
CM

Changelogs on post #2

Enjoy people!

XDA:DevDB Information
ZZ Kernel, Kernel for the Huawei Nexus 6P

Contributors
##W4TCH0UT##
Source Code: https://github.com/W4TCH0UT/ZZ_angler

Kernel Special Features:

Version Information
Status: Stable
Current Stable Version: R6
Stable Release Date: 2016-06-14

Created 2016-04-19
Last Updated 2016-06-14

 

[##W4TCH0UT##]

Changelogs:

R6
* Latest f2fs patches
* Latest linux patches(Updated to 3.10.102)
* Usual tweaks from CAF
* Use franco's sound control instead of faux's
* Same Changelog for R6-exp with minor CAF experimental tweaks

R5-exp
* Enhanced sound quality(patches from CAF)
* Enhanced video quality(patches from CAF)
* Enhanced camera quality(patches from CAF)
* Fixes to major things
* Governors: ZZMoove, Impulse

R5
* Governors: ZZMoove, Impulse

R4
* More F2FS patches from kernel.org
* Upstream patches from google and CM
* Whole lotta fixes from CAF(check git for wide list of commits)
* Enable Zram, Zsmalloc and Zpool
* Squashfs file system intro

R3
* CDROM emulation drive support (DriveDroid support)
* Latest F2FS patches from kernel.org
* -O3 optimizations
* Kill some logspam
* Fixes from CAF

R2
* UKSM(Ultra Kernel Samepage Merging) 0.1.2.3
* Frandom
* Implemented UFS ICE driver
* I/O Schedulers: SIOPlus
* Advanced TCP Congestion controls(default: cubic)
* Fix Sound issues

R1
* Initial build
​

 

[Heisenberg]

Added to Nexus 6P index thread:

[INDEX] Huawei Nexus 6P

 

[HesThatGuy]

Good job on the support for F2FS. I hope more devs start to add support for their kernels and roms soon as F2FS continues to mature.

 

[iron maiden01]

Hello supported Ciyanogen? Very thanks

Regards

Enviado desde mi Nexus 6P mediante Tapatalk

 

[ps000000]

Welcome. :laugh::laugh::laugh::laugh::laugh:

 

[##W4TCH0UT##]

Hello supported Ciyanogen? Very thanks

Regards

Enviado desde mi Nexus 6P mediante Tapatalk

Yes works on cm/aosp too(not sure about aosp though)

 

[GreaterLesser]

Yes works on cm/aosp too(not sure about aosp though)

Works on AOSP (PureNexus) though I believe there is a sound issue. Have to double check and report back later.

 

[bobbarker2]

Good job on the support for F2FS. I hope more devs start to add support for their kernels and roms soon as F2FS continues to mature.

F2FS support is great and all but worthless at the moment since we don't have a way to format the three partitions ( system, data, cache) to really take advantage of potential gains f2fs as the offer.

The solution is pretty straightforward but I don't have the knowledge to know if it's feasible or not.

The road block is the fact that the 6p cache partition is under 1GB, which is a minimum requirement for f2fs to work.

There is TWRP custom build out there that's support f2fs but it only works on the data partition and that's meaningless as f2fs relies heavily on using the cache partition.

We could increase the size of the cache partition easily because the data partition is right next to it on the device and we could take space from data and allocate it to cache. I just have no idea of the possible repercussions of resizing partitions on an Android device.

My guess is that it would screw with Google releases and maybe there's something in the bootloader or kernel that needs to be edited so the device knows which blocks belong to which partition.

If it isn't a big deal to resize partitions, then its trivial. Use the latest f2fs-tools off github and make a TWRP kernel.

 

[shag_on_e]

I remember jt1134 modifying partitions for new ROMs to work on the Fascinate. Even coding RIL stuff single handedly for CM. I miss those days, when locked bootloader wasn't even heard of ?

 

[##W4TCH0UT##]

ZigZag R2 is out now!

R2
* UKSM(Ultra Kernel Samepage Merging) 0.1.2.3
* Frandom
* Implemented UFS ICE driver
* I/O Schedulers: SIOPlus
* Advanced TCP Congestion controls(default: cubic)
* Fix Sound issues

Kernel is stable from R2 onwards!

Cheers!

 

[bobbarker2]

I remember jt1134 modifying partitions for new ROMs to work on the Fascinate. Even coding RIL stuff single handedly for CM. I miss those days, when locked bootloader wasn't even heard of

Making a custom TWRP that allows the 6P to fully use F2FS has been on my "to-investigate/to-do" list for a while now. I've msg'd a couple people with experience in modifying the TWRP kernel and a few devs to see the feasability about changing partition sizes, but have gotten no responses

 

[bobbarker2]

* UKSM(Ultra Kernel Samepage Merging) 0.1.2.3
* Implemented UFS ICE driver
* I/O Schedulers: SIOPlus
* Fix Sound issues

I saw these and thought "oh thats new".. But I'm perplexed. Your kernel is a fork of CyanogenMod/android_kernel_huawei_angler with only a few commits done recently, https://github.com/W4TCH0UT/ZZ_angler/commits/53a3c39ecd976558df111fcd874e2d5edc391d1d. If that's the wrong repo/branch somehow then my bad but I just followed the link in OP.

Not sure why you're enabling ICE (Inline Crypto Engine) when the OEMs won't even use it because its unstable. Ofc HW backed encryption is better than software-only but Google also vastly improved it's keystore on M (compare the Nexus 6 encryption performance to the 6p).
From Android Explorations @ http://nelenkov.blogspot.com/

Unfortunately, while the current implementation performs pretty well, there are still some problems, especially when the device is in sleep mode. If the devices is in sleep mode for a relatively long period of time, read errors can occur, and the userdata partition may be mounted as read only (which wreaks havoc with the system's content providers); the device may even power off. While a reboot seems to fix the issue, if the the userdata was mounted read-only, the SQLite databases storing system configuration and accounts may get corrupted, which in some cases can only be fixed by a factory reset. Thus, hardware-accelerated disk encryption is unfortunately currently not quite suitable for daily use on the Nexus 6.

CAF even tried using it for our chipset then reverted it:

ICE (Inline Crypto Engine) support requires Key restoration after UFS power collapse. This operation adds long latency to exit from power collapse and will impact the performance even when ICE is not in use.

I mean, its worth experimenting with for sure. You don't until you try. But ICE has been around for a long time and there must be a reason no one uses it.

And I don't see where you added UKSM. Could you link the merge?

 

[##W4TCH0UT##]

I saw these and thought "oh thats new".. But I'm perplexed. Your kernel is a fork of CyanogenMod/android_kernel_huawei_angler with only a few commits done recently, https://github.com/W4TCH0UT/ZZ_angler/commits/53a3c39ecd976558df111fcd874e2d5edc391d1d. If that's the wrong repo/branch somehow then my bad but I just followed the link in OP.

Not sure why you're enabling ICE (Inline Crypto Engine) when the OEMs won't even use it because its unstable. Ofc HW backed encryption is better than software-only but Google also vastly improved it's keystore on M (compare the Nexus 6 encryption performance to the 6p).
From Android Explorations @ http://nelenkov.blogspot.com/


CAF even tried using it for our chipset then reverted it:


I mean, its worth experimenting with for sure. You don't until you try. But ICE has been around for a long time and there must be a reason no one uses it.

And I don't see where you added UKSM. Could you link the merge?

https://github.com/W4TCH0UT/ZZ_angler/commit/0b91f685a025db3c2c549aad51a2565fb1467755 , this is the commit for uksm, following it were some missing bits for it.

And, yes it is a fork of cm to support cm based ROMs.
If you could check the merges, then there's a lot that has been done.

I thought it would be a good way to experiment using the ICE driver as to what it brings. I know 6p's encryption system is better than 6, but what's the harm in experimenting?

 

[bobbarker2]

https://github.com/W4TCH0UT/ZZ_angler/commit/0b91f685a025db3c2c549aad51a2565fb1467755 , this is the commit for uksm, following it were some missing bits for it.

And, yes it is a fork of cm to support cm based ROMs.
If you could check the merges, then there's a lot that has been done.

I thought it would be a good way to experiment using the ICE driver as to what it brings. I know 6p's encryption system is better than 6, but what's the harm in experimenting?

There's no harm at all, except for users who will try this kernel and experience the instability and latency issues described above. If the users don't realize that you are experimenting with some untested features then they will just end up writing this kernel off and never use it. So maybe it would be a good idea to put a disclaimer or perhaps two different buildsl?

And it isn't just the 6p that was improved it was all Android 5.0 and up.

This ice chip has been on Qualcomm SOCs for a long time now and by that I mean since at least 2011. I'm sure they've made improvements over the past five years, but I suspect there's a reason no developer uses this in their kernel. Qcoms website has very little detail about even the existence of ICE, most of what we know has come from then submitting it to get FIPS certified.

 

[opz187]

There's no harm at all, except for users who will try this kernel and experience the instability and latency issues described above. If the users don't realize that you are experimenting with some untested features then they will just end up writing this kernel off and never use it. So maybe it would be a good idea to put a disclaimer or perhaps two different buildsl?

And it isn't just the 6p that was improved it was all Android 5.0 and up.

This ice chip has been on Qualcomm SOCs for a long time now and by that I mean since at least 2011. I'm sure they've made improvements over the past five years, but I suspect there's a reason no developer uses this in their kernel. Qcoms website has very little detail about even the existence of ICE, most of what we know has come from then submitting it to get FIPS certified.

I have not experienced 1 damn issue and been on R2 since release. in fact im getting better battery life than both kylo and elemental. im not sh***ing on their kernels, just stating my experience thus far. on latest DU TEST 4/18

 

[shag_on_e]

I have not experienced 1 damn issue and been on R2 since release. in fact im getting better battery life than both kylo and elemental. im not sh***ing on their kernels, just stating my experience thus far. on latest DU TEST 4/18

I kept getting a phone and SystemUI force close on 4/18. About to try zigzag 2 then retry 4/18 DU, then maybe the combo of the two.

 

[##W4TCH0UT##]

I kept getting a phone and SystemUI force close on 4/18. About to try zigzag 2 then retry 4/18 DU, then maybe the combo of the two.

Try clean flashing the rom, then the kernel.

Regards

 

[OmegaBlaze]

I can't speak on the battery life yet, but in terms of smoothness & scrolling; this kernel is ?. (Stock x Zigzag).

Any recommended settings @##W4TCH0UT##

Sent from my Nexus 6P using XDA-Developers mobile app

 

[skulldreamz]

This kernel is running really really smooth. I am very impressed so far with the performance and also battery life seems great as well. Please keep up the great work, as i see no reason to change kernels now. Only thing i ask for is maybe drive droid support and f2fs. Thanks so much