[KERNEL] [blu_spark r181 OP8/Pro/T] [A12 OOS/Custom]

Search This thread

Phahec

Senior Member
Jun 15, 2018
197
99
Hi all
I confirm, after flashing kernel Oos12 lost warp/vooc charging, and charging is also slow.
Flashing back stock kernel warp charging is working again.
Weird 🤔
 

Phahec

Senior Member
Jun 15, 2018
197
99
Pro or T? As i said on Pro working normally. But vibration really sucks with 12, dont know its a kernel issue...
...and using alarm slider sometimes freezes and reboots device.
Sorry I forgot. I use oneplus 8T oos12 c20.
Kernel looks working great with Zen i/o and gpu boost.
Something weird is usb fast charging came back to disable after each reboot so I have to enable it after rebooting.
Maybe this is the bug of warp charging I don't know 🤔
For the slider I don't have issues.
I noticed that 4 small cores used to stuck at 1600 mhz all the time, even when no application was in back ground. And it seems to drain battery, in 8 minutes I lost 4%,but it's the first day with blue spark kernel,I will check after few days.
But for a FIRST OOS12 kernel it's a good beginning
Thanks to THE DEV he is the first people who can create Oos12 kernel 👍👍👍
Many devs gave up with oos12 **** sources
 
Last edited:

nihilista

Senior Member
Feb 1, 2012
1,457
443
Ruhrgebiet
OnePlus 8 Pro
Sorry I forgot. I use oneplus 8T oos12 c20.
Kernel looks working great with Zen i/o and gpu boost.
Something weird is usb fast charging came back to disable after each reboot so I have to enable it after rebooting.
Maybe this is the bug of warp charging I don't know 🤔
But for a FIRST OOS12 kernel it's a good beginning
Thanks to THE DEV he is the first people who can create Oos12 kernel 👍👍👍
Many devs gave up with oos12 **** sources
Yes, many thx to dev for that, was the only thing stopping me to switch to 12. But 12 is buggy, after some hours with some nasty bugs i found its ok, but buggy. But i had to know that after reading some posts in oneplus forum ;-)
 

eng.stk

Senior Member
Mar 29, 2011
7,157
60,823
OnePlus 5T
OnePlus 6
Well, I honestly tried.

It's 8350 all over again, I'm done with (C)OOS sources. Specially since OOS 11 on the OP7 series, stuff is just going downhill fast.
I lost days already fixing crap for 8350 and 8250 alone, including porting stuff from other trees. Stuff continues to be broken and/or missing.
By the reports I count 3 or 4 subsystems that I feel important to be left derped.
Specially critical stuff like charging, that can hurt people's HW, I ain't tinkering with that, sorry.
So, since I also can't stand the bloaded mess that C(OOS) 12 is, I'm done.


When LOS ships with A12 codebase, if I like how it runs on the device I will support it like I did on the OP9 series.
Until then, sayonara. This device is dead to me.
 
Last edited:

Noob9496

Senior Member
Jul 28, 2017
332
102
OnePlus 6
OnePlus 8 Pro
Oneplus 8 pro, oos 11 blu_spark r130
App name
Cross platform disk test
Lowest is with fsync on
Highest is with fsync off
 

Attachments

  • Screenshot_20220706-130658.jpg
    Screenshot_20220706-130658.jpg
    358.6 KB · Views: 75
  • Screenshot_20220706-130838.jpg
    Screenshot_20220706-130838.jpg
    388.4 KB · Views: 73

kkkhattak

Senior Member
Dec 3, 2011
958
176
Peshawar
Google Pixel 6 Pro
Well, I honestly tried.

It's 8350 all over again, I'm done with (C)OOS sources. Specially since OOS 11 on the OP7 series, stuff is just going downhill fast.
I lost days already fixing crap for 8350 and 8250 alone, including porting stuff from other trees. Stuff continues to be broken and/or missing.
By the reports I count 3 or 4 subsystems that I feel important to be left derped.
Specially critical stuff like charging, that can hurt people's HW, I ain't tinkering with that, sorry.
So, since I also can't stand the bloaded mess that C(OOS) 12 is, I'm done.


When LOS ships with A12, if I like how it runs on the device I will support it like I did on the OP9 series.
Until then, sayonara. This device is dead to me.
No more updates for A11 too ?
 

eng.stk

Senior Member
Mar 29, 2011
7,157
60,823
OnePlus 5T
OnePlus 6
Guess this was a lie 😂😂😂😂
That is a general statement, not a "hey I'm going to support this particular device until I'm dead".
I gave and continue to give support to dozens of devices over the years.

Need better support for this device, go ask OP.
As it stands, I'm out. Door left open for LOS (yet...).

I don't lie, I'm actually quite upfront about stuff.
I bother explaining the what and the why's over stuff.
Even gave a little more effort over th ecrap situation we're at concerning sources.
Could just abandon thread and/or close like others did. But I didn't (yet...).

Let's stay positive. I'm looking forward to LOS :)
 
Last edited:

jamescable

Senior Member
That is a general statement, not a "hey I'm going to support this particular device until I'm dead".
I gave and continue to give support to dozens of devices over the years.

Need better support for this device, go ask OP.
As it stands, I'm out. Door left open for LOS (yet...).
Well we obviously have working boot for 12.1 custom kernels since we a lot of ROMs using it so why not just build for custom? Aicp, crdroid, etc
 

Phoenix47

Senior Member
Aug 15, 2020
706
302
OnePlus 8T
OnePlus 9
Well, I honestly tried.

