yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] Timmmmaaahh!:
This should in fact be released immediately alongside the 'program' release as specified in the General Public Licence version 2:

Spoiler content hidden.

Unfortunately it does not surprise us when yet another company fails to do this. Which is even more unfortunate knowing that when these companies release their sources, communities like XDA really push development forward, which in turn is profitable for these companies.

I think it's also to be blamed on the massively complex hierarchic structures of manufacturers that require way too much time to dot the i's and cross the t's before okaying source releases.

Sorry if this strays a bit off topic.
[OnePlus 9 Pro] this.guy.lol:
this work on crydroid or AOSP roms?
[OnePlus 9 Pro] GuyInDogSuit:
This was made from source for OOS, so I wouldn't try it on anything but.
[OnePlus 9 Pro] this.guy.lol:
can you point me to one that is A11 aosp supported?
[OnePlus 9 Pro] GuyInDogSuit:
I don't believe there are any as of yet. There's plenty for A10, but kernel development for Android 11 has been slow, even for OOS. Apparently OnePlus hasn't released an updated source in quite a while now. And things aren't looking good for Android 12, either.

For future reference, when they finally are available, you usually can find kernels and ROMs by going to the OP9 Pro forums, here, and selecting the "Development" filter at the top. The threads usually have a prefix (in this case, "[Kernel]") and the Android version/skin it's released for.
[OnePlus 9 Pro] eng.stk:
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:

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 :)
[OnePlus 9 Pro] l_mike:
I am on c.38, so I won't install, but I wanted to say that I really appreciate your commitment here.
[OnePlus 9 Pro] Pipould:
Hi :) Been using OP7 with bluspark for long time, now having a OP9Pro... Can people relate the battery gain idle / on screen vs stock ? :) OOS11 ofc :)
[OnePlus 9 Pro] Kleinblaar:
Hi mate,

Thanks for creating this great kernel. I am trying to patch the kernel to add some additional bits. I have not done this on a clang compiled kernel before so I am stuck and can't compile it from the source git. I am sure I am missing something silly but ca't find a good guide on setting up the vm to compile so get multiple errors where the compiler don't support this or that.

Would you be so kind as to jot down the steps from a fresh debian install or what your flavor of linux is to get the necessary dependencies set up, clone the android 10 and android 11 kernel branches to compiling them as is.

This will cover all the bits I need to then just add the patch and compile the kernel.

Regards
[OnePlus 9 Pro] GuyInDogSuit:
Battery life is excellent for me, but then again, it depends on what you've got installed, customized/modded, your SoT, or usage otherwise. In other words, ymmv.
[OnePlus 9 Pro] Pipould:
Thanks, I indeed see your concern in giving numbers out :) I was hoping for like an idle / screen on battery drain in % before & after, but even on stock OOS and not having any optimisation for accubattery, it's pretty flaky... I could assume I'm around 10-15% screen on (no games) and 0.6 - 1.5% screen off with Wifi 6.
[OnePlus 9 Pro] eng.stk:
Flash it and test it yourself, all the rest is subjective.
[OnePlus 9 Pro] Kleinblaar:
I tried using proton-clan to compile blu_spark A10 and get error: the clang compiler does not support '-mcpu=cortex-a76.cortex-a55'

Not sure what I am missing
[OnePlus 9 Pro] Kleinblaar:
And if I try a11 compile I get

unknown warning option '-Wno-unused-but-set-variable'; did you mean '-Wno-unused-const-variable'? [-Werror,-Wunknown-warning-option]
[OnePlus 9 Pro] gesichterparty:
R52 feels not better than r49. 9pro with 10.10. R49 was not so much hungry for the battery. Can i downgrade just with dirtyflash r49?
[OnePlus 9 Pro] tathagatab:
Why do you need to downgrade? Is 52 worse than 49?
[OnePlus 9 Pro] gesichterparty:
Yes. I feel that 52 need more battery.
[OnePlus 9 Pro] eugenechiuu:
Have you used for few days already to optimise?

