yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] JaylanPHNX:
The first post should be moved to the second, and the first should just be a lot of empty space with this in the middle.

From my Tab Pro 8.4
[Nexus 6P Android Development] xperator:
No I didn't mean TouchBoost. I know TouchBoost is disabled. I was talking about InputBoost. And the toggle option which I saw in other kernels ( Kylo and Franco ) is not there.

By the way [MENTION=6842057]nathanchance[/MENTION] setting duration to 0 does not disable InputBoost. It still fires up the ramping stage
[Nexus 6P Android Development] nathanchance:
Setting the frequency to zero is probably necessary then. I'll look and see if I can find the commit that enables that.

EDIT: Found it, it'll be in my release tonight.
[Nexus 6P Android Development] xperator:
I thought so too but the effect is still there. Maybe I'm wrong but from my observation I can see the InputBoost is still working even if you set values to 0. The only bulletproof way is to disable it using the toggle option (in EXKM) or by running the script command.
[Nexus 6P Android Development] shadowstep:
Yep. You can find the flashable zip here!
[Nexus 6P Android Development] dpalmer76:
Is automatic high brightness mode available with this kernel. Searched thread but only found one post. Wanting to flash. Thanks in advance.
[Nexus 6P Android Development] kantjer:
yes, I use it.
[Nexus 6P Android Development] dpalmer76:
Do I need a separate app to enable. I only see option to turn on and off. Using Ex Kernel Manager
[Nexus 6P Android Development] panooos:
Check High Brightness Mode Widget from flar2
[Nexus 6P Android Development] kantjer:
yes, you can use the widget [MENTION=4408192]panooos[/MENTION] suggested, alternatively you can also use Tasker to set HBM
[Nexus 6P Android Development] nathanchance:
Update for N and M!

Releasing this because Franco added a patch today that should help with fingerprint sensor lag (basically schedules this task on the big cluster and boosts the CPU frequency while that is done). It is not going to be a miracle worker but it has helped. Also cleaned up the code base a bit, removed some old/outdated patches. I cleaned up input boost (cpu-boost) so it should function like on other kernels.

Download: v3.2 for N and v1.6 for M

Changelog for N:

Short list:

Rebased kernel (removed old/outdated patches)

Cleaned up input boost (added enabled/disable toggle)

Added a patch to make BFQ a bit better

Added a patch to improve the response of the fingerprint sensor

Added some optimization patches for virtual memory and workqueues

Long list:

Title: NINJA: v3.2

Author: Nathan Chancellor

Hash: 21ba7bb91255b1580fbb2f3f40c4da42e0e281e0

Title: input: synaptics: high prio and not unbound wq

Author: Francisco Franco

Hash: 9c6cc867e21e7c1fab38a953f2164d273a7fd2b2

Title: Revert "input: synaptics: use a higher prio workqueue"

Author: Nathan Chancellor

Hash: 850d73f618482bf33d349acda963756cd0b468ca

Title: vmstat: squash 4 patches from upstream

Author: Francisco Franco

Hash: fe420f7c04ca7b4d0353a9e42e45811b8cdf40fd

Title: drivers: fingerprint: boost tasks to the big cores when the scanner is used

Author: Francisco Franco

Hash: 551d798b465e3b4e26fe386504e23343998d017d

Title: drivers: fingerprint: boost cpufreq on unlock

Author: Francisco Franco

Hash: fdc7dec5431d57895e55025e8aa0bae1ddbe6ff6

Title: power: smbcharger: queue work on system_power_efficient_wq

Author: Francisco Franco

Hash: 6b68dc25c2bb0b7edeeeee01c3be62437a393596

Changelog for M:

Short list:

Rebased kernel (removed old/outdated patches)

Cleaned up input boost (added enabled/disable toggle)

Added a patch to make BFQ a bit better

Added a patch to improve the response of the fingerprint sensor

Added some optimization patches for virtual memory and workqueues

Long list:

Title: NINJA: v1.6

