yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
Kernel Adiutor is recommend :)

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Hecke92:
Dont get me wrong, no need to be sorry :)

I just keep f5ing ;)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
You can use both.

Also I am finishing test my final build. I am. Just making sure all the extra features work right.
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Awesome. So excited ??
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
It has been such a long time coming. I think I made just stick with working on EAS and leave hmp for the other kernel devs. I don't really add much into that area anyways and I would much rather focus on contributing through EAS.
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
I know what you mean. I've watched and tested all along the way. When I look at the GitHub in amazed at how many changes you've tested to get the final build out. For your personal sanity and to avoid using all your time, you're probably right to focus exclusively on EAS and discontinue HMP work. Let Franco, eng.stk and zero blade worry about the, IMHO, slowly dying HMP.

PS. Saw you pulled down the old test build source from your GitHub. I'm guessing this is to prepare to push r4 code to your GitHub.?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Really just to clean it up, it was getting a bit out if hand lol. So far all tests are working great. I am expecting release in a couple hours.
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Will it be ok to dirty flash the new kernel over R3, or should I re-flash the system first? I'll end up clean flashing everything to test the script issue, or just because, given enough time, but I'd love to try the kernel out ASAP lol
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
RK-LOS-N-EAS-R4 is HERE!!!

Things to note:

This build has been a huge project. Not only was I doing this work for the OP3(T), I was doing this work to lay down the groundwork for other Devs to port and use to bring EAS to their devices. I have collaborated all over XDA. If we can get EAS taking off faster, then maybe more OEMs can see the benefits of it. I have rebased, my rebase, of a rebased rebase and finally landed on what we are using today. I have thoroughly testing with the LISA Toolkit from ARM. Then I added all the normal Render Kernel features that DID NOT create performance regressions. Now, we have R4. I have build a PELT and WALT variant. Right now I prefer and recommend WALT. This is QCOMs solution to Load Tracking and is very interactive. PELT is in mainline linux and uses CFS (Completely Fair Scheduler) as its base and uses Load Decay. This one ramps up and down slower. So the fast load changes where WALT may cause SCHEDUTIL to lower frequency, PELT may continue to carry the load through this period. In theory that is. For Me WALT seems to just be better all around but the future goals of EAS is to have PELT become more competitive with WALT.

You have a questions? Ask it! There is only one way to learn and that is by digging in. Please let me know how it works for you.

Download

Changelog
[OnePlus 3 & 3T Cross Device Development] iaa85:
[MENTION=5438598]RenderBroken[/MENTION] First thanks fir all this effort, it is really nice... So if I don't understood wrong, wal will give a good performance with better battery than pelt? Thanks a lotone more time!!!!

Iaa85 from Brazil with Oneplus 3t

Powered by Phoenix AospExtended
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Can we flash this over previous variants, or should we dirty flash system first? I've heard it can cause issues with the ramdisk or something if you flash the wrong kernels over one another.
[OnePlus 3 & 3T Cross Device Development] stryker09:
Dirty flash system first would be the best way, but I've had mixed results with dirty flashing kernels since most root solutions depend on modified boot images
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
They are about equal. Experiment and report back. I would love to hear what you have to say.

Sorry, I meant to reply back earlier. Yes, I believe that it should be just fine. They way I setup my scripting would just overwrite itself each time. No issues.
[OnePlus 3 & 3T Cross Device Development] knpk13:
You said you could make EAS work on OOS. But I remember that it was mentioned that EAS needs ROM side support as well. Does OOS have that already?
[OnePlus 3 & 3T Cross Device Development] nan0s7:
I don't know why I didn't have a look at this earlier. Gunna try out the WALT for LOS... I'll let you know how it goes. I was thinking about making a custom kernel.... this may be a good way to dive right in to the good stuff ;D
[OnePlus 3 & 3T Cross Device Development] Philb90:
Amazing!!! I woke up with R4 to flash!!! Now i m just waiting new vertex ;)
[OnePlus 3 & 3T Cross Device Development] rui.ddevil:
Curiosity...

