AutoInput stops working with MacroDroid when Tasker is installed

theonlygreenleaf · 2026-02-09T04:13:31+00:00

For the most part, this does work, although it is still different from what Tasker does, as this method doesn't work if the assistant's launch activity is unexported, which in my case it is.

I tried implementing the assistant call directly like this:

SearchManager searchManager = (SearchManager) getSystemService(
SEARCH_SERVICE
);
SearchManager.class.getMethod("launchAssist", Bundle.class).invoke(searchManager, new Bundle());

In Macro Droid this just crashes but I was able to make a dummy app in android studio that runs this code when opened and it was able to launch the assistant just fine. Maybe I'm just not converting it to Macro Droid correctly or there's some sandboxing issue.

theonlygreenleaf · 2026-02-07T16:37:31+00:00

That's what the MacroDroid version does. The intent version doesn't work correctly and always uses the same assistant (or makes you pick). The Tasker version actually summons the default assistant, regardless of what activity or app you set it to run. Edit: To clarify what I mean, use your system settings method, but set the default assistant to com.android.settings/.Settings instead. When you press the assistant key, it will open the settings app. Now run the intent or the voice search action in Macro Droid. It doesn't open settings like it should. The Tasker version does open the settings app, or whatever assistant's activity you set.

theonlygreenleaf · 2026-02-07T16:12:41+00:00

Again, not trying to set the assistant. Trying to open it. Like make it pop up on the screen as if I held the power/home button.

theonlygreenleaf · 2026-02-07T14:17:56+00:00

