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

[KERNEL] [blu_spark r225 unified OP5/5T] [A10 unified]

Search This thread

sjamie

Senior Member
Aug 6, 2011
8,587
4,324
How you are not able to fix the call recording issue, I dirty flashed oos but it's not working. At least you should give us a work around. Never experienced such issues while flashing any kernel. Sorry but your answer is not acceptable @eng.stk
Please remember devs spend their own time creating ROMs, mods, and tweaks and often share them here on XDA for FREE! They owe us nothing. You are not forced to use anything you don't fully love or enjoy.
 

razafa

New member
Jul 14, 2014
4
0
Please remember devs spend their own time creating ROMs, mods, and tweaks and often share them here on XDA for FREE! They owe us nothing. You are not forced to use anything you don't fully love or enjoy.
I agree with you and in years first time i commented because it's breaking something which don't have an easy fix. Even after clean flash stock oos, call recording is not working. Definitely something is broke after this kernel and he must fix it
 

eng.stk

Senior Member
Mar 29, 2011
6,937
59,545
OnePlus 5T
OnePlus 6
I agree with you and in years first time i commented because it's breaking something which don't have an easy fix. Even after clean flash stock oos, call recording is not working. Definitely something is broke after this kernel and he must fix it
Ok that's enough.
I already answered this months ago.
I don't have any changes to make it work or not, source is totally stock on this regard.
I work with the source that is public.
If you're so sure and it's important to you, fix it yourself. Or use whatever kernel solution that works for you.
There is no must here, nobody owes you anything. You were already called out, learn some manners.
For a legacy device still having kernel updates consider yourself lucky.
Continue pushing the rudeness and that may change rapidly in the future.

Move along.
 

sjamie

Senior Member
Aug 6, 2011
8,587
4,324
I agree with you and in years first time i commented because it's breaking something which don't have an easy fix. Even after clean flash stock oos, call recording is not working. Definitely something is broke after this kernel and he must fix it
One of the quickest ways to ruin the development community is to tell a Dev what he or she "must" or "must not" do (for free). If there has not be an exchange of money, there should not be an expectation of service or support.
 
  • Like
Reactions: Drhedphuk

razafa

New member
Jul 14, 2014
4
0
Ok that's enough.
I already answered this months ago.
I don't have any changes to make it work or not, source is totally stock on this regard.
I work with the source that is public.
If you're so sure and it's important to you, fix it yourself. Or use whatever kernel solution that works for you.
There is no must here, nobody owes you anything. You were already called out, learn some manners.
For a legacy device still having kernel updates consider yourself lucky.
Continue pushing the rudeness and that may change rapidly in the future.

Move along.
I would have moved on if flashing stock solved this issue but I am stuck as after clean flashing oos also call recording is not functional. So I am stuck and you are the only hope as this kernel has broke something which can not be fixed otherwise. Sorry if you felt I was rude but there is no choice left for me
One of the quickest ways to ruin the development community is to tell a Dev what he or she "must" or "must not" do (for free). If there has not be an exchange of money, there should not be an expectation of service or supportbro
 

razafa

New member
Jul 14, 2014
4
0
I'm supporting devs since nexus 4 days and I own all oneplus devices and most of them either have custom roms or kernel but never ever faced issue like this if it can not be fixed with stock oos then my friend there is something wrong with it. I appreciate your hard work but Sorry @eng.stk
 

sjamie

Senior Member
Aug 6, 2011
8,587
4,324
I would have moved on if flashing stock solved this issue but I am stuck as after clean flashing oos also call recording is not functional. So I am stuck and you are the only hope as this kernel has broke something which can not be fixed otherwise. Sorry if you felt I was rude but there is no choice left for me
If everything was working properly before you flashed this kernel and clean flashing the ROM doesn't fix what you want, consider formatting your Data partition and reflash the ROM. This would remove all residual effects of the kernel.
 
  • Like
