yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Great..

I used engstk's new firmware magisk module to fox the touch responsiveness as well so its perfect..

Only place I found a bit of jank was chrome canary... Other than that no probs! I'll flash the new walt in a bit and see how it turns out..
[OnePlus 3 & 3T Cross Device Development] Pritster5:
First of all, great work. We're going further than ever because of your work. Second, I apologize. I did t know that about the test builds and I'll refrain from doing that in the future.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Just wondering if there is a test version for OOS that I missed. Because the last OOS kernel I could find was from Jan 27. I'm new to EAS, and would like to try it out and get more info on it.
[OnePlus 3 & 3T Cross Device Development] A Sad Napkin:
You're kidding right? This update was mention in the vertex thread.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yes, I believe there is a 4/4 build. Shoujld really be compatible with all builds but his 2/28 TEST build.

What rom you flash ontop of? Thanks for the report!

No sweat bro. I know you meant well. I just want to save some ppl from some headache and who might blame this issue on my kernel instead of a different incompatibility. Thanks for the kind words!

Not yet, I am just finalizing my EAS build for LOS. Once done, I will bring it over to OOS.
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
AOSPextended EAS version by siankatabg.

A bit early still but I'll upload screenies anyway

?

Edit: phoenix aex is the name its titled as in the 3&3t dev forum..
[OnePlus 3 & 3T Cross Device Development] Antsu:
Actually it was different update/test-kernel: ...T47-CLAMP-PELT.zip, hence the question. Those posted here is ...T51-STUNE-PELT.zip

---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------

Ok, sorry for not to mention build date. I was referring to 28th build.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
OK guys,

We (Alot of ppl in the slack groups I am part of) have been working on bringing the best EAS we can. We are experimenting with different input boost values. I have a build of Phoenix AEX that uses an input boost freq of 1113 and sets top-app boost to 10 only during interactions (Touches and flings) and I have a build of Vertex OS using special changes whether its a touch or a fling. A Fling is when you swipe on the screen and then raise your finger off the screen. It is literally like a fling. A Touch is everything else. So for touches Vertex uses 729Mhz and 0 for top-app boost and for flings it uses 1113MHz and 10 for top-app boosting. This approach should be more battery conscious. I think this is a good starting point. I would like more testers to confirm. Also, those new to EAS or those that tried EAS while it was still super beta, this is your chance at seeing what EAS was meant to be on the OP3. This is going to be the future of Android as HMP is deprecated. Links below, as always, please share your findings. That is all I ask in return. Thanks!

Please note that with these two builds, the Rom maintainers will not be accepting any bug reports!

ROM:

Pheonix AEX 4/4

Vertex OS 4/4

PELT (More conservative but I think runs best)

https://drive.google.com/open?id=0B-GVJKBx9-GnbE5ZZlBTSVlTdGc

WALT (More interactive)

https://drive.google.com/open?id=0B-GVJKBx9-GneVBUY09PWkFKLUk
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Gonna try phoenix with walt here.

Did one cycle with walt yesterday like I mentioned. Very similar battery life. About 20-30 mins difference on sot with pelt winning. Walt definitely feels smoother. The second cycle isn't that great as there was a drop from 100-80% as the phone was kept awake for some reason.. But that's probably some other wakelock/app/gplay services issue.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Big things in the works. Of course I have been making leaps and bounds with EAS on LOS but like I said before, all I have been doing on LOS will be used for OOS. I have been able to work around some of the old pitfalls on EAS and I will really happy about. Not only does it make OOS-EAS possible, but it will closely mirror the performance gains I have been able to make with LOS-EAS. I will be rebuilding my OOS-EAS kernel from scratch. I should have some builds as early as tomorrow. Thanks guys for your support! Not just for me but the support you give all of our OP3 devs.

Kind Regards,

