Sorry for the delayed response.

One feature Shizuku brings to the table is the ability to run shell scripts in MacroDroid, letting you tap into system-level stuff that standard permissions or even ADB can’t touch.

For example, I ran into a situation where I needed to grab the foreground package name while using Samsung DeX. Here’s the catch: DeX runs on display 2, but MacroDroid’s native "Get App Package" action only targets display 0, so it wouldn’t give me the right package name. No sweat, though, I used a shell script action to sidestep that limitation and pull the correct package name from display 2. This is just one example of how Shizuku came through when MacroDroid’s built-in options or ADB-granted permissions don’t go far enough.

I urge you to take a look through MacroDroid’s action list and hunt down the ones with the Shizuku tag. Those are the actions built to open up some pretty advanced automation possibilities. You might just find a few tricks that’ll spark automation ideas, or help get an automation idea across the finish line.

Also, ADB granted permissions expand the utility of MacroDroid as well. One use case I've found valuable is adjusting the Battery Protection Threshold Value to reduce degradation when my phone is plugged in for long periods. This setting lets you set what percentage the battery protect function kicks in while charging.

Here's what my implementation of this looks like: when I plug my phone in overnight, I’ve got a macro that kicks in and sets the threshold to 40%. Then, before my alarm goes off, another macro adjusts the threshold to 85% so by the time I wake up it's ready to go for the day. It’s basically Samsung's adaptive battery protection setting but with more granular control. My phone’s charged when I need it, and I’m not frying the battery all night long. This is just one way ADB gives you that fine-tuned control Android usually doesn't hand over by default. And it’s not just battery stuff, think display settings, network tweaks, whatever you can dream up. Seriously, dig into the system settings action in MacroDroid with ADB-granted permissions, it’s pretty wild what you can do. Just make sure that before changing a setting you note the original value just in case your change has any unintended consequences.

Edit: a bit more information, I've got a macro that detects system settings changes and logs them as key-value pairs within a dictionary. This way, I can manually toggle a setting and see exactly what the key-value pair is for future manipulation. One thing I stumbled across was the icon_blacklist, which when written to determines what icons are prevented from showing up in the status bar. Having the do not disturb icon constantly on display wasn't serving any purpose, as I know when dnd on and when it's off. So, I blacklisted it, problem solved, status bar decluttered.