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

Search This thread

reffu

Senior Member
Feb 11, 2008
116
45
OnePlus 9
It's been mentioned, but can confirm newest version doesn't work with Nameless 12.1 for OP9 (Lemonade). Flashed through FKM and rebooted. Boots to initial boot screen (with "Powered By Android" on the bottom) but never loads past that. Flashing dtbo and ROM boot.img allowed booting back into Rom (without Blu_Spark)
 
  • Like
Reactions: Rilindd

Rilindd

Member
Jan 9, 2017
33
4
It's been mentioned, but can confirm newest version doesn't work with Nameless 12.1 for OP9 (Lemonade). Flashed through FKM and rebooted. Boots to initial boot screen (with "Powered By Android" on the bottom) but never loads past that. Flashing dtbo and ROM boot.img allowed booting back into Rom (without Blu_Spark)
Same here with StagOS.
 

Stogie87

Senior Member
Oct 3, 2015
1,055
476
Berlin
Seems like audio distortion bug on LOS 19.1 based custom roms was fixed on los kernel side. Will this fix be included in blu spark as well?
 

Stogie87

Senior Member
Oct 3, 2015
1,055
476
Berlin
Okay, then it was probably not just a kernel issue. I hope devs for other custom roms can also fix it easily.
 
Last edited:
  • Like
Reactions: eng.stk

eng.stk

Senior Member
Mar 29, 2011
7,128
60,665
OnePlus 5T
OnePlus 6
blu_spark_r96 release (A12 custom)

New build is up (y)

I tested with lineage-19.1-20220628-nightly-lemonadep-signed.zip, 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.

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


Changelog:
  • drm-msm-dsi: add backlight scale option (up/down speed/power ratio brightness changes)
  • net/wireguard: merge v1.0.20220627 from wireguard-linux-compat
  • Properly ship vendor_boot (thanks to @osm0sis)
  • Don't ship dtb to improve ROM compatibility
  • Misc. fixes to improve install process
  • For root, Magisk 25.1 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 :)
 

EtherealRemnant

Senior Member
Sep 15, 2007
3,730
1,165
37
Denver, CO
r96 didn't work on StagOS 12.1 on my 9. Manually flashed the zip with FKM and when it rebooted, I got kicked back to fastboot. Restoring boot and vendor_boot didn't fix it, reflashing boot, dtbo, and vendor_boot didn't either. I had to dirty flash the ROM to get it to boot again (fortunately the recovery still worked).

I don't have time to test it right now, was actually scrambling to fix it because I have a doctor's appointment, but those are my findings so far. Presumably if the Lineage code changes aren't compatible, this would break every custom ROM besides Lineage so beware when trying it.
 
  • Like
Reactions: golfgtiedition30

Shooter7889

Senior Member
Mar 24, 2019
204
110
FLORENCE
OnePlus 7 Pro
OnePlus 8T
I got it to flash and reboot no problem, on latest StagOS. But yest I went thru several different ROMs and sometimes I could flash BluSpark no problem and sometimes no matter if I had flashed it the last time I was on "said ROM" but this time it's wld not boot no matter what I did. I think maybe the problem is, if ur on a ROM w/BluSpark, if u switch ROMs if u don't reflash stock dtbo, vendor_boot, and boot imgs for "said" rom b4 and switching roms that is the problem that keeps u from flashing kernal after switching roms. So now I reflash those imgs, reboot into stock rom(no root, no kernal) then back to BL and then flash the 3 imgs to go into recovery to go to different rom(lol) then once set up and rooted I can flash BluSpark fine.. I am not sure.... 🤔

Edit/update

Ok, so testing my theory, I went from having StagOS on slotA(I restored dtbo, vendor_boot and boot) and then rebooted, went to BL, flashed new imgs for SparkOS, went to recovery, wiped and adb sideload the new ROM.. after setting up and rooting I attempted to flash BluSpark. I was on slotB, also I had went from one ROM on slotA and now different one on slotB. Forced to fastboot.. I had to reflash Spark imgs, then I went to recovery and adb sideloaded ROM again to get to slotA.. Then I successfully flashed BluSpark!

So for BluSpark to work you either 1) have to be on slotA or 2)u need to have whatever ROM u are on, on both slots..thank you eng.stk for great kernal!! Maybe u can confirm/deny my theory..
 

