Bingblop/ADB-Root-Toolbox v7.16.2

ADB Application Manager Pro v7.16.2

on GitHub

A feature release on top of v7.16.1, cut from main (#322 to #324, with the earlier #167, #168, #177 and #179 brought up to date): an app's trackers can be switched off and back on with Super User, Live Logcat wears one colour per level and keeps up with a busy log, saved lists are edited by ticking apps instead of typing package names, Working Modes has a Connection Check card with a Turn on Wireless Debugging button, a Wireless Debugging port that changed is found again over mDNS, and the Console has Screenshot and Record screen. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. This app roots nothing: the tracker switch, like the component switch it is built on, needs Root with su granted or a Shizuku server that already runs as the system user (UID 1000) or root (UID 0), and is shown locked (never hidden) without it. Nothing in it has been run on a phone by the people and tools that wrote it. docs/PHONE-SCRIPT-v7.16.2.md is the phone script.

• Switch trackers off in root mode. The TRACKERS chip of an app's menu now opens with a card "N tracker parts · N switched off" and Disable all trackers / Enable all trackers; under each tracker of the Exodus Privacy list come its parts (screens, services, receivers, providers) with their state, and a DISABLE / ENABLE for that tracker alone. The batch sheet has Disable Trackers (asked first, with a note when system apps are selected) and Enable Trackers, with progress, Batch Results, CSV and Run again. History keeps each Disable all trackers / Enable all trackers of an app ("Disabled trackers in (app)") and each batch run ("Disabled trackers in N apps"), and a step's Undo switches back exactly the parts that step changed, never every tracker part of the app (a single tracker's DISABLE / ENABLE is not written to History, as a single part's switch is not). Root Features has a third row, Trackers in apps, whose Open apps shows the Apps tab with the Trackers filter on. It works in Root mode with su granted, or with Shizuku as the system user (UID 1000) or root (UID 0); Shizuku over ADB (UID 2000) keeps the lock, because Android refuses the shell a component change. A part counts as a tracker's only when the tracker's code signature covers whole pieces of its name (com.tune is not TuneIn Radio's com.tunein), and never when the signature is the app's own package; each part's state is read back from Android, and a part that is off only because the app ships it off (off by default) is never switched on. Switching off stops what a tracker does through its own parts, not the code it runs inside the app, and an app can lose push notifications or break where it opens a switched-off screen: the new Help Guide section "Switching trackers off in apps" covers what it does, the risks and every way back.
• Live Logcat colours. Every level wears one colour across its whole row (the key's dot, the badge, the tag, a bar on the leading edge, the tint and the message), as the colour key above the log says, in dark, light, pure black and any Monet accent, with the message kept readable (4.5:1). Connected Devices' Logcat uses the same colours.
• Live Logcat keeps up. A live read adds only the new lines at the end instead of redrawing the whole log, up to 2,500 entries are kept, rows far above the screen are laid out only as you scroll near them, and the list follows the newest line only while you are at the bottom. At 360 px nothing scrolls sideways.
• Edit saved lists by ticking apps. New List and a list's Edit show this phone's apps as the Apps tab's rows, the list's apps first and ticked; a tap (or a hold) on an app adds or removes it, and a row never moves under your finger. Search apps and the chips All / In this list / System / User narrow the rows, and a line counts the apps and what was added and removed. A package of the list that is not on this phone keeps a ticked row tagged NOT INSTALLED until you untick it. The package names are still under Edit as text for pasting.
• Connection Check. The first card of the Working Modes sheet says why a connection works or not: Wi-Fi, the Wireless Debugging switch, the ADB connection (including a saved Wireless Debugging port that no longer answers), Shizuku and secure settings access, each OK, CHECK or INFO in words. Most things to do come with a button that fixes it or opens the place to fix it (Open Developer Options, Turn on Wireless Debugging, Auto-Detect Ports, Open Shizuku, Authorize & Use Shizuku, Grant now); when Wi-Fi is off, Developer options are off or the ADB port is open but not connected, the row only says what to do. It only reads, except for the buttons you press; Check again reads it afresh.
• Turn on Wireless Debugging. When Wireless Debugging is off (Android 11 and newer, on Wi-Fi, with a working mode connected or the secure settings permission granted), the Connection Check's switch row offers Turn on Wireless Debugging: it switches it on and reads it back, and Auto-Detect Ports then finds the port Android chose.
• Wireless Debugging finds its new port. Android picks a new port each time Wireless Debugging is switched on. While Wireless Debugging is the working mode (or when you select it again), a saved port that no longer connects is looked up over mDNS on the saved address only (a blank or 127.0.0.1 address means this phone's own Wi-Fi address, which is then saved), connected and saved, so you neither pair nor type again; another phone is never used. In Automatic mode a stale port is not looked up. Connect tries only the address and port you typed and never jumps elsewhere; a port you type becomes the saved port, which a later reconnect (at launch, before a command, or when the mode is selected) replaces if it stops answering.
• Screenshot and Record screen in the Console. The ADB Shell button row has Screenshot (waits 3 seconds, then saves a PNG in Pictures/ADB App Manager) and Record screen (saves an MP4 in Movies/ADB App Manager and stops by itself after 3 minutes; the button reads Stop recording while it runs). Both need a working mode, and a file counts as saved only when the phone reports it above 0 bytes.