yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Welp, I'm definitely glad to hear that performance on stock was satisfactory despite the WiFi issue. The other aspect that's had me hesitant to support stock is the EAS factor as

I'm unsure about the feasibility/viability of an EAS kernel for a ROM that doesn't natively support it. That being said EAS-Project seems to be having great success with their OnePlus kernels and OOS doesn't support EAS either. So, it doesn't seem like it should be an impossibility. Plan B would be an HMP variant for stock, I just don't really have a great deal of interest in working with HMP so that's a pretty 'meh' option for me.

This is all to say, you might just get your wish in the nearish future. I'm taking some time now to revamp my build environment and format, build my own toolchains, and ideally move to AnyKernel. The next releases will more than likely still be for Lineage/custom ROMs, but I do want to move back to stock sooner than later now that Pie has been released officially. Realistically, it's probably going to take some time for me to get to the point where I'm ready to make that jump, so no one needs to be panicking about Lineage support being dropped (yet), but I will be continuing to take steps towards making that transition as smooth as possible should I decide to go that route.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JoshuaUB78:
Cool Beans man. Take your time.

Haha! I have to look up what EAS is. Any way your work is wonderful. I really just need to flash Lineage OS.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
EAS stands for Energy Aware Scheduling,

This is a great article to peruse if you're looking to understand how EAS works, it's advantages, and how it differs from classical HMP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
So this isnt entirely related to this particular kernel but i want to ask this since the thread regarding this phone being able to boot the Pixel 2 system img hasnt been fruitful as of late. as far as i can tell based on what people have commented in that thread the only real issues with the system img is no wifi or mobile data. and doing some reading from posts in this thread led to to believe that a custom kernel of some sorts could solve these issues? Im by no means an expert on these things and i would love to have some insight on to whether or not having a custom kernel would make WLAN and mobile data work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I'm not sure that the solution to that problem would be so simple. For what little I know about Treble, you'd need a kernel which specifically supports it which I don't believe any of the custom kernels available for this device currently do as there aren't any GSI-based Treble ROMs floating around that would require one. It's feasible that you might be able to correct the WLAN issue with an appropriate kernel (although I can't say that with any certainty), but the lack of mobile data is another beast entirely likely tied to modems and firmware and beyond the scope of a custom kernel. That being said, I have approximately zero experience working with treble so everything I just said is pure speculation.

My two cents on the matter goes something like this: I'm not sure I understand why you would need/want to run a Pixel system image on this device seeing as the stock ROM is incredibly similar to the Pie builds the Pixels are receiving. I mean, the PH-1 is one of, if not the only, other device to have received Android 9 updates and not only that, but they're being pushed moments after Google pushes theirs so how different are they really?

Turns out, I'm stupid. EXKM supports flashing AnyKernel zips of literally any kernel without the need for TWRP. I never noticed this because up until this point I've never used AK. So, problem solved, I no longer have any reservations about switching formats. I'll likely do at least one more release for Lineage to test out the new backend before I move to working on stock, unless some unofficial LOS 16 builds start popping up for this device. Doesn't mean that Lineage support will be dropped indefinitely, but it may wind up on the back burner until they catch up with Pie. Unfortunately, I barely have time to do what I'm doing right now and I can't afford to allocate time and effort to support a ROM that I'm not personally using. At least not right now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
Thanks for the input. I just find this particularly interesting not because it can boot the system img but the fact that in theory it will be able to continue to do so all the way to android R. As you said its likely a custom kernel would not actually help. more to do with drivers probably. but i feel like this is something to continue to keep an eye on more for the future when essential stops giving updates.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
So, with a bit of effort and some testing with a friend of mine who's currently running stock I'm pleased to say that I now know how to facilitate working WiFi on both lineage and stock simultaneously. Looks like I may be able to support both after all.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
Great to hear. I've always wanted to taste an EAS kernel but wanted to stick with stock. Glad you could find a way to make it work :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
Does your kernel help at all in reducing the jitter on this phone? That would be fantastic for those of us on stock.

I'm convinced it's a real issue, probably hardware related, so I'm not expecting it to be eliminated. I'd be happy with an improvement.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NikoZBK:
Excellent news!
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Oh, wow. How will I decide between this and EX when you build a stock compatible kernel?!?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Yeah, it remains to be seen how well an EAS kernel will behave on stock ROM, but I'm going to go for it. If it can be done for OnePlus devices on OoS with positive results than I don't see why I wouldn't be able to pull it off with this device on stock.

