yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] phoenix1589:
I've got a OP5 running 9.0.11 and blu_spark 188. Trying to flash 191 via FKM (exactly as I did for 188) says unsupported device ... Any ideas how to find out why it thinks it's unsupported?

### log output ###

CANNOT LINK EXECUTABLE "/system/bin/sleep": file offset for the library "liblog.so" >= file size: 0 >= 0

Archive: /storage/emulated/0/franco.kernel_updater/kernel_backups/blu_spark_r191-oos_op5-op5t_7e7d07c1e.zip

inflating: anykernel.sh

inflating: banner

inflating: Image.gz-dtb

inflating: LICENSE

creating: META-INF/

creating: META-INF/com/

creating: META-INF/com/google/

creating: META-INF/com/google/android/

inflating: META-INF/com/google/android/update-binary

inflating: META-INF/com/google/android/updater-script

creating: ramdisk/

inflating: ramdisk/init.qcom.rc

inflating: ramdisk/init.blu_spark_boot.sh

creating: tools/

inflating: tools/busybox

inflating: tools/magiskpolicy

inflating: tools/magiskboot

inflating: tools/ak3-core.sh

_ _

___ _ __ __ _ ___| |_| | __

/ _ \ '_ \ / _` | / __| __| |/ /

| __/ | | | (_| |_\__ \ |_| <

\___|_| |_|\__, (_)___/\__|_|\_\

|___/

*** blu_spark kernel for OnePlus 5/5T ***

AnyKernel3 by osm0sis @ xda-developers

Checking device...

Unsupported device. Aborting...
[OnePlus 5 & 5T Cross Device Development] wowkazmir:
Thanks for your message, brought me one step closer to solving the mystery!
[OnePlus 5 & 5T Cross Device Development] phoenix1589:
I did a bit of digging, the do_devicecheck function in update-binary isn't able to read the device (or any other) properties.

If I add extra debug, the output is blank for device:

ui_print "Checking device...";

device=$(getprop ro.product.device 2>/dev/null);

ui_print "-$device" " ";

Checking device...

-

Rather than what I get from termux:

$ device=$(getprop ro.product.device 2>/dev/null);

$ echo $device

OnePlus5

No idea why ?!
[OnePlus 5 & 5T Cross Device Development] radz_:
I have dumpling but everytime I flash this kernel it says device is cheeseburger, works fine though.
[OnePlus 5 & 5T Cross Device Development] dead90:
Someone use modified settings and want to share it?
[OnePlus 5 & 5T Cross Device Development] WhoDunnit:
I had the same issue. Flashing with TWRP works fine though.
[OnePlus 5 & 5T Cross Device Development] phoenix1589:
Thanks, that worked for me too. I guess it could be an issue with FKM?!
[OnePlus 5 & 5T Cross Device Development] rohithksaj:
May be !

I opted for flashing with FKM and tried cancelling it ! But it got flashed any way !
[OnePlus 5 & 5T Cross Device Development] zaibansari20:
Does it support Android 10 custom ROMs ???

It was great experience on Pie OOS
[OnePlus 5 & 5T Cross Device Development] eng.stk:
blu_spark r193 release (Pie unified)

All right crew!

New build is up!

Pie builds are unified, good to go on 5/5T :good:

Also checkout latest recommended blu_spark extras with blu_twrp v9.110 (Pie support).

You can now use FKM download kernel feature, just import the links bellow in the app flash section :highfive:

blu_spark_r193 release

FKM download configs: oos | custom

Keep in mind: I will give no active support for custom ROMs (including OOS based ones).

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.

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 :)
[OnePlus 5 & 5T Cross Device Development] Flint2:
r193 working ok with OOS 9.0.11

Thanks!!
[OnePlus 5 & 5T Cross Device Development] Az Biker:
* * * Thread Cleaned * * *

Please keep all comments related to development of this kernel.

Disrespectful, rude, off-topic, and insulting comments will not be tolerated and will be deleted without warning.

If your comment isn't helpful, respectful, and directly related to development, please don't post it.