Author: Nathan Chancellor

Hash: 592ba9e8d4054b4ecfd2921b29df4feb18bae595

Title: input: synaptics: high prio and not unbound wq

Author: Francisco Franco

Hash: 442d0392a6a3dd7f2ec61ad5befbe3240f03411f

Title: Revert "input: synaptics: use a higher prio workqueue"

Author: Nathan Chancellor

Hash: 645e72ae557254926e7947a3a6a92e2b0aaf0efa

Title: vmstat: squash 4 patches from upstream

Author: Francisco Franco

Hash: b7521a6942eacce35f1a1d6b5633394bd7ac7483

Title: drivers: fingerprint: boost tasks to the big cores when the scanner is used

Author: Francisco Franco

Hash: ae74b6f73eeb8130c24055498fb2b5ac23f4f486

Title: drivers: fingerprint: boost cpufreq on unlock

Author: Francisco Franco

Hash: cd48a581e45c59d9db00d53c1ce9f1844a13f494

Title: power: smbcharger: queue work on system_power_efficient_wq

Author: Francisco Franco

Hash: dd13888692dc7a8892ec4867e2703ff31eaf691f
[Nexus 6P Android Development] primo14z:
can we just dirty flash over the older version?
[Nexus 6P Android Development] kantjer:
yes
[Nexus 6P Android Development] Prattham:
Which rom are you on

I guess du?
[Nexus 6P Android Development] bkrickles:
How's this running on digitalhigh's rom? Loved the mm version on du.

Also, since digitalhigh 7.0 comes with elemental kernel, can we still just flash this over that without doing anything else?

Thanks in advance.
[Nexus 6P Android Development] Sheetzie03:
If you would have taken the time( maybe less than 60 seconds even), you would have seen that Nathan just said a few posts back you can flash new versions over old versions.
[Nexus 6P Android Development] th3discodancer:
All good here. No problems with flashing over the previous iteration of the kernel, which was flashed over EX.
[Nexus 6P Android Development] Ofthecats:
The new fingerprint commit seems to help a lot, especially with conservatively designed governor profiles.
[Nexus 6P Android Development] Lucius1972:
V1.6 running great so far with FairPark script Nate.

Thx for the hard work buddy.

Using Velis Auto Brightness app, sioplus I/O, read ahead 128.
[Nexus 6P Android Development] desireaftergod:
What is the Fairpark script?
[Nexus 6P Android Development] DJMartini:
http://xdaforums.com/showpost.php?p=68454227&postcount=4624
[Nexus 6P Android Development] desireaftergod:
Thanks:)
[Nexus 6P Android Development] Lucius1972:
Just got ninja'd by DJMartini but that's the link indeed, it's for the 5x but it runs fine on the 6p.
[Nexus 6P Android Development] drharder:
You using Standard or HE script for FairPark?
[Nexus 6P Android Development] masri1987:
[MENTION=6842057]nathanchance[/MENTION] i hadn't realized you were still updating M builds.. thank you very much.. not quite ready to make the move to N lol
[Nexus 6P Android Development] gborgert:
Read ahead 128 is better then 1024?
[Nexus 6P Android Development] hroo772:
[MENTION=6842057]nathanchance[/MENTION] I had the most odd experience when trying to flash ninja 1.6 over a working setup of 1.5 (which includes supersu and xposed). After the install, my phone boot looped on the 4 spinning circles animation and never made it to the starting apps dialog. I then tried wiping system/cache and installing pretty fresh with 1.6, still bootlooped (with xposed). I then tried wiping again and flashing 1.5 with xposed, still bootlooped when getting to "starting apps". Only after I removed xposed was I able to get a flash of PN with no custom kernel.

