yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] komidzo:
Here's what I'm running:

Latest Pure Nexus Rom

Latest Flash Kernel with the init.flash.rc from Flash's Legacy 4.2 Kernel (See my post #3493), with nothing changed from [MENTION=6842057]The Flash[/MENTION]'s boot settings except inputboost disabled and the little core min freq set to 302. Honestly, these settings give the best experience I've had yet compared to his newer releases and even to EX and Franco.

I have naptime running and Greenify, but I'm not convinced Greenify really helps anything :p

Other than that, I do keep mobile data off all the time. I spent a couple years on Republic Wireless's $10/month plan, so I got used to doing everything without data, hopping from wifi spot to wifi spot (thanks McDonalds!). And on Google Fi now, I got $9.99 refunded last billing cycle!

Anyway, thanks Nathan for your work on this Kernel. It would be sad if you stopped work on it, but take care of what you need to in life. That's far more important than any of us here :p
[Nexus 6P Android Development] chrisexv6:
Going to try this myself.

What I find interesting, though, is that after a clean flash my idle drain will be about 1% per hour. Eventually it starts to go down and gets as low as .3% per hour. Then at some point along the way it starts to creep back up to 1% per hour. No changes along the way (i.e. not adding any apps, just a web browser, Best Fiends, Tapatalk (all notifications off) and an imgur browser). It seems odd, but I end up seeing the same drain you and the person who suggested the init.rc change were seeing.

I compared the init.rc from latest vs init.rc from 4.2 and there are plenty of differences. If I have the time (and patience) I might try adding the new changes one at a time to see what causes the break.
[Nexus 6P Android Development] psychomaniac189:
and then what????

open elemental x app which loads the stock settings from flash kernel, then go to governor options, pick load, pick the profile, do the same for big cluster? i dont have to do anything else?
[Nexus 6P Android Development] Balino:
You have to do it once, little and big cluster is the same, no matter where you load it. And check the apply on boot button in that page on top right, is a gray slider that becomes blue when enabled
[Nexus 6P Android Development] psychomaniac189:
Thanks. I noticed that after awhile you only have to load it once and it loads for both the little and big. Hoping this gives me some better battery life. I'm always looking for quick ways to get a little bit more juice out of my device.
[Nexus 6P Android Development] Bobbaloo:
I see you had it answered. Good.
[Nexus 6P Android Development] moi123:
Looks like it's working for me as well, will need to see how it goes the next few days. Thanks buddy!
[Nexus 6P Android Development] nikosrs4:
Is there any limitation to the NFC antenna? I'm trying to read a tag but no app can read/copy it. An image was nfced correctly.

Sent from my Nexus 6P
[Nexus 6P Android Development] nathanchance:
Fairly certain that NFC is not something the kernel handles. I've never added a commit that mentions NFC so even if it is in the kernel, it'd be stock.
[Nexus 6P Android Development] nikosrs4:
Thank you ?

Sent from my Nexus 6P
[Nexus 6P Android Development] komidzo:
Here's an update on how the init.Flash.rc swap is doing. I've been using it really light the last couple days. That said, over 3 days uptime with just shy of 4 hrs SOT is still doing just fine for me.
[Nexus 6P Android Development] TRgamer:
Thanks for the update... Will give it a try :good:
[Nexus 6P Android Development] luigidk:
Same here
[Nexus 6P Android Development] sengab1991:
Can you provide the modified kernel zip ?
[Nexus 6P Android Development] komidzo:
Two things:

#1 I'd encourage you to play around and try to do it yourself first. It really isn't very difficult.

#2 Its not my work at all, so I'd prefer it if [MENTION=6842057]The Flash[/MENTION] would give permission before I post it.

