yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Can't speak to the lockscreen pattern as it works fine on Lineage. By chance, does RR have the touchscreen smoothness settings from OEM ROMs? When Lineage first implemented it the default latency was so bad that it was almost impossible to enter a lockscreen pattern.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
No it doesnt.
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Testing this kernel :) hope all is well. Last time I tried this kernel I couldn't make calls looks like I can on this release! yay!
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Just a side note, I picked up on an oversight I made in regard to the new Dynamic Schedtune Boosting feature which you may or may not have noticed. While it has been implemented and enabled, it is not currently user configurable. I will correct this for the next release and properly expose the function, at that point I'll provide a better reference as to what the feature actually does and how to go about using it. Until then, there's nothing detrimental about where things stand now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Hmmmm has anyone noticed charging is really slow? Just took me like 2 hrs to charge from 40 to 95% using a thunderbolt port on my laptop. Usually it takes like 30 mins. Not a deal breaker just want to make sure I am not alone here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Anyone else? I haven't personally encountered this, but I use the charger that came with the phone more often than not. Is this the case for you with other chargers as well, or just the thunderbolt port?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
I'll watch it charge later today...I know last night when I plugged it in to charge the screen read "charging slowly" briefly then switched right over to "charging rapidly" like normal. Stock charger brick and cable.

Course it would be easier to test it right now, if your kernel had poor battery life and never Deep Sleeped. How dare you make things that work well. :cyclops:
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Here is what I am seeing it is gradually rising then caps at 2k ma/h then resets which appears to be extending how long it will take to charge. I tested the charge rate with AccuBattery.

Note: Yea I tried it with the wall charger and my laptop same result. I wonder if it is just me. :c
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
That's really peculiar, I'll try and look into a bit further and see if I can reproduce data like that on my device but I honestly can't say that I've encountered noticeably slow charge times on the surface level. Is this on Lineage, or another ROM?
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Lineage my good sir
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Yea, latest of both AICP and AOSIP both rapid charge fine over here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
Invictrix fast charges fine with the latest version of neutrino as well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Fantastic. I'm in the process of staging a modest update. Provided no major releases from OEM, CAF, Linux-stable, etc. manifest in the next 24 hours, I expect to drop a new build in a day or two.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
Great kernel for the PH-1!!

I'm very happy with the overall performance and low battery drain of this Neutrino caelum kernel, paired with most recent AOSiP. Thanks a lot for your work, [MENTION=6474612]return.of.octobot[/MENTION].

The only issue I've found is a couple reboots when using two or more tabs at the incognito mode of Chrome version 67.0.3396.68. I haven't been able to capture a last_kmsg because both times the reboot led to a boot loop and I had to force a new reboot, which I guess erased the last_kmsg.
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Hmmmm something must have broke on my end. I did a -w went back to stock then reloaded lineage everything is good now! :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
If you could perhaps dump a log via adb from launching chrome to the point that it reboots it may be helpful in determining exactly what is going on. In the meantime, I'll see if I can reproduce the issue on my device.

Excellent, very glad to hear that. I'm testing the next release as we speak, so again unless any last minute updates pop up (and even if they do) I plan to upload a new build tomorrow.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
**OP updated for Neutrino Kernel release (4.4.135-neutrino.delphinus)**

Changelog (Summarized):

kernel.lnx.4.4.r27-rel: Update to LA.UM.6.2.r1-08700-sdm660.0

Correct treewide build warnings

Drop State Notifier, convert Maple I/O to use fb_notifier

Enable GPU Nap State

[TEST] Apply Modest CPU/GPU Undervolt

Expose Dynamic Stune Boost function to be user configurable

Several optimizations adopted from sultanxda

Full changelog available here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
I thought the 835 had dynamic voltage something or other that made undervolting obsolete?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
That's partially right, 8998 does use circumstantial voltage scaling such that there is no longer one voltage level tied to each frequency step. However, the dynamic scaling still occurs based on a defined voltage table, much like CPU frequency scaling. Thus, the available voltage levels have been universally reduced, you can view the commits here and here.

