yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] GuyInDogSuit:
I tried to flash this in FKM. I get the error "Unsupported device. Aborting...."

My OP9P is a T-Mobile on LE2127 on 11.2.4.4.LE5ACB. afaik that's stock OOS, so I'm confused as to what the issue is.
[OnePlus 9 Pro] osm0sis:
It doesn't have the variant names for carrier versions in the AK3 device check yet. I sent the full list I'm aware of to eng.stk the other day so should be in the next release. 🙂
[OnePlus 9 Pro] mattie_49:
This truth my friend. Why I'm posting a happy dance post 😂
[OnePlus 9 Pro] rejectedjs:
Do you have a link to the reveal?
[OnePlus 9 Pro] mattie_49:
GitHub - OnePlusOSS/android_kernel_oneplus_sm8350 at oneplus/SM8350_S_12.0_9Pro

Contribute to OnePlusOSS/android_kernel_oneplus_sm8350 development by creating an account on GitHub.

github.com
[OnePlus 9 Pro] eng.stk:
And it's broken and also incomplete!! Yay
[OnePlus 9 Pro] mattie_49:
Just like their new oos.
[OnePlus 9 Pro] rejectedjs:
Damn that's really unfortunate. Is it bound to stay that way or is it par for the course for it to improve later on?

It just seems beyond silly to make the kernel open source yet incomplete for anyone to actually utilize the git in the first place
[OnePlus 9 Pro] eng.stk:
There's plenty of stuff to fix in order to get things in working state.

Several drivers are missing and/or half done also.

After some hours I have a half done/half broken booting kernel, there's hope but it ain't looking great
[OnePlus 9 Pro] andr01dfr3ak:
I'm trying to get that kernel code OnePlus released to compile and boot on LineageOS, so I think I get your frustration.

I look forward to using your kernel if I go back to OOS 12 though, since it worked great on OOS 11.
[OnePlus 9 Pro] Arcide:
Realme did the same thing for the X2 Pro, releasing crippled sources. I'm just wondering what's in their heads
[OnePlus 9 Pro] eng.stk:
Indeed, I used a couple drivers from one Realme with sm8350 and even those are broken also.

I have some stuff working, some broken and some not available atm