But really, try it yourself :)
[Nexus 6P Android Development] nathanchance:
I don't really mind. It's about to become obsolete in a bit. I hope to finish my rebase today.
[Nexus 6P Android Development] komidzo:
Here's the modified kernel that's about to be obsolete! But again, try playing around with doing it yourself.
[Nexus 6P Android Development] shekinahsmoke:
Ditto
[Nexus 6P Android Development] komidzo:
For anyone still wanting updates on how the mashup is going, I used a little more today:
[Nexus 6P Android Development] TRgamer:
After how many cycles you reached this stats? I'm asking cause I flashed the zip you shared and phone idle is about 4.5 right now.. Guess needs some time to settle down...
[Nexus 6P Android Development] komidzo:
Hmmmm... Mine settled down pretty quickly. My first cycle was the 3 days without charging that I posted. This is cycle #2. I'd do some wakelock troubleshooting if it doesn't go down soon.
[Nexus 6P Android Development] TRgamer:
OK... İ will wait and check what happens... Anyway thanks for sharing your zip and stats :good:
[Nexus 6P Android Development] Dbj.Dhaval:
Hey flash will u update the kernel today? No eta it's just I am about to format the phone try new rom so was wondering if u are then will do it after the update. Again no eta.
[Nexus 6P Android Development] Benjamin_L:
Just use the latest version and update whenever it is released. And you are asking for an ETA...
[Nexus 6P Android Development] Dbj.Dhaval:
I wanted to do a clean flash. I knew eta police will come.
[Nexus 6P Android Development] Benjamin_L:
What's wrong with the latest version? Also new security update will come tomorrow and there will probably be a new build anyway...
[Nexus 6P Android Development] nathanchance:
I am hoping to be done today but my time has been taken up elsewhere. Just use the most recent version, you'll be able to dirty flash the new kernel over it without any issues!

I personally don't care about ETAs :)
[Nexus 6P Android Development] kyzn:
A kernel update hardly warrants a clean flash. For one thing, when I'm on ElementalX, I let the EXKM do the update for me. Auto download and restart to install.

Do a clean flash now and just flash over the new version of the kernel. Unless Flash says otherwise.
[Nexus 6P Android Development] JPREMEEE:
Anyone phone die at 20%
[Nexus 6P Android Development] jfishbone311:
No issue here. Been using it since the last release.
[Nexus 6P Android Development] bgboii:
You arent the only one. It happens usually for me under 15%
[Nexus 6P Android Development] RanXeroxxx:
Is anyone having issues with saving/processing photos? After I snap a pic with or without hdr+ when I try to view it in gallery I get a grey image and have to wait a couple of minutes for it to appear. It's fine on a stock kernel. Thanks.
[Nexus 6P Android Development] nathanchance:
It's sdcardfs, it'll be fixed in the rebase.
[Nexus 6P Android Development] Neejay:
Nope, all is well here. I've never had a problem with camera/gallery that was kernel related.

Edit: I see it is a known problem then? Can't say that I've ever seen/noticed it...
[Nexus 6P Android Development] nathanchance:
Not every ROM enables sdcardfs, it is a build.prop entry.
[Nexus 6P Android Development] JPREMEEE:
Any ideas why? I reflashed (LOL) haven't any issues besides kernel auditor changing frequencies
[Nexus 6P Android Development] bgboii:
Im not sure why but I think it's a bug that Google has to fix
[Nexus 6P Android Development] RanXeroxxx:
Thank you. For now I've edited "ro.sdcardfs.enable=false" and it did the trick.

It was my ROM/Kernel combo. ResurrectionRemix and Flash.
[Nexus 6P Android Development] shadowstep:
Will the rebase also include the updates done to the conservative and ondemand governors by flar2 for big.LITTLE?
[Nexus 6P Android Development] nathanchance:
Yes it's on my list!
[Nexus 6P Android Development] HikingMoose:
Where could I read about his changes? I like conservative quite a bit. I can get it to do what I want easier than interactive. But the latter has more tuneables, so I keep trying to use it to dial in what I want. I want it to hold lower clocks as much as possible, yet also ramp down very slowly if I'm using the phone, I.e. scrolling. I hate scrolling lag, but can't get rid of it.

I'd be in heaven if someone would make touchboost tuneable! If it could be set to something like 672 or 960....holy cow would that be useful for me, I could hold back my ramping even more.
[Nexus 6P Android Development] xSilas43:
Does anyone have ram management issues? I find after half a day to a full day or so my free ram has dropped to around 300-400 and i find my phone extremely slow, havent had this issue on the orher kernel i use.
[Nexus 6P Android Development] nathanchance:
Most likely something with the mm stuff I have added in the past. A lot of that will be removed in the rebase, which I truly hope to have done today.
[Nexus 6P Android Development] chevycam94:
Are you still posting new kernels/TWRP builds to your website? Wasn't sure if you forgot about it, or were busy with other, real life things. :good:
[Nexus 6P Android Development] xSilas43:
no rush, im eager to try the rebase. loving the kernel otherwise! the hotplug seems to make a noticable difference.
[Nexus 6P Android Development] nathanchance:
Yup: http://nchancellor.net/Downloads/TWRP

I'll push a new TWRP build today or tomorrow.
[Nexus 6P Android Development] shadowstep:
This commit should give you what you're looking for, I guess. Coming to touchboost, it's hardcoded in the userspace and I don't think there is a way to change the frequency to which it is boosting to (which is 1248MHz for the 6P, I believe). You can only disable or enable it at kernel level at the moment.
[Nexus 6P Android Development] nathanchance:
IT IS HERE!

DOWNLOAD: http://nchancellor.net/Downloads/Kernels/

Welcome to Flash Kernel 2.0 so to speak; this kernel has been completely rebased from the ground up. I have learned a lot in these past few months about what should and shouldn't be added for the best overall experience. So rather than fix my source in steps, I just decided to start from scratch so to speak. Here's what I did:

Grabbed kernel source straight from Google fresh

Picked upstream Linux commits from kernel.org, fixing conflicts again (as I had messed some up before)

Added known working patches (like governors, I/O schedulers, file systems, and such)

Went through the remaining patches, evaluating what the patch exactly did, and locating the original source to see if it had been altered

Left out anything that was not relevant or helpful to our version

Cleaned up dmesg a ton, by removing spammy logs and warnings that should not have been happening

At the end, I have a much cleaner and stable kernel. You may notice that some of your favorite features are missing, that's not by accident. The part that got me really down a little bit ago is I felt like this process was going to be a waste. People have so many preconceived notions about kernels, like that they will give so much more battery and performance and it's hard as a developer to shake off those things. I've seen so many people in both this thread and a few others rave about and disparage this kernel for completely subjective and inaccurate reasons. While I don't necessarily care about number of users, it's disheartening to see something that I put out for free without absolutely no expectation of reimbursement get a bad rap. But I've just decided to ignore it or correct it when I can. If someone blames my kernel for their drain, so be it. I do this because I use my kernel myself and I like doing it, I hope you guys can respect that. Also, bug reports are going to change a bit. If I cannot reproduce your issue myself, I'm not going to fix it. Simple as that, I cannot go on wild goose chases for issues I don't experience. Logs will still be required but steps to reproduce will be as well. Anyways, off my soapbox lol, enjoy the kernel guys.
[Nexus 6P Android Development] AzraelsKiss:
[MENTION=6842057]The Flash[/MENTION] Ya know what they say... You can please some of the people all the time and all of the people some of the time... But you can't please all the people all the time. Keep up the good fight m8!

Have a good one!
[Nexus 6P Android Development] xatou:
[MENTION=5196311]flash[/MENTION] thanks for the new kernel! One question.. is permissive like the older one? I ask because I want to use it with magisk and arise sound mod.

Στάλθηκε από το Nexus 6P μου χρησιμοποιώντας Tapatalk
[Nexus 6P Android Development] nathanchance:
Yes, still permissive while reporting as enforcing for things like SafetyNet.
[Nexus 6P Android Development] nathanchance:
Telegram chat is back. I expect things to remain civil otherwise you will be removed: https://t.me/joinchat/AAAAAEJFGwFu603w9ogOHg
[Nexus 6P Android Development] joeyfong:
I got stuck in the boot animation
[Nexus 6P Android Development] kantjer:
Flash the stock boot.img for your ROM and then flash the kernel
[Nexus 6P Android Development] Bobbaloo:
Welcome back [MENTION=6842057]The Flash[/MENTION] and THANKS
[Nexus 6P Android Development] joeyfong:
should be a bad download, sorry
[Nexus 6P Android Development] dadoc04:
Thanks Nathan!!
[Nexus 6P Android Development] Pozanos:
Used 0207 kernel, love your work. Switched to the new build. THX!
[Nexus 6P Android Development] minhgi:
New build is much smaller than the previous one. You must have clean up allot of commits. I don't see any missing feature that I used with elementx kernel manager. I will report back with any finding or issue. Thanks again
[Nexus 6P Android Development] CappyT:
Can i flash it over the previous release or it's suggested to flash boot.img (stock one) first?
[Nexus 6P Android Development] Bobbaloo:
Just to be safe, I re-flashed my ROM (dirty) all is working great!
[Nexus 6P Android Development] kantjer:
If you are coming from a custom kernel other than Flash you should flash the ROM's stock boot.img first (or dirty flash the whole ROM)

In all other cases you should be able to flash this on top of your current kernel.
[Nexus 6P Android Development] Neejay:
Same here. I normally just flash on top of the previous flash kernel, but since this appears to be a huge change/rebase, I went ahead and dirty flashed my ROM first.
[Nexus 6P Android Development] Prattham:
Yea sure

Using ninja kernel

Sio plus 1536 dentist default

