[KERNEL] [6P] [8.x/7.1.x] [2018-02-14] Kernvatore v3.11 - Nexus 6P Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* kernvatore-angler.c
* --------------------------
* YOUR WARRANTY IS NOW VOID
*
* I am not responsible for bricked devices, dead SD cards,
* sick/abused animals, thermonuclear war or you getting
* fired because you missed your alarm.
*
* Do some research if you have any concerns about features
* included in this kernel BEFORE flashing it!
*
* YOU ALONE are choosing to make these modifications,
* and if you try to blame me for messing up your own
* device, I will drink your tears.
*/
Introduction
Kernvatore is intended to be a super light and lean kernel, much like leanKernel or ElementalX. Kernvatore only exists because Imoseyon has not been able to update leanKernel in a while, and I miss his kernel very much. Though I would never claim my kernel compares to the great leanKernel, I do aim to make it as close to the original lk experience as possible. The only place where this kernel really deviates from lk is the included I/O schedulers. However, including additional ones does NOT make this kernel any less lean, so no need to worry. I know some people love to change settings, even if you recommend they don't, so I just want to provide ample choices in that department. I have no desire to add new CPU governors at this time, as most of them are highly unstable and have been ported many times between devices.
Click to expand...
Click to collapse
Features
Built from the latest Oreo sources
InteractiveX V4 governor is the default (replaced original interactive)
KCAL color control support from @savoca
Optimized for cortex-a57/a53 and built using UBERTC optimized 4.9.x toolchain
Performance/stability optimizations
Some unnecessary features were removed/disabled
No F2FS support currently (trying to find time to merge upstream f2fs again)
Full SDCARDFS support
Synced with upstream to the latest 3.10.x version (currently 3.10.105)
Disabled forceencrypt to widen adoption
No longer patched with any root solution as of v2.x, so you can choose your own root adventure
Removed dm-verity
Filter ro.boot.verifiedbootstate from /proc/cmdline (for SafetyNet checks - Android Pay/PoGo/whatever)
Some code pulled from CAF repo directly, likely more to come in the future
Enabled deadline and ROW I/O schedulers (both built-ins, but disabled by default)
Added FIOPS, SIO, SIO+, Zen I/O schedulers - FIOPS is the default.
Kexec support with hardboot
Config access via /proc/config.gz - mostly for us nerds
Disabled ZRAM and swap
Rudimentary support for init.d scripts in /system/init.d using run-parts (but neither the zip nor the kernel's ramdisk will EVER mount your system RW, so this does not enable support where it doesn't already exist).
Gesture sleep/wake support
FauxSound support
More features will be added as I see fit, as long as they don't add too much "heft" to the kernel.
Click to expand...
Click to collapse
Installation
Download the zip
Flash the zip in TWRP or using your preferred flashing app
BEER
Click to expand...
Click to collapse
Downloads and Changelog
Pushbullet channel
XDA:DevDB Information
Kernvatore N6P, Kernel for the Huawei Nexus 6P
Contributors
vt0r, imoseyon, franciscofranco, googy_anas, flar2, ryanbg
Source Code: https://github.com/vt0r/kernvatore-angler
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.11
Stable Release Date: 2018-02-14
Created 2016-09-29
Last Updated 2018-02-14

---

Frequently asked questions
Q: What's with the two zips for encrypted and unencrypted?
A: If your device is encrypted, and you want it to stay that way, use the "-encrypted" variant. This is an absolute must if you're using FBE with Oreo (and possibly Nougat as well).
If your device is not encrypted, either join the dark side and encrypt it, or avoid using the "-encrypted" zip.
Q: I run XXXXX ROM. Will it work?
A: Should no longer be an issue, as we're using AnyKernel2 by @osm0sis. IT SHOULD NOW BOOT ON ANY ROM. If you find one that isn't working, please provide all the logs you can possibly get (see log question below).
Q: I'm just getting a bootloop. What should I do?
A: Please provide logs if you have them, or at least provide full details about your setup and what steps lead you to the bootloop (also see log question below).
Q: How can I collect debug logs?
A: Download and flash my debug log collector zip file in TWRP. This zip will gather some common kernel/boot logs and create a tarball in /sdcard/debug_logs that you can upload to some file sharing site for me to review. Once you've flashed the zip, you can either pull the resulting archive using adb or reflash some kernel that previously worked, reboot back into the system and upload from your phone. Either PM or post the link where I can retrieve the log archive, and I'll review as soon as possible. This does not guarantee I'll be able to resolve the issue, but it should provide a great deal of debugging information either way.
Click to expand...
Click to collapse