I mean, I can't exactly make any promises before I have an actual product on hand but I want to say there should be a good likely hood of touch improvements. I've got a handful of commits relative to touch response from my Lineage builds which will eventually make their way over and since LOS uses the same touch sensitivity and response controls from stock there's a good chance for a net positive result.

Tomorrow I will start tearing down and rebuilding once more, if I've set myself up as well as I think I have then it shouldn't be too painful of a process. Test builds will likely come first given the significant change in format and experimental nature of what I'm trying to accomplish.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JoshuaUB78:
SCORE!

Seriously looking forward to how this comes out. Thank you!
[Essential Phone ROMs, Kernels, Recoveries, & Other] ranasrule:
what version is the latest one for LineageOS 15.1 ? Oreo 8.1 ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Oh, yeah. Sorry, I archived the original (LOS) release repository and didn't consider that doing so would break my existing download links. You can now find the current as well as all previous releases here.

I'll have to update the links in OP ASAP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MrPhilo:
Do you need any beta tester for your Stock EAS kernel? I don't mind testing, got my Essential yesterday currently using Elementalx. Would love to go back to an EAS kernel, just miss the smoothness compared to the stock settings.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I'll get back to you on that when there's a kernel to be tested. I just started rewriting my source the other day and it's going to take some time before I get to a point where I'm comfortable shipping it. Likely a few days at a minimum, depending on how much time I have to work on it. I've got the day off tomorrow so I'm hoping to knock out a good chunk of the bringup so, we'll see how it goes.

What I'll likely do is upload test builds once I've established a baseline, as opposed to prolonging the wait until I have the new kernel 100% back to where I was at with the Lineage variant. First ones will be sparse as far as bells and whistles go and I'll continue working back to the point my previous source was at during the testing phase.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Double post?
[Essential Phone ROMs, Kernels, Recoveries, & Other] governmentissuejoe:
Will this be for stock Oreo, pie, both?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
The only thing I can say with certainty is that it will support stock Pie and current LOS Oreo builds. I doubt it will work on stock Oreo because it simply does not know how to handle inline WLAN stacks whatsoever. The only reason I can achieve cross-compatibility between stock Pie and Lineage 15.1 is because the Pie WiFi HAL is a smart boi that knows how to handle WLAN drivers regardless of whether they're built as modules or built into the kernel. In short, it will support the current iterations of both stock and LOS.

CAF just pushed their first Pie tag/branch, so I'm back to square one again rebasing on that. Stuff like this always happens when I'm trying to do a rewrite.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
So, I pretty much spent all day getting back to the point I was at yesterday but such is life. On a positive note I've rebased OEM source on kernel.lnx.4.4.r34-rel (our new CAF branch for 9.0), and upstreamed to 4.4.152. It was a slog considering there was no android-linux-stable repo to work off of this time, but it was good exercise to go through the process myself and I'm extremely pleased with how clean the result turned out to be. Really looking forward to seeing how this progresses, apologies in advance for the delay that ensues, but I promise I'm working as quick as I possibly can (just ask the last 8 hours of my life). If you're at all interested, you can follow the progress here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MrPhilo:
There seems to be no option to disable the wakelocks on the EX Kernel App? Has it been removed from the recent kernel?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
It has not, EXKM -> Miscellaneous -> Block Wakelocks (See attachments).

I intend to have an initial release for the new source up by the end of the week. Here's hoping I can meet that target.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MrPhilo:
When I click into it there's no wakelock to block, it's just blank ... I do however see them in MTweak.

On my OP6 it is working fine the Wakelock so I don't think it's the app problem.

EDIT: Also the performance is so much better than Stock Essential and LOS Kernel! Great job :)

EDIT 2: Also vibration seems to stick to 77%, when I change it to 100%, it goes back to 77%, this also seemed to be an issue on EX Kernel, but he has patched it later. Idk if you can also do this if possible in a later time as I know your busy atm building a new one for the device :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertbarber:
Will you be adding Adreno Idler back in? Can't wait to try out the initial release of your stock Kernel when it's ready. Thanks again for all your hard work you're putting into this. If I may ask once Official Pie ROMs start coming out will you support them as well?
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Adreno idler is useless for modern Adreno GPUs. Stock governor is good at keeping frequency low when gpu is unused.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
You're right, it was a bit foolish of me to send you those screenshots without actually tapping block wakelocks to see what happened. I guess I was assuming you were having a hard time finding it in the app. I can't really say with any certainty why that feature is no longer functioning properly on the latest release, and it would be a little value for me to look into it at this point as I am now working with a completely new codebase. Will just have to hope for better luck next time when that feature makes it back into future iterations of this project.

