yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] VanGolfer:
I installed new Google factory image, and flashed twice this kernel but still showing the google kernel. TWRP and sysytemless rooted. Can anyone help me ? Thanks
[Nexus 6P Original Android Development] SysAdmNj:
Does this kernel automatically keep settings on reboot? Or is there a setting the kernel manager app which I purchased and thanks.
[Nexus 6P Original Android Development] nathanchance:
You can purchase the EX Kernel Manager from the Play Store. It allows you to apply settings on boot and has an auto update feature. Great way to support the developer, good looking app, and it has deep integration with the kernel. I love it.
[Nexus 6P Original Android Development] flar2:
Just to make sure, please flash the stock boot.img, reboot to recovery, flash SuperSU, reboot to system, reboot to recovery, flash ElementalX.

I need to look at what the SuperSU installer does, as it seems to backup and restore a previous boot.img or something.
[Nexus 6P Original Android Development] SysAdmNj:
Yea, I purchased it as I tried to state lol. Just not sure where that setting was to keep settings on reboot.
[Nexus 6P Original Android Development] nathanchance:
It is the little circle icon next to the settings. It will spin and turn blue when you activate it.
[Nexus 6P Original Android Development] gman88667733:
Question, if I wish to switch from EX to a different kernel, how do I do so?
[Nexus 6P Original Android Development] SysAdmNj:
Thanks, wasn't sure what that meant.
[Nexus 6P Original Android Development] nathanchance:
Either dirty flash your ROM OR the stock boot.img if you are on stock Android. Then follow the instructions for your other kernel.
[Nexus 6P Original Android Development] flar2:
Stock ROM:

Flash stock boot.img, reboot to recovery and flash SuperSU, reboot to system once, flash ElementalX

Custom ROM:

Dirty flash ROM, flash ElementalX
[Nexus 6P Original Android Development] gman88667733:
Does this wipe any data?
[Nexus 6P Original Android Development] nathanchance:
No.
[Nexus 6P Original Android Development] flar2:
no
[Nexus 6P Original Android Development] THATTON:
I did flash it manually. It still shows 1.0.3. I actually did it twice. I also tried downloading from the app and from the link in the OP.
[Nexus 6P Original Android Development] flar2:
This is very odd. Are you on stock or custom ROM. If youare stock, try exactly what I suggest in the quote above.
[Nexus 6P Original Android Development] THATTON:
I'm running Cataclysm. I was flashing the kernel, then SuperSU 2.66. I'll do it in reverse this time.
[Nexus 6P Original Android Development] mobileman88:
Since I am already encrypted, no issue with leaving the encryption on and still using it rooted with xposed and ex kernel is there? Thanks
[Nexus 6P Original Android Development] nathanchance:
Correct, there is no issue. EX will work with encrypted and decrypted devices.
[Nexus 6P Original Android Development] mobileman88:
Thanks for the quick confirmation. This encrypted stuff is new to me.
[Nexus 6P Original Android Development] THATTON:
That worked [MENTION=298610]Flar[/MENTION]. I had gotten used to flashing SuperSU AFTER the kernel. Thanks for the help.
[Nexus 6P Original Android Development] flar2:
Yup, SuperSU is before the kernel for EX.

Otherwise it restores your previous kernel.
[Nexus 6P Original Android Development] ratson:
if i do a nandroid backup (from TWRP) of an encrypted system then create backup of /sdcard, wipe userdata than restore /sdcard and restore backup with EXkernel will i get a decrypted device with all data restored?
[Nexus 6P Original Android Development] nathanchance:
I don't believe so, I think TWRP backups are encrypted if you are encrypted and same for decrypted. You would need to copy your sdcard to your computer and copy them over after formatting data.
[Nexus 6P Original Android Development] ratson:
I am not sure if I only need to format /sdcard or /data too? In case /data I will have to use tibackup I guess. So please clarify what folders, partitions do userdata exactly mean.

Btw I accidentally encrypted my system while installing latest update by flashing boot (unnecessarily) and rebooting wo installing Elemental or supersu (since I had systemless). Don't make the same mistake...
[Nexus 6P Original Android Development] mobileman88:
Would be good for someone knowledgeable about the encryption stuff and TWRP to shed some light to this. I always thought TWRP is making unencrypted backups of the encrypted volume (decrypted on the fly when accessing /data). So when the TWRP backup is copied out, a unencrypted version will be on the PC unless the user selects the "encrypt with password" option in TWRP
[Nexus 6P Original Android Development] nathanchance:
You would need to format both sdcard and data.

