yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
[MENTION=5438598]RenderBroken[/MENTION] [MENTION=5060769]Mostafa Wael[/MENTION] clean flashed Vertex then the latest R1. Restored app one by one via TiBu, found the culprit. It was a music app (MusixMatch). Didn't let the CPU to go back down to 307 MHz. I'll get back to you with whatever my results are after this. I need to download a music app first though! :p
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Top Tip: when hunting for hogging apps, open Terminal Emulator and type

top

and see what is the app package name on the top with how much percentage of CPU power it takes up

that will narrow it down a lot :)

Use landscape mode for more convenience when viewing the top list
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
Nice. Thanks for the tip! I didn't know this! Cheers to you! :)
[OnePlus 3 & 3T Cross Device Development] Prattham:
Is there a version for mm?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not any more, I am not supporting MM. Sorry for the inconvenience
[OnePlus 3 & 3T Cross Device Development] Prattham:
I understand that you have stopped the support but i would like to use it so is there a version you can link me to still available?:)

Cheers
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
[MENTION=5438598]RenderBroken[/MENTION] [MENTION=5060769]Mostafa Wael[/MENTION] the kernel is working like it should. The ROM feels smooth. Battery life is great! Keep up the good work. Here are some screenshots!
[OnePlus 3 & 3T Cross Device Development] 7root:
Is that EAS or HMP version?
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
EAS R1
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I try to not delete any old builds so here you go:

https://www.androidfilehost.com/?w=files&flid=134460

Sueweeeet! Glad to hear. Bow you get to use your phone properly! What rom you using? I am using official LOS but will soon be moving to a pure eas rom.
[OnePlus 3 & 3T Cross Device Development] Konskl:
Is there any "PURE" eas rom out? As far as i know even vertex is still not complete or am i wrong in that? In any case ye it seems that the eas kernel is approaching the performance levels of hmp. Think it needs a bit more tuning but it will get there and even further than that! Glad to have you here :)
[OnePlus 3 & 3T Cross Device Development] Prattham:
Does R3 version has eas?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-zenity-resurrection-remix-n-t3551384

Vertex is the other but he is trying to finish up an anoying bug before release.

MY goal in the near future will be to write up a guide for other rom maintainers to easily add in the last bit of EAS changes needed for full support. Most roms support EAS enough that you still get a decent experience but it could be better. That is my goal. Also when adding in the EAS changes, it doesnt effect HMP one bit so I hope they add support just be be cool ;)

No. My OOS-MM kernel does not support EAS. None of my MM kernels do.

I meant to add them for R1 but I cant think of everything lol. It will be added to R2. Thanks for the reminder!
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Note: there were two early builds of primitive EAS support for OOS-M, namely RenderKernel-OP3-OOS-R1-T40-EAS.zip and RenderKernel-OP3-OOS-R1-T46-EAS.zip, but they weren't what you call a RenderKernel experience, since we were missing a lot of necessary changes for EAS ROM-sided and we had a half-working EAS implementation with some people having a lot of random reboots ;)

TL;DR

there were some trial builds but to no avail.
[OnePlus 3 & 3T Cross Device Development] liver20:
Whats is the lastest build for custom rom?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
https://www.androidfilehost.com/?w=files&flid=157049
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Question: why can't I see any folder for the top-app ...? Was going through the thread and referring to this post..

https://xdaforums.com/showpost.php?p=70885986&postcount=507
[OnePlus 3 & 3T Cross Device Development] stryker09:
Because there is a bug somewhere that is preventing the folder from being created at boot... Not sure what's causing it
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Thanks, went through the discussion a few pages back. So is this ROM side issue? I am on Zenith RR. Tried flashing the R1 version seperately..But doesn't help.

Any other solutions?
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
I'm on Vertex 2.0, mate! I had to make EAS work properly for me since I'm testing the difference for a user while using HMP and EAS! I'll be writing stuff up as soon as I'm done testing HMP. I'll be using your Kernel for the comparison and so I would like your permission to let me post it on OnePlus forums? I'll send the write up to you once it's done!

PS: It'll be a different kind of a writeup than what [MENTION=5060769]Mostafa Wael[/MENTION] has written. A little educating and noob friendly for the guys over there! I will of course be linking Mostafa's post there for more info.

