MuntashirAkon
More features for running apps menu
Please check before submitting an issue
- [x] I am using the latest version of App Manager
- [x] I have searched the issues and haven't found anything relevant
- [x] I have read the docs
Describe a description of the new feature
- I would like to be able to stop applications in adb mode differently, e.g. kill -9/15/2/1/1/3 etc.
- 1 (SIGHUP) - process restart (e.g. daemons).
- 2 (SIGINT) - soft shutdown (safe kill)
- 3 (SIGQUIT) - core dump.
- 9 (SIGKILL) - forced kill (cannot be intercepted).
- 15 (SIGTERM) - correct termination (default in
kill). - 17/19/23 (SIGSTOP) - suspend process (as
Ctrl+Z). - 18/25 (SIGCONT) - resume a stopped process.
- 10/30 (SIGUSR1), 12/31 (SIGUSR2) - user signals for programmes.
There is an am kill
-
In addition, I would like to be able to stop only a process and not all application processes (This is done with the kill command, not am kill)
-
I would like to be able to cancel background prevention for applications that have background prevention enabled.
-
Add an option to update the list or auto-update the list of processes in the "running applications" section
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
And here is an example of using the kill command: For example, if you start screen recording with the screenrecord command and just stop it with kill, the recording file will be destroyed and if you stop it safely with kill -SIGINT
- I would like to be able to stop applications in adb mode differently, e.g. kill -9/15/2/1/1/3 etc.
You cannot kill a process in ADB mode (for any UID other than 2000). It requires superuser permission. But yes, for rooted users, such advanced kill could be added. AFAIK, am kill basically lists all the processes under the UID denoted by the package and kills them all. This could've been added in place of kill in ADB mode, but it was not considered, because force-stopping is more effective for packages anyway. (Since Android processes are started by Zygote, killing an Android process will most likely restart it instead of actually killing it permanently. Force-stop, as a result, is more like killing processes in Linux processes.)
- I would like to be able to cancel background prevention for applications that have background prevention enabled.
- Add an option to update the list or auto-update the list of processes in the "running applications" section
These features are already available. You can prevent background operation by clicking the three-dots menu next to the Android process or in batch mode. The contents of the running apps page are reloaded automatically every 10 seconds (which is standard in many process viewer applications).
I have the "kill" command working without root. Some processes cannot be stopped without root, but those that can be stopped without root can be stopped with "kill".
To stop all processes related to a package, you can use: killall <arguments> <package>
But only I don't know about the effectiveness of am kill compared to kill and killall on different devices