yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not sure if it works on RR that was linked above. I haven't tried. I do know that my LOE-EAS kernel build works on stock LOS without issues. At least, I couldn't find any. The only problem was that I was using the newest LOS kernel source on the old Rom source. Still waiting for official LOS Rom to drop and cant test that.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Well with my last Test Build on LOS. It was gone completely. That's the kind of lag that drives me nuts.
[OnePlus 3 & 3T Cross Device Development] fcisco13:
What can be causing it on OOS then?
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
I have not tried your kernel direct with that rom that I linked. however the built in kernel is already EAS enabled.
[OnePlus 3 & 3T Cross Device Development] stryker09:
[MENTION=5438598]RenderBroken[/MENTION] was just wondering if there were any specific commits you were referring to about getting the needed EAS parts to work on the ROM side?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Hard to say. Once I a done with the LOS bringup I will take my findings there and apply them back to OOS.

Here is an awesome PDF you can look through. It links the specific commits needed and gives some amazing information.

EAS PDF
[OnePlus 3 & 3T Cross Device Development] stryker09:
Thanks for that, I'll go over the PDF :)

side note - the other ROM which has EAS support doesn't really have its sources pushed, so I can't really find the commits that he pulled in to get EAS support on the ROM side, the OP just uses the RR github as the source, hence my question
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
OOS has always had that for me in the MM days, has been a bit minimised with Nougat but they are still there even with stock kernel. LOS has always been smoother and has less scrolling lag. Even typing on LOS is better than on OOS.
[OnePlus 3 & 3T Cross Device Development] stryker09:
[MENTION=5438598]RenderBroken[/MENTION] so I managed to put together a clean LOS build + the (8?) AOSP commits for EAS + your kernel, used schedutil and some settings posted by [MENTION=5060769]Mostafa Wael[/MENTION] hopefully i did everything right and this will work? I like to learn how to put things together just for my own knowledge and this has been fun!

update: im seeing some jank quite considerably so maybe I did something wrong with the commits (or maybe i just need to let it settle down a little), i just used your kernel repo directly to build, was there anything else that was needed?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Amazing work :good:
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Amazing work RenderBroken! One question though, You said you included the ROW scheduler in this kernel but I can't find it using EXKM or Kernel Auditor. Was it removed?
[OnePlus 3 & 3T Cross Device Development] vinax89:
I have also noticed this. Optimizations are easily introduced in LOS (per dev style and liking), but that's different in OOS where they prioritize stability(you wouldn't want to anger your ~10+million OP3 users (rough estimate) on stability issues do you?) over optimizations with risks. Also some optimizations don't follow standards and risk precision and accuracy over speed.

On another note, Nebula Kernel by Eliminater74 has added the EAS code too and used the same experimental branch I have referenced in my previous post. It seems devs from other devices have looked upon EAS as a new standard for intelligent and energy efficient power management.
[OnePlus 3 & 3T Cross Device Development] stryker09:
Small thing to note: I had to export USE_SCHEDBOOST when building the ROM as mentioned in the PDF at the end of page 28
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Render is the genesis.:good:

---------- Post added at 06:19 PM ---------- Previous post was at 06:09 PM ----------

And I can tell you that the EAS implementation here is much more sane and seamless, and will get better with LOS support :good:
[OnePlus 3 & 3T Cross Device Development] cba1986:
No matter what i do. i cannot solved the high cpu usage

What i tried:;

reflash ROM + super su + kernel

reflash ROM + kernel + super su

reflash ROM + stock kernel + super su + kernel

reflash ROM + stock kernel + kernel + super su

all end up with high CPU. a shame really
[OnePlus 3 & 3T Cross Device Development] 5nickers:
you need to set selinux to permissive. There is an app for that: https://www.androidfilehost.com/?fid=745425885120703510 That fixed it for me.

Flash this and set it to permissive. It should do it for you everytime you reboot.
[OnePlus 3 & 3T Cross Device Development] Matokov:
Which ROM are you using? Try in Terminal app write(must be rooted)

su

setenforce 0

After this close app and check cpu speed...
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
LOS-N-R1-T10-EAS is HERE!!!

