ADB Application Manager Pro v7.19.3

A release on top of v7.19.2, cut from main, with the changes the owner asked for on 2026-10-29: a new app icon, the ADB Stub opening on a watch as soon as it connects and showing the watch's IP address and port, and an app's permissions, app ops, activities, components and manifest for the apps of a connected device. Package, signing certificate, APK file names, permissions and the name under the icon (ADB/Root Toolbox) are unchanged, so it installs over every earlier version. Nothing in it has been run on a phone or a watch; the icons were checked under the circle, squircle and rounded-square launcher masks and the pages in a headless browser with a mock, the Java by the Java suite and a build against Android 34. docs/PHONE-SCRIPT-v7.19.3.md is the phone script.

• New app icon: the Android robot, in glasses and a tie, in a blue toolbox with a wrench. It has no background: no tile or colour behind it on the home screen, in the app drawer, in Settings → Apps or in the recent apps. On Android 8 and later it is an adaptive icon whose background layer is see-through and whose picture stays inside the safe zone, so the launcher's shape (circle, squircle or rounded square) never cuts the lid, the antennas or the wrench; the older icon files (every density) and the round icon are the same picture. With no tile of its own the picture can look a touch smaller than icons drawn edge to edge.

• About tab shows the new icon (in place of the lightning bolt on a coloured tile), and so do the README, the website's tab icon and the About screenshots in the guide. The small one-colour icon in the status bar, on the quick tiles and in notifications stays the bolt: Android draws those as a plain white shape, and the toolbox picture would turn into a blob there.

• The ADB Stub opens on the watch as soon as the watch connects. In Connected Devices, a Wear OS watch with the stub installed gets it started the moment it connects: also when another device is the one chosen in the picker (the new watch is asked once whether it is a watch), and also when it still has the previous stub (version 2), which lets go by itself when the phone goes away. Only the very first stub, which does not, still waits for Update. Start ADB Stub on connect in the device menu still switches it off.

• The ADB Stub shows the watch's IP address and port. The stub (now version 3, offered as Update to a watch with an older one) shows IP: and Port: in bold under its state: the address the watch has on Wi-Fi and the adb port this phone reached it on, which the phone now sends when it starts the stub. When the watch connects again on another port while the stub runs, the phone tells the stub the new one at once, and with every renewal after that. Over the Bluetooth link, or when the stub is started by hand, it shows the port the watch reports itself, or unknown.

• On the watch the ADB Stub is now called ADB Toolbox and has the new icon. On the watch's app list, at the top of its screen and on its notification it is named ADB Toolbox (it is still the ADB Stub card in Connected Devices on the phone), with the same robot in a toolbox as this app on the phone (the same files, with no background) in place of the green link tile. Its notification keeps a plain white shape, now the same lightning bolt as this app's notifications on the phone. It comes with stub version 3, so a watch gets it with the Update above.

• App details for the apps of a connected device. An app's three-dot menu in Connected Devices → Apps has Permissions, App Ops, Activities, Components, Manifest and Details, which open the app in the same sheet as an app of this phone in the Application Manager, with the same tabs, filters, search and maximize button that makes a tab fill the screen (Back comes out of it):

  • Permissions: grant and revoke runtime permissions on the device (pm grant / pm revoke), read back afterwards; app-op permissions such as Display over other apps are switched through their op; install-time ones are locked.
  • App Ops: Allow, FG, Ignore, Deny or Reset for each op (the uid's mode too when it has one), read back with Android kept ... at ... when the device kept another mode; any other op by its name.
  • Activities: LAUNCH opens a screen of the app on the device itself, on a watch with its screen woken first; DISABLE / ENABLE.
  • Components: receivers, services (with STOP) and providers, exported or not, and switched on or off.
  • Manifest: the AndroidManifest.xml read straight from the APK on the device (a pulled copy on Android 8 and older, deleted afterwards; a copy that breaks off part-way, or is stopped, shows adb's reason and is never read as a manifest), with find, Copy, Share and Save to Downloads. Features marks what the device has (pm list features); Libraries and Raw (the device's dumpsys package) complete it.
  • What Android lets only root or the system do (switching a part of an app, opening an unexported activity) is tried once more through the device's su when it has one; otherwise the app says so and nothing changes. A part of a system app asks first. Details now opens this sheet on its Raw tab.

• App Ops read the uid's modes right, here and in the Application Manager. Since Android 10, cmd appops get lists an app's uid-level modes first but marks only the first of them, so every other uid-level mode was shown, and set, as the app's own (and the app's own mode for that op was dropped). The uid's list is now read as well (cmd appops get <uid>) to tell where it ends, so each op shows its mode with its uid: note, and setting an op also sets its uid mode when it has one.

• Four icon-only buttons have a name for screen readers:

  • the ✕ on the drift banner (Dismiss)
  • the ✕ on the File Manager's selection bar and on its copy/move bar (Cancel)
  • the archive viewer's ⋯ (Menu)

  They come from the owner's accessibility review (buttons_missing_aria_labels.md). Every other button on that list already had a name.

• Help Guide (Connected Devices: the ADB Stub, App details) and every new text in all 14 languages.