Does anyone know why is the Westwood and other TCP algorithms missing from the EAS version?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
No, oos does not have the eas support natively. But with the gains I have made with eas and how it performs now, I am not as worries about the UI being in the top-app tasks list. There are a few tricks up my sleeves that I will be using. ;) I have put a ton of thought into this very thing.

Doing is through best way to learn. It's best to start of with a other devs kernel and tweaking it further since they normally already have all the different pitfalls covered. Let me know of you have a question.

Just forgot. Lol thanks for the heads up. It was even on my to do list...
[OnePlus 3 & 3T Cross Device Development] Balino:
[MENTION=5438598]RenderBroken[/MENTION] Sorry to bother you but do you think eas will require a lot of work to be implemented on oos?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not really. Since I had done all the groundwork for LOS, I have a game plan for OOS. EAS at its baseline is so much better than it was before. I have used it without any boosting on LOS and was happy with the performance. For OOS, I have a few ideas about how to make it the most compatible. I will also continue working with [MENTION=6745491]joshuous[/MENTION] with gettting EAS ported to OOS the best we can. The goal for EAS on LOS was to show how powerful EAS can be when setup properly in both the kernel and the Rom. EAS for OOS will show other Kernel devs how to implement EAS in the kernel for roms that don't support it.
[OnePlus 3 & 3T Cross Device Development] nadejo:
pretty good kernel
[OnePlus 3 & 3T Cross Device Development] afrob:
What is the different from HMP and EAS?

I have the OP3T and i am on AEX Phoenix 4.1. In this thread they recommend LOS version
[OnePlus 3 & 3T Cross Device Development] ahepas:
Please, do your homework... Everything you want or should know it's out there... Some stuff even in this thread...

Στάλθηκε από το ONEPLUS A3003 μου χρησιμοποιώντας Tapatalk
[OnePlus 3 & 3T Cross Device Development] nadejo:
ive noticed gaming performance using mem_latency gpu governor and zen 4k scheduler is unmatched :) however interactive governor acts like performance governor and scrolling performance using sched and schedutil is very choppy=very high hw latency :(

latest walt kernel using official rr rom
[OnePlus 3 & 3T Cross Device Development] Philb90:
For the moment i think is better to run eas kernel on ROMs that support ead.... Check if official RR is compatible
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Note, you guys DO NOT want to use interactive with my EAS Kernels, it is there because if not, it causes the kernel to not boot. So please stick with the default governor (SCHEDUTIL) only.

You may have to reboot to get things back to normal again though. I imagine Interactive screwed things up. Give that a shot and report back please. Thanks!
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
While true. it should still run o on LOS based roms that don't fully support EAS as well. Though it is highly recommended to use a rom that does support it. Like Vertex
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
RK-LOS-N-EAS-R5 is HERE!!!

Things to note:

Just some minor fixups I missed for R4 and wanted to leave on a more completed note since I am moving to OOS for further EAS testing.

Added in Advanced TCP Options

Disabled some debugging

Downloads

Changelog:

R5:

2941cbc (HEAD -> rk-los-n-eas-master) Defconfig: Enable Advanced TCP Options

18d3e99 msm: mpm: disable debugging

d9494ee msm: vidc: disable debug logs

04bc1d9 qcom-cpufreq: take different startup freqs from OP3 into account

c31b66f qcom-cpufreq: ensure startup is according to default frequencies (no overclocking/underclocking)

9611e7e Remove "-dirty" from Kernel name

520efe7 power: make sync on suspend optional
[OnePlus 3 & 3T Cross Device Development] liver20:
What version do you recommend for DU?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] masri1987:
for the OOS version, do i really need to set any settings or can i flash n go?

The r2 oos kernel isn't on the link in the OP... can anyone provide link?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thats up to you, I prefer WALT but you may like PELT. Just try it.

I dont support the old builds nor do I recommend them. There are changes needed for them to even work on the new OOS builds so hang tight till I can get new OOS builds out. Thanks!
[OnePlus 3 & 3T Cross Device Development] masri1987:
TY, i was under the impression based on the title of the thread that the update was posted. i shall be patient.

