You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Termux is force-stopped by the Android system (such as after device reboots), the RUN_COMMAND intent no longer functions. In this state, the user must manually launch Termux before it can receive any intents. However, startActivity intents continue to work. Therefore, If Termux supports receiving intents via startActivity, client applications could deliver commands without relying on background services. This would eliminate the need for users to manually launch Termux after a reboot or force-stop.
Additional information
n/a
The text was updated successfully, but these errors were encountered:
Feature description
When Termux is force-stopped by the Android system (such as after device reboots), the RUN_COMMAND intent no longer functions. In this state, the user must manually launch Termux before it can receive any intents. However, startActivity intents continue to work. Therefore, If Termux supports receiving intents via startActivity, client applications could deliver commands without relying on background services. This would eliminate the need for users to manually launch Termux after a reboot or force-stop.
Additional information
n/a
The text was updated successfully, but these errors were encountered: