Add optional START and STOP intents for automation apps

[kitsumed]

功能描述

I am ShizuCallRecorder developer and have a feature dependant on a Shizuku fork (thedjchi) that has intents to trigger a start and stop of Shizuku (would be Stellar here).

使用场景

Automations applications could implements this for various usages, allowing users to automatically decide when to start or stop Stellar.

My own application, ShizuCallRecorder, would be able to run Stellar only when nessesary, and stop it later. This is useful for the device overall security and because some applications (games and banking apps) detect when you have Shizuku, Stellar, USB Debugging, or even Wireless Debugging enabled.

建议的实现方案

I think there should be two intent, one to START, and another one to STOP.

I think this should be a toggelable feature so users who do not want this can disable it. For more security, I think there should also be a key. The intents would have a extra called auth and Stellar would refuse to do anything, or show an error notification, if the intent does not have that key.

You can see in my own application how I currently handle this.

替代方案

No response

[lovelmxa]

Exposing control through Intents creates a potential abuse risk. Even with some form of authentication token, Stellar cannot verify whether the calling application is acting in good faith.
For example, a game’s anti-cheat component could repeatedly send commands to stop the Stellar service.
Instead, in a future update, we may add separate permissions for individually authorized apps, similar to the existing per-app auto-start setting. Authorized apps could then be allowed to perform specific actions through Intents.