Way far from daily driver :(
[OnePlus 9 Pro] Arcide:
It's like BBK said let's sh*t on people :/
[OnePlus 9 Pro] eng.stk:
Yeah, without proper sources things don't look promising for OOS support.

As I said I managed to boot.

There's a handful of vendor drivers borked, some are missing, drop-ins from other oppo/realme devices some are borked also.

wifi using Open Source drivers I managed to load it, but no service, they seem to be using a heavily modified one so the HAL is picky (with again no source for the wifi driver).

Panel works with several color modes, HZ stuff, advanced smooth, etc etc.

Brightness works fine with auto levels also.

Sounds works fine with full dolby support.

Touch works nicely with offscreen gestures also.

FoD works fine, faster than stock even.

Tri state key and vibration is wonky , works half the times.

Camera works fully both pics and video, all lens.

BT works nicely also, didn't test SIM because I'm not in the mood after several hours working around broken crap.
[OnePlus 9 Pro] GuyInDogSuit:
Wow, that sounds like a massive clusterf*ck of issues to sort out. Do you think there's any hope of a more "complete" source in the future, or would this be the best you could hope for?
[OnePlus 9 Pro] mattie_49:
This was more than I expected from OnePlus. Oppo releases nothing. OnePlus realizes how bad they fumbled with merge and are trying to revert. Who knows
[OnePlus 9 Pro] mattie_49:
We're pulling for you bud. Lots of us. Arter already said he's not touching and I highly doubt kristo is gonna jump back into this madness. Be only A12 custom oos kernel available. Thank you for all your efforts to help development continue for device.
[OnePlus 9 Pro] eng.stk:
Does't matter what the name is, nobody is going to play magic here.

I'm not sure people realize what's happening: unless source is released fully and without major derps, there's not going to be any release from me and the device will go to the back of my drawer.

I don't know if I'm going to get LOS builds, but not being able to properly support stock ROM is a big nono for me (even if OOS 12 is in general crappy af).

As it is, for all of this, I don't feel particular interessed to even pick up the device anymore 😕
[OnePlus 9 Pro] GuyInDogSuit:
Wasn't this already mentioned a couple days ago?
[OnePlus 9 Pro] Atul Menon:
Srry, i was inactive for a few months, just saw it yesterday 🙃
[OnePlus 9 Pro] shadowofdeth:
Works on the standard 9 no worries but happened to KCAL support? It's been a while but I remember back on my 5T this kernel had support for it.

Is there something we can download to make KCAL happen?
[OnePlus 9 Pro] eng.stk:
There's no KCAL for FoD devices with blu_spark, been said several times.
[OnePlus 9 Pro] Badger50:
Thread cleaned! Please let us keep things respectful and on topic. And a friendly reminder as well about XDA Forum Rule 2.3:

Thank you all for your cooperation.

-Regards: Badger50
[OnePlus 9 Pro] metbed:
hey guys, i m new regarding this stuff, may i ask something,

I have really huge problem regarding battery drain issue, and when i use Twitter app the phone getting hot in just several minutes. So is this kernel helpful for these problems?
[OnePlus 9 Pro] toolhas4degrees:
@eng.stk any hope for a 10 pro kernel?
[OnePlus 9 Pro] osm0sis:
Not with OnePlus' "source drops" in their current state.
[OnePlus 9 Pro] eng.stk:
Hey ya :cool:
[OnePlus 9 Pro] gillim74:
Nice a working a12 kernel
[OnePlus 9 Pro] eng.stk:
blu_spark_r91 release (A12 custom)

New build is up (y)

After the ongoing situation with delayed/broken/missing Op kernel sources and given the bloated crap that (C)OOS 12 is, I decided to take a look at custom ROMs.

I'm quite satisfied with the LOS 19.1 builds, so I decided I will support a kernel for custom ROMs.

I tested with lineage-19.1-20220621-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:

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 :)
[OnePlus 9 Pro] gillim74:
Awesome stuff man.thanks
[OnePlus 9 Pro] EtherealRemnant:
crDroid won't work with the kernel that was just posted as crDroid uses OOS11 firmware, not OOS12.
[OnePlus 9 Pro] golfgtiedition30:
Oh silly me. Sorry guys :eek:
[OnePlus 9 Pro] EtherealRemnant:
It's something that is very confusing. I had to go look myself to see if it was an OOS11 or OOS12-based ROM. We have a mix of ROM bases right now and likely will for awhile since OOS12-based ROMs have various issues with the speaker, microphone, and sensors, and some people will want to stick with the more stable OOS11 base for a good while. It should work with StagOS' new build though so I'm thinking about rooting, backing up my partitions, and flashing it myself.
[OnePlus 9 Pro] eng.stk:
Yeah ROM firmware must be A12 since it's a A12 kernel.

Also ROM must have vendor_dlkm support or else won't be compatible.
[OnePlus 9 Pro] gillim74:
Works on a12 bliss will test more roms and post results.works on aospxtended.does not work on ricedroid.
[OnePlus 9 Pro] maxDL:
Works on Nameless A12.1 very well. Testing more.

WOW!!! And work WARP Charge!!! Its amazing!

Spoiler content hidden.
[OnePlus 9 Pro] EtherealRemnant:
Works on StagOS 12.1. 👍
[OnePlus 9 Pro] sbute:
Didn't work for me on OP9 Nameless 12 fw, flashed through FKM.
[OnePlus 9 Pro] darkness4every1:
Works on Namless 12.1 but overheats a lot and battery drains fast
[OnePlus 9 Pro] Reentry310:
Might be worth posting a logcat so OP is able to debug the issue. Personally I am using this kernel on LineageOS 19.1 and I don't have any problems like that.
[OnePlus 9 Pro] darkness4every1:
How can I do that?
[OnePlus 9 Pro] Reentry310:
Here is an XDA article which shows you want you need to do. In that article you are specifically wanting to look at the "System Logs" subheader as that is what is relevant for getting logcat messages. TLDR, Use either ADB or a Logcat reader android app to get your system logs.

https://www.xda-developers.com/how-to-take-logs-android/
[OnePlus 9 Pro] EtherealRemnant:
Gotta say this kernel is working great on StagOS, no complaints.

Also, WireGuard performance is stellar.

Without kernel module activated:

With it activated:

