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

Freeze an app with a different method when holding the freeze button #1449

Open
3 tasks done
ghost opened this issue Sep 28, 2024 · 7 comments
Open
3 tasks done

Freeze an app with a different method when holding the freeze button #1449

ghost opened this issue Sep 28, 2024 · 7 comments
Labels
Feature New feature or request

Comments

@ghost
Copy link

ghost commented Sep 28, 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

You should add buttons to the menu that shows when you hold the Freeze button to freeze an app with a different method.

Describe the solution you'd like

Add new buttons to the Freeze/unfreeze menu to freeze an app with a different method.

@ghost ghost added the Feature New feature or request label Sep 28, 2024
@ghost ghost closed this as completed Sep 28, 2024
@ghost ghost reopened this Sep 28, 2024
@shuvashish76
Copy link

shuvashish76 commented Sep 29, 2024

So your feature request is :

  1. Add the freezing method "Suspend, Disable, Hide" options as chips (just like how it's used for "sort" in Main page) for individual apps when you long click "Freeze" option from "Horizontal Action Panel" of "App Info" page, without each time changing default option from "Settings > Rules > Default freezing method"
  2. And under that show all the checkboxs for creating shortcuts as we currently show. (both 1 & 2 in one dialog)
  3. Remember the different Freezing methods used for all the apps.

Note 1 : If you choose one of the "freezing method chip" by long clicking Freeze (doesn't matter if you create shortcut or not) then it would remember the method. So if you close the dialog and simply single-click "Freeze" it'll use user preferred freezing method.


This feature request is similar to how we've freedom of individual configuration for "IFW+Dis, IFW, Dis" component blocking methods, overriding Default options.

Note 2 : Similar to #1201, we already show the correct "Freezing status Tag" for individual apps.

@MuntashirAkon
Copy link
Owner

I've been thinking about this feature myself for quite some time. The problem is the long-click option has already been used for creating shortcuts. I cannot think of a good way to offer both features at the same time.

@MuntashirAkon
Copy link
Owner

3. Remember the different Freezing methods used for all the apps.

This could be problematic though. Because unless there's a way to report to the user about the freezing method used for the app, it might be difficult for them to figure out (in advance) which freezing method is going to be used for this particular app (since we don't expect them to remember the last used freezing method for an app). But, there are also some benefits, especially for batch operations and profiles.

@shuvashish76
Copy link

shuvashish76 commented Nov 9, 2024

it might be difficult for them to figure out (in advance) which freezing method is going to be used for this particular app (since we don't expect them to remember the last used freezing method for an app).

Yes I agree. I thought "Hit-and-Trial" method shouldn't be a problem as you don't lose any data with any of the freezing method.

[From my previous comment

Note 1 : If you choose one of the "freezing method chip" by long clicking Freeze (doesn't matter if you create shortcut or not) then it would remember the method. So if you close the dialog and simply single-click "Freeze" it'll use user preferred freezing method.

]

i. (a) Just click Freeze to check what tag appears on Horizontal action panel. If it's different than your intended method, simply unfreeze and (b) Long click to view/change which chip used for the freezing method.
ii. If you want to know what freezing method is already set before performing the action, then follow i.(b)

@shuvashish76
Copy link

shuvashish76 commented Nov 9, 2024

there are also some benefits, especially for batch operations and profiles.

That would be a different but related feature request...

  • For "Freeze" batch operations, show 4 options in the dialog (Suspend, Disable, Hide and User preferred or something similar name...which would follow your default freezing method set from the AM for all apps + (except) user preferred method set for specific apps). If you choose none of the options and click Freeze then follow only default freezing method set from the AM for all apps.
  • Give similar 4 options for Profiles > open any profile > Configurations > Freeze

@shuvashish76
Copy link

shuvashish76 commented Nov 9, 2024

User preferred or something similar name...which would follow your default freezing method set from the AM for all apps + (except) user preferred method set for specific apps)

If you choose none of the options and click Freeze then follow only default freezing method set from the AM for all apps.

Limitation of my Freeze" batch operations proposal : Suppose you want to use Suspend (which is not your default freezing method) + User preferred method. Then it's not possible with current proposal.

Alternative idea:
image

Edit: Sorry, use chips for Suspend/Disable/Hide.

This way you'll have the freedom to do

  • Only Suspend/Disable/Hide
  • Suspend/Disable/Hide + User preferred
  • If you want to go AM default method then unselect all options and click Freeze.

@MuntashirAkon
Copy link
Owner

i. (a) Just click Freeze to check what tag appears on Horizontal action panel. If it's different than your intended method, simply unfreeze and (b) Long click to view/change which chip used for the freezing method.

Technically, if an app is frozen with any methods, it needs to be unfrozen again before applying any other method. Because App Manager will freeze again with the new method without checking whether it was frozen before. This is because App Manager does not know if it was previously frozen with App Manager (the system does not supply a timestamp for these operations).

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

No branches or pull requests

2 participants