Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verbose Output #1470

Open
3 tasks done
deadlevel13 opened this issue Nov 16, 2024 · 1 comment
Open
3 tasks done

Verbose Output #1470

deadlevel13 opened this issue Nov 16, 2024 · 1 comment
Labels
Feature New feature or request Priority: 4

Comments

@deadlevel13
Copy link

deadlevel13 commented Nov 16, 2024

Please check before submitting an issue

  • I am using the latest version of App Manager
  • I have searched the issues and haven't found anything relevant
  • I have read the docs

Describe a description of the new feature

I'm always frustrated when doing long activities, there is nothing to show clearly what the app is doing, so if it fails, you just stuck there not know what to search to fix for
Example:

  • When force stop many (like 200-300 apps), the only thing that show it is running is a nofication says "Force stop a/b", then when it killed something bad, how do i know which app that action just run on?

There is way more stuff that can be improved by showing more stuff on what the app is doing, like the installer menu (a small text to show what it is doing now) or failed actions (show a nofication that have the command and the failed message below it)

Describe the solution you'd like

Add a advanced options in the setting that when enabled, show more verbose stuff about what it is running, like the example changed to "Force stop | am force-stop com.tencent.ig 30/300" or something like that

Describe alternatives you've considered

No response

Additional context

No response

@deadlevel13 deadlevel13 added the Feature New feature or request label Nov 16, 2024
@MuntashirAkon
Copy link
Owner

I'm always frustrated when doing long activities, there is nothing to show clearly what the app is doing, so if it fails, you just stuck there not know what to search to fix for

When it fails, there will be a failure notification which you can click to view the details and an option to try again. There's no need to constantly look at it.

When force stop many (like 200-300 apps), the only thing that show it is running is a nofication says "Force stop a/b", then when it killed something bad, how do i know which app that action just run on?

Force-stop operation is very fast. You won't even get a time to notice the apps it is operating on.

There is way more stuff that can be improved by showing more stuff on what the app is doing, like the installer menu (a small text to show what it is doing now) or failed actions (show a nofication that have the command and the failed message below it)

App Manager does not use those unreliable commands, it uses Binder calls for most operations, same as what Android itself does. As I've said above, you get a failure notification when the operation finishes, and you can find which apps were failed along with logs and an option to try again.

More advanced features will be available in the future, but for simple and fast operations, the amount of details will likely remain the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature or request Priority: 4
Projects
None yet
Development

No branches or pull requests

2 participants