Flash n go? or is there a preferred setting?
[OnePlus 3 & 3T Cross Device Development] liver20:
I ask doesn't matter that du not Eas?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] ShiShTuBaBu:
Why am I getting this much lower than you. I am on Aex ROM and render r5 walt kernel. :(

[IMG="img"]http://i.imgur.com/aFVogTI.png[/IMG]
[OnePlus 3 & 3T Cross Device Development] joshuous:
It matters a lot of if a rom doesn't have the needed EAS support. You will have a poor experience with the EAS kernel (choppy performance)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not all phones are made the same and Geekbench isn't always accurate. There are a number of different reasons. Try running again with Vertex OS. Try running again after having the phone be idle and cool for a long time.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not really, I tested on stock LOS and it was fine. So your milage may vary. There is no doubt that you get a perfect EAS experience when the rom supports it, like Vertex ;) Please test and report back guys. That's the only sure way to know.
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
I just installed R5, and as far as I can tell it's still booting in permissive. I didn't see you say you switched it in the changelog, but the weird thing about all this is that R3 would boot in enforcing by itself, and only switch to permissive when Magisk was installed as well.

I haven't been able to clean flash and test R5 without Magisk, but I will test R5 both on just ROM and GApps, and with Magisk as well. So, once I have the chance to do that I'll let you know what I'm seeing. It would be cool to have a version that is enforcing by default, (if R5 isn't already,) if only just to see how that affects it. The service.d script is still successfully putting it in enforcing for me, though, so it's more a matter of curiosity at this point.

Similarly curious about something else, too. I swear I saw the "wq_power_saving" setting in EX Kernel Manager's CPU settings page set to enabled by default when I was running R3, which was weird because with normal kernels, even if I set EXKM to toggle that to enabled at boot, it doesn't work and remains disabled. I assumed this was something to do with EAS, as it sounds exactly like the point of EAS, but on R5 it's disabled by default and once again if I set it to enable at boot, it remains disabled. I don't really know anything about the kernel or what this setting might do, but just thought I'd ask in case it was important. (side note: could this be a bug in EX Manager?)

Thanks again for all this work you've done, I haven't used R5 much but it feels as smooth and snappy as any other kernel I've ever tried, and R3 was already the best battery life I've ever seen! So huge thanks and huge congrats for breaking some serious ground on the future of Android!
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am leaving it disabled by default now. The reason being is how eas handles task placement. Before, power effecting work queues would schedule certain work queues on cpu0 to conserve energy by not waking idle cores to complete them. I do not want that mechanism messing with ease native energy aware task placement.
[OnePlus 3 & 3T Cross Device Development] afrob:
[MENTION=3646325]ahepas[/MENTION] i read the topic, i dident find it and then i asked. Whats wrong with you?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
The two have been discussed in detail but not together. I will add a note to OP with this information.

HMP = Heterogeneous Multi Processing

This was CAF's attempt at handling BIG.little processors. Especially to handle scheduling with the scheduler knowing about the energy efficient small cores and the performance oriented big cores. Before HMP, on SMP (symmetric multiprocessing) the processors are all the same, the share resources, etc. So the scheduler was just worried about just task placement with throughput in mind and didnt have to worry about placing a task on an insufficient core. HMP, does alot of the same things that SMP systems do, just with BIG.little in mind. So now it has to look at the workload and assign it to the most efficient core to complete those tasks. It was designed to continue with the similar scheduling methods but could handle BIG.little.

