[Kernel][21.08.2021][4.14.243][Android 11] Kirisakura 1.3.9_R for OP7/Pro aka Guacamole

[daniel84cs]

Thanks again for your work, it works great on stable (OP7 Pro), rock solid. I was wondering if it was possible in the next versions to align the core prime to the snap 855 plus, then have 2.96 GHz instead of 2.84?

 

[Freak07]

Thanks again for your work, it works great on stable (OP7 Pro), rock solid. I was wondering if it was possible in the next versions to align the core prime to the snap 855 plus, then have 2.96 GHz instead of 2.84?

no it´s not possible to change the max cpu freq on modern qcom SoCs. It´s restricted at hardware level for consumer chips.

 

[daniel84cs]

no it´s not possible to change the max cpu freq on modern qcom SoCs. It´s restricted at hardware level for consumer chips.

Thanks for the reply.
I did not know. Thanks again for supporting this device, F2FS works great and guarantees a great boost for apps. Before flashing your Kernel my wife's Mi9T (F2FS) opened COD before mine, now my OP7 Pro is a rocket, it consumes less battery and it is evident during use the thermal and performance optimization of the SOC. Great job, great.

 

[Freak07]

Thanks for the reply.
I did not know. Thanks again for supporting this device, F2FS works great and guarantees a great boost for apps. Before flashing your Kernel my wife's Mi9T (F2FS) opened COD before mine, now my OP7 Pro is a rocket, it consumes less battery and it is evident during use the thermal and performance optimization of the SOC. Great job, great.

happy to hear that. enjoy

 

[uhh186]

Hi Freak,

I installed R_1.1.1 on a clean install of android 11 on a 7 Pro and I must say once again you have outdone yourself. It was immediately noticably better and I haven't had any deal-breaking issues.