Also it'll not be only about HMP vs EAS but more of an overview of the kernel landscape.
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Is Vertex 2.0 for OnePlus 3 only ?
[OnePlus 3 & 3T Cross Device Development] mysky911:
I am using OOS-N_EAS_R2. running on OOS 4.0.3 without any issue.. Not sure why this release no longer exist on download files site. :confused:

Been told OOS is not EAS tuned, but still hoping to get update on OOS 4.0.3 EAS update.:cowboy:
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
Nope! It's unified. I have a 3T
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Awesome and I guess its works best with Render Kernel too :)
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I am actually doing the same thing lol. Trying to make it more noob friendly like my benchmarks article. But i guess there is someone to lift it up my shoulders and i like that!

Feel free to ask me for anything. I am intrigued i have to say.

And sadly i am in the middle of some troubles. One of which is related to my new machine and i have to take it to the shop for debugging. It crashed two times in 12 days - one of which reported a missing keyboard!! so...i am a bit down...

---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------

Coming up next, some information from [MENTION=6745491]joshuous[/MENTION] about alucardsched that should enlighten us greatly :good:

He is a bit occupied but he certainly has something to write :good: :highfive:
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
Yes!

---------- Post added at 02:59 PM ---------- Previous post was at 02:55 PM ----------

I'm pretty sure what you're going to write will be a lot more knowledgeable and I'd love to read that but what I'll be writing can be a good prelogue to yours! :p

I'm very intrigued by alucardshched and would love to read what [MENTION=6745491]joshuous[/MENTION] has to say!

Slowly there'll be more governors for EAS mostly based on schedutil but still, EAS seems like the future!

PS: Hope your machine is back up and flying for us to get some knowledge! :cowboy:
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Well it was not properly synced with OnePlus's latest source drop of OOS 4.0.3 so it was better to be off the shelves for now till Render brings his EAS kernel up to date with OOS 4.0.3 sources. Don't worry the EAS kernel for OOS is not dropped, until he says so. Tho if you really want to see EAS in full attack mode, use LOS based ROMs, and would be more preferable to use one of those who fully support EAS.
[OnePlus 3 & 3T Cross Device Development] Jole7:
VertexOS must be a performance rom very ineteresting! and Render kernel is awesome too.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Its a bug and is fixed in the newest test build I have. I will go ahead and release as LOS-N-EAS-R2 shortly.

I am finishing up my LOS releases then will move back to OOS. ?Glad its working and I appreciate everyone's patience with this matter.

Going to move to OP#3.

Everyone please point users to OP#3 in the future when regarding AlucardSched
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Thanks mate. Looking forward to the new release
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
RK-LOS-N-EAS-R2 is HERE!!!

Things to note:

Fixed "'top-app" not showing for newer LOS based builds

Updated inline with LOS Kernel

Updated WIFI Driver

Download

Changelog:

R2:

f2a97e02 (HEAD -> rk-los-n-eas-master, rk-los-n-eas-r2-t1) qcacld-2.0: Update to LA.UM.5.5.r1-03400- 8x96.0

91dc18d Revert "msm: isp: Add support for VFE resolution limit"

4883754 Merge tag 'LA.UM.5.5.r1-03400-8x96.0' of https://source.codeaurora.org/quic/la/kernel/msm-3. 18 into cm-14.1

602c12c Defconfig: Re-enable CONFIG_MEMCG

f47f1b9 Fix build warning in kernel/cpuset.c
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
RK-LOS-N-HMP-R2 is HERE!!!

Things to note:

Updated inline with LOS Kernel

Updated WIFI

ETC

Download

Changelog:

R2:

8ff591a (rk-los-n-hmp-r1-t1) qcacld-2.0: Update to LA.UM.5.5.r1-03400-8x96.0

daa389b Revert "msm: isp: Add support for VFE resolution limit"

41c444f Merge tag 'LA.UM.5.5.r1-03400-8x96.0' of https://source.codeaurora.org/quic/la/kernel/msm-3.18 into cm-14.1

