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
I have searched the issues and haven't found anything relevant
I have read the docs
Describe a description of the new feature
Some applications evades user privacy, but a user usually has no choice but to use it. In such cases, the best a user can do is run the application with limited/temporary permissions or settings that will be reverted after it is closed again, thus, preventing some background tracking. While this may be useful for people with certain threat models, this, in general, will not replace the necessity of an isolated profile.
Describe the solution you'd like
A separate page for managing rules for each app launch. A user should be able to configure what to do when the app is being launch and upon closing it. The list of operations they can do could be similar to the profiles, but the following features should be given more importance:
Freeze/unfreeze
Force-stop
Settings (e.g., enable/disable developer settings, USB debugging, etc.)
A user should have the ability to create a launcher shortcut for these configurations so that they can launch the app with the controls enabled. In some versions of Android, it may be possible to actually apply the settings automatically by monitoring running processes. While usage access may also be used in old platform, the API is not reliable, therefore, may have an impact on the battery usage.
The user should also be able to configure these options directly from the App Info tab of an app.
Describe alternatives you've considered
For most tasks, profiles can be used. However, this unnecessarily increase the workflow. Because the user, at first, have to apply a profile and then launch the app (and do the same thing again after closing the app). For quick freeze/unfreeze, the freeze/unfreeze shortcut can be used, but is not very reliable. Finally, App Manager currently provides no way to modify system settings during an app launch (or closing) even with profiles.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Please check before submitting an issue
Describe a description of the new feature
Some applications evades user privacy, but a user usually has no choice but to use it. In such cases, the best a user can do is run the application with limited/temporary permissions or settings that will be reverted after it is closed again, thus, preventing some background tracking. While this may be useful for people with certain threat models, this, in general, will not replace the necessity of an isolated profile.
Describe the solution you'd like
A separate page for managing rules for each app launch. A user should be able to configure what to do when the app is being launch and upon closing it. The list of operations they can do could be similar to the profiles, but the following features should be given more importance:
A user should have the ability to create a launcher shortcut for these configurations so that they can launch the app with the controls enabled. In some versions of Android, it may be possible to actually apply the settings automatically by monitoring running processes. While usage access may also be used in old platform, the API is not reliable, therefore, may have an impact on the battery usage.
The user should also be able to configure these options directly from the App Info tab of an app.
Describe alternatives you've considered
For most tasks, profiles can be used. However, this unnecessarily increase the workflow. Because the user, at first, have to apply a profile and then launch the app (and do the same thing again after closing the app). For quick freeze/unfreeze, the freeze/unfreeze shortcut can be used, but is not very reliable. Finally, App Manager currently provides no way to modify system settings during an app launch (or closing) even with profiles.
Additional context
N/A
The text was updated successfully, but these errors were encountered: