• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[KERNEL] [blu_spark r112 OP8/Pro/T] [A11 OOS]

Search This thread

Imprezzion

Senior Member
Dec 12, 2011
671
249
Gorredijk
OnePlus 8 Pro
Hi 😊 first of all thanks for your work 🙂
One question. You say you don't give support to custom ROMs but can you say if it works on them or not. Because it's a little bit confuse to me when I open the "custom" link from OP page. It says "OOS 11, custom + OOS 10"😊
Thanks in advanced and keep strong and healthy 😉

Like I posted 2 posts above this one, I just decided to give it a try on custom A11 as obviously I have a backup .img of the stock rooted kernel anyway.

Yes, I can confirm it works without any problems on CrDroid 7.1 which is A11 custom. I imagine it will work fine on LOS 18.1 / PE as well.
 

Shooter7889

Senior Member
Mar 24, 2019
122
50
FLORENCE
OnePlus 7 Pro
OnePlus 8T
Like I posted 2 posts above this one, I just decided to give it a try on custom A11 as obviously I have a backup .img of the stock rooted kernel anyway.

Yes, I can confirm it works without any problems on CrDroid 7.1 which is A11 custom. I imagine it will work fine on LOS 18.1 / PE as well.
Custom/works on EvoX as well with all functionality/no issues. I've been running both together all wk perfectly
 
  • Like
Reactions: alex moymoy
D

Deleted member 5408779

Guest
Hi @eng.stk I flashed the latest r78 on OnePlus 8T 11.0.6.9 EU (magisk v21.2 too) using EXKM and I got a bootloop into recovery. Didn't happen with the previous version.

EDIT: not sure why but somehow it worked in the end. Due to the bootloop I booted my patched stock OOS boot.img, and I direct install magisk after booting. After that it reboots successfully into blu_spark r78

I have used FKM to flash r78 on my 8T with 11.0.6.9 and didn't have any issues.
 

tidschi

Senior Member
Mar 5, 2008
329
92
Hi @eng.stk I flashed the latest r78 on OnePlus 8T 11.0.6.9 EU (magisk v21.2 too) using EXKM and I got a bootloop into recovery. Didn't happen with the previous version.

EDIT: not sure why but somehow it worked in the end. Due to the bootloop I booted my patched stock OOS boot.img, and I direct install magisk after booting. After that it reboots successfully into blu_spark r78

Here the same, went also into recovery because of bootlop. I only wiped cache, tried again and it boots again. Maybe luck?
 

Reddit3321

Senior Member
Jan 19, 2017
50
36
Here the same, went also into recovery because of bootlop. I only wiped cache, tried again and it boots again. Maybe luck?

I also had the same experience, flashed with exkm and bootlooped to recovery eventually. I didn't have a saved copy of my stock boot img anywhere except for my phone so I screwed my self and ended up msm tool'ing.

After I got back up and running again, I tried this time flashing with fkm and I have not had any troubles since. I think it may have something to do with the AK3 changes and how exkm flashes.
 

tidschi

Senior Member
Mar 5, 2008
329
92
I also had the same experience, flashed with exkm and bootlooped to recovery eventually. I didn't have a saved copy of my stock boot img anywhere except for my phone so I screwed my self and ended up msm tool'ing.

After I got back up and running again, I tried this time flashing with fkm and I have not had any troubles since. I think it may have something to do with the AK3 changes and how exkm flashes.

Forgot to mention, that I flashed with FKM. xD
 

RMarques

Senior Member
Jan 28, 2013
952
160
OnePlus 8
@eng.stk

Sup bud, thanks for putting your project out there to all of us to enjoy!

I'm rolling with a rooted OP8, featuring A11 OB5 + xXx + Acc module. Using FKM to manage kernel options.

I'd like to ask if:

1. Does it have sound control? I'm looking forward to be able to improve my bluetooth earbuds mic input volume, so ppl can hear me better.