CPU freq 1.5 and 384 on little and 1.9 and 384 on big

That's pretty much it
[Nexus 6P Android Development] xperator:
Going to flash 1.4
[Nexus 6P Android Development] Ntress:
thank you dude will try this one this week
[Nexus 6P Android Development] nathanchance:
Awesome! Glad to see [MENTION=5051294]frap129[/MENTION] get some love, he's been doing some great things with Electron, I recommend everyone go check out his thread here and thank him for the work he has done: http://xdaforums.com/nexus-6p/orig-development/kernel-electron-kernel-angler-t3443431

I agree, already made them my personal default :) https://github.com/nathanchance/Ninja-Kernel/commit/510a7a3e9e80c2ca59c47a3ec25922f2ca53775b

Yeah those permissions and everything look right... I'll see if I can dig in later and come to a conclusion about that.

It's a modified thermal-engine.conf file to help with thermal throttling and rate of charge to the battery.

I would recommend it, I've done quite a few charges since then. I'd actually recommend dirty flashing your ROM first.
[Nexus 6P Android Development] xperator:
Finally :victory: the kernel is working perfectly, no more process usage issue :)

First time using and damn, this is well optimized and smooth :good:

Now time to start working on a custom governor based profile
[Nexus 6P Android Development] SlyUK:
Look forward to it :)
[Nexus 6P Android Development] kyzn:
Deadpool based please. ;)
[Nexus 6P Android Development] Ntress:
are you using Deadpool with the same current settings from 1st post?
[Nexus 6P Android Development] nathanchance:
Yes, I'll go update the OP now.
[Nexus 6P Android Development] xperator:
Anyone has issues with not seeing the governor options for Bioshock when set to Big cluster (EXKM) ? Is it just me or am I missing something ?

The governor options shows fine when Bioshock is set to Little cluster but they don't come up for Big. It says "Not available"

Edit: IntelliActive/Wheatley's options also doesn't show up for Big cluster. Seems EXKM doesn't play well with custom governors specially on big cluster
[Nexus 6P Android Development] kantjer:
Your personal build is my personal build [emoji6]

Sent from my Nexus 6P
[Nexus 6P Android Development] Nekromantik:
When using deadpool settings, is it worth lowering cluster 2 min to 384?
[Nexus 6P Android Development] xperator:
I would say no.
[Nexus 6P Android Development] nathanchance:
It's most likely because those governors have not been updated for big.LITTLE. Chill, zzmoove, and elementalx all show big cluster options because they have been updated for those values.

You can but I haven't noticed much gain in the battery life department from doing so.
[Nexus 6P Android Development] xperator:
Another question, are custom governors different across different kernels ? For instance governor "blabla" would have variables A, B and C in Ninja kernel, but is missing some of those variables or functions in different kernel because different version used.
[Nexus 6P Android Development] nathanchance:
Assuming they pick the same commits (99% of the time we do), the sys paths should be identical. For example, I picked chill directly from frap129 so I should have the same values as he does with Electron.
[Nexus 6P Android Development] sandman1234:
Just flashed PN with ninja. My device isn't rooted anymore?
[Nexus 6P Android Development] evilryry:
You're supposed to flash supersu after rom on PN. He removed built in root because there was several people who wanted to use systemless/system root so it was removed to give people the option to flash what they want.
[Nexus 6P Android Development] sandman1234:
You the man. So my bootloader should still be unlocked right? Only root is gone?
[Nexus 6P Android Development] evilryry:
Right, just download supersu zip and boot to recovery and flash it. All should be good at that point
[Nexus 6P Android Development] HikingMoose:
[MENTION=6842057]The Flash[/MENTION] I kind of thought that was why you posted that you might discontinue your development of your kernel. It must be hard developing, and working on something all the time (which I'm sure you're probably working on it, it thinking about it daily), and seeing someone foo foo your hard work. I think your feelings are completely understandable.

I'm glad you're sticking with it, there's a lot more users that like your work, than those that don't. If they don't like it, they don't have to use it. Those that love it, will greatly appreciate you and your work.

Keep putting up the good fight!

---------- Post added at 10:20 AM ---------- Previous post was at 10:03 AM ----------

Oh, don't get me wrong, I know touchboost is hardcoded, I wasn't saying it should be tuneable but isn't. I just wish it was tuneable, and that someone could find a way to implement it, or maybe just get input boost to boost when screen is touched.

I thought I remembered input body doing this, but lately it is delayed and only responds to input if you touch and hold the screen for 1 second. But I have never really used input boost, so I could certainly be misremembering. Others told me it had never and is not supposed to respond to input... So it's very confusing.

