Failing to set "allow" for im.vector.app.debug

[madduck]

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.

[theslimshaney]

Think this is dead, but someone started a fork
https://f-droid.org/en/packages/com.oF2pks.adbungfu
https://bitbucket.org/oF2pks/adbungfupermissionsetter/src/xda
https://forum.xda-developers.com/t/app-root-7-0-runinbackgroundsetter-v1-4-25-07-2017.3637705/post-81660135