Context:
I use automation apps to initiate commands.
The Termux app has a feature called RUN_COMMAND intent to launch commands from other apps, and I use this to use adb in Termux while it runs in the background.
However, I would prefer to do this in a simpler app like aShellYou that's just focused on adb, without all the other tools that Termux comes with.
There's another app called ShizuTools that has something called IntentShell that receives intents to do commands, but unfortunately I think that one only works on the local device.
Solution:
Implement the ability for aShellYou to receive intents for initiating local or wireless debugging commands. Even better, with an option to have this happen in the background.
Context:
I use automation apps to initiate commands.
The Termux app has a feature called RUN_COMMAND intent to launch commands from other apps, and I use this to use adb in Termux while it runs in the background.
However, I would prefer to do this in a simpler app like aShellYou that's just focused on adb, without all the other tools that Termux comes with.
There's another app called ShizuTools that has something called IntentShell that receives intents to do commands, but unfortunately I think that one only works on the local device.
Solution:
Implement the ability for aShellYou to receive intents for initiating local or wireless debugging commands. Even better, with an option to have this happen in the background.