Render Kernel [OOS-N-EAS-R1-T26]

[RenderBroken]

for OOS-N​

/*  *** Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, 
* or you getting fired because the alarm app failed. Please do some research 
* if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* BOOM goes the Dynamite
*/

I am releasing this kernel because I like to share my work and have had requests to do so and, lastly, because we needed yet another kernel released for our beloved OP5! I started out at XDA because I wanted to learn and share what I have learned. My goal with this kernel is to be a very fast and stable build that offers some things that the other kernels do not. I also want to initiate Development Discussions among the community. This will be a noob friendly thread as long as users follow two rules. First is to do some research before asking. Most likely your question has already been asked. If not in this thread then in another. Remember to always search first! Second is BE RESPECTFUL. You do these two things and even the most hardened Dev will assist you.

Wanna be notified of an Update? Here is my PushBullet Channel!!
https://www.pushbullet.com/channel?tag=renderkernel

Current Features
General List:

* EAS Only
* Built with LINARO 4.9.x
* Wake Gestures


I recommend Kernel Aduitor/EX Kernel Manager for making kernel changes

Kernel Downloads:
Test Build

Instructions:
* Boot into Recovery
* (Recommended) Make a complete backup of everything!
* At least backup BOOT via TWRP
* Flash Zip
* Reboot

THANKS!!!!
First I want to say thank you to everyone who has answered my questions and responded to my pm's when I know they are busy with their own lives. Pretty much everyone I have come into contact with here on XDA has been truly helpful and respectful. Here is a list of people that had helped me in one way or the other:

joshuous, Neobuddy89, ak, myfluxi, Dorimanx, Savoca, Faux123, DespairFactor and Many More!

Thank you guys! Without your contributions to the community we would not have the level of performance, stability and interaction that we have today

Special Thanks!

Donators: @nfin1te, @MrDarkKV, @V1TRU, @Really now @erad1

Source Links:
https://github.com/RenderBroken/OP5-OOS-kernel
https://github.com/RenderBroken/RenderKernel-AnyKernel2


XDA:DevDB Information
Render Kernel [OOS-N-EAS-R1-T26], ROM for the OnePlus 5

Contributors
RenderBroken, joshuous
ROM OS Version: 7.x Nougat

Version Information
Status: Testing

Created 2017-07-20
Last Updated 2017-07-26

 

[RenderBroken]

Reserved

An amazing write up by a talented dev @joshuous:

PELT and WALT

Time for me to flex the analogy muscles.

Just to set things straight, PELT and WALT are different load tracking metrics that try to determine the load of the system. The load will eventually be used by the frequency governor to set the frequency. Think of them (the load tracking metrics) as an employee who is dedicated to announcing how quickly customers are coming into your burger restaurant. The frequency governor is the burger chef, who isn't able to see the number of customers entering, so he has to rely on the announcer in order to know the rate at which he is making burgers. The announcer can say that there are "many" customers, and the chef has to decide how fast to make the burgers based on how he interprets "many".

One announcer can say that 10 customers is "many", while another may say that 20 is "many". An announcer may also attempt to predict the number of customers that will enter based on how many he sees at the current point in time. In this way, burger output is more 'bursty'. For example, there are 10 customers ("many"), then no customers ("none"), then 15 customers ("very many"). The chef works hard, then thinks he can take a break for a moment, then suddenly has to work like crazy to dish out burgers for 15 customers. An oversimplified analogy to WALT.

On the other hand, another announcer may observe a trend of customers and apply some prediction to guess how many customers might come through the door. Using the same customer sequence as before, he may instead tell the chef "many", "some", then "many". So the chef may make burgers even when there are no customers, in anticipation of future customers, but he won't be worked so darn hard all of a sudden. This is less bursty and more consistent. An oversimplified analogy to PELT.

In the same way there are different chefs (e.g. Sched and Schedutil). They have different interpretations of what "many" means to them. That's why their burger outputs may be different even when having the same announcer.

