ADB Connect Service

Certain features of the apps require that root or ADB privileges are available as soon as the device reboots. For instance Permission Watcher, Scheduled Checks and Process Watcher. But if ADB has not been enabled by the time the app starts after boot, the app will no more try to connect to ADB unless explicitly done by opening the app.

There's a solution. If you enable ADB on boot in an automated way, you can notify the app by sending the following Intent that ADB has been enabled:

am startservice -a PKG_NAME.action.ADB_CONNECT -d adb://:5555

where PKG_NAME is the package name of the app and 5555 is the ADB port. You can also pass the host along with the port like adb://127.0.0.1:5555.

For Backopier, the command should be:

am startservice -a com.mirfatif.backopier.action.ADB_CONNECT -d adb://:5555

Tip

Read here how to use the am tool to start an app's service.

You can also try am start-foreground-service if am startservice not works.

Make sure to use the correct package name depending on the app and its version (see PMX versions and WhatsRunning versions).

Here's a list of package names:

• PMX
  • Free / Play Store Pro: com.mirfatif.permissionmanagerx
  • Standalone Pro: com.mirfatif.permissionmanagerx.pro
• WhatsRunning
  • Play Store Free: com.mirfatif.whatsrunning.ps
  • Play Store Pro: com.mirfatif.whatsrunning.ps.pro
  • Standalone Free: com.mirfatif.whatsrunning
  • Standalone Pro: com.mirfatif.whatsrunning.pro
• Backopier: com.mirfatif.backopier

Note

Unattended ADB connection works only if you've already checked the "Alway allow from this computer" option while allowing USB debugging to the app. See Connect the app to ADB.