This design worked ok, but they (developers and engineers from ARM, Linaro, Google, ETC) knew that there is a better way to have the same throughput, yet save more energy doing the same work. EAS was born. IT started out as a discussion on how they could save energy, yet keep the same throughput by quantifying the task in the scheduler, and assigning said task to the best core. Really, EAS comes down to just proper task placement on cores. Sometimes, it's more energy efficient to wake an idle core. While doing this is keeps in mind what sleep state the core is in. If it's too deep, it might cost a bit more energy than to just increase the capacity of a core and placing the task on it. Capacity, it like you would think, it is tied to the frequency a core uses, so really it means the amount of work that can be done, at certain freqs on a certain core. With BIG.little SOCs this means that the small cores share resources, and the big share their own resources. So EAS has to have a map of the SOC otherwise, it won't know the efficacy of task placements. To do this EAS uses an Energy Model. These are specific to the SOC they were made for. What this does is tell EAS (Scheduler) the cost and ability of task placement. Sometimes it's more energy efficient to move a task to the big core. sometimes, it's better to pack them all on the small cores. There are other things that EAS does to make sure throughput is kept while remaining energy efficient. So this means that all NEW tasks (ones yet to be measured, or quantified) start out on a BIG core, and if needed migrated to a small core if deemed that the BIG core would be overkill.

TLDR:

HMP wants to have throughput on BIG.little systems

EAS wants to have throughput while saving energy by doing more effective task placement. This is for BIG.little and SMP systems.
[OnePlus 3 & 3T Cross Device Development] afrob:
Really nice. Big thx
[OnePlus 3 & 3T Cross Device Development] ahepas:
Wrong? Nothing at all.... I found it... Like others did... End of story... You should search better next time... Sorry for the ot...

Στάλθηκε από το ONEPLUS A3003 μου χρησιμοποιώντας Tapatalk
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
The scores he's getting look more like 3T scores, while yours look more like standard for the normal 3. Not sure if you're using basic AEX or phoenix AEX, but in the phoenix AEX thread there's a couple pretty much identical posts, and the guy who got the higher scores replied that the benchmark app wasn't showing his model correctly.

If someone asks a question you don't think was necessary, you're only adding to the clutter by replying to them to tell them they shouldn't. They aren't harming anyone by making a post. If you don't want to make posts you think are off-topic, then just don't, especially if all you have to offer is disparaging and useless advice like "search better". OP and the moderators can do that job if needed.
[OnePlus 3 & 3T Cross Device Development] iceman0826:
anyone tried playing CSR2 game using this combination, P.AEX+Render Kernel R5? It seems the frequency switching is wrecking havoc to the gaming performance. There's a noticeable lag using this combination.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
What is CSR2? Also , does it work ok with stock kernel?
[OnePlus 3 & 3T Cross Device Development] iceman0826:
It's a drag racing game :svetius:

I've been using Sultan's CM13 Rom and Freedom v2.8+Blu_spark kernel before I tried the P.AEX + Render Kernel combination.

It's just my theory that EAS kernels are much aggressive with voltage+frequency switching than HMP ones and that it's affecting the gaming performance of these 2 games:

Dawn of Titans

CSR2 Racing
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Could very well be possible, though I haven't found a game that caused me issues yet. So I will test with yours when I can.

Also, don't think about EAS as switching voltage/freqs, think of it like, you have 2 tasks, one is a background task so it has a small capacity and the other is a top-app task, so it has a larger capacity. The BG tasks uses 307 MHz if it was the only task, the TA task uses 900MHz if it was the only task. BUT If both are being worked to completion on the same core at the same time, the freq used would be 1.2GHz.

So you see, we don't use timers like HMP, and tasks could get underpowered. EAS gives each tasks an amount of bandwidth. When a core drops to idle, this means that those tasks were completed or migrated from Top-app to foreground. There is alot going on. But the more info the better. So thanks for reporting!

I am on OOS right now but will see if I can get anyone else to repeat your claim.
[OnePlus 3 & 3T Cross Device Development] iceman0826:
Thanks for this wealth of information :) I'm gonna redo and reflash again, P.AEX (this rom reminds me of Temaseks Rom ☺️ Galaxy S3 days) plus your Kernel, to eliminate any user errors in my side and to satisfy my OC'ness hehe.

And yes, I think EAS is the future since as u said it cuts out the middle man, this analogy reminds me of Vulkan API (closer to the metal something ?)

UPDATE

Just finished starting again from scratch, and I remember setting the gpu governor to mem_latency for testing purposes, and yep the "latency" really does work and made the gaming performance to suffer.