Reactions: Michael R

niklas389

Senior Member
Mar 19, 2013
120
121
Hannover
onedrive.live.com
OnePlus 8T
How you are not able to fix the call recording issue, I dirty flashed oos but it's not working. At least you should give us a work around. Never experienced such issues while flashing any kernel. Sorry but your answer is not acceptable @eng.stk
Well no one forces you to use his kernel. And by the way speaking like this to someone who gives so much for the community (for free) is unacceptable - maybe think about that for a second.
 

eng.stk

Senior Member
Mar 29, 2011
6,937
59,545
OnePlus 5T
OnePlus 6
blu_spark_r225 release

New build is up!

A10 builds are unified, good to go on 5/5T.
You can use FKM download kernel feature, just import the links bellow in the app :highfive:
FKM download configs: oos


Changelog:
  • tracing: Add entries from msm8998-coresight (tentative less idle draw)
  • efi/libstub/arm64: link stub lib.a conditionally
  • wireguard updates (v1.0.20210606)
  • AnyKernel3 updates (v20210721)
  • For root, stable Magisk 23.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 :)
 
Last edited:

sjamie

Senior Member
Aug 6, 2011
8,587
4,324
blu_spark_r225 release

New build is up!

A10 builds are unified, good to go on 5/5T.
You can use FKM download kernel feature, just import the links bellow in the app :highfive:
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 :)
Thank you for your work and effort! #FirstClass
 
  • Like
Reactions: eng.stk

harshdoshi25

Senior Member
Apr 23, 2011
525
147
27
Kolkata
www.instagram.com
I'm supporting devs since nexus 4 days and I own all oneplus devices and most of them either have custom roms or kernel but never ever faced issue like this if it can not be fixed with stock oos then my friend there is something wrong with it. I appreciate your hard work but Sorry @eng.stk

I understand call recording is breaking for you after installing this kernel. It's the same with me. However, if clean flashing oos/restoring kernel backup/flashing boot isn't reversing the process for you, then the problem is not with the kernel but something else. Maybe some magisk module. Gcam and it's dotfix breaks call recording for most people. Look into that.

P.S. Stop acting entitled if you want support from people here.
 
  • Like
Reactions: razafa

lulli1

Senior Member
Dec 12, 2011
1,454
827
One question regarding the blue spark TWRP recovery. I'm decrypted without any lockscreen or other security setting. When I boot to recovery version 9.110 all is fine. But as soon as I flash the latest one 9.116 over it and reboot, I get asked for my password to enter the TWRP. When I enter a password that I used to use in the past it decrypts and I can enter the 9.116 TWRP. Why is that, please? And what can I do to boot to recovery without being asked for a password on 9.116 version as well?
 

sjamie

Senior Member
Aug 6, 2011
8,587
4,324
One question regarding the blue spark TWRP recovery. I'm decrypted without any lockscreen or other security setting. When I boot to recovery version 9.110 all is fine. But as soon as I flash the latest one 9.116 over it and reboot, I get asked for my password to enter the TWRP. When I enter a password that I used to use in the past it decrypts and I can enter the 9.116 TWRP. Why is that, please? And what can I do to boot to recovery without being asked for a password on 9.116 version as well?
I believe you may need to format your Data partition to remove the password requirement.
 

lulli1

Senior Member
Dec 12, 2011
1,454
827
I believe you may need to format your Data partition to remove the password requirement.
Thanks but that's not what I wanted to here 😂. I always flashed no verity after last data format. What could have brought back encryption to my device? In settings it says device is not encrypted.
 

Attachments

  • Screenshot_20210801-165213375.jpg
    Screenshot_20210801-165213375.jpg
    156.7 KB · Views: 74

Romanelo

Member
Jun 4, 2017
20
1
blu_spark_r225 release

New build is up!