I prefaced the change with [TEST] because I'm not 100% sold on it's viability and generally have not been a proponent of undervolting in the past, so I reserve the right to pull the feature if it proves to be problematic or ineffective. That being said, I pulled it from frap129's Pixel 2 kernels and was intrigued enough that I wanted to give it a trial. Fortunately the UV is non-user configurable so I won't have to concern myself with anyone overdoing it and creating issues for themselves where there weren't any, otherwise I wouldn't have even considered it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
My idle drain is now 21 ma/hr on the latest kernel(135) vs 35 ma/hr on (133). amazing.

Will give more feedback later but so far looks very promising.

I have a very consistent phone routine because of work so I will let you know about the gains.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
[MENTION=6474612]return.of.octobot[/MENTION] would you consider adding in the camera fix from AICP into the kernel? I believe LOS has already incorporated it into the stock kernel, and it would be nice to have working video recording while using LOS with neutrino.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Absolutely, I know exactly what you're referring to and will pick it up for the next release.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Oh, nice! I'll be sure to flash LOS tonight, and add Neutrino asap. I've been on stock for a few weeks in hopes that the video recording issue would eventually get resolved.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Obamaloominaty:
Is it possible to use FlashFire to flash this kernel? It could be an alternative to TWRP until we can get it to persist in the boot image
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Wut? You can flash the image through fast boot no twrp necessary.
[Essential Phone ROMs, Kernels, Recoveries, & Other] oken735:
Flashfire should not work.

What you can do, if you want to update on the go, as I do, you can dd your image directly in terminal emulator or an equivalent. A guide for how to do this is in the OP under "ADVANCED INSTALLATION (No Fastboot/PC)"
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
If you're rooted you can DD the kernel instead.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Speaking of dd.. Is that an option for flashing an entire rom zip to your "off" system partition? I'm sitting on rooted stock and was wondering if that would work. Or, is LOS not packaged in a way that allows you to extract the system, vendor, and boot images for flashing like that?
[Essential Phone ROMs, Kernels, Recoveries, & Other] oken735:
I haven't tested that, but theoretically yes, you should be able to do that.

You are right though, you would probably have to repackage it as .imgs, or something like that
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
In theory, it'd be possible in practice it's really not. I believe you would have to dump the system images in order to dd them, and to do that you'd need to flash the ROM conventionally first kind of defeating the purpose.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
If there were a way to convert the package.bin to images, though. I'm guessing that the secret is in the TWRP code. It would be sweet to have an app that reads a ROM zip and flashes it to your off partition, in addition to having the option to wipe data if necessary.
[Essential Phone ROMs, Kernels, Recoveries, & Other] oken735:
I managed to extract a boot.img using something like this a few months ago, but I don't remember if it worked after I flashed it, since it was back in December

https://gist.github.com/stainslav/5b88649f2554de47978a3f754dfcce2b

And it seems like similar projects existed but have since been abandoned. So yea, you might be able to extract .imgs from the zip on a computer and then push them to your phone, but at that point, you might as well just plug your phone in. I guess theoretically you could do something like this if you do not have access to a good usb data cable though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
Has anyone else noticed more input lag especially in keyboard with newest version or am I crazy? RR ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
My desired end result would be to be able to do the entire thing on the device, negating any need for the PC.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
If you remove lockscreen security and then dd TWRP into boot, you can select the slot you want a ROM flashed to, which would do what you seem to want to do.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I'd like to eliminate using TWRP from the equation.

The short of it is that I'd like to be able to flash a ROM from within the running OS, similar to the seamless updates. We have two partition sets, so why not put that to use? Only thing that might truly suck is a bootloop after the flash if you aren't near a PC to recover from it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Interested to hear if anyone else has found this to be an issue. It'd be interesting if this were the case as we never had an input boost driver before, but we do now. Have you played around at all with the cpu boost settings, if not perhaps you might try enabling Dynamic Stune Boost and see how it fairs.

I've kind of embarked on rebuilding my source from scratch basing on pure CAF code instead of merging CAF into OEM for various reasons that I can expand upon if anyone is interested. In short, jb-essential really likes to pick upstream commits before they're merged into linux-stable and in many circumstances those commits end up undergoing further changes before they're shipped. This results in a significant amount of broken, incomplete, and/or conflicting commits floating around in OEM source. I've combated this in previous releases by doing mass reverts of a hundred-something commits before redoing proper CAF/upstream merges, but it will prove beneficial in the long run to just reconstruct the stock kernel source from the ground up. This is probably going to suck, but it's only going to suck once and will result in a much cleaner source and much less headaches keeping it updated in the future.

