yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Stroky:
How can you run Discomark under Nougat?

Sounds very interessting your EAS Stuff here.

Will wait a few weeks if its stable, and then switch from Oxygen and to your Kernel.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not sure but it just works with no issues.

Honestly, its stable now.
[OnePlus 3 & 3T Cross Device Development] pantmunu:
Actually I was using the los ROM someone posted a few pages back which had your kernel inline. Currently I'm at my lawyers so won't be able to test. As soon as I get home. I have 2 op3t( work benefits) and I can help you test this kernel for the 3t on either oos or los based Roms depending on what you want. I switched back to freedom.in my test op3t but I'll flash some los based ROM.and give this a go. Again, thanks for the reply and your hard work.
[OnePlus 3 & 3T Cross Device Development] Roykooiman:
the developer gave me rights to download it from AFH. So yeah i used the latest test builds.

Also now im on Oos 4.0.3 + render R2 and experiencing a high cpu usage. While doing nothing it's stuck on the max freq of the little cluster.
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Not sure if it applies to your case but have a look at this..

https://xdaforums.com/showthread.php?p=70847148

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Hard to say but I would use something like Kernel Aduitor to make sure that the little cluster is set to the proper governor and not something else. Lastly, my OOS-N-R2-EAS kernel is out of data and needs the 4.0.3 kernel changes so that could also be the issue. I can only say that before 4.0.3 there was not such an issue.

Thanks for the report!

I am updating my flashable Zip and once I release my finaly LOS-N-EAS-R2 build, I will update the other three builds I will be doing including those for OOS-N.
[OnePlus 3 & 3T Cross Device Development] Roykooiman:
CPU governor is properly set on schedutil. Also it stutters quite alot. Here a screenshot:
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
https://xdaforums.com/showpost.php?p=69762512&postcount=2

EAS analysis is up! :)

hope you enjoy your read :good:

---------- Post added at 10:20 PM ---------- Previous post was at 10:04 PM ----------

try the following:

1- dirty flash OOS 4.0.3

2- flash anything you like to flash like root, mods,...etc

3- boot into system and let it settle (wait for some 2-3 minutes maybe)

4- After 3 minutes, observe the CPU frequency used on the little and the big cluster.

--> If you see the same behavior, then try going in terminal emulator and type "su" followed by "setenforce 0" (without the quotes)

--> If you still see the same behavior, then it is an app causing that chaos.

5- After ensuring that the CPU is in the green, go flash the latest OOS-EAS build

6- Boot in the system and let it settle for some minutes (3 minutes maybe)

7- After some 3-5 minutes, observe the CPU usage for both cluster

--> If you see the same issue you report, try doing the same thing in terminal emulator mentioned earlier

--> If you still see the same behavior, open up terminal emulator again and type

echo 4 > /dev/stune/top-app/schedtune.boost

waiting for feedback.

P.S. if all that fails, it is an issue related to the fact that the kernel is not in sync with the latest source drop from OnePlus concerning OOS 4.0.3
[OnePlus 3 & 3T Cross Device Development] rankin1:
Vertex Os plus your new kernel equals the best rom out there by far please guys keep up the great you'll are going places

---------- Post added at 03:54 PM ---------- Previous post was at 03:52 PM ----------

I am afraid to even flash another rom because this is so my daily driver
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
GLad to hear. Yea they are essentially made for each other.
[OnePlus 3 & 3T Cross Device Development] stryker09:
[MENTION=5438598]RenderBroken[/MENTION] do you plan on pushing your latest sources? :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
It is, I always try to keep it pushed and up to date. Maybe you are looking at the wrong branch but I am currently finishing up my final LOS-N-EAS build.

See here:

https://github.com/RenderBroken/OP3-LOS-kernel/commits/rk-los-r1-t5
[OnePlus 3 & 3T Cross Device Development] rankin1:
How can I monitor vortex Os development
[OnePlus 3 & 3T Cross Device Development] A Sad Napkin:
Any chance you could make it compatible with one plus 3t?

Im on a EAS resurrection remix build and would love to use your kernel with it.

