yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
updated v3.8.1 build; https://github.com/nine7nine/Apps/raw/master/exns_eas_v3.8.1p_bca050b.zip

Changes:

- Merged in "Adaptive Battery" support

- disabled RT_RUNTIME_GREED feature (likely a source of drain)

- Explicitly hard-coded some defaults that used to be handled by my init rc script. (so these settings are now applied/enabled without needing script on boot).

- Important fix for touchscreen driver

- fix for Boostbox

- tackled a couple of suspend/pm issues

- Updated Coccinelle and used it to analyze / improve some of the code base.

On this release, you still must execute ~/boostbox script (root folder) ~ I'll get this sorted on next update, but at least now I've reduced what my init rc script does (now it only creates cpusets, nothing more)... So that's one step closer to my goal... I'm hoping later today / tonight I can have a stab at getting the need to execute boostbox manually resolved.

I'd encourage anyone using v3.8.1 to upgrade, as a few of the fixes are important. Also, I didn't bump the version, it's still v3.8.1 ~ I won't bump the version until I've resolved the need to execute boostbox script manually.

anyway, I have to head off to work ~ but hopefully, I can tackle the next bunch of todo's on my list later.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kkjb:
Installed update and installed fine, found troubles on terminal for boostbox, write errors on files just like previous user. Verified root, terminal root (permissions were off in Magisk) so write errors where on not having file dir's. Flash again (-w) removed. In bed stand mode went from stock 100-96% to 100% to 64% same app loads. So something is odd. Went back to stock to verify my bed stand mode for tonight. Sorry I couldn't be more specific on troubleshooting data but for next time let me know what you need from my device to help// but maybe it's me :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
i have zero time today to deal with anything, but thanks for letting me know... not sure what the deal is with your drain, but i haven't had that issue at all...

boostbox script doesn't matter; I'm killing it and getting the kernel handle that, do i don't care about the script anymore (started on code to handle it lastnight)...

anyway, I'll be working basically until i go to bed tonight, maybe an hour off to eat n shower.

and just an FYI at everyone; magisk appears to be a bit screwy on Pie. safetynet check is invalid && i was using a fresh stock system + boot.img - uninstalled magisk, from in the app; crashed my device... also, looking through those bug reports, other things seem to be screwy... not sure what's up there.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] laofan:
Thanks for the heads up on Magisk. My device is on Pie and is also showing invalid for safetynet check. But Google pay works... I was very closed to uninstall Magisk. Now that you mentioned it, I would just leave it alone.

Thanks for the hard work .
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nil253259:
Use SafetyNet Helper Sample
[Google Pixel ROMs, Kernels, Recoveries, & Other De] HyaenidaeNET:
Hi, I have tried to install your kernel recently, but I don't know what I did wrong. I got some issues with lock screen, smartphone started to reboot sometimes. Can describe how to flash your kernel? Because, I booted twrp in RAM, flashed magisk, reboot, booted twrp again and flash your kernel, after that I ran boostbox in terminal, got some errors and tried to run from root explorer. That's all. Can you describe what I did wrong, if it's no problem to you. Thanks for your work.

Android 9.0
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Okay, So I have (unfortunate) news;

After some careful thought and consideration, I've decided that (at least for now);

I will no longer be providing builds, and most likely not participating in this community anymore. I will be still developing my kernel, but essentially only for myself and a few close / local friends (it's likely that binaries/builds will still appear on my github, but that's about it. absolutely no support from me, going forward).... There are a number of reasons for this and I will try to outline them a bit (in no particular order), so you may understand;

- On average, I'm receiving a crazy amount of PMs on XDA every week (like clockwork). Most of these are from people wanting me to solve their own problems (often other devices, kernels, etc that I know very little about / don't have the time to look into), resolving conflicts (that I know nothing about), compiler issues (that aren't my problem), they want/expect help with tools that I'm not the author of, etc ~ when I explain to them that they need to contact the correct the author, RTM and/or in situations relating to kernels ~ that I'm not really in any position to help them ~ in return; 9/10 people are just absolute jerks about it.... This isn't sustainable, it's extremely frustrating && demotivating (as I do try to help when I can) and it's getting to the point where I pretty much hate XDA.

- Being as I've had a number of bad interactions with people on XDA, which has caused me enough stress/aggravation, I seriously question if XDA is really a community that I want to part of (at this point, I pretty much don't think that it is.).

- i've also become extremely busy at work, as of late and will continue to be for a while anyway.... this is a bit of a problem right now (if I'm to be supporting builds)... and actual paid work takes priority over this, no question...