What I think I may do in the meantime is re-release delphinus with the video recording hotfix, so that you all will at least have a fully functioning camera while I work on the next evolution of Neutrino.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
I haven't seen any lag with latest GBoard or any other app, but I think I could be kind of "lag tolerant".

Will the rebuilded kernel still be compatible with AOSiP? I really hope so, because I'm very happy with the excellent match with your kernel and that ROM on my PH-1.

This will be great. Thanks in advance.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Yes, while I've never directly supported AOSiP, if it works well for you now it will continue to do so in the future. The end product won't change radically, it's more about keeping the source clean and zeroing in on a pure CAF base.

Truth be told, this kernel boots on stock ROMs, P included. The primary thing preventing it from being used on stock is the WLAN drivers being built into the kernel as opposed to modules. I've been hesitant to mention that because if you try it your WiFi will be broken, so don't do that. I've considered eventually switching to an AnyKernel zip format and fully support cross ROM compatibility. I just don't really care for AnyKernel, and I like being able to eliminate TWRP from the equation. For now, I'm focusing on supporting the ROM that I use personally in the most efficient way possible but anything could happen. I have been feeling the itch to jump over to stock P, this project is the only reason I haven't.
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Hey octobot gonna let you know about my experience with this kernel. I am running the latest los(no root) with the . 135 kernel. First off the kernel is running flawlessly I have no complaints. The under volt has definitely made a difference in idle drains. I have had zero instability issues with the under volt so please keep them. :) so far I have had 1 day 2hrs since last full charge and 2hrs 30mins of SOT and my phone % is 55%. Seriously good stuff I can't wait for the camera fix so my phone is fully functional. Thank you for your work this kernel has made things a lot better for the essential community. Have a good day :
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I'll try and get that camera fix for delphinus up by the end of the weekend, may be a bit of a lull after that until I get everything situated source-wise but it won't be incredibly long and incredibly silent like the bootes -> caelum gap. I've reopened my staging repo for anyone that wants to spectate. Sources have been released for the newest P beta (PPR1.180510.022), fortunately there's not a whole lot in the way of new code that I didn't already have in my upstream CAF base. Stay tuned.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
Eagerly waiting for the camera hotfix version of the kernel.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ryanvakil19:
Flash aicp kernel...download it..rename it boot.img..boot to bootloader and in adb type in fastboot flash boot boot.img..if u want root..patch the boot img in magisk and reflash...problem solved
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
Lmao I know how to flash a boot image and root, and your "solution" is using a completely different kernel. Also, the two latest AICP kernels don't work with non-AICP ROMs, flashing them causes it to boot into a black screen with nothing being displayed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ryanvakil19:
Use the 4.4.136 ...works great for me.. battery life is better too..to be fair...its a viable option if u want the camera working now and then u just switch back as soon as the hotfix is up
[Essential Phone ROMs, Kernels, Recoveries, & Other] Geezerooo:
Use the HMP kernel not the EAS and that won't happen.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
I previously already tried the HMP kernel and the dev of the kernel said that the issues I was facing may have come from the HMP version of the kernel, which us by I tried the EAS instead, only to have the same issue.

---------- Post added at 07:29 AM ---------- Previous post was at 07:27 AM ----------

Which is why I initially posted "Eagerly for the camera hotfix version of the kernel" lol... Both of your posts were wholly unnecessary, as all you did was rehash known information and not contribute anything to the discussion.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
**HOTFIX: (4.4.135-neutrino.delphinus)**

Video recording is not working properly on PH-1 #1

Changelog:

Fix video recording

Full changelog available here.