I'm not sure what changed in the 1.6 install script which would cause issues with xposed as this combo was working fine in 1.5. I don't have any good logs since I wasn't near a pc with the right usb cable.
[Nexus 6P Android Development] kantjer:
Some (I'm one of them) believe that on phones with fast device storage, like the 6P, having a larger read ahead is only a waste of CPU cycles (= battery power) and memory.

For years now I always set read ahead to a minimum and never experienced any negative effects.

I fail to see the benefit of constantly reading data from one fast flash memory and write it to an other equally fast flash memory, but thats just my opinion.

Read ahead cache is/was interesting on phones with an external SD card, those are slow in comparison to the phones internal storage.

The fact external storage is relatively slow is also one of the reasons many phone manufacturers stopped offering that option, users tend to by large, cheap and slow micro SD cards and then complain about performance.
[Nexus 6P Android Development] Lucius1972:
Standard

---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------

128 should be good enough for internal storage (like our 6p) but if you use external storage values like 512 or 1024 should be good. See kantjers explanation in more detail
[Nexus 6P Android Development] nathanchance:
There was nothing that changed that would cause a problem like that. The kernel doesn't modify the system partition, only the boot partition. You just flashed 1.6 and rebooted right?
[Nexus 6P Android Development] kantjer:
Now with FP boost implemented in the kernel I switched off input boost. No lag issues yet.

It should improve battery use.

Screen on with FP unlock definitely improved.
[Nexus 6P Android Development] hroo772:
Yep, cleared exxm settings, rebooted into recovery and flashed ninja 1.6 then booted. No other changes happened and the issues showed on the first boot. I hadn't seen anything like this with my previous updates since I've stayed current on each ak then ninja build.
[Nexus 6P Android Development] nathanchance:
Hmmmm interesting. I am just guessing it is a one time thing since 1. I changed nothing about the installer and 2. I dirty flashed probably five times during testing.
[Nexus 6P Android Development] yung40oz84:
Yep the latest weekly from DU
[Nexus 6P Android Development] masri1987:
so on 1.6 Ninja Kernel, we can turn off input boost and input boost milliseconds?
[Nexus 6P Android Development] kantjer:
Give it a try, so far its working fine for me.

Sent from my Nexus 6P
[Nexus 6P Android Development] SixFourSix:
My fingerprint is usable again. Back to a healthy 0,5 sec from the former 2 to 3 secs.

Good job and thanks!
[Nexus 6P Android Development] hroo772:
I just flashed 1.6 without issues but with no xposed installed. I know xposed causes huge headaches for devs so I'll run without it for now. At least, I can say that you are right that nothing changed in the installer that could have caused this.

I wouldn't have the slightest idea what xposed is doing that caused this odd issue. Thanks for the responses.
[Nexus 6P Android Development] kantjer:
Lol, xposed doesn't cause headaches for devs, they just ignore all xposed related posts. It's the users that suffer the headaches [emoji6]

Sent from my Nexus 6P
[Nexus 6P Android Development] aostrom:
Inntsy teensy bug in 1.6...

Nathan my good fellow... I am hard put to report such a minor issue, but... I just installed Ninja V1.6. Twice. Unfortunately, when you look in "About Phone", or I actually first found it in EXKM, the kernel is reporting the version as v1.4. About Phone is actually reporting it as 3.1.102-NINJA-V1.4 with a build date of August 18. SInce the Zip says it's 1.6, I assume I have right bits and you just overlooked updating the strings.
[Nexus 6P Android Development] kantjer:
Weird, I build from the same unmodified source

Sent from my Nexus 6P
[Nexus 6P Android Development] aostrom:
Ok, just to be sure I downloaded it over again and reinstalled. I put it in a directory by itself do I couldn't accidentally install v1.4... Same result.
[Nexus 6P Android Development] Mikulec:
How do you flash the zip? I experienced few times that Flashfire didnt actualy flash the zip I wanted.
[Nexus 6P Android Development] nathanchance:
That just doesn't make sense, if the zip is named 1.6, it should show as 1.6 in the settings as my script takes the name from the Makefile directly.

https://github.com/nathanchance/Ninja-Kernel/commit/592ba9e8d4054b4ecfd2921b29df4feb18bae595

https://github.com/nathanchance/scripts/blob/master/Kernels/ninja.sh#L291

How are you flashing the zip?
[Nexus 6P Android Development] meleelord:
[MENTION=6842057]nathanchance[/MENTION] do you use chill along with glassfish?
[Nexus 6P Android Development] nathanchance:
No, that profile is for interactive.
[Nexus 6P Android Development] blitzkriegger:
The kernel version mismatch likely has something to do with flashing supersu last. I got a similar error yesterday when i dirty flashed the latest nougat version then flashed supersu. Instead of having Ninja 3.2 I still had 3.1. To resolve this just flash clean by doing the following:

1.) Access TWRP and flash the decrypted boot.img provided for nougat. If on MM flash the related boot.img.

