[OnePlus 3 Guides, News, & Discussion] Mostafa Wael:
Just wanted to say ....

HAPPY

NEW

YEAR !!!​

And with that said, I am back in business! Yes you are not dreaming, yes it was just a day away and all i can say is,...the Almighty has just made me baffled again! :victory:

And allow me to tell you that there is a gift coming to you from all of us 4 [MENTION=1515965]patalao[/MENTION] [MENTION=6187429]Asiier[/MENTION] and [MENTION=6773050]Senthil360[/MENTION]

Stay tuned, it will be here shortly (I am having some pizza with the family, I am sure they are enjoying their time as well :) )

FYI, it is BIG!!!

And in other news,

OOS Nougat 4.0 STABLE has been released

for the OP3 (And the OP3T), so that is definitely a nice new year's even gift from OnePlus :good: :victory:

Last but never the least in any way, feel free to tell me any queries I haven't answered in the last day(s) as always.

And once again, thank you thank you thank you :) It was a really bad storm in the house and I am glad it just went away. Perhaps it is New year's eve magic!! :D

Now back to the fun!!

---------- Post added at 11:23 PM ---------- Previous post was at 10:41 PM ----------

I encourage you to dump that mod. It actually could do more harm than good!

---------- Post added at 11:27 PM ---------- Previous post was at 11:23 PM ----------

I am back from my cave on my bike :cool:

https://www.youtube.com/watch?v=EBicn4PqLFY

---------- Post added at 11:36 PM ---------- Previous post was at 11:27 PM ----------

[MENTION=2731014]SREEPRAJAY[/MENTION] [MENTION=4686073]ungeeked[/MENTION] your kind words are definitely appreciated :highfive:

glad the storm just passed away, and now i am seeing the rainbow :) ;)

---------- Post added at 11:53 PM ---------- Previous post was at 11:36 PM ----------

EAS stands for Energy Aware Scheduling, where the whole governor settings + HMP Settings are replaced by one system relying on "scheduler hints" from specifically modded low-level files including specially modded libs and framework patches. Also it is coupled with a DVFS (Dynamic Voltage Frequency Scaling) via the utilised sched-DVFS governor to conserve some battery, since V * I * t = Energy consumed, so at same time of usage, you want to lower the Energy consumed, so the total product of Voltage and Current draw must be decreased, and instead of just focusing on the current draw via frequency scaling (what we see by default in the current setup) EAS aims to achieve better battery through lowering the product of V * I by altering the voltage along with the frequency dynamically based on loads calculation and the frequency used and many other variables.

EAS has been attempted by XDA's recognised developer RenderBroken in his RenderKernel (it is pulled now...) and has been proven to work not as well as intended for some reasons. Hit me if you need to know more.

---------- Post added 1st January 2017 at 12:06 AM ---------- Previous post was 31st December 2016 at 11:53 PM ----------

if you talking out of OnePlus 3, only one other kernel other than RenderKernel had attempted EAS and that was named Nebulix (A merge between my Team Helix members work and Nebula's dev work, now everyone is on his side and the project has been scrapped) and imo the checkpoint reached in this kernel is virtually the same as RenderBroken's checkpoint and, aside from team conflicts between Nebula and Helix, the project was scrapped for the same technical reasons as well.

EAS in the Pixel is a ROM+Kernel project implementation where all the tasks are categorised in 4 main CPUsets: Top-app, foreground, background and system-background. Each CPUset has its own sched settings set for maximum efficiency while maintaining the highest average speed possible. The tasks are categorised based on "sched hints" that come from the ROM via some low-level changes including modified libs and a set of framework patches. Up till this "checkpoint" the EAS is only implemented kernel-sided, which means no ROM-side changes were involved in the implementation of EAS, which also means categorising the tasks is broken and all the tasks are on the same ground (the global floor) receiving the same sched settings, causing inconsistency in the phone's performance and the overall behaviour since the CPUs are often overloaded, and some sched settings can be quite wrong for the foreground tasks, causing some instability, which misses almost the whole point of EAS ruining the efficiency advantage we should have gained. Don't get me wrong, you can still achieve quite good battery stats, but performance most of the time is less than stellar unless you bias the global sched settings fully towards performance murdering your battery life completely. And that's why the EAS implementation in the Pixel duo most likely won't make its way to non-Pixel phones, unless the dev maintains both a ROM and kernel build himself in his free time, which is again virtually impossible.

Hope I answered everyone's question about EAS :)

and Happy new year!