Development [KERNEL] [blu_spark r96 OP9/Pro] [A11 OOS/A12 Custom]

[toolhas4degrees]

I'm not lol

At least at the moment. But eventually if we want to keep updated, we will have to I guess.

But not before I have source to take a look

In the last 2 or three updates even though I set all io schedulers to bfq, it resets 2 to mq deadline after reboot and have to manually toggle them back to bfq each time.

 

[eng.stk]

In the last 2 or three updates even though I set all io schedulers to bfq, it resets 2 to mq deadline after reboot and have to manually toggle them back to bfq each time.

ofc, deadline is default.

You need to set that later on boot.

 

[toolhas4degrees]

ofc, deadline is default.

You need to set that later on boot.

It was set on boot to bfq.for all in Franco. And every reboot 2 of them change back to deadline regardless

 

[eng.stk]

It was set on boot to bfq.for all in Franco. And every reboot 2 of them change back to deadline regardless

Doesn't mean anything.

Later on boot is later on boot. 45 60 secs

 

[toolhas4degrees]

Ok yeah it's boot delay. But it's more like 5 minutes now. Fkm service is 0 seconds.
Is this controlled in the kernel or a lag from processes in the kernel startup? Or is it fkm or zygisk magisk issues?
Like I said never had this long of a delay until 3 or 4 builds ago I think 52 was the last one that didn't.

 

[eng.stk]

Ok yeah it's boot delay. But it's more like 5 minutes now. Fkm service is 0 seconds.
Is this controlled in the kernel or a lag from processes in the kernel startup? Or is it fkm or zygisk magisk issues?
Like I said never had this long of a delay until 3 or 4 builds ago I think 52 was the last one that didn't.

There's no kernel changes related to that, always has been the same.
There's a 30 sec delay tagged to boot events, that could be influenced by several things running on boot and taking time.
You need to add a bigger delay to fkm service, nothing new here.

 

[Flying Fox]

First of all, many thanks for the development of this kernel. It was already my favourite on my Oneplus 6. Flashed for the first time after a long time on my Onplus 9 pro (via EX kernel manager). Then no more settings changed. But then, out of old habit, I deleted the flar kernel and installed the FKM. No changes made here either. By the way, I am on the latest A11 firmware EU. A few Magisk modules like Viper4Android, otherwise nothing spectacular.

Now to the issue. For the first time (overnight) there was probably a random reboot, but into recovery mode (original, I don't have TWRP). Reboot was not possible. Only after flashing the boot and vendor partition via fastboot.
(I am glad that I made a backup. Normally I would have flashed dirty if there was a problem. So for everyone, a backup of the two partitions pays off in any case).

My question is whether this can be related to the kernel. I think so, see screenshot. Oh well, concerns your last update and the first I flashed.

So, now I have to go, I think my info is complete. If I'm the only one, then there's probably something wrong with my phone. But I have no mods, no custom rom, nada.
Kind regards

 

[toolhas4degrees]

First of all, many thanks for the development of this kernel. It was already my favourite on my Oneplus 6. Flashed for the first time after a long time on my Onplus 9 pro (via EX kernel manager). Then no more settings changed. But then, out of old habit, I deleted the flar kernel and installed the FKM. No changes made here either. By the way, I am on the latest A11 firmware EU. A few Magisk modules like Viper4Android, otherwise nothing spectacular.

Now to the issue. For the first time (overnight) there was probably a random reboot, but into recovery mode (original, I don't have TWRP). Reboot was not possible. Only after flashing the boot and vendor partition via fastboot.
(I am glad that I made a backup. Normally I would have flashed dirty if there was a problem. So for everyone, a backup of the two partitions pays off in any case).

My question is whether this can be related to the kernel. I think so, see screenshot. Oh well, concerns your last update and the first I flashed.

So, now I have to go, I think my info is complete. If I'm the only one, then there's probably something wrong with my phone. But I have no mods, no custom rom, nada.
Kind regards

Pull your stock root boot imgand reflash it in fastboot. Then use fkm to flash bluspark kernel. If you are using other Magisk or xposed mods check to see if they are causing issues.
Also if you tried arter kernel you will need to flash dbto img vendor_boot img and boot img in fastboot from stock firmware before using this kernel

 

[GuyInDogSuit]

Flashing the current ROM again is also an option, but it's best to always do what 4degrees mentioned, to extract those files from every ROM update, for safety reasons.

 

[zeraora]

Dear blogger, I now try to compile your code on Ubuntu 20, but it always fails too times. I wonder if you can give me some advice?
Ubuntu20. 04, gcc9, aarch64-linux-android-4.9 (this is from your makefile), but there are always various errors in the kernel source code compilation (make phase) of oneplus9 (similar to prohibiting float, unknown type name 'in_addr_t')

This afflicts me because I don't know why. May it be a compiler and environment version problem?
By the way, what platform, environment and cross compiler links do you cross compile?

 

[zeraora]

Thank you, blogger. What is your platform, environment and cross compiler link for cross compilation?

 

[GuyInDogSuit]

"blogger"?

 

[eng.stk]

blu_spark_r56 release (A11)

New build is up

This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also.

You can use FKM download kernel feature, just import the links bellow in the app.
FKM download configs: oos


Changelog:

• Build with Google Clang 14.0.2 + LLD linker
• defconfig: regenerate
• "DirtyPipe" (CVE-2022-0847) fix
• AnyKernel3 updates (v20220310)
• For root, Magisk 24.3 or newer is mandatory

Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
I am mostly interested on debugging stuff in stock stable OOS (with logs and reproducible steps to replicate the issue).


No mirrors please
Don't forget to hit like, it's free [/list]

 

[Moka UA]

Works with Android version 12??
C44

 

[Moka UA]

Works with Android version 12??
C44

 

[ekin_strops]

Works with Android version 12??
C44

 

[JWnSC]

So magisk v23 won't work with this updated kernel?

 

[mattie_49]

So magisk v23 won't work with this updated kernel?

Don't believe this has anything to do with it. Yes it will work with magisk 23. That's the magisk version for A 11 which is where this kernel is at.

 

[mattie_49]

C-44 kernel source released today !! Yay

 

[rejectedjs]

C-44 kernel source released today !! Yay

You're lying! It's too late for an April Fools joke!!

Did they really release kernel sources?? We're gonna get OOS12 kernels soon? That makes me so happy