I have a special treat for LOS based rom users. I have been working on EAS for you guys as well and will be moving to LOS full time for awhile. I have a Test build that is essentially just Stock LOS with EAS added in. Please Test and let me know what you guys think. I believe it to run much better than Stock OOS-EAS. I have also been working with some ppl to get the rest of the needed Romside EAS commits to be added in. I look forward to the future of my OP3 kernel.

Download:

LOS-N-R1-T10-EAS

Please note that this is ONLY for LOS based roms. Also test and report back if you can, it would be much obliged!

Kind Regards,

Render
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
Hey [MENTION=5438598]RenderBroken[/MENTION] any specific reason you are switching to Los? I have been thinking about it too recently but it seems they are still very young and having a ton of growing pains. I read you previous post about micro lags and stutters is that it? Thanks for all your hard work
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
If I were you, I would switch to LOS as well for two reasons (talking in general here):

1- LOS works much better with Renderkernel's EAS variant since more control over the EAS ROM source is gained and LOS is generally more manageable. OOS ROM is still closed sourced after all, this is something we cannot change and won't change in the near future even. So with LOS, devs can incorporate some more essential ROM-sided commits that they can't do so with OOS.

2- OnePlus has issued an update on their Github prepping for their release of the promised Cam blob(s) - which increases camera quality for non-OOS based ROMs at the cost of some speed. So now LOS and all other custom ROMs can have OOS-like picture quality and that will render the camera more useful and functional. So if the camera performance was what holds you back to OOS, cheer up and prep yourself for a switch to LOS soon :)

Now I know LOS has been a bit chaotic recently. The devs are almost taking steroids to keep up with their foul moves, but LOS is slowly but surely being tamed now.

P.S. EAS on LOS is much much much smoother than on OOS-N. And that kinda confirms one thing in an indirect way; OnePlus's source drop was missing some essential EAS "bits" in the framework. That was a hunch me and [MENTION=5438598]RenderBroken[/MENTION] had once the OOS-N-EAS build has been available here. However, we must consider the fact that in OOS, we are using a weird setup: CAF's ROM source + Google's kernel source, so maybe that could have attributed to the flaky performance of EAS.

-TDK
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Mainly, I know I will not be able to reach the full potential of EAS with Stock OOS. Not yet at least and not without a ton more work. I was waiting to jump to LOS till after the Kernel rebase and that is now done. I have to say that I have really enjoyed my LOS experience lately. I have had no issues with bugs either. Everything just works and works well. With that said, LOS has merged in a lot of the same EAS related commits google has and it makes it easier to build EAS kernels for as a side effect. But with LOS and Custom Roms, I can finally add in the EAS changes that were missing. I am currently Testing a rom that has these changes added just for me to test with. We should have something more in the near future.

If you want to try out EAS. You will have a much better experience with LOS.
[OnePlus 3 & 3T Cross Device Development] madeferro:
Working nice, no lags :laugh:
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
Hey Renderbroken, is there any specific build of LOS that should be used with this kernel or can we use any LOS build or LOS based build?
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
Cool. What flavor of LOS are you running? Official with the eas changes or something else?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not really. I just know that this kernel is based on the new LOS kernel source. Also LOS has been kind enough to keep their rom source up to date and thus have added in alot of the needed eas changes.

I am running a build of Vertex OS and love it. It's by [MENTION=6745491]joshuous[/MENTION]

It's been a rock solid experience. He has been so kind as to provide the missing eas changes we needed to do eas right.
[OnePlus 3 & 3T Cross Device Development] cba1986:
could you provide a link? cannot find it in xda.
[OnePlus 3 & 3T Cross Device Development] gleggie:
Pm sent
[OnePlus 3 & 3T Cross Device Development] jmtjr278:
Me too?
[OnePlus 3 & 3T Cross Device Development] liam_davenport:
Me three? :laugh:
[OnePlus 3 & 3T Cross Device Development] iDynamics:
Can I get the link also? :D
[OnePlus 3 & 3T Cross Device Development] JagravNaik:
May I also get the link to Vertex OS please? Thank you!
[OnePlus 3 & 3T Cross Device Development] Zarancar:
With Google you find it easily, I found in 10 seconds.
[OnePlus 3 & 3T Cross Device Development] JagravNaik:
Found it!
[OnePlus 3 & 3T Cross Device Development] Ashtrix:
[MENTION=5060769]Mostafa Wael[/MENTION], So we have to rely on the ROMs commits to get the EAS working fully from what I read

So what about the AOSP based ROMs which are not using the LOS Source, Like maybe AOSPA in the future (Yeah I know Arter's been working with 4.x kernel and EAS too but just in case), Can we expect them also incorporate the Google's EAS patches with the Developer's fixes (all the weightlifting work), Really hoping that OP might also be interested in this new EAS.

I guess google should deploy this for all the ARM's big.LITTLE powered hardware, not just exclusive to Pixel (821) so that most of the ARM powered devices can reap the benefits & reduce the developer's overhead...Anyways Thanks.
[OnePlus 3 & 3T Cross Device Development] JagravNaik:
How's battery life on the ROM with your kernel?
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Please this post: https://xdaforums.com/oneplus-3/development/rom-zenity-resurrection-remix-n-t3551384/post70928582
[OnePlus 3 & 3T Cross Device Development] Pritster5:
ATTENTION: TO EVERYONE COMPLAINING ABOUT BEING STUCK AT HIGH CLOCKSPEEDS

It was a simple solution for me really. I went into EX Kernel Manager after flashing the Render Kernel and I noticed my CPU Governer was set to PERFORMANCE instead of SCHEDUTIL which is the correct EAS governor. Before saying nothing is working, PLEASE check in whatever Kernel Auditor you use to see if your CPU governor is on SCHEDUTIL and not PERFORMANCE.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Please note that the latest public version of VertexOS (1.8) does not incorporate the EAS changes. A lot of changes has taken place between 1.8 and 1.9. Stay tuned for the official release when it hits 2.0 ;)
[OnePlus 3 & 3T Cross Device Development] stryker09:
Awesome stuff [MENTION=5438598]RenderBroken[/MENTION]!! Btw do we still need to adjust the schedtune parameters or is this already preset? :)

Also any chance of a regular kernel test release? I'd like to give it a test run with my LOS build to see if I got everything in correctly :)