It's 8350 all over again, I'm done with (C)OOS sources. Specially since OOS 11 on the OP7 series, stuff is just going downhill fast.
I lost days already fixing crap for 8350 and 8250 alone, including porting stuff from other trees. Stuff continues to be broken and/or missing.
By the reports I count 3 or 4 subsystems that I feel important to be left derped.
Specially critical stuff like charging, that can hurt people's HW, I ain't tinkering with that, sorry.
So, since I also can't stand the bloaded mess that C(OOS) 12 is, I'm done.


When LOS ships with A12, if I like how it runs on the device I will support it like I did on the OP9 series.
Until then, sayonara. This device is dead to me.
Hey ! Can I atleast get dtbo image for 8t ?
 

eng.stk

Senior Member
Mar 29, 2011
7,157
60,823
OnePlus 5T
OnePlus 6
Well we obviously have working boot for 12.1 custom kernels since we a lot of ROMs using it so why not just build for custom? Aicp, crdroid, etc
I will not build for something I don't personally use.
I will not build for old codebase. I don't care about having a 12.1 ROM with a patched up A11 codebase kernels or CAF adaptations.

Lastly: I'll always build and give support to stuff out of fun and on my own terms. That's not going to change.
 
Last edited:

nihilista

Senior Member
Feb 1, 2012
1,457
443
Ruhrgebiet
OnePlus 8 Pro
Well, I honestly tried.

It's 8350 all over again, I'm done with (C)OOS sources. Specially since OOS 11 on the OP7 series, stuff is just going downhill fast.
I lost days already fixing crap for 8350 and 8250 alone, including porting stuff from other trees. Stuff continues to be broken and/or missing.
By the reports I count 3 or 4 subsystems that I feel important to be left derped.
Specially critical stuff like charging, that can hurt people's HW, I ain't tinkering with that, sorry.
So, since I also can't stand the bloaded mess that C(OOS) 12 is, I'm done.

When LOS ships with A12 codebase, if I like how it runs on the device I will support it like I did on the OP9 series.
Until then, sayonara. This device is dead to me.
Too bad, but absolutely understandable. I dont know much about building kernel but if one of the most skilled developer gives up, the people from oneplus didnt made their job. OOS 12 seems beta for now, i hope things get better, but for now it maybe could be better to stay with OOS11........
 

dlb4all

Senior Member
May 12, 2013
173
52
OnePlus 8T
Ahhh... OnePlus realllly dropped the ball with a12 and that massive crap of buggy kernel source
certainly doesnt make it easier for the devs and the community . but then oneplus was always stingy about releasing codes or was unwlling . a lot of promised was made by them but non delivered.
i guess im gonna skip a12 and wait for the next one then
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    blu_spark_r171 release (A12 custom)

    New build is up (y)

    I tested with lineage-19.1-20220901-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 by @capntrips 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 14.x (Clang 14.0.6 + LLD linker)
    • Rebase to lineage-19.1 from LineageOS/android_kernel_oneplus_sm8250
    • vendor/drivers/techpack: fix build and linking errors
    • Several upstream build fixes
    • Added some blu_spark goodies (check git for details)
    • wireguard updates
    • 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 :)
    11
    blu_spark_r181 release (A12 custom)

    New build is up (y)

    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 :)
    4
    Hi, can you help me how to change the file step by step please ?

    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.
    2
    los+bluspark
    best sir 😎
    2
    Anyone tried on evox 17.0 (Android 13)?
  • 96
    DWHxIK

    Kernel features:
    • Build with Google Clang version 15.0.1 + LLD linker + IAS
    • Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
    • Less is more: stockish OP8 builds based on OnePlusOSS/android_kernel_oneplus_sm8250 for max stability
    • Systemless installer (doesn't touch system 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 sm8250 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, added schedulers ZEN v2 is default, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
    • ZRAM Swap (LZ4 default) and with file disabled, 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 backlight scale option
    • Gamepad support enabled (xbox, ps4, switch)
    • USB Fast Charge (USB mode up to 900mA with MTP on)
    • FS fsync toggle on/off
    • Wakelock blockers available
    • wireguard support
    • CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
    • Compatible with Kernel Adiutor, EXKM, FKM 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 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 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/op8
    Don't forget to hit thanks, it's free ;)


    OnePlus 8 Pro development unit donated by OnePlus. Big shouts to them :)
    Very proud of being on the OnePlus Developer Program, special thanks to dev relations team.
    29
    blu_spark_r109 release

    New build is up (y)

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    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.7 + LLD linker
    • Add some build improvements
    • Silence a couple logging and debug
    • wireguard updates (v1.0.20210606)
    • AnyKernel3 updates sync
    • For root, Magisk v23.0 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 thanks, it's free :)
    28
    blu_spark_r115 release

    New build is up!

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Synchronize codes for OnePlus 8T Oxygen OS 11.0.12.12.KB05AA and OnePlus 8 Oxygen OS 11.0.9.9.IN21AA and OnePlus 8 Pro Oxygen OS 11.0.9.9.IN11AA
    • AnyKernel3 updates (v20211215)
    • For root, Magisk v23.0 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 thanks, it's free :)
    28
    blu_spark_r110 release

    New build is up (y)

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    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.7 + LLD linker (updated)
    • hwtracing: Add entries from kona-coresight (tentative less idle draw)
    • defconfig: enable ld deadcode elimination
    • arm64: Allow LD_DEAD_CODE_DATA_ELIMINATION to be selected
    • arm64: Keep alternative-instruction sections
    • AnyKernel3 updates (v20210721)
    • For root, Magisk v23.0 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 thanks, it's free :)
    26
    blu_spark_r101 release

    New build is up (y)

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Revert "fs: exfat: sync with v5.8-1arter97"
    • defconfig: disable IKHEADERS
    • Remove some logspam and debug
    • net/wireguard: merge v1.0.20210424
    • AnyKernel3 updates sync
    • For root, Magisk v22.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 thanks, it's free :)