---

Reserved

---

Thanhks.... ??????
Enviado desde mi Nexus 6P mediante Tapatalk

---

Welcome
:laugh::laugh::laugh:

---

So what's the difference between normal interactive on other kernels and interactiveX in this? :fingers-crossed:
Sent from my angler using XDA Labs

---

Prattham said:
So what's the difference between normal interactive on other kernels and interactiveX in this? :fingers-crossed:
Click to expand...
Click to collapse
Created by kernel developer Imoseyon, the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery v/s performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.

---

I'm not going to ask you to disable force decryption, you're the author of this good work. But can i at least ask why you wont? You seem to have strong reasoning behind it

---

At first i read it as ''KERVINATORR'' n i was like '' now thats one badasss kernel right there.'' lol

---

eqbirvin said:
I'm not going to ask you to disable force decryption, you're the author of this good work. But can i at least ask why you wont? You seem to have strong reasoning behind it
Click to expand...
Click to collapse
Absolutely. I'm a paranoid fool, so the thought of intentionally disabling Android's full disk encryption (or file-backed encryption) just makes my stomach turn.
Also, unless things have changed drastically since the N6, unencrypted devices don't even offer that much of a performance boost, especially considering the encryption ops are all done on chip using the built-in AES-NI extensions, which are extremely fast. I just can't fathom someone voluntarily foregoing protection on a device that's so easy for some to lose, just for some perceived performance boost.
TL;DR - I don't want to be the one to make your device less secure, so just update the fstab in the ramdisk if you're one of those who wants to disable encryption, but please don't tell me about it, because I don't like to cry.

---

Lord. Tech said:
At first i read it as ''KERVINATORR'' n i was like '' now thats one badasss kernel right there.'' lol
Click to expand...
Click to collapse
It's a play on my name (Salvatore), but your version sounds a little cooler for sure.

---

@vt0r
hey mate
i wanted to try your kernel.zip but with no luck
i'm on stock N with systemless root and stock kernel....
flashed with flashfire but it says "no 6p device abborted"
But I have to say I've unticked the mount/system read write option in FlashFire .. Because I want a full OTA support
Just an example in screenshot
with elementalx i had not this ......maybe ex kernel doesn't touch the system partion?
hmmm weird

---

danmaman said:
@vt0r
hey mate
i wanted to try your kernel.zip but with no luck
i'm on stock N with systemless root and stock kernel....
flashed with flashfire but it says "no 6p device abborted"
But I have to say I've unticked the mount/system read write option in FlashFire .. Because I want a full OTA support
Just an example in screenshot
with elementalx i had not this ......maybe ex kernel doesn't touch the system partion?
hmmm weird
Click to expand...
Click to collapse
Sorry, but I'm having trouble understanding what you mean. Can you provide the recovery.log, please?
Based on what I think you mean, it's not detecting either of the property values it checks to ensure your device is a 6P, so I'm expecting the log to confirm this.
Also, neither my zip nor ramdisk scripts will EVER try to mount system RW, so that option has nothing to do with the failure. My zip doesn't even mount system RO.

---