Regarding the vibration issue, I am aware of the commit from flar2 that you're referring to. The problem is it directly conflicts with a separate qpnp-haptic related commit that, believe it or not, is required for Lineage to boot. If there is any way that I can reconcile the two, I will.

As [MENTION=7030080]Star_king12[/MENTION] has bluntly pointed out, the Adreno Idler driver is more no longer useful for modern devices such as ours. I dropped it intentionally once it occurred to me that it was no longer being used by basically anyone and as assumed that there was likely a good explanation for that.

If your referring to custom pie ROMs, yes the idea is to maintain cross compatibility, and I anticipate that it should be even easier to do so between stock and custom pie.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
i saw some other people test this out on stock pie knowing wifi wouldnt work and they commented on how smooth it was. so i decided to test it for lolz. Allow me to preface: its one thing to say a phone is fast, fluid, and smooth. and its another to say that it is equal to that of the Pixel 2. In my opinion, this kernel as of the latest build on stock Pie is 99% of the smoothness of the Pixel 2. thats really damn good. my way of determining this may seem flawed to some of you but i think we can all universally agree that a good way to see how smooth a phone can really be is to just open up the Play store and swipe around. On stock kernel is was pretty decent but you could tell it dropped some frames in the Play store. With this kernel its basically perfect with no observed dropped frames that my eye could see. Now thats amazing. I truly commend your efforts OP :D

Can't wait to see the new build
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Well, my goal is to port this over to truly support stock while changing as little as possible from the Lineage-only releases. The primary difference will be that the upcoming releases will be based on newer Pie source from CAF. Otherwise, I'm trying to stay fairly close in line with what I was doing previously. I still think its feasible that I could get the first beta release out by the end of the weekend, and if not it should be shortly thereafter. I've slowly but surely been making pretty good progress and I'm looking forward to seeing how this pans out.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MrPhilo:
Looking forward to this. I'm about to switch over to Essential from my OP6, but waiting for this kernel (legit) as the performance on stock with stock kernel or EX Kernel is abit laggy at times for me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Yeah, for the sake of choosing my words carefully so as not to have them misinterpreted, flar2 is a very, very talented individual who is far more experienced and knowledgeable than I am. That being said, I will make the blanket statement that most of the standalone kernels available for this device are built on top of OEM source, so it's not surprising that some of the issues you may encounter with the stock kernel are carried over into whichever custom kernels you may have tried. Neutrino uses a pure CAF base with minimal commits picked from OEM. I'm down to around 180 commits picked from Essential, which in the grander scheme of things is a pretty small number. I'm not saying that this is the best way to go about things, or even the right way, and it's certainly not infallible. It's just the way that I do it and as long as it's working out well for everyone then I will continue to do so.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Hit one final hurdle in supporting LOS/Stock cross-compatibility, being video recording. The fix needed for Lineage breaks recording on stock, and of course removing it breaks video recording on Lineage. Currently exploring what options may be available for hacking out a solution.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Possible to have an Aroma style installer check MD5 of the vendor partition and compare it to stock, and adjust accordingly? The system partition would be too large to do it quickly, but vendor might be small enough.

Of course, you'd probably need to build and package two separate boot images into one installer, which would be tedious AF for you, and not really useful when trying to fastboot flash a kernel. It would be limited to only TWRP style recoveries.

Nevermind, lol.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
yep, ive see you've been going hard with all your commits. but that is quite the predicament to be in. perhaps consult flar, nathen, or franko?
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
It's fixed already ;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
did a test here with an odd result. So I went a head and followed the procedure i posted above to pass saftynet. Right after that I clean flashed lineage os to see if I could use the patched boot.img from my previous flash. It did flash but it did not pass saftynet this time. I had to again flash your non-magisk boot.img and then boot into rom and patch it again and then transfer the new patched boot.img to computer and fastboot flash it and then saftynet passed. Seems like the patching process is unique per new flash to pass safetynet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Well thank you for the independent confirmation, it certainly helps to solidify my trajectory going forward. I was only speculating about the unique patching scenario but this seems to have confirmed my suspicion. Much appreciated, it likely would have taken me awhile (if ever) to pick up on this as I've become accustomed to failing safetynet checks in lieu of having xposed installed.