Render
[OnePlus 3 & 3T Cross Device Development] keaheng:
Yeah me too. As he said before features will be added after he finish his EAS. No matter how fantastic the kernel work, if the kernel wakelocks are there, the battery will drain so quick and my phone will never go to a proper deepsleep. Maybe only few that suffer from the kernel wakelocks issue. Unfortunately i cant build myself a kernel so I wish he merge those commits from franco soon.
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
I'm not concerned about the blocker actually. It was a one time occurrence. The next cycle was much better.

[MENTION=5438598]RenderBroken[/MENTION] this is my second cycle with phoenix aex that you posted plus WALT.

Could have probably reached 5 hours++ if I didn't use lte in the middle for like an hour plus yesterday (terrible signal).
[OnePlus 3 & 3T Cross Device Development] keaheng:
The number of sot does not show the battery improvement​. People use phone different ways. Get BBS or WLD to count the wakelocks and use the app form store to see the active drain and the idle drain. Sure the more kernel wakelocks count the more battery drains. Its simple.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Guys, if [MENTION=5438598]RenderBroken[/MENTION] deems it as a priority, he will add it. It would help even more to back up your Wakelock claims with screenshots of stats (particular kernel stats from BBS).

The Zenith test builds have been completely rebased to [MENTION=5438598]RenderBroken[/MENTION]'s latest kernel, and I have incorporated Franco's Wakelock blocker. I'll probably release it later today if you guys want to play with it.
[OnePlus 3 & 3T Cross Device Development] the-erazer:
This is over night without charging. Flashed vertex and pelt kernel yesterday evening. Charged to full and over night it doesn't drain much.

Scrolling and everything is really smooth... No lags so far. Will test more and report back..

Sent from my OnePlus3 using vertex 0404
[OnePlus 3 & 3T Cross Device Development] liver20:
This kernel works properly in not eas rom?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
yes you can download and use the HMP version and you are good to go
[OnePlus 3 & 3T Cross Device Development] joshuous:
It works, but not completely. You likely won't have a good experience.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
DELETED. . . Duplicate post
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
My biggest priority for the past few weeks has been working on bringing something completely new to our beloved OP3(T) and other MSM8996 devices. Since the beginning, I knew EAS was the way to go. I also knew the potential. In the beginning I decided to port EAS and just see how it operates. I was able to get it to build but I knew I was missing other parts that Make EAS work properly on a UI/forward facing Operating system such as Android. Since the beginning I was able to get with [MENTION=6745491]joshuous[/MENTION] to help m on the rom side while I could focus on the kernel side. I know I have been neglecting other parts of the OP3 community by focusing on EAS but I ultimately do this work for myself, to learn. I also love to share my work and to teach what I know to anyone who is respectful and asks politely. I have the best users on XDA. everyone here is generally polite and respectful. I think many know that I will do whatever I can if it's in my power to do so and it makes sense. With that, I believe that I have finally been able to really hammer out a solid base for EAS to build on. I will soon be working to release R4 and it will include the many features you all know and love. This also means the wakelock blockers. I like to operate with the motive that most times, less is more.

Also please note that I don't run with any Greenify, Naptime or any other "battery" saving app and I am able to idle just fine and get great SoT. If you are unable to get good Deep Sleep then you may need to remove the harmful app.
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Yeah man, it's amazing whats been done. Bleeding edge stuff that's working like a charm..

Like I mentioned I'm not concerned with wakelock blocking because when it sleeps it's flatline! Doesn't run like hammered dog crap (TM) [emoji14]

Probably useful for some who wanna mess around with it..

There was just that one time that the problem was there and a reboot fixed it :D

All new cycles have been amazing.