vt0r said:
Sorry, but I'm having trouble understanding what you mean. Can you provide the recovery.log, please?
Based on what I think you mean, it's not detecting either of the property values it checks to ensure your device is a 6P, so I'm expecting the log to confirm this.
Also, neither my zip nor ramdisk scripts will EVER try to mount system RW, so that option has nothing to do with the failure. My zip doesn't even mount system RO.
Click to expand...
Click to collapse
all good now...
i flashed the 32mb boot.img not the zip.....and all ist good
thanks a lot
i'll test now

---

Considering this kernel is for N and TWRP cannot decrypt android N yet, I cannot flash because it does not disable force encryption. This is kind of a catch 21.
---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------
vt0r said:
Absolutely. I'm a paranoid fool, so the thought of intentionally disabling Android's full disk encryption (or file-backed encryption) just makes my stomach turn.
Also, unless things have changed drastically since the N6, unencrypted devices don't even offer that much of a performance boost, especially considering the encryption ops are all done on chip using the built-in AES-NI extensions, which are extremely fast. I just can't understand someone voluntarily foregoing protection of a device that's so easy for some to lose, just for some perceived performance boost.
TL;DR - I don't want to be the one to make your device less secure, so just update the fstab in the ramdisk if you're one of those who wants to disable encryption, but please don't tell me about it, because I don't like to cry.
Click to expand...
Click to collapse
I do I update the fstab in the ramdisk as you speak of? I would be willing to do so if it is not such a hard process so I can try this kernel. Thanks in advance!

---

yung40oz84 said:
Considering this kernel is for N and TWRP cannot decrypt android N yet, I cannot flash because it does not disable force encryption. This is kind of a catch 21.
---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------
I do I update the fstab in the ramdisk as you speak of? I would be willing to do so if it is not such a hard process so I can try this kernel. Thanks in advance!
Click to expand...
Click to collapse
TWRP 3.0.0-1 upwards support N. I'm encrypted and have been not facing any issues on any kernels I've tried so far.
@OP, really excited to try this. Gotta love leans.

---

After flashing this kernel and rebooting phone, I could not boot back into rom. After 15 minutes waiting I booted back into twrp and it asked me for a password which I have never set. Was only able to mount system as read only. After trying to read the sdcard, it says I have 0mb of space. After trying to flash factory images it says that it cannot write system.img as it does not have enough space. I have tried all options that I can think of. Any help would be appreciated.

---

yung40oz84 said:
...TWRP cannot decrypt android N yet.
Click to expand...
Click to collapse
This is not true. Visit http://dl.twrp.me/angler and grab the latest (3.0.2-2 I believe), which has no issue decrypting /data.
yung40oz84 said:
I do I update the fstab in the ramdisk as you speak of? I would be willing to do so if it is not such a hard process so I can try this kernel...
Click to expand...
Click to collapse
I wouldn't recommend it for beginners, but there are utilities to make the process simpler, like abootimg and similar. Check their man pages for usage info.
My current recommendation is to use some other kernel that disables forced encryption if you don't want your device to be encrypted.

---

atrus5 said:
After flashing this kernel and rebooting phone, I could not boot back into rom. After 15 minutes waiting I booted back into twrp and it asked me for a password which I have never set. Was only able to mount system as read only. After trying to read the sdcard, it says I have 0mb of space. After trying to flash factory images it says that it cannot write system.img as it does not have enough space. I have tried all options that I can think of. Any help would be appreciated.
Click to expand...
Click to collapse
Try doing a full wipe in TWRP i.e. system,data and cache

---

atrus5 said:
After flashing this kernel and rebooting phone, I could not boot back into rom. After 15 minutes waiting I booted back into twrp and it asked me for a password which I have never set. Was only able to mount system as read only. After trying to read the sdcard, it says I have 0mb of space. After trying to flash factory images it says that it cannot write system.img as it does not have enough space. I have tried all options that I can think of. Any help would be appreciated.
Click to expand...
Click to collapse
Ok I'm going to need lots more info to help here.
First, which ROM were you trying to boot into?
Second, were you unencrypted?
Third, where is the error you're getting about not having enough space? TWRP? Fastboot? Something else?