A10 builds are unified, good to go on 5/5T.
You can use FKM download kernel feature, just import the links bellow in the app :highfive:
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 :)
thank you very much for the kernel, but still I would like to have a recording of conversations, I remember the earliest kernel builds and it was also impossible to record a conversation in them, unlike the stock kernel. Anyway thank you for supporting this kernel.
 

sjamie

Senior Member
Aug 6, 2011
8,587
4,324
thank you very much for the kernel, but still I would like to have a recording of conversations, I remember the earliest kernel builds and it was also impossible to record a conversation in them, unlike the stock kernel. Anyway thank you for supporting this kernel.
Use this app for to produce perfect call recordings on the OP5/T. I've been using it for YEARS!

 
  • Like
Reactions: Michael R

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Stop using the kernel in custom ROMs.
    Builds are for OOS only.
  • 248
    DWHxIK

    Kernel features:
    • Build with custom toolchain blu_gcc-11.1 (cortex-a73.cortex-a53 targeted, build from gcc-11.1.0 snapshot with latest bleeding edge components)
    • Full -O2 build with device and target flags enhanced, linaro build improvements, etc
    • Less is more: stockish OP5 builds based on OnePlusOSS/android_kernel_oneplus_msm8998
    • 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
    • Several CPU Governors (blu_active modded own governor by default - fastlane mode available!)
    • No OC, use 300HZ kernel timer frequency
    • msm_performance input boost toggle on/off (enabled by default), tweaked cpu_boost driver
    • Enhanced TCP methods (westwood is default), Network and Wifi tweaks and updated drivers
    • Several I/O control tweaks, added schedulers FIOPS and ZEN v2 is default, tweaked and upstreamed filesystems (F2FS, ExFAT, NTFS, CIFS & NFS)
    • Removed verify and doesn't force encryption, patched SafetyNet flags to pass CTS
    • Stock thermal driver by default (custom tunables available for ROMs with no thermal daemon)
    • Disabled hotplug, also on low battery levels (CTL and BCL)
    • Optimized crypto routines
    • ZRAM Swap (LZ4) and adaptive LMK on by default
    • Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
    • KGSL fixes and reworked GPU driver (goes to idle @ 180MHz)
    • adrenoboost enabled by default at low level
    • KCAL - Advanced color control for Qualcomm MDSS v2 (RGB calibration and post-processing features)
    • KLAPSE support (v5.0)
    • Backlight min brightness option
    • USB Fast Charge (USB mode up to 900mA with MTP on)
    • Battery/Notification LED control
    • FS fsync toggle on/off
    • Wakelock blockers available
    • zx2c4's 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
    Extras download location
    (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.


    OnePlus 5 development unit donated by OnePlus. Big shouts to them :)
    Very proud of being on the OnePlus Developer Program, special thanks to Adam K. for being such a supportive person.


    Contributors
    eng.stk
    Source Code: https://github.com/engstk/op5
    100
    blu_spark r8

    All right crew!

    First build of your favorite kernel is up. Wicked!

    Just got an OP5 developer unit yesterday from Oneplus, so today you already have a fully featured blu_spark build.
    Most of the features you are used to from blu_spark on OP3/3T and others are in, this first build was compiled with Linaro GCC 5.4 (blu_naro 7.1 build still need some work).
    Pretty happy with the stable and smooth base, next weeks will bring more of the usual goodies, there's still lot's of room for improvements :fingers-crossed:

    blu_spark_r8-oos_op5_49e4692.zip

    • First public build (check OP and github for details)

    Keep it real, keep it true, keep it blu :highfive:

    Keep in mind: I will give no active support for custom ROMs (including OOS based ones) or OB.
    Meaning, if using anything besides stock and stable OOS don't bother posting about it.
    I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).
    Don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
    Custom build isn't compatible with EAS stuff.
    Also don't go spam and bug reporting on ROM threads if using this.


    pp-acceptance-small.png

    If you like my work, donations are always welcome.
    Don't forget to hit thanks and rate the thread nicely, it's free ;)
    57
    blu_spark extras v9.110

    All right crew!

    Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-9.0 branch (including more recent upstream than official TWRP) and some specific device fixes.

    Fully synced with TWRP 3.3.1+, name changing to reflect base 9.version, full compatible with Pie stuff (you need Pie fw also) and A10 custom ROMs will work also (OMNI tested)
    TWRP blu_spark edition is unified, works for both OP5/5T.
    Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.
    This build is treble ready, allowing /vendor partition operations. If you don't use treble enabled ROMs, ignore any vendor errors that may appear, TWRP will work just fine.


    twrp-3.3.1-x_blu_spark_v9.110_treble-op5_op5t

    • build: TWRP 3.31-x | blu_spark v9.110
    • Supports Android 10
    • /sbin should come first in the linker search path
    • Move decryption error from logerror to loginfo
    • Encryption: don't try wrapped key if not needed
    • Removing fake error: E: recv error on uevent
    • bootable: read all asserts in case there are more than one.
    • Prevent errors caused by /data/per_boot/
    • crypto: add some missing newlines
    • Complete overhaul of Dutch translation:
    • recovery: wipe bootloader message from index 0 when using custom offsets
    • android-5.1: use char constructor for default on c++ streams
    • recovery: Move bldrmsg offset symbols to bootloader_message.cpp
    • Encryption: try wrapped key also for device without metadata support
    • ldconfig: add /sbin to search.paths
    • Device specific changes here




    Wakelock blocker info and example script


    I'm just sharing my personal mods since people asked, meaning no support will be given (don't bother post about it).
    If your cat get's on fire you're on your own ;p


    No mirrors please
    If you like my work, donations are always welcome.
    Don't forget to hit thanks and rate the thread nicely, it's free ;)
    56
    blu_spark r30

    All right crew!

    New build is up :highfive:
    Also take a look to the rest of blu_spark v43 extras to get some nice and useful additions to the kernel.

    This build features latest blu goodies and new wakelock blocker interface by boeffla, build with latest blu_naro-7.2 :good:
    With the new wakelock block system you can add any wakelock source you want, works like this: you can edit /sys/class/misc/boeffla_wakelock_blocker/wakelock_blocker and add the wakelock name in there to block it (list separated by ';')
    If you want to survive reboots, you can use a script (check the attached example inside the zip). Just copy your script to /magisk/.core/post-fs-data.d or /su/su.d, depending on root option you use ( don't forget to set the file permission 777)
    You can get more info about it here. Because this is powerful and can bring potentially derps if you choose to block unknown stuff, I will give no support if you choose to use any wl blocking (which I didn't before anyway).


    blu_spark_r30-oos_op5_28565f7.zip
    blu_spark_r30-custom_op5_28aae04.zip

    • build: use newest and improved blu_naro-7.2, build from developer snapshot Linaro GCC 7.2-2017.09, with updated components and improvements/fixes
    • blu_active: handle error for module load fail
    • defconfig: enable boeffla wakelock blocker
    • boeffla_wl_blocker: add generic wakelock blocker driver v1.0.0, update to wakelock blocker driver v1.0.1, update to wakelock blocker driver v1.1.0
    • boeffla_wl_blocker: don't block wakelocks by default
    • Revert singular wakelock block
    • Revert su expose workarounds
    • DASH: spoof normal usb fastcharge into android-7.1 (custom only)

    Keep it real, keep it true, keep it blu :highfive:

    Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
    Meaning, if using anything besides stock and stable OOS don't bother posting about it.
    I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).
    Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
    Also don't go spam and bug reporting on ROM threads if using this.


    pp-acceptance-small.png

    If you like my work, donations are always welcome.
    Don't forget to hit thanks and rate the thread nicely, it's free ;)
    48
    Merry Christmas for all the blu_crew :highfive: