Melt Kernel v2.6 for marble/marblein

Changelog:

• Merge 5.10.212
• Merge KERNEL.PLATFORM.1.0.r3-04200-kernel.0 (base)
• Merge LA.VENDOR.1.0.r2-09400-WAIPIO.QSSI14.0 (wifi driver, audio driver, eva driver, dataipa driver)
• Merge VIDEO.LA.2.0.r2-01900-WAIPIO.0 (video driver)
• Synchronize with the upstream android12-5.10 and android12-5.10-lts branch
• Update WiFi driver (2.0.9.21U)
• Update NTFS3 driver
• Update KernelSU driver
• Disable CASS (it's said to cause some strange problems)
• Backport the latest binder driver
• Backport kernfs driver from android13-5.10
• Backport the latest Damon driver from AmazonLinux
• Add EDAC modules to custom module blacklist
• Add cs35l43_dlkm to custom module blacklist
• Add Coresight device placeholder driver
• Recompile the binder prio driver and optimize for AOSP's default launcher and Poco Launcher
• Fix a memory leak bug in msm_kgsl
• Use 12ms half-life for PELT (faster system response while taking into account power saving)
• Introduce & enable Uclamp Assist (improve performance or save power by controlling CPU utilization of tasks in different process groups)
• aw882xx: Force disable cali mode for marble
• goodix_9916r: Allow enabling 360HZ sampling rate in the "Game Turbo" app of MIUI/HyperOS (set 触控滑动跟手性 to higher than 2nd gear)
• goodix_9916r: Fix the problem of high touch sampling rate failure after reopening the screen
• goodix_9916r: Set the correct regulator output voltage for marble
• goodix_9916r: Do not compile fod function for marble
• AK3: Added an option during installation to always use 360HZ touchscreen sampling rate
• AK3: Added an option during installation to fix abnormal battery usage data in some AOSP roms
• AK3: Added an option during installation to make the device display a more realistic battery percentage
• Disguise the kernel version string to pass the Play Integrity authentication (prepare for possible futures)
• Some other fixes and optimizations

Note:

• (for Chinese users) 在尝试安装Melt内核之前，请认真阅读以下内容（如果阅读英文有困难，可以借助翻译软件）。如果你没能阅读并理解以下内容，请不要安装Melt内核！如果你执意按照自己的想法行动，由此造成的设备无法启动、数据丢失、变砖，我不负任何责任！
• I cannot guarantee it's compatible with EvolutionX A14 rom, please test it yourself.
• LineageOS based on OSS kernel is not supported.
• Support both MIUI14 firmware and HyperOS firmware.
• Unless you are absolutely sure, do not try to bypass restrictions to install Melt on other models. Please be responsible for your actions!
• If you just installed or updated a rom, then Melt Kernel may fail to install until the snapshot merge is complete. Usually, after installing or updating rom, the Android system will silently merge snapshots in the background. You can manually merge snapshots in TWRP's Advanced menu. Some technical details.
• If you are installing the Melt Kernel on the current ROM for the first time, we recommend that you follow the prompts during installation to generate a restore package. If you want to restore the stock kernel or replace with another kernel, you should flash this restore package, otherwise you can only dirty flash rom. Please note: If you try to change kernel before reverting to stock kernel, your device may not boot!
• If you encounter the problem that the device cannot boot after installing Melt Kernel, please refer to the solution.

About KernelSU:

• Select through the volume keys during the installation process to install the kernel that supports KernelSU.
• Install the KernelSU app v0.8.1 for use with KernelSU.
• We don't recommend using Magisk and KernelSU at the same time. If any problems occur, it's your own responsibility!

v2.6-unstable changelog (differences from v2.6):

• Drop "per memcg lru lock" (it has too many conflicts with mglru)
• 🚫 Add MultiGenerational LRU support (v15 patch)
• 🚫 Add BBR2 TCP congestion control algorithm support

⚠️ Warning:

Features marked with 🚫 are definitely not going to be in the stable release since they seriously destabilize KMI.

It's not worth sacrificing stability for these new features.

So, can this unstable kernel boot?

I don't know. Try yourself.

Can I use it for a long time?

I don't know. Try yourself.

I found a bug in the unstable build, what should I do?

Switch to normal builds, and do NOT report bugs to developer that only happen on unstable builds!

Will the unstable version be kept updated?

I will update from time to time.