yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Just a heads up, I'll be rolling out an update in much quicker succession than I typically would in order to address some stability issues which have been brought to my attention, i.e. lockups and subsequent reboots. Seems as though the frequency and severity varies among users, but I imagine some of you have encountered similar behavior despite the lack of reports. Regardless, I'm aiming to have maintenance update out by the end of the week. I'll try and cram in as many goodies as I can between now and then to make it at least somewhat significant.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Just so everyone's aware, there's a new build on git. I'll update this thread later on when I've got a minute, but I would highly recommend updating.
[Essential Phone ROMs, Kernels, Recoveries, & Other] raoulbhatia:
Thanks [MENTION=6474612]return.of.octobot[/MENTION] - I already flashed it and will let you knke if I still see the sporadic reboots.

I am very grateful for your kernel! The stock lineage one gave me a lot of trouble...
[Essential Phone ROMs, Kernels, Recoveries, & Other] 冰糖葫芦娃:
[MENTION=6474612]return.of.octobot[/MENTION]

I installed the 167 version of the kernel, in the phone reboot, stuck on the startup page, also can not boot to recovery, and finally had to go back to the official kernel, and then brush into the 161 version of the kernel, 161 kernel does not seem to have this problem.

Thanks to the developer's hard work ~

--From Bing Translator--
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Not sure what to tell you on that one, I'm fairly confident in the recent build, and everyone else that's used it thus far have only affirmed that the reboot issues that were present on Hercules have been corrected. As far as the phone not booting, and being unable to boot into recovery, this is the first time I've heard anything of the sort about any build I've ever released. Makes me think there's something larger at play here, but regardless there's not a whole lot I can do based on your reporting with no subsequent logs. I'm sorry you had this experience and you are of course free to use whatever you see fit, but I'd hope that this anecdote does not discourage others as I built and tested this lastest release on stock, and all of these builds are tested amongst the telegram group on various ROMs before they hit xda. That's not to say things can't slip through the cracks, but I would have never released something that exhibited such extreme behavior.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
??

Kernel review
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
Kernel's working fine for me, no problems at all.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hx3:
Yep, latest kernel is working just fine on the HavocOS GSI ROM. Though I will be switching to a different Pie ROM shortly as HavocOS is pretty outdated now and the team is going on hiatus for a while.

Thank you for all or your hard work, as it's greatly appreciated! I'll get a donation sent out shortly after the holidays.
[Essential Phone ROMs, Kernels, Recoveries, & Other] raoulbhatia:
I didn't encounter any reboots until now ??. I recall a few times the device might have reacted a little slow when switching on the screen - nothing that I consider a serious issue though.

Great work - please keep it up. As said, your kernel made LineageOS useable again! ✌?
[Essential Phone ROMs, Kernels, Recoveries, & Other] falleny:
best kernel i tried so far...thanks...hope op don't give it up...
[Essential Phone ROMs, Kernels, Recoveries, & Other] shekinahsmoke:
:eek:

Hey so I used Ex Kernel Manager to flash on Res Remix. Im currently on the booting screen. Something didnt work right.

How long should I wait.

Edit: TWRP flashed my backup
[Essential Phone ROMs, Kernels, Recoveries, & Other] MrPhilo:
Any reason why this kernel doesn't get updated anymore?
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
The dev DESTROYED his mata and now own a OP6T
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Is aosip eas???
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Yes
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bobbaloo:
Bah!
[Essential Phone ROMs, Kernels, Recoveries, & Other] initguru:
Yes, I have less than 1 hour of deep sleep overnight.

When using BBS, both kernel and userspace wakelocks.

I can use Greenify but it cannot block kernel wakelocks such as IPA_WS or wcnss_filter_lock.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
hmm strange, I'll have to check it tonight.. on the other hand it seems like the changelog has been updated so it won't take too long until we see an update. Maybe try that one out and see if it make a difference.
[Essential Phone ROMs, Kernels, Recoveries, & Other] initguru:
Sure I can wait but wanna see if that is possible, so I git cloned this upstream source and patched the source by the commit I mentioned.

Compiled without error, I'm going to flash a new kernel soon and test if it works or not.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Sounds good. Let us know the outcome. :good:
[Essential Phone ROMs, Kernels, Recoveries, & Other] initguru:
Seems like blocking wakelock feature is working.

I will check my phone can be put into deep sleep overnight!
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Awesome!! Are you using Bluetooth by any chance?
[Essential Phone ROMs, Kernels, Recoveries, & Other] initguru:
Yes, I have been using Mi Band quite long and I remember you said enabling bluetooth causes wcnss_filter_lock. (You are right)

