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

Add option to choose component blocking method #326

Closed
gnuhead-chieb opened this issue Mar 22, 2021 · 1 comment
Closed

Add option to choose component blocking method #326

gnuhead-chieb opened this issue Mar 22, 2021 · 1 comment
Labels
Feature New feature or request Priority: 3

Comments

@gnuhead-chieb
Copy link
Contributor

AM currently only support IFW for component blocking method.
IFW is the best method for root users but it isn't works for ADB/nonroot users.
so I think it is better to make let users to choice component blocking methods(eg, pm,apk patching(after it is supported in AM)

@gnuhead-chieb gnuhead-chieb added Priority: 3 Feature New feature or request labels Mar 22, 2021
@MuntashirAkon
Copy link
Owner

AM uses both IFW and PackageManager to block and disable components respectively (from v2.5.22) as both methods have been found to have certain weakness (#205), and both are root-only methods. The PackageManager also works for the test-only apps since Android Oreo (I might explicitly enable blocking options for them in future).

APK editing has many risks associated with it. Therefore, the implementation will be a bit different than the usual.

I wish there existed an easier way to control application components. But Google doesn't particularly like apps that prevent other apps from tracking or displaying ads as they have explicitly described in their developer program policies.

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: 3
Projects
None yet
Development

No branches or pull requests

2 participants