I like very conservative settings, slower to respond than when most will tolerate, it just gives me a smoother experience not having the clocks jump up and down constantly. But with my slower settings, I could really benefit from a boost when I touch the screen.

Nowamasayin?
[Nexus 6P Android Development] redsmith:
Woohoo Flash 2.0 is here! About the whole sdcardfs thingy, is that fixed? I've found that setting the sdcardfs flag to FALSE no longer causes issues with pictures in Gallery. Also, really long conversations in Whatsapp load much faster, and I'm pretty sure that's not placebo. So, I guess my question is, should I leave that flag set to false?
[Nexus 6P Android Development] shadowstep:
I'm sure all of us truly appreciate all that you do man. You're a mod on XDA, you take care of your kernel for not just one, but multiple mainstream devices, you keep churning F2FS supporting TWRP recoveries like a machine, you're killing it on the Substratum scene, you actively work on your own ROM, you contribute greatly to ROMs like DU and PN.. and all this while completing your degree AND having a life outside the tech world. It's nothing short of insane! So, a big THANK YOU once again! :)

Coming to your rebase, does this contain the March security updates or still based off the February security updates? I ask because the OP says February still (and you keep OPs updated, which is amazing, thanks again for that).

Of course, I didn't get you wrong mate. I've seen you lurking around the 6P forums a lot, so I already knew what you were trying to achieve when you posted before. :p I agree though, if touchboost was a tuneable, it would've been so much better for everyone, but then again, wishful thinking..

Coming to input boost, I'm not sure of what constitutes "input" for this tuneable. Does a simple touch to the screen (which can be on a blank/unused space of, let's take an example of an app or home screen, clicking which will not give any input to perform an action) constitutes an "input" or not. For touchboost, it does for sure, but for input boost, I'm not sure and to be honest I haven't checked too.

Nonetheless, good luck with trying to reduce power consumption as much as you can! :good:
[Nexus 6P Android Development] xSilas43:
looking forqard to trying the rebase out, im sure its incredible, you put a lot of hard work into it. :good:
[Nexus 6P Android Development] Bobbaloo:
[MENTION=6842057]The Flash[/MENTION] - The Man, The Legend, The Kernel. Experience 2.0 now!
[Nexus 6P Android Development] weazie:
Hiya,

For the first time ever with Flash kernel, I'm experiencing endless bootloop. I've downloaded the new kernel 3 times (2 times via phone, 1 with computer), I've flashed PN boot.img two times, let it boot, then this one, and still...

Stock kernel and older versions work fine. Re-download once more or something else? Thanks Flash for Your work, appreciated muchly!
[Nexus 6P Android Development] rakkkar:
The new rebased kernel is blazingly fast! No issues so far on Uber Rom and it feels like I just got a new phone ?
[Nexus 6P Android Development] martinomac:
I'm experiencing the same issue running latest PureNexus and SuperSU v2.79 SR3. I tried flashing this order: PN -> FLASH-N6P-20170308-0323 ->SU 2.79 SR3 but continued to bootloop. Tried downloading 3 times and MD5 matched up.
[Nexus 6P Android Development] nathanchance:
I tested sdcardfs and it was fixed for me. You can try using it again and just disable it if it isn't.

It's March lol, I wrote the OP when I thought I was going to be done this weekend.

I need a log. Make sure you are downloading the MD5 file alongside it as TWRP will automatically verify it before flashing.
[Nexus 6P Android Development] Neejay:
I used to have bootloops when trying that order too. I've found that I have to flash root first, then flash kernel.

And I also usually boot up once (ROM + SuperSU), then go back and flash the kernel ONLY.
[Nexus 6P Android Development] weazie:
MD5 matches. Do You mean TWRP "Copy log"-function?
[Nexus 6P Android Development] martinomac:
Thanks, I tried that but no go :( Will post logs shortly, just need to dirty flash PN and root.
[Nexus 6P Android Development] nathanchance:
I'd also like a dmesg and logcat while booting.
[Nexus 6P Android Development] weazie:
So to make it easy for you, and correctly - I just install Logcat extreme for example, then flash newest kernel - let it bootloop for a while - flash older kernel - as soon as I boot into ROM, I hit save on Logcat extreme?

Here's logcat. Unfortunately logcat extreme couldn't save dmesg, it shows it though.

The problem might be with Magisk 11.1. I read from PN thread just now that someone has had bootloop problems with Magisk.