AxManager

English

简体中文

English

简体中文

Appearance

FAQ ​

Many manufacturers have made modifications to the Android system that prevent AxManager from working properly.

Start via wireless debugging: keeps showing "Searching for pairing service" ​

Please allow AxManager to run in the background.

Searching for pairing service requires access to the local network, and many manufacturers disable network access for apps as soon as they become invisible. You can search the web for how to allow apps to run in the background on your device.

Start via wireless debugging: immediately fail after tapping "Enter pairing code" ​

MIUI (Xiaomi, POCO)

Switch notification style to "Android" from "Notification" - "Notification shade" in system settings.

Start via wireless debugging/Start by connecting to a computer: the permission of adb is limited ​

MIUI (Xiaomi, POCO)

Enable "USB debugging (Security options)" in "Developer options". Note that this is a separate option from "USB debugging".

ColorOS (OPPO & OnePlus)

Disable "Permission monitoring" in "Developer options".

Flyme (Meizu)

Disable "Flyme payment protection" in "Developer options".

Start via wireless debugging/Start by connecting to a computer: AxManager randomly stops ​

All devices

  • Make sure AxManager can run in the background.

  • Do not disable "USB debugging" and "Developer options".

  • Change the USB usage mode to "Charge only" in the "Developer options".

    • On Android 8, the option is "Select USB configuration" - "Charge only".
    • On Android 9+, the option is "Default USB configuration" - "No data transfer".

  • (Android 11+) Enable "Disable adb authorization timeout" option

EMUI (Huawei)

Enable "Allow ADB debugging options in 'Charge only' mode" in "Developer options".

MIUI (Xiaomi, POCO)

Do not use the scan feature in MIUI's "Security" app, since it will disable "Developer options".

Sony

Don't click the dialog shows after connecting the USB, because it will change USB usage mode.

An app says Shizuku is not found ​

  1. Turn on Settings → AX-Permission Intercept while AxManager is running.
  2. Some older Shizuku clients (for example older versions of ZArchiver) only connect when the Shizuku app is installed. Install it; it doesn't need to be started.

See Shizuku compatibility.

The Shizuku app says an update is needed ​

This is expected. When AxManager serves the Shizuku app, the server version it reports is 13.<AxManager version code>, which no real Shizuku release matches, so the Shizuku app shows its update note. Nothing needs updating.

axsh says "AxManager permission required" ​

The terminal app isn't allowed. Set it to Allowed in Privilege, or leave it on Ask and allow it in the dialog that appears; axsh waits for your answer for up to 15 seconds. If it is set to Denied, no dialog appears. See Run in any terminal.

axsh says "AxManager server is not running" after swiping AxManager away ​

In shell mode, axsh asks AxManager for the server, so AxManager has to be started in the background. Some systems, MIUI / HyperOS in particular, kill apps swiped from recents and block them from being started again. AxManager allows its own Autostart on MIUI / HyperOS when it connects to the server; if the message persists, allow Autostart (or "run in background") for AxManager in the system settings. See How it connects.

An app-op shows a raw name like MIUIOP(10050) ​

It is a permission your ROM added, and the ROM gives it no name AxManager can read. AxManager shows it by its number so you can still change it. Names exist only for the few it knows, and only on the ROM they belong to, because another brand can use the same number for something else. See Other app-ops.

Plugins keep running after the server stops ​

That is the default: plugins run on their own once started. To stop every plugin's processes whenever the server stops or dies, turn on Settings → Stop plugins with the server. See Plugin processes.

Where are the plugin logs? ​

post-fs-data.sh and uninstall.sh write their output to $AXERONDIR/logs/<id>.post-fs-data.log and $AXERONDIR/logs/<id>.uninstall.log:

  • Root mode: /data/adb/axeron/logs
  • Shell mode: /data/user_de/0/com.android.shell/axeron/logs

Output of service.sh is not kept; redirect it to a file yourself if you need it. Installing a plugin and running its action show their output on screen, with a button to save the log.