By using the wakelock blocker it seems to effectively block specified wakelocks so the kernel wakelock issue is no more problem.

Now I have to catch why I still have a deep sleep issue.. I ran Google Battery Historian and here is a screenshot. CPU has been running overnight.
[Essential Phone ROMs, Kernels, Recoveries, & Other] thehappydinoa:
Hi all, I am very interested in using LineageOS, but I still want to be able to use my 360 cam. Has anyone had negative or positive results with one?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Wrong thread.
[Essential Phone ROMs, Kernels, Recoveries, & Other] initguru:
I have been using custom compiled 4.4.121 kernel with wakelock blocker for two days and feeling that overall responsiveness and performance are much better. (still have the deep sleep issue though)

I hope op will give us an update soon.

Furthermore we have one more option now, the official 8.1 is out. I heard that the kernel version is 4.4.120 which is the same as this upstream kernel.

I will give it another shot when I have a chance.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nathanchance:
It's close, 4.4.121. It's a pretty amazing feat, it's the most up to date device I know of.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
You're kind of my inspiration, js.

Annndd on an unrelated note, I've updated the OP with download links for 4.4.121. Apologize for the slight delay, Bionic Beaver played a few tricks on my build environment which took me some time to sort out, but it seems as though we're back in business.

Because you've all been such patient boys and girls, I've also decided to take things a step further with these builds and update the compiler to Clang 6.0.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
No need to apologise. There are many who are grateful for the work you do here and bringing us up to speed. Thank you very!!! :o
[Essential Phone ROMs, Kernels, Recoveries, & Other] initguru:
[MENTION=6474612]return.of.octobot[/MENTION]

Thanks for the great work, I have been using your kernel and it is just wonderful.

I am very interested in switching gcc to clang and have tried to apply patchset for clang but failed compiling.

Would you give me some guide please?
[Essential Phone ROMs, Kernels, Recoveries, & Other] PixelatedVision:
i cant get safteynet to pass, even followed [MENTION=1339445]Arju[/MENTION] step process directly
[Essential Phone ROMs, Kernels, Recoveries, & Other] lasset:
Thanks for your kernel. After installes Linage 15.1 for third times, complemented with your kernel I got a solution very much in my taste. Snappy, and very well performance. Thanks!

.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
I've been flashing magisk through patched boot image throughout the whole weekend and I'm passing safetynet. Are you on LOS 15.1? Walk me through how exactly you've been going about trying to pass safetynet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] PixelatedVision:
about 10 minutes after I posted that, I rebooted and then it started passing safteynet. Just on first boot after flashing the patched image it didnt. Now it does, maybe it was just drunk from St. Patties day idk hahaha
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
It certainly can be a bit of a headache, and something that I'm in the process of learning myself. Then, like GCC, code that compiles with clang 5 will not necessarily compile with clang 6 so it becomes an on going battle. I may be able to provide you with more in-depth information in the future, but I'm far from an expert on the subject myself. For the time being, have a look at this branch. I'm currently in the middle of trying to rebase the linux-stable source I've been using on top of the new 8.1 source from Essential. I've been trying to break each step of the way into it's own branch for reference, and that one in particular contains the patch set needed to compile the stock Essential source with Lineage's default clang toolchain. Hopefully that will at least get you going in the right direction.

That being said, looks like the cat's out of the bag. There may be a minor delay in releases while I continue to sort this project out, but I am hoping to repurpose this thread to release builds from my own "custom" source. This won't be radically different from what you've been getting and will still be largely based on linux-stable code, like I said, as of right now I'm just attempting to rebase their source on top of the latest from Essential. Things seem to be progressing quite well, so I'll certainly keep everyone informed of my successes and/or failures.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Edit: understand your statement now. Awesome to see you continue.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
That's not true. Once your kernel compiles with clang 5, it will compile fine with 6 and 7 without major issues. If you have issues compiling kernel let me know, I'll help you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
I would debate that statement based on my own experience, for example, after my initial rebase of the Lineage kernel on OPM1.180104.092 source (including the clang compile patchset I referenced earlier) I was unable to build this branch with Clang 6 due to -fstack-protector-strong errors if I'm remembering correctly, I reverted to Lineage's default Clang 5 and it built fine. It was only after I merged in code from linux-stable (here) that I was able to build with Clang 6 again. So, unless that was a fluke, I beg to differ.