2.) Flash SuperSu

3.) Lastly flash the kernel. Upon rebooting the correct kernel and version should be displayed.
[Nexus 6P Android Development] Vangelis13:
No sharing anymore, no..? ;)
[Nexus 6P Android Development] aostrom:
Yes, I am flashing Ninja, suhide, supersu. When I flashed just the kernel I had root problems. What is the proper order? I thought Nathan says it's ok to dirty flash ninja across versions?
[Nexus 6P Android Development] blitzkriegger:
Like I said this is just how i do it if i want things clean. Dirty flashing is a ok long as you are updating from previous versions. You just have to flash supersu first then the kernel last.
[Nexus 6P Android Development] nathanchance:
If you are just upgrading Ninja, don't flash SuperSU. It's not necessary as I don't remove any of its ramdisk edits.
[Nexus 6P Android Development] booogermonkey:
I had something similar. No super su after boot. Downloaded from play store and updated binary without flashing anything.
[Nexus 6P Android Development] aostrom:
That's what I tried the first time -- I just flashed 1.6. That's when my root issues appeared. So -- I re-flashed SuperSU (I didn't think to uninstall and reinstall it from the Play Store), and ended up with v1.4.

I assume I'm solving my problem now -- here's what I'm doing (it's not a big deal, and if this is the right way to upgrade, that's OK):

dirty flash PureNexus

flash ARISE Audio

flash Ninja v1.6

flash suhide

flash SuperSU

wipe cache

boot

Phone is "optimizing apps" now (120 of 189) - I will report back.

-------------------------

Update: That did exactly what I thought - refreshed the ramdisk and everything else that might have got out of sync and now all is well. Thanks to all who suggested fixes and to Nathan for his work bringing this to us in the first place!
[Nexus 6P Android Development] justin1221:
I flashed supersu first then kernel and it flashes just fine.
[Nexus 6P Android Development] sharp87:
After flashing v1.6 , the back scanner reads fingerprint quick and seems noticeable improvement for 6p

Sent from my G➿gle Ne❌us 6P
[Nexus 6P Android Development] kantjer:
No, now [MENTION=6842057]nathanchance[/MENTION] is building the m kernel again.

I use his source, so my build is exactly the same.
[Nexus 6P Android Development] Vangelis13:
Ah, ok. Makes sense. Thanks once again for the inbetweenies! :good:;)
[Nexus 6P Android Development] joeyfong:
Just want to ask, which profiles is suitable input boost disabled? I found GlassFish is very slow when it is disabled. Thanks
[Nexus 6P Android Development] kantjer:
It depends on you're usage, I'm using DeusEX with input boost disabled

Sent from my Nexus 6P
[Nexus 6P Android Development] joeyfong:
My main usage is whatsapp, telegram, fb, no gaming
[Nexus 6P Android Development] xperator:
If you disable InputBoost expect lags, high temperatures, issues during gaming, micro stutters and so on.