Since my router is an old AC68U, that's about the max it's actually capable of. I actually like WireGuard a lot but I have been very frustrated because for some reason on this device it was performing worse than OpenVPN 128-bit so I stopped using it. Now I can use it again.
[OnePlus 9 Pro] sbute:
Ok with StageOs on OP9
[OnePlus 9 Pro] golfgtiedition30:
So after my initial mistake :eek: I flashed StagOS followed by this great kernel. All good so far cheers dev!! :)
[OnePlus 9 Pro] tathagatab:
This seems to be a meeting place for a number of A12-based ROM users, so I want to ask something offtopic. I hope no one minds.

After the poor review of OOS 12, I decided to stay on OOS 11.2.10.10. But now that there are several alternatives, should I try any of them or should I wait for OOS 13? Does any of the custom A12 ROMs offer anything over OOS 11?
[OnePlus 9 Pro] break.cold:
How is it working out for you RiceDroid rom and blu-spark kernel, performance, smoothness and stability?
[OnePlus 9 Pro] Shooter7889:
So far so good. Only had BluSpark for few hours today but def seems to make what was already great just more great.. Smooth, and battery idle seems great too.
[OnePlus 9 Pro] break.cold:
I tried RiceDroid rom the other day, it's good rom but the problem I faced was audio and mic problem which is available in many other roms too. Because of this reason I'm back to stock OO12.
[OnePlus 9 Pro] darkness4every1:
My wifi is really slow and I have a lot of delay using Bluetooth headphones after I flashed the kernel, battery/ overheating issues still persist.

9 Pro Nameless 12.1
[OnePlus 9 Pro] Stogie87:
Great! Latest bluesparm custom build for A12 works amazing on riceDroid and makes the rom finally smooth.

Big thanks!
[OnePlus 9 Pro] eng.stk:
All normal in LOS.
[OnePlus 9 Pro] JohnTheFarm3r:
The "heating" is not due to the ROM/Kernel, it's the SOC, SD888. This was already clarified a few times. Any device with this SOC has "heating" issues, simply because it's eating the power, and it's not efficient like for example the Sd865.

If you wanna eliminate the heat a bit, you can reduce the maximum boost of the CPU with FKM to something lower, or set it to a power saver scheduler.
[OnePlus 9 Pro] gillim74:
Looks like you need a bot for that also lmao
[OnePlus 9 Pro] darkness4every1:
It only overheats with this kernel for me
[OnePlus 9 Pro] JohnTheFarm3r:
Kernel doesn't do any changes related to the SOC or how the CPU boosts.
[OnePlus 9 Pro] Hammerhand.17:
Doesn't boot in Nameless 12.1 for me. I only downloaded the kernel, installed through ex kernel manager and phone got stuck in oneplus screen at the very beginning.

Flashed ROM boot and dtbo and it works again,
[OnePlus 9 Pro] Advali:
Any chance of this getting to work on LE2120? Tried it 3x now and its failing during flashing, says its not supported or something.
[OnePlus 9 Pro] Mr.Conkel:
So, is this kernel working with OOS12 sources or OOS11 sources?