- I have little to no motivation to provide monthly builds, support users, debugging their issues (especially, the issues that I can't reproduce) and at this point, putting in endless hours of my time (that I don't have) on this kind of thing makes very little sense... It may have been different, if I had been able to generate some income somehow to justify my time invested, possibly had more free time, etc... But this kind of thing has never worked out / it's come to a point where it just really isn't worth the hassle anymore. (and hasn't been for a long time).

- given all of the above, i'm unhappy - and I need to fix that.

So all things considered (+ some other factors not mentioned), I'm taking a break from all of this.

Sorry to drop this on you guys, but it is what it is... I may pick back up on public builds/support in a month or two ~ but I also might not, idk yet...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kkjb:
Thank You for all the help in creating a new Kernel, (from what little I understand) a structure that is different than most so I can see why the back channel stuff is happening. Most would just stop, but the fact you told us your reasons speaks volumes on your investment and frustrations. Thanks again. I will remember if I see you some point in the future, your comments in my mind will always hold more weight :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
It's very sad to see you go, and I hope you decide to come back, but we understand. Being happy takes full priority over (almost) anything! :D
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Bryanx86:
Sorry to see you go, but I understand your frustrations. Thank you for all of your hard work on this kernel and for sharing it with us.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
I understand you fully, thank you very much for your hard work. I hope you post on GitHub as your kernel is the best.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
It is always sad to see a good dev go away. It just reduces the community and its power but, I completely understand the people who never seem satisfied, hardly ever say thank you, and always expect (sometimes demand) your attention. I have never used your work but, can only hope you find your way back to XDA and ignore the people you will never satisfy and understand there are more out there who appreciate your work!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] matt99017d:
Well [MENTION=7810360]nine7nine[/MENTION] I hate to see you go....feel free to pm me so I can be a close person to enjoy your hard work! I hope to see you come back man! It's super unfortunate that people are complete ass tards.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
you're probably right about the back channel stuff. I do a lot of porting, out-of-tree stuff, etc ... I think many of the people who bug me with things that I can't do anything about (on another kernel, device, etc) don't seem to understand how much time I've invested and just how dissimilar my kernel is to other msm8996 kernels.

Example; I mean without even understanding the specifics, you can just look at a quick diff (that I just made) between Marlin's (vanilla) and my kernel's scheduler code; https://pastebin.com/PBdyywSC (the +/green is my kernel) .... They aren't just 'slightly' different, that code is almost entirely been replaced....

