yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] nathanchance:
Okay, good to hear! Yes, LZ4 is enabled on ZRAM: https://github.com/nathanchance/Ninja-Kernel/blob/m/arch/arm64/configs/ninja_defconfig#L1065. It is now enabled on crypto as well. GZIP is for the actual kernel on a whole.
[Nexus 6P Android Development] kantjer:
Because I build the inline with the ROM, it doesn't have the anykernel stuff.

Sent from my Nexus 6P
[Nexus 6P Android Development] hinxnz:
I haven't even looked at any of kernel packages yet and also anykernel either, I just assumed that the kernel packages just include the zImage, maybe some include a script to edit ramdisk and anykernel thing just basically unpacks the boot image and makes a new boot image with the new kernel.

Do you not recommend flashing new kernel on top of your build? I'll have a look at kernel.zip etc later though and see what actually happens..

Edit: Do you recommend just to flash zImage instead?

Edit: But LZ4 compression is usually set in ramdisk too..

Edit: Cheers ↓↓ I out of thanks again
[Nexus 6P Android Development] kantjer:
Have a look at this to see what Anykernel is/does.

In the 1.4 kernel [MENTION=6842057]nathanchance[/MENTION] removed the thermal-engine.conf and modules references from AnyKernel so you should be OK to flash it on top of my build.
[Nexus 6P Android Development] FanDroid09:
What exactly do you mean by "temporary dark camera"?

I'm running that same setup and Snapchat seems to be working fine.

Are you using the correct vendor?
[Nexus 6P Android Development] nathanchance:
Update your vendor.

Because it is flar2's implementation and he changed the sys paths for EX Kernel Manager. Either switch to that or modify the sysfs values under /sys/kernel/sound_control.
[Nexus 6P Android Development] nathanchance:
F2FS TWRP update!

Pulled in the latest TWRP upstream changes so it is now bumped to 3.0.3-0 due to their app release. I don't know if decryption is working or not but personally (sorry if this sounds blunt) I don't care. I don't have a way to test if it works or not since I am decrypted and I am not encrypting to test. This build comes without any support so don't bother me with issues, I'm not going to fix them. If it works, great, if not, sorry, it works fine for me and that's all that matters. This is only really to enable F2FS support and it serves its purpose.

Download link: twrp-3.0.3-0-angler-f2fs-20161216.img

How to switch to F2FS:

Boot into TWRP

Flash a ROM that supports F2FS (and this kernel if you want)

Go into Wipe > Advanced Wipe and select Data

Click change filesystem

Choose F2FS and swipe to confirm

Reboot

NOTE: This will wipe your internal storage as well so back that up before this process. I am also going to try to work with Beans to get Pure Nexus full F2FS support.
[Nexus 6P Android Development] samorgs:
I'm already running PN 7.1 with F2FS. Used your earlier TWRP to convert data partition, flashed PN, gapps, SR5 SuperSU & your kernel.

All appears good so far.
[Nexus 6P Android Development] chikimonke:
FYI the stable release of SuperSU 2.79 is out. Quick question, is the latest PN F2FS compatible or is that your own build?
[Nexus 6P Android Development] samorgs:
Latest build of PN is what I'm using.
[Nexus 6P Android Development] eduardozeassesme:
Can I use is as a normal recovery?
[Nexus 6P Android Development] nathanchance:
Yes, it is just TWRP, I just don't know if it will work while you are encrypted
[Nexus 6P Android Development] eduardozeassesme:
Thanks, my device is unencrypted
[Nexus 6P Android Development] nathanchance:
That's intentional
[Nexus 6P Android Development] Citizen_Snips:
It does not. Still giving an error about invalid password. Also had some trouble booting after flashing it. It would keep rebooting if it sat on the boot up password entry field. Finally got my password in before it rebooted and booted fine. Flashed back the old TWRP and all is right in the world again. Just reporting for others!
[Nexus 6P Android Development] Dbj.Dhaval:
Hi. I have two questions

1.is it possible to decrypt without using pc that is without using fastboot command as I don't have laptop or pc

2. I have heard that SuperSU doesn't work with f2fs. Is it true?
[Nexus 6P Android Development] shadowstep:
It's the same version, just with interactive governor on the big cluster in place of ironactive governor. The small one would be on impulse.
[Nexus 6P Android Development] nathanchance:
1. You can in TWRP, Wipe > Format Data

2. I don't know, I use phh's Superuser inlined into my ROM so there is no mounting of the su.img.
[Nexus 6P Android Development] Pollie81:
Thanks Flash,