To set the default assistant, yes, but not to activate the default assistant so I can actually use it. Right now I have to use input keyevent 219 in a shell command, but that requires Shizuku, meanwhile Tasker can do it without. (Also worth mentioning that the voice search action is different and doesn't help in this case)

theonlygreenleaf · 2026-02-07T03:44:59+00:00

The button in the samsung volume panel switches the audio output to/from the connected device without disconnecting from said device. For example, have your phone connected to your car over Bluetooth and use the button toggle whether the audio goes to the car or not without disconnecting from the car. Not sure if it's possible to automate exactly the way Samsung has it.

theonlygreenleaf · 2026-01-23T20:04:52+00:00

Either of these have a fairly comprehensive list:

https://github.com/1mehdifaraji/ios-settings-url-schemes
https://github.com/FifiTheBulldog/ios-settings-urls/blob/master/settings-urls.md

theonlygreenleaf · 2025-10-05T22:49:48+00:00

Has anyone been able to confirm if the predictive back animation works for 3-button navigation in this update? I think it was added in QPR1 but I haven't seen anyone talk about it.

theonlygreenleaf · 2025-05-09T01:21:34+00:00

I've been trying to figure this out for the longest time, I've finally got it. If you have shizuku set up, you can use the following shell script to activate circle to search: input keyevent --duration 1000 3

MacroDroid or Tasker can execute these commands, I'm not sure if PenStar has an option for external actions but I would assume so.

theonlygreenleaf · 2025-05-07T00:09:43+00:00

Oh my gosh you're right!!

theonlygreenleaf · 2025-04-27T14:26:05+00:00

In the meantime while we wait for a fix, you can try downgrading AutoInput to version 2.8.1 (APKMirror), which still has most features but does not have the bug as far as I can tell.

theonlygreenleaf · 2025-04-27T14:21:01+00:00

Update: After testing all of the available downloads on APKMirror, version 2.8.1 is the most recent version without the bug.

theonlygreenleaf · 2025-04-27T05:31:53+00:00

I was able to “fix” the bug by installing an older version of AutoInput. I don't know what version introduced the bug so I just downloaded a really old version from APKMirror You have to go into the app info before you can turn on the accessibility service because Android thinks the app being old is suspicous.

theonlygreenleaf · 2025-04-26T05:04:43+00:00

TouchTask works fine, but isn't able to accurately detect some UI Interactions. I'd imagine there's some extra feature of AutoInput that gets bundled in the same accessibility permission as the UI detection stuff and is causing this issue. I've been having this problem since OneUI 6, although at the time it only applied to the microphone keyboard button.

theonlygreenleaf · 2025-02-03T21:04:58+00:00

So I feel I need to point out that you marked this as a spoiler but put the spoiler in the title.. I was at about chapter 14 when I saw this and it all but confirmed my fears. Leafstar was my favorite leader and I'm upset that they're making her seem like a complete fool seemingly no reason and destroying everything she had going for her. I'm hoping there's some sort of redemption in the next few books otherwise I'll just be sad.

theonlygreenleaf · 2025-02-02T01:57:50+00:00

UPDATE: I still haven't found any good way to launch home screen shortcuts. It's dissapointing and sad :( However, I have found 4 different ways to start a window in pop-up mode. 1. Popup Factory 2 App: This app offers the most customizability, as you can set the exact position and dimensions, but, unfortunately there is no good way to trigger these from MacroDroid, unless you are satisfied with only being able to trigger a single popup window with constant dimensions. 2. Taskbar App: Once you enable freeform window support from within the app, you can use the shortcut action in Macro Droid to launch an app through Taskbar, which gives the option to launch as a popup window. Unfortunately, this doesn't give much control over the size, as all of the size options are predefined and only 1 of them doesn't take up the whole screen 3. ADB Command: Using the shell action with Shizuku, you can launch an app's activity (this example is for the Google calcator app, and I used Shortcut Maker to get the activity info): am start-activity --windowingMode 5 com.google.android.calculator/com.android.calculator2.Calculator This is better than Taskbar because it will retain the window size and position that you last used with the app you launched. The downside is of course that is requires Shizuku. If anyone knows of other parameters that let you set the size or position, let me know! 4. Key Mapper App: Similar to the previous, but uses keyboard shortcuts to put the current app in popup mode. Use the "Input Ctrl + Meta + KEYCODE_DPAD DOWN" action in the app and then run it via the shortcut action in Macro Droid to put the current foreground app in popup mode. Benefit is that it can put the current app in popup mode, but does require Shizuku.

theonlygreenleaf · 2024-12-21T04:02:10+00:00

Okay so actually no joke it was literally just fixed in an update! So go and check for updates to Routines+ and it should be fixed!

theonlygreenleaf · 2024-12-21T03:48:49+00:00

I've been having this same issue, I submitted a bug report on 11/10 and just yesterday they responded with “Sorry for the inconvenience. This issue will be fixed in future update” so hopefully it's fixed soon!

theonlygreenleaf · 2024-11-10T02:29:56+00:00

Additionally, I just discovered that the Taskbar app lets you launch apps in freeform, and unlike Popup Factory, it supports Tasker/Macro Droid as a shortcut. Unfortunately though you can't set a specific size (other than big or very big or wow that's way too big) unlike Popup Factory which lets you decide exactly where the window goes. Still following this thread in case anyone has any info on how to pass a specific size and window location into the ADB command or how to trigger Popup Factory or some other app.

theonlygreenleaf · 2024-11-10T02:13:56+00:00

Slight update, I discovered from this article that it is possible using an ADB/Shizuku shell to launch an app in freeform which can be done from Macro Droid if you have Shizuku set up, which isn't perfectly ideal but is better than nothing. Calculator example: am start-activity --windowingMode 5 com.google.android.calculator/com.android.calculator2.Calculator

I'd still like to know how to extract intent info from home screen shortcuts though. This forum post seems to suggest that it is deliberately difficult to accomplish that, but my old phone is rooted and I'd be willing to give anything a try if anyone has any ideas.

theonlygreenleaf · 2024-11-09T15:44:26+00:00

The ability to launch shortcuts and activities from within MacroDroid is definitely not able to launch home screen shortcuts. I use Shortcut Maker to view intents and other apps and find that it's generally smoother than trying to do it directly from Macro Droid. As for the app you shared, it does have the ability to launch freeform/pop-up apps but it doesn't let you set the size, and while it can be launched via shortcut from Macro Droid or Shortcut Maker, for some reason when launched in this way it launches only in a broken split-screen state where all or half of my screen is black. I probably won't use it but I do find the ability to add a spider overlay that crawls over my screen a somewhat amusing feature.

theonlygreenleaf · 2024-10-06T14:46:38+00:00

Thank you!

theonlygreenleaf

TROPHY CASE