Can't wait for what's coming from now onwards :D
[OnePlus 3 & 3T Cross Device Development] the-erazer:
This ROM kernel combination (vertex pelt) runs really great... Device is cool all the time and idle drain is nothing to worry about. The phone is at least on for about 23 hours with 4h15 sot... This is really great for me.
[OnePlus 3 & 3T Cross Device Development] liver20:
[MENTION=221618]ReNDeR[/MENTION]brokren your kernel hmp is amazing, combo with dirty unicorns awesome

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks! Crazy part is I am able to get similar scores with my EAS kernel as well! Thanks for sharing!
[OnePlus 3 & 3T Cross Device Development] stryker09:
Hey [MENTION=5438598]RenderBroken[/MENTION] just thought I'd post that I've been following your work/branches on GitHub and just generally doing a build for myself with your kernel with LOS. I may not have everything on the ROM side yet and I'm still learning on my own but ever since you moved to the EAS 1.2 branch schedutil has been _amazing_ , I don't think I've ever had more than 24h standby but I've been getting it alot since the new branch and words can't say how wonderful it has been :victory:
[OnePlus 3 & 3T Cross Device Development] liver20:
Is possible your kernel with old oneplus camera blobs for roms that not have it like du?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] CroW_D:
Thats the normal behaviour for eas bro no worry you will get great battery life.
[OnePlus 3 & 3T Cross Device Development] pantmunu:
With Walt on latest aex phoenix. Freaking sweet. Real world usage is just awesome.
[OnePlus 3 & 3T Cross Device Development] vampire36:
Hey any update for OOS users like me as to by when they can get a taste of your amazing work :) Waiting eagerly to see EAS and its impact!
[OnePlus 3 & 3T Cross Device Development] mady51:
+100
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
He has pretty much finalized his work for LOS. When he releases the R4 build he'll start on an oos build from scratch because it requires a lot of changes because the room doesn't have the EAS sorry built in to work with the kennel.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Its been a long road of builds, rebuilds, rebuilds of rebuilds, etc. All in all, about 200+ test builds to get where we are at today. I am glad it has paid off massively.

Something is definitely lost in translation. Can you try again? Thanks!

I use DevCheck and enable the overlay. It doesnt check so aggressively. The reason EAS seems to jump all over is that it doesnt use timers and such like with HMP. HMP and interactive use load tracking and timers to set a freq. Tt will remain at a freq for an amount of time till the timer expires and it follows through with the rest of its algorithm. EAS tracks each task (That makes up the workload) and assigns an OPP (Operating Performance Point) for that task. No timer, no guessing, just the proper voltage and freq to complete that task.

I will be releasing two builds when it comes to EAS, PELT and WALT. I am working on a few other things to give EAS a few options for those that want ultra conservative or ultra performance and those in between.

I have started working on this. there is alot more to just adding a completely new Scheduling system. I have to add it in such a way to make sure there is not a piece of code that doesnt belong. For example, a piece of code that over accounts RT (Real Time) and DL (Deadline) tasks. this would mean that the code gets accounted for twice and EAS calculates the wrong freq and voltage. Thus overpowering the tasks and wasting energy. But, long story short, I have started the work. I am planning an Official release of RK-LOS-N-EAS-R4 with all the bells and whistles and once done, I will be bringing over all the fun to OOS.

Also, I need to know if the Freedom rom is a USER or USERDEBUG build. Can I get someone to confirm for me? If not, is there another OOS build that is? I really need to know this so if someone can help me out here, I would be grateful.
[OnePlus 3 & 3T Cross Device Development] A Sad Napkin:
So much information to take in it hurts my brain. Awesome and interesting thread.
[OnePlus 3 & 3T Cross Device Development] cristianvaz81993:
Are this freqs normal with any use in this moment?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
That looks pretty accurate. It's the way the energy model works. It'll try to use the little core before ramping up the big core
[OnePlus 3 & 3T Cross Device Development] weeka89:
EX kernel Manager doesn't read frequencies correctly for EAS now
[OnePlus 3 & 3T Cross Device Development] cristianvaz81993:
Do you recommend other app?

Which config do you recommend guys?
[OnePlus 3 & 3T Cross Device Development] fonlan:
Will update OOS version? It's long time no update for OOS.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yes, there is alot of overhead in the particular view. Imagine, EXKM is having to read the SYSFS file that shows the freq, per core every second and export that info into the app and show it to you. So I wouldn't use any kernel app like that to view freqs, I do use DevCheck and use the Overlay. It is really light and I can watch the freqs idle properly with it and watch freq usage throughout using the phone.