I was doing some reading and searching lately because now i have a lot of free time i wanted to try f2fs. Thank you for this updated twrp and info.

So if i understand in correctly; if you want to use f2fs. Both the rom and the kernel needs to support f2fs?
[Nexus 6P Android Development] vibranze:
What is the diff between the Governor profile in CPU - Governor and those in Governor options. I am having a Flash as a CPU governor but in governor options I am using Hawktail6p1.2.

Sorry if this question has been asked and explain before.

Thank you.
[Nexus 6P Android Development] infamousvincci:
+1 .

Im curious too.
[Nexus 6P Android Development] shantam3108:
Super su isn't working with nitrogen on f2fs. Gives bootloops but some guy posted above that it works with PN
[Nexus 6P Android Development] ariefabuzaky:
So PN is F2FS support ?
[Nexus 6P Android Development] hh11bbaacchh11:
Hey. I don't mean to sound stupid, but can anyone tell me, in layman's term, what UKSM is and for what it is? i just want to know since it's enabled on Flash's settings on th OP.
[Nexus 6P Android Development] Samuel Holland:
It saves memory by merging duplicate pages into single pages therefore using less memory I believe. Here's the wikipedia link: https://en.m.wikipedia.org/wiki/Kernel_same-page_merging.
[Nexus 6P Android Development] nathanchance:
Ultra Kernel Samepage Merging, it basically conserves memory by combining duplicating pages: https://en.wikipedia.org/wiki/Kernel_same-page_merging
[Nexus 6P Android Development] shantam3108:
Somebody few pages back flashed it and it worked for him with super su 2.79 and didnt bootloop but for me on nitrogen it did bootloop so using superuser on nitrogen with f2fs
[Nexus 6P Android Development] 1Ishara:
Hi flash in OP you have mention that in you setting you have put thermal throttling limit to 48c .. can please tell how you apply that limit using exkernel app?
[Nexus 6P Android Development] nathanchance:
It should show up in the CPU section.
[Nexus 6P Android Development] Thunderbolt:
On this ZIP there are 3 profiles.

N6P
[Nexus 6P Android Development] Rakuu:
No, it's three files for setting it three different ways.
[Nexus 6P Android Development] Thunderbolt:
Now i dont understand IT. I suppose that i unpacking ZIP to exkm profile, boot exkm, CPU governor and pick up.

N6P
[Nexus 6P Android Development] hh11bbaacchh11:
One is to be used in init.d folder, the other is a governor profile for EXKM using stock frequencies, the other is a governor profile for EXKM with overclocked frequencies. That's how I understand it. I stand to be corrected. If I am right, hope it helps you.
[Nexus 6P Android Development] Thunderbolt:
Thank U bro. So lets do IT. I have folder init no init.d on the system folder.

N6P
[Nexus 6P Android Development] ariefabuzaky:
Could you check again your data in TWRP ? Cz i try PN with f2fs, yes its boot but when i check again my data, it comeback to ext4
[Nexus 6P Android Development] Lawlrus:
That's strange, even less than a few pages back Nate stated he was going to work with beans to get full f2fs support on pure nexus.

Id trust a developer that works on the rom before I would a user.
[Nexus 6P Android Development] shantam3108:
True that is why in the previous post I said I didn't try myself. For me it bootlooped when I used so using super user
[Nexus 6P Android Development] clambert11:
Ok, I've had a bizarre issue for a while but haven't said anything because I was dirty flashing and hadn't seen anyone else complaining about it. Recently I clean flashed PN 7.1.1 with Flash Kernel 4.1 and it seems I still have the issue. Honestly it could be a EXKM issue but I thought I'd start here to see what you all think.

The problem is when I reboot Sweep2Wake stops working. I've got it set to up and it's set to apply on boot. In order to get it working I have to disable the gesture and then turn it back on and re-apply. No reboot needed.

Has anyone heard of this happening before? I'm running version 2.94 of EXKM.
[Nexus 6P Android Development] bkrickles01:
Happens to me too
[Nexus 6P Android Development] Sheetzie03:
You could try to go back a version or 2 of the app until its fixed
[Nexus 6P Android Development] nathanchance:
Happened to me on every kernel that I've run on this device, I think it is an EXKM issue because I can set it up in ramdisk without any issues.
[Nexus 6P Android Development] drothenberger:
I had a kernel oops this morning with 4.1. I've attached the log in case it's useful.
[Nexus 6P Android Development] Bobbaloo:
Maybe it's intentional? If I booted and it was enabled and I forgot, pocket calls or worse could result. Thanks for the kernel [MENTION=6842057]The Flash[/MENTION] !
[Nexus 6P Android Development] clambert11:
I brought it up on G+ and then did a little experimenting myself. Here is what Aaron said:

I reverted to the stock PureNexus Kernel and it seemed to have the same problem. I then installed ElementalX and everything seemed to be fine. I'm really just reporting my findings. It's not a big deal by a long shot.
[Nexus 6P Android Development] hinxnz:
You could apply an init.d script if kernel supports it, most kernel tuning apps give you this option but flar2's doesn't seem to.

For example:

echo 4 > /sys/android_touch/sweep2wake
[Nexus 6P Android Development] RASanchez007:
Yo ShadowStep can we still do this thing to the kernel on 7.1.1 to get sweep2wake to keep working off reboot?
[Nexus 6P Android Development] flar2:
Turns out there is something more going on. If you apply the setting too early in the boot process, wake gestures dont' work. I've changed the scripts in my kernel to apply the settings "on boot completed" and it solves the problem. I have no idea why this is the case, it doesn't make sense and I don't know when this behaviour started.
[Nexus 6P Android Development] clambert11:
Cool! Thanks for the update. I appreciate it.
[Nexus 6P Android Development] nathanchance:
Hmmm interesting, I was able to get them working with on boot but I had to change some permissions around (this is my personal branch, I attempted to do the same thing in my release branch but it doesn't seem to have worked). I'll have to mess around with it this weekend myself and see if there is a way to fix the apply on boot with EXKM in the kernel/ramdisk.
[Nexus 6P Android Development] shadowstep:
Yep, it sure is. I've taken the init.flash.rc files from the latest versions of Flash Kernel (namely v1.14 for Android Marshmallow 6.0.1, v3.16 for Android Nougat 7.0/7.1 and v4.1 for Android Nougat 7.1.1), edited them to enable sweep to wake (up & down) by default so that when you flash the kernel zip containing this modified file instead of the original one, sweep to wake (up & down) will be enabled by default and will persist through reboots.

Following are the steps to be followed (in order, on a Windows machine) to achieve this, in case anyone is looking for it:

Download the latest version of Flash Kernel (Click here if you're using Android Marshmallow 6.0.1, click here if you're using Android Nougat 7.0/7.1 or click here if you're using Android Nougat 7.1.1)

Download the appropriate modified txt file from the attachments in this post for your Flash Kernel version (init.flash.rc.flash-1.14.txt for Flash Kernel v1.14, init.flash.rc.flash-3.16.txt for Flash Kernel v3.16 or init.flash.rc.flash-4.1.txt for Flash Kernel v4.1)

Once you've downloaded the attachment, rename the file to init.flash.rc from init.flash.rc.flash-1.14.txt, init.flash.rc.flash-3.16.txt, or init.flash.rc.flash-4.1.txt

Open the downloaded kernel zip file using the native windows zip viewer or a third-party zip program that can edit zip files (7-zip, etc.) and delete the existing init.flash.rc file from the ramdisk folder present in the kernel zip file

Paste the downloaded and renamed init.flash.rc file (which you downloaded and renamed from the attachments in this post) in the ramdisk folder present in the kernel zip file

Save your changes (if needed/prompted) and close

Now, the flashable zip that you have of Flash Kernel will have sweep to wake (up & down, both) enabled by default and it should work fine. :)
[Nexus 6P Android Development] weazie:
Rad. :)
[Nexus 6P Android Development] drothenberger:
Hey [MENTION=6842057]The Flash[/MENTION], I had another reboot this morning.
[Nexus 6P Android Development] nathanchance:
Hmm low memory killer was going to town, I'll look into this, thanks for the log.
[Nexus 6P Android Development] discodestroyer10:
Seems like 2% battery drop fix works fine, at least for until now (85%)