In my case, r52 seems better optimised for 10.10 compared to r49 hmm.. unless it's placebo effect
[OnePlus 9 Pro] xer0o0x:
Hello,

can I use this kernel for the OnePlus 9RT?

greez
[OnePlus 9 Pro] JohnTheFarm3r:
OP9/Pro​
[OnePlus 9 Pro] Atul Menon:
No
[OnePlus 9 Pro] tathagatab:
Of course you can. It's your phone and you have every right to brick it.
[OnePlus 9 Pro] mattie_49:
V52 def fixed my issue of not getting Gmail pushed to device automatically. On latest 11.2.10.10 build op9 global. Fantastic kernel although I wish someone with some knowledge of kernel settings through fkm. I'm blind af in that area.

After some reading in fkm I found battery optimizations and underclocks!! Yay
[OnePlus 9 Pro] infamousvincci:
You went back to oos11? What happened?
[OnePlus 9 Pro] eugenechiuu:
Mind sharing your settings in FKM?
[OnePlus 9 Pro] mattie_49:
Newest build from OnePlus was still bad. Many issues . Flashed cr-droid didn't care for it. Used msm tool and just staying in the sweet spot till further development.
[OnePlus 9 Pro] mattie_49:
I Uc'd everything by 50%. Installed Naptime. Zero issues ,our phones and way juiced for most people's needs. Fkm bottom right battery life tips.
[OnePlus 9 Pro] Gamlerr:
is it worth to switch from omega kernel to blu spark? Because omega stopped with develop or has r52 problems with oss11 10.10
[OnePlus 9 Pro] GuyInDogSuit:
Sure. It's your phone. Doesn't hurt to test drive a kernel for a for a week or two to see if it is satisfactory. All you need to do is back up your stock boot and vendor_boot images (they're labeled "_a" and "_b") prior to flashing this, in case you decide it's not for you.

While Omega was a bit "bleeding edge" and had a lot of features that that other kernels didn't have, this one is closer to stock, but with some needed tweaks and improvements. It doesn't have all those bells and whistles, but for most people, it works great.
[OnePlus 9 Pro] tathagatab:
Also the dtbo partition.
[OnePlus 9 Pro] Gamlerr:
I want first go back to stock and then flash blu spark. Is it enough when I flash boot.img and system.img?
[OnePlus 9 Pro] MrSteelX:
the quickest way would be to just flash your rom again.
[OnePlus 9 Pro] RheinPirat:
But this is a ultima ratio solution. Or do you re-install windows when something is wrong? Probably not. - I hate such answers!

He askes something else. And I also would like to know what Gamlerr asked for.
[OnePlus 9 Pro] MrSteelX:
Clearly you don't understand how to read and assume that flashing rom wipes phone. It doesn't remove the data.
[OnePlus 9 Pro] JohnTheFarm3r:
Flashing ROM would just clean "replace" the system files while keeping user data intact, that means no wipe, no reset or similar, so you keep your phone as it is. It's also called a "dirty" flash, so you're not doing a wipe.
[OnePlus 9 Pro] bea231:
Hi, is it possible to enable support for TTL spoofing in next release?

# arch/arm64/configs/blu_spark_defconfig
CONFIG_NETFILTER_XT_TARGET_HL=on
[OnePlus 9 Pro] toolhas4degrees:
Omega only changed boot.img you can flash this over Omega. To go back to stock from this you need to flash rom zip. If you try arter kernel you need to backup dbto, boot and vendor boot.imgs and flash via fastboot to go back to stock.

I've been running this kernel for a year and works well
[OnePlus 9 Pro] break.cold:
Which version of blu_spark you are using? And what setting's you use to config the kernel. Because I used blu_spark perviously on OOS it drain battery quickly and for some reason my wifi became slow after flashing blu_spark kernel compare to arter kernel.
[OnePlus 9 Pro] toolhas4degrees:
Pm if you want my settings nothing special, but with every new kernel flash you need to let it settle for 2 to 3 days before complaining about battery life.
[OnePlus 9 Pro] break.cold:
I did, I used blu_spark at least 8 to 9 days.
[OnePlus 9 Pro] loulondono:
Do I need to do the whole fastboot boot magisk patched image thing again after flashing the kernel, or does it not delete root? I haven't installed twrp and I can't really be arsed, I just got this device and after ~3 years of playing around with my 6t I've become pretty burnt out so I'm not looking to be flashing a whole bunch or playing with custom ROMs (at least until android 12 comes into full effect, can't stand the new OOS)
[OnePlus 9 Pro] eng.stk:
If

If you're already on a stock rooted device, it will keep root.

Keep in mind I only have builds for OOS 11
[OnePlus 9 Pro] galaxys:
Happy New Year's blu_spark kernel!🎉🎇🥂🍻🌠
[OnePlus 9 Pro] loulondono:
Yes I'm on 11.2.10.10, I'm actually a big fan of the A11 version of oxygen os, got way more features than on my old phone. I'll be on stock for the foreseeable future. Thanks for the quick response
[OnePlus 9 Pro] loulondono:
Hey, I just started playing some music with my wireless earbuds, and noticed that it will have a tiny stutter whenever I locked the phone. I reset all my Bluetooth settings to default (I was changing them at the time) uninstalled viper and it persisted. Before root I would have definitely noticed this as it drives me insane, and I don't think it was happening after root either. Is it possible for the kernel to be causing this? If it is, how exactly do I flash my backups? Ik it sounds minor but it bugs me an awful lot and I listen to a lot of music throughout my day
[OnePlus 9 Pro] mattie_49:
How did you install viper if you don't mind? I've tried till I'm blue in the face to get driver's installed . So I went to James DSP. But I like viper better
[OnePlus 9 Pro] loulondono:
Magisk, installed the modules (the standard on, first one you see) then reboot. When you open the app it prompts you to install drivers or something and reboot, I had to do the above twice for it to work
[OnePlus 9 Pro] GuyInDogSuit:
Not sure if this is related, but I had a similar problem when I was rooted (not just with this kernel). My audio would sometimes stutter ridiculously and shutting off the car and opening the door to turn the stereo off, would fix it, sometimes. I haven't had that issue since going back to stock T-Mobile non-rooted. Food for thought, I suppose.
[OnePlus 9 Pro] Gamlerr:
install JamesDSP and keep it, after that install viper4android and you can use it without driver issue
[OnePlus 9 Pro] tathagatab:
This is the method that works for me on OOS 11. I copied this some time ago from someone else's post. I have lost track of the original post. Pasting here with apologies to the author.

This is the procedure I do. I used RootExplorer to modify the file. Reboot when it says. This is important.

uninstall any previous versions of V4A and other audio mods

install Audio Modification Library from the Magisk repository; reboot

install Audio Compatibility Patch from the Magisk repository; reboot

install V4A v2.7.2.1 from local storage if you have the zip file or from the Magisk repository; do not reboot

open the V4A application, grant root access and follow the prompts to install the Magisk module; reboot

open V4A and go to Settings and enable Legacy Mode

modify the following file: /data/adb/modules/Viper4Android/post-fs.sh

add the following lines to the end of post-fs.sh

magiskpolicy --live 'allow audioserver audioserver_tmpfs file { read write execute }'

magiskpolicy --live 'allow audioserver system_file file { execmod }'

magiskpolicy --live 'allow mediaserver mediaserver_tmpfs file { read write execute }'

magiskpolicy --live 'allow mediaserver system_file file { execmod }'

magiskpolicy --live 'allow audioserver unlabeled file { read write execute open getattr }'

magiskpolicy --live 'allow hal_audio_default hal_audio_default process { execmem }'

magiskpolicy --live 'allow hal_audio_default hal_audio_default_tmpfs file { execute }'

magiskpolicy --live 'allow hal_audio_default audio_data_file dir { search }'

magiskpolicy --live 'allow app app_data_file file { execute_no_trans }'

magiskpolicy --live 'allow mtk_hal_audio mtk_hal_audio_tmpfs file { execute }’

open V4A and go to Settings and disable Legacy Mode; reboot

open V4A and go to Settings and enable Legacy Mode.
[OnePlus 9 Pro] mattie_49:
When I go back into viper after trying to install drives following guide. I can't ever get to settings /legacy mode menu on viper. Keeps telling me no driver's installed.
[OnePlus 9 Pro] loulondono:
I don't remember doing this previously, but turning off lock sounds fixed it. Not that it matters, I'm quite pissed off at the slow performance of the phone in general so I'm actually going to just install a custom ROM and see if it fairs better without so much oneplus crammed inside
[OnePlus 9 Pro] osm0sis:
Can someone still on OOS11 give me the output of:

su -c "find /sys | grep /hbm"

?
[OnePlus 9 Pro] toolhas4degrees:
:/ $ su -c "find /sys | grep /hbm"

/sys/devices/platform/soc/ae00000.qcom,mdss_mdp/drm/card0/card0-DSI-2/hbm_brightness

/sys/devices/platform/soc/ae00000.qcom,mdss_mdp/drm/card0/card0-DSI-2/hbm

/sys/devices/platform/soc/ae00000.qcom,mdss_mdp/drm/card0/card0-DSI-1/hbm_brightness

/sys/devices/platform/soc/ae00000.qcom,mdss_mdp/drm/card0/card0-DSI-1/hbm

/sys/devices/platform/soc/ae00000.qcom,mdss_mdp/drm/card0/card0-Virtual-1/hbm_brightness

/sys/devices/platform/soc/ae00000.qcom,mdss_mdp/drm/card0/card0-Virtual-1/hbm

/sys/devices/platform/soc/ae00000.qcom,mdss_mdp/drm/card0/card0-DP-1/hbm_brightness

/sys/devices/platform/soc/ae00000.qcom,mdss_mdp/drm/card0/card0-DP-1/hbm

:/ $
[OnePlus 9 Pro] osm0sis:
Great! Thanks!

What about:

su -c "cat /sys/class/drm/card0-DSI-1/hbm"

?
[OnePlus 9 Pro] toolhas4degrees:
:/ $ su -c "cat /sys/class/drm/card0-DSI-1/hbm"

hbm mode = 0

0--hbm mode(off)

1--hbm mode(XX)

2--hbm mode(XX)

3--hbm mode(XX)

4--hbm mode(XX)

5--hbm mode(670)

:/ $
[OnePlus 9 Pro] osm0sis:
Perfect! And finally, does:

su -c "echo 5 > sys/class/drm/card0-DSI-1/hbm"

enable hbm? If not try the same command but -2 on the directory name instead of -1. echo 0 instead of 5 to turn it off again. 🙂
[OnePlus 9 Pro] eng.stk:
The path for HBM on the device is /sys/class/drm/card0-DSI-1/hbm (0-5 will work)
[OnePlus 9 Pro] osm0sis:
Perfect. Thanks for confirming. OOS12 changes this completely (it's now /sys/kernel/oplus_display/hbm 0|1 technically, but 5 also works to enable), so it'll be a little trickier to support, but I'll see if I can figure it out myself when I've got a bit more time to poke around in FKM's Java code.
[OnePlus 9 Pro] eng.stk:
Yeha I already have passsed it down to franco quite a while ago.

Those should be symlinks, you don't have anything on drm?
[OnePlus 9 Pro] osm0sis:
Yeah nah, on OOS12 it doesn't link up anywhere in drm anymore.
[OnePlus 9 Pro] NotCat_:
*Deleted*
[OnePlus 9 Pro] eng.stk:
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:

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 :)
[OnePlus 9 Pro] moosefist:
su -c "echo 5 > /sys/class/drm/card0-DSI-1/hbm"

This does enable hbm, but you were missing the /slash before /sys/
[OnePlus 9 Pro] mattie_49:
Stoked that your moving on to A12 !! Good deal
[OnePlus 9 Pro] eng.stk:
I'm not lol

At least at the moment. But eventually if we want to keep updated, we will have to I guess.

But not before I have source to take a look 😅
[OnePlus 9 Pro] HaKy5:
Will it be possible to lower the cpu voltage in the future?
[OnePlus 9 Pro] toolhas4degrees:
Yeah not feeling the a12 oos cos merger either. Oppo is terrible with source updates. That why omega dev quit.
[OnePlus 9 Pro] toolhas4degrees:
In the last 2 or three updates even though I set all io schedulers to bfq, it resets 2 to mq deadline after reboot and have to manually toggle them back to bfq each time.
[OnePlus 9 Pro] eng.stk:
ofc, deadline is default.

You need to set that later on boot.
[OnePlus 9 Pro] toolhas4degrees:
It was set on boot to bfq.for all in Franco. And every reboot 2 of them change back to deadline regardless
[OnePlus 9 Pro] eng.stk:
Doesn't mean anything.

Later on boot is later on boot. 45 60 secs
[OnePlus 9 Pro] toolhas4degrees:
Ok yeah it's boot delay. But it's more like 5 minutes now. Fkm service is 0 seconds.

Is this controlled in the kernel or a lag from processes in the kernel startup? Or is it fkm or zygisk magisk issues?

Like I said never had this long of a delay until 3 or 4 builds ago I think 52 was the last one that didn't.
[OnePlus 9 Pro] eng.stk:
There's no kernel changes related to that, always has been the same.

There's a 30 sec delay tagged to boot events, that could be influenced by several things running on boot and taking time.

You need to add a bigger delay to fkm service, nothing new here.
[OnePlus 9 Pro] Flying Fox:
First of all, many thanks for the development of this kernel. It was already my favourite on my Oneplus 6. Flashed for the first time after a long time on my Onplus 9 pro (via EX kernel manager). Then no more settings changed. But then, out of old habit, I deleted the flar kernel and installed the FKM. No changes made here either. By the way, I am on the latest A11 firmware EU. A few Magisk modules like Viper4Android, otherwise nothing spectacular.

Now to the issue. For the first time (overnight) there was probably a random reboot, but into recovery mode (original, I don't have TWRP). Reboot was not possible. Only after flashing the boot and vendor partition via fastboot.

(I am glad that I made a backup. Normally I would have flashed dirty if there was a problem. So for everyone, a backup of the two partitions pays off in any case).

My question is whether this can be related to the kernel. I think so, see screenshot. Oh well, concerns your last update and the first I flashed.

So, now I have to go, I think my info is complete. If I'm the only one, then there's probably something wrong with my phone. But I have no mods, no custom rom, nada.

Kind regards
[OnePlus 9 Pro] toolhas4degrees:
Pull your stock root boot imgand reflash it in fastboot. Then use fkm to flash bluspark kernel. If you are using other Magisk or xposed mods check to see if they are causing issues.

Also if you tried arter kernel you will need to flash dbto img vendor_boot img and boot img in fastboot from stock firmware before using this kernel
[OnePlus 9 Pro] GuyInDogSuit:
Flashing the current ROM again is also an option, but it's best to always do what 4degrees mentioned, to extract those files from every ROM update, for safety reasons.
[OnePlus 9 Pro] zeraora:
Dear blogger, I now try to compile your code on Ubuntu 20, but it always fails too times. I wonder if you can give me some advice?

Ubuntu20. 04, gcc9, aarch64-linux-android-4.9 (this is from your makefile), but there are always various errors in the kernel source code compilation (make phase) of oneplus9 (similar to prohibiting float, unknown type name 'in_addr_t')

This afflicts me because I don't know why. May it be a compiler and environment version problem?

By the way, what platform, environment and cross compiler links do you cross compile?
[OnePlus 9 Pro] zeraora:
Thank you, blogger. What is your platform, environment and cross compiler link for cross compilation?
[OnePlus 9 Pro] GuyInDogSuit:
"blogger"?
[OnePlus 9 Pro] eng.stk:
blu_spark_r56 release (A11)

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:

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 :)[/list]
[OnePlus 9 Pro] Moka UA:
Works with Android version 12??

C44
[OnePlus 9 Pro] JWnSC:
So magisk v23 won't work with this updated kernel?
[OnePlus 9 Pro] mattie_49:
Don't believe this has anything to do with it. Yes it will work with magisk 23. That's the magisk version for A 11 which is where this kernel is at.
[OnePlus 9 Pro] mattie_49:
C-44 kernel source released today !! Yay
[OnePlus 9 Pro] rejectedjs:
You're lying! It's too late for an April Fools joke!!

Did they really release kernel sources?? We're gonna get OOS12 kernels soon? That makes me so happy
[OnePlus 9 Pro] Flasher8:
Weird, did u test with YouTube vanced ? Just happened today when I flashed Blu. I'm using vanced everyday 😅😅😅 the log doesn't shown anything?
[OnePlus 9 Pro] eng.stk:
Charging is totally stock and there were changes on the latest OOS 11.2.6.6 sourcedrop to match the ROM changes.

If you're still in OOS 11.2.5.5 there could be "issues".
[OnePlus 9 Pro] ginbo:
@eng.stk I am very happy, thank you
[OnePlus 9 Pro] toolhas4degrees:
@eng.stk is the hbm button in qs not active in the kernel yet?

On latest update eu 11.2.6.6 LE15BA
[OnePlus 9 Pro] eng.stk:
Yes and it's similar to OP8, seems like the app isn't' picking it up because reasons.

Wait for FKM updates.
[OnePlus 9 Pro] lollettu:
How did you changed the grid rows and columns?
[OnePlus 9 Pro] osm0sis:
Weird, HBM works on 8T since I pestered Franco to add it. Is it a different sysfs path on 8 and 9? I can see about adding it myself now that I've seen him do it for 8T in the app code.

Edit: Franco actually added 8, 8Pro and 8T all at once so they should all work already I think? Looks like he does it by device whitelist rather than tuneable path, so that explains 9 Series not working yet. Nothing kernel-side to be done about it.
[OnePlus 9 Pro] eng.stk:
Yep, he's already on it ;)
[OnePlus 9 Pro] toolhas4degrees:
Substratum themes. Pm if you need a link to the one I use
[OnePlus 9 Pro] djsubterrain:
If you have a problem with him it should be taken elsewhere and not vented as harassment in his own post. Good with the mods if you keep this up.
[OnePlus 9 Pro] rakib.abdullah:
Can it support j6 2018??
[OnePlus 9 Pro] pyry666:
I am sorry. Had a bad day. My behavior was not correct. I a apologize
[OnePlus 9 Pro] Timmmmaaahh!:
[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
[OnePlus 9 Pro] Atul Menon:
Are you blind🤐
[OnePlus 9 Pro] mattie_49:
My bud flashed this on op9 and reports having no issues. I guess the op9 and pro and unified like the 8 was?
[OnePlus 9 Pro] osm0sis:
Yeah that's listed in the thread title. 9R is another thing though, it's basically just a renamed 8T, hdr_v2 boot.img and all.
[OnePlus 9 Pro] mattie_49:
Ok last question before I flash this. I see in op it supports wakelock blocking. Does it also support k-cal color's or is it planned in the future. ? Global op9 unlocked
[OnePlus 9 Pro] Hot-Proton:
Nice to see you here @eng.stk .