2. Does it have battery idle? Device starts to draw power directly from the power outlet, once Acc does reach a given battery level, allowing you to let it connected to the charger all night long, reducing battery heat and stress.
 
  • Like
Reactions: eng.stk

eng.stk

Senior Member
Mar 29, 2011
6,922
59,470
OnePlus 5T
OnePlus 6
@eng.stk

Sup bud, thanks for putting your project out there to all of us to enjoy!

I'm rolling with a rooted OP8, featuring A11 OB5 + xXx + Acc module. Using FKM to manage kernel options.

I'd like to ask if:

1. Does it have sound control? I'm looking forward to be able to improve my bluetooth earbuds mic input volume, so ppl can hear me better.

2. Does it have battery idle? Device starts to draw power directly from the power outlet, once Acc does reach a given battery level, allowing you to let it connected to the charger all night long, reducing battery heat and stress.
Welcome :)

1. Nope, already discussed this for others devices.
2. Nope OP8 already has a complicated charging stack as it is and intwligent charging is already in place.
 
  • Like
Reactions: RMarques

Boing7898

Member
Aug 10, 2011
44
8
Hi @eng.stk
I've noticed in your OP7/Pro blu_spark kernels you added support for WiFi on ROMs that have built in wifi module (like LOS with the latest updates):

- Rework runtime backend to suport WLAN in all custom ROM variants (via AK3 kernel companion Magisk module)
- Misc. LOS patches for better device support (custom)

Do you have any plans in doing the same for this kernel for OP8/8T/Pro?

Thank you for your work!
 
  • Like
Reactions: eng.stk

eng.stk

Senior Member
Mar 29, 2011
6,922
59,470
OnePlus 5T
OnePlus 6
Hi @eng.stk
I've noticed in your OP7/Pro blu_spark kernels you added support for WiFi on ROMs that have built in wifi module (like LOS with the latest updates):

- Rework runtime backend to suport WLAN in all custom ROM variants (via AK3 kernel companion Magisk module)
- Misc. LOS patches for better device support (custom)

Do you have any plans in doing the same for this kernel for OP8/8T/Pro?

Thank you for your work!
All my current Oneplus lineup have that in place (y)
 
  • Like
Reactions: Boing7898

Boing7898

Member
Aug 10, 2011
44
8
All my current Oneplus lineup have that in place (y)
Oh that's great!
Do you have any idea what could the problem be then? Magisk module is enabled, can't enable WiFi though.
Here's the logcat

Code:
01-13 22:41:06.467   957   957 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-13 22:41:08.274   957   957 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-13 22:41:10.486   957   957 E [email protected]: Failed to access driver state control param No such file or directory, 2: No such file or directory
01-13 22:41:10.486   957   957 E [email protected]: Failed to load WiFi driver
01-13 22:41:10.486   957   957 E [email protected]: Failed to initialize firmware mode controller
01-13 22:41:10.486   957   957 E [email protected]: Wifi HAL start failed
01-13 22:41:10.487  1492  1953 E HalDevMgr: Cannot start IWifi: 9 ()
01-13 22:41:10.487  1492  1953 E WifiVendorHal: Failed to start vendor HAL
01-13 22:41:10.487  1492  1953 E WifiNative: Failed to start vendor HAL
01-13 22:41:10.487  1492  1953 E WifiNative: Failed to start Hal
01-13 22:41:10.487  1492  1953 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle

Thank you!!
 

eng.stk

Senior Member
Mar 29, 2011
6,922
59,470
OnePlus 5T
OnePlus 6
Oh that's great!
Do you have any idea what could the problem be then? Magisk module is enabled, can't enable WiFi though.
Here's the logcat

