yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
Yes yes very exciting stuff. Plus we are bound to get the September security patch any time of the day now since the patches usually drop every first monday of the month. then this lovely kernel is almost ready as well for prime time. feels great to have chosen this phone
[Essential Phone ROMs, Kernels, Recoveries, & Other] soup6020:
Hello, would it be at all possible to add the necessary drivers for applications like DriveDroid and USB Mountr to neutrino? It's not a hardware limitation, someone in invisiblek's Discord got it working on a custom kernel, but their implementation was pretty ugly lol. I understand if you'd prefer not to, but it'd be a neat feature to have.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Yeapp Yaro's been helping me out with the cross compatibility issues as he's on stock and I'm staying on Lineage until I get this bringup finished, so between the two of us we've been able to work out a few kinks in terms of supporting both ROMs. What we came up with is not a perfect solution, but it will work for this device and the ROMs currently available for it and the ROM detection via command line can likely be further improved via AnyKernel. I basically just need to finish up with the EAS implementation and we should be ready to roll.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Well, just when I thought I could see the light at the end of the tunnel. The latest OTA from Essential has nuked my ability to support LOS and stock due to this plague of a commit. Its presence breaks input detection on Lineage, reverting it will break input detection on stock, and there is no hacking my way out of this one.

The only way I'll be able to continue supporting Lineage in light of this, is if whoever's maintaining the unofficial builds now updates their vendor blobs accordingly. I have no idea who does these builds now following invisiblek's departure, or what source is being used to compile them. If any of you know the answers to either of these it may be a helpful push in the right direction, although I somehow doubt I'm going to be able to convince the lineage maintainer to update to Pie blobs for their Oreo builds, but that is what would need to happen.

Needless to say I am immensely discouraged by this, given the amount of effort I've put in trying to make this work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
:( Its looking like you might have to stop supporting LOS since as you said he has departed and as far as i know, the torch hasnt been passed on to anyone as of yet. it is unfortunate but things like this happen
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Well I guess what I'm getting at is, someone has to be doing these builds, we just got a new LOS OTA a few days ago. We've gotten several updates since invisiblek announced his retirement, so either he hasn't actually quit or we have a new maintainer.

Either way, I do have a possible 'emergency use only' solution, which I would really rather not do but will look into in order to gauge it's feasibility. This being, two kernel images, one zip, AnyKernel decides which one gets flashed based on build fingerprint. Stock gets one, custom ROMs get the other, it would only be a difference of 2-3 commits between variants.

I'd much rather Lineage just update their blobs, but I will look further into this.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tvisforme:
Where did he announce this? I'm trying to find it in the thread but I haven't as of yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NikoZBK:
Invisiblek automatically builds LOS every few days/week
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I'm being told now that it is no longer invisiblek releasing these builds, and that Ethen Chen is in fact the current maintainer.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
Blek still releases builds regularly, he just stopped hosting them on his site and shifted them to github since there's basically unlimited hosting of files for developers there. You can find them here: https://github.com/blekreleases/mata
[Essential Phone ROMs, Kernels, Recoveries, & Other] tvisforme:
Do you know if there's still a possibility of the build becoming official? It has been a while since I've seen any posts about that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
Blek himself has stated multiple times that his personal LOS builds will never go official, as LOS doesn't ship with gapps. However, he did mention that it has been picked up by other members of the active LOS team, and it'll eventually become official. No dates or anything though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mattern1974:
I wanted to personally take the time to thank you for developing this kernel since it seems to have fixed all the smoothness and touchscreen issues I was experiencing with LOS. Thank you for all your efforts!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] izzyfanto:
It seems the ElementalX kernel doesn't have this customization, so I thought I'd ask here.

Is there any plans to add LED customization? The blink rate is so slow! Thanks in advance! :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Hmm, that is interesting. I've heard from a couple sources at this point that intervigilium is ghost writing these newer updates in invisiblek's absence. Would be nice to know who's doing them one way or the other but I suppose it's neither here nor there. I'll go ahead an assume it's invisiblek until I see some actual concrete evidence to suggest otherwise, it just seems to me that he's up and vanished from maintaining the LOS thread for awhile now.

Again, this is based purely on heresay and some hints on gerrit but my understanding is that yes, this device is on the road to receiving official support alongside the Pixels. Lineage is already in the process of revamping their backup/addon.d scripts to support A/B devices so the GApps issue will no longer be an issue. I have to suspect we won't see anything official until LOS 16 rolls out but that is pure speculation.

Can anyone still using my kernel on the most recent LOS update (09/09) confirm for me that everything is still running smoothly, particularly in regards to having functional display and input detection? I just want to confirm that they are still using Oreo vendor blobs, which I suspect is the case.