I know it says A12 custom roms but that could mean 2 different things...
[OnePlus 9 Pro] EtherealRemnant:
r91 is OOS12, previous versions are OOS11.
[OnePlus 9 Pro] MostaphaHida:
Does this kernel work on oneplus 9 nameless rom ?
[OnePlus 9 Pro] reffu:
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)
[OnePlus 9 Pro] Rilindd:
Same here with StagOS.
[OnePlus 9 Pro] EtherealRemnant:
You're doing it wrong. Running this kernel just fine on StagOS 12.1. Make sure it's r91 you're using. Older versions are for OOS11.
[OnePlus 9 Pro] Rilindd:
For some reason when I put in the link for the custom kernel in FKM it decided to download and flash R56 and not R91. Reflashed R91 and it booted just fine.
[OnePlus 9 Pro] zefyx:
Thank you for r91!
[OnePlus 9 Pro] DirtryElectroOP3:
Will r91 run on EvolutionX V6.1? Android version is 12.0 using OOS11.
[OnePlus 9 Pro] EtherealRemnant:
No, it needs the older builds.
[OnePlus 9 Pro] Stogie87:
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?
[OnePlus 9 Pro] DirtryElectroOP3:
Do you know by any chance which version I'll need?
[OnePlus 9 Pro] alb94:
I'm using the latest LOS + Blu spark, and everything works perfectly, no problems now with audio recordings, and no distortions in the speaker.
[OnePlus 9 Pro] Stogie87:
Okay, then it was probably not just a kernel issue. I hope devs for other custom roms can also fix it easily.
[OnePlus 9 Pro] EtherealRemnant:
I haven't tried it myself but r56 uses OOS11 firmware.
[OnePlus 9 Pro] eng.stk:
It's not kernel, it's ROM binaries stuff.
[OnePlus 9 Pro] eng.stk:
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:

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 :)
[OnePlus 9 Pro] EtherealRemnant:
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.
[OnePlus 9 Pro] reffu:
Unlike r91, this one works for me on Nameless 12.1 OP9 (Lemonade). Just flashed through FKM and it booted right away. So far no issues and everything is running smoothly
[OnePlus 9 Pro] Shooter7889:
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..
[OnePlus 9 Pro] Advali:
Can you flash this via adb sideload instead? (Im unrooted/stock)
[OnePlus 9 Pro] break.cold:
I don't think so.
[OnePlus 9 Pro] xontax:
nope I'm just restoring my device on stag OS. Use FKM and import that file https://raw.githubusercontent.com/engstk/kernelfkm/master/updater_op9_custom.json. Works great!
[OnePlus 9 Pro] break.cold:
My bad, you can adb sideload spark kernel through LOS recovery. However, I think you need to be rooted.
[OnePlus 9 Pro] break.cold:
Yeah, It took me couple of hour of experiment in getting spark kernel to get it working, because it keep sending me back to fastboot menu even on LOS 28 June update. I installed it through Fk manager, it sent me to fastboot menu even though I flashed every img files. Then I adb sideload copy.zip after flashing LOS rom and Gapps, reboot to system and reboot to recovery to flash magisk and reboot to system again and then reboot to recovery and then use LOS recovery to flash spark kernel successfully.
[OnePlus 9 Pro] xontax:
FKM worked for me with the attached script right away. I copy.zip prior to the rom upgrade so cant judge on that
[OnePlus 9 Pro] break.cold:
I used above method that I mentioned.
[OnePlus 9 Pro] eng.stk:
No, it works fine in either slot.

The problem is that sometimes both slots aren't exactly well populated and the installer trusts on certain conditions to successfully work.

Both slots should be on latest and exactly the same A12 firmware from stock ROM previously to install anything.

Both slots should be flashed with working custom ROM.

Partitions to restore are the ones touched: boot, vendor_boot and vbmeta, you can do dtbo also. vendor_dlkm is mandatory to be restored and I think people with issues are missing it (flash only is available via fastbootd, not regular fastboot). MOst of the time device is so fast flashing ROM zips, maybe it's easier to do it like that.

We are used to this stuff on the Pixel and you guys are lucky to have already auto logical partitions processing, avb patching and all that jazz. We didn't in the Pixel 6 series initially and it was ruff during some months.

AK3: add full vendor_boot.img flash support · osm0sis/AnyKernel3@146f9b2

- Use similar dtbo.img logic - Support new hdr v4 images without repacking - Process before boot to safe bail Signed-off-by: engstk <eng.stk@sapo.pt>

github.com

AK3: add full vendor_dlkm.img flash support · osm0sis/AnyKernel3@2b7f6e8

- Use similar dtbo.img logic - Support new hdr v4 images without repacking - Process before boot to safe bail - No resize available, checks output size and bounces if larger - Handle block state co...

github.com