Use profiles that are meant to work without it. I'm currently working on a new one
[Nexus 6P Android Development] joeyfong:
Wait for ur new one :fingers-crossed:
[Nexus 6P Android Development] nathanchance:
On the whole input boost thing, it really does not drain that much battery if you keep it at something low like 600 or 768 MHz for 40-60ms. The phone will stay smooth and battery savings is solid. I have tested no input boost versus input boost with both a profile (Bluejay versus stock) and no profile and it does not make a noticeable difference for me. Heck, I am on GlassFish right now that has little boosted to 600 MHz for 1920ms (yes, almost two seconds) and I can easily hit 5-5.5 hours through my normal usage.

Not saying removing input boost will not save battery but there are more impactful ways to save battery like controlling Android processes as the kernel cannot control those and those tend to use more resources that people think.
[Nexus 6P Android Development] xperator:
Yeah it's not something you should get rid of. It benefits the performance in many ways and could actually affect the battery life positively.

When there is an input the OS gives CPU a heads up to start warming up cause the user is probably is onto something. So it's a good thing.

The only reason you would want to disable it is when you are a heavy texter and your profile/kernel has set InputBoost to very high values. So constant typing/touching cause CPU to stay on high freq for no reason.

And 600 is actually a nice value for it. It's a quick jump for CPU whenever an input is detected.
[Nexus 6P Android Development] HTC_Phone:
With that said, with a profile like Glassfish, what would you recommend for a user that does a lot of texting? I definitely agree that input boost is important and probably helps battery life more than hurting it, unless you do a lot of texting with a high ms count for input boost, like you said. Any recommendations or thoughts on profiles that are suited a little more to heavy texting users? I know that I wouldn't mind hearing other people's thoughts, so far Glassfish has been pretty good, and I'm a heavy user.
[Nexus 6P Android Development] kantjer:
You can try to reduce to boost time and see how that goes.

Sent from my Nexus 6P
[Nexus 6P Android Development] xperator:
That's what I'm trying to figure out with this new profile I'm experimenting with. It's very tricky to have InputBoost disabled while solving lag and heat issues.

The real challenge is to keep the CPU at very low clock rate (below 600) while texting and interacting with the phone. We don't want the CPU to go at/above 600Mhz while we are simply typing. Heavy texting users spend a lot of time typing why would the CPU go use and waste that much power.

As for Glassfish, it's really a simple profile. You know they say anything is better than stock settings so that's why you like it. And based on what I briefly explained above, Glassfish is not designed or intended for such use case.
[Nexus 6P Android Development] Rohit jat:
will vomer tweaks works with ninja ? or it is compulsory to use only elemental x ?
[Nexus 6P Android Development] nathanchance:
VomerTweaks is just a set of governor tunables or a profile if you will. I can't say if it is compatible with my kernel but there are several great governor profiles that work well with the kernel.
[Nexus 6P Android Development] Rohit jat:
thank u for clearing this out. How much time do you prefer to test any profile because when i try to apply new profile, there is another updates to them..:confused: in simple words how much time should i give ?
[Nexus 6P Android Development] nathanchance:
Generally, I test a profile for about three days or so before determining its worth. Some I can tell within a day, others may take five but on average, it is three. Keep in mind updates are not always better. If you find a profile that suits your usage, stick with it; it's not broken or anything lol.
[Nexus 6P Android Development] shadowstep:
FYI Post (and sorry for the OT!): TWRP has been been updated to 3.0.2-2! Click here to download. :)

Also, if anyone is using version 3.0.2-1 of TWRP, do note it has a

fatal bug

. Read about it here!
[Nexus 6P Android Development] nathanchance:
OT is always fine by me. Good heads up for sure. I've never had to restore my EFS partition luckily but I would not do it unless absolutely necessary.
[Nexus 6P Android Development] jollaman999:
Sorry for asking here.

But didn't you experienced battery drain after applied 3.10.103 patches?
[Nexus 6P Android Development] shadowstep:
Battery drain? Not one bit. I'm getting stellar performance and battery life using this kernel with the interactive governor tweaks. Ninja is definitely one of the best kernels out there.
[Nexus 6P Android Development] jollaman999:
I just want to know is it ok with 3.10.103. I'm testing with my N5X kernel.