update: ok so i misread your post :) that was the kernel
[OnePlus 3 & 3T Cross Device Development] joshuous:
Look inside the /dev/stune/* folders for several schedtune.boost and schedtune.prefer_idle. You may adjust the values in those files. For quick adjustment you can link those files in the User Settings option of Ex Kernel Manager.
[OnePlus 3 & 3T Cross Device Development] stryker09:
Thanks! Yeah just noticed some values are preset :) thanks for the heads up :good:
[OnePlus 3 & 3T Cross Device Development] Zarancar:
Nice I'm glad to hear,I look forward to see your work:good:
[OnePlus 3 & 3T Cross Device Development] jithuelad:
Ultra sonic noob here. What is EAS? What is the advantage ? Is it something related with device battery performance ? :(
[OnePlus 3 & 3T Cross Device Development] novas78:
Energy Aware Scheduling (EAS): https://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-progress-update/
[OnePlus 3 & 3T Cross Device Development] Love4Taylor:
EAS only for Kernel 3.18 (820+) ?
[OnePlus 3 & 3T Cross Device Development] Konskl:
Could you pm the webpage where you found the Vertex rom? Can't find it :(
[OnePlus 3 & 3T Cross Device Development] franky14:
Me too please
[OnePlus 3 & 3T Cross Device Development] comediiian:
coz its not official i think.

only internal in slack group, when i remember right.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
AOSPA is said to include a "modified version of CAF's EAS".

I guess EAS can be incorporated in AOSP ROMs later on, but as far as I know, LOS is the easiest
[OnePlus 3 & 3T Cross Device Development] joshuous:
Hi all,

Let's respect [MENTION=5438598]RenderBroken[/MENTION] and keep discussion only on his kernel and EAS.

My official builds can be found here https://www.androidfilehost.com/?a=show&w=files&flid=138608.

If you want to know more about VertexOS and test builds, please check out the AKT Slack group. I'll be lingering there.

Edit: Corrected the url
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Bad SOT, Great Idle

Hey, I just wanted to see if others are having this issue: My standby time is amazing but my screen on time is **** (2-3 hours) because Android System and Android OS are draining SO MUCH battery. Am I the only one?

Here's a pic:

and the SOT:
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Deleted
[OnePlus 3 & 3T Cross Device Development] Jagdish84:
You mean you tried installing this kernel on this rom? I did just that and am writing this msg from my phone, running zenity Rom and Render kernel...
[OnePlus 3 & 3T Cross Device Development] knpk13:
Does any other device have EAS yet? Will you be supporting the OP3T [MENTION=5438598]RenderBroken[/MENTION] ?
[OnePlus 3 & 3T Cross Device Development] juginkrebs:
Keep up the Work Great Kernel !

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] 1337jay:
I think only Pixel has it, at least that is what I got from reading the PDF from the OP. Other Snapdragon 821 devices are more likely to have it.

Seems like a nice addition.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Boosting foreground apps makes no sense to me. Why would you give them higher priority than the app you are currently using? On the Marlin it is different. Like I had said before, they use cpuset/top-app along with stune/top-app. I think I found a way to port this over. So I would remove the current universal boost. Set foreground to prefer_idle, and top-app to boost and prefer_idle

Thanks! There was actually something useful in the new log so it is much appreciated! Depending on how this goes, I have another kernel base waiting in the wings.

The only device I know of right now that supports it are the Pixel phones.

No, I will not support a device I don't own. Despair will be supporting OP3T and will be playing with EAS as well. Not sure if he will release public builds though.
[OnePlus 3 & 3T Cross Device Development] habylab:
Can't download. I've tried everything but it always says "opening in Google drive" and then switches to Root Explorer. Really want to try this but can't annoyingly.

Edit: had to disable Drive.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
OK Guys, I need some help gathering some files. I need someone that is on the latest CM Nightly. I need some files from the system partition. If you can:

/system/lib/libutil.so

/system/lib64/libutil.so

/system/lib/hw/power.qcom.so

/system/lib64/hw/power.qcom.so

CM has added support for CPUSET Top-App. And this would greatly help me and allow me to properly use EAS to ONLY boost the top app and handle background tasks better.

I would do it myself but need my phone for work, so I cannot have alot of downtime.

Thanks Ladies and Gents!
[OnePlus 3 & 3T Cross Device Development] nadejo:
id say lets wait for next nightly because todays build is corrupted.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Ok , so here is a newer build of my EAS Tree:

R1-46-EAS

It fixes a few minor things and set sched by default correctly now. To stay up to date and check development see my commit history for my EAS branch here:

EAS Commit History

For those that are looking for the traditional and STABLE kernel, Here is a build from my alternate branch that is without EAS but is updated with CAF. It has a few under the hood enhancements and such.

R1-T47-Non-EAS

To stay up to date and check development see my commit history for my Non-EAS branch here:

Non-EAS Commit History

Honestly, going forward, you should have a solid kernel to fall back on when testing EAS since its unstable at the moment. So try out my Non-EAS build and let me know your thoughts on it as well. If EAS doesnt pan out right, it will be my dev branch.

Thanks guys!
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
I'm going to run the newest EAS build, I will edit my post at the end of the day. I also tried to find someone for the files you needed, but didn't manage to find anyone who is on the latest Nightly atm.

1. I got an instance where I couldn't get my phones screen on again.

2. Random reboot when my screen was off. Was making my math suddenly it rebooted.

3. Another reboot while it lied flat on the table.

4. Soft reboot right after I clicked the power button to do the screen off.

Most reboots seem to happen when the screen is off (was done not my maths so don't didn't had time to see if it happens when screen is on) . I'm switching back to stock kernal. Hopefully these logs provided something!
[OnePlus 3 & 3T Cross Device Development] DespairFactor:
EAS is currently only on the Pixel and OP3. It has been tested on bullhead and angler, but I think we did a poor job on those 3.10.y backports and didn't use sched changes properly in our configuration. I have had the opportunity to see how it works with the Pixel/XL as well and the nexus devices first hand. If we implement it with the proper values, we should see a huge benefit over qHMP. I will be doing my work on the OP3T, I believe mine will be at my house tomorrow or Monday given that DHL stops acting stupid.
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
The latest one seems to have an awesome battery effect on standby. Though there are some lags I am experiencing on gaming. Will update more.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Am I the only one who sees it stable enough to be a daily driver ??
[OnePlus 3 & 3T Cross Device Development] Bob823:
I had two reboots yesterday but couldn't look into it at the time. I flashed T46 today and so far it's been smooth sailing. Keeping an eye on reboots though.
[OnePlus 3 & 3T Cross Device Development] stryker09:
No reboots on yesterday's or today's builds thus far. Guys you want to make sure your CPU govs are set to 'sched' via your favorite kernel manager app
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Yes it is. Interactive will burn your hands btw; sticks to max freq on both clusters.

And no I had only 2 reboots with the last T40 build. T46 is so far so good. :good:
[OnePlus 3 & 3T Cross Device Development] habylab:
Do we have to reboot for schedtune settings to take effect, and will they stick upon boot? I'm trying 16 instead of 20, should be a little easier on the battery life I think. Currently on 40 mins SoT at 75%. Was much better on 4g though, has struggled on WiFi idling.

I've had one RR with 20 mins screen off, followed by troubled sleep thinking my phone will be dead in the morning - it was fine!
[OnePlus 3 & 3T Cross Device Development] njunxuan:
Hi may I know what app you guys are using to set "schedtuneboost". cant seem to find it in ex kernel manager
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Navigate to dev/Stune. Or make a custom path in kernal adiutor.
[OnePlus 3 & 3T Cross Device Development] frickinjerms:
[MENTION=5438598]RenderBroken[/MENTION] yoooo! I used your kernels all the time on my opo! Now I'm excited!
[OnePlus 3 & 3T Cross Device Development] njunxuan:
Sorry, what do you mean by navigate to dev/stune?
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Odd
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
Sorry for ot but i dont get any answer in any rom thread :D nur did Laos has the shelduled on/off function like in oos?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for the anouncement. I am still working on all my scripting so there may be weirdness like this when flashed on other roms.

No matter how much of a noob you are, you should always read OP and it clearly states to at least perform a simple search first. That is all I ask and if you cannot find your answer, I am sure we can help you. This is a kindly reminder to search before asking. Other devs are not as cool as I am about such a thing. It's OK though, we were all noobs once ;)

Not sure why you are asking about a different kernel in my thread. I cannot help you there lol

No, its in the newer linux kernels too. But for "Android, the 820/1 are the only ones that I personally know of but it could be used for others.

I didnt see this feature but please, if you have to ask something soooo OT, just PM me.

Thanks!

Should have a new test build soon.
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
I was having trouble installing your kernel, but fixed the issue.
[OnePlus 3 & 3T Cross Device Development] Eliminater74:
It had made a world of difference.. All my users said its the best Kernel they ever ran.. But again, this is my 4th attempt to get it right.. and I have managed to finally do that..

Also note that our HTC10's come with all the included framework for EAS, the only thing it did not come with are the system/lib/libutils.so and system/lib64/libutils.so ...

But using the pixels in replace of our stock ones made it all happen..

and the new EAS branch that Google is working on is the icing on the cake............ I also have dipped into Linaro-lsk-3.18-android which is the most updated

of them all.. and google pulls from there as well..................

And some of our HTC10 users also have pixels XL, and have reported that the htc10 now keeps up with the pixel.. some reported its faster, but I think think they are just being nice.

but to keep up with the pixel is a big time improvement, the fact the HTC10 is a 820 SOC while the Pixels are 821 SOC..........

I have manipulated much of the 821 SOC settings and functions......... like our GPU hits 650mhz with no problem........

Technically according to qualcomm, our GPU is capable of reaching 900mhz,a s long as Heat can be tamed.. so for us on the HTC10, I would say 750mhz max.......

anyhow I will end it here.......... sorry to be a little off on this thread... but I just happen to see that I was mentioned and figured I add that.........

l8rz.
[OnePlus 3 & 3T Cross Device Development] cba1986:
[MENTION=5687366]Eliminater74[/MENTION] [MENTION=5438598]RenderBroken[/MENTION]

https://twitter.com/arter97/status/829199018513281027