I could be wrong about that to be honest but otherwise, people would just say backup, format then restore but I have never thrown that around.
[Nexus 6P Original Android Development] Raijin:
[MENTION=4684315]flar2[/MENTION]

I'd like to be able to enable and disable DoubleTap2Wake with Tasker. It's for a car profile.

I understand that, for your implementation, it's necessary to keep Sweep2Wake enabled too, true? So, for DoubleTap2Wake, the shell command for your one is the same than with the stock implementation?

echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture

Which are the commands for Sweep2Wake?

Thank you. I wish you a happy new year!
[Nexus 6P Original Android Development] lovemachine35:
FYI for folks using the AOSiP Rom. Using EX Kernel Mgr to upgrade to newest 1.04 kernel, pick the custom version to download. I originally picked express download and it boot looped on reboot. Probably because the kernel defaults to enforced selinux. The AOSiP rom requires permissive be set in kernel setup.
[Nexus 6P Original Android Development] drothenberger:
Here's a little expanded information for those that are interested.

SuperSU patches the boot image, and it can't patch an already patched image, so it makes a backup of the unpatched image before it does the patch. When you install SuperSU, it checks if the current image is patched and restores the backup if it is.

So if, for example, you install EX 1.0.3, then SuperSU, it will make a backup of SuperSU. If you then install EX 1.0.4 and reflash SuperSU, it will first restore your 1.0.3 backup.

For these reasons, I always flash stock kernel, then SuperSU, then EX, in that order. I do this when I want to update the kernel *and* when I want to update SuperSU. It's a little more flashing, but avoids surprises.
[Nexus 6P Original Android Development] Chilidog:
I was stock rooted 6.0.1 on ex 1.03 and I did the express upgrade to 1.04 and it didn't boot. I have tried everything and I still cant get my phone to boot...
[Nexus 6P Original Android Development] VanGolfer:
I had that too. So what's the correct procedures to avoid encrypted system? I guess I have to learn and flash again.

Thanks
[Nexus 6P Original Android Development] flar2:
Flash stock boot.img, then SuperSU, then EX.
[Nexus 6P Original Android Development] ShermanTenor:
[MENTION=4684315]flar2[/MENTION] - I've been avoiding a version of SuperSU higher than v2.52 as I didn't want a systemless root. Maybe I've misunderstood something along the way, but I had understood that systemless + xposed was a non-starter.

Anyway... I can't seem to get my 6p to boot after installing the new mmb29p update following the instructions a few pages back (flash boot, then vendor then system etc.) when I flash SuperSU v2.52 from TWRP. As an experiment, I tried v2.66 and I've got well past where I was before, and am now waiting for it to finish optimizing apps.

I appreciate this isn't EX related as I haven't even got that far yet, but is there an issue with SuperSU v2.52 and Marshmallow 6.0.1 in your experience?

Thanks - and sorry for the OT nature of this question...

---UPDATE---

I managed to get back into the phone, but nothing root related seems to be working. Very strange indeed. SuperSU (the app) says its v.2.66, but nothing which requires root access seems to work.

Scratching head...

Do I need to use a modified boot.img with MMB29P and SuperSU v2.52? Maybe that is the problem?
[Nexus 6P Original Android Development] Chilidog:
It still doesn't work. Does xposed affect this at all?
[Nexus 6P Original Android Development] chubby65:
Don't think so

I'm using xposed with Ex and systemless root and all is really smooth

Well for me anyway
[Nexus 6P Original Android Development] azsl1326:
Just flashed the lastest security update - system.img / vendor.img and then flashed the latest kernel 1.04 along with root and get the following error: "There’s an internal problem with your device. Contact your manufacturer for details."

I have backups but would like to know if this is fixable or if I need to revert to my latest nandroid.

Thanks, in advance!
[Nexus 6P Original Android Development] cabbieBot:
EDIT: it seems that the 'Xposed Additions' module will break camera launch via double-press power on Chroma/ElementalX
[Nexus 6P Original Android Development] drothenberger:
If you previously installed 2.52, you need to flash stock system image or the unSU zip floating around to remove it before you go systemless su.

There are no problems with xposed and systemless root. The only issue is that xposed will modify your system partition, so Android Pay won't work. But systemless root will still work fine.

You can't use 2.52 without a modified boot image. The later versions of SuperSU automatically modify the boot image for you.

