• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread
Hello @eng.stk

Since the revelation about OnePlus throttling several popular apps, I have been wondering – does your kernel inherit the behaviour? If yes, then will it be possible to remove the throttling code?

Thanks for your work, your kernel has much improved my phone's battery life, especially on idle.

Throttles what now?
 

eng.stk

Senior Member
Mar 29, 2011
6,937
59,545
OnePlus 5T
OnePlus 6
Hello @eng.stk

Since the revelation about OnePlus throttling several popular apps, I have been wondering – does your kernel inherit the behaviour? If yes, then will it be possible to remove the throttling code?

Thanks for your work, your kernel has much improved my phone's battery life, especially on idle.
Same as stock.

And then what? What about people that want to run the same as stock because they don't care about benchmarks and UX is good enough for them?
And then also people would complain about heat and battery drain and so on.

This is not an OP9 or even OP problem tbh. The fact is that snap 888 is an overpriced piece of kit.
All other devices that use the SoC face similar heat and poor battery issues, QC just rushed the X1 design and used a very underwhelming 5n process node by Samsung.
Some vendors preferred to let more performance in, mitigating the heat with better cooling and battery go bye bye faster, other disabled cores and throttled stuff like OP via sw mitigation.

This already happened in the past for instance with the worst SoC QC ever released, the snap 810, which was a freakin' furnace and also made on Samsung foundries.
Samsung 5n process is underwhelming even compared to TSMC 7nm, most companies ditched Samsung foundries (ex Apple) in favor of TSMC.
All current high performance/efficiency chips (SOC, CPU, GPU) are with TSMC. Historically, Samsung exynos always was hotter and less efficient than QC counterparts, none of this is by chance.
Seems like QC didn't learn anything from past events. I understand the silicon shortage and TSMC 5nm nodes being fully booked didn't help here, but a top of the line SoC must have higher quality.
And I still don't understand why a smaller node silicon needs so much cooling power to perform up to spec.

Only thing to really fix this device is take the SoC out and put a proper one. But since QC wants to continue using Samsung foundries to next 2 ou 3 models at least, I don't see a future to look to.
If you want to disable the OP task management, you can disable the service that uses the kernel driver, don't even need a custom kernel.

EDIT: in the previous generation, snap 865 has stellar performance (TSMC) and the mid up 765G (similar arch), despite less performant had heat and battery issues compared to the high power flagship.
Google for instance was caught doing similar "optimizations" - read cut down performance - to the Pixel 5 to mitigate the heat and battery issues.
Guess what was the foundry that made the 765G? Starts with an S...
 
Last edited:

tathagatab

Senior Member
Dec 31, 2014
368
135
Kolkata
OnePlus 9 Pro
Same as stock.

And then what? What about people that want to run the same as stock because they don't care about benchmarks and UX is good enough for them?
And then also people would complain about heat and battery drain and so on.

This is not an OP9 or even OP problem tbh. The fact is that snap 888 is an overpriced piece of crap.
All other devices that use the SoC face similar heat and poor battey issues, QC just rushed the X1 design and used a very underwhelming 5n process node by Samsung.
Some vendors preferred to let more performance in and devices heat up and battery go bye bye faster, other disabled cores and throttled stuff like OP.

This already happened in the past for instance with the worst SoC QC ever released, the snap 810, which was a freakin furnace and also made on Samsung foundries.
Samsung 5n process is underwhelming even compared to TSMC 7nm, most companies ditched Samsung foundries (ex Apple) in favor of TSMC.
All current high performance/efficiency chips (SOC, CPU, GPU) are with TSMC. Historically, Samsung exynos always was hotter and less efficient than QC counterparts, none of this is by chance.
Seems like QC didn't learn anything from past events. I understand the silicon shortage and TSMC 5nm nodes being fully booked didn't help here, but a top of the line SoC must have higher quality.

Only thing to really fix this device is take the SoC out and put a proper one. But since QC wants to continue using Samsung foundries to next 2 ou 3 models at least, I don't see a future to look to.
If you want to disable the OP task management, you can disable the service that uses the kernel driver, don't even need a custom kernel.