ae304ee Defconfig: Re-enable CONFIG_MEMCG
[OnePlus 3 & 3T Cross Device Development] JagravNaik:
Which one is best for battery? EAS or HMP?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Try it out and report back :)
[OnePlus 3 & 3T Cross Device Development] nadejo:
How can we change thermal values they dont seem to work. Thanks
[OnePlus 3 & 3T Cross Device Development] drive2droad:
As per the developer it is the EAS version which s more battery friendly .
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
You try and tell us. Nothing is static. All depends on the usage patterns of the user
[OnePlus 3 & 3T Cross Device Development] saberzaid:
What's the deffrent between both versions?
[OnePlus 3 & 3T Cross Device Development] tmimaesk:
First one is EAS

Second one is HMP
[OnePlus 3 & 3T Cross Device Development] saberzaid:
I know but what is EAS and HMP mean
[OnePlus 3 & 3T Cross Device Development] tmimaesk:
Go read post #2
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not to single anyone out but there have been alot of questions lately that could have been easily answered with a simple search. I try to be the most approachable dev on XDA but I need something for the users as well and that is to just search before asking.

Kind Regards,

Render
[OnePlus 3 & 3T Cross Device Development] BolintsMiki:
Speaking of this, I have been searching a lot, but I can't find your OOS-N-EAS-R2 build. Also does it have the Oxygen 4.0.3 updates? If not, when is a new build coming?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Its super hidden. I will add a link to my OOS stuff. Just not happy with those builds and no its not updated. I am trying to finish up my EAS work. I am working with a group of Devs to bring a true EAS experience to the OP3. We are so close right now that I don't want to change horses just yet. Once we do get it, I will move to rebase both my OOS builds.

OOS Builds
[OnePlus 3 & 3T Cross Device Development] BolintsMiki:
Yeah, I have found that folder, but the R2 build is not in there.

Anyways, so you're saying I should wait a bit for a new kernel (or maybe ROM). That brought up a question in my mind: is it going to have OOS camera quality. (Might be a stupid question, since as far as I understand from your reply, it is OOS-based.)

Anyways, I'm waiting for it, keep up the good work.
[OnePlus 3 & 3T Cross Device Development] Durrz:
Camera is rom reliant, not kernel :)
[OnePlus 3 & 3T Cross Device Development] liver20:
This kernel is awesome in dirty unicorns!!! And now with sweep2sleep. Thanks [MENTION=5438598]RenderBroken[/MENTION]
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
[MENTION=5060769]Mostafa Wael[/MENTION] [MENTION=5438598]RenderBroken[/MENTION] flashed PhoenixAEX and your R2 kernel. The little cluster not going to 307mhz problem came back.

Tried to look for a power hungry app, couldn't find it. (Looked for it using terminal emulator) removed the Pixel Launcher as that was at the top of the 'top' list in terminal emulator.

Finally I changed the governor from schedutil to sched and the CPU goes back down to 307mhz and stays there! Weird problem!

Update : after going onto sched, active battery drain right now is 11.01℅/hr, previously it was more than 13/hr.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for the report!
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Sched-DVFS active drain rate depends more on the usage pattern. If your usage is more of a medium mixed usage, then yea sched-DVFS can be more efficient. However, in heavier usage schedutil is more efficient and performs better.

As for your issue with active idling (that 307 thingy), i find it quite odd actually and it's definitely not happening here at my end.
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
I know it's too weird! No one else has this problem!

Also, I'm a heavy mixed user! I play UFC (mostly), Modern Combat 5 (rarely), Alto (Rarely), WhatsApp, Telegram, YouTube, etc. The only reason I'm on sched is because it stays on 307. It's too weird! I would've met you had we been in close proximity to learn more about this problem!! :confused:
[OnePlus 3 & 3T Cross Device Development] ShiShTuBaBu:
Will this kernel work on hydrogen os based rom?
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
You can try the OOS based kernel but I don't think it'll work. No one uses hydrogenOS much so try and let us know!
[OnePlus 3 & 3T Cross Device Development] madsponge26:
Issues in stock ROM 7.1.1
[OnePlus 3 & 3T Cross Device Development] B3501:
7.1.1 stock OOS kernel sources haven't been released yet and they won't be because it's a beta. You'll have to wait until the final release and sources are out before you get a working kernel for 7.1.1 OOS.
[OnePlus 3 & 3T Cross Device Development] Remorcer:
I'll just leave this here.
[OnePlus 3 & 3T Cross Device Development] B3501:
That's not from 7.1.1 OOS sources though, is it?
[OnePlus 3 & 3T Cross Device Development] Remorcer:
No, since they aren't released yet. You can ask eng.stk about his magic.
[OnePlus 3 & 3T Cross Device Development] scrbenni:
EAS lags more on phoenix AEX. HMP very smoooth!
[OnePlus 3 & 3T Cross Device Development] hooliganx:
feel same thing.