But there was huge battery drain after applied 3.10.103 patches.

I saw Ninja's kernel source and it was definitely great. :good:
[Nexus 6P Android Development] mitchdickson:
Battery drain? Well, yes I have.

I have yet to find a kernel that does not allow my battery to drain.
[Nexus 6P Android Development] nathanchance:
Hmm interesting... I ran my phone into the ground while testing and didn't notice any major regression. Did you notice higher CPU usage or anything?

I think the context of his comment was pretty clear that he meant higher battery drain due to the upstream patches.
[Nexus 6P Android Development] nathanchance:
I have received a few requests to have some way to be notified of kernel updates outside of XDA so I have made a Telegram channel you can join here. If I decide to start doing beta builds, I will use the channel to announce these. They may or may not be unstable so please do not post about them in the thread; please PM me on XDA or Telegram to let me know of any issues instead.
[Nexus 6P Android Development] chachin:
who here on 7.0 and what rom other than stock you guys recommend O.o
[Nexus 6P Android Development] joeyfong:
I used ex kernel before, how to clear its setting? I found that some setting still there even I cleared the app setting, thanks.
[Nexus 6P Android Development] nathanchance:
Well I'd first try rebooting after clearing the app settings then if that does not work, you'll want to dirty flash your boot.img then flash Ninja.

[MENTION=4338352]chachin[/MENTION] I am just on stock, actually been enjoying it quite a bit.
[Nexus 6P Android Development] joeyfong:
msm is disabled and core is enabled by default?
[Nexus 6P Android Development] nathanchance:
Yes, I left that stock.
[Nexus 6P Android Development] BIGWORM:
So, are we supposed to flash rom boot.img then flash kernel and wipe cache upgrading Ninja? I see that's suggested, but I've only been flashing the kernel right on top, not flashing the boot or wiping anything...
[Nexus 6P Android Development] nathanchance:
No, just flash the kernel and reboot. That's all that is needed when upgrading.
[Nexus 6P Android Development] BIGWORM:
K cool. Just making sure.
[Nexus 6P Android Development] arcticnights:
What Nougat Roms are you guys using with Ninja? Looking to try something new :)
[Nexus 6P Android Development] shadowstep:
UPDATE: The fatal bug was fixed in v3.0.2-2, but a new different bug was found in it (details here). I'd recommend staying onto 3.0.2-0 until the new, fixed version of TWRP is out.
[Nexus 6P Android Development] SlyUK:
Which one(s) have you tried already ?

I'm hoping Calatclysm makes a comeback :)

EDIT:

That should be Cataclysm, apologies :)
[Nexus 6P Android Development] arcticnights:
I’m only aware of pure nexus mod and stock! :) Anything to recommend?
[Nexus 6P Android Development] nathanchance:
Stock, it's really the most stable at this point. Blobs/binaries haven't been released from Google yet so ROMs haven't really taken off. DigitalHigh's ROM may be worth trying but I haven't really explored it.

Also, I will be adding links shortly to the OP for the most popular governor profiles so they are easy for people to find and experiment with.
[Nexus 6P Android Development] arcticnights:
Where can I find the stock N image? What gapps do i flash with it? Many thanks. :)
[Nexus 6P Android Development] ariefabuzaky:
Page 60,, give thanks who posted it

No gapps,stock rom already include gapss
[Nexus 6P Android Development] nathanchance:
Give this thread a brief read. This is how I upgraded:

Upgrade TWRP to 3.0.2-2 (beware, there are some backup issues right now but flashing is fine).

Download the OTA zip from that thread.

Wipe system, data, cache, and dalvik cache in TWRP.

Flash the OTA zip.

Flash Ninja then SuperSU if you want either.

Reboot.

That's the boot.img, not the full ROM.
[Nexus 6P Android Development] ariefabuzaky:
Opps .. i think he wants N stock kernel .. sorry my bad