Does this supports f.20 ?blu_spark_r134 release (A13 custom)
New build is up
I tested with lineage-20.0-20230307-nightly, kernel build may work with other ROMs that use similar device/kernel trees (confirm before flashing).
This is only for ROMS with A13 fw kernel patchset.
This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 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:
Keep in mind: 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
Development [KERNEL] [blu_spark r145 OP9/Pro] [A13 Custom]
- Thread starter eng.stk
- Start date
OOS? Nope.
You're in custom? Then yes, it's the latest LOS merged.
If you have graphical glitches, it means your ROM/build isn't using firmware/vendor blobs compatible with this kernel.
For the updater to work, add the URL from the json in Kernel Flasher Updates section. Then you'll be able to enter view and check changelog, downlaod kernel, etc
Zips will be in the Downloads folder, you must then enter the enabled slot menu in Kernel Flasher and Flash the zip.
Last edited:
i'm using blissrom which i believe uses lineage 20 as a base. after a couple reboots i was able to get it to boot without graphical glitches. i just restored back to the stock kernel cause i didnt wanna risk it anymore. i just wanted to ask what im supposed to do with the configuration json inside of kernel flasher. i'd be happy to report if it's compatible or not but i wanna give you a fair shot, i assume i made a mistake
Check my answer again.
Also a ROM being based from something doesn't mean it's compatible with current kernel patchset for that same base.
For instance we ran LOS 20 with A12 firmware and now it's A13. Sometimes different firmwares revisions within the same patchset also makes a difference, blobs merged, etc.
It's up to you to make your homework and understand what is compatible with what and why it's not.
Bliss is using A13. Maybe it's incompatible, I just sooner assumed it was my mistake using kernel patcher over there being an incompatibility. Maybe I should've asked my question in kernel flashers xda post rather than here. Sorry to bother
osm0sis
Senior Recognized Developer / Contributor
I'll say it again:
Go report these issues in your ROM thread instead and ask them to get up to date on their Lineage base, since the base has changed due to the OOS13 firmware upgrade.
Go report these issues in your ROM thread instead and ask them to get up to date on their Lineage base, since the base has changed due to the OOS13 firmware upgrade.
blu_spark_r136 release (A13 custom)
New build is up
I tested with lineage-20.0-20230314-nightly, kernel build may work with other ROMs that use similar device/kernel trees (confirm before flashing).
This is only for ROMS with A13 fw kernel patchset.
This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 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:
Keep in mind: I will give no active support for custom ROMs besides LineageOS.
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
New build is up
I tested with lineage-20.0-20230314-nightly, kernel build may work with other ROMs that use similar device/kernel trees (confirm before flashing).
This is only for ROMS with A13 fw kernel patchset.
This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 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:
Keep in mind: I will give no active support for custom ROMs besides LineageOS.
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
OK im still at OOS and am about to switch custom solely cause of blue Kernel, realy Like the cam quality of OOS but not how fck fast the battery drains in it, any custom Rom out there that has Same quality folks? Last time i tried some they had worse cam
running latest Nameless, No sound whatsoever. tried installing viper and other audio mods with the same result. Wavelet gives me an error saying wavelet was unable to instantiate QUALCOMM technologies virtualization... Also tried with disabling dolby and its other related packages and without as well
Last edited:
Update Nameless. Sound on 230320 works again with the kernel.
can you tell the advantages of this core compared to the standard one, better power saving in the background? And what are your average SOT?
Working flawlessly on the latest Nameless AOSP with OP9Pro.
Thank you for your amazing job!
Thank you for your amazing job!
Similar threads
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
15blu_spark_r145 release (A13 custom)
New build is up
I tested with lineage-20.0-20230516-nightly, kernel build may work with other ROMs that use similar device/kernel trees (confirm before flashing).
This is only for ROMS with A13 fw kernel patchset.
This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 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:
Keep in mind: I will give no active support for custom ROMs besides LineageOS.
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 free2
latest kernel build. and current lineage 20230514-NIGHTLY-lemonade. works perfect. Battery is a dream come true. The linage AOD consumes a lot of battery. but you can easily turn it off. excellent blue_spark work as always. Big thanks to Mr. eng_stk1
Thank you so much for letting me know, I just flashed your kernel and OverlayFS is working perfect, I'm so glad I'm back to your kernel, my phone is so snappy as soon as I flash your kernel as always, thanks again!!! -
102
Kernel features:
- Build with custom upstream LLVM 14.x (Clang 14.0.6 + LLD linker + IAS)
- full ThinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
- Less is more: stockish OP9 builds based on OnePlusOSS/android_kernel_oneplus_sm8350 for max stability
- Systemless installer (doesn't touch system/vendor partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
- Removed some debug and logging options
- ARM enhanced performance and battery patches
- CVE security patches, general upstream and CAF fixes for important subsystems
- Modded schedutil governor merged from latest CAF sm8350 patchset
- No OC, use 250HZ base timer frequency
- msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
- Enhanced TCP methods (westwood is default, BBR available), Network tweaks and updated drivers
- Several I/O control tweaks, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
- ZRAM Swap (4GB LZ4 default) and with file disabled (2 GB storage gain), LZO-RLE and ZSTD are available
- Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
- KGSL fixes and general improvements for GPU driver
- adrenoboost ready (disabled by default)
- Backlight min brightness and brightness scaling (custom) option
- Gamepad support enabled (xbox, ps4, switch)
- USB2 Fast Charge (USB mode up to 900mA with MTP on)
- FS fsync toggle on/off
- Wakelock blockers available
- wireguard support
- Compatible with Kernel Flasher, EXKM, FKM , Kernel Adiutor and others
Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
If you come from other kernel or have any issues, you should restore your stock boot.img/vendor_boot.img or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
If you are upgrading between blu_spark versions, just flash the kernel zip.
About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock OOS ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
If you're using custom ROMs (including stock based ones) and OOS Open Betas you're much on your own. I'm mostly interested on debugging stuff in stock and stable OOS.
Also try not to spam the thread with OT. There's threads for all kind of stuff, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img/vendor_boot.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
Source Code: https://github.com/engstk/op9
Don't forget to hit thanks, it's free
OnePlus 9 Pro development unit donated by OnePlus. Big shouts to them
Very proud for being on the OnePlus Developer Program, special thanks to dev relations team.33blu_spark_r23 release
First blu_spark build for the OP9 series is up
This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also (need some fixes since code is broken). So backup you boot if you want to test and let me know
Kernel already have some merged goodies and I think I have a good base to work with. For a couple days of work, it's not bad
I'll take a look into more stuff to come, some things in OP are WIP. Stay tuned!
You can use FKM download kernel feature, just import the links bellow in the app.
FKM download configs: oos
Changelog:
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 thanks, it's free21[Thread Cleaned]
Good (or perhaps not so good?) day everyone! I've removed a few posts but left the ones that matter: civilized closure of conflict – social media can learn a thing or two from this. As we sit behind our desks and in our couches (or on a plane, even that's a thing nowadays), protected by that anonymity shield, we easily throw our words out into the world. And sometimes we regret them. Unfortunately, we find it so easy to judge one another for that. But facing the fact that we're all just humans that make mistakes, I believe we know that we shouldn't judge so quickly. Now more than ever; kindness should prevail.
Thank you for your attention and have an energetic day or quiet night in your part of the world. If you need a chat, drop me a line. Just keep our development threads focused on development and mutual respect.
Cheers!
Timmy
Forum Moderator18blu_spark_r120 release (A13 custom)
New build is up
I tested with lineage-20.0-20230103-nightly-lemonadep, kernel build may work with other ROMs that use similar device/kernel trees.
This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 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:
Keep in mind: 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 free17blu_spark_r52 release
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:
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 thanks, it's free