Thanks for everyone's cooperation :good:
[OnePlus 5 & 5T Cross Device Development] joeyfong:
How do you flash it???
[OnePlus 5 & 5T Cross Device Development] surajloharia:
TWRP
[OnePlus 5 & 5T Cross Device Development] DarkStryder:
Can i flash this straight over stock non rooted device?
[OnePlus 5 & 5T Cross Device Development] surajloharia:
You can flash if not rooted, but still need unlocked bootloader and TWRP
[OnePlus 5 & 5T Cross Device Development] Pokemetti2:
Can't you have locked bootloader and TWRP too?
[OnePlus 5 & 5T Cross Device Development] Flint2:
No
[OnePlus 5 & 5T Cross Device Development] Pokemetti2:
You can, actually. You can use TWRP normally even.
[OnePlus 5 & 5T Cross Device Development] joeyfong:
which magisk you are using, I got stuck at boot logo. Back to r191 is fine.
[OnePlus 5 & 5T Cross Device Development] Mackie Messer:
20.4

20.1 or newer is mandatory
[OnePlus 5 & 5T Cross Device Development] joeyfong:
do you flash magisk after kernel?
[OnePlus 5 & 5T Cross Device Development] surajloharia:
It doesn't matter if you flash kernel before or after the kernel, as Magisk just patches the boot image.

If kernel is flashed after the magisk, the kernel have additional patches so u don't have to flash magisk again.
[OnePlus 5 & 5T Cross Device Development] Pokemetti2:
I always flash Magisk afterwards, just to be sure.
[OnePlus 5 & 5T Cross Device Development] surajloharia:
Never faced any issue till yet

Flashing kernel afterwards Magisk !!
[OnePlus 5 & 5T Cross Device Development] KaZo58:
Stuck on boot logo with newest Canary Magisk (20406). just flash previous version and it'll boot up normal again.
[OnePlus 5 & 5T Cross Device Development] eng.stk:
Magisk canarys are not stable and not suitable for daily driving.

Latest ones had issues with overlay.d used on some kernels.

Stick to stable or at least beta Magisk versions.

Sent from my blu_spark'd OnePlus
[OnePlus 5 & 5T Cross Device Development] joeyfong:
same here
[OnePlus 5 & 5T Cross Device Development] anujyadava:
Phone has become bit sluggish after updating to r193. Apps opening time has increased a bit.anyone else facing the issue?
[OnePlus 5 & 5T Cross Device Development] Chaplan:
Not really, all is working smoothly on my end.
[OnePlus 5 & 5T Cross Device Development] dsjd:
I tried flashing this on h2os 10 on my 5t. Everything was perfect except wifi didn't turn on. Can't wait to officially have blu spark back on my phone.
[OnePlus 5 & 5T Cross Device Development] Astur_Torque:
Can I use this recovery (v193) to install the new Android 10 beta?
[OnePlus 5 & 5T Cross Device Development] Unn113:
Yes.
[OnePlus 5 & 5T Cross Device Development] dsjd:
Will the kernel be updated for oos 10 beta 1?
[OnePlus 5 & 5T Cross Device Development] Flint2:
Was source code released by Oneplus?

I don´t see it in https://github.com/OnePlusOSS/android_kernel_oneplus_msm8998
[OnePlus 5 & 5T Cross Device Development] rohithksaj:
Nope . He bulids only for stable !
[OnePlus 5 & 5T Cross Device Development] Chaplan:
Urban myths.

No source, no dice. More accurate, same missing feelings... ?
[OnePlus 5 & 5T Cross Device Development] RMarques:
Does anyone know if this kernel does support Battery idle mode?
[OnePlus 5 & 5T Cross Device Development] eng.stk:
Always on the fastlane [emoji16]

View attachment 5005969

Sent from my blu_spark'd Oneplus
[OnePlus 5 & 5T Cross Device Development] gbeardmore:
Screenshot shows Kernel version #194 with today's date. Will that be released or is it only a test build of yours? TY!
[OnePlus 5 & 5T Cross Device Development] dsjd:
Ahhhhhhh
[OnePlus 5 & 5T Cross Device Development] tinuz97:
Fastlane, and WireGuardLane for me ? (slow without bluspark kernel now on Android 10)