In other news, I am making slow but sure progress. It's taken me longer than anticipated to sort out my EAS implementation and port over what I had going on in the previous releases to the new codebase. I think I mentioned this, but unlike the Oreo tags, CAFs pie source seems to have code present to support both HMP and EAS so it's taken a bit of trial and error to reconcile commits between the two and properly gut all HMP code but I think I've managed to do it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hx3:
Everything is running great and smooth on my end with your latest kernel and the 09/09 build of LOS. Still need to raise the touch smoothness in Settings, but I'm sure that's normal.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gregfink83:
I second that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
[MENTION=6474612]return.of.octobot[/MENTION]

I'm on the latest build of LineageOS with Neutrino and all seems to be well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kdp162:
The official DM's for Los Mata are Ethen and Rashed .. intervigil@gmail.com , rashed@linux.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] kdp162:
I just got confirmation that Invisiblek is indeed still building the unofficial Mata builds as well
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Yay, more conflicting information!

EDIT: Sorry, just realized the same person made both of those posts. So, we effectively have three maintainers is that the rub?
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
LOS is officially being maintained by intervigil and rashed, but blek is still rolling unofficial builds and seems like he'll continue to do so for the foreseeable future.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kdp162:
Exactly

---------- Post added at 03:05 AM ---------- Previous post was at 02:55 AM ----------

https://updater.invisiblek.org//mata

Link for Dan's unofficial builds

---------- Post added at 03:07 AM ---------- Previous post was at 03:05 AM ----------

Dan is continuing to build unofficial but it looks like Mata will become official since it now has official LOS trees

Dan is no longer affiliated with Los so maybe he's just building until it goes official.. Dunno haven't asked him what's up yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Welp, regardless. I'm pretty please to see this (attachment), it looks like they've incorporated the dreaded display breaking commit, so it seems like there may be some hope of not having to maintain two separate branches after all.

Of course, this won't come into play until (hopefully) until the next LOS OTA. At that point it will actually be good news if my previous release stops working.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
For the sake of courtesy to anyone who still cares, I will be requesting the closure of this thread. This does not mean I am effectively throwing in the towel on this project, it's just indicative of the fact that I have run up against a wall which I am currently unable to overcome on my own accord. It seems I am currently the only person on the entirety of the internet trying to implement EAS on the new CAF Pie tags, and my individual attempts have had embarrassing results to say the least. I have no desire to maintain an HMP based kernel as there is very little that I'd be able to offer on that end that you wouldn't be able to find elsewhere, by someone more talented than I am. With that being said, until I get smarter, or find a like minded collaborator I see no reason to keep this thread open for the time being and passively stoke expectations for a future release that is unlikely to materialize in any sort of timely manner.
[Essential Phone ROMs, Kernels, Recoveries, & Other] xanthrax:
Thread closed as per OP request, can be reopened at any time if he would like to.
[Essential Phone ROMs, Kernels, Recoveries, & Other] SacredDeviL666:
Thread reopened as per OP's request.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JBlaze05:
Yep. Glad to see its back in action.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
With all do respect guys, I requested this thread be reopened in preparation for new releases. I was hoping that it would silently remain unbumped until I was ready to update it but it seems that ship has sailed.

Yes, there is a new build and I will be continuing work on this project. Some of you may very well already be running it, but there are a few things I need to take care of before it hits XDA officially and more importantly there is some pertinent information that I need to make clear in the OP in an attempt to mitigate future headaches. I will attempt to summarize some of these points for the times being..

- New builds will be in AnyKernel zip format

- They will run on anything including stock and oreo/pie custom ROMs provided that your firmware is up to date with PPR1.180905.036 (September) or newer.

- Just because it runs on stock does not mean that you should flash it. This is an EAS kernel and is best suited for use with EAS compatible ROMs, I will not entertain complaints stemming from the use of Neutrino on stock or any other ROM that does not natively support EAS.

- If you choose to flash Neutrino on stock YMMV and you are doing so at your own discretion. Stock/universal support is a perk and an experiment on my part. Do not make me regret giving you the ability to flash on stock, I will drop public support for it like a hot potato.

That's more or less the gist of it, I'm going to take the next day or two to get a few things in order at which point I will update this thread and officially drop the new release. Thank you for your patience.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LoveScarGuitar:
I knew someone slipped up when I saw all of the 'DELETE's lol.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
It's no biggie, I just would rather not have links to builds floating around before I get a chance to update this thread. I'm bumping from 4.4.160 -> 161 for the public release anyway. It really won't be too long before I drop on XDA, final builds are compiling now, mostly just have some logistical things I want to get in order. We're talking a day, two days at the absolute maximum.
[Essential Phone ROMs, Kernels, Recoveries, & Other] raoulbhatia:
Thank you so muxh for picking this up again. w/o your work and kernel, I would have been forced to go back to stock a long time ago due to a lot of issues that I experienced w/ LOS on mata.

