yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
When I had magisk installed and was running lineage... The OTA program didn't care about signatures...

Since it's not a Delta... It's not patching anything... Just overwriting what is currently there... So it SHOULDN'T matter...
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Hey, great to see you here. I remember you from the Nexus 6 forums. Thanks for the answer :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Yeah... I couldn't help myself... When I found out buying this phone was a direct thank-you to Andy Rubin...
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
He is right, I was recommending that the unrooted image be flashed prior to OTA but you could also certainly restore the boot.img that was originally included in invisiblek's build for maximum peace of mind. I would tend to agree that it doesn't actually matter as the OTA should be installing a completely new image on the opposite slot so I'm not sure what difference it would make, I was just leaning my instructions towards the safe side, perhaps I'll try and clean them up.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kakabobo:
only for lineage can it work on aosp rom?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Yeah, it's literally built from Lineage source with upstream Linux kernel merged in. I wouldn't recommended flashing this on AOSP any more than I would recommended flashing the stock Lineage kernel on an AOSP build. Even if it booted I imagine there's a good chance it would break things to the point of being unusable. That being said, I haven't tried it so I'm only speculating. If you do, make sure you've got a copy of your ROMs stock boot.img to recover with. But seriously, I wouldn't.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Without further ado, 4.4.118 images are available for download here.

Same deal as before, built from unadulterated upstream linux-stable source. Stock and Pre-Patched Magisk variants available.

I did manage to get a CAF-based version of this kernel building and booting, however it broke my touchscreen and is clearly not ready for public consumption. So, until further notice we're going to stick with the 'if it ain't broke..' philosophy, although you may or may not see me releasing some experimental builds in the future.

For now, enjoy 4.4.118 ;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
***OP updated for 4.4.118 release, revised comprehensive installation instructions***
[Essential Phone ROMs, Kernels, Recoveries, & Other] shooterlgk:
That's for the build today right?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
In theory these images should work on any LineageOS install, regardless of build date, but yes it's compatible with both the 02/26 and 02/28 releases from invisiblek. I've updated the screenshot in OP which shows this kernel installed on the latest Lineage OTA.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
flashed your kernel with magisk support on todays (28th) lineageos build. Magisk is not passing safteynet.

edit: followed your instruction to patch the boot img using magisk and now it passes safteynet. had to use the non patched on from here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Good to know, I'll have to make note of your findings in the OP. I would've never figured that out myself as I've got xposed installed and to the best of my knowledge my SafetyNet checks will always fail because if it. I've really just been offering the prepatched images because I thought it would be helpful to allow some to bypass the step of patching manually. However, I'll have to consider whether it might be a better idea to just provide the clean image with instructions on how to patch it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
So this is what I did.

1. Flashed lineage os. Set it up.

2. Flashed your kernel (non magisk version) using fastboot and booted back into rom. (Not sure if this is necessary as I later on flash the patches version by magisk manager).

3. Install magisk manager. Have the non magisk version of your boot image on my phone. Patch it with magisk manager.

4. Transfered the patched boot image to computer.

5. Flashed the patches boot image using the computer (fastboot). Reboot into system.

6. Safetynet check passes.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Thanks for sharing. I essentially went through the same process to patch these images myself after they were built, perhaps there is some kind of security measure in place where the boot.img needs to be installed to the same device it was patched on? I find it strange that it would successfully root the device, but not pass SafetyNet. I'll think on that and figure out if it makes more sense to just release unpatched builds in the future.
[Essential Phone ROMs, Kernels, Recoveries, & Other] blakeatl:
I flashed it on AOSIP without issue. Not sure if it's considered the same as AOSP.....
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
I wouldn't realy mind and I think it would make it easier for you too. If the patching is unique per phone then it makes sense that we patch it ourselves. But we need upstreamed updated kernels!!! so don't stop doing those!! ;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Yeah of course, no sooner had I uploaded 118 than 119 was pushed. I'm not sure if I'll be able to get one out for each release before the next one comes out, but I'm going to be keeping these updated a frequently as I can. Anyway, I was only speculating about device-specific images, but I'm going to try and flash an image that was patched by my buddy and see if I can reproduce any issues. Regardless, I'll likely stick to uploading unpatched images in the future.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tech_Savvy:
I always do it that way...i have a script i run that flash twrp to Current boot and then i flash update kernel nd reboot..jt yave to remember to remove pin every time
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tech_Savvy:
Heres the script if ur interested..it backs up boot to /data/media and /sdcard....then it flashes twrpboot to current boot slot and immediately reboots to recovery (providing you have twrp.mata.11.img renamed to twrp.img nd in root of sdcard)...that way if you forget to remove pin you can still flash the boot.img in /data/media since on /sdcard is encrypted....nd u can boot back to system....
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
So if I'm on RR ROM what are the correct steps for installing kernel and patching boot IMG by magisk. Thank you very much
[Essential Phone ROMs, Kernels, Recoveries, & Other] billybong10:
Download kernel go to Magisk click install twice select patch boot image select kernel. Rooted kernel will be found in Magisk manager folder. Flash that to boot partition.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
I like this...

