[OnePlus 3 Guides, News, & Discussion] Asiier:
The Future of this Project and some other stuff in general

Hey guys, have been a while since my last post...

I've been pretty busy with college and other stuff that have been going on in my life, in addition to that I was no longer that motivated for this project as they are practically no more things that can be done for improving it.

Anyways, I'm here to have a little talk with all of you guys, so let's start!​

Is this project dead? Are more updates to come?

No, it's not death at all, in fact, our Slack community (which I'm really proud of) is tremendously active.

And the updates will come but not as often as they were before. Now let me explain all this.

Basically, there are not more things we can do for improving this project.

We have tried a lot of different approaches, methods, etc trying to get the best out of our phone, and I firmly believe we did get the best out off it. But there are simply not much stuff to improve from the Profile's perspective unless a revolutionary parameter appears or something like that (not EAS, I'll talk about that later on)

I'm really happy about how my profiles works, each of them fits a specific scenario and usage, I feel they suit really well that scenario and there are little to no things I'd improve on them and I'm pretty sure my mates [MENTION=5060769]Mostafa Wael[/MENTION] and [MENTION=1515965]patalao[/MENTION] think the same about theirs.

The Futere is now and its name is EAS

From a huge fan of Interactive governor switching to EAS and its Scheduntil or Sched governor haven't been easy at all.

If you still don't know what's EAS I'll let my mate [MENTION=6745491]joshuous[/MENTION] give a brief explanation on EAS:

For more information on EAS make sure to check Vertex ROM thread, Render's Kernel thread and EAS Linaro webpage. All of them have tons of useful and really interesting information about EAS.

So now, my opinion about it!

As I said before, I like Interactive (Keep in mind Interactive != HMP and SchedUntil != EAS), I like it because how customizable it's, for the possibilities it gives to the user which I believe is the essence of Android, being able to customize everything as you like.

What's the problem with EAS then? Well, EAS it's supposed to be a no-fuss no-mess system that can effectively and dynamically optimize energy efficiency.

That means little to no control for the user over, for example, the freqs that would be used during certain load.

This could be changed, of course, but not only defeats the purpose of EAS but adding that would create a huge overhead increasing both latency and power draw, and that's exactly what we don't want.

And you may ask then; What's so wonderful about EAS?

In words of [MENTION=5438598]RenderBroken[/MENTION]

Hella fast and with a really consistent battery life.

But once again, I feel like it falls behind HMP in certain aspects.

As you cannot really customize it, you cannot "limit" it for achieving better battery or "Freeing" the CPU for having beast performance.

EAS is really Balanced, it gives great performance and battery, but it cannot YET be pushed to the limits. Getting better battery at a cost of performance or vice versa.

This is both good and bad, some ppl would say it's good to make it stable and good as it's with stock settings, I totally agree but I also believe that Android is all about customization and therefore a user should be able to modify this in order to fulfil their preference, for example, better battery.

I hope I've explained myself properly and everybody is able to understand me hahaha

AKT and EAS??

Short answer, No but maybe

Long answer, As I said before, EAS and both of its governors SchedUntil and Sched are little to no customizable even the most advanced settings give us little control over how the CPU behaves.

It doesn't make much sense as right now, maybe in the future we will be able to work something around.

As today, the only way to really control this is sort of things are modifying the inner layer of the Kernel and not the outer layer as it's on HMP. So building a Kernel is the only way :p;)

UPDATE!

Well, I think I have talked to everything I wanted to talk about. I have to give all of you guys huge thanks for the awesome support you have given to this project!!!

If you guys have any question make sure to use [MENTION=6187429]Asiier[/MENTION] so I can get notice, If you don't I most likely won't see it.

Also, expect and update around the next week, it will add some extra functionality and some last adjustments to some profiles​