ADB Application Manager Pro v7.12.11

A feature release on top of v7.12.10: a Private DNS card in Settings, a result line under each command in the ADB Console (not in Rish mode), the app's own question before an install from the Installer, the Updater (and Update All), a restore or the Morphe Patcher (and no privileged install in Read-Only mode), and readable text on the App Stores buttons. Nothing else in v7.12.10 is changed. Each is tested on a computer.

• Settings: a Private DNS card. Settings has a new card for the phone's Private DNS (encrypted DNS for the whole phone, Android 9 and newer): AdGuard DNS (dns.adguard-dns.com), Cloudflare (one.one.one.one), Quad9 (dns.quad9.net), Automatic, Off, or a host name of your own. The card shows what the phone has now, checks a host name before sending it (letters, digits, hyphens and dots; at least one dot; no address, URL, port or space), changes the setting through the working mode you use (it does nothing without one), and then reads the settings back and shows what the phone really holds; it never says "done" because a command ran. Pressing a button during a change, or switching the working mode during one, cannot make an old answer update the card. A wrong host name can leave the phone without DNS, and Automatic or Off is the way back. Not run on a device.
• ADB Console: a result line under each command's output. After a command run in the ADB Console the output is followed by one line: "Finished. No error text in the output." or "Looks like a failure:" with the reason (error, timed out, permission denied). It reads the failure signs of the Kotlin console and the app's own shell code: output that starts with Error: or adb: device (any capitals) or Failure [, or that contains adb: error:, SecurityException, Permission Denial, unauthorized or the time-out note. The shell gives the page no exit code, so no exit number is shown, and a command that fails without printing one of these phrases still reads "Finished"; a listing that merely contains one of the words (for example adb devices showing unauthorized) reads as a failure. Rish mode keeps its own [exit N] note and gets no result line. Not run on a device.
• Installs through ADB, Shizuku or Root ask first on the Installer, Updater, restore and Morphe Patcher paths. Since v7.12.10 only the store route asked: pressing Update in the Updater, Install in the Installer, restoring a backup and installing from the Morphe Patcher still installed without a question of the app's own. Each of them now shows the app's dialog (which the page cannot press) before anything is removed, signed or installed. For Installer Install, Updater Update, Restore (also before a removed system app is brought back) and the Morphe Patcher the dialog shows what the app read from the file itself (package, version, whether it replaces an app); the Morphe Patcher's uninstall-first step removes the app the APK is, as read from the APK. Update All is asked once, before any download, so its dialog can only show the names and versions the update check found, labelled "not checked" (at most 8 apps are named); a yes covers those apps at that version, source and working mode, once each, for 15 minutes at most, and ends with the queue, and each file is still checked as it arrives. If the working mode changes while a question is open, nothing is installed. Not asked: updating the app itself (the page chooses nothing there: fixed release page, this package, newer, same signing key) and Connected Devices, which installs on another device through that device's own authorization. Known gaps, listed in docs/COPILOT_CLAUDE_HANDOFF.md: rows of an Update All queue can stay on "queued" after the mode switches to Read-Only until the next update check, and an older Update All yes is cleared only when a new Update All question is allowed. Not run on a device.
• Read-Only mode no longer installs through a still-connected ADB. In Read-Only mode the Installer used the Authorizer the page chose, so an install could run silently through ADB, Shizuku or Root even though the app was in Read-Only mode. The app now ignores any privileged Authorizer outside the four working modes and uses the system installer, which asks; the Authorizer drop-down follows the working mode (a choice made by hand is remembered), hides ADB, Shizuku and Root in Read-Only mode with a sentence saying why, and a package loaded from the File Manager cannot be installed in Read-Only mode. Not run on a device.
• App Stores: readable text on the install buttons. The text on the install button, the letter tile of an app without an icon (in the list and in the details window), the selected store tab and the main buttons of the working-mode cards is now black or white, whichever reads better over the whole accent-to-secondary gradient, not over the accent alone. Checked on a computer in 16 palette and light/dark combinations. Not run on a device.
• Not run on a device: none of the above has been run on a phone by the people and tools that wrote it. Sections 20 (installs), 21 (Private DNS) and 22 (ADB Console) of docs/DEVICE-TEST-CHECKLIST.md list the phone checks for this release; section 20 also covers the two install steps that failed in the v7.12.10 phone check (the Updater without a question, and a silent install in Read-Only mode).