But I have patience ?
[OnePlus 5 & 5T Cross Device Development] dsjd:
Just curious, don't you need OnePlus to update the kernel source before you can update the kernel?
[OnePlus 5 & 5T Cross Device Development] elbuenzurdo:
Is that a teaser? ??
[OnePlus 5 & 5T Cross Device Development] eng.stk:
Touché! :victory:
[OnePlus 5 & 5T Cross Device Development] eng.stk:
blu_spark r194 release (Pie/A10 unified)

All right crew!

New build is up!

Pie builds are unified, good to go on 5/5T :good:

Also checkout latest recommended blu_spark extras with blu_twrp v9.110 (Pie support).

You can now use FKM download kernel feature, just import the links bellow in the app flash section :highfive:

Early support to A10 ROMs is in, keep in mind this is wonky hax, your mileage may vary (although is going strong lates couple days). I'll probably have to rebase when A10 sourcedrop is available.

Enjoy :highfive:

blu_spark_r194 release

FKM download configs: oos | custom

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 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.

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 :)
[OnePlus 5 & 5T Cross Device Development] tinuz97:
Yay, WireSparked again.

This does make such a big difference, without the kernel I 'only' get +-165/175mbps download speed with WireGuard VPN server on my raspberry pi 4. (I have 500/500mbps Fibre).

Now back at full speed again with BluSpark 194 (Android 10 open beta 1, op5).

i'm blue daba dee daba die ???

Wicked!
[OnePlus 5 & 5T Cross Device Development] n0j0e:
Great [MENTION=3873953]eng.stk[/MENTION] ! blu_spark kernel r194 on crDroid Luis #0427 (LOS, OB1 firmware) is up and running. WLAN works :laugh:

But there is something wrong with /sdcard. Apps can't see the files now. Empty :crying:

Restored stock sigmaKernel and all fine.

I know you're not support customs rom official. Only a report from me.
[OnePlus 5 & 5T Cross Device Development] Bodygard379:
r194

Wifi doesn't work, can't connect. Major issue...

Formatted Data in TRWP and also wiped cache, system, data etc so it was a clean install. Installed OOS 10 beta and everything went well. After configuring everything, went again into TWRP and flashed r194 for OOS, rebooted and can't turn wifi on.
[OnePlus 5 & 5T Cross Device Development] Mackie Messer:
Zero problems here. I'm connected.
[OnePlus 5 & 5T Cross Device Development] Bodygard379:
Gonna flash everything again and test it. Kinda weird...

PS: flashed another kernel just for testing (weeb kernel for OOS) and WIFI started working. Investigating...
[OnePlus 5 & 5T Cross Device Development] SatishSharmaCh:
Can we flash on 9.0.11?
[OnePlus 5 & 5T Cross Device Development] anujyadava:
Deleted
[OnePlus 5 & 5T Cross Device Development] cieffe54:
Flash and reboot in fastboot! Why??

I am on beta 1 with magisk 20.4

edit: solved with magisk reflash boot but wifi not work
[OnePlus 5 & 5T Cross Device Development] eng.stk:
Yes.

Sent from my blu_spark'd OnePlus
[OnePlus 5 & 5T Cross Device Development] dsjd:
I couldn't flash it using FKM update link on oos 10. I had to do it manually. If you get a chance, please look into that
[OnePlus 5 & 5T Cross Device Development] cieffe54:
+1
[OnePlus 5 & 5T Cross Device Development] Angelcho:
+1 on the no wifi issue, at your disposal if you need any logs.
[OnePlus 5 & 5T Cross Device Development] SatishSharmaCh:
Make sure you guys flashed the correct version..

OOS/CUSTOM.

It's working fine here no issues at all.
[OnePlus 5 & 5T Cross Device Development] SatishSharmaCh:
Check the screenshot.
[OnePlus 5 & 5T Cross Device Development] Bodygard379:
You're on OOS Android 9, i'm using OOS Android 10 beta1. But Eng.stk said he only supports stable OOS so we all can wait for a stable Oneplus OOS release and then this will probably be solved.
[OnePlus 5 & 5T Cross Device Development] cieffe54:
Shure! I am not alone with this bug!
[OnePlus 5 & 5T Cross Device Development] eng.stk:
Flash the correct build and flash Magisk 20.4 stable, canary has issues with kernels systemless backend.