If you read the thread just a few posts back, you would have your answer but since you didnt I will save you more time by just answering:

No

;)
[OnePlus 3 & 3T Cross Device Development] weeka89:
I use cpu float
[OnePlus 3 & 3T Cross Device Development] :
Eas kernel works on LOS rom based on 7.1.2?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
If the ROM in question has an EAS tag on it, or the OP has explicitly stated that the ROM fully supports EAS, then yes. Otherwise, you should flash the HMP variant of RenderKernel
[OnePlus 3 & 3T Cross Device Development] dhantheh:
when are you going to release the version for OOS?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Be patient. He hasn't even finished his r4 build for LOS and AOSP. When that's done he'll start porting to oos
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Give it some time.. He is not sitting still doing nothing EAS is something that needs alot of testing.. It just needs alot of time.
[OnePlus 3 & 3T Cross Device Development] dhantheh:
Thanks, I did not know, I'll keep waiting.

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Would the R3 kernel set selinux to permissive on boot for some reason? I'm trying to track down why I can't get it to boot in enforcing, I removed the permissive script installed by arise, but I can't stop it from booting in permissive.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Real life does become too intrusive sometimes chaps. And he already reached another milestone yesterday quite literally. He is playing with EAS freely on LOS and testing all EAS changes there, to establish a base in order to build his kernel on top for OOS. Once this Base is established successfully, it should be smooth sailing.

Patience.....is a virtue.
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Magisk and EAS-R3 Kernel setting SELinux to permissive

[MENTION=5438598]RenderBroken[/MENTION] Flashing the latest stable release of your kernel (RenderKernel-OP3-LOS-N-EAS-R3.zip) seems to cause SELinux to be set to permissive when I have magisk installed! Do you know if there is there any way to get around this? I'm not sure if it's magisk or the kernel.

I've tried it by itself, and magisk by itself, and both boot as enforcing, but when I have both flashed SELinux boots in permissive! I can flash magisk with EX Kernel and it boots in enforcing, but I'd really really like to take advantage of EAS with Phoenix AEX.

Very confused, I never looked at SELinux state before installing Arise and now I don't know if it was always permissive with these two installed, or if it's only because of the permissive script you can install with Arise. I tried deleting the script, and I've tried totally wiping in TWRP and clean installing many times, all I can think to try now is restoring fully to stock. I wouldn't think that the script should persist at all, anyway, but unless this behaviour is intended I have no idea what else might cause it.

Any help would be hugely appreciated!
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I replied to your PM but thought I would also reply here for others to know as well.

I run my kernel as permissive. Mostly so I can test the kernel without having SELinux throwing curveballs. You can easily set my kernel to enforcing by running in terminal:

su
setenforce 1

This will have to be done at each boot. I may go ahead and set my kernel to enforce but want to make sure all is well before doing so.

Also, I am sure many of you would like to hear that I am just about done with my LOS kernel. I have been doing a metric crap ton of testing. Using the LISA toolkit from ARM. making sure EAS is behaving like it should and I have to say that this has surpassed my expectations. I have barebones test builds that I would like to share for you all to experience. Many many many things have been improved. Once namely being video playback. [MENTION=261663]mostafa[/MENTION]wael found:

Around 50% of the time is spent on either the 307 MHz or the 422 MHz frequency. around 20% of the time is spent on 652 MHz and some very rare spikes to frequency steps beyond that step of 652 MHz, topping at 844 MHz for precisely 1 second in a 20 minute stream session.

I can confirm as well.

I am getting closer to releasing my final R4 for EAS. I am planning on releasing this weekend.
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Really? That's so weird! I've tested it over and over the past day and it's ALWAYS in enforcing until I flash magisk as well. Same in reverse, it only boots in permissive with both magisk and the kernel installed. Do you have any idea why that might be? init/su scripts?