EDIT: in the previous generation, snap 865 has stellar performance (TSMC) and the mid up 765G (similar arch), despite less performant had heat and battery issues compared to the high power flagship.
Google for instance was caught doing similar "optimizations" - read cut down performance - to the Pixel 5 to mitigate the heat and battery issues.
Guess what was the foundry that made the 765G? Starts with an S...


Thanks for your explanation. Perhaps I'm better off sticking with the OnePlus optimizations. Still, I'd like to see what it's like without the throttling. If I don't like it, I can always return to stock behaviour. What is this service that uses the kernel driver? How do I disable it using FKM or ExKM? Please share your knowledge.
 

Burt Squirtz

Senior Member
Feb 11, 2018
498
178
Hello @eng.stk

Since the revelation about OnePlus throttling several popular apps, I have been wondering – does your kernel inherit the behaviour? If yes, then will it be possible to remove the throttling code?

Thanks for your work, your kernel has much improved my phone's battery life, especially on idle.
It's super easy to fix I'm sure Eng.stk will do it. all he has to do is remove the oneplus TCP commit from the Kernel.

Omega dev has done this. I have not seen any heat issues whatsoever from the un-throttling. It's amazing using the device now. It feels like the device should feel. Almost as fast as smooth as my S21 Ultra.
 
It's super easy to fix I'm sure Eng.stk will do it. all he has to do is remove the oneplus TCP commit from the Kernel.

Omega dev has done this. I have not seen any heat issues whatsoever from the un-throttling. It's amazing using the device now. It feels like the device should feel. Almost as fast as smooth as my S21 Ultra.
He has said many times he was going for stable and not altering source so I think it will remain the same. Also didn't notice much of a difference with throttling removed
 
  • Like
Reactions: GuyInDogSuit
does this work on lineage? i know it says oos

Nope, pretty sure eng.stk has stated this won't work on anything other than OOS.



He has said many times he was going for stable and not altering source so I think it will remain the same. Also didn't notice much of a difference with throttling removed


Yup, this is based on OnePlus source and he's sticking to that. Any other route could possibly lead to Note 7-level disasters (and while he might have been joking [he wasn't], there's no reason to chance that.
 
Nope, pretty sure eng.stk has stated this won't work on anything other than OOS.






Yup, this is based on OnePlus source and he's sticking to that. Any other route could possibly lead to Note 7-level disasters (and while he might have been joking [he wasn't], there's no reason to chance that.
You quoted the wrong person
 

eng.stk

Senior Member
Mar 29, 2011
6,937
59,545
OnePlus 5T
OnePlus 6
So for the (hopefully) last time about the throttling drama:

Guys I understand that the reddit/twitter mindset sometimes takes over xda, but we need to be objective.
People may agree or disagree with OP decision, but this is beside the point.

Like it was discussed earlier, while numbers on synthetic may rise, I don't believe general UX will improve all that much and battery will for sure be worse.
Probably will even introduce jank since OOS is so tightly integrated to some vendor modules.
And further testing seems to suggest just that (check attach)

I praise stability and daily driving above anything else. And I prefer not to break stock stuff if there's no hard reason to do it.
If you're after untested merge and revert nightly style releases, this is not the place for you.

Now please read carefully my original take on this throttling:

Just to compare stuff in a simple matter most users will relate to:
My OP9 Pro running without SIM as a tablet drains the same as the 8T daily driving on the street with a SIM. It's nuts, should be a lot less like my other devices.

TLDR: snap888 is not to the level of efficiency we are used to get from QC. Some models seem to be better than other due to battery tweaking processes, but pushing the envelope a bit and it goes bye bye.
Also you may get a better heat dissipation tech to maintain performance (like vapor-chamber used in some models), but all the devices have the tendency to be hand warmers, because then again the heat is still there, it just dissipates faster.
 

Attachments

  • screen01.png
    screen01.png
    82.7 KB · Views: 156
Last edited:

tathagatab

Senior Member
Dec 31, 2014
368
135
Kolkata
OnePlus 9 Pro
So for the (hopefully) last time about the throttling drama:

Guys I understand that the reddit/twitter mindset sometimes takes over xda, but we need to be objective.
People may agree or disagree with OP decision, but this is beside the point.

Please be smarter than news outlets that just want to live of drama and feed you stuff without explaining nothing.