I don't mind testing.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
[MENTION=6745491]joshuous[/MENTION] where do you want them to line up?
[OnePlus 3 & 3T Cross Device Development] rankin1:
I prefer use his rom compared to stock and your kernel of course please bring out a joint project it would lift off really quickly
[OnePlus 3 & 3T Cross Device Development] rankin1:
Any plans of building a kernel for aosp based roms just politely asking or this current kernel can also be used as well because I know it says Los
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not sure. I would imagine that they are using LOS device source and kernel so it should work. Flash and see. Only thing that would happen is it would boot or not. If not, just get back into recovery and restore the backup of /boot you should have made before flashing a kernel. boom, you are back to where you started. No harm done.

If you try it, let me know please. Thanks!
[OnePlus 3 & 3T Cross Device Development] rankin1:
OK I surely will
[OnePlus 3 & 3T Cross Device Development] joshuous:
Hey man, you can keep track of my updates here:

https://github.com/vertexos

https://github.com/vertexos-devices

I currently have to rebase because of the massive LineageOS rebase to the latest CAF updates recently.
[OnePlus 3 & 3T Cross Device Development] aadityarulez:
Tested LOS EAS version on Validus based on aosp. Booted fine. Will let you know how it performs after a few cycles.

Cheers.
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Were did you get an EAS version of Validus?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am pretty sure he is referring to my LOS-N-EAS kernel
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
That rom would not have the proper commits to work well, or at least as it is intended with EAS, but I guess if it works and boots fine, so be it.

Any updates on Vertex, RenderBroken?

I am loving T19 on Zenity's latest right now.
[OnePlus 3 & 3T Cross Device Development] joodii:
Working fine here on cosmic os with op3t
[OnePlus 3 & 3T Cross Device Development] joshuous:
Very very near to release. Looking hard for issues, and making sure everything works well for the most part
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Will you create your own thread for 2.0 release?
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Will VertexOS 2.0 use the 4.0.3 firmware?
[OnePlus 3 & 3T Cross Device Development] joshuous:
Yes, the current test builds run with 4.0.3 firmware.

I will be doing so :)
[OnePlus 3 & 3T Cross Device Development] aadityarulez:
I didn't. I used the los variant of eas on Validus.
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Hey joshuous, I just wanted to point out that on VertexOS the apps start crashing after a while and a reboot fixes them. For example my Google messenger app started crashing after a while and I had to reboot to be able to use it. Is this a known issue?
[OnePlus 3 & 3T Cross Device Development] joshuous:
Were you running 4.0.3 firmware on VertexOS 1.9? If so then that might be the problem.

I'm running 2.0 with 4.0.3 firmware and have not experienced crashes with Google Messenger over the week
[OnePlus 3 & 3T Cross Device Development] aadityarulez:
Vertex 2.0 is released ? Couldn't find it anywhere.
[OnePlus 3 & 3T Cross Device Development] Pritster5:
No, I'm on 4.0.2 firmware. I can't figure out the issue.
[OnePlus 3 & 3T Cross Device Development] joshuous:
It's a private test release. The official release will be in a few days, supposing no major bugs come up.

Strange, it would be best for you to PM me the logcat.

I won't say much more about VertexOS on [MENTION=5438598]RenderBroken[/MENTION]'s thread, so that we don't go off topic further. If anyone is interested in more information, please PM me or find me on the AKT Slack group.

