[KERNEL] [blu_spark r151 OP8/Pro/T] [A12 OOS]
- Thread starter eng.stk
- Start date
Pro or T? As i said on Pro working normally. But vibration really sucks with 12, dont know its a kernel issue...Hi all
I confirm, after flashing kernel Oos12 lost warp/vooc charging, and charging is also slow.
Flashing back stock kernel warp charging is working again.
Weird
...and using alarm slider sometimes freezes and reboots device.
Sorry I forgot. I use oneplus 8T oos12 c20.
Kernel looks working great with Zen i/o and gpu boost.
Something weird is usb fast charging came back to disable after each reboot so I have to enable it after rebooting.
Maybe this is the bug of warp charging I don't know
For the slider I don't have issues.
I noticed that 4 small cores used to stuck at 1600 mhz all the time, even when no application was in back ground. And it seems to drain battery, in 8 minutes I lost 4%,but it's the first day with blue spark kernel,I will check after few days.
But for a FIRST OOS12 kernel it's a good beginning
Thanks to THE DEV he is the first people who can create Oos12 kernel
Many devs gave up with oos12 **** sources
Last edited:
Yes, many thx to dev for that, was the only thing stopping me to switch to 12. But 12 is buggy, after some hours with some nasty bugs i found its ok, but buggy. But i had to know that after reading some posts in oneplus forum ;-)Sorry I forgot. I use oneplus 8T oos12 c20.
Kernel looks working great with Zen i/o and gpu boost.
Something weird is usb fast charging came back to disable after each reboot so I have to enable it after rebooting.
Maybe this is the bug of warp charging I don't know
But for a FIRST OOS12 kernel it's a good beginning
Thanks to THE DEV he is the first people who can create Oos12 kernel
Many devs gave up with oos12 **** sources
its also an 8T on OOS 12....build KB2005_11_c.11
it will finally boot to the lockscreen and ask for pin but i cant enter my pin, screen doesnt respond to touch
Well, I honestly tried.
It's 8350 all over again, I'm done with (C)OOS sources. Specially since OOS 11 on the OP7 series, stuff is just going downhill fast.
I lost days already fixing crap for 8350 and 8250 alone, including porting stuff from other trees. Stuff continues to be broken and/or missing.
By the reports I count 3 or 4 subsystems that I feel important to be left derped.
Specially critical stuff like charging, that can hurt people's HW, I ain't tinkering with that, sorry.
So, since I also can't stand the bloaded mess that C(OOS) 12 is, I'm done.
forum.xda-developers.com
forum.xda-developers.com
forum.xda-developers.com
forum.xda-developers.com
forum.xda-developers.com
When LOS ships with A12 codebase, if I like how it runs on the device I will support it like I did on the OP9 series.
Until then, sayonara. This device is dead to me.
It's 8350 all over again, I'm done with (C)OOS sources. Specially since OOS 11 on the OP7 series, stuff is just going downhill fast.
I lost days already fixing crap for 8350 and 8250 alone, including porting stuff from other trees. Stuff continues to be broken and/or missing.
By the reports I count 3 or 4 subsystems that I feel important to be left derped.
Specially critical stuff like charging, that can hurt people's HW, I ain't tinkering with that, sorry.
So, since I also can't stand the bloaded mess that C(OOS) 12 is, I'm done.
[KERNEL] [blu_spark r151 OP8/Pro/T] [A12 OOS]
Kernel features: Build with Google Clang version 14.0.2 + LLD linker Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP8 builds based on...
forum.xda-developers.com
[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...
forum.xda-developers.com
[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...
forum.xda-developers.com
[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...
forum.xda-developers.com
[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...
forum.xda-developers.com
When LOS ships with A12 codebase, if I like how it runs on the device I will support it like I did on the OP9 series.
Until then, sayonara. This device is dead to me.
Last edited:
No more updates for A11 too ?Well, I honestly tried.
It's 8350 all over again, I'm done with (C)OOS sources. Specially since OOS 11 on the OP7 series, stuff is just going downhill fast.
I lost days already fixing crap for 8350 and 8250 alone, including porting stuff from other trees. Stuff continues to be broken and/or missing.
By the reports I count 3 or 4 subsystems that I feel important to be left derped.
Specially critical stuff like charging, that can hurt people's HW, I ain't tinkering with that, sorry.
So, since I also can't stand the bloaded mess that C(OOS) 12 is, I'm done.
[KERNEL] [blu_spark r151 OP8/Pro/T] [A12 OOS]
Kernel features: Build with Google Clang version 14.0.2 + LLD linker Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP8 builds based on...[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...
When LOS ships with A12, if I like how it runs on the device I will support it like I did on the OP9 series.
Until then, sayonara. This device is dead to me.
Guess this was a lieThis one of the main reasons why I keep pushing on: the nice community we've been building over the years.
Thanks for the support mate
That is a general statement, not a "hey I'm going to support this particular device until I'm dead".Guess this was a lie
I gave and continue to give support to dozens of devices over the years.
Need better support for this device, go ask OP.
As it stands, I'm out. Door left open for LOS (yet...).
I don't lie, I'm actually quite upfront about stuff.Unfortunately yes
I bother explaining the what and the why's over stuff.
Even gave a little more effort over th ecrap situation we're at concerning sources.
Could just abandon thread and/or close like others did. But I didn't (yet...).
Let's stay positive. I'm looking forward to LOS
Last edited:
Well we obviously have working boot for 12.1 custom kernels since we a lot of ROMs using it so why not just build for custom? Aicp, crdroid, etc
Hey ! Can I atleast get dtbo image for 8t ?Well, I honestly tried.
It's 8350 all over again, I'm done with (C)OOS sources. Specially since OOS 11 on the OP7 series, stuff is just going downhill fast.
I lost days already fixing crap for 8350 and 8250 alone, including porting stuff from other trees. Stuff continues to be broken and/or missing.
By the reports I count 3 or 4 subsystems that I feel important to be left derped.
Specially critical stuff like charging, that can hurt people's HW, I ain't tinkering with that, sorry.
So, since I also can't stand the bloaded mess that C(OOS) 12 is, I'm done.
[KERNEL] [blu_spark r151 OP8/Pro/T] [A12 OOS]
Kernel features: Build with Google Clang version 14.0.2 + LLD linker Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP8 builds based on...[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...[KERNEL] [blu_spark r103 OP9/Pro] [A11 OOS/A12 Custom]
Kernel features: Build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS) full thinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc Less is more: stockish OP9 builds based on...
When LOS ships with A12, if I like how it runs on the device I will support it like I did on the OP9 series.
Until then, sayonara. This device is dead to me.
I will not build for something I don't personally use.
I will not build for old codebase. I don't care about having a 12.1 ROM with a patched up A11 codebase kernels or CAF adaptations.
Lastly: I'll always build and give support to stuff out of fun and on my own terms. That's not going to change.
Last edited:
I don't touch DTBO in any of my kernels.
Just use payload-dumper-go to unpack what you need from your zips.
Too bad, but absolutely understandable. I dont know much about building kernel but if one of the most skilled developer gives up, the people from oneplus didnt made their job. OOS 12 seems beta for now, i hope things get better, but for now it maybe could be better to stay with OOS11........
Ahhh... OnePlus realllly dropped the ball with a12 and that massive crap of buggy kernel source
certainly doesnt make it easier for the devs and the community . but then oneplus was always stingy about releasing codes or was unwlling . a lot of promised was made by them but non delivered.
i guess im gonna skip a12 and wait for the next one then
certainly doesnt make it easier for the devs and the community . but then oneplus was always stingy about releasing codes or was unwlling . a lot of promised was made by them but non delivered.
i guess im gonna skip a12 and wait for the next one then
Similar threads
Top Liked Posts
-
1
-
6Go to a kernel thread and ask for an experince dev, seriously. Normally i just scroll past those, but i can't cope it anymore. Xda used to be the best place to be, for knowledge, learning, social, teamwork etc. Over the past years, more and more don't take their time, to actually read, even 1 page back, they can't wait for a fix, can't deal with wip or even a dead end, due to release from oneplus. Its so negative to enter a thread now, just to see what dev's have to deal with from the community, its their free time, not getting payed, they deliver for many phones every month, year after year, and we see more devs leaving the site because of it. How about being a little grateful, say thx, got a problem share a log, and wait, nomatter the outcome.
Sry for OT, but cmon. You don't go to Ferrari and ask who can build a quality car either. If for whatever reason, you cant live with the kernels/firmware etc, theres plenty of threads with guides, then read and build one yourself, ask a few devs if they cant help and live with the yes/no answer.
Save Xda instead of bashing around with all that negativity.
Good day.4
Better contact OnePlus, they are full of experienced devs that are actually paid to fix their customers problems.4
Go to the official OnePlus Community forums or contact their customer support...1
Yes, its for oos12. But its a dead project and there are some bugs....you are better with stock oos12 kernel.1 -
86
Kernel features:
- Build with Google Clang version 14.0.2 + LLD linker
- Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
- Less is more: stockish OP8 builds based on OnePlusOSS/android_kernel_oneplus_sm8250 for max stability
- Systemless installer (doesn't touch system partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
- Removed some debug and logging options
- ARM enhanced performance and battery patches
- CVE security patches, general upstream and CAF fixes for important subsystems
- Modded schedutil governor merged from latest CAF sm8250 patchset
- No OC, use 250HZ base timer frequency
- msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
- Enhanced TCP methods (westwood is default, BBR available), Network tweaks and updated drivers
- Several I/O control tweaks, added schedulers ZEN v2 is default, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
- ZRAM Swap (LZ4 default) and with file disabled, LZO-RLE and ZSTD are available
- Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
- KGSL fixes and general improvements for GPU driver
- adrenoboost ready (disabled by default)
- Backlight min brightness and backlight scale option
- Gamepad support enabled (xbox, ps4, switch)
- USB Fast Charge (USB mode up to 900mA with MTP on)
- FS fsync toggle on/off
- Wakelock blockers available
- wireguard support
- CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
- Compatible with Kernel Adiutor, EXKM, FKM and others
Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
If you come from other kernel or have any issues, you should restore your stock boot.img or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
If you are upgrading between blu_spark versions, just flash the kernel zip.
About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock OOS ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
If you're using custom ROMs (including stock based ones) and OOS Open Betas you're much on your own. I'm mostly interested on debugging stuff in stock and stable OOS.
Also try not to spam the thread with OT. There's threads for all kind of stuff, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
Source Code: https://github.com/engstk/op8
Don't forget to hit thanks, it's free
OnePlus 8 Pro development unit donated by OnePlus. Big shouts to them
Very proud of being on the OnePlus Developer Program, special thanks to dev relations team.29blu_spark_r109 release
New build is up
This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
You can use FKM download kernel feature, just import the links bellow in the app.
FKM download configs: oos
Changelog:
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 free28blu_spark_r115 release
New build is up!
This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
You can use FKM download kernel feature, just import the links bellow in the app.
FKM download configs: oos
Changelog:
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 free28blu_spark_r110 release
New build is up
This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
You can use FKM download kernel feature, just import the links bellow in the app.
FKM download configs: oos
Changelog:
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 free26blu_spark_r101 release
New build is up
This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
You can use FKM download kernel feature, just import the links bellow in the app.
FKM download configs: oos
Changelog:
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