Sorry for the delay, what little time I've had to work on this project has been focused on rewriting Neutrino source from scratch. To that end, I'm definitely making some progress and I'd like to envision that I'll be able to wrap that up before the week is out. Hopefully this will suffice in the meantime.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gregfink83:
Working great on LOS! Thank you for the update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
Neutrino delphinus hotfix is also working perfectly with latest AOSiP. Thanks a lot, [MENTION=6474612]return.of.octobot[/MENTION].
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Glad to hear that guys, the new bringup is starting to come together nicely. Stay tuned.
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertbarber:
Latest Link for the bringup commits since the one in the last post leads to a 404 https://github.com/0ctobot/neutrino_staging
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
The link for neutrino staging repo included in a post on the previous page is still working: https://xdaforums.com/showpost.php?p=76765343&postcount=272
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
It may have went down for a moment while I was shuffling sh*t around, but everything should be in order now. Had a minor setback in that the latest WLAN drivers from CAF are not playing nice with Lineage. Because of that, and also because Essential has switched from tracking CAF -> AOSP for their WLAN source I have decided to do the same at least for the time being. I've imported the OEM drivers and brought them up to date with android-p-preview-3_r0.2. While I don't particularly love the idea of mixing sources, it really isn't a big deal in the grander scheme of things, and technically AOSP WLAN source is ahead of CAF so, there's that.

This will have virtually zero impact on the end product, except for that you'll have working WiFi. Other than that little caveat, the kernel proper has been brought up from scratch on a pure CAF base and excluding the WiFi problem, I've gotten the new source built and booting with zero issues.
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
So does that mean new release coming soon? :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Pretty soon I'd reckon, yeah. Likely by this coming weekend. I realize I don't have a ton of users but the few regulars I do see have been great both in terms of patience and feedback.

I don't know how many, if any, of you have been following the staging branch but if it looks like I've been doing the same thing over and over again, it's because that's more or less what's happening. I'm very critical about keeping a clean commit history, especially when I'm trying to establish a new base so if I make it to the end of a feature branch and realize I've made a mistake or need to fix something, I'll redo the whole thing as opposed to cluttering things with reverts and minor fixups, it's just in my nature. That being said, I've got all my pieces looking really, really good and at this point all that's left is to assemble the puzzle. I may not be the quickest pull on the trigger, but I try my best to make these updates count.
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Your kernel is awesome man. I will continue to give you feed back during my free time as I work a lot and rely on this phone for daily use. I have been following the staging process and noticed the repetition but had an idea of what you were doing. Also no worries about rushing man we understand it takes time to make a butter kernel. Can't wait for the new release and thank you for all the efforts you put toward this project!
[Essential Phone ROMs, Kernels, Recoveries, & Other] ipdstnger2:
New to this device after being on Shamu for a couple years. Wanted to say thanks for the solid kernel! Unlocked, Rooted, flashed & letting things settle down a bit. Off the charger about 8am & still sitting at 33% battery with moderate use today. Looking forward to seeing more of your work! Thanks again!
[Essential Phone ROMs, Kernels, Recoveries, & Other] pementosequence:
Kernel is great but ever since I installed it my CPU cores are hovering at highest frequency despite no load. Tried all different governor's, did a hard reset, cleared system/app cache and still stuck on this

Any idea?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Thanks for the kind words and patience. A new release is imminent, I just flashed a test build and I am extremely pleased with the results. I've got to re-incorporate some of the 'features' from previous builds, but I've finally reached the point where I'm satisfied with this new base, extremely satisfied. I hope you'll find that the wait has been worth it, in the future I anticipate being a bit quicker with the updates as I'll be continuing to build on the foundation I'm establishing now as opposed to rewriting the kernel from scratch.. Definitely looking forward to sharing this one with you guys.

That's definitely strange and wholely unintended. I can't say that anyone else has ever reported such behavior, and I certainly haven't encountered it myself. As far as the governors go, I wouldn't recommend using anything other than schedutil as it is designed for use with EAS. While the others may function, they are intended for HMP and will not provide the benefits of EAS compatibility. As a matter of fact, I'm going to be removing most of them for the next release. Other than that, may I ask which ROM you're using?
[Essential Phone ROMs, Kernels, Recoveries, & Other] innocentone1:
Yessss patiently waiting for the update :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] soup6020:
Hey Octobot, invisiblek just announced last night on his Discord that he will no longer be making Lineage builds. Do you plan to take over?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I know I've said this a couple times at this point, but I've just pushed the final release source to the main repo, I will be testing this tomorrow and barring any major hiccups will be uploading the build shortly thereafter. After which point, I anticipate that I'll be cranking them out with more consistent regularity.

While I'd be honored to continue the unofficial builds, I believe the reason that this has happened is because Lineage will be officially picking up support for this device in the near future. You can see some pretty telling evidence of this here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] soup6020:
Alright, that makes sense then. Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gregfink83:
That is great news. I love this phone with LOS and your kernel.