mrbimc / runinbackgroundpermissionsetter Goto Github PK

Please Add ADB Support

Hi ! I use your app and thank you for your work. I had a mistake with Facebook and Instagram app !? I had App's inn drawer and when I place it in my springboard the App's won't stay ? I search why ?
I use Substratum but I remove theme and it's not Substratum.
I use OnePlus Launcher and test it with Nova and the same won't stay in my springboard.
I don't know if are the background restrict ? I use greenify too.
Thanks

The app works fine and I seem to be able to control the setting for most of the other apps.

However, I spotted one app for which it does not work: "Element dbg", aka im.vector.app.debug.

If I flip the switch for that app to "allow", then the RUN_IN_BACKGROUND permission is removed from the output of cmd appops get im.vector.app.debug:

hero2lte:/ # cmd appops get im.vector.app.debug                                      
VIBRATE: allow; time=+1m37s980ms ago; duration=+763ms
READ_CONTACTS: allow; time=+73d3h1m15s212ms ago
WRITE_SETTINGS: default; rejectTime=+26d6h41m15s753ms ago
CAMERA: allow; time=+26d6h40m57s246ms ago; duration=+18s579ms
TAKE_AUDIO_FOCUS: allow; time=+26d6h41m16s385ms ago
WAKE_LOCK: allow; time=+1m26s416ms ago; duration=+16s16ms
TOAST_WINDOW: allow; time=+12d18h9m28s55ms ago; duration=+2s510ms
READ_EXTERNAL_STORAGE: allow; time=+11m38s1ms ago
WRITE_EXTERNAL_STORAGE: allow; time=+11m38s1ms ago

hero2lte:/ # cmd appops get im.vector.app.debug RUN_IN_BACKGROUND                    
No operations.

If I flick it back to "ignore", then the permission is set correctly:

hero2lte:/ # cmd appops get im.vector.app.debug RUN_IN_BACKGROUND
RUN_IN_BACKGROUND: ignore

I can use the adb command line to set "allow", and when I load your app, the state is correctly reflected upon load. But for some reason, the app fails to set "allow" for just "Element dbg", whereas I have been unable to reproduce this problem with any other app setting.

Many Android phones allow ADB over network.

I don't know if adb itself can be embedded but it it can, then you can trivially connect to localhost:5555 and run the required commands.

Which means your app may work without root.

well i restrict whatsapp in app
but still receiving msgs in background..

I get the "there was an error setting...." even though the permission is set correctly (checked restarting app and also calling appops get com.package.name RUN_IN_BACKGROUND from a root terminal emulator).
When using a terminal emulator i don't get any output to stdout, so I don't see where the bug in the code is.
It may be a good idea to add the result ofoutputString.trim() in the toast when !isSuccess.
Using rooted stock Android 8.0 in a Nexus 5X

BTW, great app!

This app is genius, if it could be applied to other permissions as well (internet permission for WiFi and data can be restricted as well on Nougat) it could become a pretty good privacy manager, unifying both a much more simple way of managing AppOps/PrivacyGuard and the easiness of backing up and restoring allowed and denied permissions with apps like TitaniumBackup, Helium, etc. which cannot be used for AppOps or LineageOS's PrivacyGuard.

I'm using OnePlus 8 and this app is not even starting