Working fine here.
[OnePlus 5 & 5T Cross Device Development] broky:
I flashed r194 OOS yesterday(OOS Beta 10) and my WiFi was not working either.

Today I tried again,flashed r194 ,flashed Magisk,boom,WiFi works like a charm:good:.
[OnePlus 5 & 5T Cross Device Development] Bodygard379:
My OP5 is not rooted, i don't use Magisk. Only OOS10 beta1 clean install in TWRP and flashed r194 for OOS later. No success, wifi doesn't activate. I'll wait for OOS stable thank you for your work and dedication.
[OnePlus 5 & 5T Cross Device Development] andreacos92:
OP5 with OOS10 OpenBeta1 (clean install) and Magisk 20.4, kernel is good as usual and wifi is working.

Maybe is Magisk required for it to work? I noticed that flashing the kernel adds a Magisk module, AK3 Helper Module. What is it?
[OnePlus 5 & 5T Cross Device Development] elbuenzurdo:
Same issue here with the json config file, it never started downloading in FKM. However, downloaded manually and used FKM for flashing.
[OnePlus 5 & 5T Cross Device Development] eng.stk:
Try this for me, should be good to go :fingers-crossed:
[OnePlus 5 & 5T Cross Device Development] eng.stk:
Magisk is mandatory since I went with totally systemless installs.

It's needed to inject kernel settings on the fly and some other stuff, like some current hax's.

While it should be fine running rootless, nowadays is pointless. A lot will be missing.
[OnePlus 5 & 5T Cross Device Development] dsjd:
I uninstalled and reinstalled FKM and now it's working fine
[OnePlus 5 & 5T Cross Device Development] andreacos92:
Got it :good:

Anyway, do I remember not correctly, or the installing script in TWRP says "Magisk is not necessary" when it detects Magisk? :D
[OnePlus 5 & 5T Cross Device Development] replica88:
”...so reflashing Magisk is not necessary", get your fact straight dude. It's a feature allowing flashing kernel after magisk.
[OnePlus 5 & 5T Cross Device Development] n0j0e:
Nope.

/storage/emulated/0/ = no files!

/storage/self/primary/ = there be the files.

primary is a symbolic link to /storage/emulated/0.

..but WiFi still works. ^^
[OnePlus 5 & 5T Cross Device Development] andreacos92:
Sorry, maybe I misunderstood, my fault.

No need to be rude :)
[OnePlus 5 & 5T Cross Device Development] Mar-cel:
It shows encrypted. How can I know now if it is FDE or FBE?
[OnePlus 5 & 5T Cross Device Development] eng.stk:
type on terminal:

getprop ro.crypto.type

If you get file you're using FBE

You can use whatever you have atm, don't need to change remove anything. I use pattern lock myself.
[OnePlus 5 & 5T Cross Device Development] Fenvarien:
Great working kernel, stable and very smooth with good battery life. Thanks for your hard work [MENTION=3873953]eng.stk[/MENTION] !
[OnePlus 5 & 5T Cross Device Development] eng.stk:
You're welcome :highfive:

On the other news, good days ahead for custom ROMs users :fingers-crossed:
[OnePlus 5 & 5T Cross Device Development] Teren49:
Just a question, do you apply these settings for both big and little clusters?

Thanks!
[OnePlus 5 & 5T Cross Device Development] asti patel:
Yes
[OnePlus 5 & 5T Cross Device Development] Teren49:
Perfect, thanks for the reply!

I've just applied and my OP5 flies. Guess activating fastlane and reducing threshold value reduces battery life, right?
[OnePlus 5 & 5T Cross Device Development] liver20:
Perfect [MENTION=3873953]eng.stk[/MENTION], then tonight cant sleep

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[OnePlus 5 & 5T Cross Device Development] asti patel:
I think not .

It just help to kick the cpu for fast processing.