Happy to help if there is any way you can think of!

Raoul
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Just bare with me guys, there's been an issue identified during prerelease testing that I'm trying to quash prior to official rollout. Luckily, I'm fairly certain that I know what's going on and it should be remedied quickly. You can learn more about this here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Paddybecks87:
Thanks for the update! I'm unbelievably excited for your kernel. If there is any possibility to help you test it before you publicly release it, I'd be more than happy to help out. The PH-1 is my secondary phone, so it won't be a loss if it temporarily malfunctions.

Either way, thank you so much for your work, really looking forward to running your kernel.

Greetings
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
4.4.161-NeutrinoKernel-gemini

**OP updated for Neutrino Kernel release (4.4.161-gemini)**

Please, for the love of god, read through the updated OP, or at the very least the RELEASE NOTES:

Neutrino Kernel release for Essential PH-1 (mata)

Linux Version: 4.4.161

Neutrino Version: gemini

HEAD: c1dd910

Changelog (Summarized):

Move to AnyKernel2 format for universal compatibility†

Rebase on kernel.lnx.4.4.r35-rel (LA.UM.7.4.r1-03600-8x98.0)

Update to latest Essential P release (PPR1.181005.034)

Build with self-compiled Clang 8.0.3 and GCC 8.2.0

Revamp EAS implementation for Pie

Implement and enable VDSO

Introduce oom_reaper and various memory management enhancements to improve LMK performance

__________________________________________________

Carryover from 4.4.145-neutrino_fornax:

Maple I/O scheduler

Broader subsystem support for power efficient workqueues

KCAL gamma control

Overclock CPU (partial) silver cores @ 2035 MHz

Underclock GPU @ 180 MHz

Backlight control, backlight dimmer

Fsync toggle (enabled by default)

Boeffla Wakelock Blocker v1.1.0

Wireguard Support

Drop Qualcomm's cpu-boost in favor of [MENTION=4800121]Sultanxda[/MENTION]'s cpu_input/devfreq_boost drivers

Adapt cpu_input_boost for compatibility with Dynamic SchedTune Boosting

Correct treewide build warnings

Treewide memory allocation/overflow patches from mainline

(Complete Changelog)

† Neutrino will run Oreo/Pie, custom as well as stock ROMs provided that minimum firmware requirement is met (PPR1.180905.036), anything older than this will result in broken input detection. Furthermore, just because it can be flashed on stock does not mean that you should. This is an EAS kernel best suited for use on ROMs which natively support EAS, otherwise you will likely find battery performance to be sub-optimal. I will not entertain any complaints stemming from the use of Neutrino on ROMs incompatible with EAS (such as stock). If you choose not to heed my recommendations, you are doing so at your own discretion.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Jz5678910:
Thank you for adding stock support, right out of the gate it's so much smoother. No crashes, no FC's. For my use cases it's running really well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Did you flash this via TWRP or EXKM?

I currently have the Stock 181005.34 firmware, with magisk 17.2 and persistent TWRP, and was curious if there were any issues with flashing that you ran into. Also wondering if you've been running it long enough to notice any battery life issues, as suggested may happen by [MENTION=6474612]return.of.octobot[/MENTION]
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I would agree that if you value performance over tremendous battery efficiency than it can be a viable option for stock, I'm using it on stock currently myself for testing purposes. I'm only going out of my way to discourage use on stock because users who may be used to the battery performance of prior builds will not achieve the same results flashing an EAS kernel on an incompatible ROM and I'm just trying to avoid getting spammed with "muh battery suxx" comments from those who might not understand what EAS is and why it may not be in their best interest to pair it with stock.

Use on a compatible, EAS ROM should yield the same level of power efficiency as previous builds. Flashing on stock, or an HMP custom ROM (in my experience) has resulted in mediocre to average battery life. It's more of an ongoing experiment to see how good I can get it to run on stock despite the compatibility issues, but I make no promises and doubt that it will ever run as well on stock as it will on ROMs with native EAS support.