I'll see if I can't crank out 4.4.119 by tomorrow and update the OP according to your findings.

Thanks for your feedback, I'll make note of this in OP during the next update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
4.4.119 build has been uploaded. I've omitted the pre-patched image and removed them from the build archive for the reasons previously discussed in this thread.

To preserve or enable root during kernel update please see the following instructions:

Install/Launch Magisk Manager

Select 'Install' (Twice)

Select Patch Boot Image

Locate 4.4.XXX-lineage.img

Fastboot flash resulting patched image @ /sdcard/MagiskManager/patched_boot.img

I will update OP for this release to further clarify and update download links when I have a moment today.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
***OP updated for 4.4.119 release***
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Thanks for the update. Updated from your previous build to this and patched it using magisk. Safetynet passes so everything is running great. :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
***OP updated for 4.4.120 release***

Download
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Thank you for posting these! Really appreciated everything is working smoothly with root.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Going to bump to .78 now that it's on lineage? Not asking for an eta by the way, just curious.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
What do you mean? We're on .120 here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
New lineage is 4.4.78
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Have a look
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Read the op to understand what these build are. The build here is merging mainline fixes and is newer that the one compiled with LOS 15.1 by stock. This kernel is currently 4.4.120
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
What he said ^^

These builds are based on the stock Lineage kernel with upstream linux-kernel source merged in. They're more current versions of the kernel Lineage ships with by default. Seeing as 120 > 78, what you're suggesting would technically be a downgrade. That's not to suggest one is better than the other, that's somewhat of a subjective matter and I don't mean to give the impression that these are superior to what invisiblek is offering. Lineage has their reasons for sticking with the device's stock kernel release, these are just to offer an alternative approach for those of us who prefer to be on the bleeding edge of development. That being said, I think anyone that's flashed these builds will agree that you won't find any stability issues here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Hey sorry I was unaware! I appreciate the explanation :) I used your kernel for the past bit. I was thinking .78 was higher lol Doh!
[Essential Phone ROMs, Kernels, Recoveries, & Other] blakeatl:
I flashed the latest kernel through Magisk but for some reason .118 is still shown. I'm on AOSIP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
You're lucky then...

I would never trust a kernel to work like that... Flashing a Lineage kernel with ramdisk on AOSIP is really asking for trouble unless you can recover...
[Essential Phone ROMs, Kernels, Recoveries, & Other] blakeatl:
I understand. I'm having no issues at all though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I think you're a little confused as to what Magisk Manager will and won't do for you. You can patch the boot images I'm providing via Magisk Manager, but it will not install the kernel for you. Magisk Manager simply takes the boot.img you feed it and outputs a second boot.img (patched for systemless root) to /sdcard/MagiskManager/patched_boot.img. You'd still need to take that patched image and flash it via fastboot in order to install the kernel. I think I was pretty clear about that in the OP. Bottom line, Magisk or no Magisk, if you're not using fastboot flash boot boot.img then you're not installing a kernel. This is why you're still seeing your ROMs stock kernel version being reported in settings, because you never actually installed anything.

That being said, as someone else has pointed out, perhaps it was for the better seeing as A) this kernel is for Lineage, and B) your ROM's stock kernel is only 2 versions behind current linux-stable (unlike Lineage, which is 42 versions behind). I have seen one other report of someone installing these builds on AOSiP without issue, so you're welcome to try it again, just understand that I take no responsibility if/when things go south.
[Essential Phone ROMs, Kernels, Recoveries, & Other] initguru:
Dear [MENTION=6474612]return.of.octobot[/MENTION]

Some people here(including me!) have been suffering from some wakelocks.

Is there a chance for your upstream kernel to merge this wakelock blocker feature?

https://github.com/flar2/mata/commit/9fcee7921f55b798613d08efcf732f50229ed710
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Are you and those "some people" having wakelock issues on LOS 15.1?
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
oh? do tell more please :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
https://github.com/0ctobot/neutrino-staging/commit/274204e1c954a1c46f9e1099b4ba652281a961fb I believe that's what they're referring to