Hmmm...

Where can we store the TWRP image in magisk so we can put the script in /system/bin/ and call it from anywhere...

Oh... And maybe modify the reboot menu to add reboot recovery and run this script

Edit:

/data/local/

That's where it should go... With a helper script ala [MENTION=4544860]osm0sis[/MENTION]'s AIK...

Ok... Now... One more question... I wonder if we could use the command line in the script to remove security... Since we have root already...

Hmmm
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tech_Savvy:
I have it in sdcard nd just give root premission to terminal to execute it.... I thought about it nd added the lockscreen.db to mine but i have no fingerprint enrolled so idk if it works for ppl wit fingerprint
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
Thank you ! Worked like a charm.
[Essential Phone ROMs, Kernels, Recoveries, & Other] billybong10:
NP
[Essential Phone ROMs, Kernels, Recoveries, & Other] duminduweera:
How can i adjust the vibrator strength on this kernel, cannot seem to do it in EXKM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertbarber:
It's under Miscellaneous in EXKM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] duminduweera:
Yes i saw that, but it doesn't actually adjust the strength, its like that option doesn't work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I'll take a look into this prior to the next release, I never personally included any additional functionality as far as vibration control is concerned so it's possible that tunable needs to be exposed for user configuration.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
Does the backlight dimmer option not work for anyone else? I've set it in EXKM and have both the backlight dimmer and the level for the backlight turned on, yet it refuses to change when tuned in EXKM. I also tried using the backlight dimmer option in Kernel Adiutor, that didn't work either.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Eun-Hjzjined:
I too have never been able to change vibration, and noticed the backlight dimmer hasn't done anything noticeable. One more thing is the color inversion toggle doesn't work for me either.

I use KA, just thought it had to do with that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
The KCAL inversion is broken by design, it's a deprecated feature. I originally had removed it entirely, but it was reintroduced with no functionality as a placeholder to maintain compatibility with apps like CF.lumen.

As far as the backlight dimmer goes, I'll do some testing on that as well. I used the same implementation, for instance, as flar2 does in EXKernel. It's worth noting that in theory the backlight dimmer is operating on a scale of 0-255, and being that the default is 0 there's really no where to go but up. I think the way to test it would be to set it as 255 and see if it effectively disables backlight dimming. It's also a possibility that LOS Adaptive Brightness could be overriding the setting. I'm in the middle of some major housekeeping anyway so now's the to be pointing out issues. So, thanks, consider it noted.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I really ought to stop making promises. Thought I was almost out of the woods, but to be honest this update is kicking my ass. I'm not sure if it's the new Lineage source, or the new Essential source itself but between the two it's been an absolute nightmare trying to get back to where I was at with this last release and I'm far too OCD to compromise on my design goals and I may have to go back to the drawing board entirely. Simply put, I have no idea when I'm going to update Neutrino again other than as soon as I possibly can. Until then, we all know the last release is solid af and at the very least it's even with the stock Linux kernel version, so it'll have to do for the time being.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Airwolf79:
Tried to find this in the thread but couldn't. Which firmware version do I need for wifi to work?

Edit: Disregard. I forgot that with RR, boot.img gets flashed to other slot. All good now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
No worries

Both the 4/11 and 4/12 builds have a strange bug no anyway. The built-in-updater no longer finds updates.

The Updater no calls for a changelog from LOS official for MATA...not Invisiblek's own servers. So I'm wondering of the updater is calling for updates from LOS-official too.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Funny you should mention that, I finally updated from the 04/05 build to 04/14 this morning. In doing so, I came to the realization that half of the problems I've been running into were being caused by trying to test kernels based on the new source on an old build. Needless to say, I'm feeling like an absolute moron right about now. So, there may be hope yet now that I've got my head out of my ass.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
LOL I have a more bizzare one than that.