It's really neither here nor there though, ultimately I accomplished my goal source-wise, and the end product does build with Clang 6. The errors I encountered occurred during the middle of my bringup, but by the time it was said and done all was well. That's why I said what I said though. Haven't attempted to use Clang 7, but I will be moving to it as soon as it's officially supported by AOSP. Which, judging by the latest commit on master, should be fairly soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Didn't see you're original comment pre-edit, but rest assured, I won't be stopping these builds anytime soon. Like I said, I'm just in the process of moving from pure android-linux-stable source to my own personal source which is essentially just a rebase of linux-stable on top of the newest source drop from the stock 8.1 official release (OPM1.180104.092).

Things won't be radically different on your end, I still plan on staying very close to stock using the most current sources available for this device. It'll just give me a little more freedom to respond to issues (to the best of my ability) and exercise more control over the code in general. At this point, I'm just wrapping up the testing phase so expect a new release within the next day or two max.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Fstack protector errors appear for me only when incompatible flags are found in makefile or path to clang is specified incorrectly.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
***4.4.122 has been uploaded, please refer to revised OP for information on new codebase***

As this is the maiden voyage for new builds using my personal source repository, I'm interested to hear any and all feedback that you guys may have. I don't expect there to be any radical differences as the general concept is much the same as it always has been and the end product is still largely based on linux-stable. I expect that these builds will perform just as well as they always have, if not better. This is still very much a stock kernel, and I don't plan on making any major departures from that design philosophy. That being said, I may or may not have included a small addition to the I/O scheduling department. I'll let you all figure out what that could be. :good:
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
First thing I noticed right away...

3.20 build of LOS takes a long while to get Wifi online on boot or reboot...this kernel fires right up. IIRC 3/20 is the first PH1 Unofficial LOS build with the 4.4.120 kernel.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Glad to hear that! You're right, I did notice some janky WiFi behavior during the bringup when I was initially using the drivers straight from Essential's source. At one point I had to manually enable WiFi on each boot to get it rolling, not sure how invisiblek ultimately handled this I don't see that he's uploaded his 120 source to git yet but I brought in some WLAN patches from CAF that seemed to remedy the situation.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
I have the same experience as the user above your comment said. I'm also on the 3.20 LOS build and wifi connects quickly after reboot when on your latest build. Will keep on testing it. Thank you for this build.
[Essential Phone ROMs, Kernels, Recoveries, & Other] BakedTator:
Just wanted to say...keep these kernels up man...they run great on both Los and rr rom.
[Essential Phone ROMs, Kernels, Recoveries, & Other] initguru:
Thank you so much.

I have looked into some commits and realized that you and other contributers have made great effort to get this buildable.

It is better for me to just take an advantage of your awesome work. ;)

Cheer up guys!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Lol, mainline is already on 4.4.123, those guys are working fast.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Geez I literally just flashed this one haha
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Thanks for confirming this, I was going to mention now that RR is available for the PH-1 that these builds would likely be compatible as that ROM is largely based on Lineage.

I'm working on the 4.4.123 release as we speak, looking to get it out by tomorrow at the latest. I'm hoping to include a few new additions to this build, I still plan on keeping it pretty minimalistic as far as features go but I've got a few things in mind that I think would be more beneficial than bloat. I imagine some of you guys might appreciate KCAL, yeah? ;)

It's almost getting to the point where I might have to start thinking of a real name for this project..
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Neat!

FYI...the latest LOS build 3/22, reverted to the old 4.4.78 kernel. You *.122 kernel works fine tho
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Thanks for all your time :)

New version seems to be sleeping like a baby, fyi
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Hmm, I did not know that. I try and test these on the latest Lineage releases but I haven't had time to update the to today's yet. Not sure why that decision was made, but as long as these are running well for you I'm gonna keep doing what I'm doing.

Oh awesome! You were the one with the BT deep sleep issue right? I'm actually really glad to hear that, kind of affirms that I made the right decision taking this source into my own hands.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
I suspect the revert on LOS is a fix for the slow-to-start-WiFi.

I've seen the BT associated sleep bug too....one thing I've found hitherto is that it takes 24+ hours of uptime to set in. I'll see if it does it tomorrow at work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
***OP Updated, 4.4.123 release uploaded***

In addition to business as usual, you'll find that this release contains a few small perks. Let's say that Maple has been 'officially' added to the I/O roster, in addition I've enabled and included broader support for cpu utilization of power efficient workqueues, KCAL gamma control has been added, and I've enabled and set westwood as our default TCP congestion algorithm. These builds are now being compiled with the latest Google Clang 7.0 toolchain from AOSP.

In case AFH is acting a fool today, here's a temporary Drive mirror.