Also, can I beg you to release a version of your final that is supposed to be enforcing? I would donate just for that, honestly. If I can get this setup I'm looking at now to boot in enforcing with both Magisk and an EAS kernel, I would be ecstatic!

Could anyone try this out for me if it's convenient, to see if it happens for them? I've wiped it as clean as I can without going back to stock over and over, I have no idea why I'm getting such a strange occurrence. I can totally understand it being in permissive if it's supposed to be, but not why it would *only* be in permissive once I've also flashed Magisk (12).
[OnePlus 3 & 3T Cross Device Development] masri1987:
no op3t? but unified?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Definitely runs in the op3t as well as the op3t. Unified so, just flash it to either device and it will function. We've been testing his kernels over in the vertex slack group and they work for both devices perfectly.
[OnePlus 3 & 3T Cross Device Development] masri1987:
is there a version newer than the one in jan?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Not currently. He's busy finalizing the new build all the goodies on the new was base. Patience
[OnePlus 3 & 3T Cross Device Development] Skinpipe:
I'm using pelt from page 101 so yes there is a newer build its solid as a rock but it's a test build
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Yes, but he clearly didn't approve of the test build being released and asked that we wait until the final release. Also, from his post it seems most likely that he is not running the test build of Vertex which this test build were designed and tested with
[OnePlus 3 & 3T Cross Device Development] Skinpipe:
Well im using it and its absolutely sweet the battery life is ridiculously good but thanks for chiming in im running latest stable build of Phoenix and the pelt test build, if render posted a link to it then it's flashable and free to use, so...

Render posted the links himself and said dont report on the test builds go back and read what is said

"clearly didn't approve" what are you on about?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
On page 101 he told the guy that reposted the links from the vertex slack that he didn't want them posted.

The quoted text from Renderbroken was from the slack group. He didn't post it in this thread.

I'll agree, it's amazing but not something for this thread.
[OnePlus 3 & 3T Cross Device Development] JohnHorus:
Issues getting boot scripts to run

If you just flash it and try it out you're not hurting anyone, but he doesn't want to support questions on that particular build as he already has enough to support. So it's probably best if we just don't post about it at all at this point as it's in the past and we almost have a finalized build of goodness. Can PM people if you really wanna talk about it.

In other news, I managed to get the EAS-R3 to boot in enforcing. Init/Su/post-fs-data scripts didn't seem to be running, but I guess magisk has another boot-script directory called service.d, and running setenforce 1 from that folder worked. I have no idea why the other directories don't seem to work, it may be just certain commands that don't run properly? I tried adding a command to echo some text to a file in /sdcard/ but it never appeared when run from post-fs-data OR service.d (probably the wrong command or something), so when I noticed that enforcing WAS actually taking when run from service.d I just stopped for the night, lol.

post-fs-data is apparently loaded early in boot so maybe that has something to do with it, but I would think init.d or su.d would still work if the kernel supports them (didn't test init and su as thoroughly). If Render puts out a version that's enforcing when it's all done being tested, this is moot, but until then if anyone wants to do the same, note that I never tried it without this text prior to setenforce 1 in the service.d script, so that may or may not be necessary.

[MENTION=5438598]RenderBroken[/MENTION] Do any of my confused fumblings make sense? Should init, su, or post-fs-data scripts be running? My only major mods to Phoenix AEX 4.1 are the R3 EAS kernel and Magisk 12. If any of this seems unusual, I would be happy to take some time and figure out how to test it more thoroughly if that could be helpful. Thanks again for all this work you put out! = )
[OnePlus 3 & 3T Cross Device Development] Hecke92:
I am f5ing this thread every 5 minutes since yesterday. Any news?

So excited [MENTION=5438598]RenderBroken[/MENTION] thank you so much :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
That doesnt sound right to me. Lets see how the default behavior of my soon to be released R4 works for you. Can you let me know?

Sorry bro, work got in the way then other work sprinkled in some work. So you know, work. lol I am working on releasing asao this very moment!
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Apologies if this has been asked before:

Can one use EX Kernel Manager or is it only Kernel Adiutor ?