Like it was discussed earlier, while numbers on synthetic may rise, I don't believe general UX will improve all that much and battery will for sure be worse.
Probably will even introduce jank since OOS is so tightly integrated to some vendor modules.
And further testing seems to suggest just that (check attach)

I praise stability and daily driving above anything else. And I prefer not to break stock stuff if there's no hard reason to do it.
If you're after untested merge and revert nightly style releases, this is not the place for you.

Now please read carefully my original take on this throttling:

Just to compare stuff in a simple matter most users will relate to:
My OP9 Pro running without SIM as a tablet drains the same as the 8T daily driving on the street with a SIM. It's nuts, should be a lot less like my other devices.

TLDR: snap888 is not to the level of efficiency we are used to get from QC. Some models seem to be better than other due to battery tweaking processes, but pushing the envelope a bit and it goes bye bye.
Also you may get a better heat dissipation tech to maintain performance (like vapor-chamber used in some models), but all the devices have the tendency to be hand warmers, because then again the heat is still there, it just dissipates faster.

Does this mean that I can never (or very rarely) activate the prime core on my shiny new phone? That makes me sad.
 

eng.stk

Senior Member
Mar 29, 2011
6,937
59,545
OnePlus 5T
OnePlus 6
Does this mean that I can never (or very rarely) activate the prime core on my shiny new phone? That makes me sad.
Well you can always have a blob of lava in your hands, a couple months/years down the line your device starts bootloop and the only way to boot is disabling high power clusters like with the good 'ol 810 furnace and little furnace brother 808.

People usually think of silicon degredation being tied to voltages, but degredation by sustained exposure to high temperarures is also a thing.

Pretty sure you would be much happier then 🥲
 
  • Like
Reactions: osm0sis

Burt Squirtz

Senior Member
Feb 11, 2018
498
178
Well you can always have a blob of lava in your hands, a couple months/years down the line your device starts bootloop and the only way to boot is disabling high power clusters like with the good 'ol 810 furnace and little furnace brother 808.

People usually think of silicon degredation being tied to voltages, but degredation by sustained exposure to high temperarures is also a thing.

Pretty sure you would be much happier then 🥲
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.
 
  • Like
Reactions: Shooter7889

eng.stk

Senior Member
Mar 29, 2011
6,937
59,545
OnePlus 5T
OnePlus 6
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.
 
Last edited:

chrmica

Senior Member
Dec 4, 2011
68
6
OnePlus 9 Pro
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.
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 !!!
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,814
33,489
Halifax
GT-i9250
Nexus 7 (2013)
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. 🙂✌️
 

samwhiteUK

Senior Member
Jul 1, 2012
124
42
Cambridge
OnePlus 9 Pro
If you want a kernel that removes the throttling, use an Omega build that does so. Eng.stk is obviously cautious, and it's his/her project, so he/she can do as he/she pleases. You don't have to be loyal to a particular dev, just like a dev doesn't have to give in to your requests. It's quite rude to keep trying to persuade a dev to do your bidding, when there is another project out there that accomplishes just what you want.
 

infamousvincci

Senior Member
Apr 10, 2013
1,444
332
Carson
OnePlus 9
OnePlus 9 Pro
Well you can always have a blob of lava in your hands, a couple months/years down the line your device starts bootloop and the only way to boot is disabling high power clusters like with the good 'ol 810 furnace and little furnace brother 808.

People usually think of silicon degredation being tied to voltages, but degredation by sustained exposure to high temperarures is also a thing.

Pretty sure you would be much happier then 🥲
I would agree. Voltages dont cause a cpu to break. Its the heat. And yes, im a cpu overclocker.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Blu.Spark r44 installed on 11.2.9.9 (9 pro) and all seems good.
    It also works fine on the OP9 (11.2.9.9).
  • 51
    DWHxIK

    Kernel features:
    • Build with Google Clang version 13.0.1 + 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.
    26
    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
    15
    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 :)
    15
    blu_spark_r44 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 13.0.1 + LLD linker
    • Synchronize codes for OnePlus 9/9Pro Oxygen 11.2.8.8.LE25AA
    • Add a couple build improvements
    • Remove some debug and logspam
    • lz4 fixes
    • zram and zsmalloc updates and fixes
    • AnyKernel3 updates (v20210721)
    • 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 :)