If I were you, I'd flash stock system, then stock boot.img, then SuperSU 2.66, then ElementalX, then xposed. Do that all at once in recovery and then boot to system.
[Nexus 6P Original Android Development] ShermanTenor:
Thanks - I had been flashing the stock system.img from MMB29P as per flar2's earlier post. I had forgotten about the need for a patched boot.img for SU v2.52, but it looks like there isn't one yet available for MMB29P anyway.

I tried installing SU v2.66 again, but again ran into problems getting any root apps to run. I put the phone down for about 10 minutes to do some more research online, and then noticed that it had finally popped up with new SU prompts to allow root access. Maybe something was still loading in the background - not sure.

I'll give SU v2.66 a go now - thanks again.
[Nexus 6P Original Android Development] marbertshere:
So I don't know much about kernel tweaking. I usually flash a kernel, select a governor (ElementalX) and a I/O scheduler (FIOP). I leave everything else stock. I would like to tweak for battery life. I read a post about tweaking the interactive governor. What do you guys suggest? Can doing the tweaks really help me or just leave it be?
[Nexus 6P Original Android Development] nathanchance:
I have heard those tweaks have kind of hit or miss. Some said drastic results, others saying not at all. Honestly, I was really into tweaking when I first got into kernels but as time went on, the only things I still change are wake gestures, vibration, and colors. Underclocking and undervolting have become nearly obsolete with newer technology and tweaking the governor seems like more trouble than it is worth. I trust the stock settings enough to get good battery life. You can always change the values, test, then revert if you do not like it.
[Nexus 6P Original Android Development] marbertshere:
The ElementalX governor is tweaked to reduce battery use, correct?
[Nexus 6P Original Android Development] Mikulec:
Are you bsure u flashed the right vendor file? Cause this is error you get when you flash the system.img without the vendor file.
[Nexus 6P Original Android Development] mobileman88:
For those who would like more battery. The v2 and ghost pepper governor songs works very well. Look at post 2 of http://xdaforums.com/showthread.php?t=3269557

Remember to disable touchboost
[Nexus 6P Original Android Development] ratson:
just for the record

- twrp backup data

- copy /sdcard to pc

- fastboot format userdata

- copy from pc to /sdcard

- restore data in twrp

are the needed steps to decrypt without losing any data.
[Nexus 6P Original Android Development] mobileman88:
Did decrypting it give much added performance?
[Nexus 6P Original Android Development] ratson:
not much, it can only be noticed during extensive io operations (like installing an app). but since I am pushing my phone to the limits with custom kernel and governor tweaks I decided to not skip this performance increasement.
[Nexus 6P Original Android Development] hbkekko:
hi guys, yesterday i upgraded kernel with the app notification even if i'm on MMB29M. Since now i want to upgrade cataclysm and i've to flash vendor of new factory image, will i have some issues? have i to follow some steps for this upgrade? (flash vendor, cataclysm, root, flash again elementalx?)
[Nexus 6P Original Android Development] phistyle:
does this work with systemless rooted roms? I'm missing the swipe to unlock a lot.
[Nexus 6P Original Android Development] Millz120:
Yeah, I'm systemless right now running Pure Nexus.
[Nexus 6P Original Android Development] phistyle:
How did u flash? Kernel then supers 2.66?
[Nexus 6P Original Android Development] Millz120:
I'm on Pure Nexus. Not sure if this is a universal thing, but my steps go something like this...

1) Dirty flash ROM

2) Flash UnSu

3) Flash Kernel

4) TWRP > Advanced > Terminal (Type these two in, they won't return anything)

"echo SYSTEMLESS=true>>/data/.supersu" + "echo BINDSYSTEMXBIN=false>>/data/.supersu"

5) Flash SU 2.66
[Nexus 6P Original Android Development] Alhaddad:
I'm already on 1.04, however EXKM still offers me to update
[Nexus 6P Original Android Development] ZiggSVO:
anyone have NTFS support working?

Trying to use a USB drive formatted to NTFS and its not recognizing it and my nexus is telling me that its not a supported format?

Running Current Cataclysm
[Nexus 6P Original Android Development] adrman:
With ElX, flash the kernel after SuperSU.
[Nexus 6P Original Android Development] sean222:
I don't think there is native support for NTFS. I installed an app called StickMount to get my NTFS USB drive recognized.
[Nexus 6P Original Android Development] flar2:
I haven't tweaked it at all, I've been happy with Interactive

Try those tweaks and see for yourself

Please flash boot.img, then SuperSU, then ElementalX

yes

Yes, of course. It works with everything.

Why are you doing all this stuff? Just flash Pure Nexus, then flash ElementalX