#n6p
[Nexus 6P Android Development] Vaseag:
Phone was charging over night and in the morning i also had ~85%
[Nexus 6P Android Development] Nekromantik:
delete
[Nexus 6P Android Development] bartendersimon:
Does anyone having issue wil HotSpot after last update?
[Nexus 6P Android Development] Arzee08:
Like the device using the wi-fi dropping connection all the time but still showing as on on your phone?
[Nexus 6P Android Development] bartendersimon:
That is the issue I'm having. I didn't get that error with the RC version
[Nexus 6P Android Development] Arzee08:
Funny that as I thought it was my provider updating the local cell tower ( which they have been doing a lot lately). But yeah I have been having this issue over the past few days , I wouldn't put it down to just this kernel tho as I did try elite and elemental x with the same outcome so I don't know what the cause would be.
[Nexus 6P Android Development] Herk718:
After listening to like 4 songs on iHeartRadio continuously, my data just drops, and I have to either go in airplane mode or turn data off/on or clear app from recents menu to get it running again, don't know if it's kernel related or just the app itself :confused:
[Nexus 6P Android Development] bartendersimon:
But the thing is that i dont have that issue with the RC version before this one. So i dont really know, i rolled back to the RC version and now no issues so far.
[Nexus 6P Android Development] Shockz:
Not sure why a kernel would cause this issue. Try wiping data for that app and see if the issue persists.
[Nexus 6P Android Development] xflowy:
would u guys recommend blu_active or zzmoove gov. for a snappy and smooth phone experience. and zen or maple sch.? tolerating some more battery drain for this performance gain ofc.

thanks :)
[Nexus 6P Android Development] nathanchance:
I'd go with blu_active and I/O scheduler doesn't really contribute to smooth performance but I've been a huge fan of maple.
[Nexus 6P Android Development] fapste:
[MENTION=6842057]The Flash[/MENTION] I have conducted a survey on /r/Nexus6p and surprise surprise there are alot of people who faced Bootloop of death (the phone can't go into recovery and flashing stock images wouldn't breath the life into the phone either). Bootloop of death is where the phone never gets past Google logo upon booting and never makes it to the Android boot animation. Some people can't even go into recovery and flashing stock images or erasing EFS isn't helping either.

The issue started appearing since 7.0 and still persist in 7.1.1. What is your take on it? What do you think might be the cause of this bootloop of death. A victim had a dialog with Huawei and they told him that there is some sort of nasty bug in the kernel that is erasing the partition tables or something. Your Views please.
[Nexus 6P Android Development] nathanchance:
It could be for a bunch of different reasons. eMMC failure, BCL going crazy, software bug. I doubt it is a kernel issue but it is possible I suppose. I haven't really dug into it because it sounds like a hardware issue that may be exacerbated by software.
[Nexus 6P Android Development] fystrified:
hey flash any governor profile works well with flash cpu governor?
[Nexus 6P Android Development] fapste:
What's BCL? EMMC failure doesn't look like the probable answer because if EMMC had failed, it would have given them errors upon flashing ANYTHING onto the phone in bootloader mode.

Can I link the Google form survey here and may be you can make it sticky for gathering more data that might help in figuring out a pattern or a probable cause?
[Nexus 6P Android Development] nathanchance:
Switch to interactive to use profiles, flash is purely there for my profile.

Battery current limit, it is basically a hotplug driver that monitors battery capacity and unplugs cores when the phone gets low; this can cause hard shutdowns but not anything like what has been documented.

You can link it here but I don't really want to put it anywhere, it's not really relevant to the thread.
[Nexus 6P Android Development] adinkwok:
I am trying to get in contact with Huawei about this problem, having gone through it myself (getting a replacement from them though! :silly:). I will continue to pester them until I can get an answer from their engineers, but until we get some concrete answers, this discussion should stay out of this thread ;).
[Nexus 6P Android Development] fapste:
Sure thing. That's why I am holding off of updating to 7.x.x. I have created a survey and posted the results on reddit but some PRO GOOGLERS have come there with pitchforks to kill me :D

I am not in US or Europe so RMA is completely out of the question. I guess it;s true for majority of the users. That's why I would love Google to give some sort of statement or reasons for this bootloop. May be you can create issue on Android issue website and create a thread asking users to star it in order to bring Google's attention to it. Otherwise I don't see Google releasing any statement on this issue at all.

I am trying to save them from a lurking death of their phone but they don't want that :D However most of the people on XDA are very cooperating and providing data to resolve/figure a probable pattern for this issue.
[Nexus 6P Android Development] tcat007:
Love DU ROM and tried Unicorn blood for a few cycles but never got above 4.5 hrs sot. First cycle on Flash:
[Nexus 6P Android Development] leondestiny:
Alright ! first of all , this is by far my most favourite custom kernel, i love it!

now to my question, i hope someone can clarify a few things for me.

so from a reddit post regarding flash kernel + exkm (elemental kernel config app).

to use these for better battery life

"Cpu: Gov options: hawktail 1.2. Small cluster MHz Min: 302, Max: 1708. Large cluster min: 302, Max: 1958. Hot plug: msm_hotplug.

GPU: Backlight dimmer enabled

Misc: read ahead 1024kb. Fsync disabled(you may want to leave this on..Google it..almost doubles read speed with it off though.) Set all the wakelock options to enabled.

