ADB Application Manager Pro v7.22.1

A patch release on top of v7.22.0, cut from main, for the owner's request of 2026-10-31. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version.

• RRO/Monet Customization, Theme half: the line of text under Apply theme and Reset in the bar at the bottom is gone (Android repaints in a moment, and apps may restart., This is already what the phone uses., Material You needs Android 12 or newer., and with Super User Also writes these colors into Android with Super User: the same palettes as ColorBlendr. and Reset also removes the theme overlay.). The bar holds only the two buttons and is shorter. Nothing else on the tab changed: the buttons, what Apply and Reset do, the confirm before Reset, the Undo bar and the Overlays half with its press and hold to uninstall are as in v7.22.0.
• The five texts are removed from the 13 translations, the guide's steps no longer quote them, and UI scripts t67, t564, t565, t570, t573, t574, t615 and t616 check that the bar has no line under the buttons.

ADB Application Manager Pro v7.22.0

A feature release on top of v7.21.0, cut from main, for the owner's request of 2026-10-30 that the Monet colours written with Super User be the ones ColorBlendr makes, on one screen with one Apply. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. Nothing in it has been run on a phone yet: the colour maths were checked in a Node test against ColorBlendr's behaviour as read in its source, the page in a headless browser with a mock phone, the overlay rules by the Java suite.

