• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Development [KERNEL] [blu_spark r40 OP9/Pro] [A11 OOS]

Search This thread

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,659
33,032
Halifax
GT-i9250
Nexus 7 (2013)
On devices in regions that aren't using Google OTA you can still use Magisk's Install to Inactive Slot, so they're different, and slightly easier instructions than my Google OTA ones.
 
Last edited:

Bunecarera

Senior Member
Mar 4, 2008
244
80
OnePlus 9 Pro
Only an operating system update will solve that. You think OnePlus would of fixed all that bs before release. Tmob variant op9? I'm on global and don't have that issue whatsoever.

No, I'm on the European variant.
I thought maybe this kernel had changed doze settings.
Problem with the notifications seem to be doze related.
Although disabling doze via adb doesn't bring them back...
 

Haunt3r

Senior Member
Yup, you can grab it from any full OTA or from someone else's backups if you really need them.
I mean to keep safetynet during an incremental OTA it seems like it's required. I'm on AA so it sounds like I do need them. Just don't wanna lose safetynet. Would it be safe to assume I could use the full OTA dumps from .5.5 when doing an incremental from .7.7 to whatever the next OTA is (assuming it's not a full OTA).
 

Haunt3r

Senior Member
What variant / build are you on? That's necessary info for this post.
Screenshot_20210617-010617.jpg
 

eng.stk

Senior Member
Mar 29, 2011
6,891
59,176
OnePlus 5T
OnePlus 6
Finally flashed. Under wakelock blocking I have no wakelocks to block. Am I missing something ? Usually shows a list of what you wanna 🚫 or not...just curious. Much faster than stock scrolling /opening apps. Winning!!
You need to give it time to appear on the list.
Then long press the one you want to block to copy the name and add it on the block screen.

Keep in mind that wakelocks are there for a reason, if you block the wrong ones you can introduce instability
 

Attachments

  • Screenshot_20210617-112359.jpg
    Screenshot_20210617-112359.jpg
    265.9 KB · Views: 57
  • Screenshot_20210617-112407.jpg
    Screenshot_20210617-112407.jpg
    468 KB · Views: 57

mattie_49

Senior Member
Feb 4, 2010
2,931
901
Seymour Tn
OnePlus 9
You need to give it time to appear on the list.
Then long press the one you want to block to copy the name and add it on the block screen.

Keep in mind that wakelocks are there for a reason, if you block the wrong ones you can introduce instability
Is this the interface of Fkm? I use ex kernel manager. Maybe time for me to switch
 
I mean to keep safetynet during an incremental OTA it seems like it's required. I'm on AA so it sounds like I do need them. Just don't wanna lose safetynet. Would it be safe to assume I could use the full OTA dumps from .5.5 when doing an incremental from .7.7 to whatever the next OTA is (assuming it's not a full OTA).

I would suggest grabbing them from a full OTA package for your variant if that's the case. Or someone could provide them. I would provide mine, but they're from an LE2127 on 11.2.6.6. In my experience, for boot.img files, most of the time any boot variant will do, as long as it's the same OOS build (for example, on the 7T, I was able to root using a EUR boot.img, which was necessary due to the fact that the T-Mobile full OTAs were not yet available online at that time), but it's best to patch it yourself and boot into it to test first. The vendor files, however, I cannot speak for.

Is this the interface of Fkm? I use ex kernel manager. Maybe time for me to switch

No, that doesn't look like FKM to me.
 
  • Like
Reactions: Haunt3r

Dashwood Foxe

Senior Member
Dec 23, 2014
137
33
That's what stock does too to save your battery health. Also Google OnePlus Optimized Charging.
A bit strange for this when I connect my warp charger, the phone will damnedest cram as much amps into my phone until it reaches 43c then it dials back the current, only to push max 4-6amps again as soon as it drops a degree vs having it cool down a bit further then slowly dial it back up. An exact opposite of preserving battery health.

I know Omega kernel takes greater consideration in charging behavior that it'll only crank the current with the screen off and is in full on doze, doesn't exhibit the 94% trickle when on wireless, strangely enough.
 

kristofpetho

Senior Member
May 27, 2009
5,181
9,886
Zoetermeer
  • Like
Reactions: QanTnkz and osm0sis

mattie_49

Senior Member
Feb 4, 2010
2,931
901
Seymour Tn
OnePlus 9