Memory: Turned zram off."

now to my questions, is it safe for my phone to have zram turned off and having these enabled on boot 'Hot plug: msm_hotplug.'

'GPU: Backlight dimmer enabled' (i know that backlight dimmer only reduces brightness correct? so it should be safe to have it enabled set on boot i guess?)

and what about these in Misc: read ahead 1024kb./ Fsync disabled, and also enabling all the wakelock options in the Misc section. (is it safe to do all this?) and i think i am only aware that fsync could mess it up for me so i wont touch that.

i have the 32gb 6P.

sorry for the long post, hope someone can help.
[Nexus 6P Android Development] HikingMoose:
Would if be ok if I asked you all with personal experience with of latest builds people prefer? Is there one that was slightly more stable, or performed better than any others? I haven't used Flash in a while, sorry. I'll read the last couple pages and see what I find. But that likely will not answer my inquiry.
[Nexus 6P Android Development] nathanchance:
I've never put out a buggy build. I run all of my changes for at least a week before releasing.
[Nexus 6P Android Development] HikingMoose:
I didn't mean one might be buggy. I have the latest build downloaded. I just wanted to make sure there wasn't one that is more favored. A couple ROMs I use were more stable in December, and their last builds have decreased battery life, and are not as smooth. They are great developers, and no one is complaining . But some older builds were a little better. That was all, I was wondering. I meant no disrespect.

You know, it's just how life is. Some days at work I perform way better than others. It's not physically possible to improve every day, or for developer to improve every single build, sometimes a new build might not be as good. I'm not saying that's the case here. I just wanted to ask which of the last few builds might be the best in people's opinions. I know you guys do this out of the kindness of your hearts, and are always striving to improve, that goes without question. Thank you for what you do.
[Nexus 6P Android Development] nathanchance:
No disrespect taken lol. You can try running both 4.0 and 4.1 to see what happens, that's probably my only advice.
[Nexus 6P Android Development] juzkimmi:
hi everyone! been a long time lurker since ninja days! after I updated to PN 7.1.1 rom and flash 4.1,, my settings thru EX manager just won't survive a reboot. I have to set every up again from gestures to vib strength to frequency. I have looking around for solutions but none found. I'm just wondering any of you facing this problem? I have Nvr had a problem since ninja kernel days. baffled.
[Nexus 6P Android Development] efan3719:
there is an option in EX Kernel manager to set at boot next to whatever option you are changing. Have you enabled that for the settings?
[Nexus 6P Android Development] moi123:
Have been on PN Marshmallow & Kylo all this while primarily because I need stability as a daily driver, and recently updated to the final PN MM build (Aug), decided to try Flash kerne. And right out of the bat I'm experiencing incredible batt standby time. I think this is attributed to this fab kernel.

Will be waiting a few more months on stable 7.1.1 builds to hit, and then Flash again (pun intended!)

Keep up the fabulous work!!
[Nexus 6P Android Development] juzkimmi:
yes yes of course. [emoji23]
[Nexus 6P Android Development] clambert11:
Damn! Saying Ninja Kernel just feels weird now. Feels like an eon ago even though it wasn't. The name Flash Kernel just fits like a glove.
[Nexus 6P Android Development] efan3719:
just tried it with tap to wake and it wouldnt work until i unlocked the device at least once. i have fingerprint unlock. after that everything worked as it should.
[Nexus 6P Android Development] shuckeru:
From what i understand Doze on the go in the 7.0+ android versions are supposed to keep doze on even while the phone is in your pocket and you're moving around.

This doesn't seem to be the case for me. Is it working well for anyone? i've noticed the drain is worse with v4.1 of the kernel compared to when i used v4.0. But it should be noted that doze itself works fine when it sits on my desk. Regardless, I've checked a few wakelocks and removed remotely possible apps as well that may hold any wakelocks from motion. No improvement there. I'm wondering if Flash itself has tampered with doze...

my setup is in my signature.
[Nexus 6P Android Development] nathanchance:
I can't touch doze with the kernel, it is a userspace thing. The kernel sleeps like a baby, my average screen off drain is between 0.15%/hr and 0.50%/hr.
[Nexus 6P Android Development] moi123:
Would you mind sharing your (EXKM) settings? Any Greenify? Kudos again to such an excellent kernel! :good:
[Nexus 6P Android Development] redskinsfan:
What is your average screen on drain?
[Nexus 6P Android Development] nathanchance:
I'll update my settings in the OP later. No Greenify or anything like that.

15-20%/hr, varies on what I am doing