what is HMP? ? Im new on OP3T world.
[OnePlus 3 & 3T Cross Device Development] scrbenni:
Read second Post ;)
[OnePlus 3 & 3T Cross Device Development] bassgenerator:
global:

http://stackoverflow.com/questions/...sing-hmp-scheduling-implemented-in-linux-kern
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Because I have had alot of questions regarding this, I wanted to let you guys know whats going on. I am going to be releasing R3 builds for LOS-(HMP/EAS) this weekend. Once done, I will be taking everything I have built with my LOS kernels to OOS. Initial builds should be out soon for OOS as well. I look forward to the EAS version of OOS. The things I have been able to do for LOS should work well enough for OOS even without having full EAS support. After the next OOS-N-EAS build and how it goes, it will dictate whether or not I continue supporting it. Thanks guys for your patience!

Kind Regards,

Render
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
I understand all the benefits of eas and read the whole PDF about it. One thing I don't understand is, why does eas suffer in rendering and latency in scrolling? I've tried analysing from many aspects but I'm not able to. At least, why is this problem not there with the pixel which uses the same EAS? Ours has the same hardware configuration as pixel. LOS gives freedom, so I don't think some parts of EAS miss. What is the reason for this, then?
[OnePlus 3 & 3T Cross Device Development] joshuous:
The main reason is the lack of touch boost in EAS governors. EAS governors rely a lot on CPU load and utilisation to calculate their next frequency. The issue is that they set frequencies according to the present load instead of anticipating future load. Using the present load is battery efficient but not suitable for situations like scrolling and flinging because the governor will always be playing catch up.

Compare this with Interactive, which has a form of touch boost capability. It is very tunable, thus allowing us to define how frequencies should behave. Therefore we can set the frequencies to spike to a large value and remain there for a longer period of time if we want. That would be very good for scrolling. However it is not power efficient for other tasks, and you will almost always see a lot more time spent on higher frequencies on Interactive. Interactive will always be better for performance, if tuned correctly.

So now on EAS governors we have a few possible solutions:

1. We can increase the schedtune.boost for top-app and maybe foreground tasks so that frequencies will spike faster, and give us better scroll performance. However, the boost will apply for all actions besides scrolling, thereby increasing battery drain unnecessarily for other actions.

2. Or we can leave the EAS governor as it is, and implement another mechanism to force frequencies to spike under specific events only (such as flings and app launches), thereby replicating touch boost. That would enable us to be performance focused for scrolls and battery efficient for other actions. This is where we play with the Power HAL... I wholeheartedly believe that this is the ROM-side solution that complements and completes the EAS implementation. [MENTION=5438598]RenderBroken[/MENTION] and several other VertexOS testers have gotten to play with it over the past week. Can't wait to let you guys give VertexOS a shot when it's officially out.
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
I already analysed the touch boost part but i didn't understand how the pixel didn't suffer. That's why I asked. Thank you so much for your very informative reply! And check your pm :)
[OnePlus 3 & 3T Cross Device Development] Mayank7795:
[MENTION=6745491]joshuous[/MENTION] Eagerly waiting for VertexOS. The Slack channel is all about it.. :D :D
[OnePlus 3 & 3T Cross Device Development] CroW_D:
I can say i had this problem tho little cluster wasn't going down always stays between 1036 and 15800 whatever.
[OnePlus 3 & 3T Cross Device Development] B3501:
I thought this was a bug with the base 4.0.x OOS Roms? It's reported all over the OP forums. The CPU would spike and stick to 80-90%. It seems solved with the 7. 1.1 beta they released.
[OnePlus 3 & 3T Cross Device Development] JagravNaik:
Link to Slack channel please? Thank you!
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Will VertexOS come with Render Kernel integrated within the rom itself ?
[OnePlus 3 & 3T Cross Device Development] kentexcitebot:
No, it uses the Zenith kernel. Renderkernel is fully compatible though.
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Should be worth the wait :)
[OnePlus 3 & 3T Cross Device Development] 7root:
Does this kernel have the kexec-hardboot patch for MultiROM?
[OnePlus 3 & 3T Cross Device Development] comediiian:
what's that? ?
[OnePlus 3 & 3T Cross Device Development] 7root:
That's a patch that allows to boot any kernel without changing boot partition, which is required for MultiROM to work. MultiROM is a mod that allows us to boot several ROMs. I want to try it out, but therefore I need to know if the kexec-hardboot-patch is merged.

More infos here ==> https://xdaforums.com/showthread.php?t=2104706
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
No, I dont think I do. I will look into it.
[OnePlus 3 & 3T Cross Device Development] comediiian:
ah ok.. never had problems with multirom and custom kernels before.

Sians build with renders newest kernel is the first, which get me those issues after boot.

but never heard before of that patch, thx mate :)
[OnePlus 3 & 3T Cross Device Development] joshuous:
The multirom patch shouldn't be required, and I recall that it creates a security vulnerability. Multirom can already boot custom Roms without the kexec patch.
[OnePlus 3 & 3T Cross Device Development] Pritster5:
[MENTION=6745491]joshuous[/MENTION] How's the rebase coming along? Any ETA on the release?
[OnePlus 3 & 3T Cross Device Development] joshuous:
It's complete. ETA would be next week at the earliest.
[OnePlus 3 & 3T Cross Device Development] Pritster5:
That's awesome!
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
[MENTION=5438598]RenderBroken[/MENTION] Would you consider adding the blu_active governor. I absolutely love what you have done, but I'm.a huge fan of the governor. If not, I'll still use the kernel because it's amazing
[OnePlus 3 & 3T Cross Device Development] kalapapa:
Blu_active is just a tweaked variant of interactive governor

So just take a screenshot of the tunables and use them on render hmp kennel
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Yes and no. I understand what you mean as he does base it off the up to date CAF interactive governor sources, but he's added quite a few features, such as load prediction, and fastlane which makes a huge difference.
[OnePlus 3 & 3T Cross Device Development] 7root:
So EAS requires a compatible rom to work. What changes do I need to get it work on my own ROM? Could anyone kindly suggest me where I find the commits or whatever it takes?
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
I tagged [MENTION=5438598]RenderBroken[/MENTION] so he can point out for you..

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] stryker09:
If your code base is latest LOS or AOSP then there isn't anything needed to add for EAS support. On the tweaks side however.... That's a different story
[OnePlus 3 & 3T Cross Device Development] 7root:
I am based on OOS, so I guess I'll need the commits...
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
I'm using this ROM with the latest Render Kernel (HMP) and it breaks camera (crashes on launch)

https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-citrus-caf-t3505010

The ROM is using the OOS 7.1.1 camera blobs (maybe that's the problem?).

Is there someone else who experienced this issue, maybe even on an another ROM?
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Most custom kernels don't work yet on the 7.1.1 blobs.. I think its cuz los hasn't merged the required stuff yet...

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] Acxjet:
Even on a LOS based rom you need eas commits to fully implement it. Also the reason why Zenity RR, VertexOS and PhoenixAOSP are the compatible EAS rom's
[OnePlus 3 & 3T Cross Device Development] stryker09:
If you look at upstream AOSP those commits are already there, and with the latest LOS rebase, CAF changes have also been merged. It's just the device tree tweaks which need to enable SCHEDBOOST and the supporting kernel is what is left. I've built them many times over already.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
I hope there is going to be an update soon (not asking for ETA). The ROM is absolutely flying with this Kernel while keeping the phone cool. A working camera would make it perfect.
[OnePlus 3 & 3T Cross Device Development] 7root:
As I said I am based on OOS. So I will probably need all of the commits and tweaks
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I agree

No, I will not be adding in blu_active. Interactive alread has load_prediction. Fastlane is really just a corner case and is not needed if interactive is tuned right.

I am working with [MENTION=6745491]joshuous[/MENTION] with implementing EAS properly for the OP3. When we are done and finalise all the changes needed, we will be rebasing all EAS commits so that other rom maintainers can easily pull in the needed changes.

Weird, couldnt say for sure but I think the other users are correct in that its just not compatible atm.