Dragonfly Kernel v1.5 for the LG G8 Korean / US
Introduce
First of all, I'd like to thank Metaphysics team for giving the first custom kernel of G8 USA. Unfortunately I'm using G8 - Korean and they haven't released version for the Korean variant yet. I had to learn how to build a kernel for myself based on their kernel source. However, I want to learn more so I decided to compile the kernel from LGE open source. Now, my kernel is quite stable to be released and shared to the G8 community. You can call it the Dragonfly kernel.
Main Features:
- Based on LGE open source LMG820N_Android_Q_v20r: http://opensource.lge.com/osSch/list?types=NAME&search=g820n
- Linux-Stable-Upstream included to latest 4.14.205
- Next-Gen CAF-Tag LA.UM.8.11.r1-02600-NICOBAR.0 merged
- Regular CAF-Tag for SD855 merged LA.UM.8.1.r1-16200-sm8150.0
- Compiled by ProtonClang 12.0.0 with -O3 speed optimizations
- No VLAs
- Magisk included
- F2FS support
EAS related features:
- EAS implementation patched up to latest CAF state
- Disable autogroups and use cgroups for more efficient task placement
- CPU input boost
File System related features:
- Include rapid GC by @arter97
Network related features:
- Wireguard Support (Details)
- Add new TCP congestion algorithm: BBR2, agilesd
Memory related features:
- Include zstd
Wakelock Blocker:
- Add Boeffla Wakelock Blocker v1.1.0
- The most common and safe wakelocks are blocked by default: qcom_rx_wakelock;wlan;wlan_wow_wl;wlan_extscan_wl;netmgr_wl;NETLINK
How to flash the Kernel:
- You can flash the kernel zip file via TWRP or Magisk
- You can also extract the new_boot.img to flash it via fastboot mode
Known bugs:
- You tell me
DOWNLOAD:
Download is located always in
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases
Important: Read after Download
Be sure to turn off Secure start-up before flash this kernel
Credits:
- Metaphysics kernel team: https://github.com/KamioRinn/Metaphysics_LGE_G820_Kernel
- SGCMarkus for his guide of building kernel and TWRP
- Erick G for bringing new TWRP to G8 which supports F2FS
- Jean Carlos Bencosme for adding / picking kernel features
- Kirisakura for his great kernels
- Sultanxda for his simple_lmk
- LGE for the kernel open source
- All other great kernel devs
Contributors
quantan
Source Code: https://github.com/anht3889/LGE_G820_Kernel_Caf
XDA:DevDB Information
Dragonfly, Kernel for the LG G8
Contributors
quantan
Kernel Special Features:
Version Information
Status: Stable
Created 2020-09-16
Last Updated 2020-11-14
Previous versions, e.g. v1.4, don't work with the new TWRP 3.4. Therefore, I use Anykernel from v1.5. I recommend you follow the steps below:
1. Install magisk patched stock boot.img
2. Install new TWRP 3.4 from Magisk Manager
3. Reboot to TWRP
4. Install Magisk and reboot to TWRP
5. Install Disable Verity zip file and reboot to TWRP
6. Install my kernel Dragonfly v1.5
For newer version, i.e. v1.6, you don't need to repeat all steps above. You just want to flash thew newest Dragonfly.
And good news to you guys, TWRP 3.4 supports F2FS so I decided to enable F2FS support in my kernel as well. To make F2FS, please follow these steps:
1. Install my kernel v1.5
2 .Reboot to TWRP 3.4
3. Change file system of /data to F2FS
4. Replace the attached modified fstab to support F2FS of /data
5. Reboot
Note: You will lose your data.
In case you don't know:
- TWRP-3.4.0.0-G820N.zip and fstab.alphaplus for G8 Korean
- TWRP-3.4.0.0-G820UM.zip and fstab.alphalm for G8 US
Give credits to Erick G and @SGCMarkus for bringing TWRP to our phones.
Changelog:
v1.5:
- Fix touch issues for TWRP
- Add Kcal
- Add KLapse v5.0
- Update to 4.14.205
- Update lze and add lzo-lre for Zram
- Use Anykernel
v1.4:
- Import LGE v20r open source changes
- Upstream to linux-stable v4.14.203
- Upstream CAF LA.UM.8.1.r1-16200-sm8150.0
- Fix audio and OK Google hot word issues
- Improve schedutil
- Power saving workingqueues enabled by default
- Change various drivers ( MM, audio) to user power efficient workingqueues. Thanks to @Freak07 's commits
- Update sdcardfs
v1.3:
- Merge tag 'LA.UM.8.11.r1-04300-NICOBAR.0'
- Add ntfs and exfat support
v1.1 - v1.2 - Intial kernel
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
tron1 said:
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
Click to expand...
Click to collapse
Thank your for pointing it out. I just add exfat and ntfs support to v1.3. Enjoy it
tron1 said:
Good work ...mostly. Huge showstopper is the missing support for exfat/ntfs with sdcard. With USB exfat is working. Only fat32 formatted sdcards are working. But this is a nogo with files > 4GB
Click to expand...
Click to collapse
Which exact Model do you use? Is there a specific german Model nesessary?
Deutschmann said:
Which exact Model do you use? Is there a specific german Model nesessary?
Click to expand...
Click to collapse
It doesn't work on any LG g8s models...
@quantan Could you make it compatible with LG G8s models? LM-G810 is the model code
Hi Guys. The new v1.4 is just released. I have been quite busy due to family and work stuff. Here is the changelog:
- Import LGE v20r open source changes
- Upstream to linux-stable v4.14.203
- Upstream CAF LA.UM.8.1.r1-16200-sm8150.0
- Fix audio and OK Google hot word issues
- Improve schedutil
- Power saving workingqueues enabled by default
- Change various drivers ( MM, audio) to user power efficient workingqueues. Thanks to @Freak07 's commits
- Update sdcardfs
Eduxki said:
@quantan Could you make it compatible with LG G8s models? LM-G810 is the model code
Click to expand...
Click to collapse
I'll check if I can make a version for LG G8s tomorrow. However, I can't guarantee that it will work for G8s or not since I don't have that phone. @Eduxki Give me your model, e.g. LMG810EA, and your operator / country as well. Is Android 10 available for your phone now since this kernel is for Android 10
quantan said:
Hi Guys. The new v1.4 is just released. I have been quite busy due to family and work stuff. Here is the changelog:
- Import LGE v20r open source changes
-...
Click to expand...
Click to collapse
thanks for your hard work! i just installed it on my G820N with latest 20s-fw... seems to be working fine so far.
PS: installed it via TWRP, and had twrp re-inject itself into the boot-img afterwards again.... => would be nice if your prepared installer zip-file would not just include magisk, but also twrp (just as a safety-measure to not loose twrp when installing your kernel.
PPS: after your src rebase/update to that 20r kernel source drop, "dragonfly" is working with my 20s-fw image again!! your previous version with only 20a kernel src only worked until 20m (march sec-patch) firmware, neither 20o nor 20s could run stable on that 20a-kernel. gui hung, apps didn't respond etc... thankful that 20s-fw finally runs stable so far on those 20r-kernel updated version.
kimba99 said:
thanks for your hard work! i just installed it on my G820N with latest 20s-fw... seems to be working fine so far.
PS: installed it via TWRP, and had twrp re-inject itself into the boot-img afterwards again.... => would be nice if your prepared installer zip-file would not just include magisk, but also twrp (just as a safety-measure to not loose twrp when installing your kernel.
PPS: after your src rebase/update to that 20r kernel source drop, "dragonfly" is working with my 20s-fw image again!! your previous version with only 20a kernel src only worked until 20m (march sec-patch) firmware, neither 20o nor 20s could run stable on that 20a-kernel. gui hung, apps didn't respond etc... thankful that 20s-fw finally runs stable so far on those 20r-kernel updated version.
Click to expand...
Click to collapse
Thank you for your feedback. Actually in Dragonfly v1.3 I did lots of changes to schedultil based on Pixel 4 XL kernel. However it didn't work well. Sorry about that. In the v1.4, I revert the changes and make other improvement to schedutil gov.
I'll look into the TWRP injection and hopefully it will be available in v1.5 or 1.6. Any other features you guys want, please let me know.
quantan said:
Thank you for your feedback. Actually in Dragonfly v1.3 I did lots of changes to schedultil based on Pixel 4 XL kernel. However it didn't work well. Sorry about that. In the v1.4, I revert the changes and make other improvement to schedutil gov.
I'll look into the TWRP injection and hopefully it will be available in v1.5 or 1.6. Any other features you guys want, please let me know.
Click to expand...
Click to collapse
as for TWRP integration: keep in mind that there are also separate versions for INTL vs KOR edition of TWRP, just like with the kernel itself!
further ideas? :cyclops: ... fix touchscreen in recovery => code fixes already exist, check here:
https://github.com/ErickG233/LMV500-sm8150_kernel/commit/1b5b93d72ec87054ef2d80c8d955dcdaa40d4332
if i come up with additional ideas i'll let u know.
PS: it's been a while since i last modded/hacked/upgraded android kernels :good:
PPS: maybe sth like the ooooold "crossbreeder" mod =>
https://github.com/f1vefour/CrossBreeder ... but i'm unsure if this is still relevant and or working on "10"... as the original code is rather... dated
Thank you for your efforts. Is there a GSI suitable for g820?
kimba99 said:
as for TWRP integration: keep in mind that there are also separate versions for INTL vs KOR edition of TWRP, just like with the kernel itself!
further ideas? :cyclops: ... fix touchscreen in recovery => code fixes already exist, check here:
https://github.com/ErickG233/LMV500-sm8150_kernel/commit/1b5b93d72ec87054ef2d80c8d955dcdaa40d4332
if i come up with additional ideas i'll let u know.
PS: it's been a while since i last modded/hacked/upgraded android kernels :good:
PPS: maybe sth like the ooooold "crossbreeder" mod =>
https://github.com/f1vefour/CrossBreeder ... but i'm unsure if this is still relevant and or working on "10"... as the original code is rather... dated
Click to expand...
Click to collapse
- The fix for touchscreen in recovery is added to my kernel.
- I currently have no idea about TWRP. I have ramdisk with TWRP but no magisk. Can you install TWRP and Magisk then export boot.img and give it me? I will extract ramdisk from it then integrate the ramdisk to my kernel.
lufan said:
Thank you for your efforts. Is there a GSI suitable for g820?
Click to expand...
Click to collapse
Havoc, Bliss, Lineageos GSI should be good.
quantan said:
- The fix for touchscreen in recovery is added to my kernel.
- I currently have no idea about TWRP. I have ramdisk with TWRP but no magisk. Can you install TWRP and Magisk then export boot.img and give it me? I will extract ramdisk from it then integrate the ramdisk to my kernel.
Havoc, Bliss, Lineageos GSI should be good.
Click to expand...
Click to collapse
It can be used, but it can't double-click the wake-up screen, the display after the screen is not turned off, and the vibration intensity is not adjustable. I backup the g820 boot through twrp, which contains magisk. I hope you can use it
https://drive.google.com/file/d/17I-m9QdmOzn7CXH3hOl-c04Jnvd7GC3P/view?usp=sharing
wrote you a PM quantan, with my backup stuff in it likewise.
cheers and best regards =)
lufan said:
It can be used, but it can't double-click the wake-up screen, the display after the screen is not turned off, and the vibration intensity is not adjustable. I backup the g820 boot through twrp, which contains magisk. I hope you can use it
https://drive.google.com/file/d/17I-m9QdmOzn7CXH3hOl-c04Jnvd7GC3P/view?usp=sharing
Click to expand...
Click to collapse
kimba99 said:
wrote you a PM quantan, with my backup stuff in it likewise.
cheers and best regards =)
Click to expand...
Click to collapse
Could you guys test the kernel v1.5 with TWRP to make sure it work. Thank you.
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases/tag/v1.5-test
quantan said:
Could you guys test the kernel v1.5 with TWRP to make sure it work. Thank you.
https://github.com/anht3889/LGE_G820_Kernel_Caf/releases/tag/v1.5-test
Click to expand...
Click to collapse
I saw this link in TG channel. It has been tested. Twrp can't access it
@lufan Have you tried it. If not please try it to double check. The ramdisk from KR boot is working.
Related
KaminariKernel
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now (even more) 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 simply grab my popcorn and laugh at you.
*
* Tl;dr: if your device crashes and burns, and if you get screwed up because of that, it's entirely your fault.
*/
Hiya fellas.
I suppose yall know that there's a ported rom from titan/thea (IDCrisis) for our Moto G. And I've ported a rom myself (but I don't plan on releasing it >.<). And this kernel is designed to work with any stock-based (read: ported from titan) rom for our device (especially IDCrisis).
But fair warning: don't even think about flashing it on Lollipop.
Features:
Sources & Optimizations
- Based on CM13's shared falcon/peregrine/titan/thea sources
- Compiled with Uber Toolchain 4.9.4
- Compiled with -O3 optimization & some more flags (e.g. Pipe flag)
- Optimized ARM RWSEM & Square Root algorithms
- Kernel-side NEON mode
- Some miscellaneous armv7 tweaks
Click to expand...
Click to collapse
Hotplugging Drivers
- Ye Olde MPDecision
- AutoSMP
Click to expand...
Click to collapse
Extra CPU Governors
- Bioshock
- Dancedance
- Impulse
- Lionheart
- Smartmax
- Yankactive
- Yankdemand
- Zzmoove No more!!!
Click to expand...
Click to collapse
Extra I/O Schedulers
- Bfq
- Fiops
- Sio
- Vr
- Zen (Default)
Click to expand...
Click to collapse
Sound
- Faux's Sound Control
- Headset High Performance Mode
Click to expand...
Click to collapse
Screen/GPU
- Kcal Screen Control
- Dt2w/s2w Nicht mehr!
- State Notifier driver
- Adreno Idler
- GPU overclock & underclock (533MHz/100MHz) No more!!!
Click to expand...
Click to collapse
Extra Sh*t
- Simplified msm-thermal driver by @kwoktopus Was causing trouble
- Disabled gentle fair sleepers
- USB Fast Charge
- Extra TCP Congestion Controllers
- Compass & Accelerometer drivers now use State Notifier Was causing trouble too
- Fsync enabled by default
- Kexec-hardboot patch (for multirom compatibility)
- Power-efficient workqueues
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
For Falcon:
Standard Version
Permissive Version (Flash this only if you're having major SELinux-related issues)
Click to expand...
Click to collapse
For Peregrine:
Standard Version
Permissive Version (Flash this only if you're having major SELinux-related issues)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Looking for previous releases?
Pre-reset builds:
Falcon releases
Peregrine releases
Click to expand...
Click to collapse
Post-reset builds:
Falcon releases
Peregrine releases
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ran into issues? Go back to the stock kernel - just download one of these!
New Stock IDCrisis Kernel (Adapted from CM13) - Falcon
New Stock IDCrisis Kernel (Adapted from CM13) - Peregrine
Click to expand...
Click to collapse
Flashing Instructions (Follow this very carefully!!!):
- Place the zip at the root of your phone's internal storage, i.e. /sdcard (This is very important! If you flash the zip from a subfolder, you'll be left without wi-fi!!! This is a bug on the install script's side. I'll be looking into it.)
- Reboot into recovery
- Flash the zip
(Another way: Reboot into recovery without copying the zip, and flash it via adb sideload)
- Reboot again and have fun!
Coming from another kernel which isn't mine? Don't worry, no need to dirty flash the ROM/kernel anymore. The install script now does all the dirty work for you.
If you wanna tweak stuff, use Kernel Adiutor! (Synapse is NOT supported!)
Click to expand...
Click to collapse
Want some info on what this kernel offers you?
Then go here! (Credits to @AssToast for suggesting and to @gsstudios for creating the site!)
Click to expand...
Click to collapse
"Thank You" Section
- Motorola/Lenovo, for putting up them sources
- The CyanogenMod team
- @Flashhhh, his work kinda inspired me to do this
- @lost101, for creating IDCrisis
- @Aayushya, he provided the initial cherry-picks
- @faux123, for Sound Control & Intellithermal
- @savoca, for Kcal Screen Control
- @hurtsky, a huge load of cherry-picks came from his sources
- @Alberto97, for the Linux version bumps (.43 up to .109)
- @kwoktopus, for some more stuff
- Some more fellas whose names I can't remember
Click to expand...
Click to collapse
XDA:DevDB Information
KaminariKernel (IDCrisis), Kernel for the Moto G
Contributors
kingkaminari
Source Code: https://github.com/Kamin4ri/KaminariKernel/tree/idcrisis
Kernel Special Features: Read above!!!
Version Information
Status: Stable
Current Stable Version: R7
Stable Release Date: 2017-01-02
Current Beta Version: R6 Beta 2
Beta Release Date: 2016-11-01
Created 2016-03-26
Last Updated 2017-01-02
Reserved
Reserved
Reserved
Reserved!
Reserved
Reserved!
For those of you running IDCrisis, no matter which version.
Flash the stock kernel before flashing my kernel. I'll upload a stock titan/thea boot image for you guys to use.
Edit: Here's the image. It doesn't include any modules.
https://www.androidfilehost.com/?fid=24459283995306368
kingkaminari said:
For those of you running IDCrisis, no matter which version.
Flash the stock kernel before flashing my kernel. I'll upload a stock titan/thea boot image for you guys to use.
Edit: Here's the image. It doesn't include any modules.
https://www.androidfilehost.com/?fid=24459283995306368
Click to expand...
Click to collapse
do i need to flash it even if i have the previous version of your idcrisis 2.0?
if yes do i need stock modules also?
Using the latest (1.2) Identity Crisis, single SIM, normal (non-GNL) version. Using the IDCrisis version of the kernel recommended by lost. Falcon 2013 xt1032.
Want to try this kernel. Flashed the stock Titan/Thea image as instructed. Everything fine. Proceed to try to flash the Kernel. Error message. Something like "this kernel is for Lollipop 6.0.x (SDK 23). Your version is Marshmallow 6.0 (SDK 23)". Can't flash. Odd.
I reflashed the older IDCrisis kernel, and it's fine (hello from my Moto G) so at least it didn't go horribly wrong.
same here, couldn't flash it
+1
Enviado desde mi XT1072 mediante Tapatalk
Lolz. Looks like i did **** with the install script. Please open meta-inf/com/google/android/update-binary and remove the compatibility check part (do NOT remove anything else).
I'll upload a fixed flashable zip soon.
Here are the fixed flashable zips. Sorry for the derp, guys.
I lost my root permissions. Of SuperSU when I installed this kernel.
mahadev111 said:
I lost my root permissions. Of SuperSU when I installed this kernel.
Click to expand...
Click to collapse
Was your root systemless? Just reflash SuperSU.
kingkaminari said:
Here are the fixed flashable zips. Sorry for the derp, guys.
Click to expand...
Click to collapse
no worries mate. anyway, i'm able to flash the zip now but it gets stuck on M logo, what's wrong?
lucastracq said:
no worries mate. anyway, i'm able to flash the zip now but it gets stuck on M logo, what's wrong?
Click to expand...
Click to collapse
Funny, mine gets stuck at the WARNING BOOTLOADER UNLOCKED screen (I never got rid of that).
....But hey, it flashed.
Damn. I forgot to say, thats an experimental build using a new codebase. I'll have to switch to the old codebase...
Here's a build based on the old codebase. It has selinux force-set to permissive. Hopefully it boots.
Edit: There's a peregrine version as well.
And here are builds based on the new codebase, also with selinux force-set to permissive.
Selinux on marshmallow is a *****.
Choochter said:
Was your root systemless? Just reflash SuperSU.
Click to expand...
Click to collapse
Yes,root was systemless,I was on identity crysis 1.1d.when I reflashed SuperSU.stucked at boot logo.then I have to reflash rom.
Hi,
I recently bought the redmi note 3 and noticed the lack of kernel support, so I decided to share this with you guys:
https://github.com/daeiron/kenzo_caf_kernel
Its a fully functional buildable kernel for stock MIUI.
Changelog:
05-06-2016
- Merge LA.BR.1.3.2_rb3.28
- Fix camera for some?
28-05-2016
- Enable KSM
- Fix fingerprint on 6.5.26 (xiaomi didn't update their kernel source, so have to use fingerprint hal from 6.5.19)
- Update ramdisk
- Other small stuff
21-05-2016
- Merged to LA.BR.1.3.2_rb3.27
- Merged some patches from ido source drop
15-05-2016
- Tested with 6.5.12
- Full kcal support
- Defauls at boot to 400mhz min freq & bfq scheduler
- Fsync toggle
- State_notifier and state_helper (from neobuddy89)
- Backlight dimmer (from flar2)
- A lot of patches and fixes (see git)
04-05-2016
- Merged to LA.BR.1.3.2_rb3.26
- Upstream patched to 3.10.101
- O3 + makefile optimized
- BFQ, Fiops and SIO
- RGB color support (use custom app like kernel adiutor)
- Other patches (see git)
Limitations:
- No color/contrast/reading mode support, seems they didn't release it as part of the kernel
- In kerneladiutor gpu freq displays at 600mhz, this is just a false reading. Check 'cat /sys/class/kgsl/kgsl-3d0/devfreq/cur_freq' for the real frequency
- If you build the kernel and it won't boot try stock toolchain (https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9) with up to this commit e1a8a48e59638c0d24d2214c2a85046068158a08
To build;
- Clone the repo
- Get yourself a toolchain (I use stock google 4.9 up to commit: e1a8a48e59638c0d24d2214c2a85046068158a08)
- Edit user vars in build/build_kernel.sh
- From kernel root run: sh build/build_kernel.sh
- You end up with a flashable zip file in build/dist/
I am planning on keeping the source up to date with CAF and also sync in the latest patches from kernel.org.
Feel free to fork or use, please mention that you did though.
You can find my flashable zip builds here: https://drive.google.com/open?id=0B7XCSgymRoP0ZjJtSkxuS01kYUk
In oneplus one forum, sultanxda build a CM13.0 with CAF kernel and is pretty smooooooooth
Whoah,
Thank you, I was working on the same thing, this will save me a lot of time.
Yay more dev support, maybe in a month I'll figure out the stuff about building kernels and all that
Thanks for this
Thanks m8 great work
Flashed the kernel, feels snappy but has a big bug, system fails to detect simcard.Tested on both miui and aosp.
sanjib734 said:
Flashed the kernel, feels snappy but has a big bug, system fails to detect simcard.Tested on both miui and aosp.
Click to expand...
Click to collapse
Wich improvements have you felt with this kernel? Share your personal opinion please
EDIT: I´ve googled CAF meaning and didn´t found anything, anyone could help me?
EDIT 2: I´ve flashed and it works perfectly, no bugs, and in Antutu Benchmark got 78.000 points. Feels fast and smooth. Working on Xiaomi.eu dev 6.4.21
Migueliyo98 said:
Wich improvements have you felt with this kernel? Share your personal opinion please
EDIT: I´ve googled CAF meaning and didn´t found anything, anyone could help me?
EDIT 2: I´ve flashed and it works perfectly, no bugs, and in Antutu Benchmark got 78.000 points. Feels fast and smooth. Working on Xiaomi.eu dev 6.4.21
Click to expand...
Click to collapse
caf is Code Aurora Forum
color and contrast disable
am currently using global beta 6.4.21 can i flash this..?
Johnny199314 said:
am currently using global beta 6.4.21 can i flash this..?
Click to expand...
Click to collapse
Yes.
a2820356 said:
color and contrast disable
Click to expand...
Click to collapse
Confirmed. It seems that they didn't include this in their open source kernel.. I already created an issue for it at their git; https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/44
thomas1991_12 said:
Yes.
Click to expand...
Click to collapse
needed any modified boot image are just simply flash?
Stock aosp, sim doesn't get detected and Wi-Fi doesn't work
asdafdasdaf said:
Stock aosp, sim doesn't get detected and Wi-Fi doesn't work
Click to expand...
Click to collapse
he has clearly mentioned its for miui 6.4.21
Any possibility to maintain the kernel updated too on aosp? Someone can do it? *_*
Inviato dal mio kenzo utilizzando Tapatalk
Johnny199314 said:
he has clearly mentioned its for miui 6.4.21
Click to expand...
Click to collapse
Sorry that slipped out its 2am I should go to sleep thanks thoug
thomas1991_12 said:
Hi,
I recently bought the redmi note 3 and noticed the lack of kernel support, so I decided to share this with you guys:
https://github.com/daeiron/kenzo_caf_kernel
Its a fully functional buildable kernel for stock MIUI.
Limitations:
- No color/contrast support, seems they didn't release it as part of the kernel
To build;
- Clone the repo
- Get yourself a toolchain (I use stock google 4.9)
- Edit user vars in build/build_kernel.sh
- From kernel root run: sh build/build_kernel.sh
- You end up with a flashable zip file in build/dist/
I am planning on keeping the source up to date with CAF and also sync in the latest patches from kernel.org.
Feel free to fork or use, please mention that you did though.
You can find my flashable zip builds here (ramdisk based on 6.4.21 beta): https://drive.google.com/open?id=0B7XCSgymRoP0ZjJtSkxuS01kYUk
Click to expand...
Click to collapse
Hi! Do you think you could help me with this issue?
http://forum.xda-developers.com/redmi-note-3/help/help-developers-network-issue-t3367436
Probably a stupid question but I did read all the posts. Is this considered a modified 'cracked' boot.IMG?
Sent from my kenzo using Tapatalk
qkall said:
Probably a stupid question but I did read all the posts. Is this considered a modified 'cracked' boot.IMG?
Sent from my kenzo using Tapatalk
Click to expand...
Click to collapse
Are you in aosp?
Inviato dal mio kenzo utilizzando Tapatalk
This particular kernel arose out of frustration at the lack of choices that T-Mobile and Canadian S6 users have when flashing ported roms with the GraceUX UI and it would not have been possible without the original source posted by @Greck99 .
Feature-wise, this is the same exact kernel included in Noble Experience; however, it has been built against a W8 configuration and uses a stock ramdisk that has been modified solely for the purpose of booting hybrid ports.
Yes, blue light filter works. So does AOD (no touch for now)
Pair this kernel with the call audio fix for grace ux for the complete Noble Experience (or whatever GraceUX port you desire) on T/W8
Suggestions and feedback are welcome. Feature requests may be considered if I determine them to be useful enough to include
Thanks to:
@Greck99 & @Noxxxious for this awesome source
@AlexisXDA for making killer roms and something to be envious of
@The Sickness for his continued work on our devices and for all his contributions
@arter97 for hybrid ramdisk commits
And the Nexus7420 team in general.
I am not responsible for your device, you are.
This kernel should work for both T-Mobile and Canadian devices,
though has only been tested on a G920W8.
Download Flat
Download Edge
Fix for flashlight/video playback
After flashing the kernel, flash SU of choice: Magisk or SuperSU
Changelog:
V3.1 -
- Fix video playback issue
V3 - Upstream merge
- Merge lastest N920 sources
- Update to Linux 3.10.105
- AOD drivers added
- Zen-tune added. Increased performance at the cost of some battery
- Add lz4 for zswap
- Add Smartmax, Smartmax_EPS and Yankactive governors
- Update bfq scheduler
V2.1
- Removed SU injection as it is not necessary and was not the source of boot failures.
Can be run unrooted, and with system or systemless root modules (SuperSU and MagiskSU)
V2
- SuperSU is now injected into ramdisk.
- Knox, tima, selinux stuff disabled (This fixes bootloops on Noble Experience)
- Battery enhancements
- Google play services wakelock fix
- noatime on system parition
V1
- Initial release
XDA:DevDB Information
Noble Kernel, Kernel for the T-Mobile Samsung Galaxy S6
Contributors
lizaSB, Greck99, Noxxxious
Source Code: https://github.com/lizaSB/android_kernel_samsung_universal7420
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v2.1
Stable Release Date: 2017-02-06
Created 2017-02-06
Last Updated 2017-02-14
congrats!!
just tried it with fastrom v3.1 D: got a bootloop unfortunately.. will try it again when i switch roms again!!
stephhh said:
congrats!!
just tried it with fastrom v3.1 D: got a bootloop unfortunately.. will try it again when i switch roms again!!
Click to expand...
Click to collapse
Interesting.. Did you flash SU after?
Edit: It also may be necessary to wipe dalvik if you are flashing this coming from Arter. I have flashed this on two different W8s without issue, so I'm fairly certain it works
No! So sorry! Did not think about flashing su because my rom already has it installed. I'll try again next time when I flash
lizaSB said:
Interesting.. Did you flash SU after?
Edit: It also may be necessary to wipe dalvik if you are flashing this coming from Arter. I have flashed this on two different W8s without issue, so I'm fairly certain it works
Click to expand...
Click to collapse
Great kernel! Thanks to the developers for their hard work.
One question, even though you said no AOD, would you consider it as a feature request?
rtx7 said:
Great kernel! Thanks to the developers for their hard work.
One question, even though you said no AOD, would you consider it as a feature request?
Click to expand...
Click to collapse
The main issue I have with AOD is the massive battery drain. Even with it not enabled in the kernel, the AOD app still drains battery. I actually trimmed it from my rom.
The other issue is that the only kernel I'm aware with the AOD feature is TN kernel, which the developer has chosen not to share his source.
lizaSB said:
The main issue I have with AOD is the massive battery drain. Even with it not enabled in the kernel, the AOD app still drains battery. I actually trimmed it from my rom.
The other issue is that the only kernel I'm aware with the AOD feature is TN kernel, which the developer has chosen not to share his source.
Click to expand...
Click to collapse
Yeah, you're right. My only issue is I'd love to try out AOD even it drains my battery, since tn kernel brakes call function.. So if you have a test build, I'd gladly try it out
Its nice to have more choices anyway! Thanks a lot. :victory:
Can you make an edge version
sebo.ks15 said:
Can you make an edge version
Click to expand...
Click to collapse
Did you read the OP carefully
Edge didn't work on my 925w8
sebo.ks15 said:
Edge didn't work on my 925w8
Click to expand...
Click to collapse
This was confirmed working last night. This kernel won't boot on Noble Experience without flashing SU after and is mentioned in the OP that root should be flashed after the kernel
lizaSB said:
This was confirmed working last night. This kernel won't boot on Noble Experience without flashing SU after and is mentioned in the OP that root should be flashed after the kernel
Click to expand...
Click to collapse
OK I'll try that that thanks..
What groundwork did arter97 do? We should credit Samsung for giving us the proper bootclasspath instead.
And btw AOD is working
Thanks for making this kernel available on other models. When you need help or have feedback about the kernel PM me.
Quintz said:
What groundwork did arter97 do? We should credit Samsung for giving us the proper bootclasspath instead.
And btw AOD is working
Thanks for making this kernel available on other models. When you need help or have feedback about the kernel PM me.
Click to expand...
Click to collapse
I used his commits for building the ramdisk, would've probably taken a lot more trial and error without them -- they aren't documented clearly anywhere else to my knowledge (and to be fair, not all of what he ships in the n7 kernel is required in the ramdisk for booting). Most kernel authors don't include their ramdisks in the source they post. Sure I could've decompiled the ramdisk shipped with Noble Experience and reverse engineered it, but that's not what I did. I just wanted to give credit for the path I took regardless of my opinions regarding those whose steps I followed.
I just noticed a slurry of new commits in the upstream branch which I pulled into my fork earlier today and built a test build for myself. I will be releasing it once I've had a bit of chance to test things out and make sure all is working :good: So far things are running great for me.
Thank you very much for the work you've done and for sharing your source. The blue light filter is the real cream for me here as the overlay in cf.lumen causes lag for me. It is greatly appreciated by myself and all the others with our device. I could've just taken a stock kernel and started from scratch, but this is oh-so-much better than that!
Kernel Updated to Version 3
This update is largely a merge with up upstream source. Kernel is feeling very smooth, and in addition AOD drivers have been added and most of the kinks have been worked out.
Kernel is now using a custom built dt.img for AOD support which has not been tested for edge devices (though the reboots never affected them). I see no reason why it shouldn't work, please let me know if it causes any catastrophic failures!
Edit: V3 Image for G925T/W8 has been re-uploaded as of 1:05pm PST. Fixes for call audio regarding the custom dt.img -- removed it as it's not needed.
Download Flat
Download Edge
Changelog:
V3 - Upstream merge
- Merge lastest N920 sources
- Update to Linux 3.10.105
- AOD drivers added
- Zen-tune added. Increased performance at the cost of some battery
- Add lz4 for zswap
- Add Smartmax, Smartmax_EPS and Yankactive governors
- Update bfq scheduler
@lizaSB nice work. I see now that I have some compitition lol. JK.
Glad to see some fresh blood here on the kernel side.
Works beautifully on my G920T (XAR). Thanks OP! One thing though: I would suggest highlighting the note that installing SuperSU immediately afterwards is mandatory to make it more easily seen as the device wouldn't boot without it...
The Sickness said:
@lizaSB nice work. I see now that I have some compitition lol. JK.
Glad to see some fresh blood here on the kernel side.
Click to expand...
Click to collapse
Maybe when you start developing for Grace ports there will be some competition
stevenchen1995 said:
Works beautifully on my G920T (XAR). Thanks OP! One thing though: I would suggest highlighting the note that installing SuperSU immediately afterwards is mandatory to make it more easily seen as the device wouldn't boot without it...
Click to expand...
Click to collapse
This is no longer the case as of v2.1. I flash many of my test builds without rooting them, so I am positive it still works without
3.1 online! Bug fix for video playback.
Download Flat
Download Edge
Changelog:
V3.1 -
- Fix video playback issue
lizaSB said:
Maybe when you start developing for Grace ports there will be some competition
Click to expand...
Click to collapse
No need to worry about that. I dont do ports of any kind.
Kirisakura-Kernel for the Pixel 3 and Pixel 3 XL
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Pixel 3 aka Blueline and the Pixel 3 XL aka Crosshatch, together Bluecross.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
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 focus during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
If reading about upstream in the paragraph above got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 845 that´s built into Pixel 3 and Pixel 3 XL.
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 the other features 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 EAS implementation is heavily updated with changes from CAF, kernel/common and other improvements.
To have a read about our scheduler, which is called EAS, take a look here:
https://developer.arm.com/open-source/energy-aware-scheduling
Main Features:
- Based on latest kernel sources from Google, Kernel is made for Android 12 (Android S)!
- Linux-Stable-Upstream included to latest 4.9.317
- compiled with prebuilt Clang 13.0.1 from Google and built with -O3 optimizations
- ZRAM patched up to latest kernel/common state and use ZSTD LZ4 as default compression algorithm to improve memory managment (more info see this post regarding the earlier switch to ZSTD) and this post regarding the switch back to LZ4
- fixes the magisk freezes caused by f2fs-stable
- Safety Net patches are included -> Kernel passes Safety Net
- Wake Gestures from @flar2 included
- Flashing the kernel will keep root!
- Tested to work on custom ROMs
- Flashable via EXKM and FKM on a rooted system!
- AnyKernel3 powered by @osm0sis (big thanks!)
EAS related features:
- EAS implementation patched up to latest CAF state
- Schedutil is patched up with kernel/common and CAF patches to improve performance and efficiency!
- Memory Leaks inside EAS are fixed
- disable autogroups and use cgroups for more efficient task placement!
- Enable sched_min_task_util_for_boost_colocation feature from CAF
CPU related features:
- Power saving workingqueues enabled by default (toggleable in EXKM)
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This should work well in conjunction with EAS
- improved Schedutil governor
- Add hold functionality to schedtune CPU boost
- WQ_HIGHPRI for the IO and crypt workqueues (replaces googles approach with a better upstream one)
- cpufreq/times vastly improved
File System related features:
- 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.)
- Set the bio REQ_NOENCRYPT flag (When lower layers such as dm-crypt observe the REQ_NOENCRYPT flag, it helps the I/O stack avoid redundant encryption, improving performance and power utilization. )
Usability related features:
- High Brightness Mode for increasing backlight level related to brightness accessible via EXKM app
- High Brightness Mode for just boosting display to max level accessible via EXKM app
- Vibration Intensity adjustable via EXKM app
- Backlight dimmer functionality included (adjustable via EXKM App)
GPU related features:
- KCAL to control the display
- KLAPSE integrated
- KCAL/KLAPSE: changes safety measures -> allow completely disabling two RGB values (this was requested to, for example, only have red values on night dimming)
- Enabled NAP power saving state of Adreno 630
- improve GPU profiling for improved rendering performance (1,2 , 3 )
- Update GPU driver to latest CAF state
Network related features:
- Wireguard Support (Details)
Memory related features:
- Enable Userspace LMK/freak07/Kirisakura_bluecross/commit/aac453635549699c13a84ea1456d5b0e574ef855"]2[/URL])
- Patch up kernel LMK backend (PSI) with kernel common upstream
- ZRAM patched up to latest kernel/common state and ZSTD LZ4 as default algorithm. (information can be found in this post regarding the switch to ZSTD, which is now reverted) and this post regarding the switch back to LZ4
- possibility to use lzo-rle as default ZRAM compression algorithm (more information here and there )
- possibility to use zstd as default ZRAM compression algorithm!
- Speculative Page Faults (1. 2)
- Fix various memory leaks in different subsystems
- Reap memory of a task that receives sigkill
- various other changes from mainline
Sound related features:
- Adjust microphone gain via sound control in EXKM
- Adjust speaker gain via sound control in EXKM
Security related features:
- CFI and LTO both kept intact and are used to keep additional security Google implemented for us!
- Shadow Call Stack
- built with latest clang found on google repo
Misc Features:
IO-Schedulers:
- cfq
- maple
- deadline
- noop
- tripndroid
- fiops
TCP Congestion Algorithms:
- advanced algorithms enabled
- includes new bbr and sociopath tcps
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read this for further info
Other features:
- enable some additional Sony and XBox controllers
- add support for steam and nintendo switch controller
- patches to loop device, xfrm and usb gagdet
- disable logging to make the kernel more lightweight in various places
- add support so you can enable faster charging for non pixel wireless charging stands (use at your own risk, disabled by default, how to enable here)
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
How to flash the Kernel:
1. Download the kernel.zip to your device. Make sure your device is rooted properly, with the magisk version suiting your current firmware version.
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, reroot with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Flash the kernel.zip via either a kernel manager app capable of flashing kernels or TWRP if available. Make sure whatever method/app you decide to use, supports your current Android Firmware. Apps/Recoveries need to be possibly updated for firmware updates!
It´s your job to ensure compatability.
Flashing the kernel will preserve root.
3. Reboot and profit! Before reporting any issues make sure to read the Release-Post of Bluecross_Q_Release_1.0.0!
DOWNLOAD:
Download is located in these respective folders:
Android 9:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Android 10/11:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Android 12:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9 / Pie Kernels
1.0.0 Initial Release
1.5.0 https://forum.xda-developers.com/showpost.php?p=78151322&postcount=81
1.5.1 https://forum.xda-developers.com/showpost.php?p=78154423&postcount=112
1.7.0 https://forum.xda-developers.com/showpost.php?p=78196945&postcount=190
1.7.1 https://forum.xda-developers.com/showpost.php?p=78220526&postcount=227
1.7.2 https://forum.xda-developers.com/showpost.php?p=78221906&postcount=228
1.8.0 https://forum.xda-developers.com/showpost.php?p=78249473&postcount=267
1.8.1 https://forum.xda-developers.com/showpost.php?p=78280355&postcount=285
1.8.2 https://forum.xda-developers.com/showpost.php?p=78316038&postcount=345
1.8.3 https://forum.xda-developers.com/showpost.php?p=78330435&postcount=389
1.8.4 https://forum.xda-developers.com/showpost.php?p=78364541&postcount=451
1.8.5 https://forum.xda-developers.com/showpost.php?p=78377334&postcount=481
1.8.6 https://forum.xda-developers.com/showpost.php?p=78396058&postcount=538
1.8.7 https://forum.xda-developers.com/showpost.php?p=78420137&postcount=591
1.8.8 https://forum.xda-developers.com/showpost.php?p=78449511&postcount=621
1.8.9 https://forum.xda-developers.com/showpost.php?p=78496196&postcount=654
1.9.0 https://forum.xda-developers.com/showpost.php?p=78564181&postcount=701
1.9.1 https://forum.xda-developers.com/showpost.php?p=78637123&postcount=758
1.9.2 https://forum.xda-developers.com/showpost.php?p=78672005&postcount=775
Milestone 2.0.0 https://forum.xda-developers.com/showpost.php?p=78689028&postcount=782
2.0.2 https://forum.xda-developers.com/showpost.php?p=78761004&postcount=853
2.0.3 https://forum.xda-developers.com/showpost.php?p=78767857&postcount=867
2.0.4 https://forum.xda-developers.com/showpost.php?p=78805387&postcount=896
2.0.5 https://forum.xda-developers.com/showpost.php?p=78838240&postcount=928
2.0.6 https://forum.xda-developers.com/showpost.php?p=78840488&postcount=936
2.0.7 https://forum.xda-developers.com/showpost.php?p=78851682&postcount=953
2.0.8 https://forum.xda-developers.com/showpost.php?p=78898745&postcount=981
2.0.9 https://forum.xda-developers.com/showpost.php?p=78913421&postcount=991
2.0.10 https://forum.xda-developers.com/showpost.php?p=78950068&postcount=1007
2.0.11 https://forum.xda-developers.com/showpost.php?p=78975193&postcount=1025
2.0.12 https://forum.xda-developers.com/showpost.php?p=79009799&postcount=1041
2.0.13 https://forum.xda-developers.com/showpost.php?p=79043694&postcount=1067
2.0.14 https://forum.xda-developers.com/showpost.php?p=79050238&postcount=1103
2.1.0 https://forum.xda-developers.com/showpost.php?p=79136483&postcount=1182
2.1.1 https://forum.xda-developers.com/showpost.php?p=79159209&postcount=1221
2.1.2 https://forum.xda-developers.com/showpost.php?p=79190516&postcount=1261
2.1.3 https://forum.xda-developers.com/showpost.php?p=79214430&postcount=1279
2.2.0 https://forum.xda-developers.com/showpost.php?p=79291045&postcount=1372
2.2.1 https://forum.xda-developers.com/showpost.php?p=79332619&postcount=1452
2.2.2 https://forum.xda-developers.com/showpost.php?p=79425173&postcount=1531
2.3.0 https://forum.xda-developers.com/showpost.php?p=79463560&postcount=1569
2.4.0 + 2.4.1 https://forum.xda-developers.com/showpost.php?p=79505198&postcount=1623
3.0.0 https://forum.xda-developers.com/showpost.php?p=79533358&postcount=1641
3.1.0 https://forum.xda-developers.com/showpost.php?p=79570912&postcount=1685
3.1.1 https://forum.xda-developers.com/showpost.php?p=79575209&postcount=1698
3.1.2 https://forum.xda-developers.com/showpost.php?p=79578541&postcount=1722
3.1.3 https://forum.xda-developers.com/showpost.php?p=79612212&postcount=1743
3.2.0 https://forum.xda-developers.com/showpost.php?p=79658098&postcount=1774
3.3.0 https://forum.xda-developers.com/showpost.php?p=79696166&postcount=1807
3.3.1 https://forum.xda-developers.com/showpost.php?p=79736674&postcount=1829
3.3.4 https://forum.xda-developers.com/showpost.php?p=79791144&postcount=1857
3.4.0 https://forum.xda-developers.com/showpost.php?p=79919877&postcount=1929
3.4.5 https://forum.xda-developers.com/showpost.php?p=80023518&postcount=2064
Legacy Downloads for Pie Kernels: https://www.androidfilehost.com/?w=files&flid=285183
Android 10/ Q Kernels
1.0.0 https://forum.xda-developers.com/showpost.php?p=80269185&postcount=2132
1.1.3 https://forum.xda-developers.com/showpost.php?p=80324259&postcount=2199
1.2.0 https://forum.xda-developers.com/showpost.php?p=80533347&postcount=2291
1.2.2 https://forum.xda-developers.com/showpost.php?p=80809357&postcount=2325
1.3.0 https://forum.xda-developers.com/showpost.php?p=81115229&postcount=2451
1.4.0 https://forum.xda-developers.com/showpost.php?p=81418351&postcount=2519
1.4.1 https://forum.xda-developers.com/showpost.php?p=81421719&postcount=2529
1.5.0 https://forum.xda-developers.com/showpost.php?p=81684289&postcount=2582
1.5.1 https://forum.xda-developers.com/showpost.php?p=81947785&postcount=2607
1.5.2 https://forum.xda-developers.com/showpost.php?p=82213193&postcount=2635
1.5.3 https://forum.xda-developers.com/showpost.php?p=82484463&postcount=2642
1.5.4 https://forum.xda-developers.com/showpost.php?p=82742517&postcount=2688
1.5.5 https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84424203
Android 11
2.0.0_R https://forum.xda-developers.com/showpost.php?p=83554503&postcount=2753
2.1.0_R https://forum.xda-developers.com/showpost.php?p=83649655&postcount=2808
3.0.2_R https://forum.xda-developers.com/showpost.php?p=84007163&postcount=2906
3.0.4_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84230135
3.0.5_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84605183
3.0.6_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84812093
3.0.7_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-84975703
3.0.8_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-85166867
3.0.9_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-85298651
3.1.0_R https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-85432093
Android 12
4.0.0_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-85808391
4.1.0_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-86249089
5.0.0_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-86413291
5.1.0_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-86541411
5.1.1_S https://forum.xda-developers.com/t/...ixel-3-xl-aka-bluecross.3864563/post-87007931
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:
@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!
@topjohnwu for magisk!
@Sultanxda for all of his work!
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_bluecross/
FAQ
Important: What to do if you face issues on Android 10/Q
You might face issues on Android 10 like non working sensors, edge sense not working properly or similar things.
Here´s a thread that has more info about it: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
This also caused seemingly in a random fashion issues with magisk modules not unpacking properly when you flash them via magisk manager.
I recommend everybody who faces symptoms of random issues, which they cannot explain, to completely nuke their device and flash a factory image with -w intact, as to complete set up the device from scratch.
This will wipe your whole phone, so backup videos, photos, music, apps and other stuff you don´t want to lose!
@jcmm11 and me were hunting this magisk bug for a week and it turned out it´s connected to the above mentioned issue, although it gets more prominent by the latest CAF - EAS changes, which are merged in my kernel. Probably due to the way tasks get handled a bit differently.
Please everybody keep this in mind, before reporting back.
Question: Upon flashing the kernel zip I got a message that there is an error with ramdisk. What to do?
Answer:
Procedure to fix the ramdisk issue:
The ramdisk error is now fixed. Please take a look at this post from @osm0sis for more information:
Big thanks to @osm0sis and @topjohnwu for everything at this point here! And everyone else that helped in the process!
Important:
What do you have to do to get finally rid of the ramdisk error?
1. Flash back a stock clean boot.img either for stock rom or the custom rom you´re on. (not a backup from some time ago, a clean stock boot.img)
Link to stock boot.img from Google´s december factory image for convenience
2. REDOWNLOAD(!) either magisk 18.0 or the latest canary directly from magisk manager and delete all old magisk zips on your device. (this is really important!)
3. Optional: Reinstall twrp.zip if you want to.
4. Flash the redownloaded magisk zip in TWRP
5. Flash my kernel either via TWRP, EXKM App or FKM App
6. Profit
Question: Is root preserved when flashing this kernel?
Answer: My kernel.zip keeps a device rooted by magisk rooted.
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 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!
To easily get a logcat in case of a crash take a look at this post:
https://forum.xda-developers.com/showpost.php?p=79462002&postcount=1566
Big thanks to @jcmm11 for it
Here´s a tasker task to automatically copy /sys/fs/pstore on each boot to internal storage. Be advised these files get also created on correct reboots.
https://forum.xda-developers.com/showpost.php?p=79549126&postcount=1670
thanks @jsauder2 for this little trick
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!
https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt
Gonna give this a go now. Thanks!
Sweet, thank you sir!
Sent from my Pixel 3 XL using Tapatalk
fsync toggle?
How much do the 3 and xl differ on kernel level?
Would this flash and work on the 3?
frewys said:
How much do the 3 and xl differ on kernel level?
Would this flash and work on the 3?
Click to expand...
Click to collapse
Working on mine
RE: " - Flashing the kernel will keep root ! "
Who had done the steps and ( then the pixel ) lived to see to see another happy day ?
( assuming magisk ( root ) is installed and and has been happy for days... )
turn security pin off, fastboot twrp_323 image, twrp the kernel zip, twrp the twrp_323 zip, reboot back into twrp, wipe the cache to see that the finger presses workie, boot to system, re-verify root is okay, buy the man a beer...
May I ask if you could add zram zstd from Pixel 2 XL ? It is a BIG improvement for ram management.
Gesendet von meinem Pixel 3 XL mit Tapatalk
frewys said:
How much do the 3 and xl differ on kernel level?
Would this flash and work on the 3?
Click to expand...
Click to collapse
Kernel is unified, the main difference is the display driver (ftm5 vs sec_touch)
virtyx said:
fsync toggle?
Click to expand...
Click to collapse
I can include it, but I recommend to leave it on. I know several people that suffered from corruption when something unexpected happened and their device shutting down.
I´ll include the toggle but leave fsync on by default, just like the wakelock blocker.
frewys said:
How much do the 3 and xl differ on kernel level?
Would this flash and work on the 3?
Click to expand...
Click to collapse
Chronzy said:
Working on mine
Click to expand...
Click to collapse
thanks for chiming in @frewys
also thanks for confirming it works on the regular pixel 3 too @Chronzy
old_fart said:
RE: " - Flashing the kernel will keep root ! "
Who had done the steps and ( then the pixel ) lived to see to see another happy day ?
( assuming magisk ( root ) is installed and and has been happy for days... )
turn security pin off, fastboot twrp_323 image, twrp the kernel zip, twrp the twrp_323 zip, reboot back into twrp, wipe the cache to see that the finger presses workie, boot to system, re-verify root is okay, buy the man a beer...
Click to expand...
Click to collapse
yeah it works I tested it.
In theory you can flash the kernel "on the go" without a computer and keep root via franco kernel manager. which is pretty handy.
although I only recommend to tinker with pixel phones when a computer is nearby and available. :good:
Komodoketavaran said:
May I ask if you could add zram zstd from Pixel 2 XL ? It is a BIG improvement for ram management.
Gesendet von meinem Pixel 3 XL mit Tapatalk
Click to expand...
Click to collapse
yes that´s one of the things I definitely wanted to try in the nearby future. it was my kernel that firstly introduced it on the pixel 2 xl but memory managment on my unit is not as bad as I saw in some reviews/videos.
Additionally I think the underlying cause, when Pixel 3 cannot hold more than 3 apps in background is a bit different than pixel 2 xl "just having 4gb of ram".
But I´m sure there is room for improvement. Just wanted to use the phone as it is to get a baseline of how it works before I start modifying all sort of stuff.
Freak07 said:
I can include it, but I recommend to leave it on. I know several people that suffered from corruption when something unexpected happened and their device shutting down.
I´ll include the toggle but leave fsync on by default, just like the wakelock blocker.
Click to expand...
Click to collapse
Thank you that'd be great
Freak07 said:
yeah it works I tested it.
In theory you can flash the kernel "on the go" without a computer and keep root via franco kernel manager. which is pretty handy.
although I only recommend to tinker with pixel phones when a computer is nearby and available. :good:
Click to expand...
Click to collapse
Can confirm it's working. I flashed with FK Kernel Manager. Root still intact, Magisk and all still installed.
Worked for me to flash try exkm
Root remainder. Was hoping the kernel would fix an issue with magisk not passing safety net whenever hit the check safety net. It asks me to download. I hit yes and then it fails immediately was like this on stock as well
That would be great. It is very bad on my unit.
On my P2XL there are nearly no redraws with your kernel
Freak07 said:
yes that´s one of the things I definitely wanted to try in the nearby future. it was my kernel that firstly introduced it on the pixel 2 xl but memory managment on my unit is not as bad as I saw in some reviews/videos.
Additionally I think the underlying cause, when Pixel 3 cannot hold more than 3 apps in background is a bit different than pixel 2 xl "just having 4gb of ram".
But I´m sure there is room for improvement. Just wanted to use the phone as it is to get a baseline of how it works before I start modifying all sort of stuff.
Click to expand...
Click to collapse
Gesendet von meinem Pixel 3 XL mit Tapatalk
old_fart said:
RE: " - Flashing the kernel will keep root ! "
Who had done the steps and ( then the pixel ) lived to see to see another happy day ?
( assuming magisk ( root ) is installed and and has been happy for days... )
turn security pin off, fastboot twrp_323 image, twrp the kernel zip, twrp the twrp_323 zip, reboot back into twrp, wipe the cache to see that the finger presses workie, boot to system, re-verify root is okay, buy the man a beer...
Click to expand...
Click to collapse
When I followed those steps my phone would only boot straight to twrp with no touch. Had to flash factory boot.img to get it back.
Hi, all
Recently I was attracted by the idea behind the Energy Awareness Scheduler (EAS) model and shared some thoughts on this topic here. But nowadays Android system must be deeply modified to work with the kernel. So EAS powered ROM was born.
I selected LineageOS as a base because of its stability and long term support. All but changes in Changelog are from LineageOS. If there are bugs about tasks/CPU scheduler in some circumstances, please let me know. Thank you.
More info about EAS.
Features
EAS model from Pixel 2
HMP and MSM_PERFORMANCE disabled in the Kernel
"schedutil" as default CPU governor
No QTI boost services in userspace
No power HAL built-in
Issues
Probably none, but "adb root" is enabled by default for testing reason.
Download
SourceForge.net
Changelog
20210704
Optimize ext4 fsync for SSD to improve random write speed
Enable Simple LMK
Use 100 Hz timer in the Kernel
Reduce latency while processing GPU's ioctls
Minor fixes on CFS scheduler
20210527
Nuke power-libperfmgr
Restore stock CPU frequencies table
Enable CPU_BOOST and set boost on touch
Support CPU low latency on touch
Rebased on official LineageOS 18.1
20210520
Switched to Pixel AIDL power-libperfmgr
Optimize powerhint for power HAL (~1.1 GHz for each CPU cluster)
Fix UI jitter issue while moving floating window
Enable ZRAM with 50% of total RAM
Enable background Blur effect on Launcher
Various fixes in CPU fair scheduler
Disable debug configs in the Kernel
Fixes from LineageOS upstream
20210422
Rebased on LineageOS 18.1
Restore libperfmgr and remove CPU frequencies boost on INTERACTION
Installation
backup your personal data
flash the ROM via TWRP, remember to factory reset if from other ROMs
Source
Device tree
Kernel
Credits
LineageOS team and sagit device maintainer @NeoArian
Sultan for kernel optimizations
I'll try
Couldn't get it to boot with gapps
Managed to do it with newly downloaded binary and new copy, i guess old one was corrupted somehow
Magisk requires manual boot.img patch, not a big problem but would be nice if we can use the zip or the app, also for some reason google play doesnt display many apps because "its incompatible", I edited build.prop to Pixel 2 solve it
And this rom really feels really smooth, good job!
Google contact can't sync. I replaced aosp contact to Google contact.
Vinesandroid said:
Google contact can't sync. I replaced aosp contact to Google contact.
Click to expand...
Click to collapse
I don't use Google apps for now. New build is now rebased on LineageOS 18.1. Let's see if it works well with Gapps.
Using your rom atm, so far so good, hoping havoc have EAS too, Anyways thank you for your work and ofc @NeoArian
Good job on the rom so far! Just wanted to check how do I acquire root on this via Magisk? Thanks!
skeeeee said:
Good job on the rom so far! Just wanted to check how do I acquire root on this via Magisk? Thanks!
Click to expand...
Click to collapse
Please follow the official instructions to install Magisk for root access.
The basic steps for root should be:
Extract the original boot.img from the ROM
Install Magisk app and use it to patch this boot.img
Flash the patched boot.img in TWRP
Reboot and enjoy
Thanks for your work!
And can you explain in simple terms, what will the firmware with the EAS give me vs official LineageOS 18.1?
Alexander078 said:
Thanks for your work!
And can you explain in simple terms, what will the firmware with the EAS give me vs official LineageOS 18.1?
Click to expand...
Click to collapse
I don't understand your words exactly. But for the firmware, there are no differences between EAS ROM and the official ROM. EAS is just a bunch of schedulers and methods to balance the performance and battery usage.
cn.fyodor said:
Please follow the official instructions to install Magisk for root access.
The basic steps for root should be:
Extract the original boot.img from the ROM
Install Magisk app and use it to patch this boot.img
Flash the patched boot.img in TWRP
Reboot and enjoy
Click to expand...
Click to collapse
The thing is when I installed this ROM the recovery became Lineage Recovery so idk what to do right now.
Update planned?