Edit: Major bugs came up (thank you LOS) and I'm now rebasing to CAF. Official 2.0 release will be delayed but I want to ensure it works fantastically. I will release a VertexOS 2.0 release candidate for you guys to play with while I'm rebasing (https://www.androidfilehost.com/?fid=457095661767138580). Please use 4.0.3 firmware. You should be able to flash [MENTION=5438598]RenderBroken[/MENTION]'s kernel over this. Absolutely NO bug reports will be accepted for Release Candidate.
[OnePlus 3 & 3T Cross Device Development] Gomezie:
Will it take the form of a thread in this dev forum? I would be eager to try it.. but will wait if coming more formally

Kind regards
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Ok so after testing VertexOS with the LOS version of the Render Kernel, I have to say the battery life has been a little underwhelming. I have consistently gotten 4 hours of SOT over a week of testing. While the standby time is phenomenal, is there any way to increase the SOT? I used to get 5-6 SOT on OOS stock kernel so this is kinda disappointing.
[OnePlus 3 & 3T Cross Device Development] pantmunu:
I need to test vertex os ... Is it still in private testing ?
[OnePlus 3 & 3T Cross Device Development] Pritster5:
You can find the link a ew pages back in this thread. It has not been released on XDA yet, that will happen with VertexOS 2.0. It is currently at version 1.9
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Here yeah go: https://www.androidfilehost.com/?fid=457095661767138580

[/I]
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Here are my results with vertexOS 2.0, crazy high screen on Time, I also under clock allot 1824B 1478L.

https://www.androidfilehost.com/?fid=457095661767138580

This was with render kernel's T19 kernel
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Wow thats insane. What kind of usage do you do and what changes does VertexOS 2.0 bring?
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Yes it is insane, as for usage mostly twitter, tumblr, chrome dev, inbox, checking gerrits, no heavy apps at all, no FB, what's up, snap ****, hate all those apps, crap, if I can't run it in a browser I don't use it at all. This was done with at home good WiFi on the whole time. Vertex OS is very light AOSP/CAF ROM.
[OnePlus 3 & 3T Cross Device Development] pantmunu:
Hold up. Is this unified. Coz I'm on one plus 3t. Just wana make sure before flashing.
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
I believe it is just make sure you only update firmware with the right one.
[OnePlus 3 & 3T Cross Device Development] pantmunu:
I'm.up to date with the firmware. Lemme flash it. Backing up now. Thanks much.
[OnePlus 3 & 3T Cross Device Development] Pritster5:
That's strange. I'm running 1.9 and I have pretty much the same usage as you but with some light gaming too. Did 2.0 improve battery?

---------- Post added at 04:07 AM ---------- Previous post was at 04:03 AM ----------

I noticed that maybe because of a bug in the Render Kernel my CPU speed never drops to 307 MHz which is the minimum, it always goes to 422 MHz. Is this a bug with VertexOS or the Render Kernel?
[OnePlus 3 & 3T Cross Device Development] pantmunu:
Running smooth on 3t with the recent los was kernel and vertex os

Few observation. Small clusters don't want settle down to the lowest frequency. Changing tonunteractuve keeps the core to the highest frequencies all the time. Will spend some more time and test.

Thanks.
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
You need to make sure the CPU gov is set to shedutil and no other for both big and little cores.
[OnePlus 3 & 3T Cross Device Development] pantmunu:
Both are on schedutil

---------- Post added at 06:34 AM ---------- Previous post was at 06:33 AM ----------

It probably just needed to settle down ....
[OnePlus 3 & 3T Cross Device Development] eroigaps:
Anyone tried this with Dirty Unicorns?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
/dev/stune/topapp/schedtuneboost what value is it on? I'm currently on 5 it works fine for me, 10 is default.
[OnePlus 3 & 3T Cross Device Development] joshuous:
It should just work, but DU doesn't have the additional flags required for EAS to run optimally (looking at their source code)
[OnePlus 3 & 3T Cross Device Development] eroigaps:
Alrighty. Guess I'll just stick to the stock kernel for now.

Thanks!
[OnePlus 3 & 3T Cross Device Development] joodii:
Changed schedtune.boost to 2 and schedtune.prefer_idle to 0, now device use the 307mhz values, but I don't know if it's the optimal conf. It's better to stay in the stock values but you can play with this two files.

PD: is Vertex 2.0 based on AOSPA?, love it and performs excellent, can't wait for the final release
[OnePlus 3 & 3T Cross Device Development] stryker09:
[MENTION=5438598]RenderBroken[/MENTION]

Waiting for your latest sources to be pushed :) it's no longer in sync with LOS after the rebase as /dev/stune/top-app does not get created during init nor can it be created (disk is full, it seems)

Not sure if you're running into it as well but let me know if you need a logcat!
[OnePlus 3 & 3T Cross Device Development] JagravNaik:
Can you give me the link to T19?
[OnePlus 3 & 3T Cross Device Development] joshuous:
I'm running into this after the rebase. And I don't know the cause and the fix yet. That's why I'm rebasing VertexOS to CAF.
[OnePlus 3 & 3T Cross Device Development] stryker09:
Thanks for confirming! It gets created just fine when I comment out USE_SCHEDBOOST in the BoardConfig and switch back to stock LOS kernel.. so must have something to do with that. The same build with T19 also has the issue so its looks like it may be on the kernel side...