I'm guessing you flashed SuperSU after flash ElementalX. SuperSU is restoring your previous kernel.

As mentioned, you need to use an app like StickMount to mount the drive. The kernel supports NTFS (and exFAT), but the drives still need to be mounted. Android doesn't do this automatically, so you need StickMount.
[Nexus 6P Original Android Development] belloni:
I flashed vendor/system/boot but getting google play services error once booted and got the vendor out of date message?
[Nexus 6P Original Android Development] Slartibartfast_:
Do we really need SuperSU 2.66 (systemless) before we flash this kernel? I'm on 2.52 (latest version of "standard" SuperSU).
[Nexus 6P Original Android Development] Kappa Lamda:
Why do we need to type these on twrp? I typed nothing and have no problem.

I flashed kernel first, the 2.66 and have no problems.
[Nexus 6P Original Android Development] nathanchance:
It is for if you want Android Pay to work on Pure Nexus. If you don't care, stick with 2.52 or 2.64+ for System root.
[Nexus 6P Original Android Development] adrman:
Just following instructions
[Nexus 6P Original Android Development] geoff5093:
Great work! I purchased your app as well. I noticed that under the CPU settings, if I set the minimum to 3xx MHz, when I leave and go back it goes right back to 12xx MHz being the minimum. I believe this is for the low powered cores.
[Nexus 6P Original Android Development] flar2:
Yeah, try not to touch that for now. I have to handle touchboost in the app.
[Nexus 6P Original Android Development] geoff5093:
Will do. One last question, what does the circle next to some settings mean when you press it and it turns blue? Is it an apply on boot button?
[Nexus 6P Original Android Development] igalmarino:
Yep

Sent from my Nexus 6P
[Nexus 6P Original Android Development] TonyStark R.I.P.:
[MENTION=4684315]flar2[/MENTION]

Thank you sir for your continued excellent development here on XDA:good:
[Nexus 6P Original Android Development] just4747:
Also having a few issues, some mentioned in here already:

Getting the faded/dim washed out colors on boot after setting some color corrections in your Kernel Manager app (until I enter Developer Settings again).

Even when selecting the little circular power button icon which (I think) is for keeping the Double tap to wake setting on boot, it never stays set after a reboot.

Pretty sure it is related to the Kernel because I didn't have the issue before, but a few times since yesterday I am showing no carrier service at all (no signal whatsoever) until I reboot. Airplane mode/data toggling doesn't work, only a reboot. I woke up to it this morning.

---------- Post added at 10:04 AM ---------- Previous post was at 10:02 AM ----------

I also have a slightly yellowish/warm screen and I used similar settings to yours but slightly different and it works great to my eyes - so much better:

Red: 232

Green - 232

Blue - 256

I also changed contrast to 132 just because.

Awesome!
[Nexus 6P Original Android Development] bsg411:
I pumped it up a bit to try to get the white to pop.....I using the following:

Red: 230

Green: 225

Blue:256

Saturation:27

Value:145

Contrast:142

Hue:0
[Nexus 6P Original Android Development] just4747:
Ok now I am having pretty consistent issues where I have no service at all and it says Emergency Calls only.

OP, is it possible this is related to the kernel or the kernel settings? I didn't have any issues a day or so ago at all and now I am barely able to get it to say I have any service at all....
[Nexus 6P Original Android Development] flar2:
99.9% sure that's not related to the kernel. I've made no changes to those subsystems

Did you install 0.03? That should solve the washed out color on boot.

Dt2w on boot has a timing issue, I will look into it
[Nexus 6P Original Android Development] just4747:
Ok good to know, although now I am not sure what would've caused it other than the radio I flashed to get Band12 working (sorry, unrelated to this thread, I know).

I will flash .03 now, thank you.
[Nexus 6P Original Android Development] flar2:
You should probably go back to the original radio, that's most likely the cause of your cell service issue.
[Nexus 6P Original Android Development] just4747:
It's possible, although the first few days I had it flashed I did not have these issues at all. The reason I thought it maybe had to do with your kernel was due to the time it started happening, but is most likely a coincidence.

I will flash the radio back tonight though to see.
[Nexus 6P Original Android Development] minieod:
with the 6p and 6.0 (was running 6.0 on my n6 before) i dont find a need to really root.....yet

im sure the time will come, but for now i want to try out android pay and see if keeping the phone root-less is worth the benefit of pay - i gave up on it with the n6 and rooted since i had it with 5.0