I flashed back to March unrooted stock to get the April modem and other OTA stuff via OTA update (Back-to-Stock zips didn't exist yet for April)...it went crashy on me after a day following some playing around in Magisk....no biggie went back to LOS and your kernel. So what? When I got back to LOS--About-Phone said I was still on the March modem. :eek:

Not sure what I'll do now that I'm on 4/12, given the OTA updater in LOS doesn't appear to work....I'm taking tomorrow off work so maybe I'll wipe and flash the 4/14 zip---although that is how I got from 4/11 to 4/12, and same problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheBurgh:
What's the procedure to flash through twrp? Just check slot current LOS is on and wipe and flash new zip to that slot? Thanks in advance
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Honestly, as much of a crack flasher as I can be, things are so solid on what I'm running now (RR with your kernel) that I wasn't sure if I wanted to mess with it anyway. Take your time, your last version is perfect so no point in rushing to be on the latest just to say you are.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Basically, although when you flash TWRP it will boot to whatever your current slot is. So, if you've got Lineage currently installed to slot A and then flash TWRP it will boot to recovery on slot A and you just do your standard wipey flashy thing. It doesn't hurt to check, but it also effectively doesn't matter what slot you flash Lineage to as long as you make sure you're rebooting to the appropriate one afterwards.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
If you guys can answer me this it could prove to be incredibly helpful, are any of you currently using the latest Neutrino release on the newer/newest lineage builds (12th or 14th, or whichever ones began using the new 4.4.126 stock kernel)?

If so, are you experiencing any reboots and/or severe hardware key lagging, specifically volume buttons?
[Essential Phone ROMs, Kernels, Recoveries, & Other] duminduweera:
I was on the 12th built and everything was fine other than the touch sensitivity, i had to change that manually.

I've reverted back to a previous built because my phone wasn't deep sleeping properly on the April 12th built.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gregfink83:
I'm still on the 12th build and running neutrino with no issues. No reboots. No lagging. Volume buttons seem fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nomesrjp:
Likewise, I too have been using 4.4.126 on each LOS April release (lineage-15.1-201804xx) without issue. In fact, it's the best kernel release yet and deep sleeps perfectly.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Thanks guys, that's good to know.. also, interesting in it's own right. The touch response thing is tied to changes made in the device tree and not the kernel source unfortunately. I've tried several test builds based on the new lineage kernel and the touch response still sucks. Granted, you can tune it to the point where it's passable but they did choose a real crappy default setting. Increasing the tunable to compensate seems to cause pronounced jitter, lower it too much and the latency becomes so bad you can't enter a lockscreen pin. Yeah, I really don't get this feature, I know it's from stock but it seems to me that at best the options it provides are so extreme no one will ever use them, and at worst actually made things worse.

Anyway, so oddly enough based on what you guys are telling me, my old Neutrino source based on the old Lineage kernel is running better than my new Neutrino tests based on the new Lineage kernel. Ideally, I would really like to be able to base this on the current Lineage kernel but at least I know I can dump it and go back to what I had if all else fails.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Seraph08:
:highfive:
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Don't mind that guy.

I'm still not going to make any promises in regard to a release because I found that unforeseen problems crawl out of the woodwork as soon as I do. That being said, I've had a bit of a break through and managed to trace back a couple of CAF commits at the root of the problems I was experiencing trying to rebase on this new source. I've still got to wrap up the upstreaming and get everything back to the point I was at with the last Neutrino release, but hopefully that will be the easy part. As I've right now, I've begun merging CAF tags back into the source and everything appears to be behaving beautifully again. Needless to say I'm thrilled to announce that Neutrino should be back amongst the living very soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
No prob :good:

Bootes is clicking along normally on the 4/17 LOS build in the meanwhile. Curiosity question, once a kernel release is patched for Magisk into a patched_boot.img does it need repatched against a new LOS when LOS updates? It seems to not matter, but I was wondering if I'm just lucky or not.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
If I'm understanding your question correctly, no generally you wouldn't necessarily need to repatch a boot.ing just because Lineage updated. If we're talking about a stock boot.img, your best bet is to just use MagiskManager to install to second slot after taking an OTA then you don't have to worry about it and you'll always have the current stock image patched. If you're talking about this kernel, as long as it's still functioning properly on your current build there should be no need to repatch it after a Lineage update as there's really no correlation between being compatible with Magisk and being compatible with your current Lineage install. The only reason I've been discussing compatibility at all is because (starting, I believe, with the 4/11 build) Lineage EOL'ed their old kernel source for this device and switched to a completely new one but that should have no bearing on Magisk.
[Essential Phone ROMs, Kernels, Recoveries, & Other] duminduweera:
has the development of this kernel stopped or the developer just busy with other things? this kernel was perfect with LOS, but its giving me some random restarts and deep sleep issues with the latest LOS.
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertbarber:
Probably just busy with other things. He has added some commiits here https://github.com/0ctobot/neutrino_staging/commits/OPM1.180104.141_lineage-15.1 very recently so as far as I can tell he is still working on the kernel itself.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gregfink83:
I'm on the LOS 4-23 build with this kernel and have no problems at all. No reboots and insane battery life.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
People do have lives outside of XDA lol. It's only been a couple weeks, cut the guy some slack.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Further not only did LOS rebase their kernel one week...then a week later they added HAL-level color profiling and god knows what else.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Exactly, I can't even imagine the amount of work this takes, especially if you factor that he may have a family and job outside of this.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Projects not dead, sharp individuals may have noticed that I temporarily moved my work over to this repo. Apologies for the radio silence, I did spend quite a while getting my ass handed to me debugging and working out a proper pure CAF base and it escalated into a huge learning process to the point where I didn't want to put out another release until I managed to meet my own developing standards. Meanwhile, I had new OEM, CAF, and Linux stable updates to contend with seems like every other day, but needless to say the end result is better than it ever was. I have indeed also had a good deal of personal turbulence going on as well but that's neither here nor there.

I am officially done constructing my newest base from the latest PPR1.180412.048 developer preview source from Essential rebased on pure CAF source, with an overhauled implementation of EAS based on upstream code among other things. All that's left to do is to bring back the existing Neutrino features from previous releases and take it from there. I'm not going to speculate on when this will be completed, but I can say that it will be soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Testing for a potential release candidate is underway. Assuming everything goes smoothly (which I anticipate that it will), you can expect a new drop by tomorrow.
[Essential Phone ROMs, Kernels, Recoveries, & Other] KuranKaname:
<3
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
If he hadn't already shown up, I would have taken this opportunity to shout out [MENTION=6760768]KuranKaname[/MENTION]. His input and assistance have been instrumental in breathing new life into this project. I may have been able to do it without you, but it wouldn't have turned out half as well as it did.

**OP updated for Neutrino Kernel release (4.4.133-caelum)**

Changelog (Summarized):

Complete source overhaul, based on Essential's Android P Developer Preview (PPR1.180412.048)

Rebased on CodeAurora sources, tracking kernel.lnx.4.4.r27-rel, and up-to-date with LA.UM.6.4.r1-08500-8x98.0

Checkout WLAN drivers @ LA.UM.6.4.r1-08500-8x98.0

Revamp Lineage EAS implementation using upstream sources

Dynamic SchedTune Boost

EAS-Compatible Input Boost

Revert Min/Max Backlight Limiting

Various upstream updates targeting clang, kasan, and aes crypto

Full changelog available here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Happy Panda!
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
That was quick ;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Hmmm, I didn't know we have that many kernels for our device:)

Gonna add one soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
I *may* have been spamming F5 on your GitHub this morning after seeing *.133 changelog on GH last night. :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
Does anyone know if the newest kernel helps the deep sleep issues prevalent in 8.1?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I can only speak for myself, but she seems to be sleeping just fine as far as I can tell. I'd be interested to hear how everyone else is fairing in that department.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Sleeps like a kitten. I missed this kernel while it was away. BTW this is with BT on and a smartwatch paired
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Awesome, yeah I don't expect there to be any more drastic gaps between releases. More than anything I was just starting to become discouraged with the amount of trouble I was encountering, but it ended up being a blessing in disguise because I learned a ton throughout the process and I feel like I've really nailed my design goals even more so this time around and I'm very pleased with the results. The nice thing is we're way ahead of the game now with the P kernel source, plenty of time to refine things until Lineage catches up.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
Just installed in over an older version of RR ROM and am very excited. Lockscreen pattern doesn't work but pin does and fingerprint is good to go. I'm sure new version of kernel will be stellar as always. Thank you so much OP!