When I try to manually mkdir /dev/stune/top-app from terminal it throws a "disk is full" error so I'm leaning towards sdcardfs related stuff... which is way out of my league :(

Edit: heck it could even be sepolicy related
[OnePlus 3 & 3T Cross Device Development] joshuous:
Thanks for checking! That's some valuable information that you've provided
[OnePlus 3 & 3T Cross Device Development] Pollie81:
The link is just in OP..
[OnePlus 3 & 3T Cross Device Development] pantmunu:
Weird mine was in 8, so I changed it back to 5 which showed some erratic frequency changes in little cluster .. may be it's my fault. I'm gonna try to Dona clean install with vertex is and the kernel again and see how it works. But battery life seems pretty good till now.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
No, I am sure it has to do with the new SDARDFS commits. I had them before the rom source supported it so I reverted them, now I need to add them back lol. No worries, I will release a new test build shortly. Also note that it would be best flashed ontop a clean ramdisk.

Hold tight and I will release a new build.

See above about SDCARDFS

I have been running with 5.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
LOS-N-R1-T28-EAS is HERE!!!

New Test build! Should resolve some issues. Please test and report. Thanks! Getting really close to final build. Working on one last issue but is a big one imo. Performance has been great for me so far. Let me know what you guys think.

Download

Based on this branch: Here
[OnePlus 3 & 3T Cross Device Development] mittimus:
Default governor is schedutil in this build? Coudl you post the stock parameters? Because I have seen that sometimes are totally random after reboot.
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Feels much smoother. There were some micro stutters in the previous one.. Now its mostly gone.. Nice! Using with vertex 2.0.

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] siankatabg:
This is how I fixed this issue:

https://github.com/siankatabg/android_system_core/commit/d45226240438e570b3c641025d6dbbd586da473a

Seems to be some missmerge, because those lines are not present in the google code(link in the commit) and I'm not sure if this is the best way for fixing this, but it works for me :)

Also those lines are not presented in the prerebase branch.
[OnePlus 3 & 3T Cross Device Development] joshuous:
I'm aware of this fix but I would prefer a solution that enables us to have all tunables, including system-background as well. The lines for this are not mismerges, but rather an addition by CAF. But yeah, it is more important for us to have top-app tunable imo
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
Working with 3t?
[OnePlus 3 & 3T Cross Device Development] joshuous:
Yes it works. The majority of LOS-based kernels are now Unified. You may consider using the search tool next time to check whether other OP3T users have got it working.
[OnePlus 3 & 3T Cross Device Development] joodii:
What's the default schedboost and idle for the last version?
[OnePlus 3 & 3T Cross Device Development] siankatabg:
Well this was fast and dirty fix, because without the top-app folder and tunables, the big cluster(at least for me) was almost constantly on idle. I didn't knowed that it is a CAF addition, but I didn't looked much anyway... Hope we will find a proper fix soon :) Please inform me if you find something :good:
[OnePlus 3 & 3T Cross Device Development] joodii:
pls delete this post
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
THis build is best flashed ontop of a stock ramdisk. The default setttings for all schedutil tunables is just "1000"
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Those lines should make any difference for top-app to be missing. must have been something else that fixed it because I just don't see that fixing the issue. It should still create the folders, just they will be empty except for a single "tasks" file. Just fyi.

Yes, for now my LOS kernels are unified. I need to update my OOS builds to work for both as well. I will make this clearer for new users.
[OnePlus 3 & 3T Cross Device Development] siankatabg:
Yeah it's strange, but actually I did two exactly same builds with just this commit and the top-app folder and the tunables are created without problems. Without the commit, the top-app folder can't be created with error "no space".

P.s. - The kernel is getting better and better, good work and thanks :)
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
Have flashed now.
[OnePlus 3 & 3T Cross Device Development] liver20:
Have gestures? Like sweep2sleep