(Edit: I'm apparently a bit slow and didn't notice you posted an updated version - I'm gonna try that out now but the below is for the previous version)

In fact I've only seen one problem so far, and it's with k-lapse. Nightmode doesn't seem to trigger at the set start time, but if I toggle "vision comfort" (the new os level night mode) it will immediately activate and I can then turn off comfort mode and enjoy k-lapse. It doesn't seem to have any issues turning itself off in the morning, only starting.

(Edit 2: behavior appears to be the same on R_1.1.2)

Proximity sensor works great for me.


Thanks for the great kernel once again!

-----


Btw as an unrelated aside for anyone wanting to upgrade to 11 but worried about all the problems people have been talking about, I'm only one anecdote but I haven't had any problems on a clean install. Freshly formatted F2FS data as well. I'm no developer but I would be inclined to say most if not all issues with android 11 are from some kinda data corruption in certain scenarios when upgrading from the previous OS version that they missed due to the vast array of possible data states across everyone's phones.
Anyway, I'm sure there'll be an updated 11 soon regardless.

 

[Jerreth]

apologies if this has been answered and i believe i already know but.... i noticed that f2fs works with this kernel and android 11 but, is there anyway to switch to f2fs after being on android 11 already? or do i need to revert to a version with with working twrp to switch over?

 

[Freak07]

Hi Freak,

I installed R_1.1.1 on a clean install of android 11 on a 7 Pro and I must say once again you have outdone yourself. It was immediately noticably better and I haven't had any deal-breaking issues.

(Edit: I'm apparently a bit slow and didn't notice you posted an updated version - I'm gonna try that out now but the below is for the previous version)

In fact I've only seen one problem so far, and it's with k-lapse. Nightmode doesn't seem to trigger at the set start time, but if I toggle "vision comfort" (the new os level night mode) it will immediately activate and I can then turn off comfort mode and enjoy k-lapse. It doesn't seem to have any issues turning itself off in the morning, only starting.

(Edit 2: behavior appears to be the same on R_1.1.2)

Proximity sensor works great for me.


Thanks for the great kernel once again!

-----


Btw as an unrelated aside for anyone wanting to upgrade to 11 but worried about all the problems people have been talking about, I'm only one anecdote but I haven't had any problems on a clean install. Freshly formatted F2FS data as well. I'm no developer but I would be inclined to say most if not all issues with android 11 are from some kinda data corruption in certain scenarios when upgrading from the previous OS version that they missed due to the vast array of possible data states across everyone's phones.
Anyway, I'm sure there'll be an updated 11 soon regardless.

Thanks for the kind words enjoy the kernel.

This sounds like the sde layer klapse uses might be occupied with vision comfort. Nots sure something can be done about that if the display Hals/framework on OOS now work that way.

I’ll take a note and think about it! Thanks for the report!

OOS 11 runs pretty well for me too. I didn’t face most of the bugs others seem to report.
It’s always difficult to tell the difference of bugs that affect users, because root allows them to do something they shouldn’t or if it’s due to other things.

apologies if this has been answered and i believe i already know but.... i noticed that f2fs works with this kernel and android 11 but, is there anyway to switch to f2fs after being on android 11 already? or do i need to revert to a version with with working twrp to switch over?

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

arter97.com

I used the zip here. Beware, it will format data entirely. Everything on the phone will be gone.

Flashed it via fkm and worked without issues. arter told me fkm is tested, so no idea about exkm.

 

[Jerreth]

Thanks for the kind words enjoy the kernel.

This sounds like the sde layer klapse uses might be occupied with vision comfort. Nots sure something can be done about that if the display Hals/framework on OOS now work that way.

I’ll take a note and think about it! Thanks for the report!

OOS 11 runs pretty well for me too. I didn’t face most of the bugs others seem to report.
It’s always difficult to tell the difference of bugs that affect users, because root allows them to do something they shouldn’t or if it’s due to other things.

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

arter97.com

I used the zip here. Beware, it will format data entirely. Everything on the phone will be gone.

Flashed it via fkm and worked without issues. arter told me fkm is tested, so no idea about exkm.

wow thanks very much will i need to re root after the format? if so i expect i will just use the patched boot.img from somewhere in the forums lol

 

[lil_kujo]

wow thanks very much will i need to re root after the format? if so i expect i will just use the patched boot.img from somewhere in the forums lol

You wouldn't need to re-root since you are not re flashing the boot, your are just formatting data so root should stay since your boot.img is still rooted.

 

[Jerreth]

Ok conversion to f2fs went flawlessly took awhile to transfer 40GB back and forth but its working thank you guys so much for the support, and @Freak07 Thank you for all your work and a kick ass kernel!

 

[daniel84cs]

For me the conversion to F2FS worked smoothly from TWRP and directly from Oxy11 (not encrypted)

 

[santiagoruel13]

Do i also need to flash the companion magisk module?? Im on A11 rom too. Thanks

 

[Freak07]

Do i also need to flash the companion magisk module?? Im on A11 rom too. Thanks

OOS 11 is supported. I don’t know if the recent kernel update will work on custom roms. Just a heads up.

No need to flash the companion module. It’s all in the kernel.zip now. Just follow the instructions in the first post.

 

[Ramalama]

OOS 11 is supported. I don’t know if the recent kernel update will work on custom roms. Just a heads up.

No need to flash the companion module. It’s all in the kernel.zip now. Just follow the instructions in the first post.

i could test.
The only problem is, if i will flash this kernel and twrp stops working, and the kernel won't boot...
im fu..ed

but i could still boot another kernel with fastboot boot whateverkernel.img ?

 

[RokCruz]

i could test.
The only problem is, if i will flash this kernel and twrp stops working, and the kernel won't boot...
im fu..ed

but i could still boot another kernel with fastboot boot whateverkernel.img ?

You can make a backup of your boot.img before you flash the kernel, if something goes bad just flash the boot.img with fastboot (fastboot flash boot boot.img)

 

[GenjiD]

Update to 1.1.1_R

Hey guys and girls,

So this update has the fingerprint sensor fixed for the OnePlus 7T. I´ll include the changelog of 1.1.0_R again to this post as I´m sure not everybody has updated to the first version of the kernel.
So if you haven´t read the release post of 1.1.0_R I suggest to read the following section!


New Things in the Android 11 Update

Here´s the update for Android 11. This will be a longer post. It would be nice if you took the time reading and not head straight to the download button.

OnePlus Source Code "Situation"

As it was already suggested by other people in the OP7/Pro Forums on XDA, the source code OnePlus pushed to github for Android 11 on the OnePlus 7 series is incomplete and does not resemble the stock kernel.
@LuK1337 began to work on the lineage kernel based on the A11 OP 7/Pro source and ported some of the missing stuff from the OnePlus 8 pro. Since his work is made for a source-built custom rom, it´s not a problem to disable most vendor/OnePlus specific implementations in the kernel since Lineage OS´s framework does not rely on them. A big thanks to him for porting some missing code that was very helpful for my project!
However OOS does rely on exactly these changes, that can be removed for Lineage. OOS either fails to boot completely (like described here)or the framework complains about missing stuff in the kernel. That´s also the reason why I never removed the OnePlus specific additions in the Android 10 kernels. (like described there)
The framework complaining can be silenced by "spoofing" the removed values to the framework. The problem with this approach is, that while the kernel is open source, the framework is not. So it´s not clear what will be happening when spoofing these values.
This is a battle I chose to not fight, even if I don´t like some of those vendor/OnePlus specific changes in various parts of the kernel.
The missing code was ported by comparing the OP7 Pro A10 source with the OP8 Pro A11 source. The OnePlus specific code that was not missing in the OP7 A11 source was (almost) identical to the OP8 A11 source.
A lot of people (more than I expected) PMed me offering to test the kernel alongside me. So far nobody complained about anything not working properly and I´m pretty sure this is a very good base to start.
I´ll push several branches to my kernel repo so other developers have a good point to start as well. I hope this helps in getting development started for A11 kernels.
Still, if other developers decide to wait for a proper source code from OnePlus I can also understand that. What OnePlus is doing is violating the GPL.
There´s no longer any doubt that the source they push is not the actual source. There is code missing everywhere.
Even if they maintain a seperate repo for public source code and the private code they actually work with, these discrepancies are no longer tolerable. (not that they ever were)
The reason I decided to go that route now, is the course of events this all is taking. Despite several updates on the OP8 Pro for example, they didn´t push a new source for months on OOS 11 there.
Source code updates get published less timely the more time goes by, starting with A10 on the OP7 Pro last year.
I hope they will fix all of this and get back on track, but at the moment I don´t have much hope.

I´m not in the developer program from OnePlus, but I´m sure that many developers that are part of this are upset about this situation as well and tried to talk to OnePlus.
I don´t have any contact at OnePlus so this is the only thing I could do.

At this point I want to say a huge thanks to all my testers that PMed me! I really appreciate their dedication. Without it this would not be possible and the kernel wouldn´t be where it is.
Remember that I only have a OnePlus 7 Pro to test. That´s why the kernel is posted in the OnePlus 7 Pro section. One of the tester uses the kernel without issues on the OnePlus 7T Pro. So that is confirmed working as well.

New Features and Update for OOS 11

But lets get to the features and the update. I learned a thing or two during the previous years. I waited for the OP7 Pro A11 for a long time now, to start from scratch and implement what I learned and did for other devices.
The way I did the bringup for A10 last year, didn´t really allow for this without starting from scratch. That´s why I decided to wait for A11 to start from scratch and do a new bringup.
I´d advise everybody to re-read the whole OP. It´s updated and contains all the most important changes. I´ll include a few snippets to this post.

This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.

Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features.
The only kernels made by OEMs offering this security feature by default are the ones for the Pixel 3, 4 and 5 devices.
Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features. So far CFI found its way to the ROG 2, the ROG 3, the OnePlus 7 Pro and the Zenfone 6 as well.

Another security feature is Shadow Call Stack (SCS). Similar to CFI, only the Pixel 3, 4 and 5 kernels use this security feature.
SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
If you´re interested here are a few good links:
Google Security Blog explaining SCS.
LLVM doc about SCS
Android DOCs documenting SCS

If reading about upstream in the paragraph above got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.

Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 855/+ that´s built into the different SKUs of the OP7/T/Pro.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. Most OEMs usually stop updating the initial base after the phone is released, and only cherry-pick certain commits to be in line with the android security bulletin.
This kernel focuses amongst the other features to merge CAF-Updates in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.

The EAS implementation from 4.19 CAF (sd865/+) was ported to this kernel. There are several interesting mechanisms qcom worked on. The basic layout of the soc architecture ( 4xLittle- , 3xBig- and 1x Prime-Core(s)) has not changed from SD855 to SD865. That means instead of revolution there was a very nice evolution the scheduler underwent.

Changelog:
Since I don´t have the time to create a changelog specific for this release, lets take the updated feature list from the first post as a changelog!

Main Features:
- Based on latest kernel sources from OnePlus for Android 11
- Upstreamed against latest CAF
- Linux-Stable-Upstream included to latest 4.14.228
- compiled with Clang 12.0.4 prebuilt from Google
- built with -O3 speed optimizations
- Link-Time-Optimization (ThinLTO)
- Kernel Control-Flow-Integration (CFI)
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO for full program visibility (needed by CFI)
- fix CFI-Violations found in various subsystems like OnePlus/device specific drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Anykernel zip is based on the Anykernel3 repo from @osm0sis
- include vDSO 32 patches to improve 32-bit performance
- disable various debugging configs, that are not needed in a perf build kernel according to google.
- Removed RTB(interrupt) logging entirely
- disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
- fix several coding issues detected by newer Clang-Toolchains

EAS related features:
- EAS scheduler backported from 4.19 CAF
- disable autogroups and use cgroups for more efficient task placement!
- updates from kernel/common
- scheduler updates from Googles Pixel kernel

CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers ( MM, audio) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
- vdso32 patches as found on Google Pixel devices (brief documentation here)
- arm64: lse: Prefetch operands to speed up atomic operations
- improve bluetooth performance
- improve /proc performance
- remove VLA-usage (info)
- option to disable touchboost in msm_performance

File System related features:
- improve memory allocations in sdcardfs
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
- ufs improvements from pixel 4/ pixel 5 kernel
- default IO scheduler to CFQ and readahead to 128

Usability related features:
- High Brightness Mode for increasing backlight level related to brightness accessible via EXKM app
- Vibration Intensity adjustable via EXKM app
- DC Dimming setting now fully functional
- add support for steam controller
- add support for nintendo switch controller

Display related features:
- KCAL to control the display
- KLAPSE integrated
- KCAL/KLAPSE: changes safety measures -> allow completely disabling two RGB values (this was requested to, for example, only have red values on night dimming)
- display tweaks to save power on statically rendered images (taken from samsung galaxy source, which uses a very similar panel)
- improve memory allocation

GPU related features:
- Ability to use the new 675mhz GPU step officially introduced by CAF (OP7/Pro is set to only use 585mhz as max)
more information and benches in the 1.2.0 release post
- add low_prio_worker thread for gpu driver (Improves performance when tearing down processes (eg, via LMK) and not blocking currently running UI from submitting work to the GPU
- remove debugging tracing from GPU driver
- improve memory allocation


Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbrv2 (default to bbr as advised by @kdrag0n )

Memory related features:
- Memory Management patches from mainline kernel
- Speculative Page Faults (1. 2) (CAF-default)
- Fix various memory leaks in different subsystems
- allow ZRAM to use higher swappiness values than 100
- default ZRAM algorithm set to lz4 (fastest compression/decompression speeds)
- possibility to use lzo-rle as default ZRAM compression algorithm (more information here and there )
- possibility to use zstd as default ZRAM compression algorithm ( higher compression ratio, slightly lower compression decompression speed, more information and benchmarks here)
- free up memory by removing unused memory regions from dts

Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- Shadow Call Stack (SCS) Security-Feature
- fix various CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message

WLAN Driver:
- use CAF wlan driver and compile it inline, the only way to ensure working wlan with this kernel
- the kernel cannot even force load prebuilt WLAN module as the kernel base is way to far from stock!
- do no longer rely on the pre compiled wlan driver module
- removed debugging from wlan driver
- removed logging from wlan driver

Scheduler Setup and Kernel Settings:
- kernel setting get automatically applied at boot
- no magisk module is necessary on OOS 11


Misc Features:
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!



Download:

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

Instructions can be found in the OP!
But look at this post too

Have fun, enjoy the kernel and your phone.

Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07

Is the advanced charging control (ACC) feature still in this kernel for OOS11? I do not see you list it in the main features.

 

[Freak07]

Is the advanced charging control (ACC) feature still in this kernel for OOS11? I do not see you list it in the main features.

It should still work like before as the commits are included. (if you refer to the idle charging mode "feature" that´s being controlled by ACC)

 

[Freak07]

Update to 1.1.3_R

Hey guys and girls,

so here´s the next update. It includes the Source Code OnePlus pushed a few days ago, that was included in 1.1.2_R, which was uploaded without a release post a few posts above following this link.
1.1.3_R includes latest linux-stable upstream to 4.14.229.

1.1.1_R has the fingerprint sensor fixed for the OnePlus 7T. I´ll include the changelog of 1.1.0_R again to this post as I´m sure not everybody has updated to the first version of the kernel.
So if you haven´t read the release post of 1.1.0_R I suggest to read the following section!


New Things in the Android 11 Update

Here´s the update for Android 11. This will be a longer post. It would be nice if you took the time reading and not head straight to the download button.


OnePlus Source Code "Situation"

Apparently OnePlus pushed some of the missing code to their github by now. That´s great, but it should never have been missing in the first place. It´s no secret by now that the source they push is not the actual source they work on, but an edited one. That´s not a bad thing in itself, but if multiple times the wrong source gets pushed, a broken source or a source that´s simply incomplete that´s not acceptable.

As it was already suggested by other people in the OP7/Pro Forums on XDA, the source code OnePlus pushed to github for Android 11 on the OnePlus 7 series is incomplete and does not resemble the stock kernel.
@LuK1337 began to work on the lineage kernel based on the A11 OP 7/Pro source and ported some of the missing stuff from the OnePlus 8 pro. Since his work is made for a source-built custom rom, it´s not a problem to disable most vendor/OnePlus specific implementations in the kernel since Lineage OS´s framework does not rely on them. A big thanks to him for porting some missing code that was very helpful for my project!
However OOS does rely on exactly these changes, that can be removed for Lineage. OOS either fails to boot completely (like described here)or the framework complains about missing stuff in the kernel. That´s also the reason why I never removed the OnePlus specific additions in the Android 10 kernels. (like described there)
The framework complaining can be silenced by "spoofing" the removed values to the framework. The problem with this approach is, that while the kernel is open source, the framework is not. So it´s not clear what will be happening when spoofing these values.
This is a battle I chose to not fight, even if I don´t like some of those vendor/OnePlus specific changes in various parts of the kernel.
The missing code was ported by comparing the OP7 Pro A10 source with the OP8 Pro A11 source. The OnePlus specific code that was not missing in the OP7 A11 source was (almost) identical to the OP8 A11 source.
A lot of people (more than I expected) PMed me offering to test the kernel alongside me. So far nobody complained about anything not working properly and I´m pretty sure this is a very good base to start.
I´ll push several branches to my kernel repo so other developers have a good point to start as well. I hope this helps in getting development started for A11 kernels.
Still, if other developers decide to wait for a proper source code from OnePlus I can also understand that. What OnePlus is doing is violating the GPL.
There´s no longer any doubt that the source they push is not the actual source. There is code missing everywhere.
Even if they maintain a seperate repo for public source code and the private code they actually work with, these discrepancies are no longer tolerable. (not that they ever were)
The reason I decided to go that route now, is the course of events this all is taking. Despite several updates on the OP8 Pro for example, they didn´t push a new source for months on OOS 11 there.
Source code updates get published less timely the more time goes by, starting with A10 on the OP7 Pro last year.
I hope they will fix all of this and get back on track, but at the moment I don´t have much hope.

I´m not in the developer program from OnePlus, but I´m sure that many developers that are part of this are upset about this situation as well and tried to talk to OnePlus.
I don´t have any contact at OnePlus so this is the only thing I could do.

At this point I want to say a huge thanks to all my testers that PMed me! I really appreciate their dedication. Without it this would not be possible and the kernel wouldn´t be where it is.
Remember that I only have a OnePlus 7 Pro to test. That´s why the kernel is posted in the OnePlus 7 Pro section. One of the tester uses the kernel without issues on the OnePlus 7T Pro. So that is confirmed working as well.

New Features and Update for OOS 11

But lets get to the features and the update. I learned a thing or two during the previous years. I waited for the OP7 Pro A11 for a long time now, to start from scratch and implement what I learned and did for other devices.
The way I did the bringup for A10 last year, didn´t really allow for this without starting from scratch. That´s why I decided to wait for A11 to start from scratch and do a new bringup.
I´d advise everybody to re-read the whole OP. It´s updated and contains all the most important changes. I´ll include a few snippets to this post.

This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.

Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features.
The only kernels made by OEMs offering this security feature by default are the ones for the Pixel 3, 4 and 5 devices.
Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features. So far CFI found its way to the ROG 2, the ROG 3, the OnePlus 7 Pro and the Zenfone 6 as well.

Another security feature is Shadow Call Stack (SCS). Similar to CFI, only the Pixel 3, 4 and 5 kernels use this security feature.
SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
If you´re interested here are a few good links:
Google Security Blog explaining SCS.
LLVM doc about SCS
Android DOCs documenting SCS

If reading about upstream in the paragraph above got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.

Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 855/+ that´s built into the different SKUs of the OP7/T/Pro.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. Most OEMs usually stop updating the initial base after the phone is released, and only cherry-pick certain commits to be in line with the android security bulletin.
This kernel focuses amongst the other features to merge CAF-Updates in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.

The EAS implementation from 4.19 CAF (sd865/+) was ported to this kernel. There are several interesting mechanisms qcom worked on. The basic layout of the soc architecture ( 4xLittle- , 3xBig- and 1x Prime-Core(s)) has not changed from SD855 to SD865. That means instead of revolution there was a very nice evolution the scheduler underwent.

Changelog:
Since I don´t have the time to create a changelog specific for this release, lets take the updated feature list from the first post as a changelog!

Main Features:
- Based on latest kernel sources from OnePlus for Android 11
- Upstreamed against latest CAF
- Linux-Stable-Upstream included to latest 4.14.229
- compiled with Clang 12.0.4 prebuilt from Google
- built with -O3 speed optimizations
- Link-Time-Optimization (ThinLTO)
- Kernel Control-Flow-Integration (CFI)
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO for full program visibility (needed by CFI)
- fix CFI-Violations found in various subsystems like OnePlus/device specific drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Anykernel zip is based on the Anykernel3 repo from @osm0sis
- include vDSO 32 patches to improve 32-bit performance
- disable various debugging configs, that are not needed in a perf build kernel according to google.
- Removed RTB(interrupt) logging entirely
- disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
- fix several coding issues detected by newer Clang-Toolchains

EAS related features:
- EAS scheduler backported from 4.19 CAF
- disable autogroups and use cgroups for more efficient task placement!
- updates from kernel/common
- scheduler updates from Googles Pixel kernel

CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers ( MM, audio) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
- vdso32 patches as found on Google Pixel devices (brief documentation here)
- arm64: lse: Prefetch operands to speed up atomic operations
- improve bluetooth performance
- improve /proc performance
- remove VLA-usage (info)
- option to disable touchboost in msm_performance

File System related features:
- improve memory allocations in sdcardfs
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
- ufs improvements from pixel 4/ pixel 5 kernel
- default IO scheduler to CFQ and readahead to 128

Usability related features:
- High Brightness Mode for increasing backlight level related to brightness accessible via EXKM app
- Vibration Intensity adjustable via EXKM app
- DC Dimming setting now fully functional
- add support for steam controller
- add support for nintendo switch controller

Display related features:
- KCAL to control the display
- KLAPSE integrated
- KCAL/KLAPSE: changes safety measures -> allow completely disabling two RGB values (this was requested to, for example, only have red values on night dimming)
- display tweaks to save power on statically rendered images (taken from samsung galaxy source, which uses a very similar panel)
- improve memory allocation

GPU related features:
- Ability to use the new 675mhz GPU step officially introduced by CAF (OP7/Pro is set to only use 585mhz as max)
more information and benches in the 1.2.0 release post
- add low_prio_worker thread for gpu driver (Improves performance when tearing down processes (eg, via LMK) and not blocking currently running UI from submitting work to the GPU
- remove debugging tracing from GPU driver
- improve memory allocation


Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbrv2 (default to bbr as advised by @kdrag0n )

Memory related features:
- Memory Management patches from mainline kernel
- Speculative Page Faults (1. 2) (CAF-default)
- Fix various memory leaks in different subsystems
- allow ZRAM to use higher swappiness values than 100
- default ZRAM algorithm set to lz4 (fastest compression/decompression speeds)
- possibility to use lzo-rle as default ZRAM compression algorithm (more information here and there )
- possibility to use zstd as default ZRAM compression algorithm ( higher compression ratio, slightly lower compression decompression speed, more information and benchmarks here)
- free up memory by removing unused memory regions from dts

Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- Shadow Call Stack (SCS) Security-Feature
- fix various CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message

WLAN Driver:
- use CAF wlan driver and compile it inline, the only way to ensure working wlan with this kernel
- the kernel cannot even force load prebuilt WLAN module as the kernel base is way to far from stock!
- do no longer rely on the pre compiled wlan driver module
- removed debugging from wlan driver
- removed logging from wlan driver

Scheduler Setup and Kernel Settings:
- kernel setting get automatically applied at boot
- no magisk module is necessary on OOS 11


Misc Features:
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!



Download:

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

Instructions can be found in the OP!
But look at this post too

Have fun, enjoy the kernel and your phone.

Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07

 

[Beachbum2049]

1.1.3_R working so far on 7 Pro flashed by EXKM. Thanks!

 

[Mohitash]

Flashed the new update with FKM. Working great so far.
Just noticed one thing, after restarting phone (after update) fingerprint animation was not working then I selected animation again in settings now it is working as before.
It's not a bug may be. It's just a so called cache update. It confirms that some changes are made in kernel (source) related to fingerprint sensor.