Another very idiotic user error on my part, apologies for that :( This Kernel didn't introduce any kind of performance penalty at all!

Gonna stick to P.AEX + Render Kernel to test battery performance. Using schedutil+maple@4k for 5days and will report back.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
It's all good! I am just glad that you came back and reported the solution and admitted fault. I wish all users that levy a complaint would report back a solution if they found one. Glad you are enjoying!

Progress update!

I was able to get my OOS source to compile. At this point, I am setup to start pulling in all my EAS work. Should start ripping builds soon.
[OnePlus 3 & 3T Cross Device Development] infamousvincci:
What is the maple@4k?
[OnePlus 3 & 3T Cross Device Development] aymahalawa:
Maple is I/O scheduler and 4K is read ahead value :)
[OnePlus 3 & 3T Cross Device Development] infamousvincci:
Read ahead of 4k? Isnt it a lot? Or is it a good tweak? :) Thanks for the info
[OnePlus 3 & 3T Cross Device Development] JumboMan:
OOS by default set read ahead kb to 4096(4kb). so i don't think its out of space.

But I never seen such high value on custom roms ( most rom comes with 256/512kb)

And [MENTION=5169579]iceman0826[/MENTION] i am waiting for your feedback on maple with 4kb read ahead
[OnePlus 3 & 3T Cross Device Development] iceman0826:
From what I know maple is a combination of SIO+Zen, which imho both are good for gaming and they compliment each others weaknesses hence, Maple was born.

As for the 4k read ahead, I'm just testing the waters and it seems 2048 is still ideal/recommended since I have the 64gb variant.

As for the battery life, I think 5 days trial will be enough to gauge it. Otherwise, glad to know that we already have this awesome of a EAS kernel, thanks to RenderBroken ??
[OnePlus 3 & 3T Cross Device Development] Balino:
I've always seen 512kb on oos :confused:
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Magisk and RenderKernel causing SELinux to boot in permissive

[MENTION=5438598]RenderBroken[/MENTION] So, I've clean flashed the latest build of Phoenix AEX, and as before it's booting in enforcing, even with your kernel, until I flash Magisk as well, at which point SELinux boots in permissive. Is your kernel supposed to be enforcing by default now? Because I remember you saying it was supposed to be permissive before, for testing, but it always booted enforcing, until I installed Magisk as well.

I've posted about it in the Magisk thread as well, so I'll be sure to let you know if I get an answer there. If not, a simple script containing "setenforce 1" in /magisk/.core/service.d switches it to enforcing by the time I can check.

If it's not too much trouble (and R4/5 aren't enforcing already), would it be possible to ask for a version of the kernel that is enforcing by default? I don't know much of anything about system-level stuff, but I am very curious if that will have an effect on it.

Would you like me to try the same things on Vertex OS and see if the results are the same? I was going to, but I noticed that joshuous lists your kernel as "RenderZenith" and didn't know if that was his modification of this kernel, or something else, so I thought I should ask you for advice on it all, before I confuse myself any further lol.
[OnePlus 3 & 3T Cross Device Development] joshuous:
RenderZenith builds upon the vanilla EAS base from [MENTION=5438598]RenderBroken[/MENTION].

Mine is on Enforcing all the way. [MENTION=5438598]RenderBroken[/MENTION] might have forgotten remove one line in the init.rc of his kernel that causes permissive mode
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Yeah, I installed Magisk on the latest Vertex and SELinux remained in enforcing, but after installing R5 it became permissive. I asked in the Magisk thread and the only reply was that the kernel is setting it to permissive somehow.

Edit: A nice fellow in the Magisk thread helped me out, said line #111 in ak2-core is what's doing it. I didn't want to fill the thread any more but I'm very curious as to why it isn't doing that before Magisk is installed. https://github.com/RenderBroken/RenderKernel-AnyKernel2/blob/rk-op3-los-n/tools/ak2-core.sh#L111

I tried editing that locally and reinserting into the zip. I have no idea if that's a viable way to change it, lol, but it didn't do anything. So, either he was wrong, and that's not what's causing it, or Render has to change it before building.