Enviado desde mi du_oneplus3 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
No, I dont normally run with gestures. Just not needed imo. But I may add them in so as to not wear out the power button. Request noted.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Tho according to Mr Carl Pei, every button has been carefully paired with its correct slots with full precision so that it doesn't wobble and wear out quickly. :p
[OnePlus 3 & 3T Cross Device Development] habylab:
That's complete marketing spin I'm afraid. Mine is still wobbly
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
No need to say it, we all know haha! :laugh:
[OnePlus 3 & 3T Cross Device Development] liver20:
Dirty unicorns with render Last build

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] Pollie81:
I'm just trying out vertexOS with render kernel and so far it's really good! Can't really comment on battery life but it feels great. Thanks for the rom and kernel.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yea, my old Captivate had a power button that wore out. So with any wake gestures, I could care less since we have the finger print sensor but for sleep, I would like to add the ability for those that have to make their phones stretch longer lifespans than normal. So with that, I will try to add in gestures into the final build.

On a good note, I have fixed the last real issue I had with eas and that was schedutil tunables not sticking after a cores goes offline. So I will be shipping the final release with a personally tunes schedutil governor. Planning on releasing in a couple hours. Cooking dinner at the moment. . . . Mmmmm. . . .
[OnePlus 3 & 3T Cross Device Development] stryker09:
I believe all ROMs who have rebased on top of CAF and/or latest LOS sources (system/core, frameworks/base, frameworks/av) should have all the necessary commits for EAS support so theoretically everyone can try this out as long as their ROM base build is recent enough! :)

Can't wait for the final release! :victory:

Update: [MENTION=5438598]RenderBroken[/MENTION] - so I did a build with your latest T7 sources... top-app still isn't showing up :(
[OnePlus 3 & 3T Cross Device Development] joshuous:
You will need to enable some flags in the device tree as well to get the changes in system_core working
[OnePlus 3 & 3T Cross Device Development] stryker09:
Besides USE_CPUSETS, ENABLE_CPUSETS, USE_SCHEDBOOST, ENABLE_SCHEDBOOST, what else needs to be flagged on?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Most like you are just missing the needed changes in Ramdisk. Flash my final R1 build that I am about to release ontop of your rom you built and check again. No flags you enable will add the needed lines to the ramdisk but my kernel script has them. Most likely you will just need to add them to the ramdisk source you are using.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
LOS-N-EAS-R1-FINAL is here!!!

Things to note:

A metric crap ton of work has gone into this EAS project. I would like to thank the AKT Slack group for allowing me to hijack some of their followers and to give EAS for the OP3(T) a place for discussion. This EAS build would not be where its at right now without the help from you guys. Now to the less important stuff ;)

I have ported Google EAS derivative that is used for the Pixel. Not only Google's EAS but their Experimental branch. I have been able to get it up and running rather well. Side note: I am hoping to port to my OOS-N kernel soon. Not only have I ported EAS I have also added in all the other goodies I normally run with Render Kernel and a few extra. I have added in wake gestures and Sleep2sweep by request since it really made sense. I have put so much work into this build and tested, and re-tested, then tested my test methods to make sure that its working the way it should and that each new change didnt add any performance regressions. I originally set out to get EAS moving for the OP3 since at the time there was not any public work being done on it and I wanted to see where it could go, now, we have roms being build to support it and kernels will flourish as well. I have made the commits in such a way that a user should be able to easy pull in the EAS commits I made. I am sure this will need more testing and I plan on continuing updating this particular kernel for the foreseeable future. Like I have said before, I will be releasing an HMP build for LOS-N next then redoing my OOS-HMP and OOS-EAS kernels. Also, in case those of you haven't realized but since I am using LOS my kernel source is unified and I have made my flashable zip universal as well to accommodate OP3T users as well.

Download

Changelog:

Too big to paste here so check out file: HERE
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Hooray! Just for verification, is Sched the correct governor now instead of Schedutil?
[OnePlus 3 & 3T Cross Device Development] joshuous:
Those will suffice
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Schedutil is the one to use
[OnePlus 3 & 3T Cross Device Development] mysky911:
Still stick to OOS .. can't wait to test your EAS for 4.0.3 ..:cowboy:

No rushing, enjoy your real life, and of cause your self cooking dinner:D

You always show us your positive passion of open source development:svetius:
[OnePlus 3 & 3T Cross Device Development] abhi0502:
Getting lots of fcs on [MENTION=4608158]ZeNiXxX[/MENTION]'s RR rom.

Edit logcat attached