Develop Bugs

[ROM] [Kitkat 4.4.4] Slim-Honami-4.4.4.build 8.10-UNOFFICIAL

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

[ROM UPDATED NOV 11 [UB] DirtyUnicorns Lollipop 5.1.1 r29 Unofficial

If anyone has a problem with Dialer crashing, flash this and reboot: http://forum.xda-developers.com/attachment.php?attachmentid=3542888&d=1447583272
November 11: Rom updated. This is the same release 29 with the following changes:
1. Fixed notifications: now you have the correct icons in status bar
2. Network switches in Settings: mobile, wifi and bluetooth
3. Changes in WP8_supplicant: better wifi
You can flash dirty if you are on the previous release.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=15160
--------------------------------------------------------------------------------------------------------
November 9: Rom updated to release 29
1. Latest Google sources including stagefright and audioflinger patches
2. Updated M5 kernel compiled with GCC 5.2.1 Ubertc - some say no one has done it before
3. Du has abandoned Lollipop (too bad for them), so, this is final unless there are further releases by Google
Kernel does NOT have recovery builtin. So, have TWRP in Fota/Recovery partition
Download: See download link for November 11 above
You may try to do dirty flashing if you were on a previous release, but full wipe is preferable
Oh, I want to give credit (the second time in this thread) for initial kernel sources to @Myself5
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
October 14. New update to LP 5.1.1 r24. This release includes:
1. Blacklist (call blocking). If you go to Security, you will see Blacklist heading where you can add numbers to block
2. Google October Security Patches.
3. Latest Sources (r.24)
This is probably the final Lollipop release, unless Google does r.25 et al. Virtually no one is doing anything with Lollipop: everyone is on Marshmallow... So, enjoy it while it lasts, as we are looking at the next summer the earliest when Marshmallow could become stable...
Download: http://forum.xda-developers.com/devdb/project/dl/?id=14752
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
September 23. Rom updated to LP 5.1.1 r18, DU release 9.7. Latest sources.
Kernel includes the implementation of the latest Linux commit where persistent ram is replaced with Pstore. Also, the latest Sony 14.6 release with a revamped wifi module. The result: more ram available, better wifi and general stability... This kernel is only available on my Jaguar rom (originally) and this version of DU.
Do a fresh install and then you can restore your data (if you were on my prior release), otherwise, fresh install.
Remember, due to DU implementation of Selinux switch (which in my release is redundant (as Selinux is disabled in kernel), the system will take an extra minute (on first boot only) to have access to Settings. Android may complain that Settings app is not responding, choose wait and then allow root access to Settings, so that it could do its thing with Selinux switch. You only have to do it once...
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=14515
____________________________________________________________________________________________________
August 22: Rom updated to LP 5.1.1 r13. Latest sources.
The main change: I have fixed brightness in TWRP 2.8.7. Due to horrendously wrong values, brightness could not be manually adjusted and also exceeded Sony's maximum settings over 18 times, which resulted in temperature rising to over 65 degrees during flashing. So, now the brightness lever works and you have about 52 degrees during backup/restore. I will be pushing commits upstream soon..
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=14132 Download link fixed. There were 4 downloads, please re-download and re- flash.....
You can flash dirty if you are on my previous release.
____________________________________________________________________________________________
August 14: Rom updated to LP 5.1.1 r10 and DU 9.6. Original DU is still release 9, but I used Google's r10 sources.
Latest AOSP/CM/DU sources. Latest M5 kernel with cpu/gpu overclock. TWRP 2.8.7 is in boot image.
You may flash dirty if you were on my previous release. If you use Xposed modules, you must flash Xposed for LP5.1.1 before rebooting.
Otherwise, clean flash. Keep in mind that due to DU changes LockClock app is part of DU Tweaks and if you remove it, you won't have access to Tweaks anymore. The good news is that DU's Lockclock does not have googleplay binaries...
Download: http://forum.xda-developers.com/devdb/project/dl/?id=14022
__________________________________________________________________________________________
August 11: Kernel updated to include the latest CM and M5 commits. Kernel now is 2 mb lighter. Also, the fixed TWRP 2.8.7 is included in boot.img.
Download: http://forum.xda-developers.com/showpost.php?p=62282724&postcount=198
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
August 3: New build. Latest changes. On my end latest M5 kernel with the following additions:
1. CPU frequencies and voltage: 268/300/422/652/729/883/960/1036/1190/1267/1497/1574/1728/1958/2150/2265/2419/2457 and they all show up in voltage
2. GPU two new frequencies: 533/600
I flashed dirty, wiped cache/dalvik and had no problems, but clean flash with the subsequent data restore in TWRP is still preferable.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=13841
P.S. TWRP is in boot, so, get rid of your fota recovery first...
___________________________________________________________________________________________________
July 31: Kernel updated to reflect recent M5 changes. Also, GPU overclock to 600 is added thanks to Androguide.
Download: http://forum.xda-developers.com/showpost.php?p=62126634&postcount=145
____________________________________________________________________________________________________
July 30: New build. This is DU's release 9.5. Latest sources. See changelog in rom.
On my side: Wifi disconnection after 15 min of sleep and excessive draining are fixed. Now, the battery draining is very close to Kitkat
And generally wifi has more power now, as I have increased power cap to 80. All features listed below are also included
On first boot, Settings app is going to hang for about 1 minute due to the fact that SElinux switch is looking for Selinux which is expelled from the rom (as you know), so, just wait for Settings ask for root permission and grant it. If the system says app is not responding, choose wait, because you really want to give Settings that root permission, so that it wouldn't bother you anymore
If you are on a previous DU build, you may flash dirty, but fresh install (and then data restore in TWRP) is preferred.
TWRP is back in boot.img, so, if you have fota recovery, get rid of it in bootloader: fastboot erase recovery
Enjoy
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13759
_______________________________________________________________________________________
July 19: rom updated. This is 5.1.1 release 8. Latest changes
All hardened features
FM radio included
New M5 kernel with TWRP
Slim Launcher
Here is how to update without losing your data, provided you are upgrading from an earlier DU version:
1. Back up your current DU version
2. Factory Reset
3. Wipe System/Data/Cache
4. Flash the rom
5. Do Xposed Framework if you use it
6. Restore Data partition from your previous DU version
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13601
_____________________________________________________________________________________________________
July 14. This is an update in SystemUI.apk and Settings.apk. The first one may (or may not) fix the infamous screen freezing issue and incorporates this AOSPA commit: https://github.com/AOSPA-L/android_frameworks_base/commit/0542d859b7678b40c1e39f46a75cd9eb4af68103.
The second in Settings brings Hotspot idle support based on this: https://github.com/DirtyUnicorns/android_packages_apps_Settings/commit/ccabd57818de51196e7cb82eeae266e90029bb08
Just flash the attached dirty and reboot.
Download Link: forum.xda-developers.com/attachment.php?attachmentid=3404076&d=1436880734
________________________________________________________________________________________
New build is available. Latest changes including Selinux switch, Quick settings access to the respective setting.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13497
_______________________________________________________________________________________
July 8, new kernel added
Download Link: http://forum.xda-developers.com/showpost.php?p=61766574&postcount=92
________________________________________________________________________________________
July 4, FM Radio added
Download: http://forum.xda-developers.com/showpost.php?p=61699414&postcount=88
Rom updated on June 27. This is LP 5.1.1 release 5. Latest DU and Google sources. All my hardened features included.
Additional changes (by me):
1. Network selection includes all options seen in phone test menu. Now, you can select many combinations of networks in Settings/More/Cellular Networks, as opposed to just 3g/2g/Lte, which means that your selection will stick, unlike when you make changes in test phone menu
2. SlimLauncher instead of Launcher3
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13325
______________________________________________________________________________________________________
New build is up. I think I was able to address most heat issues. There are also a few changes in DU sources in framework, telephony, vendor and DU tweaks. CPUs are running at about 32 degrees idle and about 42-47 under load. You should also see battery life improvement. There is absolutely no screen flickering (because of no overheating). This is experimental, as I have addressed some MP decision triggers, which in generic CM based kernels result in all 4 CPUs being online all the time. No wonder there was overheating.
I have also found that surprisingly the most lag free action is with Conservative governor. This is counter intuitive, but nonetheless true.. You try it and report
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13091
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Rom Updated on June 11. This is 5.1.1 release 4. Numerous changes, see DU update info in Settings:
Add USB Tether title
Various ThemeChooser fixes
Add Volume Rocker Swap button function
Add Wakelock Blocker
Add AOKP System /Listview Animations
Task Manager
Show 4G instead of LTE
Make headset notification dismissable
Allow all files over BT
Increasing ring volume
Unlink ringer and notification volumes
ADB over Network tile
Compass tile
PIN keypad shuffler
My own hardened features
Kernel with TWRP 2.8.0; overclocking, voltage, sound and kcal
Fixed Camcoder mike low recording level
Fixed Thermanager to address low charging and flickering
DOWNLOAD: http://forum.xda-developers.com/devdb/project/dl/?id=12979
___________________________________________________________________________________________________
Here is the latest Dirty Unicorns LP 5.1.1 unofficial compiled from sources on May 25. The lightest rom - only 252 mb in zip. All hardened features enabled including:
1. Removed nefarious IPs (Google, AT&T, Department of Defence and others from over 30 files in sources)
2. Hardened kernel features
3. 256 bit data encryption
4. Background WIFI scanning disabled
5. VOLTe (voice over LTE) provisioned
6. Restoring network selection is handled by system, as opposed to modem (the less control to modem, the better)
7. Latest CM and DU sources
Instructions:
1. Unlocked bootloader, root and recovery
2. Enter recovery, wipe /System/Cache/Data
3. Flash the rom and reboot
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12638
WARNINGS: I am not responsible for your device turning into a paper weight. You are on XDA, which means if anything goes wrong, blame yourself (and Putin)
Credit: DU Team; Slimroms for kernel and CM
XDA:DevDB Information
Dirty Unicorns Lollipop 5.1.1, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP; CyanogenMod
Version Information
Status: Testing
Created 2015-05-26
Last Updated 2015-10-13

New Kernel: Sound, Voltage, Color, Overclock
Here is a new kernel, which is based on CM12.1/M5
New Features:
1. All hardened features included
2. Overclocked to 2457
3. Voltage, Screen Color, Sound
4. TWRP 2.8.0 in boot image
5. Kernel compiled in DU5.1 build environment (with DU ram disk), as opposed to
generic build, which may cause issues because of different init files
Here is my voltage table, which is pretty stable:
300 mhz 730
422 mhz 740
652 mhz 760
729 mhz 770
883 mhz 790
960 mhz 805
1036 mhz 815
1190 mhz 835
1267 mhz 845
1497 mhz 855
1574 mhz 860
1728 mhz 870
1958 mhz 885
2265 mhz 955
2342 mhz 965
2457 mhz 980
Instructions: Unzip boot.img and flash in fastboot:
fastboot flash boot boot.img
fastboot reboot
Credit to MyselfM5 and to anyone who contributed to overclocking/sound/screen color
Source: https://github.com/HonamiZ1/android_kernel_sony_msm8974

soon i test this rom very thanks for the work

I have run this rom for about 24 hours and here are my impressions:
Most stable rom so far and I have tried them all. Also, good on battery. Flickering issue has been definitely fixed (by CM) and I have used their honami device with new values in thermanager. It was not easy to build, but doable, as opposed to Omnirom, which as of now, has no chance for our device. Thanks to DirtyUnicorns, they have a separate calf branch which is suitable for Z1. Don't try to use another kernel with this rom unless you copy modules too. This kernel has screen, sound settings, but no voltage, and I don't recommend tinkering with default values. I have also given up on TWRP 2.8.6, as it has major bugs resulting in overheating and failure to backup/restore. Use any version below.
The rom requires some tinkering: as such, Adaway defaults to disabled on reboot, because of DirtyUnicorn's internal adblock. If like myself, you like Adaway more, then disable adblock in Dirty Tweaks and also delete /system/etc/hosts.alt file. This way, Adaway will work fine.
A separate word on battery. It takes me 3-3.5 hours on OEM charger for a full charge from about 16%. If it takes you more or less, don't blame the rom/kernel, it is your battery dying. Forget about fast charging, it will do nothing good and for sure will destroy the battery. Heat just kills it like nothing else. If the charging is slow, the battery can't get the required voltage and the phone wouldn't report it fully charged. If it is too fast, that means that it attained the required voltage, but holding capacity has been severely reduced, which in turn means, the battery won't hold the load. Trust me, I have recently put a new battery (and new battery door) after using the phone for less than a year. Changing the battery was not a pleasant experience (the sticky they put on glass did not hold, so, I had to use glass glue,.) Why it was a battery? Because, while the phone would say battery heath is good, youtube wouldn't last for more than 20 minutes. Considering that the phone appeared in 2013, that's a miserable battery life, bit it was my fault: too much flashing and heat.

Screen freezes?
Any screen freezes on this ROM? Stayed away from AOSP cause my panel has issues with it. Would be nice to have a ROM which doesn't freeze

Wow, I've been waiting for this!
The only thing that's bothering me now is the lack of advance WiFi and Bluetooth option in the tiles (no arrow below WiFi and Bluetooth icon).

What things do or do not work? I honestly want to flash this so bad, but I'm afraid I might want to go back to my previous ROM when I find out my camera/shutter key doesn't work :/
I'm running a debloated version of the stock ROM, and I'm looking into this for an even lighter experience.
Thanks!

Quick question regarding C6902...would it be required to flash the modem separately like before on kitkat? Or has that been integrated into the rom?
Thanks.for understanding

kpbotbot said:
What things do or do not work? I honestly want to flash this so bad, but I'm afraid I might want to go back to my previous ROM when I find out my camera/shutter key doesn't work :/
I'm running a debloated version of the stock ROM, and I'm looking into this for an even lighter experience.
Thanks!
Click to expand...
Click to collapse
Camera shutter button will never work on AOSP. Just saying.

LOL. I just checked the camera hardware button and it works...

optimumpro said:
LOL. I just checked the camera hardware button and it works...
Click to expand...
Click to collapse
The launch from sleep?

AnrgKrshn said:
The launch from sleep?
Click to expand...
Click to collapse
Not the launch, but shutter...

optimumpro said:
Not the launch, but shutter...
Click to expand...
Click to collapse
I thought he meant the launch

Camera Mike Low Level Fix
This takes care of low level camera sound recording:
http://forum.xda-developers.com/xperia-z1/themes-apps/camera-low-recording-sound-permanent-fix-t3121958/post61044646#post61044646
Enjoy...

I had this bug in all 5.1 ROMs where the camera preview would work fine in low light but after pressing shutter, the photo would come out dark.
Is it still here in this ROM?

Hi, have some problems installing. When I install it seems to remove recovery and I think the efs as well since the network doesn't work at all. I've flashed it three times, each time losing recovery and having to flash the stock rom back. Thanka for your help

Reserved

bigmeech084 said:
Hi, have some problems installing. When I install it seems to remove recovery and I think the efs as well since the network doesn't work at all. I've flashed it three times, each time losing recovery and having to flash the stock rom back. Thanka for your help
Click to expand...
Click to collapse
Just do a search for Xperia Z1 recovery fota solution or fastboot any kernel with good recovery.
I don't know what efs is, but I have absolutely no network/wifi problems: works straight on boot. If you have C6902, you need to flash a file that is posted in general section.

Kernel with TWRP integrated
http://forum.xda-developers.com/showpost.php?p=60569243&postcount=136
Here is a 5.1 kernel with TWRP integrated.
Unzip it and flash in fastboot: fastboot flash boot boot.img
Remember, if you have TWRP in FOTA, don't flash this one, because you wouldn't be able to get to recovery at all.

optimumpro said:
Just do a search for Xperia Z1 recovery fota solution or fastboot any kernel with good recovery.
I don't know what efs is, but I have absolutely no network/wifi problems: works straight on boot. If you have C6902, you need to flash a file that is posted in general section.
Click to expand...
Click to collapse
Thank you. It's c6902, Could you direct me to the file Im meant to flash? Maybe efs is the wrong term, but no network and when I dial *#06# to check imei, it doesn't send a code back and doesn't seem to recognize a Sim, reflashed to stock and got network back

[JDCTeam] [Kernel] BUFFcore-o rel02 [8.x.x][AOSP/Lineage based rom] {EOL]

Buffcore oreo kernel​Samsung Galaxy S4 i9505 (jfltexx)​Release 02 - 11th June 2018​
Code:
#include
/*
* Your warranty is now void.
* And other random stuff no-one reads.
*/
Intro
I had never intended releasing this as a stand alone, but had always been aware that it would work.
With BB and Side both being busy and AOSP and OptLos stalling for a bit, the kernel from RR-oreo should I think help a bit to alleviate users battery issues.
What is it?
Buffcore 2.04 - this is a fork of BB's AOSP 8.1 kernel with added fastcharge and battery saving features.
It is the kernel supplied with RR-o release 2, so isn't needed for RR users.
Code:
renamed to buffcore;
sdfat enabled;
fastcharge implemented for faster charging (up to 1900 ac / 1000 usb);
bcmhd wakelocks for rx and tx halved;
libmemcopy and libstring sped up;
io readahead to 1024k;
lower min cpu governor frequency (270);
power efficient work queues;
voltage tweaking user interface;
faster vmstat;
autosmp hotplugging replacement;
mmc crc disabled;
allow for lower cpu voltage;
reduce swapiness;
optimise divide / multiply by power of 2;
added tcp optimisation options,;
set westwood default;
force doze screen off helper;
optimise cbfillrect function;
reduce wifi wakelock times;
nohz: reduce overhead under high-freq idling patterns.
What rom is it for?
BB's AOSP oreo
Side's OptLos 15.1
Installation
Dirty (use with current rom flash)
Extract the boot.img file from the zip (It is not a flashable zip!).
Reboot rom into twrp.
Perform a nandroid backup to be safe, incase you need to go back.
Go into Install, then select Install Image for Buffcore kernel.
Reinstall your prefered root solution (Magisk, etc).
Do not wipe caches.
Reboot.
Clean (flash as part of clean install)
Extract the boot.img file from the zip (It is not a flashable zip!).
Reboot rom into twrp.
Perform a nandroid backup to be safe, incase you need to go back.
Perform clean recomended in your rom thread.
Install rom.
Go into Install, then select Install Image for Buffcore kernel.
Reinstall your prefered root solution (Magisk, etc)
Install Gapps.
Do not wipe caches.
Reboot.
Usage
Some features will need to be forced on (IF desired) and set to apply on boot with an app like Kernel Aduitor, EXKM etc. (Fastcharge, Min cpu frquency used, Power efficient work queues, Voltage tweaking, AutoSMP hotplugging).
This kernel should / will not be compatible with stweaks.
There will essentially be no support with this, if it works then it works, or doesn't.
If it helps you then it helps you, if it doesn't tough, don't moan about it.
It has had a little testing with the roms it is intended, boots fine and seems to provide some benefit.
This may not get updated either - see it as a stop gap for the moment.
Thanks
Thanks due to Drrossum, Kesaras, CR4IGY_BOY for testing for me.
BB for original kernel and Side and TsvietOK for picks.
Download
Download from AFH here BUFFcore-o-2.04-release02-20180611.zip
md5sum - d2293a1e623ddcc68946dbea7ea12869
XDA:DevDB Information
BUFFcore-o, Kernel for the Samsung Galaxy S4
Contributors
Buff99, side
Source Code: https://github.com/Buff99/platform_kernel_samsung_jf/tree/aosp-8.1
Kernel Special Features: Fastcharge, battery saving features
Version Information
Status: No Longer Updated
Created 2018-06-18
Last Updated 2018-09-13

Reserved
might as well have one, won't be writing much tho....

Very well done, master!

Perfect. I guess it's my new optlos main kernel

side said:
Perfect. I guess it's my new optlos main kernel
Click to expand...
Click to collapse
Of course, we work better and smarter together.

Since Kernels are/should be backward compatible, any reason why this shouldn't work with RR Marshmallow?
Thx!

<CuriousCat> said:
Since Kernels are/should be backward compatible, any reason why this shouldn't work with RR Marshmallow?
Thx!
Click to expand...
Click to collapse
Backwards compatibility with kernels? Not guaranteed that I know of.
When Oreo kernels use 64 bit binder, it locks out use with ROMs that don't have 64 bit binder defined.
You'd be better trying a sidecore kernel for nougat as an intermediate, if it works then try this. A kernel flash that doesn't work should be easy to recover from if have you stock one on hand ready to reflash. Remember that any mod / root that patches the kernel will need reflash.

SideCore kernel is a no go. A stock RR Nougat kernel also. Do you think some repacking with the boot.img of the RR Marshmallow would help?

<CuriousCat> said:
SideCore kernel is a no go. A stock RR Nougat kernel also. Do you think some repacking with the boot.img of the RR Marshmallow would help?
Click to expand...
Click to collapse
if they don't work, then this is a definite no-go.
I think RR marshmallow used the stock CM13.1 kernel, nothing was changed. Your viable choice would be anything cm13 compatible.
Syzrgy & Alucard spring to mind from back in the day.

Buff99 said:
if they don't work, then this is a definite no-go.
I think RR marshmallow used the stock CM13.1 kernel, nothing was changed. Your viable choice would be anything cm13 compatible.
Syzrgy & Alucard spring to mind from back in the day.
Click to expand...
Click to collapse
Alucard can't be found for MM and Synergy is very old (and not sure how stable).
Is there a way to take the (your/lineage) source and compile it to work with MM?

<CuriousCat> said:
Alucard can't be found for MM and Synergy is very old (and not sure how stable).
Is there a way to take the (your/lineage) source and compile it to work with MM?
Click to expand...
Click to collapse
just change the ramdisk using an image kitchen

side said:
just change the ramdisk using an image kitchen
Click to expand...
Click to collapse
I was thinking the same. Let me try.

Once repacked it boots but it's unstable. After running AnTuTu a few times it restarted every time. Not a good sign.

I flashed it several times on I9505 running the LOS15.1 and everytime I reboot after flash it shows the boot up screen with the phone model and then goes to Download mode. The fix for this non booting condition is to reflash the ROM.

Pecata01 said:
I flashed it several times on I9505 running the LOS15.1 and everytime I reboot after flash it shows the boot up screen with the phone model and then goes to Download mode. The fix for this non booting condition is to reflash the ROM.
Click to expand...
Click to collapse
Where is los15.1? Which rom u mean

I meant the Optimized Lineage OS 15.1 builds Version1 on which I tried to install BUFFcore-o rel02 kernel and it didn't work. But i flashed the Lineage OS 15.1 Version2 and it's all working. Good job

Is it possible to change the max frequency? Before compiling? Or manually with an root Explorer?
Just for fun

M4verick44 said:
Is it possible to change the max frequency? Before compiling? Or manually with an root Explorer?
Just for fun
Click to expand...
Click to collapse
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all

Can you add Boeffla Wakelock Blocker to this kernel? The Wi-Fi wakelocks are still annoying.

side said:
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Click to expand...
Click to collapse
Will you add over clocking to this kernel anytime soon? @side @Buff99?, maybe @ripee
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
side said:
aka overclock.
yes its possible.not suggested though.this thing is really advanced and i dont think that u will have nice results.wont be 'fun' at all
Click to expand...
Click to collapse
Will you add over clocking to this kernel anytime soon? @side @Buff99?, maybe @ripee

[KERNEL][OREO] [SM-T830/T835] [2019-11-21] Modesty 1.0.0 [Linux 4.4.202] [ARK4]

Modesty - a modest custom kernel for the Samsung Tab S4
Modesty aims to provide a mildly appealing and reasonable alternative to the stock 4.4.78 kernel that comes with The Tab S4. In its pursuit of being both mildly appealing and reasonable, it will eschew features that could compromise device stability, whilst gleefully embracing low-risk, self-contained enhancements. In other words, your lowest expectation should be that this kernel will be at least as stable as the stock kernel.
Since there are currently no other custom kernel projects supporting the Tab S4, there isn't really any previous device-specific work to build on. Development of this kernel is therefore likely to be slow and steady.
"Why is this kernel called Modesty? That's crap! Why not Wolverine, Intrepid or Jupiter?"
Because it's just a operating-system kernel, not a turbo-charged supercar or a mission into outer space. Even as operating-system kernels go, this one is pretty dull. Besides, I'm a weary curmudgeon in his fifties, not a teenager.
This project has the modest aim of modestly enhancing the pleasure you derive from your Tab S4 and is therefore modestly named Modesty.
Key characteristics
Supports both the wi-fi only (T830) and wi-fi/LTE (T835) models.
Forked from Samsung's pristine kernel source code (Linux 4.4.78 for ARGH firmware at time of launch).
Regular merging of the upstream Linux kernel's linux-4.4.y branch (4.4.161 at time of public launch).
Regular merging of Samsung's updates to its modified kernel source as they are made available.
Includes @savoca's KCAL advanced colour/gamma control driver.
Includes @flar2's sound control driver to manage headphone and microphone gain.
Disables a huge amount of tracing and logging features inexplicably left enabled by Samsung in the stock release kernel. These debugging features have no place outside engineering builds.
Packed into a boot.img (boot image) taken directly from Samsung's latest stock firmware and kept as close to the original as possible. No obscure boot-time kernel configuration is stashed away here, and no changes are made to any other part of the file system at either install time or run time.
Provides a fully automated installer, with the option of interactive installation to allow manual selection of features and the ability to automatically root the device with Magisk in the post-installation phase.
Includes WireGuard VPN support (version 0.0.20180818 at the time of public launch), which will be updated as available.
Includes @Lord Boeffla's generic kernel wakelock blocker. The conservative default block-list is: qcom_rx_wakelock and NETLINK.
Utilises Westwood+ TCP congestion algorithm by default.
Includes Veno TCP congestion algorithm.
SELinux operates in enforcing mode and cannot be dynamically switched to permissive mode.
FAQ
Q. Is this kernel still actively developed?
A. No. The final ianmacd release was v1.0.0 on 21st November 2019 and no-one else has picked up maintenance of the project.​
Q. Will this kernel also run on Android 9.0 (Pie) devices?
A. No. Modesty targets Android 8.1 (Oreo) and there was never an intention to update it for 9.0 (Pie).​
Q. Can I overclock or underclock the CPU using this kernel?
A. No.​
Q. How does interactive installation mode work?
A. If the ZIP file name contains the string _interactive or a dot-file called .modesty_interactive is present in the root of the external SD card, interactive installation mode is triggered. Please note that this mode overrides any selections implied by the archive name or the presence of dot-files on the file-system.
In interactive mode, you will be asked whether to root the device afterwards with Magisk. Selections are made using the Volume buttons. Just follow the on-screen prompts.​
Q. Can I safely block wakelock X?
A. Perhaps. However, unless you know what a particular wakelock does and are certain that it is causing an actual problem on your device, I suggest you leave it alone.​
Q. Why is this kernel labelled beta? Is it safe to use? And who are you, anyway? Can you be trusted?
A. My T830 has been running this kernel every day since I first rooted it, and I can therefore personally vouch for its stability on this model.
A couple of users have reported Modesty running well on the T835. Initially, it was reported that the kernel did not boot on this model, but after trying several test kernels, the user in question discovered that his machine had a non-standard firmware installation. Once this situation was remedied, Modesty booted and worked as designed.
As the person who built the kernel, I know exactly what's in it, and therefore the only risk I'm exposing myself to when I run it is that of my own incompetence. That's not true for you, however, and you should exercise due caution and at least pause for a moment to consider what you are installing, and the far-reaching powers you are about to grant this unaudited code over your device. Although I link to the source code below, you have only my word for it that this bears any resemblance to the kernel actually provided in the installer.
There are likely to be many iterations of this kernel before it sees a 1.0 release. Features may be added or removed along the way, although there is no clear roadmap at this point in time. Development will go where the needs of the users take it.
Please see the Installation section below for an important note regarding the use of this kernel in combination with stock (i.e. unmodified) Samsung firmware.​
Q. Can I safely root this kernel?
A. Of course. What use would it be if you couldn't? I recommend Magisk for the task. It has a few minor issues, but as a project is very much alive, something that cannot be said about its peers. Magisk has arguably now established itself as the de facto root solution for Android devices.
It just so happens that I also produce my own builds of Magisk, which you are welcome to use. These are release builds (as opposed to debugging builds), produced from my own fork of @topjohnwu's original source, often augmented with patches. You can use anyone's builds, though.
Again, these builds work for me on various Samsung devices, but they are unofficial and you should approach them with fitting caution.​
Q. Can I install Magisk at the same time as Modesty?
A. Yes. The Modesty installer allows you to automatically root your device with Magisk following installation of Modesty..
To make use of this facility, either rename the Modesty zip file to contain the string _magisk or create a file called .modesty_magisk in either the root of your external SD card or in the standard Download directory of the internal SD card. Alternatively, you can utilise interactive installation mode. See above for details.
If any of these trigger conditions is met, the installer will look in the standard internal Download directory as well as in ./Magisk (if present) on the external SD card (if present) for a suitable Magisk zip file to install. Preference is given to versioned files matching the glob Magisk-v*, in which case the latest according to lexical sort order will be used. If none is found, the installer then looks for unversioned release builds (e.g. official Canary channel release builds) called magisk-release.zip in the same locations, selecting the one with the most recent timestamp. If none is found, the installer will then try to find unversioned debug builds (e.g. official Canary channel debug builds) called magisk-debug.zip, again picking the one with the most recent timestamp. Finally, the installer falls back to looking for the most recent file called Magisk.zip or magisk.zip. If still no files have been found by this stage, chaining of Magisk is abandoned.
For example:
Code:
star2lte:/ $ ls -l /storage/0000-0000/.modesty_magisk
-rwxrwx--x 1 root sdcard_rw 0 2018-09-15 14:31 /storage/0000-0000/.modesty_magisk
star2lte:/ $ ls /storage/0000-0000/Magisk/Magisk-* | tail -n 3
/storage/0000-0000/Magisk/Magisk-v17.2-2018091001-ianmacd.zip
/storage/0000-0000/Magisk/Magisk-v17.2-2018091201-ianmacd.zip
/storage/0000-0000/Magisk/Magisk-v17.2-2018091501-ianmacd.zip
When you flash the Modesty archive in TWRP, the most recent version of Magisk that could be found will now be used to automatically root your kernel, i.e. Magisk-v17.2-2018091501-ianmacd.zip in this example.​
Q. Why doesn't Modesty have its own Telegram group?
A. Because my experience of Android-themed Telegram groups is that they invariably degenerate into seething cesspits of rudeness, ignorance, superstition and — on a good day — pseudo-science. I don't wish to police such a den of iniquity. Of course, it's a free world (or so I still like to kid myself), so you are at liberty to create your own Telegram group for Modesty if you wish. Just please don't invite me to it.​
Building
Building the kernel from source is beyond the scope of this document. If you want to build this kernel from scratch, for example to change its configuration, start with this handy reference tailored to building kernels for Android.
Download
See posting #2 in this thread for links to the latest and all previous versions.
Known Issues
Bluetooth HID (input) devices do not work.
Versions 0.99.11 to 0.99.22 contained a bug that caused Bluetooth HID (input) devices, such as mice, keyboards and gamepads, not to function. They could be paired with the tablet, but their input was not recognised. This bug was finally traced and fixed in 0.99.23.​
Installation
Make a back-up of your existing boot partition using the custom recovery environment provided by TWRP. If your device doesn't yet have TWRP, you will need to install it first. Then, use it to flash the Modesty ZIP file. The boot image will automatically be installed in the boot partition of your device.
If your device has unmodified Samsung firmware, you will encounter problems with Bluetooth (namely delayed initialisation and forgotten pairings) after installing this or any other custom kernel. To remedy this, you will need to patch your system with modified libsecure_storage.so libraries. Some custom kernel installers actually install these without telling you, overwriting your system libraries and transparently circumventing the problem before you can run into it. This approach necessarily modifies your device's file-system, however, and that may not be what you want. At the very least, the user should be made aware what is happening to his device.
For this reason, I have instead prepared a companion Magisk module that achieves the same goal without modifying the file-system. This will allow you to run a custom kernel (not just this one, but any custom kernel) on pristine stock firmware without any Bluetooth issues. The module can be found in the official Magisk module repository, accessible from Magisk Manager on your tablet. If you install this Magisk module, you may wish to also disable the secure_storage_daemon by editing /system/etc/init/secure_storage_daemon.rc (change start to stop), as it no longer serves a purpose.
In a similar vein, you may encounter authentication errors when connecting to wireless networks after installing this or any other custom kernel. This problem is not serious and easily remedied by re-entering your passphrase for the networks you use.
Finally, if SecurityLogAgent notifies you that unauthorised actions have been detected, do not be alarmed. This is a normal consequence of having installed a custom kernel. You may wish to disable SecurityLogAgent to avoid being repeatedly notified..
Whilst the above issues are the only ones you can expect to encounter when running this kernel vs. the stock Samsung kernel, they may sound like more trouble than they're worth. In that case, you might be happier just sticking to Samsung's stock kernel. The company supplies a perfectly good kernel straight from the factory.
Configuration
You are encouraged to use either @morogoku's excellent MTweaks (a modified version of Kernel Aduitor) or @flar2's EX Kernel Manager to manage the features provided by this kernel.
Source code
Modesty's GitHub repository.
References
A useful guide to CPU governors, I/O schedulers (and more).
For more information on the some of the individual schedulers included in this kernel, you can also look under Documentation/block in the kernel source.
The WireGuard user guide, control app, home page and source code.
Credits
Thank you to everyone in the Linux kernel universe for getting us this far. Within the Android development community, I am grateful to the following people for their time-saving contributions:
@osm0sis for Android Image Kitchen, which has saved me a huge amount of work in packing and unpacking boot images.
An honorary mention must go to @Chainfire, the extent of whose benefaction to the Android community is still not fully understood or appreciated in some quarters.

Change log
v1.0.0 (final ianmacd release) (2019-11-21)
Kernel proclaimed stable. Version number incremented. No code changes since v0.99.49.
v0.99.49 (2019-11-16)
Updated to Linux 4.4.202.
v0.99.48 (2019-11-13)
Updated to Linux 4.4.201.
v0.99.47 (2019-11-11)
Updated to Linux 4.4.200.
v0.99.46 (2019-11-06)
Updated to Linux 4.4.199.
v0.99.45 (2019-10-31)
Updated to Linux 4.4.198.
v0.99.44 (2019-10-19)
Updated to Linux 4.4.197.
v0.99.43 (2019-10-08)
Updated to Linux 4.4.196.
v0.99.42 (2019-10-07)
Updated to Linux 4.4.195.
v0.99.41 (2019-09-22)
Updated to Linux 4.4.194.
v0.99.40 (2019-09-16)
Updated to Linux 4.4.193.
v0.99.39 (2019-09-11)
Updated to Linux 4.4.192.
Fixes unavailability of external SD card in Modesty 0.99.38.
v0.99.38 (2019-09-08) Release withdrawn (External SD card unavailable)
Updated to Linux 4.4.191.
v0.99.37 (2019-08-26)
Updated to Linux 4.4.190.
v0.99.36 (2019-08-12)
Updated to Linux 4.4.189.
v0.99.35 (2019-08-07)
Updated to Linux 4.4.188.
v0.99.34 (2019-08-05)
Updated to Linux 4.4.187.
v0.99.33 (2019-07-23)
Updated to Linux 4.4.186.
v0.99.32 (2019-07-12)
Updated to Linux 4.4.185.
v0.99.31 (2019-06-28)
Updated to Linux 4.4.184.
v0.99.30 (2019-06-22)
Updated to Linux 4.4.183.
v0.99.29 (2019-06-18)
Updated to Linux 4.4.182.
v0.99.28 (2019-06-12)
Updated to Linux 4.4.181.
v0.99.27 (2019-05-17)
Updated to Linux 4.4.180.
v0.99.26 (2019-04-28)
Updated to Linux 4.4.179.
v0.99.25 (2019-04-07)
Updated to Linux 4.4.178.
v0.99.24 (2019-03-26)
Updated to Linux 4.4.177.
Build only the latest revision of the DTB.
v0.99.23 (2019-03-02)
Fixed bug, introduced in v0.99.11, that caused input from Bluetooth HID devices, such as keyboards, mice and gamepads to be ignored.
v0.99.22 (2019-02-23)
Updated to Linux 4.4.176.
v0.99.21 (2019-02-20)
Updated to Linux 4.4.175.
v0.99.20 (2019-02-11)
Updated to Linux 4.4.174.
v0.99.19 (2019-02-08)
Updated to Linux 4.4.173.
v0.99.18 (2019-01-26)
Updated to Linux 4.4.172.
v0.99.17 (2019-01-17)
Updated to Linux 4.4.171.
v0.99.16 (2019-01-13)
Updated to Linux 4.4.170.
v0.99.15 (2018-12-30)
Rebased on ARK4 kernel source code and boot images.
v0.99.14 (2018-12-23)
Updated to Linux 4.4.169.
Merged four more UPSTREAM commits from android-4.4 kernel branch.
v0.99.13 (2018-12-13)
Updated to Linux 4.4.167.
Merged selected BACKPORT and UPSTREAM commits from android-4.4 kernel branch.
v0.99.12 (2018-12-05)
Updated to Linux 4.4.166.
Realtek USB Ethernet driver upgraded from v2.08.0 to v2.10.00.
v0.99.11 (2018-11-29)
Updated to Linux 4.4.165.
KCAL advanced colour/gamma control driver optimisation.
Added @flar2's sound control driver for controlling headphone and microphone gain. (Configure with MTweaks or EX Kernel Manager).
v0.99.10 (2018-11-21)
Updated to Linux 4.4.164.
Added KCAL advanced colour/gamma control driver. (Configure with MTweaks or EX Kernel Manager).
Lots of tracing and debug logging disabled, further reducing kernel size.
CONFIG_DISPLAY_USE_INFO
CONFIG_SEC_DISPLAYPORT_LOGGER
CONFIG_FB_MSM_MDSS_XLOG_DEBUG
CONFIG_SEC_FILE_LEAK_DEBUG
CONFIG_SEC_DEBUG_USER
CONFIG_SEC_DEBUG_SUMMARY
CONFIG_SCSI_UFSHCD_CMD_LOGGING
CONFIG_MSM_SMEM_LOGGING
CONFIG_PROFILING
CONFIG_DEBUG_INFO
CONFIG_SCHED_DEBUG
CONFIG_SEC_PM_DEBUG
CONFIG_CORESIGHT
Built as monolithic kernel (i.e. without CONFIG_MODULES).
Built as relocatable code (CONFIG_RELOCATABLE_KERNEL).
Assembler symbols stripped (CONFIG_STRIP_ASM_SYMS set).
Embedded kernel config (reported via /proc/config.gz) now falsely reports stock settings to allow disabling of superfluous kernel features that otherwise cause grave Android System warning on boot.
v0.99.9 (2018-11-13)
Rebased on ARJ3 kernel source code and boot images.
v0.99.8 (2018-11-10)
Updated to Linux 4.4.163.
More than 100 fixes applied from upstream AOSP android-4.4 and android 4.4-o branches.
Lots of tracing and debug logging disabled:
CONFIG_IPC_LOGGING (debug logging for IPC drivers)
CONFIG_QCOM_RTB (register tracing)
CONFIG_TRACER_PKT (for tracing IPC protocols)
CONFIG_FTRACE (kernel tracing infrastructure)
CONFIG_CPU_FREQ_SWITCH_PROFILER (CPU frequency switch profiler)
CONFIG_TRACING_EVENTS_GPIO (traces GPIO subsystem)
Fixes to allow kernel to build when above logging and tracing options are disabled.
v0.99.7 (2018-10-30)
Rebased on ARH5 kernel source code.
Reworked the v4l2 fix that restores liboemcrypto-dependent apps to working state.
v0.99.6 (2018-10-28)
v4l2 fixes to restore liboemcrypto-dependent apps to working state.
v0.99.5 (2018-10-21)
Updated to Linux 4.4.162.
v0.99.4 (2018-10-19)
Initial public release, based on Linux 4.4.161.
v0.99.3
Internal build, based on Linux 4.4.160.
v0.99.2
Internal build, based on Linux 4.4.159.
v0.99.1
Initial internal build, based on Linux 4.4.78.

It begins! Awesome to finally see a custom kernel for the Tab S4.

I want to test for you once I can get root back

ianmacd said:
Change log
v0.99.4 (2018-10-19)
Initial public release, based on Linux 4.4.161. Caution: This kernel remains completely untested on the T835.
v0.99.3
Internal build, based on Linux 4.4.160.
v0.99.2
Internal build, based on Linux 4.4.159.
v0.99.1
Initial internal build, based on Linux 4.4.78.
Click to expand...
Click to collapse
Flashed on T835 device doesnt even get past the Boot (custom device) screen is there a way to get logs without using a computer?
Sent from my Samsung SM-G950F using XDA Labs

dr460nf1r3 said:
Flashed on T835 device doesnt even get past the Boot (custom device) screen is there a way to get logs without using a computer?
Click to expand...
Click to collapse
I'll look into it this evening. I'm just about to get off a plane.
Were there any errors when installing? Was your device properly detected as a T835?
Sent from my SM-G965F using XDA Labs

ianmacd said:
I'll look into it this evening. I'm just about to get off a plane.
Were there any errors when installing? Was your device properly detected as a T835?
Click to expand...
Click to collapse
Installing just fine, correctly detected as well.
Sent from my Samsung SM-G950F using XDA Labs

dr460nf1r3 said:
Installing just fine, correctly detected as well.
Click to expand...
Click to collapse
I've gone through the ramdisk of the T835's boot image with a fine-tooth comb and can find nothing untoward. I also verified that I properly removed the dm-verity flag from the T835's device tree.
There are actually very few source code differences between the T830 and T835. Both can be built from a single tree. The only differences lie in the kernel config file and the device tree, but I am building with the default T835 configuration, and with the proper device tree for that device.
Let's try at least ruling out my installer code. Please image-flash this new boot image[/i] to your device and tell me if it boot-loops. If it does, my installer isn't the problem, because it's only used for a ZIP flash. I've already checked the installer code and can't see any bugs, so I don't think the issue lies there.
Can you also please tell me which version of the firmware your device is running? Possibly there's an issue there, too. Samsung has so far released the source to the ARGH kernel only. This seems to work fine on my ARH5 firmware, but it's uncertain whether it would still work on something based on ARI*, and I've seen that a couple of countries do now have ARI firmware available. Mind you, even if it wasn't compatible, it should still get as far as booting.
Anyway, please test that boot image and let me know your firmware version.

While I soldier on with the issues afflicting the T835 build, can anyone else verify the T830 build as working for them?
Don't be shy; I'm running it on my own device, so I'm certain that build boots.

ianmacd said:
While I soldier on with the issues afflicting the T835 build, can anyone else verify the T830 build as working for them?
Don't be shy; I'm running it on my own device, so I'm certain that build boots.
Click to expand...
Click to collapse
Sorry for the noob question if i flash this kernal on my SM-T835 will i lose DEX ? Sorry i'm not quite understanding what KERNEL does ? Thanks in advance!

N1NJATH3ORY said:
Sorry for the noob question if i flash this kernal on my SM-T835 will i lose DEX ? Sorry i'm not quite understanding what KERNEL does?
Click to expand...
Click to collapse
When the kernel is working as intended, you won't lose DeX, but it currently isn't even booting on the T835.
Only those who are able to assist in debugging the current boot failure should install the T835 build at this time.
The T830 build, on the other hand, is rock solid for me, and I encourage anyone who is capable of recovering from an unexpected bootloop to try it out.

Version 0.99.5 released.
This release updates the kernel to the latest upstream Linux.
T830 owners, install at will. T835 owners, beware: The previous release has been reported unbootable on this model, and this release is likely to be similarly afflicted. Investigations are ongoing. Until this issue is resolved, the whole project has been downgraded to alpha status.
Change log
Updated to Linux 4.4.162. Caution: This release is likely to cause a bootloop on the T835.

ianmacd said:
I've gone through the ramdisk of the T835's boot image with a fine-tooth comb and can find nothing untoward. I also verified that I properly removed the dm-verity flag from the T835's device tree.
There are actually very few source code differences between the T830 and T835. Both can be built from a single tree. The only differences lie in the kernel config file and the device tree, but I am building with the default T835 configuration, and with the proper device tree for that device.
Let's try at least ruling out my installer code. Please image-flash this new boot image[/i] to your device and tell me if it boot-loops. If it does, my installer isn't the problem, because it's only used for a ZIP flash. I've already checked the installer code and can't see any bugs, so I don't think the issue lies there.
Can you also please tell me which version of the firmware your device is running? Possibly there's an issue there, too. Samsung has so far released the source to the ARGH kernel only. This seems to work fine on my ARH5 firmware, but it's uncertain whether it would still work on something based on ARI*, and I've seen that a couple of countries do now have ARI firmware available. Mind you, even if it wasn't compatible, it should still get as far as booting.
Anyway, please test that boot image and let me know your firmware version.
Click to expand...
Click to collapse
Firmware Version ist arh5 and after flashing your img the device still constantly reboots on the start screen and doesnt even get to the boot Screen
Sent from my Samsung SM-G950F using XDA Labs

dr460nf1r3 said:
Firmware Version ist arh5 and after flashing your img the device still constantly reboots on the start screen and doesnt even get to the boot Screen
Click to expand...
Click to collapse
Thanks. That absolves the installer of any wrongdoing, at least.
Something is fundamentally wrong with the kernel for the T835.
The boot image is taken from stock firmware, and modified just enough to allow a custom kernel to boot. I very much doubt the problem lies there. A virtually identical image works for the T830.
The kernel config used is the one supplied by Samsung. The only modifications made to it are the same ones I made to the T830's.
I think my next step will be to produce a kernel built without downstreaming the 4.4.y Linux branch, so back to 4.4.78. If that works, it will indicate that an error affecting only the T835 was introduced during all of my merging of the upstream kernel.
I'll post again when I've built the kernel, which won't be for a few hours, as I'm on holiday at the moment.
Sent from my SM-G965F using XDA Labs

ianmacd said:
I think my next step will be to produce a kernel built without downstreaming the 4.4.y Linux branch, so back to 4.4.78. If that works, it will indicate that an error affecting only the T835 was introduced during all of my merging of the upstream kernel.
Click to expand...
Click to collapse
OK, @dr460nf1r3, please try this new T835 build.
This is rewound to 4.4.78, with just a few extra cherry-picked commits to enable it to build cleanly and boot without triggering dm-verity.
In other words, this kernel should be 99% identical to the one that shipped with the machine. This assumes that the source as supplied by Samsung was actually used to build the stock kernel.. They have been known to publish sources that don't match what's on the machine.

ianmacd said:
OK, @dr460nf1r3, please try this new T835 build.
This is rewound to 4.4.78, with just a few extra cherry-picked commits to enable it to build cleanly and boot without triggering dm-verity.
In other words, this kernel should be 99% identical to the one that shipped with the machine. This assumes that the source as supplied by Samsung was actually used to build the stock kernel.. They have been known to publish sources that don't match what's on the machine.
Click to expand...
Click to collapse
Thanks, flashing now will report back in a few minutes
Sent from my Samsung SM-G950F using XDA Labs
---------- Post added at 05:44 PM ---------- Previous post was at 05:17 PM ----------
ianmacd said:
OK, @dr460nf1r3, please try this new T835 build.
This is rewound to 4.4.78, with just a few extra cherry-picked commits to enable it to build cleanly and boot without triggering dm-verity.
In other words, this kernel should be 99% identical to the one that shipped with the machine. This assumes that the source as supplied by Samsung was actually used to build the stock kernel.. They have been known to publish sources that don't match what's on the machine.
Click to expand...
Click to collapse
Did not work still the same issue.. flashed via twrp to boot partition. Noob question, the boot backup i got is 64mb while your kernel hardly has 25.. whats going on here?
Sent from my Samsung SM-G950F using XDA Labs

dr460nf1r3 said:
Did not work still the same issue.. flashed via twrp to boot partition.
Click to expand...
Click to collapse
Well, that's disappointing. I was hoping that it was my screw-up, rather than Samsung's, but at this point almost everything I've done has been backed out and it still won't boot.
Noob question, the boot backup i got is 64mb while your kernel hardly has 25.. whats going on here?
Click to expand...
Click to collapse
Good question.
Your back-up is of the entire partition, including the area with no data on it, so you're getting a file the same size as the partition itself. My boot image contains just the data segment, so it's smaller.
If you pull the stock boot image from the AP file of Samsung's firmware, you'll see that it's a very similar size to mine (slightly smaller, actually):
Code:
$ unzip -p T835XXU1ARH5_T835OXM1ARH5_PHN.zip AP_T835XXU1ARH5_CL14008523_QB19263559_REV00_user_low_ship_MULTI_CERT_meta.tar.md5| tar xf - -O boot.img.\*lz4 | lz4 -dc > boot.img
$ ls -l boot.img
-rw-rw-r--. 1 ianmacd ianmacd 23593232 Oct 21 22:01 boot.img
$ file boot.img
boot.img: Android bootimg, kernel (0x8000), ramdisk (0x2000000), page size: 4096, cmdline (console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_le)
So, what now?
I'll see which other minor changes I can back out, in an effort to arrive at a kernel built from source that is as close to stock as possible. If you're wondering Why doesn't he just build from pristine sources?, the answer is: Because Samsung's source code won't even build out of the box. Many of the kernel header files are simply not in the expected locations. Alas, this is a fairly common problem with Samsung's kernel source code releases.
I suspect the solution to this problem may actually lie in changes that have yet to be made, rather than changes made that need to be reverted. In other words, the T835 may require some kernel modifications or configuration that the T830 doesn't. Theoretically, a kernel compiled from Samsung's pristine sources should just work, but that's starting to look unlikely now.
I'm hoping that I can enable/disable a few further options in the kernel config, rebuild and produce a kernel that works for you. If, however, the problem is that the source itself is faulty, we may have to wait for a future release by Samsung to give us something that compiles into a working kernel.
But I don't intend to throw in the towel on the T835 just yet. There are still a few more things we can try.

ianmacd said:
Well, that's disappointing. I was hoping that it was my screw-up, rather than Samsung's, but at this point almost everything I've done has been backed out and it still won't boot.
Good question.
Your back-up is of the entire partition, including the area with no data on it, so you're getting a file the same size as the partition itself. My boot image contains just the data segment, so it's smaller.
If you pull the stock boot image from the AP file of Samsung's firmware, you'll see that it's a very similar size to mine (slightly smaller, actually):
So, what now?
I'll see which other minor changes I can back out, in an effort to arrive at a kernel built from source that is as close to stock as possible. If you're wondering Why doesn't he just build from pristine sources?, the answer is: Because Samsung's source code won't even build out of the box. Many of the kernel header files are simply not in the expected locations. Alas, this is a fairly common problem with Samsung's kernel source code releases.
I suspect the solution to this problem may actually lie in changes that have yet to be made, rather than changes made that need to be reverted. In other words, the T835 may require some kernel modifications or configuration that the T830 doesn't. Theoretically, a kernel compiled from Samsung's pristine sources should just work, but that's starting to look unlikely now.
I'm hoping that I can enable/disable a few further options in the kernel config, rebuild and produce a kernel that works for you. If, however, the problem is that the source itself is faulty, we may have to wait for a future release by Samsung to give us something that compiles into a working kernel.
But I don't intend to throw in the towel on the T835 just yet. There are still a few more things we can try.
Click to expand...
Click to collapse
Thanks for explaining everything for me. Id like to help you were i can but i dont have a computer by my hands right now for the next time
Sent from my gts4llte using XDA Labs

dr460nf1r3 said:
Thanks for explaining everything for me. Id like to help you were i can but i dont have a computer by my hands right now for the next time
Click to expand...
Click to collapse
Here's a new build to try. This one reverts the last few changes I originally made to the T835's kernel configuration before building. This is as close to stock as possible, whilst still being able to build.
If this doesn't boot, it pretty much means that Samsung has supplied code for the T835 that simply will not compile into a working kernel. At that point, we'll probably have to wait for updated sources. I already have a request pending with Samsung for the release of the BRI sources.
Just to be clear, the current status quo as I understand it is that the Samsung logo never starts to be written from left to right. You never get past the static screen with the device name and the word Custom. Is that correct?

ianmacd said:
Here's a new build to try. This one reverts the last few changes I originally made to the T835's kernel configuration before building. This is as close to stock as possible, whilst still being able to build.
If this doesn't boot, it pretty much means that Samsung has supplied code for the T835 that simply will not compile into a working kernel. At that point, we'll probably have to wait for updated sources. I already have a request pending with Samsung for the release of the BRI sources.
Just to be clear, the current status quo as I understand it is that the Samsung logo never starts to be written from left to right. You never get past the static screen with the device name and the word Custom. Is that correct?
Click to expand...
Click to collapse
Im sorry to tell you but this doesnt boot either in fact it doesnt even reboot the static screen. Your right about the current status quo sadly.
Sent from my Samsung SM-G950F using XDA Labs

[Kernel][04.01.2022][Android 11] Kirisakura 1.0.0_R for Asus Rog Phone 2 aka Yoda

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.