anyways, point of this post: im a little unsure of the requirements for android pay. 6p bootloader is unlocked, i have a custom boot.img and twrp on ---- if i install this kernel will it auto insert root? it says in the first post about chainfire's su module. i'd love the functionality of elementalx working in the background, but not needing the foreground tweaking it at the moment

if installing this will auto push root status and break a-pay, then ill skip for now, til i deem a-pay not needed

thanks flar!
[Nexus 6P Original Android Development] L_Insomnia_P:
I believe I have read someone on here that ChainFire's systemless root actually works with Android Pay, but he said to expect Google to fix Android Pay for this root.
[Nexus 6P Original Android Development] bongostl:
Did you all see that the 6p hardware can support qc2? Might this be something that is doable at the kernel level?

The Nexus 6P does have Quick Charge 2.0 compatible hardware

http://phandroid.com/2015/11/06/nexus-6p-quick-charge/
[Nexus 6P Original Android Development] flar2:
This kernel does not auto-install root, you are safe to install it. I also don't modify the system partition, so you should be all good.
[Nexus 6P Original Android Development] flar2:
Yeah, I saw that too:

https://github.com/flar2/angler/commit/bed1c9c5425eff72bd600ca6da7fc1a7fa9036ce

I'm not going to mess with charging yet, until I learn more about USB C.
[Nexus 6P Original Android Development] omf05:
So glad to be able to change the super warm color! I had just got off the phone with google about getting RMA. Then your Kernel saved the day :)
[Nexus 6P Original Android Development] marcadam:
Just bought the EX kernel manager, it's beautiful and functional, worth every penny.
[Nexus 6P Original Android Development] likonvampire:
App bought , will be rooting and flashing this tonight once I am back from MTL tonight ..
[Nexus 6P Original Android Development] Fauert:
Fuyyyy.... :eek: :thumbup: :D
[Nexus 6P Original Android Development] Az Biker:
In the eternal words of David Lee Roth: CLASS DISMISSED! :p
[Nexus 6P Original Android Development] c_86:
Still not seeing disable touch boost in cm13...
[Nexus 6P Original Android Development] marbertshere:
Okay, one last question. How do you save a "profile"? I ran a script to test it out after backing up the kernel. Is all I need to do is set "apply on boot" for everything?
[Nexus 6P Original Android Development] flar2:
In version 1.04 I added the touchboost path to file contexts to change its selinux context to something more accessible, if it still doesn't work there is probably nothing I can do. I can't install CM to test, so either troubleshoot for me, or I would suggest using a ROM that doesn't mess around with normal things that devs expect to work.

Only set apply on boot for settings you want to change
[Nexus 6P Original Android Development] flar2:
Update!!!

This is a minor update.

A couple ramdisk fixes and I added the bluesleep_timer wakelock blocker. App support will follow when I have time.

Unfortunately I've been extremely busy at my regular day job lately and haven't had time to do all the things I want to do RE: app and kernel updates.

Download

ElementalX-N6P-1.05

Changes:

-fix dm-verity warning for non-root users

-add check for touchboost file_context

-bluedroid_timer wakelock block
[Nexus 6P Original Android Development] guitar1238751:
I was just about to flash 1.04. Good thing I saw this now. Thanks
[Nexus 6P Original Android Development] :
Thanks flar for the "how to" and the update. I just bit the bullet and went systemless. I feel like I'm in the "new age" era now. [emoji12]
[Nexus 6P Original Android Development] XavierD8188:
Assuming it's ok to flash 1.05 with a rom that's still based on MMB29M?
[Nexus 6P Original Android Development] DroidIt!:
Hey [MENTION=4684315]flar2[/MENTION] a little variation on all the flashing talk :) I'm currently on AICP which has the 2.52 binaries built in. I'm fine keeping those. I'm going from MMB29M to MMB29P. I wiped all and sitting at bootloader. Would I just flash the 29P boot.img and vendor.img, go to recovery and flash your kernel and the rom and boot up then? Like i said not worried about SU 2.66 and good with 2.52, so would that be good?
[Nexus 6P Original Android Development] flar2:
Yes

Assuming that AICP system you currently have installed is compatible with the new boot.img and vendor.img, that would work.
[Nexus 6P Original Android Development] XavierD8188:
Thanks, Flashing with Pure Nexus now.. Great work, I've been seeing some really good battery life with your kernel. Was gonna try other ones but I'm a firm believer in, 'If it ain't broke, don't fix it' so I'll be sticking with your kernel.. Thanks for the work again.. :D
[Nexus 6P Original Android Development] DroidIt!:
It is for the 6p, thank you :)