[Kernel] RenderZenith OP3/T [OOS-O-EAS-V1.3.0][25 Oct 2018]

for OOS-O​

This kernel is a joint collaboration between @joshuous and myself. Our primary goal is to deliver a fast, smooth and stable kernel with Energy Aware Scheduling (EAS). We have spent countless time backporting, experimenting, tuning and improving our understanding of EAS in our kernels. We aim to keep our kernel slim on features, adding only what we believe is essential.

It is also our desire 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.


Features:
* Energy Aware Scheduling (EAS) backported from Android Common Kernel 4.4
* Many backported scheduler patches from 4.4 kernel
* Dynamic SchedTune Boost
* Wireguard
* Others and more to come...


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

Kernel Downloads:
RZ-OP3-OOS-1.3.0-181025-a6ba708e.zip
RZ-OP3-OOS-1.2.0-180910-80c6d0c2.zip
RZ-OP3-OOS-1.1.0-180724-0e8f55f2.zip
RZ-OP3-OOS-1.0.0-180613-2f2d48c6.zip

Instructions:
* Boot into Recovery
* (Recommended) Make a complete backup of everything! At least backup BOOT via TWRP
* If you're not coming from completely stock OOS kernel, please dirty flash OOS first
* Flash RenderZenith!
* Reboot

Reporting Bugs (please read):
* Make sure you're not using any tweak apps (Greenify, Naptime, anything else related), otherwise no support will be given. If you have an issue, disable all your tweaks first and see if that fixes your problem. Otherwise, flash the stock kernel and see if you can reproduce it as well.
* If you previously flashed another kernel, make sure you dirty flashed the full ROM zip before flashing RenderZenith kernel.
* Logs! Please provide dmesg kernel logs via Syslog app. If you experienced a kernel panic (system crash/reboot) please provide all ramoops file in /sys/fs/pstore/


THANKS!!!!
* The kind people who keep this project alive
* Everyone who supported us throughout our projects
* @joshuous for his partnership and collaboration with our current projects and many more to come. The future looks bright!


Source Links:
https://github.com/EAS-Project/op3-oreo-kernel
https://github.com/EAS-Project/AnyKernel2

XDA:DevDB Information
[Kernel] RenderZenith OP3/T [OOS-O-EAS-V1.3.0][25 Oct 2018], Kernel for the OnePlus 3

Contributors
RenderBroken, joshuous
Kernel Special Features: Energy Aware Scheduling

Version Information
Status: Testing

Created 2018-06-13
Last Updated 2018-10-25

RenderZenith v1.1.0 released! (27 July 2018)

RenderZenith v1.1.0 release for OOS!

Please dirty flash OOS (stable/beta) before you flash this!

Changes:
* Upstreamed to Linux 3.18.116 via Android Linux Stable (thanks @nathanchance!)
* Systemless build. You can now use ExKM and FKM to flash. You can now restore boot.img of OOS if you want to return back to stock OOS.
* New Dynamic Stune Boost changes (see writeup below)
* Enabled cpu-boost for Big cluster to reduce first frame janks
* Disabled CONFIG_CC_OPTIMIZE_FOR_SIZE
* Added option to disable MSM Touchboost (or more accurately the ability to disable CPU frequency boosting via BoostFramework)
* Reduced wakelock duration for qcom_rx_wakelock (I won't block this though)
* Added DTS Eagle and Audiowizard integration for IceWizard mod support. (Refer to https://xdaforums.com/apps/magisk/unity-icewizard-t3776470) Take note that I don't provide support for this mod.

Systemless
As this is a systemless build, there might be a possibility that WiFi might break if you use certain Magisk modules due to bind mount conflicts. If you face this issue, please figure out which module causes the breakage and let me know. Reports without some form of helpful info will be ignored.

New Dynamic Stune Boost changes
Like with many CAF-based OEM ROMs, OOS uses CAF's BoostFramework. BoostFramework detects various contexts, such as app launches, swipes, etc and triggers different boosting configurations. Besides CPU Frequency boosting (aka MSM Touchboost) it also triggers Scheduler Boost (called sched_boost in the kernel), which pushes tasks to the Big cluster for higher performance. It toggles sched_boost by writing to /proc/sys/kernel/sched_boost. sched_boost was a HMP/corectl feature that I removed in my EAS bringup because it interfered heavily with the EAS task scheduling system. However, I have brought it back (/proc/sys/kernel/sched_boost is back) but altered it to perform Schedtune boosting for top-app tasks instead. Whenever you scroll, fling or launch apps, BoostFramework will now cause schedtune boost value to dynamically change to the value that you configure in the new /dev/stune/top-app/schedtune.sched_boost file (Please read this carefully. Several testers reported it not working because they read the file name incorrectly and modified the wrong file :S). Take note that changing the other schedtune.sched_boost files in foreground/background/system-background/etc will do nothing because I did not configure them to be used.

Why add this new sched_boost when we already have dynamic_stune_boost in cpu-boost kernel driver?
The dynamic_stune_boost that is triggered by cpu-boost and does the same thing as /dev/stune/top-app/schedtune.sched_boost (and it does it faster too!). However the cpu-boost version has a limitation:
- Fixed boost duration for cpu-boost. Comparatively, the sched_boost variant will automatically boost and unboost at the start and end of a fling/app launch, respectively. So you don't need to mess around with boost duration on the new sched_boost variant.

The cpu-boost and sched_boost variant of Dynamic Stune Boost complement each other, and it is hence not a "choose one only" problem. The following should clarify:

cpu-boost:
+ More responsive than BoostFramework
+ Triggers when tapping or dragging across the screen (e.g. typing)
- Fixed boost duration. Needs to be configured to meet your needs.
- Does not trigger for app launches and non-touch events

BoostFramework:
+ Automatically manages boost duration
+ Triggers for app launches, swipes, flings, etc
- Does not trigger on taps (e.g typing)
- Slightly less responsive to boost compared to cpu-boost

With this new schedtune boost, you can now imitate the Google Pixel's boosting completely (although it might be overkill for power consumption imo):

• cpu-boost duration: 1400ms
• cpu-boost frequencies: ~1.1GHz for both clusters
• cpu-boost dynamic_stune_boost: 50
• /dev/stune/top-app/schedtune.boost: 10
• /dev/stune/top-app/schedtune.sched_boost: 50

Download
RZ-OP3-OOS-1.1.0-180724-0e8f55f2.zip

RenderZenith v1.2.0 released! (12 Sep 2018)

RenderZenith v1.2.0 release for OOS!

More delayed than I hope it would be, but here you go!

Changes:

• Upstreamed to Linux 3.18.122
• More performance-oriented SchedTune boost changes
• Added USB Fast Charging feature (charges at 900mA instead of 500mA on supported connections). Use at your own risk. Toggle via /sys/kernel/fast_charge/force_fast_charge

Download
RZ-OP3-OOS-1.2.0-180910-80c6d0c2.zip

For Devs that are interested in porting EAS:

Hey guys! Just like we did for MSM8998 Devices, we took all the EAS commits that make up RenderZenith and pulled them into their own repo. This will allow those interested to port our EAS work into their own projects! Note that you may have to adjust the Energy Model commit to fit your project.

Source:
https://github.com/EAS-Project/msm-3.18

We decided to hold off on making our kernel system-less but that will be incoming soon. We just wanted more time to test it out before our first stable release. Also, we will be bringing in all the features RZ users have come to expect. We are thuroughly proud of this release. It embodies the learning and testing we have done on the OP5. With each iteration we step are game up higher and higher and I feel that it shows.