So which is better? It all boils down to your workload, and even so it is difficult to make a conclusion. All I can say is that you must test each mechanism for over a week and check your active drain rate (Ex Kernel Manager is good for this). Active drain rate is a much better measure than SOT. And make sure to keep jumping back and forth between the two to account for anomalies.

Edit: On another note, to complete the analogy... Interactive and HMP is more similar to the chef being the announcer as well. Except for he is able to see less than a dedicated announcer can. I.e the chef (interactive governor) can't look at the queue outside his restaurant but only the ones in his restaurant (so he is partly blind). A dedicated announcer can look at customers inside and outside the restaurant though.

Do note that this has little to do with EAS per se. EAS is a different beast that focuses on optimizing which customers is assigned to which chefs. I'll probably write the analogy for this another time if there is a demand for it

 

[RenderBroken]

Reserved

This first build is just a test build. So far Its stable. Please report back any issues you are having. I have had to do a major reworking of the kernel source to get EAS to compile properly. I also had to build the Energy Model from scratch and will be making further adjustments as we go along. I have way more planned for the OP3/OP5. Right now this is only for OOS based roms.

 

[Jsilver73]

This looks fascinating - I love the way you have written this so that even the biggest noob like me can start to understand

 

[Paddybecks87]

Hell yeah. I've been waiting for this! Thanks a bunch, Render! I've just flashed this beauty and I'll report back immediately if anyhting weird occurs.

Thanks again! Running beautifully smooth so far.

 

[DespairFactor]

Hi

 

[RenderBroken]

This looks fascinating - I love the way you have written this so that even the biggest noob like me can start to understand

That is the point. This is a learning centric thread. As long as ppl search I will generally answer any questions.

Hell yeah. I've been waiting for this! Thanks a bunch, Render! I've just flashed this beauty and I'll report back immediately if anyhting weird occurs.

Thanks again! Running beautifully smooth so far.

Thanks guys! I too running this build an I am very happy with the outcome. I only had to remove about 27K lines of code before adding in the EAS changes lol. So I am surprised that it is working so well already. EAS is why I bought the op5.

 

[RenderBroken]

Hi

Yo

 

[dukat0s]

great work as always my friend @RenderBroken ! ty for your hard work i wish u the best to slack group too cya around !

 

[DespairFactor]

Yo

Does this fix calling 911?

 

[nevermorenorless]

Omg eas is here!!!

 

[opensource4life]

Kernel running great so far, thanks for the good work! I did want to let you know that native double tap to wake is not working. Other than that, it's doing awesome.

 

[RenderBroken]

Hi

Does this fix calling 911?

No, but it does walk your dog. Even if you don't have one.

Kernel running great so far, thanks for the good work! I did want to let you know that native double tap to wake is not working. Other than that, it's doing awesome.

Thanks. I still have a few eas things I wanted to accomplish before bringing the rest. I may do so sooner than later though.

 

[mohammed510]

Does this fix calling 911?

No, you'll have to call 116 instead.

Hold your phone upside down and you'll get it!

Sent from my ONEPLUS A5000 using Tapatalk

---------- Post added at 05:30 AM ---------- Previous post was at 05:28 AM ----------

This first build is just a test build. So far Its stable. Right now this is only for OOS based roms.

Ready to test on Carbon rom anytime.


Sent from my ONEPLUS A5000 using Tapatalk

 

[ZeppeMan]

This is basically stock kernel with eas right? So far everything is running great!

Keep it up!

 

[MrPepperino]

Thanks for Kernel. Just installed and will report back.

 

[ilia1985]

Good to see you here Zach

Sent from my OnePlus5 using XDA Labs

 

[ponkz]

Downloading.. i'll be back in few days :victory:

 

[joshuous]

The fun begins!

 

[ponkz]

Im having a little decrease performance in game loading etc.. ist just me or is this the EAS working?