[KERNEL][8.x][EAS] AL-ice-KERNEL [CLANG][ARM64][SANDERS]

[Martichou]

Removed

 

[Martichou]

Reserved

So this post will be dedicated to information about EAS in general.

EAS is a completely different breed compared to the conventional HMP system, where it serves an entirely different purpose of achieving the optimal balance between performance and efficiency, with the latter taking the top spot. EAS achieves that via cleverer tasks placement, by which the system determines which is the more efficient cluster for the task to be processed by, as well as categorising the different tasks into cgroups (top-app, foreground and background, in order from highest priority to lowest priority respectively) by which each cgroup receives its sliver of the available firepower (cpuset). EAS also offers the capability of inflating the perceived load, that's determined by the load trackers, of the task in any of the cgroups via its schedtune.boost setting, and whether the task should be processed by all the cpu cores available or only by the cluster the task has been placed on via its schedtune.prefer_idle setting. One of the key features of EAS is lifting almost all the processing from the governor to the CPU scheduler (no it is not the I/O scheduler, something different) and letting it take much much more control, leaving the CPU governor to only do the frequency determination part, which unsurprisingly relies heavily on data supplied by the scheduler. With all that said, it is easily deduced that EAS is not all about governors and governor settings and the like, rather a much cleverer solution that serves the purpose of seeking the best balance between performance and efficiency, and to ensure the CPU is not overdoing a task or the CPU governor is overshooting a simple task, which would attribute to needlessly draining a lot of power as a natural consequence. EAS is about ensuring you get the smoothest UI possible while retaining as much power as possible. However, that does not mean that EAS is lame poor when it comes to performance. Sometimes, if not in most cases, this cleverer tasks placement makes tasks get processed faster, a point that is already proved quite well by the EAS-supporting non-OOS based custom ROMs like VertexOS, ZeNiTy-RR and PAEX. Conserving battery does not necessarily mean crushing performance. This explains that app launches are on-par with HMP if not ahead of it sometimes.

Now on to your question. After going through that brief explanation of EAS, i think your question is actually invalid, since it is not an apple-to-apple comparison anymore. EAS seeks for the optimal balance between performance and efficiency. Should there be a commit to improve performance while not being at the expense of efficiency, EAS should have that stuffed in, whereas HMP is prioritising performance higher than efficiency by design. What Burnout does is taking HMP and making it even more performance oriented, hence it is very unlikely to face micro lags with it. However, HMP still misses the cleverer tasks placement, which can show its canines if you have so much processes going in the background, where in that area EAS takes the lead quite noticeably.

Conclusion: You should try and see what suits you more. But something i can safely say is, EAS is more than satisfactory when it comes to performance from the perspective of a man that always seeks the best performance available, and with the battery gains you yield with EAS, it can go better.

Hope i helped and clear the confusion.

Thanks to @Freak07 for the message.

 

[Martichou]

Reserved

This post will be dedicated to information about Wireguard in general.

WireGuard is a next generation secure VPN tunnel for the Linux kernel, with modern yet conservative cryptography and simple design principles. It is meant as a replacement for OpenVPN and for IPsec, and generally has better performance and security characteristics than both. It also is much easier to use. The whitepaper was peer reviewed for NDSS17 and the protocol itself has been formally verified. Since it lives in the kernel, it not only is very fast, but it is able to integrate in clever ways that are quite nice for battery life and overall smoothness. There are already commercial VPN providers offering services using WireGuard, and it is very easy to run your own WireGuard servers as well.

How to use?

0. Make sure you're running a ROM or kernel that supports WireGuard.

1. Install the WireGuard app: https://play.google.com/store/apps/details?id=com.wireguard.android

2. Sign up for AzireVPN: https://manager.azirevpn.com/en/auth/register

3. Generate and download a configuration file from: https://www.azirevpn.com/cfg/wg

4. Import it into the WireGuard app using "Add from file"

5. You're done

 

[mrbojangle69]

My first impression is that the overall performance has improved, lightning fast responsive touch. Glad to see sound control added, finally I can set up the output speaker desired level when needed. Changed the tcp congestion to westwood as my preference over cubic.

Good job done with the Alize kernel, congratulations to the developer.

Enviado desde mi XT1805 mediante Tapatalk

 

[pico hackr]

Thanks for this super cool features , testing

Sent from my XT1804 using XDA-Developers Legacy app

 

[DonSolo]

Using with Pixel Experience 64bit.. Never felt so much speed and fluidity in my hand before. With stock settings it's executing everything before I left my finger. Battery seems good so far too

Sent from my XT1806 using Tapatalk

 

[mrbojangle69]

Pixel Experience rom + Alize kernel
Most of the time wi-fi, G+, Tapatalk, Telegram, Chrome, YouTube... normal usage.



Enviado desde mi XT1805 mediante Tapatalk

 

[jrubi.arseven]

Pixel Experience rom + Alize kernel
Most of the time wi-fi, G+, Tapatalk, Telegram, Chrome, YouTube... normal usage.



Enviado desde mi XT1805 mediante Tapatalk

Did you tweak the kernel if so in what way? Or did you flash and forget?

 

[mrbojangle69]

Did you tweak the kernel if so in what way? Or did you flash and forget?

The only thing I tweaked was the tcp congestion, changed it from cubic to westwood. The rest of the options are the default set up. Honestly I don't think that change to make the difference though.

Enviado desde mi XT1805 mediante Tapatalk

 

[AL_IRAQI]

Awesome work buddy, ill give it a go

 

[infixremix]

Did you tweak the kernel if so in what way? Or did you flash and forget?

I recommended using schedutil Governor and maple Io scheduler , This is based on performance and battery factor

 

[ElectricDrifty]

Will this work with cosmic os?

 

[yackback]

Will this work with cosmic os?

Is cosmic 64 bit and Oreo...?

 

[Martichou]

Will this work with cosmic os?

If cosmic is 64 bits Oreo, it will work.
This kernel work on any Oreo rom which is 64 bits, so approximately all of our 8.x rom.

 

[navnit75]

Yea it's working in cosmic, battery life is osm......

 

[jhonnyx1000]

Using with Pixel Experience 64bit.. Never felt so much speed and fluidity in my hand before. With stock settings it's executing everything before I left my finger. Battery seems good so far too

Sent from my XT1806 using Tapatalk

Which ROM are you using?

 

[lilcdroid]

Which ROM are you using?

Just a hunch but he did say he was running Pixel Experience in his first sentence.

Sent by way of magic

 

[Martichou]

AlizeEAS - SANDERS

What's new? (vSeven)
- Upstreamed to 3.18.92
- EAS is reimplemented from Google's commits.
- ‎Schedutil is default cpu governor.

Download: Click here

 

[petes12]

Awesome kernel, good job man.

 

[juniorhonorato1986]

tankks