Code:
01-13 22:41:06.467   957   957 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-13 22:41:08.274   957   957 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-13 22:41:10.486   957   957 E [email protected]: Failed to access driver state control param No such file or directory, 2: No such file or directory
01-13 22:41:10.486   957   957 E [email protected]: Failed to load WiFi driver
01-13 22:41:10.486   957   957 E [email protected]: Failed to initialize firmware mode controller
01-13 22:41:10.486   957   957 E [email protected]: Wifi HAL start failed
01-13 22:41:10.487  1492  1953 E HalDevMgr: Cannot start IWifi: 9 ()
01-13 22:41:10.487  1492  1953 E WifiVendorHal: Failed to start vendor HAL
01-13 22:41:10.487  1492  1953 E WifiNative: Failed to start vendor HAL
01-13 22:41:10.487  1492  1953 E WifiNative: Failed to start Hal
01-13 22:41:10.487  1492  1953 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle

Thank you!!
You provided the answer.
So either the module is not loading correctly or the ROM you're using has a different CAF base that makes HAL/driver render imcompatible.
Try the magisk module solo in Magisk 21.2. What ROM is that in which device?
 
  • Like
Reactions: Boing7898

Boing7898

Member
Aug 10, 2011
44
8
You provided the answer.
So either the module is not loading correctly or the ROM you're using has a different CAF base that makes HAL/driver render imcompatible.
Try the magisk module solo in Magisk 21.2. What ROM is that in which device?
First of all thanks for your reply, I know you're not really interested in helping debugging with custom ROMs. Custom kernels are pretty important to me so if they won't work with this ROM I might be forced to switch.
I'm running Magisk 21.2, with no other modules than the AnyKernel3 helper module. ROM is LineageOS 18.1, latest update, on Oneplus 8T.
 

eng.stk

Senior Member
Mar 29, 2011
6,922
59,470
OnePlus 5T
OnePlus 6
First of all thanks for your reply, I know you're not really interested in helping debugging with custom ROMs. Custom kernels are pretty important to me so if they won't work with this ROM I might be forced to switch.
I'm running Magisk 21.2, with no other modules than the AnyKernel3 helper module. ROM is LineageOS 18.1, latest update, on Oneplus 8T.


Using Bluspark on LOS 18.1 fine. Apart from WiFi everything seems to work perfectly :)

Try this one for me
 

Attachments

  • blu_spark_r79-custom_op8x_b4c239c22.zip
    20.5 MB · Views: 12

Boing7898

Member
Aug 10, 2011
44
8
Sadly it still doesn't work :(
Restarted twice after flashing, waited some time after boot, checked the Magisk module was enabled.
Logs look the same, here they are:
Code:
01-16 09:54:19.749   955   955 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-16 09:54:21.557   955   955 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-16 09:54:23.354     0     0 E         : [20210116_09:54:23.353264]@0 [SWARPCHG][mp2650_float_voltage_write]vfloat_mv = 4435
01-16 09:54:23.454     0     0 E         : [20210116_09:54:23.353680]@0 [SWARPCHG][mp2650_float_voltage_write]set the same fv 0x72, return!
01-16 09:54:23.454     0     0 W healthd : battery l=72 v=4062 t=30.3 h=2 st=2 c=-153000 fc=2067 cc=5 chg=u
01-16 09:54:23.773   955   955 E [email protected]: Failed to access driver state control param No such file or directory, 2: No such file or directory
01-16 09:54:23.773   955   955 E [email protected]: Failed to load WiFi driver
01-16 09:54:23.773   955   955 E [email protected]: Failed to initialize firmware mode controller
01-16 09:54:23.773   955   955 E [email protected]: Wifi HAL start failed
01-16 09:54:23.775  1449  2159 E HalDevMgr: Cannot start IWifi: 9 ()
01-16 09:54:23.775  1449  2159 E WifiVendorHal: Failed to start vendor HAL
01-16 09:54:23.775  1449  2159 E WifiNative: Failed to start vendor HAL
01-16 09:54:23.776  1449  2159 E WifiNative: Failed to start Hal
01-16 09:54:23.776  1449  2159 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle

Thanks man!
 
  • Like
Reactions: eng.stk

eng.stk

