Sorry, i have a question, when flash Clean State, my Solid radar auto enable, with stock it disable (beccause my country not support). Can you process to enable with your's kernel.
CleanSlate is supposed to be used without root, so the funtionality of the following magisk module is replicated with a kernel tweak on CleanSlate:
working just fine here.
Thanks for the prompt response. Yes, I have done several reboot to see if I can get the camera to start. Every time I press camera, it brings camera up, but nothing is there like it is frozen, and no preview.working just fine here.
did you try to do one additional reboot after flashing the kernel? sometimes after switching from stock kernel this seems to happen to some people on dev preview.
some stuff needs to be adjusted by magisk after flashing the kernel. I think it might be a timing issue that seems to happen on the first boot, and as a result the camera hal can´t be started.
It might be also connected to the amount of magisk modules, if you´re using xposed etc.
there´s no need to flash whole sp3 again. just restore stock dtbo.img and boot.img via fastboot and you´re back on stock.
Hi, I failed to install the Kernel in Pixel 4.
I use Android 10 factory image and the TWRP-3.5.2-10.pixel4.
I push the Kirisakura kernel.zip to the phone via adb and install it via the TWRP install.
However, it failed with the error message: Unsupported Android security Patch Level .
By the way, I also want to know how to install the kernel for Android 11 since the TWRP does not support Android 11 now in Pixel 4.
I try to use the kernel kitchen to replace the kernel file in boot.img. But it failed with the touch screen does not work properly.
Thanks for the prompt response. Yes, I have done several reboot to see if I can get the camera to start. Every time I press camera, it brings camera up, but nothing is there like it is frozen, and no preview.
I believe I tried both dtbo.img and boot.img in past when I had similar issues with earlier alpha preview release in which front camera was acting up.
I don't have any other module other then ACC to control the charging.
Thanks again. Will try again next week.
Thanks for your reply. The problem may be that my kernel version is Linux-4.14.180. But the Kirisakura-kernel version is 4.14.197. So the security patch level does not match.Give the OP a read.
You´ll find the kernel for Android 10 and the firmware you´re on there. If you run an A10 rom with a very recent security patch (I don´t know if that exists) then your best bet might be the most recent A10 release from the OP. If it doesn´t work for some reason you´re out of luck.
If twrp is not working on your specific android version, the best way to flash is a kernel manager like EXKM or FKM. There´s another more recent one called smartpack (or similar), which I haven´t tried and I don´t know if it support flashing kernels properly here.
Simply repacking the boot.img isn´t enough to get the "whole" package of this kernel. Flashing the kernel creates a magisk-helper module which is an integral part as well. So you need to be rooted with magisk as per instructions and if you go the manual route you need to re-create the magisk-module yourself.
I'd just recommend to give the OP a read and follow the instructions there.
I don´t know what is wrong on your end then. I´m using the kernel on a daily basis and my camera is working fine.
If restoring stock boot.img and dtbo.img from factory image doesn´t fix issues you face after flashing the kernel, then something else might be wrong.
Thanks for your reply. The problem may be that my kernel version is Linux-4.14.180. But the Kirisakura-kernel version is 4.14.197. So the security patch level does not match.
I have tried FKM and it works. The SmartPack does not work in Android 11.
Currently, the most serious problem for me is that my custom kernel compiled from AOSP and google/kernel does not work properly and the touch screen does not work. The reason may be that my own dtb file and the kernel modules does not match the AOSP prebuild ones. Then my own kernel cannot load the kernel modules in AOSP rom.
By the way, is the dbt file generated by "cat sm8150.dtb sm8150-v2.dtb > dtb"
Thank you. Now I can flash use the Kirisakura-FLORAL_6.0.0 version. It works well now.This has nothing to do with the security patch level. The security patch level is the one you can check in settings/system.
The anykernel.zip checks the android version and the security patch level. And if it detects incompatibility it aborts.
If you're not on the latest firmware from Google with may 2021 security patch, you need to go back in the changelog in the first post and find the kernel that fits best.
Flashing kernels that are not build for a specific android version or security patch can cause issues.
All of your other issues have nothing to do with my kernel. So I don't think this is a good place to discuss this...
You need to either force load the kernel modules (might work as long as your kernel is close to stock) or built the drivers into the zImage if you want to build a custom kernel.
One of the touchscreen drivers for pixel 4/xl must be imported from a different repo on googles git. Should be fts_touch.
It's not related to dtb, but the module magic blocking, as your kernel is not the one they have been originally been built with.
Dtb is generated similar to here:
I am sorry. I will find another place to ask some questions about it.
modifying the date specified in anykernel.sh doesn´t change that fact that you should only flash kernels on a matching firmware. flash the kernel that was released in december 2020, on a rom/firmware that has the same security patch.Thank you. Now I can flash use the Kirisakura-FLORAL_6.0.0 version. It works well now.
The patch security level seems to be a date, e.g. 2020-11-5. It works when the two kernel's dates are similar.
Thanks for your guides. Now I have learned to flash via FKM or just modify the boot.img by Android-Kernel-Kitchen.
I think I can write a tutorial for the newbie to flash the zip and avoid these problems.
I am sorry. I will find another place to ask some questions about it.
Currently, I still work on solving the problem of making touch screen works. The repository fts_touch is inside the new kernel repo manifest and generates a new kernel module ftm5.ko. The problem seems to be the module magic blocking. First, I will try to force reload all the modules.
It is a very good idea to build the kernel modules together with the kernel. But I don't know how to modify the makefile. I will try to disable the module magic checking if it still does not work after reload the kernel modules. Then I try to learn from your kernel repository to find out how to build the kernel modules into the kernel.
Thanks for your help. It finally works after moving all the modules into the kernel.modifying the date specified in anykernel.sh doesn´t change that fact that you should only flash kernels on a matching firmware. flash the kernel that was released in december 2020, on a rom/firmware that has the same security patch.
There´s no need for a guide how to be able to flash kernels on non matching firmwares.
This is not something that anybody needs or should do on my kernel zips. Search the correct kernel for the matching firmware and follow the instruction in the first post and there won´t be any issue.
Good luck in your endeavor.
change =m to =y in the defconfig to build a driver into the zImage and not as a module.
Its coincidence. There's a ton of people having problems with that from what I read.
Oh and a new build is being testedthere were no changes in the kernel source code pushed for stable A12 on googles git.
there were also no changes in the kernel source code pushed for A11 October Update that weren´t already included in the kernel.
7.9.3 is still fine to use on A11 October build and A12 beta 5.
thanks, I´ll check for the next build. Also the commits you linked me earlier.