AK3: add support for resizing logical partitions (#69) · osm0sis/AnyKernel3@79cb694

- add flash_generic support for flashing to dynamic/logical partitions larger than stock using phhusson's lptools binary - enable full automated support for flashing custom vendor_dlkm.img (no...

github.com

AK3: add support for avb patching (#70) · osm0sis/AnyKernel3@bc736e9

- this supports custom kernel users to continue not having to fastboot reflash vbmeta with --disable-verity and --disable-verification, now that Magisk 24303+ no longer patches avb out of the fstab...

github.com

Device needs to be rebooted after flashing kernel and certain conditions met because vendor_dlkm is a logical partition and for it to be active.

Also kernel shouldn't be flashed after anything that touches any logical partition before a reboot (like flashing a ROM zip, restoring partitions, etc).

In stock ROM there's no vendor_dlkm in place, but most custom ROMs, since they drink from AOSP, should be already using it.

Check the Pixel 6 series forums to read more on this.

While is possible, I don't recommend because of what's above.

Even with all the things apparently working nicely, I ended up with issues when sideloading the kerrnel zips from LOS recovery for instance.

Logical partitions are nice to mod kernel installs in , but a pain to work with.
[OnePlus 9 Pro] eng.stk:
If you guys want a nice free and open source app tp flash kernel zips, backup and restore stock partitions and so on, check out Kernel Flasher:

[DEV] Kernel Flasher

Kernel Flasher is an Android app to flash, backup, and restore kernels. Features Flash partition images and AK3 kernel zips Backup and Restore kernel partitions Mount, Map, and Resize vendor_dlkm Save dmesg, logcat, and ramoops Check for kernel...

xdaforums.com

GitHub - capntrips/KernelFlasher: Kernel Flasher is an Android app to flash, backup, and restore kernels.

Kernel Flasher is an Android app to flash, backup, and restore kernels. - capntrips/KernelFlasher

github.com

There's the ability to save the kernel flash log to Downloads folder and share it here in case of any hiccups.

It's done by @capntrips , which has been doing quite some work in all this logical partitions/avb stuff we've been talking about, both on AK3 and other mods/solutions.

Highly recommended.
[OnePlus 9 Pro] 1thomas:
thanks for that, i tried the r96 version on StagOs with FKM and it kept going to fastboot, it worked perfectly with Kernel Flasher ;)
[OnePlus 9 Pro] sbute:
Successfully flashed r96 on StageOs 12 with kernel flasher app
[OnePlus 9 Pro] DirtryElectroOP3:
Can you please describe the steps you made in detail & what copy.zip file? Im in a bootloop altough i restored vendor_boot, dtbo and boot images.
[OnePlus 9 Pro] break.cold:
It's bit complicated,

Obviously I started with C.48 of OOS stock, I flashed dtbo, vendor_boot and recovery.img files then reboot to recovery.

I flashed copy-partitions-20210323_1922.zip with doing factory wipe/ format.

Then reboot to recovery again, then I did factory and format data, then I flash LOS 28 June rom and then reboot to recovery again and flash Gapps, and again do format data/factory wipe.

Reboot to recovery again then again adb sideload copy-partitions-20210323_1922.zip for LOS to be on both slots just to be sure.

Reboot to recovery but didn't do factory wipe after flashing copy-partitions-20210323_1922.zip second time after flashing LOS and Gapps.

Reboot to system, did system setup. And then reboot to recovery flashed magisk 25.1 file in recovery and reboot to system again.

Again I reboot to recovery flash spark kernel through LOS recovery with adb sideload. Reboot to system. Success...
[OnePlus 9 Pro] GreaterLesser:
Still not able to flash this kernel even with the new app. I'm on a LE2127 (TMO OP9P) w/ LOS 19.1 and Magisk 25.1. Everytime I try to flash the kernel, it fails and my phone gets soft-bricked if I reboot. I've been able to recover to stock LOS w/o having to wipe data fortunately. I've flashed C.48 firmware (and the copy partition zip) as well but still fails. I've attached the logs from the kernel flashing app. Thanks.

Edit: I can do a logcat if the app logs aren't sufficient. Thanks.
[OnePlus 9 Pro] xontax:
Dirty flash the rom and start over
[OnePlus 9 Pro] eng.stk:
Your super partition is dirty. You probably got it while using that copy partition zip.

Also got it after use it a couple times. I advise people to stay away from that zip, it misses some stuff we have in newer devices.

Flash OOS 12 in both slots to get proper fw installed.

Go for regular LOS flash in both slots.

Unpack your LOS zip to get img and flash the logical partitions in fastbootd (NOT fastboot)

do it for slot a AND b
[OnePlus 9 Pro] GreaterLesser:
Thanks for the info - Works perfectly now.

I'll definitely avoid using that zip in the future.
[OnePlus 9 Pro] sbute:
I've just installed StageOs from OOS C61 and then successfully flash r96 with kernel flasher app
[OnePlus 9 Pro] the_link_8:
hi, in the changelog says that there are some boost options turned of, how can i activate them ?
[OnePlus 9 Pro] eng.stk:
Kernel apps like FKM or EXKM.

What boost in particular?