Senior Member
Mar 29, 2011
6,922
59,470
OnePlus 5T
OnePlus 6
Sadly it still doesn't work :(
Restarted twice after flashing, waited some time after boot, checked the Magisk module was enabled.
Logs look the same, here they are:
Code:
01-16 09:54:19.749   955   955 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-16 09:54:21.557   955   955 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-16 09:54:23.354     0     0 E         : [20210116_09:54:23.353264]@0 [SWARPCHG][mp2650_float_voltage_write]vfloat_mv = 4435
01-16 09:54:23.454     0     0 E         : [20210116_09:54:23.353680]@0 [SWARPCHG][mp2650_float_voltage_write]set the same fv 0x72, return!
01-16 09:54:23.454     0     0 W healthd : battery l=72 v=4062 t=30.3 h=2 st=2 c=-153000 fc=2067 cc=5 chg=u
01-16 09:54:23.773   955   955 E [email protected]: Failed to access driver state control param No such file or directory, 2: No such file or directory
01-16 09:54:23.773   955   955 E [email protected]: Failed to load WiFi driver
01-16 09:54:23.773   955   955 E [email protected]: Failed to initialize firmware mode controller
01-16 09:54:23.773   955   955 E [email protected]: Wifi HAL start failed
01-16 09:54:23.775  1449  2159 E HalDevMgr: Cannot start IWifi: 9 ()
01-16 09:54:23.775  1449  2159 E WifiVendorHal: Failed to start vendor HAL
01-16 09:54:23.775  1449  2159 E WifiNative: Failed to start vendor HAL
01-16 09:54:23.776  1449  2159 E WifiNative: Failed to start Hal
01-16 09:54:23.776  1449  2159 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle

Thanks man!

Tried but WiFi and hotspot are still broken
But thank you so lucky for looking into it, it would be amazing to get it to work perfectly battery life on LOS is si much better with your kernel

I can still try some stuff, let me know how it goes :)
 

Attachments

  • blu_spark_r80-custom_op8x_5d2cb0ff8.zip
    22 MB · Views: 10

Top Liked Posts

  • 1
    I am having a strange bug and I think it is a problem with this kernel (it happens to me since I updated to version r112). The sound of the notifications is not heard after a few hours. Does it happen to someone else?
    Nope, stop using mods that mess with doze and the likes.
  • 19
    blu_spark_r112 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 13.0.2 + LLD linker
    • makefile: remove some clang13 spam
    • lz4 and lzo fixes
    • zram and zsmalloc updates
    • AnyKernel3 updates (v20210910) and new device asserts by @osm0sis
    • 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 :)
    12
    I had a derp in AK3 stuff, I reuploaded r112, redownload please ;)
    6
    @eng.stk following you since the good old days of nexus 5 . gonna get my 8t tommorow
    and i just found out that youre active here. couldnt be happier
    blu_crew baby 🤗
    8T is a great device, one of my favourites, enjoy!
    3
    Great work @eng.stk !!⚡ I have the phone since Friday and already rocking this kernel :cool:
    You sir, are a man of culture 😁
    2
    @eng.stk following you since the good old days of nexus 5 . gonna get my 8t tommorow
    and i just found out that youre active here. couldnt be happier
  • 69
    DWHxIK

    Kernel features:
    • Build with Google Clang version 13.0.2 + LLD linker
    • 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 300HZ 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 (LZO-RLE default) and with file disabled, LZ4 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 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_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 :)
    24
    blu_spark_r94 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.4 + LLD linker
    • BACKPORT: lib/lzo: implement run-length encoding (zram default now, better compress/speed ratio)
    • BACKPORT: GKI: hwtracing: Add a driver for disabling coresight clocks (backport from Pixel 5, less idle draw)
    • BACKPORT: lz4: fix kernel decompression speed
    • A couple of build improvements
    • Further disable audit
    • defconfig: enable ZSTD
    • Remove some logspam
    • AnyKernel3 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 :)