Maybe don't know for sure.
[OnePlus 5 & 5T Cross Device Development] Rebel7022:
I like running the kernel without fastlane more
[OnePlus 5 & 5T Cross Device Development] Gizmundo:
Delete
[OnePlus 5 & 5T Cross Device Development] xXx:
unfortunately that's not the case. This getprop command seems to return a static value as it always returns encrypted no matter if you are encrypted or decrypted. So far I couldn't find an easy way to check the status for encryption in TWRP.
[OnePlus 5 & 5T Cross Device Development] ALEX37330:
Since I have installed your TWRP I have error failed to unmount system and I can t format or anything else with twrp
[OnePlus 5 & 5T Cross Device Development] kinfam:
Extremely happy to see you, your recovery, and your kernel here.

I was getting bootloops like crazy with the other recoveries.... Yours runs like a dream! No issues whatsoever. Kernel performance is top notch just like your 3T builds. Fastlane is the best lane.

Welcome :)
[OnePlus 5 & 5T Cross Device Development] eng.stk:
I don't think so, no.

getprop ro.crypto.state

returns at least encrypted or unsupported (old unencrypted in FDE)

getprop ro.crypto.type

returns at least file (FBE) or block (FDE)

ro.crypto.type is the most important, you will only get result if device is actually in encrypted state.
[OnePlus 5 & 5T Cross Device Development] xXx:
I just checked it again. I'm decrypted and checked in terminal with your twrp v41.

getprop ro.crypto.state returns "encrypted" and it doesn't matter which TWRP you are using. It always returns encrypted. But anyway, the question is if there is possibly another way to get reliable information about the encryption status in TWRP?
[OnePlus 5 & 5T Cross Device Development] eng.stk:
You mean unencrypted.

Decrypted is a state when you have an encrypted information and pass thought a decryption operation to get information in plain. Original information stays encrypted.

A couple users tested and got that result string in case of unencrypted. Are you in ext4 or f2fs? Don't know if it can make a difference.

Those values are coded in framework and are stock, not much we can do I guess.

I already gave you the solution, sort of:

In case of FDE, not forcing encryption works for both cases (my default).

In case of encryption, it's just a matter of testing the encryption type (for correct mount option).

Other than that, idk.
[OnePlus 5 & 5T Cross Device Development] chrissss91:
Hi eng.stk,

I was on OOS 4.5.8, with Magisk 13.3, Katinatez op-5-twrp-k2.img and your blu_spark r12 OP5 kernel.

I sucessfully flashed your blu_spark r16 OP5 kernel followed by your twrp-3.1.1-x_blu_spark_v41-op5.img.

Reboot to your recovery OK. But in your recovery when I click on any reboot option (recovery, system, ...) TWRP gets stuck.

I have to push power key for few seconds to reboot.

I've rolled back to Katinatez TWRP and everything is ok, then flashed your v40 and v41 TWRP and same problem with both of them.

I don't know what's going wrong.

[Edit] : /cache/recovery/last_log is in attachment
[OnePlus 5 & 5T Cross Device Development] eng.stk:
Remove any TWRP settings.

It reboots fine.
[OnePlus 5 & 5T Cross Device Development] chrissss91:
Thx, reboots well now :good:
[OnePlus 5 & 5T Cross Device Development] KaszasM:
oos pie only rooted wifi works but i can't get rid of the no internet message all the time on wifi r194,

193 works,

it shows only ipv6 with 194 and no 4
[OnePlus 5 & 5T Cross Device Development] cieffe54:
Flashed Beta 2 and now, finally, wifi works!
[OnePlus 5 & 5T Cross Device Development] Flint2:
r194 working ok with OOS 10 Open Beta 2 build 200424

Thanks!
[OnePlus 5 & 5T Cross Device Development] andreacos92:
I confirm r194 working good with Beta 2 on OP 5.

A question regarding TWRP bluspark 9.110: is it fully compatible with Android 10? I used it to flash these new betas, but could it not be fully compatible for other features, such as wiping cache/dalvik?

EDIT: nevermind :mad:

Thanks
[OnePlus 5 & 5T Cross Device Development] nilse:
How did you get Wifi to work on A10?

Flashed Beta 2 and then blue spark v194 and then Magisk 20.4?

Am I doing something wrong, or is the kernel just not stable yet?

