search

MuntashirAkon / AppManager

A full-featured package manager and viewer for Android
https://muntashirakon.github.io/AppManager/
Other
4.97k stars 279 forks source link

changing toggles in app ops and services #1100

Open 2011 opened 1 year ago

2011 commented 1 year ago

Describe the existing feature/documentation

No response

Describe your problem(s)

I have become a little frustrated trying to toggle various app ops and services settings (which seem to not work as well in more recent versions). I have AppManager 3.1.1 installed on all of my devices. For this question, I will use the DuckDuckGo mobile browser (com.duckduckgo.mobile.android). Of note, for Android 6 and 7 devices, I can no longer change any app ops setting (which I still can do from adb). I do recall having the ability to set those before.

More annoying (since I can always change app ops via adb), on Android 6 devices, I can no longer disable any services (disabling services still works with other Android versions). Of particular note, I want to disable androidx.work.impl.background.systemjob.SystemJobService, which allows the application to continually restart. I used to have that disabled, but somehow (I suppose this could always happen via a Google Play Services update, or something similar), it now shows as enabled, and AppManager will not allow me to disable it (the indicator changes to off, but then back on in less than a second). The log doesn't show any activity during attempts to disable this service.

Additional context

No response

MuntashirAkon commented 1 year ago

Try disabling it with pm disable command. If it gets disabled, then there might be an issue with App Manager. All components are disabled in the same way, and only affecting those particular components is very suspicious.

App Manager now sanitises the mode set by the user. Although App Manager allows setting arbitrary mode, not all modes work in all cases and for all ops (for example, setting mode deny or foreground does not work for the op START_FOREGROUND). It also attempts to alter the associated permission which can eventually change the mode again. Setting custom modes can capable of breaking the system unless you have a proper knowledge of how that particular mode work.

54M44R commented 1 year ago

In an attempt to narrow down the issue, it seems the issue began between version 2.6.5.1 and version 2.6.1.

Version 3.0.4 allows one to toggle them properly but in reality it has no effect on the App Ops from what I've seen. Refreshing shows the App Op toggles were not applied.

Version 2.6.5.1 has the same issue seen in version 3.0.4.

Version 2.6.1 does not have issues applying App Ops.

Versions between 2.6.5.1 - 2.6.1 I could not properly test due to them all being stuck "Initializing" or failing to list the apps.

Do note I have little knowledge on App Ops, and the methods that App Manager uses to toggle these App Ops.

Until then, I will be sticking on version 2.6.1 till the issue is resolved.

Given that version 2.6.1 was released roughly two years ago, this seems like a proper issue that needs to be tackled.

2011 commented 10 months ago

Try disabling it with pm disable command. If it gets disabled, then there might be an issue with App Manager. All components are disabled in the same way, and only affecting those particular components is very suspicious.

Sorry I missed this (somehow it just fell off my radar). Yes, using "pm disable" (to disable services) works perfectly (again, this used to work on Android 6 devices).

grasmanek94 commented 7 months ago

Hmm I also seem to be getting 'rules not applied' error, but when I disable it with for example adb shell pm disable com.google.android.gms/.nearby.sharing.DirectShareService the command line says 'success', although the changes are not reflected in the toggles in App Manager? How would I check if this was really successful?

logcat doesn't show any activity for AppManager when toggling a service:

04-08 22:37:27.871  1169  1169 I LayerHistory: io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.details.AppDetailsActivity$_17608#916 Max (can't resolve refresh rate)
04-08 22:37:28.907  1169  1169 I LayerHistory: io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.details.AppDetailsActivity$_17608#916 Max (can't resolve refresh rate)
04-08 22:37:47.785  1169  1169 I LayerHistory: io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.details.AppDetailsActivity$_17608#916 Max (can't resolve refresh rate)
04-08 22:37:47.971  1169  1169 I LayerHistory: io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.details.AppDetailsActivity$_17608#916 Max (can't resolve refresh rate)
04-08 22:37:48.217  1169  1169 I LayerHistory: io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.details.AppDetailsActivity$_17608#916 Max (can't resolve refresh rate)
#######  04-08 22:37:54.305  1385  1994 D MdnieScenarioControlService:  packageName : io.github.muntashirakon.AppManager    className : io.github.muntashirakon.AppManager.details.AppDetailsActivity ####### TOGGLED HERE ####### 
04-08 22:37:57.689  1169  1169 I LayerHistory: io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.details.AppDetailsActivity$_17608#916 Max (can't resolve refresh rate)
04-08 22:37:58.221  1169  1169 I LayerHistory: io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.details.AppDetailsActivity$_17608#916 Max (can't resolve refresh rate)
04-08 22:37:59.162  1169  1169 I LayerHistory: io.github.muntashirakon.AppManager/io.github.muntashirakon.AppManager.details.AppDetailsActivity$_17608#916 Max (can't resolve refresh rate)
04-08 22:38:03.927  1385  1994 D MdnieScenarioControlService:  packageName : io.github.muntashirakon.AppManager    className : io.github.muntashirakon.AppManager.details.AppDetailsActivity
grasmanek94 commented 7 months ago

https://github.com/MuntashirAkon/AppManager/issues/1218#issuecomment-2047430591 maybe this is related