Attachments

  • Screenshot_20220629-181820_Settings.png
    Screenshot_20220629-181820_Settings.png
    1.1 MB · Views: 55
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    blu_spark_r99 release (A12 custom)

    New build is up (y)

    I tested with lineage-19.1-20220712-nightly-lemonadep-signed.zip, 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.

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

    In case of derps during flashing, check this first:


    Changelog:
    • ThinLTO build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS)
    • Couple cleanup reverts
    • Fix some build naming and actions
    • For root, Magisk 25.1 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 :)
    10
    blu_spark_r100 release (A12 custom)

    New build is up (y)

    I tested with lineage-19.1-20220720-nightly-lemonadep-signed.zip, 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.

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

    Don't flash kernel zipright after LOS update and don't use LOS recovery.
    Have the system booted in a clean rooted state, don't flash any zips, reboot, flash kernel zip, reboot.
    In case of derps during flashing, check this first to get system back up running:
    https://forum.xda-developers.com/t/...-pro-a11-oos-a12-custom.4286037/post-87170985
    https://forum.xda-developers.com/t/...-pro-a11-oos-a12-custom.4286037/post-87092451
    https://forum.xda-developers.com/t/...-pro-a11-oos-a12-custom.4286037/post-87098111


    Changelog:
    • Merge lineage-19.1-20220719-nightly kernel updates
    • For root, Magisk 25.1 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 :)
    9
    blu_spark_r97 release (A12 custom)

    New build is up (y)

    I tested with lineage-19.1-20220712-nightly-lemonadep-signed.zip, 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.

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


    Changelog:
    • Merge lineage-19.1-20220712-nightly kernel updates
    • For root, Magisk 25.1 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 :)
    8
    blu_spark_r102 release (A12 custom)

    New build is up (y)

    I tested with lineage-19.1-20220726-nightly-lemonadep-signed.zip, 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.

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

    Don't flash kernel zipright after LOS update and don't use LOS recovery.
    Have the system booted in a clean rooted state, don't flash any zips, reboot, flash kernel zip, reboot.
    In case of derps during flashing, check this first to get system back up running:
    https://forum.xda-developers.com/t/...-pro-a11-oos-a12-custom.4286037/post-87170985
    https://forum.xda-developers.com/t/...-pro-a11-oos-a12-custom.4286037/post-87092451
    https://forum.xda-developers.com/t/...-pro-a11-oos-a12-custom.4286037/post-87098111


    Changelog:
    • Merge lineage-19.1-20220726-nightly kernel updates
    • Small rebase and cleanup
    • Flash vendor_dlkm temporary fix
    • AnyKernel3 updates (v20220727)
    • 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 :)
    6
    With Crdroid based on OOS12 firmware C.61 you can't install this kernel it just out right fails. Hopefully it will be updated soon!
    Changes are needed for C.61 fw, will push a build today or tomorrow when I update my LOS.
  • 80
    DWHxIK

    Kernel features:
    • Build with custom upstream LLVM 14.x (Clang 14.0.5 + 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 FKM, EXKM, Kernel Adiutor and others


    DOWNLOAD KERNEL ZIP
    FKM download configs: oos | custom
    (No mirrors please)​


    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.
    31
    blu_spark_r23 release

    First blu_spark build for the OP9 series is up (y)

    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:
    • Build with Google Clang 12.0.5 + LLD linker
    • Synchronize codes for OnePlus 9/Pro Oxygen 11.2.6.6.LE25AA
    • Several build error fixes and quirks handled
    • Compilation improvements an cruf removed
    • Some goodies already merged like filesystem stuff, cpu governor & boost/msm perf, TCP algos, wakelock blocker, vibration and haptic feedback control, gpu adrenoboost, etc
    • All drivers builtin, wifi stack and datarmmnet merged from CAF
    • net/wireguard: merge v1.0.20210424


    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 :)
    21
    [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 Moderator
    17
    blu_spark_r52 release

    New build is up (y)

    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:
    • Synchronize codes for OnePlus 9 Oxygen 11.2.10.10
    • f2fs: shrink node_write lock coverage
    • AnyKernel3 updates (v20211215)
    • Couple init runtime adjusts to better UX
    • For root, Magisk 23.0 or higher 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 thanks, it's free :)
    16
    blu_spark_r54 release

    New build is up (y)
    One last A11 hurrah before stuff start to line up for A12.

    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.1 + LLD linker
    • wakelock blocker updates
    • Couple build reverts
    • AnyKernel3 updates (v20220126)
    • For root, Magisk 24.1 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 :)