Complete changelog can be viewed here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
No mirrors found so can't download.

By the way, been using Bluetooth all day, still seems to deep sleep :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Probably just some jankiness of AFH's end, I'm seeing a mirror now. Have another go and if it's still down I'll put up a mirror on Drive.

Here you go, just in case.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Excellent. I knew there was a reason I took my Surface with its ADB/Fastboot interface to work today :highfive:
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
This is awesome! Great to be able to live on the bleeding edge. A question, you stated that it's officially supported by aosp. What do you mean?.. do you mean that it works on aosp ROMs too or?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
No , no I was referring specifically to Clang 7 and Google adding support for it to the AOSP source. I'm essentially just saying that I'm using the newest clang toolchain from Google. Should probably reword that so as not to create confusion.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Arju:
Oh ok, got it. You probably worded it right. I'm just a noob haha.
[Essential Phone ROMs, Kernels, Recoveries, & Other] deepu458:
Hi Dev [MENTION=6474612]return.of.octobot[/MENTION],

Just wanted to ask u, is there any chance of building a kernel for stock rom?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Is there any chance? Yeah, there's a chance but to be real it's unlikely to be something I'm going to commit to in near future if at all. When 8.1 got it's official release I strongly considered whether I should go back to stock or stick with Lineage. I guess it's pretty clear what my decision was. There's a good chance that with a little effort this kernel would boot on stock if it were paired with the correct ramdisk, it'd just create some headaches that I'm not willing to deal with at this point. First and foremost being that I wouldn't be able to test it, and would have to rely exclusively on others for feedback. I've got a decent amount of goals in mind for this kernel as it is before I get bored enough to take on maintenance of another variant that I'm not even going to use. No offense intended, I just enjoy working with kernel source as a hobby and doing my own personal builds for the software I'm using. I'm happy to put them out there for the benefit of others, but for the time being I can't see myself working on something that I'm not going to benefit from.

That being said, it's not out of the realm of possibility, but it's also not something I can make any promises in regard to.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Dr.Now:
are there any recommendations for the settings using Kernel Auditor?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nomesrjp:
Hey guys,

I've been using LOS 20180322 with kernel 4.4.122 and the system has been entering deep sleeping regularly (I saw 2% drop overnight). I've since moved to kernel 4.4.123 and now it deep sleeps very little, if at all (sits unused at 300Mhz). Has anyone else experiencing similar issues?

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Not saying you're wrong, I'd just ask that perhaps you observe this at least until tomorrow considering I just put out that release this afternoon and let me know if this persists. I've got others telling me it sleeps quite well and to be honest I haven't kept tabs on it up to this point so I'll take it under observation myself. If anyone else cares to report whether 4.4.123 is or is not sleeping properly I'm happy to take that into consideration.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Try a reboot. Honestly even stock LOS I get no deep sleep after about 24 hours of uptime
[Essential Phone ROMs, Kernels, Recoveries, & Other] duminduweera:
Love the KCAL support, any settings to make the screen more saturated?
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
Yeah, obviously I haven't ran a thorough test by any means but I just let my phone idle for about 30 minutes and it went into deep sleep for 12, so I'm not sure that I see a problem here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] return.of.octobot:
At this point I'm not sure how much there is to tune. The kernel uses EAS and the schedutil governor by default and because of this I don't believe governor tunables are as beneficial as they perhaps once we're, if I thought there was a better configuration I would have coded it at way, but there's undoubtedly people out there who are more knowledgeable than I so if there's any information out there in regard to optimizing cpu scheduler tuning, I'd be interested to see it.

I personally am a fan of the maple I/O scheduler, which is why I included it. Would've hardcoded it as default but Lineage includes an init script that forces BFQ on boot. If you want to try it out, you'll have to use something like KA, EX, or your kernel manager of choice. I typically like to handle any additional kernel tuning with magisk boot scripts and/or init.d, but it seems Lineage's native BFQ init is overriding these, so short of manually removing the file @ etc/init/lineage-iosched.rc it looks like you'll need an app to change schedulers.

You can of course also tune KCAL to fit your preferences, I'm just not enough of a gamma guru to be able to provide recommendations in that department, but I imagine a quick search will return plenty of results of various user sharing their preferred profiles.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
I just checked and have 5.9% awake screen off time in better battery stats, for the record that's the lowest I've had on this phone :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] nomesrjp:
No worries, appreciate the response! Let me go though another 24/48 hours and I'll report back.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Dr.Now:
[MENTION=6474612]return.of.octobot[/MENTION]: thanks for your feedback.