• ColorBlendr-identical palettes. The colours the RRO/Monet Customization tab writes with Super User are now computed exactly as ColorBlendr computes them: the same revision of Google's Material Color Utilities, the same per-palette saturation and lightness tuning with its gamut clipping, the same list of colours in the same order (the 13 shades of the six palettes, the role colours for light and for dark, the 12 fixed colours, Android's own SystemUI colours from Android 15, the surface effects on Android 17) and the same Pure black and text rules. The colour you pick is taken as it is (no grey-to-Google-blue swap, no minimum strength), the contrast is the one you choose, and the default spec is 2021, as in ColorBlendr. Why the old colours looked darker: the engine before followed the phone's own Android release (its copy of Google's library, so the 2026 spec on Android 17, the phone's contrast setting, the grey-seed remap and this app's own Intensity, accent and Accurate shades formulas), which gave darker, more muted colours than ColorBlendr for the same choices. The new engine (MonetPlan.cb in assets/monet.js) is this app's own code; ColorBlendr was the behavioural reference only, and the SystemUI custom colours are ported from AOSP (Apache-2.0) with a provenance comment.
• Two new controls. Contrast (Standard, Medium, High): the level the scheme is computed at, a choice of its own rather than the phone's accessibility setting. Tint text color (on by default): off makes the text on backgrounds and surfaces plain white in dark mode and plain black in light mode instead of a tint of your colour. Color spec keeps 2021 / 2025 / 2026 with 2021 as the default; CMF needs 2026 and the style says so while another spec is chosen.
• One screen, one Apply. The Theme half is one flow: Colors in use (with uid 0 a preview of exactly what Apply writes, with the source colour it takes), Color with the Secondary and tertiary accents, all ten styles in one grid, Color spec, Contrast, Intensity, the switches Accurate shades, Pure black and Tint text color under Shades and text, How this works (folded) and Back up and restore, with a bar at the bottom that holds the only Apply theme and Reset (called Default before). Every root-only control is a locked row without uid 0, greyed like the Root Features rows, with the lock glyph in its name, the Locked button and the reason: Needs Super User (uid 0) to write Material You colors, or, with Shizuku running as the system user, Shizuku runs as the system user (uid 1000); writing these colors needs uid 0. Apply takes every choice at the moment of the tap; Undo puts the theme and the overlay back as they were. Backups are format 2 (every choice of the screen); format 1 files from v7.18.1 to v7.21 are still read.
• Uninstall an overlay by press and hold. For the owner's request that RROs can be uninstalled with Super User, or Shizuku as root (uid 0) or the system user (uid 1000): in the Overlays half a press and hold on a row that is Off now asks to uninstall it (a hold on a row that is On still switches it off; the switch and the detail sheet still turn a row on, so nothing is lost), and the detail sheet of an Off row has a red Uninstall button, greyed and locked with the lock glyph without that privilege, where the hold only says why. The app first copies the overlay's APK files (the base APK and any splits) to a folder named after the package under Download/ADB App Manager/Overlays and checks every copy is there (no copy, no uninstall), then runs pm uninstall for the phone's current user (the one the list is read for) and believes only what it reads back: pm path must print nothing and the overlay list must no longer have it; a Success that leaves the package in place is a failure, a cut-off read-back is reported as unknown and the list is read again. Refused with the reason: an overlay on a read-only partition (switch it off instead), a name this app fabricated (a colon in it: switching it off is all there is), a name that is not installed as a package, and ADB, Wireless Debugging or Shizuku as the shell. There is no Undo bar; the saved APKs install again from the Installer tab (choose all of them together), or with adb after pulling the folder to the computer. Before anything is copied or removed, the app reads the overlay list again and refuses a name that is not a switched-off overlay; the copy counts only when it matches the APK byte for byte (an older file of that name is never taken for it), and a copy the shell had to write below the storage mount is handed to the media layer so the Installer tab and a file manager see it. The in-tab note and the Press and hold guide say the new rule; the guide has an Uninstalling an overlay section with the risks and the way back.
• The write path. An overlay entry may carry the night configuration, so the 12 fixed colours and the device default accent are written as day/night pairs from Android 14 (config="night" in the fabricate XML, which Android's overlay shell command reads; Android 12 and 13 get the current mode's colour); every android:color/* name is allowed, a plan may hold 512 entries, a resource may appear once per configuration, read-back lookups never pick a night entry, and only names the phone's framework has are sent (a per-version table for Android 14 to 17, built from AOSP's colour files and shipped as a test fixture).
• Root Features: the Monet row is Monet theme — ColorBlendr palettes ("Color spec, contrast, intensity, accents, Pure black, Tint text color. Written with Super User.").
• Tests and guide: tests/monet/cb.test.js (136 checks on the tuning, the token list, the rules, the writers and the framework table), OverlayRulesTest extended for the configuration, the widened names, the cap and the lookups, UI scripts t564–t574 and t604 rewritten for the one screen, t615 (the merged screen, locked rows at uid 1000 and at the shell) and t616 (Tint text color and Contrast reach the plan; a night entry for system_primary_fixed) new. t617 (the hold on an Off row asks, the prompt, the busy row, the success with the saved copy, the fabricated id, a pm refusal, the locked button and toast at the shell, the gate closing under a request) new, and OverlayRulesTest extended again for the uninstall rules: the fabricated-id refusal, pm path parsing and the firmware partitions, the backup script, judgeUninstall (a Success that leaves the package is not ok), and the whole flow against a fake pm in a real sh. The guide's RRO/Monet sections are rewritten for the one screen. Every new text in all 14 languages.

ADB Application Manager Pro v7.21.0

A feature release on top of v7.20.0, cut from main, with the tab the owner asked for on 2026-10-30: an app firewall. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. Nothing in it has been run on a phone yet: the page was checked in a headless browser with a mock phone, the rule scripts by the Java suite (including sh -n on every script) and a build against Android 34. docs/PHONE-SCRIPT-v7.21.0.md is the check.

• Android Firewall, a new tab (two lines on the tab bar, Firewall on the bottom bar, right after Custom Fonts; on out of the box, not pinned to the bottom bar). For every app you decide whether it may use Wi-Fi and mobile data, and with the columns turned on in Options, roaming, a VPN, your LAN or Tor: what AFWall+ does, written for this app. The rules go into the kernel's own packet filter (iptables and ip6tables), so a blocked app cannot get out whatever it tries, and no service of this app runs in the background. It needs Super User, or Shizuku running as the system user (UID 1000) or as root (UID 0); the ADB shell user may not write kernel rules, so without one of those the tab is locked with a box that says why and a Set Up button, and nothing else changes.
• Allow list or block list. An allow list (the default, the safer one) lets out only the apps you tick and stops everything else; a block list stops the apps you tick. In an allow list this app and Android's DNS resolver are pre-allowed unless you untick them yourself, and an allow list with almost nothing ticked is asked about once before it is applied.
• One row per app, one round cell per network. Icon, name, package and UID; two apps that share a UID are one row. Chips filter the list (Use the internet, User apps, System apps, Special, Ticked, All) and the search box finds a row by name, package or UID. A tap on a column's head ticks every row shown. Special rows for what is not an app: the Linux kernel, Root (UID 0), Android system (UID 1000), the DNS resolver, media, VPN networking, DRM, mDNS, GPS, 464XLAT, shell and more, each with a line that says what breaks when it is blocked.
• Profiles: up to twelve rule sets (home, work, travel) with their own ticks; the mode and options are shared. New profile (empty or a copy of the current one), Rename, Delete; switching profiles while the firewall is on applies the new one at once.
• Options: Roaming, VPN, LAN and Tor columns; IPv6 too; Log stopped connections; Drop instead of reject; Block new inbound connections; Block tethered devices; Re-apply when the network changes (roaming starts or ends); Apply on boot with a delay (15 seconds out of the box), which runs the last applied script again through su after each restart; and a card for your own iptables lines before and after this app's rules.
• Log, Active rules, Backup. The Log card reads what the kernel stopped, grouped by app, newest first, with the last destination; Clear log empties dmesg and asks first. Active rules shows this app's chains as iptables prints them, with Copy. Backup saves or shares one JSON file with the mode, the options and every profile, by package name so it works on another phone; Import asks whether to replace your profiles or add the file's next to yours.
• The state is what the kernel reports. After every Apply the app reads the tables back and counts the rules of every chain against the set it sent: the chip reads OFF, ACTIVE, NOT APPLIED, NO IPTABLES or LOCKED from what it found, a line that iptables refuses is named in the status line, and a set that did not take in full is reported as not applied rather than ACTIVE. The apply never leaves a gap: the new rules are built beside the ones in force and swapped in only when complete, so a blocked app stays blocked while the rules change. The boot script checks that Apply on boot is still on after its delay before it writes anything.
• Saved Applications get a Firewall button on every card (and the tab's own Saved list button opens the same choice): Block these apps, Allow these apps or Forget their rules for every app of the list at once, in the current profile. Block and Allow mean the right thing for the mode you are in.
• Root Features has an Android Firewall row whose Open tab brings you to the tab; locked like the other rows until a privileged mode is the working mode.
• Remove all firewall rules (the red card at the end of the tab): press and hold to delete every chain this app made, for every profile and both IP families, and turn Apply on boot off. Your profiles stay saved. The guide's Android Firewall and Undoing the firewall sections explain the risks (an allow list blocks first, the special rows that carry the phone, Apply on boot after a wrong rule set) and the three ways back, including the iptables commands by hand and the boot file to delete.
• Every new text in all 14 languages.

ADB Application Manager Pro v7.20.0

A release on top of v7.19.5, cut from main, that rebuilds the Doze & power governor and Zram & memory sections of Extra Settings, for the owner's report of 2026-10-29 that the Doze setting did not feel like it did anything, the power profile never left Balanced and the memory settings never changed. Package, signing certificate, APK file names and permissions are unchanged, so it installs over the previous version and keeps its data.

• Doze timing you can set. Five rows under the Doze timeline: Light Doze after the screen goes off, Light Doze wake-ups, Deep Doze after the phone lies still, Deep Doze wake-ups and Maintenance window, each with the value the phone runs now (Phone: 4 min) next to a few chips, and the presets Phone's own, Balanced and Aggressive. Apply N changes opens the confirm sheet with the exact commands (Android 12+: one device_config put device_idle <constant> <ms> per constant; Android 11 and older: settings put global device_idle_constants …), the phone is read back row by row, and the result says what it really runs. Phone's own deletes the overrides. The applied choice is kept: when a Google Play services sync or a reset puts the phone's own back, a line offers Re-apply. A new line under the timeline says why Doze is where it is (screen on, charging, the next step in 6 min).
• The CPU governor, live, per cluster (Root mode). Four facts read from the phone open the power governor block: battery saver, charger and level, the governor of the CPU clusters with their clock range and the clock now, fixed performance mode. A CPU governor row offers the governors the clusters have, names the phone's own and writes the chosen one to every cluster, read back right after; a cluster without that governor or a refused write is reported with the phone's words. ADB, Wireless Debugging and Shizuku mode say Needs Root mode on the row.
• Why the power profile never left Balanced. Android keeps battery saver off while the phone is charging and quietly puts low_power 0 back: the Battery saver card (called Ultra saver before) now says Not while charging, the fact says cannot turn on while charging, and an apply on a charging phone comes back as Not applied: Android keeps battery saver off while the phone is charging (USB). Unplug the cable and apply it again. Performance is marked when the phone reports fixed performance mode on or every cluster runs the performance governor, and under Root on an Android without the fixed-performance command it sets that governor instead of being locked.
• Memory settings that change something. The Zram & memory section opens with a RAM bar (used / cache / free, available of total), the memory pressure of the last 10 seconds, and Available RAM and Cache with the change after each cache button (Done. Available RAM 2.8 GB → 3.1 GB, cache 2.5 GB → 1.9 GB …): the numbers those buttons really move, where the zram counters barely did. Three new rows: Zram size (Root; swap off, reset, new size, swap on; until the next restart), Swappiness (Root; 0 to 200; until the next restart) and Low-memory killer (every mode; Keep more apps open or Free memory sooner through device_config put lmkd_native … and setprop lmkd.reinit 1; across restarts). Each shows the phone's value, Phone's own brings the first value seen back, and after a restart the applied choice is offered again with Re-apply.
• Every command the two sections run is built from a table of allowed values (xqRowCmd): a value the table does not allow is refused before the shell sees it. A bug found by the new test: the low-memory killer's values were read one line off after the separator, so the row always showed the phone's own.
• Smart Tabs stays off by default and keeps its state. Checked again at the owner's request: the switch in Settings → Navigation is off until you turn it on, the choice is saved in the app's settings store the moment you flip it and read back when the app starts, so an app you closed and opened again, or a phone you restarted, has Smart Tabs the way you left it (t612 covers the default and the restart).
• The guide's Doze and Zram pages are rewritten with every command, what it costs and how to undo it. Every new text is translated into the other 13 languages.

ADB Application Manager Pro v7.19.5

A fix release on top of v7.19.4, cut from main, for the owner's report of 2026-10-29 that Smart Tabs did not seem to work. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. Not run on a phone yet: docs/PHONE-SCRIPT-v7.19.5.md is the check.

• Smart Tabs now changes the bottom bar itself. In v7.19.4 the openings were counted and the tabs were reordered, but the bottom bar kept the four tabs pinned in the Feature List and only reordered those: a tab you opened most that was not pinned went first under More, so with the bottom bar (the default) nothing seemed to happen. Now, while Smart Tabs is on, the bottom bar holds Application Manager and the three tabs you open most, pinned or not, the most opened right after Application Manager, and the rest wait under More in the same order with About last; the top bar shows the same order. On a tie a pinned tab comes first, so turning it on before anything is counted leaves the bar as it was.
• The Feature List's pins rest while Smart Tabs is on (like its arrows), lit for the tabs Smart Tabs put on the bar, and the note says so. Your own pins are kept and are the bar again when Smart Tabs is turned off.
• The order also updates every time the app comes back to the front, from the app itself as well as the page: on some phones the web view did not report that the app had been in the background, so the new order waited for a restart of the app.

ADB Application Manager Pro v7.19.4

A small release on top of v7.19.3, cut from main, with the changes the owner asked for on 2026-10-29. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. Nothing in it has been run on a phone yet: docs/PHONE-SCRIPT-v7.19.4.md is the check.

• Smart Tabs (Settings → Navigation, off by default). Turned on, the tabs between Application Manager and About go in the order of how often you open them, the most opened right after Application Manager, on both the bottom bar and the top bar (and under More). Application Manager stays first and About last. Every opening of a tab is counted on the phone (Back to a tab is not), so turning it on uses what is known already; the order is worked out when the app starts, when Smart Tabs is turned on and when you come back to the app, never while you tap, so a tab does not jump away under your thumb. When a count passes 400 every count is halved, so what you use now outweighs what you used months ago. While it is on, the Feature List shows the tabs in that order and its arrows rest; turned off, your own Feature List order is back.
• Ask agent in Connected Devices → Hidden Settings. Every setting of a connected device has the Ask agent button, on its row and in its sheet, the same window as Hidden Settings on this phone: the agent is told the setting is on that device (its Android version and model). Nothing is kept with the setting (no AI line), unlike Hidden Settings on this phone.
• Agent API keys in Settings → Default Ask Agent. Choose any agent that takes a key (Perplexity, Exa, Browser Use, Crawl4AI, Gemini, Claude, ChatGPT, Cursor, Copilot, Grok, Muse, Deepseek), paste its key and press Test key: it is tested with the provider's own check and saved, encrypted on the phone, only when it works (the same keys as Console → Terminal's Connect sheets). A saved key shows as dots, like the VirusTotal key; Test key with nothing typed asks the agent one sample question with the saved key. Get a key opens the provider's key page, Remove key forgets it. Choosing a Default Ask Agent moves the key box to that agent.
• A green check mark next to agents whose key was tested and works, in the Default Ask Agent list, in the Agent API keys list and in Console → Terminal's Coding Agents list. A key saved without a working test (Save anyway), removed, or failing a later test loses the mark.
• Every new text in all 14 languages.

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.

ADB Application Manager Pro v7.19.2

A small release on top of v7.19.1, cut from main, with the three changes the owner asked for on 2026-10-29. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. Nothing in it has been run on a phone; the page was checked in a headless browser with a mock. docs/PHONE-SCRIPT-v7.19.2.md is the phone script.

• Phone font above Emoji fonts. On the Custom Fonts tab the Phone font card now comes right after Make a font, before Emoji fonts and System emoji.
• App Stores: the ? on its own line. The tab's ? help button sits on a line of its own above the Update stores on mobile data switch, outside it (in v7.19.1 it was inside the switch's card), so a tap meant for one never lands on the other. The switch is thinner: a button's height (36 px instead of 76), and all of it is the switch. App Updater's Check for updates on mobile data switch is as thin.
• Hidden Settings remember what Ask agent found. Each time an agent answers Ask agent about a hidden setting (from its row or from its sheet), the app keeps one short line the AI wrote with that setting for good: the agent is asked to end with an In short: line, and when it does not, the answer's first sentence is kept (at most 160 characters, without Markdown or source numbers). Under the answer it says Kept with this setting: .... The setting's row then shows the line marked AI (in place of No description yet, or under the app's own description), its sheet shows it under From Ask agent with the agent's name and date, the search finds the setting by it and Described lists it. A later answer replaces it. The lines are kept with the app's settings on the phone, by table and name, through restarts and updates. The built-in web lookup (no agent connected) and a failed answer keep nothing.
• Help Guide (Custom Fonts, App Stores, Hidden Settings) and every new text in all 14 languages.

ADB Application Manager Pro v7.19.1

A small release on top of v7.19.0, cut from main, with the three changes the owner asked for on 2026-10-28 and the new name he chose the same evening. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. Nothing in it has been run on a phone; the page was checked in a headless browser with a mock and the Java by the Java suite. docs/PHONE-SCRIPT-v7.19.1.md is the phone script.

• New name: ADB/Root Toolbox. It is the name under the icon, on the widget, in the page title, in About, the console banner, shared texts and the Help Guide, in all 14 languages; the header shows it on two lines ("ADB/Root" over "Toolbox"). Before, it was ADB/Root Full System Toolbox. The package, the APK file names and the release name stay the same, so updating keeps every setting and saved file.
• Mobile data switches below the help button. On App Stores and App Updater the slim mobile data switch sat over the ? help button, so a tap on the switch opened the Help Guide. The switch now sits below it.
• Phone font: every font on the phone in one drop-down. The Custom Fonts tab's My fonts list and Font changer card are now one Phone font card with a Font drop-down: Default (the phone's own font), then every font package installed on the phone and every font made on the tab, by name, each saying where it came from and whether Samsung's Font style takes it. Choosing a font uses it:
  • with Root, or Shizuku as the system user (UID 1000) or as root (UID 0), the app puts the chosen font on the phone itself (any font package, not only the ones made here: its Regular and Bold are read from the package), and Default puts the phone's own font back;
  • without them, a font the phone takes by itself (one that came with the phone, one signed by Samsung or Monotype, or any font before One UI 8.5) opens Samsung's Font style with its name to choose there, installing a font made here first;
  • a font not signed by Samsung or Monotype on One UI 8.5 (and 8.0 from the March 2026 patch) shows a warning and the font is not changed. The app compares a package's signer with the phone's own (the system's and its preinstalled fonts'), and a signer it cannot read counts as not signed.
• Press and hold a font to uninstall it. It asks first, uninstalls with any working mode (and reads back that it is gone) or opens the font's App info without one. Default, the fonts that came with the phone and the font in use are refused with a message saying why; a font made here that is not installed is offered for Delete instead. Delete works from the keyboard too.
• The font just made now has its buttons under the build result: Use it, Install (or Update), Export and Make again. They go away when the next font starts.
• Kept apart. Installing, uninstalling and using the same font package no longer run at once (from the drop-down, the build result or a second window); the later one says the font is busy. An uninstall that cannot read which font is in use (with Root or the system user) stops with The phone did not answer. Try again. instead of going ahead.
• Help Guide (Custom Fonts, recipes, help) and every new text in all 14 languages.

ADB Application Manager Pro v7.19.0

A release on top of v7.18.3, cut from main, with the eight fixes and enhancements the owner asked for on 2026-10-28. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. Nothing in it has been run on a phone; the page was checked in a headless browser with a mock and the Java by the Java suite. docs/PHONE-SCRIPT-v7.19.0.md is the phone script.

• Working mode order. Automatic now uses the first of these that is ready: Super User (su granted), Shizuku as root (UID 0) or as the system user (UID 1000), ADB over TCP (5555), Wireless Debugging, and Shizuku as the shell user (UID 2000) last. The Automatic card says so. Before, Automatic never used Super User and put every Shizuku after Wireless Debugging.
• Super User lost. When Super User is the chosen mode and su is gone or said no, the app switches the working mode back to Automatic by itself and says Super User is no longer available. The working mode is back on Automatic.
• Connected Devices: paired devices on your Wi-Fi. A refresh also asks adb which paired devices announce wireless debugging on the same Wi-Fi; they show under Found on this Wi-Fi with their IP and current port and a Connect button. + Add device types the first one in for you, and after a successful Pair the app finds the new device's connect port and connects by itself.
• Saved devices: one entry per IP. A device that comes back on another port (Wireless debugging picks a new one each time) replaces its old entry instead of adding one more; lists saved by older versions are merged the same way. Connect on a saved Wi-Fi device uses the port it announces now.
• Kill Apps runs to the end. The run is held by a foreground job with its notification, so it is not frozen or killed half way with the screen off or the app in the background, and Back no longer ends it. The apps that draw its notification or that the run goes through are stopped last: the keyboard, the home screen, System UI (stopping it in the middle made the live notification vanish), and Shizuku and the root manager at the very end.
• App ops and permissions. Changing an op that also has a uid-level mode now sets both (Android uses the stricter one, so the change used to look ignored); every change is read back, and a mode Android kept is said instead of claimed. The ops behind an app's permissions are listed even before Android has a mode for them. Permissions controlled by an app op (Display over other apps, Usage access, Modify system settings ...) get a working GRANTED / DENIED toggle. Large apps whose permission list was too big to read at once show their permissions again.
• DNS: Sort by speed is on by default and remembers what you last chose.
• Mobile data switches. Update stores on mobile data (App Stores) and Check for updates on mobile data (App Updater) are slim one-line switches at the top of their pages, without the description.
• Help Guide (connect, apps, tools, system, devices) and every new text in all 14 languages.