EDIT: Reflashed v194 then Magisk and Wifi works. Probably needs Magisk to be installed *before* kernel is installed.
[OnePlus 5 & 5T Cross Device Development] Bodygard379:
Wiped everything, formatted data in TWRP.

Booted to TWRP. Installed OOS 10 Beta2. Booted to system, configured everything.

Booted to TWRP, flashed magisk stable, booted to system. Installed magisk manager, everything fine.

Booted to TWRP, flashed R194 5-5T OOS and booted to system again. Everything fine, wifi works.
[OnePlus 5 & 5T Cross Device Development] andreacos92:
The EDIT is correct, right order is: ROM -> Magisk -> Kernel.

Moreover, you can flash Kernel in a second moment too, after rebooting to system.

But you have to flash Magisk right after you flashed OOS, otherwise at reboot OOS will replace the custom recovery with the stock OnePlus recovery. (EDIT: that happens if you wipe /system partition too, that I do when I want a clean install)
[OnePlus 5 & 5T Cross Device Development] shadowstep:
Magisk is not necessary to make TWRP stick. If someone wants to stay away from Magisk but wants to retain TWRP (with an unlocked bootloader, of course), then he/she can flash the OxygenOS TWRP Retainer zip from this post of mine. :)
[OnePlus 5 & 5T Cross Device Development] andreacos92:
Uh, I didn't know this. Really nice for who doesn't need root and/or any module :)
[OnePlus 5 & 5T Cross Device Development] ariadnejro:
There is another way to prevent OOS from flashing its own recovery: deleting or renaming the file install-recovery.sh located in /system/bin using TWRP's File Manager.
[OnePlus 5 & 5T Cross Device Development] djmeistro:
I had to uninstall magisk and then reinstall, then flash 194
[OnePlus 5 & 5T Cross Device Development] Flint2:
Yes, is the same effect, what flashable zip does is very simple but convenient:

delete("/system/bin/install-recovery.sh");

delete("/system/etc/recovery-resource.dat");

delete("/system/recovery-from-boot.p");
[OnePlus 5 & 5T Cross Device Development] KaszasM:
actually i have fixed that by flashing 193 than flasing 194 over franko , actually the magisk modul isnt created if i flash 194 with twrp .

but thanks for your answer
[OnePlus 5 & 5T Cross Device Development] eng.stk:
No need to do any of that and modify filesystem, blu_spark kernel install takes care of that systemlessly.

Sent from my blu_spark'd OnePlus
[OnePlus 5 & 5T Cross Device Development] surajloharia:
But to be stock we don't need custom kernel.
[OnePlus 5 & 5T Cross Device Development] eng.stk:
To be stock we don't belong on this thread.

Sent from my blu_spark'd OnePlus
[OnePlus 5 & 5T Cross Device Development] Goutham Ganesh:
I have the same problem, tried this but didn't work.
[OnePlus 5 & 5T Cross Device Development] eng.stk:
OOS 10 build is fine, custom A10 ROMs without a proper rebase is hit and miss.

When A10 source is out we'll see.
[OnePlus 5 & 5T Cross Device Development] n0j0e:
[MENTION=3873953]eng.stk[/MENTION] has you read this? Looks like a simple mount problem or? WiFi works and very fluid!
[OnePlus 5 & 5T Cross Device Development] deepongi:
OOS A10 Beta sources are out.

https://github.com/OnePlusOSS/android_kernel_oneplus_msm8998/tree/oneplus/QC8998_Q_10.0_Beta
[OnePlus 5 & 5T Cross Device Development] Chaplan:
Like for 9 hours.

Late news are always better than fake news.

:p
[OnePlus 5 & 5T Cross Device Development] eng.stk:
blu_spark r198 release (A10 unified)

All right crew!

New build is up!

A10 builds are unified, good to go on 5/5T :good:

Also checkout latest recommended blu_spark extras with blu_twrp v9.110.

You can now use FKM download kernel feature, just import the links bellow in the app flash section :highfive:

Full rebase on A10 sourcedrop is here, all goodies in.

Enjoy :highfive:

blu_spark_r198 release

FKM download configs: oos | custom

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 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.

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 :)