[KERNEL] [blu_spark r216 OP8/Pro/T] [A13 Custom]

[eng.stk]

blu_spark_r181 release (A12 custom)

New build is up

I tested with lineage-19.1-20220922-nightly-kebab-signed.zip, kernel build may work with other ROMs that use similar device/kernel trees.
This kernel is tested for the 8T but it's unified, so should work for the OP8/Pro also.

For flashing and easy of install logging, Kernel Flasher is recommended

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
Download config: custom


Changelog:

• Build with custom upstream LLVM 15.x (Clang 15.0.1 + LLD linker + IAS)
• Merge lineage-19.1-20220922-nightly kernel updates
• scripts: Makefile.build: silent objdump error message
• makefile: disable some clang noise
• drivers: vendor/techpack: fix build errors for clang-15
• defconfig: enable QCA6390 wifi extensions
• vendor/drivers: enable owakelock driver
• vendor/drivers: add owakelock drivers
• For root, Magisk 25.2 or newer is mandatory

Keep in mind: I will give no active support for custom ROMs (just kidding ;p).
I am mostly interested on debugging stuff with logs and reproducible steps to replicate the issue.


No mirrors please
Don't forget to hit like, it's free

 

[YassGo]

Thank you ! Running great but still having this strange boot message (even if it's working fine)
Any idea @eng.stk ?

 

[miramax001]

https://raw.githubusercontent.com/engstk/kernelfkm/master/updater_op8_custom.json

FrancoKM says: SHA-1 hashes don't matches. I'm the only one with this problem?

 

[dyval]

Is latest OOS 12 C.35 on 8pro works still with last released kernel? Thank you.

 

[Kobir_papon]

Still now not release oos A12 keenel tree???

 

[tay200k]

Flashed latest on latest Nameless a12 and also getting the message "There's an internal problem in your device." on boot.

 

[Coblan 86]

Will this work with latest c.41 update for t-mobile 8t+5g?

 

[dyval]

Still now not release oos A12 keenel tree???

Not unless there was no change in kernel on the latest version.

 

[Mr Hassan]

Done.

 

[eng.stk]

I don't and I won't support OOS 12.

We are passed this.

 

[Iron-E]

No kcal for FoD devices, already said many times.

The stock options for screen temperature control are unfortunately quite lacking in comparison… perhaps the author of Radioactive Kernel could help?

In my two years using that kernel, I've never encountered issues with it (though I am looking to move off Radioactive, because it is EOL).

 

[eng.stk]

The stock options for screen temperature control are unfortunately quite lacking in comparison… perhaps the author of Radioactive Kernel could help?

In my two years using that kernel, I've never encountered issues with it (though I am looking to move off Radioactive, because it is EOL).

I was involved inkcal a few years ago, I know what I'm talking about.
Want to know details search my several threads with FoD devices.
kcal isn't going to come back on my builds.

 

[Adzkii]

@eng.stk can we know what custom a12 rom you using with this kernel?

 

[DrDominate]

@eng.stk can we know what custom a12 rom you using with this kernel?

He uses nightly lineageOS 19 rom.

 

[eng.stk]

@eng.stk can we know what custom a12 rom you using with this kernel?

He uses nightly lineageOS 19 rom.

Indeed

 

[ecompton59]

working great on kinda stock 12 had to change things to bypass Google

 

[Wannajmi03]

Hi @eng.stk does this kernel support OnePlus 9r oos11?

 

[eng.stk]

Hi @eng.stk does this kernel support OnePlus 9r oos11?

Nope, 8 series kernel only.

 

[afrob101]

Does someone use this Kernel with the Evo7.2 Rom in oneplus 8T?

 

[DrDominate]

Does someone use this Kernel with the Evo7.2 Rom in oneplus 8T?

Nope

Starting with my evo builds from 09/16, you won't be able to boot with this kernel as I had to nuke oplus port of erofs and import it from the backport repo. Without these changes (which blu spark doesn't have), I couldn't get erofs working properly, which is what evo is using instead of ext4.