Related
New version Slimkat 8.10 compiled today . New kernel with Tomoyo security enabled (as opposed to Apparmor). Enjoy.
See Download section
________________________________________________________________________________________
Here is the famous Slimkat 4-4-4 rom built from sources a few hours ago. Changes made to kernel only and they are the following:
Hardened Kernel with the following features:
a. Selinux disabled (don't trust them) and APPARMOR enabled as main security
b. All crypto core features enabled
c. All authenticated encryption modes enabled - CCM, GCM and SEQIV
d. All blocks enabled - CBC, CTR, CTS, ESB, LRW, PCBC and XTS
e. All hash modes enabled including SHA512 and others
f. All ciphers enabled including CAMELIA, TWOFISH, ANUBIS, SALSA20 and others
g. Compression - DEFLATE, ZLIB and LZO
h. Random number generation all options enabled to result in a better generation without CPU wakeups
Credit: Slimroms Team
WARNINGS:
I am not responsible for your device becoming a paperweight. I am also not responsible for death and destruction caused by your flashing this rom on your device. You are at your own perill. Complain to Putin - he will surely help.
INSTRUCTIONS
1. Unlocked Bootloader
2. If you have CWM, go to mounts and storage and wipe System/Cache/Data
3. If you have TWRP, go to advanced wipe and wipe System/Cache/Data
4. Flash the rom and reboot.
5. I recommend that you delete Cyanogenmod original boot animation as it slows down the boot significantly: without it your boot should take about 25 seconds. Once you remove bootanimation.zip in /system/media, you will have a nice vanilla android bootanimation.
6. Enjoy the rom and hit Thank You or perhaps Donate?
P.S. Rom is in Download Section above
XDA:DevDB Information
[ROM] [Kitkat 4.4.4] Slim-Honami-4.4.4.build 8.10-UNOFFICIAL, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Beta
Stable Release Date: 2014-11-11
Beta Release Date: 2014-10-21
Created 2014-10-21
Last Updated 2014-11-11
Thanks Man.. Please keep up the good work
OP, it must be terrible to be asked over and over again but I'd be very glad if you could tell what those changes in the kernel that you have introduced mean for the end user. So to speak, what can we expect after installing this? is this more security oriented or would the random number generation is related to entropy stuff and is supposed to speed up the system?
I saw your other thread too, wanted to give it a try but couldn't understand what these changes to the kernel actually mean for a layman.
Thanks man for your work!
srqrox said:
OP, it must be terrible to be asked over and over again but I'd be very glad if you could tell what those changes in the kernel that you have introduced mean for the end user. So to speak, what can we expect after installing this? is this more security oriented or would the random number generation is related to entropy stuff and is supposed to speed up the system?
I saw your other thread too, wanted to give it a try but couldn't understand what these changes to the kernel actually mean for a layman.
Thanks man for your work!
Click to expand...
Click to collapse
It is actually both security oriented and system speed based on better random number generation.
First of all, I don't trust Selinux, especially in light of the recent Snowden's revelations. So, selinux is out of this kernel. Instead, you have trusted Apparmor, which has been used in Linux for years. In addition, many newer ciphers, which are in this kernel, were disabled by default -- again think of several 3-letter-agencies that are known for deliberately weakening kernels and operating systems to make it easiers for themselves to break. So, I have enabled those ciphers. Hashes, especially SHA512, which is the strongest, were disabled by default. I have enabled them all. Random number generation: the same.
So, as result, you have a more secure system that is faster, because of better and more random seeding.. If you remember, there is an app on XDA, which the author says, provides better random number generation, but it drains battery, because CPU constantly checks if the pool (of random numbers) is large enough. Here, it is different, because the changes (better and more random seeding ) are on the kernel level. So, CPU does not have to constantly wake up and check...
optimumpro said:
It is actually both security oriented and system speed based on better random number generation.
First of all, I don't trust Selinux, especially in light of the recent Snowden's revelations. So, selinux is out of this kernel. Instead, you have trusted Apparmor, which has been used in Linux for years. In addition, many newer ciphers, which are in this kernel, were disabled by default -- again think of several 3-letter-agencoes that are known for deliberately weakening kernels and operating systems to make it easiers for themselves to break. So, I have enabled those ciphers. Hashes, especially SHA512, which is the strongest, were disabled by default. I have enabled them all. Random number generation: the same.
So, as result, you have a more secure system that is faster, because better and more random seeding.. If you remember, there is an app on XDA, which the author says, provides better random number generation, but it drains battery, because CPU constantly checks if the pool (of random numbers) is large enough. Here, it is different, because the changes (better and more random seeding ) are on the kernel level. So, CPU does not have to constantly wake up and check...
Click to expand...
Click to collapse
Got it, thanks for the great explanation bro.
I totally get it now, would be trying Aragon one today would definitely come and report how that works!
Great work buddy,
Can you share your kernel sources?
I might include some of your changes in official slimkat
also out of curiosity, if the change is only on the kernel, wouldn't it be easier to share the kernel only!
Regards,
Omar.
OmarEinea said:
Great work buddy,
Can you share your kernel sources?
I might include some of your changes in official slimkat
also out of curiosity, if the change is only on the kernel, wouldn't it be easier to share the kernel only!
Regards,
Omar.
Click to expand...
Click to collapse
Of course it is easier to do the kernel only, but I haven't found the way to do that outside of building the whole rom. Plus, in CM roms, I know where to put those changes: row rhine honam_def.conf and if you look at my sources for Black Argon rom, you will find the changes there.. But Slimroms guys use some other file, so I put my .config file in during the build. Plus, for the new kernel to work, you need modules from the rom you will be using it in and roms differ from one to another. So, for now, it is easier for me to build the whole rom.
very good
each person who comes to their work
it is a hope to be in a rom kk
if this rom has the same problem that all
3g signal loss that is very unpleasant truth
You could solve this drawback
It's good to see you here. A couple of months ago in the ion forums you were patient and answered a lot of questions I had when I switched from HTC to Sony. Armed with a little knowledge, I was able to find a good used Z1 with an unlockable bootloader.
Thanks again.
New Version Slimkat 8.10 posted: see Download section
New version posted. See Download...
auto rotate not working
Auto rotate not working anywhere
Yes. For some reason autorotate does not work. I even recompiled the 8.12 version and it still does not work. The Slim original 8.12 is fine. It is also not my kernel, because I am using my kernel with Slimkat original weekly without any problem. I am puzzled as to why it is happening...
The only change in build.prop I made was to add 3 entries regarding rild. You can try to open build.prop and delete those three entries (search for "rild" and delete them). But I don't think rild has anything to do with the sensors.
thanks !
optimumpro said:
New version Slimkat 8.10 compiled today . New kernel with Tomoyo security enabled (as opposed to Apparmor). Enjoy.
See Download section
________________________________________________________________________________________
Here is the famous Slimkat 4-4-4 rom built from sources a few hours ago. Changes made to kernel only and they are the following:
Hardened Kernel with the following features:
a. Selinux disabled (don't trust them) and APPARMOR enabled as main security
b. All crypto core features enabled
c. All authenticated encryption modes enabled - CCM, GCM and SEQIV
d. All blocks enabled - CBC, CTR, CTS, ESB, LRW, PCBC and XTS
e. All hash modes enabled including SHA512 and others
f. All ciphers enabled including CAMELIA, TWOFISH, ANUBIS, SALSA20 and others
g. Compression - DEFLATE, ZLIB and LZO
h. Random number generation all options enabled to result in a better generation without CPU wakeups
Credit: Slimroms Team
WARNINGS:
I am not responsible for your device becoming a paperweight. I am also not responsible for death and destruction caused by your flashing this rom on your device. You are at your own perill. Complain to Putin - he will surely help.
INSTRUCTIONS
1. Unlocked Bootloader
2. If you have CWM, go to mounts and storage and wipe System/Cache/Data
3. If you have TWRP, go to advanced wipe and wipe System/Cache/Data
4. Flash the rom and reboot.
5. I recommend that you delete Cyanogenmod original boot animation as it slows down the boot significantly: without it your boot should take about 25 seconds. Once you remove bootanimation.zip in /system/media, you will have a nice vanilla android bootanimation.
6. Enjoy the rom and hit Thank You or perhaps Donate?
P.S. Rom is in Download Section above
XDA:DevDB Information
[ROM] [Kitkat 4.4.4] Slim-Honami-4.4.4.build 8.10-UNOFFICIAL, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Beta
Stable Release Date: 2014-11-11
Beta Release Date: 2014-10-21
Created 2014-10-21
Last Updated 2014-11-11
Click to expand...
Click to collapse
Installed this 4.4.4 version and it works gr8.. but my recovery is gone
Tried : Z1-lockeddualrecovery2.8.15-RELEASE.installer and Fota.. both states that it works but my recovery never "boots" just stands there with a another light on the phone..
Suggestions anyone ?
Now i have a working 4.4.4 Rom but no working recovery (light changes but recovery never boots, when i press volume)
hakd said:
Installed this 4.4.4 version and it works gr8.. but my recovery is gone
Tried : Z1-lockeddualrecovery2.8.15-RELEASE.installer and Fota.. both states that it works but my recovery never "boots" just stands there with a another light on the phone..
Suggestions anyone ?
Now i have a working 4.4.4 Rom but no working recovery (light changes but recovery never boots, when i press volume)
Click to expand...
Click to collapse
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.
optimumpro said:
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.
Click to expand...
Click to collapse
LOG:
C:\Megasync\Android\ADB + Recovery>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.020s
C:\Megasync\Android\ADB + Recovery>fastboot reboot
rebooting...
finished. total time: 0.002s
Thanks alot for taking the time to help me, now i got an awesome 4.4.4 With a custom recovery when i change my mind (5.x.x was not stable enough)
optimumpro said:
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.
Click to expand...
Click to collapse
this helped me a lot
Here is my Hardened Kernel with the following features enabled:
1. Kexec
2. File security
3. Network security
4. Apparmor
5. IMA
6. Crypt core: Algapi, AEAD, AEAD2, BLKCIPHER, Hash, Hash2, RNG, RNG2 PCOMP, PCOMP2 Manager, Manger2, GF128MUL, Null, PCRYPT, WorkQUEUE,
7. CCM, GCM, SEQIV
8. Block modes: CBC, CTR, CTS, ECB, XTS
9. Hash modes: HMAC, XCBC, VMAC
10. Digest: CRC32C, GHASH, MD$, MD5, Michael_Mic, RMD128, RMD160, RMD256, RMD320, SHA1, SHA256, SHA512, TRG182, WP512
11. Ciphers: AES, SNUBIS, ARC4, BLowfish, CAmellia, CAST5, CAST5, DES, FCRYPT, KHAZAD, SALSA20, Seed, Serpent, TEA TWOFISH
12. Compression: Deflate, ZLIB, LZO
13. Random Number Generation: ANSI, Hash, Skcipher, QCRYPTO, QCE
14. Selinux is out
Instructions:
1. Flash the zip from download section
2. Reboot
Warnings:
If your device dies, don't blame me. Get another one.
This kernel includes a wifi module, as those are specific to a particular kernel. Kernel should work on any CM based rom except for Slimkat and Dirty Unicorn. The kernel includes CWM recovery.
XDA:DevDB Information
Hardened Kernel for CM based roms, Kernel for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/optimumpr/android_kernel_sony_msm8974
Kernel Special Features: Hardened Kernel with many security features that were disabled by default, but now enabled. This includes many more ciphers, hashes and random seed generation hashes. As a result, your device becomes faster and more secure
Version Information
Status: Stable
Stable Release Date: 2014-10-29
Created 2014-10-29
Last Updated 2015-01-16
reserved
Hi @optimumpro does it require a App to activate these features or just Flash?
And thanks man..
abbychauhan said:
Hi @optimumpro does it require a App to activate these features or just Flash?
And thanks man..
Click to expand...
Click to collapse
No app is required. With Apparmor, default policy is used, but, as with SeLinux, you can create your own init.d scripts for every app you have.
Nice Kernel, already flashed and works good so far. I'm feeling more save now ^_^
Add source or this thread will be closed.
"Add source or this thread will be closed. "
Take it easy, bud. You are not a guard here.
P.S. Source added...
optimumpro said:
"Add source or this thread will be closed. "
Take it easy, bud. You are not a guard here.
P.S. Source added...
Click to expand...
Click to collapse
There is something called GNU General Public License.
How about adding credits to darkcyanogenmod where you forked the kernel from...
"How about adding credits to darkcyanogenmod where you forked the kernel from... "
Forget about darkcyanogenmod -- too much noise. I have forked directly from CM.
Again, take it easy...
Optimum. Just give credits to things you took from people. Because your cause to much hassle and there be a big fight!
Sent from Xperia Z1 - Customized Rooted by a smartarse 13 Year old - Hehe
When I compiled the rom, I gave credit to Darkcm, you are welcome to read it. With this kernel, there is no connection to Darkcm. I forked it directly from Cyanogen and gave credit to them. If you have trouble understanding Gpl and open source, read it until you do.
I would prefer that we don't communicate anymore, and please stay off this thread.
Kind regards.
Stable Kernel
Stable Kernel. No issues whatsoever. I'm running CM11 (11-20141118-NIGHTLY-honami), 4.4.4. Thanks!
Kernel upgraded to include TWRP 2.8.0.1. See Download section. Now, your CM based rom can have TWRP recovery.
Would this work on crDroid lollipop?
eddvys said:
Would this work on crDroid lollipop?
Click to expand...
Click to collapse
No, it won't. There is nothing related to lollipop in my threads.
Hi oneplus2 people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x roms like CyanogenMod.
It might work on other roms, but there will be little support for them.
How does one achieve this?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- etc. (most are not so easy to explain)
This kernel is built with mdalexca's latest UBER GCC 4.9.
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Latest release
BasketBuild
Source:
GitHub
This was made by request from dsst22 who also tested this bad boi like crazy.
XDA:DevDB Information
abyss kernel for the OnePlus 2, Kernel for the OnePlus 2
Contributors
kwoktopus, dsst22, OnePlus, grarak, The Flash, arter97, Lord Boeffla, frap129, Linux, Google, CAF, a bunch of other major OEMs
Source Code: https://github.com/abyss-kernels/oneplus2
Kernel Special Features:
Version Information
Status: Nightly
Current Stable Version: 1.20
Stable Release Date: 2016-12-05
Created 2016-12-05
Last Updated 2016-12-13
Key Changes:
- upstream interactive governor (with Flash 1.0 profile by The Flash) (Google and CAF)
- upstream cpufreq driver (Google and CAF)
- upstream cpu-boost driver (Google and CAF)
- upstream random driver from Linux 4.1.31 (performance..!)
- slub/slab/slob/vmalloc patches
- flar2's slightly modified thermal driver
- using Linaro's power efficient workqueues throughout kernel
- using Adreno idler by arter97 to reduce frequency scaling without performance cost
- using power efficient "relaxed" macros throughout kernel (assembler)
- KCAL Control Driver by Savoca
- Android-Keyboard patch, use your device as an external keyboard!
- too many to list here, check out my source
How to install:
Place zip in to your internal storage
Place current ROM zip on to your storage
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
For me
Thanks! I'll give it a go.
Giving it a go
Yess! Been waiting for this ever since i saw your OP2 repo!
Does this kernel install on a f2fs formatted system?
suraj.das said:
Yess! Been waiting for this ever since i saw your OP2 repo!
Click to expand...
Click to collapse
You can thank @dsst22 for helping with testing, or else you would have waited a very long time :silly:
socialdistortion said:
Does this kernel install on a f2fs formatted system?
Click to expand...
Click to collapse
I have not made any file system changes to the kernel. If the stock CM kernel supports, then this one will too.
Is kcal support present..??
chl1810 said:
Is kcal support present..??
Click to expand...
Click to collapse
unfortunately no.
good to see new kernel for our device, thanks and good luck
suraj.das said:
unfortunately no.
Click to expand...
Click to collapse
I wish it had
chl1810 said:
I wish it had
Click to expand...
Click to collapse
I can remember the YoshiShaPow falcon kernel
chl1810 said:
I wish it had
Click to expand...
Click to collapse
In the future
PeterImmel said:
I can remember the YoshiShaPow falcon kernel
Click to expand...
Click to collapse
You can probably see how much I've grown as a developer since then too :angel:
Works on a f2fs filesystem based rom. Testing it now...
Edit: No obvious bugs at the moment. Is it possible to implement some sort of charging control. The USB charging speed is super slow (on both this kernel and stock CM kernel).
kwoktopus said:
In the future
Click to expand...
Click to collapse
Nice!! thank you!!
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
adame09 said:
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
Click to expand...
Click to collapse
I trust the engineers that designed the chip to choose a safe maximum clock speed. Here's a pretty good article on the risks vs benefits, which outline some strong points.
But, if I were to add it, I would set the max value at boot to stay as stock values; so I'll leave it up to @dsst22 to decide.
I'll try this out for you dude. Impressive what you've done.
Kirisakura-Kernel for the Asus Rog Phone 2
Hello everyone,
I proudly present Kirisakura-Kernel made for the Asus Rog Phone 2 aka Yoda!
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
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. In fact this may be one of the only 4.14 msm kernels with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If that 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 Asus Rog Phone 2.
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. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst others to provide the latest CAF-Updates merged 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 kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 11 and intended for use on Asus Stock Rom
- compiled with Clang 13.0.1 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.14.243
- CAF-Upstream merged
- Link the kernel with LLD and use KASLR
- include all important fixes/improvements from kernel/common
- F2FS implementation updated to latest state of kernel/common and kernel.org maintained by Jaegeuk Kim.
- Safety Net patches are included -> Kernel passes Safety Net
- Flashing the kernel will keep root!
- Sweep to sleep functionality
- Flashable via EXKM and FKM on a rooted system!
- specifically tuned EAS for the Asus Rog Phone 2
- removed nolog usage, remove rtb logging from the kernel
- remove selinux auditing from kernel for lower overhead
- remove IPC logging from the kernel
- Anykernel zip is based on the all new Anykernel3 release from @osm0sis
- option for 144hz refresh rate (Android 10 only)
- option to improve visibility in dark scenes
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- Dynamic Stune Boost to inflate task utilization and not overload cores on interaction (thanks to @RenderBroken and @joshuous )
- improved schedutil governor
- updates from kernel/common
CPU related features:
- Power saving workingqueues enabled by default
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- vDSO 32 patches to improve 32-bit performance
- arm64: lse: Prefetch operands to speed up atomic operations (thanks to @kdrag0n )
File System related features:
- F2FS implementation updated to latest state of kernel/common and F2FS-Mainline on kernel.org maintained by Jaegeuk Kim.
- Include rapid GC by @arter97 ( best thing is to read the commit description linked here. I compared GC on stock google f2fs, upstreamed f2fs and f2fs with rapid GC. Rapid GC is the most effective, followed by upstreamed f2fs.)
- adapt F2FS to be inline with Pixel 4s code from Google, which is also directly maintained by Jaegeuk Kim
- include a few F2FS fixes from the Pixel 4 kernel
- include optimizations to UFS-Driver from Pixel 4
- various improvements to FS-Performance from the Pixel 4
- f2fs fix to prevent data loss in case of sudden power failure
GPU related features:
- Update GPU driver to latest CAF state
- remove debugging and non-sd855+ specific code from the GPU driver
- introduce low priority worker thread to improve performance in UI-critical situations
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
Memory related features:
- Speculative Page Faults (1. 2) (CAF default)
- enabled per process reclaim (CAF default)
- Fix various memory leaks in different subsystems
- improved mm with patches from latest mainline
- various other changes from mainline
- included zstd and lz0-rle as options for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- allow swappiness up to a value of 200
- remove unused mem regions to free more RAM (thanks to @kdrag0n )
Security related features:
- Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.14 kernel/common and Pixel 4 Kernel
- Shadow Call Stack ported from 4.14 kernel/common and Pixel 4 Kernel
- enable init_on_alloc for even more security, more information can be found in the commit message
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled
- includes new bbr2
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
Other features:
- disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
- remove VLAs from the kernel (more info)
- add support for steam controller
- add support for nintendo switch controller
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
- fix CFI violations
- add ramoops/pstore support (thanks @luca020400)
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of boot.img and dtbo.img to be able to restore to stock. you should be able to do this easily via TWRP.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest Asus Firmware
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img and dtbo.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk stable. (not the latest canary!)
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP (haven´t tested TWRP myself as I don´t need it) and do a full reboot.
4. Flash the kernel again. This step is needed because flashing the kernel disables verity on vendor in order to modify two files. Disabling verity takes a reboot. Flashing the second time allows the two files to be changed correctly. This step is necessary if you flashed a firmware update. (This step should not be necessary when updating my kernel, if you are already running it, but if you want to be on the safe side just flash it twice)
5. Reboot and profit. It will take around 15 seconds for the kernel and the system to execute all changes done by flashing the kernel.zip. After 15 seconds 120fps will kick in, if you use 120fps setting!
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=303784
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9
1.0.0 Initial Release
1.0.2 https://forum.xda-developers.com/showpost.php?p=81389411&postcount=33
Android 10
2.0.0 https://forum.xda-developers.com/showpost.php?p=82238713&postcount=141
2.1.0 https://forum.xda-developers.com/showpost.php?p=82317211&postcount=191
2.6.0 https://forum.xda-developers.com/showpost.php?p=82495531&postcount=252
2.6.2 https://forum.xda-developers.com/showpost.php?p=82560081&postcount=261
2.6.4 https://forum.xda-developers.com/showpost.php?p=82602927&postcount=267
2.7.2 https://forum.xda-developers.com/showpost.php?p=82834055&postcount=281
2.7.5 https://forum.xda-developers.com/showpost.php?p=82837791&postcount=285
2.9.0 https://forum.xda-developers.com/showpost.php?p=83100663&postcount=306
3.0.6 https://forum.xda-developers.com/showpost.php?p=83526987&postcount=391
3.1.0 https://forum.xda-developers.com/showpost.php?p=83606511&postcount=406
3.1.3 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84124933
3.1.5 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84617449
3.2.0 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84717691
3.2.1 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84799241
3.2.2 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-85145887
3.2.3 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-85431627
Android 11
1.0.0_R https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-86201183
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
Asus for the Rog Phone 2
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid for his awesome roms!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help too
@topjohnwu for magisk!
@osm0sis for anykernel!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the ASUS ROG Phone II
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_Yoda
F.A.Q:
Question: Why does the kernel version show as "unavailable" in settings after flashing it.
Answer: Asus does not allow for custom kernel names in their settings. Use a kernel manager to check the kernel version.
Question: Is root preserved when flashing this kernel?
Answer: Yes the Anykernel Zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img as well as dtbo.img from matching firmware you are on and flash the extracted boot.img via fastboot.
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
android-tools/guides/proper_bug_reporting.txt at main · nathanchance/android-tools
Publicly available Android stuff. Contribute to nathanchance/android-tools development by creating an account on GitHub.
github.com
and one more for me
Wow!!! Awesome! Plans for kcal in the future?
Thank you so much for giving me a reason to unlock the bootloader. Finally am happy to see development for the device and that too from a well known developer ???? cheers mate and a very happy new year.
Can I flash Android 10 beta fota file to my cn version phone using this recovery?
I love your work bro keep this devlopment continue
All rog2 user support your hardwork ,
And more developer will come after seeing your hardwork
a5he said:
Can I flash Android 10 beta fota file to my cn version phone using this recovery?
Click to expand...
Click to collapse
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
sakamaki izayoi said:
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
Click to expand...
Click to collapse
flash the boot.img extracted from the android 10 beta firmware via fastboot.
Kernel is made for Android Pie as stated in the OP.
Welcome bro and thanks for the first rog 2 custom kernel.. ?
After flashing in twrp it says i should flash companion magisk module. Is there one yet?
mohammed510 said:
Welcome bro and thanks for the first rog 2 custom kernel.. ?
After flashing in twrp it says i should flash companion magisk module. Is there one yet?
Click to expand...
Click to collapse
Oh that’s a remnant of another kernel in the flashing script.
No there is none needed. I’ll remove that message in the next release!
thanks for the hint!
You just gave me a reason to unlock my bootloader and go back to Pie
What a day! Thanks a lot @Freak07! I'm happy for you being around!
Cheers,
anthonws.
sakamaki izayoi said:
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
Click to expand...
Click to collapse
Extract the boot.img from Update and flash it under .img in twrp.
Goodluck
Very thanks
Please work on power saving and governor
Thank you for joining the ROG 2 Forums @Freak07
apollo3x said:
Extract the boot.img from Update and flash it under .img in twrp.
Goodluck
Click to expand...
Click to collapse
How to extract the Payload file of Android 10 FOTA?
The current Payload dumper doesn't support it.
Thank you so much for your hard work, I can't wait for you to make an version for Android 10 , hopefully once we have a custom kernel we can finally enjoy the 6000 mah battery
Mohamad313 said:
Very thanks
Please work on power saving and governor
Click to expand...
Click to collapse
avivv said:
Thank you so much for your hard work, I can't wait for you to make an version for Android 10 , hopefully once we have a custom kernel we can finally enjoy the 6000 mah battery
Click to expand...
Click to collapse
No idea about Android 10, but I’m enjoying the 6000mah on Pie already. That Android 10 build floating around is no finished or final piece of software.
I’ll attach my current stats from this morning.
No extensive gaming, mainly browsing, exploring the phone, massaging, videos, some calls etc.
but all on constant 120hz.
Wow that's great stats, when I had android 9 I the battery life was worst than I expected, if there was a way to rollback to android 9 without wiping the data I would have done it just to try this kernel.
would it be possible to add battery charge limiting support? currently apps like ACC don't work with this phone.
Introduction
Dora kernel is a successor of popular nem0 kernel for A10/A11 ROMs.
Dora Kernel is CAF based kernel aiming to provide great stability and performance while maxing out battery life!
Code:
// Your warranty is now void.
//
// 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.
Main Features:
- Unified for OOS 11 and Android 11 Custom ROMs (Check with your maintainer if they have R blobs merged in)
- Based and upstreamed to latest CAF tags for the SD855
- Upstreamed to latest Linux-Stable
- Upstreamed to latest F2FS stable
- Compiled with Clang 13 and -O3 speed optimizations flags
- Compiled with Clang Polyhedral Loop Optimizations (Polly)
- Simple LMK driver from kerneltoast
- BBR2 TCP congestion algorithm
- 675 MHz GPU step
- Custom energy-freq scheduling model for maximizing performance and battery life
- Custom frequencies setup (dropping to CAF default minimums during idle)
- S2idle suspend mechanism with patches from Google P4/P5 kernels
- PELT scheduling mechanism
- Many scheduler backports from mainline and/or 4.19 Google kernel
- Zip made using latest AnyKernel3 release, retains root on flash (Stable Magisk 21.4 or higher reccommended)
- Zip flashable through EXKM/FKM/Smartpack/TWRP
- Integrated OTA updates in Franco's Kernel Manager *(link for the json: JSON)
- Many more features I don't remember right now, check source if you're interested or contact me on Telegram!
Bug reports:
- If you want to report a bug, please provide some sort of logs (logcat, dmesg)
Flashing instructions:
- Just flash it through TWRP or EX or Franco's Kernel Manager apps
- No sorts of configs needed, flash and be happy out of the box
-There are 2 versions per release: one with SDCARD_FS disabled (default) and one with it enabled. Motivation behind this is recent updates to AOSP 11 ROMs (Yaap, Derp, etc.) that have disabled the support for it. And even though that builds with SDCARD_FS could still work, it's not recommended.
So, in layman terms, if you are running OOS or any custom ROM that still hasn't followed the path of those custom ROMs, please use the sdcard-fs zip or update through OTA.
Downloads
Stable and Test builds: Google Drive
Kernel being actively tested in this group: Telegram
Donations
If you would like to keep this project going with more improvements, feel free to support it: PayPal
Thank you to:
@osm0sis for AnyKernel
@nathanchance for help with upstreams
@topjohnwu for Magisk
@idkwhoiam322, @KuranKaname for being good friends
@BobAzzon, @npv12, @Gabyrx7, @Reechings and rest of my dear friends that tested the kernel (really, wouldn't be possible without you guys <3)
Contributors
nem0 aka AnnoyingZlatan
Source Code: GitHub
Version Information
Status: Stable
Created 2021-05-01
Last Updated 2021-07-20
Reserved
Reserved #2
really pru kernel, I like it
my sot tripled
jk, best kernel on here!
Best kernel ever since Nemo,,now Dora,,congrat bro,,awesome kernel,,work perfect with new official PE rom,,,
Best for A11 on OOS11 blobs and OOS11 !!!!
Ex-nem0 Kernel user here, thank you so much @AnnoyingZlatan for this one
I've just installed 1.0 with adb sideload on latest PixelExperience, all good
Love ur kernel looking forward to help u testing hehe
Toutatis_ said:
Ex-nem0 Kernel user here, thank you so much @AnnoyingZlatan for this one
I've just installed 1.0 with adb sideload on latest PixelExperience, all good
Click to expand...
Click to collapse
I'd like to try it on YAAP, but I didn't know how to go back to stock kernel. I read somebody says to restore boot.img & dtbo but not sure how to do it
Zhuang zhuang said:
I'd like to try it on YAAP, but I didn't know how to go back to stock kernel. I read somebody says to restore boot.img & dtbo but not sure how to do it
Click to expand...
Click to collapse
In Franko kernel manager you can make a backup of your current kernel. Then flash this, then restore kernel if you want it back.
Of fastbootd flash boot img from yaap, same as you most likely did when you originally installed it if you used that method. (Ps, make sure it's matching your ROM though, so you're not updated to the latest but flashing a boot image from a previous version..)
Currently using your Nemo kernel. I flashed this kernel via Franco's kernel manager but I get kicked back to my recovery..any ideas? Tia your kernels are awesome
This kernel is awesome. With Dora Freq i've the best UI performance with AOSP like LOS/CrDroid , another world compared to OOS. Thanks Dev.
bushninja07 said:
Currently using your Nemo kernel. I flashed this kernel via Franco's kernel manager but I get kicked back to my recovery..any ideas? Tia your kernels are awesome
Click to expand...
Click to collapse
Yes, this is meant for OOS 11 and A11 ROMs that switched to R blobs, as it's stated in the OP. It won't be compatible with the builds you've run Nemo on
Amazing experience out of the box, super thanks !
tested with OP7 on oos 11.0.0.2
super smooth and really impressive battery
I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes
Zhuang zhuang said:
I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes
Click to expand...
Click to collapse
Yaap has a built in logcat, perhaps check to see if there's any traces of the error. It might help Zlatan if you post that..
I have OOS 11 and and currently using a custom kernel. Should I flash OOS 11 again before your kernel? Thanks in advance.
Zhuang zhuang said:
I flashed via FKM on YAAP. Everything started good but just few minutes ago, when the screen turned off, it didn't turn on again & auto reboot. I had it 2 times in just a couple of minutes
Click to expand...
Click to collapse
I am aware of the issue. Will be fixed in next update, just a bit busy atm.
Teso79 said:
I have OOS 11 and and currently using a custom kernel. Should I flash OOS 11 again before your kernel? Thanks in advance.
Click to expand...
Click to collapse
Nope, just flashing a kernel is enough.
I have tried this version of the kernel and it feels very good! But the memory of my phone is too small, I hope there will be swap space in the future. Does the developer have plans to add zram or zswap in the future?