Pzqqt
released this
02 Feb 07:00
·
152 commits
to melt-rebase
since this release
Changelog:
- Merge v5.10.234
- Merge
KERNEL.PLATFORM.1.0.r3-05600-kernel.0
- Merge
LA.VENDOR.1.0.r2-14000-WAIPIO.QSSI15.0
(cvp driver, eva driver) - Update KernelSU
- KernelSU: Manual hooking, without using kprobes (helps to further hide KernelSU)
- Fix the problem that IR does not work on ROMs based on OSS kernel
- Fix the problem that the minimum brightness display is abnormal on ROMs based on OSS kernel
- Extract and update the zram kernel module from
OS2.0.3.0.VMNCNXM
- AK3: Uninstall KernelSU LKM which is incompatible with GKI
- AK3: Add an option to allow users to choose whether to use the Xiaomi's stock zram kernel modules or the OSS zram kernel modules (this option is only visible to MIUI/HyperOS rom users)
- AK3: Add an option during installation to disguised the GPU model as Adreno730 (same as Snapdragon 8+ Gen1)
- Synchronize with the upstream
android12-5.10
andandroid12-5.10-lts
branch - Some other fixes and optimizations
Notes:
- (For Chinese users) 在尝试安装Melt内核之前,请认真阅读以下内容(如果阅读英文有困难,可以借助翻译软件)。如果你没能阅读并理解以下内容,请不要安装Melt内核!如果你执意按照自己的想法行动,由此造成的设备无法启动、数据丢失、变砖,我不负任何责任!
- (IMPORTANT!) This build supports ROMs based on OSS kernel. Please actively report bugs. Another good news is that for ROMs that were originally incompatible with GKI, they can be compatible with GKI after flashing Melt.
- (IMPORTANT!) Does NOT support latest LineageOS roms! Do not attempt to modify the installation package to circumvent this limitation!
- (IMPORTANT!) Remember, NEVER downgrade to an older version of Melt Kernel, always use the latest version of Melt kernel.
- 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!
- For compatibility reasons, Melt Kernel will no longer retain
perfmgr.ko
in the vendor_boot partition from this version onwards. This affects some modified MIUI/HyperOS roms that support FEAS. For those who still want to use FEAS on these roms, please install the latest FEAS4Marble module. - 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.
- (Updated) For detailed instructions on each option encountered during the installation process: English | 简体中文
About KernelSU:
- Select through the volume keys during the installation process to install the kernel that supports KernelSU.
- If the installer detects that you have installed KernelSU through LKM, there will be no option to ask you whether to select KernelSU.
- Install the KernelSU app
v1.0.3
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!
- Want to try other unofficial versions of KernelSU (such as MKSU, KernelSU Next)? They all support LKM installation, please install it yourself. If you are asked to select the KMI version during installation, select
android12-5.10
.
v3.6-unstable changelog (differences from v3.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
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.