Dashwood Foxe

Senior Member
Dec 23, 2014
137
33
A bit strange for this when I connect my warp charger, the phone will damnedest cram as much amps into my phone until it reaches 43c then it dials back the current, only to push max 4-6amps again as soon as it drops a degree vs having it cool down a bit further then slowly dial it back up. An exact opposite of preserving battery health.

I know Omega kernel takes greater consideration in charging behavior that it'll only crank the current with the screen off and is in full on doze, doesn't exhibit the 94% trickle when on wireless, strangely enough.
For the record, not suggesting you downrate the charging behavior for I bought this phone because it has 65 watt charging, I expect it to work and milk every advantage it has. Great kernel.
 

eng.stk

Senior Member
Mar 29, 2011
6,891
59,176
OnePlus 5T
OnePlus 6
It's actually a problem with the charger module loading. I had this earlier on Omega as well, it can be fixed with this commit:
What exactly happens?
load stage shouldn't derp thresholds.
Unless there's some race condition in module load order, since we builtin everything.
Sometimes fw is picky about this.
I don't have a wireless charger so can't test any of this.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    blu_spark_r40 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.
    This build have dts changes and since they reside in vendor_boot, you should backup (or extract from stock) not only boot.img but also vendor_boot.img if you want go to stock.

    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Build with Google Clang 12.0.7 + LLD linker (updated)
    • hwtracing: Add entries from lahaina-coresight (tentative less idle draw)
    • Properly enable and fix LD_DEAD_CODE_DATA_ELIMINATION (less image footprint)
    • AnyKernel3 updates sync
    • For root, Magisk 23.0 or higher 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 :)
    7
    Look. I get the throttling concerns, I do, but when you have both the thread OP/dev and another dev asking you all to drop the subject, please do as they ask. This thread has gone way off topic and might have to be cleaned at this point.
    7
    Mate. I'm trying to be as diplomatic as possible.

    This whole situation should Simply Be referred to as: Throttle-Gate.

    I'd really appreciate if you listen to users once in a while.

    There's no good reason why we should allow this phone to get throttled like that. The user experience is severely gimped and diminished.

    With a throttling, we basically have a mediatek 750 SOC.

    For $1,069 device that's nothing short of ridiculous. I've got my S21 Ultra in my hand right next to me-- and the performance is incredible. It's a Snapdragon sd888. No overheating. No excessive drain.

    I've been able to test my 9Pro with the TPD removal, and same exact thing.

    The sd888 is anything but perfect. But having pixel 5 performance on $1,000 device is cutting ourselves off at the proverbial knees.

    Phone is an absolute Joy now to use and feels like a premium device without the throttling. Super fluid. Smooth as smooth can be.

    OnePlus is not god. They make very questionable decisions.

    Really appreciate it if you would simply 'try' building a build without that throttling commit.

    I promise you it's worth it. I've tested both ad nauseam, and extensively.
    Take it to QC and OP, I don't sell phones neither I make client support.
    That tends to be paid it seems.

    You mean the change that introduces heat and battery drop and it was reverted not long ago? And from what I read is not consensual at all?
    C'mon, enough of this mumbo jumbo already.

    You guys can paint it all you want, no matter what you do, it's a loose loose situation with this SoC the way is set on this device. Period.
    Disable the mitigation in place, you got the performance for a bit until device starts to heat up like a furnace (already has a tendency to do it even throttled down lol) and battery soon goes bye bye.
    And if users start coming down in a couple months complaining about silicon degradation, are you the one to provide new phones to them?
    People have to be careful with these things. If other projects want to take another path it's up to them, that's why the code is open source.

    And it's funny you mention the S21, since there's people complaining about battery not being on par with other S iterations and having a tendency to heat up more than usual.
    So much that Samsung is probably bringing back vapor chamber to their lineup which is not present on the S21
    Although some devices behave better than others, there is not a single review with snap 888 I checked that doesn't mention the "device has a tendency to heat up" and the "battery isn't grat"... "but it's ok because snap 888 is a power house".
    I read crap like this more than once. Like the 865 wasn't a powerhouse that was perfectly powerful and efficient lol.

    People may accept what I have to say or not, but that isn't going to change technical (and historical) facts. I'm done with loosing time to this topic.
    The problem isn't OP throttling down the device, the problem is that they needed to do that stuff to have a workable device in the first place.
    If people can't understand this, I rest my case. There's plenty of threads in which people can't vent all they want, I suggest you guys use that ones and don't clutter this topic again.


    TLDR: I will not change anything related to power management on this device. Want to know why, read the rest before lol. The end.
    5
    So with this argument the phone is completely useless and if using basic apps is a disaster what about games what is going to happen phone explodes in our faces !! according to OP not throttling games, so now if phone burns down during warranty the other excuse will be you played too many games not covered !!!
    It's never been "completely useless", this is exactly the type of dramatic overreaction people keep having to this from the media hype machine... 🙄

    He's asked people to drop the topic, so kindly let's all drop it. 🙂✌️
    4
    Electromigration is the cause of semi conductor failures when over voltage/over current along with heat is maintained.

    The metal atoms start to migrate and cause shorts or opens.

    I don't know what QC claims for thermals on a SD888 and I also don't think it's an issue with component failure. I think this whole thing is about battery life.

    I'm not suggesting that OP modify his kernel in any way. I'm a hardware engineer telling what causes silicon to fail.
  • 44
    DWHxIK

    Kernel features: (some WIP)
    • Build with Google Clang version 12.0.7 + LLD linker
    • Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
    • Less is more: stockish OP9 builds based on OnePlusOSS/android_kernel_oneplus_sm8350 for max stability
    • Systemless installer (doesn't touch system/vendor 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 sm8350 patchset
    • No OC, use 300HZ 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, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
    • ZRAM Swap (2GB LZO-RLE default) and with file disabled (2 GB storage gain), LZ4 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 option
    • Gamepad support enabled (xbox, ps4, switch)
    • USB2 Fast Charge (USB mode up to 900mA with MTP on)
    • FS fsync toggle on/off
    • Wakelock blockers available
    • wireguard support
    • Compatible with FKM, EXKM, Kernel Adiutor and others


    DOWNLOAD KERNEL ZIP
    FKM download configs: oos
    (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/vendor_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/vendor_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/op9
    Don't forget to hit thanks, it's free ;)


    OnePlus 9 Pro development unit donated by OnePlus. Big shouts to them :)
    Very proud for being on the OnePlus Developer Program, special thanks to dev relations team.
    24
    blu_spark_r23 release

    First blu_spark build for the OP9 series is up (y)

    This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also (need some fixes since code is broken). So backup you boot if you want to test and let me know :)
    Kernel already have some merged goodies and I think I have a good base to work with. For a couple days of work, it's not bad :)
    I'll take a look into more stuff to come, some things in OP are WIP. Stay tuned!

    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Build with Google Clang 12.0.5 + LLD linker
    • Synchronize codes for OnePlus 9/Pro Oxygen 11.2.6.6.LE25AA
    • Several build error fixes and quirks handled
    • Compilation improvements an cruf removed
    • Some goodies already merged like filesystem stuff, cpu governor & boost/msm perf, TCP algos, wakelock blocker, vibration and haptic feedback control, gpu adrenoboost, etc
    • All drivers builtin, wifi stack and datarmmnet merged from CAF
    • net/wireguard: merge v1.0.20210424


    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 :)
    20
    [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
    14
    blu_spark_r30 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.
    This build have dts changes and since they reside in vendor_boot, you should backup (or extract from stock) not only boot.img but also vendor_boot.img if you want go to stock.

    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Build with Google Clang 12.0.6 + LLD linker
    • defconfig: enable ld deadcode elimination
    • Silence some logging and debug
    • Add a couple dts tweaks
    • Change some runtime inits to improve UX
    • Reduce zram to 2GB and remove swap file (2GB extra storage!)
    • wireguard updates (v1.0.20210606)
    • AnyKernel3 updates sync (including dtb in vendor_boot support and more variants on the installer by @osm0sis)
    • For root, Magsk 23.0 or higher 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 :)
    11
    blu_spark_r40 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.
    This build have dts changes and since they reside in vendor_boot, you should backup (or extract from stock) not only boot.img but also vendor_boot.img if you want go to stock.

    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Build with Google Clang 12.0.7 + LLD linker (updated)
    • hwtracing: Add entries from lahaina-coresight (tentative less idle draw)
    • Properly enable and fix LD_DEAD_CODE_DATA_ELIMINATION (less image footprint)
    • AnyKernel3 updates sync
    • For root, Magisk 23.0 or higher 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 :)