It's not so much a matter of if, battery performance simply will not match what can be achieved with use on an EAS compatible ROM. To give you a rough and subjective figure based on my own observations, you're looking at ~10-15% per hour active drain on stock with no other battery saving techniques in play, probably about what you might expect using the stock kernel, if not slightly worse.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Thank you for the elaboration! As of yet, I haven't seen much in the way of custom Pie ROMs out there. Though, I'm debating whether or not to download Xenon source and build it "real quick" LOL. I don't think I've compiled anything at home since the earliest days of Oreo or maybe even so far back as Nougat, so I'll have to go reading up on required build environments, current syntax for the actual building, storage space needed, etc.

-- edit --

Darn it. Looks like Xenon isn't natively set up to use EAS anyway for Mata? Now I get to look into how to implement it, and how to get the power model parts in order to work with our device.

or ..... I could eat my kid's Halloween candy from the campground and just watch cartoons. Maybe I'll download LOS or AOSiP source instead of a forked variant of one of the two, and still eat all the candy.
[Essential Phone ROMs, Kernels, Recoveries, & Other] blair.sadewitz:
Thanks for continuing to work on this--I read through the whole thread today and was amazed at the attitude some people have. Funny, though, I don´t see any of those individuals doing unified kernel development.

I appreciate it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Jz5678910:
Didn't make a difference. I had the same set up you had flashed with no issues. Personally I've not seen a difference in battery the past few hours, but I'm also running helix engine and some custom kernel options, so I'm pretty optimized in terms of stock battery. For my personal use and settings, battery has been identical.

Edit: I used twrp
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
So, it didn't overwrite TWRP on flashing? Or, did you run the TWRP installer script after?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
It's probably not as bad as I'm making it sound, it's just not as good as it could be with a compatible ROM. I'm just trying to hammer home the disclaimer to cover my own ass. Right now I'm averaging about 10-12% active drain on stock which isn't atrocious and there's room for improvement there as well. If you guys are interested in WIP Pie ROMs for this device, I'd recommend checking out the telegram group @ https://t.me/EssentialPH1DEV. It's probably also a more effective way of communicating with me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Jz5678910:
I flashed the kernel, then the installer script (I always do just to be safe), and then magisk (again to be safe).
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Feel free to do as you please if it gives you piece of mind, but if you already have Magisk installed prior to flashing kernel you need not reflash it afterwards, the AnyKernel script will preserve your current Magisk install during kernel update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Jz5678910:
I just wanted to be sure that the twrp script didn't overwrite it. That was my main concern. It was also my fourth kernel flash of the day lol.
[Essential Phone ROMs, Kernels, Recoveries, & Other] governmentissuejoe:
I'm running stock Oreo. To your knowledge, would this kernel work?
[Essential Phone ROMs, Kernels, Recoveries, & Other] arjunv:
Yes running it from last few days. Awesome Battery, many thanks to the OP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
How is it that you've been running this for the last few days when I just released yesterday? Anyway..

What I can tell you is that if you're not up to date with PPR1.180905.036 firmware at a minimum then it will not work. If you can effectively flash Sep/Oct firmware on stock oreo and retain system functionality then yeah, this kernel should run on it.

On an unrelated note, I have come to the realization that the build I released yesterday is suffering from some pretty significant and unwarranted battery drain due to (I suspect) logspam stemming from the memory management backports I introduced to correct the freezing/locking issues that were being experienced during testing. I probably shouldn't have released it so hastily, but I did. I would recommend holding off on flashing until I upload a hotfix for this, but of course you're free to do as you see fit.
[Essential Phone ROMs, Kernels, Recoveries, & Other] arjunv:
I have been using the builds you have published on the telegram group. Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Ahhh should have assumed that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] governmentissuejoe:
Did you update the firmware to pie or are you running it on the last oreo firmware that was released?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Once again, you cannot run this kernel on Oreo firmware, your firmware must be up-to-date with September's Pie release (PPR1.180905.036) at minimum. I hate to sound like a broken record, but I say these things over and over because they are important, and if you fail to read the things that I say you will wind up with a broken touch screen.

As long as your firmware is up-to-date with the aforementioned build, Neutrino will run on anything regardless of ROM or Android version. If your firmware does not meet the minimum requirement, then you will boot with no input detection.

From OP:

Anyway, due to an oversight I made hastily trying to get this new release out, I will be pulling the current build and replacing it with an amended version this evening. I will give everyone a heads up once I have done so for those of you who may be interested.
[Essential Phone ROMs, Kernels, Recoveries, & Other] governmentissuejoe:
I hear you. I was just trying to ascertain arjunv's current configuration as he claims to be running your latest kernel on stock oreo. I was just curious if he was able to get it to work on the oreo firmware or if he updated to the pie firmware and was able to keep stock oreo running correctly. I meant no offense with my questions. I just wanted to get as many details before attempting this myself as I would like to avoid any bootloops.