Idk why but some people think kernel only works for a12.
It works on A12, A12.1 and A13.
So yes, you can flash it on A13.
It works on A12, A12.1 and A13.
So yes, you can flash it on A13.
Om Patel, previously @takumi021 and rn @Deadguyfr
Raided and spammed my chat.
This is a callout to him, as well as request to everyone who is fedadmin or admin in any chat to ban his ass.
This retard was one of the first maintainers for my ROM. I taught him, helped him wherever I could, when he started getting banned from chats i vouched for his ass.
Today he does this shit and says it's a joke. I'm done with this shit. Whatever follows is on u Om.
Raided and spammed my chat.
This is a callout to him, as well as request to everyone who is fedadmin or admin in any chat to ban his ass.
This retard was one of the first maintainers for my ROM. I taught him, helped him wherever I could, when he started getting banned from chats i vouched for his ass.
Today he does this shit and says it's a joke. I'm done with this shit. Whatever follows is on u Om.
Alot of guys are getting their accounts banned with the new telegram antispam api. As such im making a back up discord server.
Anyone knows how to mod discord servers?
Anyone knows how to mod discord servers?
Requiem-Kernel
Requiem-Nightly-27012023-LEMONADE.zip
tested and won't work on F11 fw (OOS13)
i'm not in mood to support OOS13, i will do this when majority of the community has completely shifted to 13
Forwarded from Komaru Gang (Cybersecbyte ALT)
Finally we have made our own bot from scratch for making demotivators🥳 🥳 🤩
Go try and use it at 👉🏻 @demotivatorgif_bot👨💻
😎 Suggestions for improvements will be appreciated at @komarugangchat 😇
Go try and use it at 👉🏻 @demotivatorgif_bot
Please open Telegram to view this post
VIEW IN TELEGRAM
On 5.10, building standalone kernels is a big mess in and of itself.
To build the qcom kernels on 5.10 and above there's kernel_platform, a sort of split build system where the kernel is built first in a kind of prebuilt kernel format, and then you build the ROM separately.
Well, what about the standalone kernels?
There's 3 ways to mostly do this as far as I know.
First method is a slight hacky way devised by arter97, the lazy initcall
https://github.com/arter97/hdk-kernel/commit/1ad367f0f821a70e5a766e267515aa6be022a44e
The second way is just bypassing those modules by not inlining them in the kernel, as such they are initialised as is from vendor_dlkm.
However here comes the biggest caveat: kmi
https://source.android.com/docs/core/architecture/kernel/stable-kmi
For the kernel to be able to load precompiled kernel modules (ko), the kernel must be compiled with Google clang 12.0.5. This means we cannot compile the kernel with the latest clang.(this is mostly just applicable for stock kernel and if ur gonna target stock rom)
The third way is by unpacking the vendor_dlkm, replacing the module inside, repacking it then shipping the img alongside the kernel Image in ak3.
To build the qcom kernels on 5.10 and above there's kernel_platform, a sort of split build system where the kernel is built first in a kind of prebuilt kernel format, and then you build the ROM separately.
Well, what about the standalone kernels?
There's 3 ways to mostly do this as far as I know.
First method is a slight hacky way devised by arter97, the lazy initcall
https://github.com/arter97/hdk-kernel/commit/1ad367f0f821a70e5a766e267515aa6be022a44e
The second way is just bypassing those modules by not inlining them in the kernel, as such they are initialised as is from vendor_dlkm.
However here comes the biggest caveat: kmi
https://source.android.com/docs/core/architecture/kernel/stable-kmi
For the kernel to be able to load precompiled kernel modules (ko), the kernel must be compiled with Google clang 12.0.5. This means we cannot compile the kernel with the latest clang.(this is mostly just applicable for stock kernel and if ur gonna target stock rom)
The third way is by unpacking the vendor_dlkm, replacing the module inside, repacking it then shipping the img alongside the kernel Image in ak3.