Well, shag, you do have my email (and while I may not be participating much on XDA ~I'm still around / doing my thing).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
thanks for your understanding && no probz.

I will be, for sure, no worries. (I'm still working on it and will be posting builds on github.).

Thanks, man. yeah, I get that and tend to agree... But I don't expect that I will be permanantly gone, just for now ~ I have too much on the go, there have been too many situations/people that rub me the wrong way, etc... So i need a break from the XDA side of things (I'll still be hacking on my kernel and I'm sure that there will still be people using it)...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sweetbabyj45:
Hey there, first wanted to say thanks for all your work. A great kernel for sure. Over the years (since the OG Droid) I've seen many, like you, understandably become frustrated with the community and overwhelmed with the time spent... Your work will be missed, for sure.

You (obviously) don't owe me anything, however, are there any kernels or developers that you've watched/know that you might recommend for a kernel for sailfish? If not, no worries, just thought I'd ask because I'm always looking for quality such as yours. Best, SBJ
[Google Pixel ROMs, Kernels, Recoveries, & Other De] almightysiman:
Been using your kernel since day one,sorry to see you leave,really appreciate your work.At least you still drop some builds on github,so I will keep checking and hope to see you here someday.Thanks nine!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
I would suggest either EX kernel ~ Obviously EX kernel is a decent choice because flar2 pulls in a lot of nice extras, while keeping it somewhat stock.... I have a lot of respect for Flar2 and at one point, i was using his kernel (the original exns kernel was based on it, but later when i started from scratch, i just pulled in Flar2's patchwork).

or;

Although I've never used it; Flash kernel seems to be quite good. Nathan does excellent work (I have an enormous amount of respect for him) and last i peaked at is github; he seems to have done a great job with picking out good features, etc for Marlin. ~ I can't say much about Clang-compiled kernels, as I tend to prefer GCC or Intel's Compiler for kernels; as both tend to have offered better performance than Clang/llvm binaries... It's possible that's changed, idk - but i doubt it...

Either of those would be good choices, i would tend to think.

Yes, I will and I will notify both of my threads when I do. Sounds good?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Hey man, your work is extremely appreciated.

I've always appreciated how patient and willing you were to fill us in on all of the nitty gritty technical info.

Thank you so much for your time and effort. If you ever decide to come back, I'm there day 1.

You the man nine, hope you can one day come back to us plebs. Good luck buddy!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nathanchance:
I appreciate the kind words, I've always followed your work on this device and I respect it a lot as well. Take some time to yourself and relax, this is supposed to be a fun hobby, not a stress inducing time sink. I've absolutely been there myself, just have to tune out all the noise for a while and rediscover your passion for this scene. Cheers man, hope you come back at some point but if not, I'll keep an eye on GitHub :highfive:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
hey Nathan, thanks! that means a lot.

my words are just ''calling it as i see it'', honestly. many of your contributions have been beneficial to a rather large audience, myself included.. it's very admirable && appreciated..

yeah, i think you've hit the nail on the head && that's what i plan to do.. take a step back, get inspired and have fun with it again.. yup, I'm sure i will see u around (and probably check around your github too).?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Arju:
I just wanted to chime in and say that following your GitHub has been a blast and I will continue to do so. Thank you very much nine7nine for all of your contribution to the android community. Your health, real life and happiness is more important than this, I agree with what has been said by you and what you plan to do henceforth. I'm glad stuff happening here haven't taken you off development and that you will continue on your own terms. Your GitHub is truly a valuable resource for learning for many. Take it easy and take care! :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ztotherad:
man, i have to see you go and hope you do come back! i haven't had the privilege of running your kernel yet, but hope to very soon! I've followed your kernel and the work you've put into it and hope you keep updating your github source so maybe we can build it and run it for personal use. hope you're doing well in your endeavors and hope to see you come back!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Thanks guys, appreciated for sure!

[MENTION=1339445]Arju[/MENTION], yeah, i do see a lot of traffic around my github, but I almost never know who's dropping by (unless they do a search and it's obvious)... Yeah, with some pressure off, i will be more prolific. ~ i kind of already am, just look at commits from yesterday, this morning and this afternoon....

....I've finally been able to write, on a handful of commits ~ "sync to 4.9" ~ as in, synchronize this code to linux/android-4.9. In the case of the locking code, with just a couple of minor exceptions + lockdep, I;m pretty much done working on the core kernel locking... the scheduler isn't far behind, either. (it's also means that I should be able to pull 4.9-LTS sched/locking related commits with ease, while ignoring 3.18/4.4-LTS. ie: reduce time spent making sure I catch LTS bug fixes).

So given the above; I would say to both of you; my kernel development will remain busy, I just need a break from XDA, direct support, etc ~ but [MENTION=4221111]ztotherad[/MENTION] => builds will show up and I will announce that, when it happens...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Just letting you guys know;

I officially will never be providing builds ever again.

Moderators please delete this thread
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ztotherad:
hate to see you go, but alas good luck on your journey of life and hope to see you again!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
so I've been in touch with the mods, my account is being deleted... just letting you all know....

take care.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
Whyyy :crying:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] armando_rod:
Xda drama, best nerd drama in the internet
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Damn, who in the hell scares away a guy like nine? In my experience, nine has been one of the most detailed, helpful, and patient devs I've ever had the pleasure of dealing with here on XDA.

Why do people have to scare him away :(

He's the only kernel dev I've ever used on sailfish and am extremely sad to see him go.

Nine, if you see this, know that you're the man and don't deserve any of this bs.

I'll miss you and your kernel deeply, if there's any way we can keep up independently of XDA please allow us to do so
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BarackMitzvah:
Has anybody heard from him at all? Still haven't switched and was wondering if anyone had heard anything/seen any new builds.

If not, anyone tried Kirisakura Harmony? Seems like it'd be the closest thing to this kernel, minus the no-install requirement for TWRP.

Nine, if you see this, know that we miss ya.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Horgar:
Very sad to see this. I used the very early builds of this kernel and they were great. Nine7nine being an exceptionally helpful and attentive dev. The only reason I stopped was because my private life got in the way and couldn't keep up my end of the bargain in flashing his builds and giving feedback. But if you're reading Thanks Nine7nine. Very very sad to see you go. And for the reasons you give. Some people are just jerks.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] AddictedToB3er:
Flashed and it's working great! Thanks for sharing your work.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Cool thx. Glad it's working for you!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
ok, Soooo.....

I've managed to change some stuff around in my kernel... it's config now is a bit closer to the Pixel 2 . OP5-EAS. This is good because in some contexts, I am downstream from them.... Part of the EAS, Schedutil, sched (and some fore linux code) I've ported back from their 4.4 kernels. That's also where I grabbed CPU boost / Dynamic Stune Boost from....

I'm currently, testing my RCU config changes WITH Input Boost enabled.... I kind of woke up and realized that my testing of input boost was too narrow of a scope, reason; Because the problem that I see in Beatonal (audio skipping with it enabled) could in fact be a problem with the app.... So now What I am doing is testing a bunch of similar proaudio apps (and I'l probably test a bunch of 3d games OR ask for some help with that (?).... ~ You know the types of apps that are heavy duty...

So far, things are looking good. I will probably enable Input Boosting, as I think it should be good for us (minus, my corner case - but for that I can just switch to performance governor which is better for realtime audio type applications anyway)....

Mext next step after a few more hours of testing, is to make available a test build.... I would like some people to try it out, specifically, gamers and people who use heavy proaudio; synths, sequencers, looopers, samplers., etc...

The good news is that if it pans out and I enable input boost - you should see a noticeable improvement to responsiveness.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
Count me in, HD audio and 3d games
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Cool. Thanks!

I'll post a test build in a while, I just have a bit of my own testing to go thru first, as I might set some defaults of input boosting in my init rc and adjust a couple of other bits...

So far though; it DOES appear to be a problem with Beatonal... I've tested Caustic, DRC, a few of the IK Multimedia apps/plugins and a handful of other synths - beatonal craps out still - but the rest do NOT... In fact, I was only able to produce an underrun or two while playing Mozart in iGrand Piano / IK Multimedia (but it's always done that soo...)....

but yes, it would be nice for me to avoid installing a ton of games - so that's awesome, if you-ll help out.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] siheals:
Yes, helping is no problem. I am on telegram if that helps.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Hey! Thanks, but I'm going to hold off on enabling Input boost. It has a bug, but I think I've figured out the issue(and it likely exists in the stock kernel too, although I'll wait to verify that next firmware update for november. - flash the stock boot image + magisk and see if i can reproduce it).... **I found another app that very much dislikes the input boosting, except it actually throws some useful information in logcat about it.... (even without input boost there is a warning in logcat - betcha it happens on stock too.

So I'm going to wait / for now just work on merging in fixes that I have queued up, then come back to the input boost in a few days....

I also have to strike the iron while it's hot; I have a project that I've been dying to dig my hands into (for android). I've been waiting for a month or so => and tonight the researcher / developer whose work I'm interested in implementing has made some progress - so I've been working on that for the last few hours....

shouldn't slow me down on the next update, but I'm not in a hurry to get input boost fixed. It can wait a few days, it's disabled in my builds in init.exnoshadez.rc on boot anyway. (and I mention it in the OP).

on the plus side though; the next release will be nice - it's coming along / will have some improvements
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Merged in the Latest EAS updates from Android-4.9-eas-dev branch into my branch...

It was rather painless, now that I'm mostly caught up with all of the plumbing needed. There were 14 commits, most applied cleanly - others I had to intervene / manually fix before signing off on them / committing... Then there was a handful that I rolled together -> they wouldn't apply at all, due to function names changing in the last couple of years (linux-3.18 is old!) and also just due to other differences in code placement.... Sooo... I went through manually and got them all in there ;)

So While I may not have ironed out Input Boosting.... I have done a nice round of bug fixes (with more in queue) and pulled in EAS code (and sched/core code in general).... It should make the next release a good one....

EDIT: Traversing through aosp/kernel_common/android-4.9-eas i'm thinking that I am actually caught up! BOOM! I went back through, found some older commits that I thought I might have missed - but I have them. YAY! :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
The temp polling rate is something I increased and I never knew there was a patch from CAF for that? :rolleyes:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
yup. It's been around for a long while...

I'm just going to throw this out there Nick, but I would be careful about picking from my github eh. In fact, if I were you I wouldn't.

Reason - I break things, test patches and revert / do forced updates (that may do away with patches that I was testing)... For example; right now I'm in the process of backporting a number of patches from wahoo (pixel 2 kernel) and there are a number of patches that I may not end up keeping...

So my kernel's github (beyond my stable builds), is pretty touchy... aka: It's not setup for other people to build from or cherry-pick from... I will likely clean up a branch for that at some point, but for now - it would slow down my own testing and progress.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] derekr44:
Nicely done. Definitely giving this a try for awhile and very interested in your edits.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
I'm not picking for about a day or two, cleaning up stuff, working on my computers, school.. :crying:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
That's cool, The current available zip / build doesn't have the latest pulls that I mention in what you quoted. I'm just trying to iron out a few things before I post a test build or stable build...

but the current build sems to be working ok for everyone, afaict. (there are some bugs that I've fixed, that I can easily reproduce, but it doesn't appear that anyone else has hit them... so should be good until I get my latest set of changes ironed out).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] derekr44:
No worries. My flashy-fingers have worn out as of late. I'll be lurking.