A patch release on top of v7.16.0. It widens the privileged-mode gate so the Root Features tab and the per-app component Enable / Disable unlock not only in Root mode with su granted, but also when the Shizuku server runs as the Android system user (UID 1000) or as root (UID 0) — the users Android lets change a single app component. Shizuku started over ADB (the shell user, UID 2000) still leaves them locked, and so does an unknown UID. Writing the root theme card's fabricated colour overlay still needs UID 0 (real root, or a Shizuku server started as root); Shizuku as the system user (UID 1000) keeps that one card locked, because Android refuses cmd overlay fabricate to anyone but root. The working-mode badge now names the Shizuku server's real UID instead of always saying 2000. UID 1000 is the Android system user, not root, and nothing in the app or the guide says otherwise. Package, signing certificate, APK file names and permissions are unchanged, so it installs over every earlier version. This app roots nothing: the unlock only reaches a phone whose Shizuku already runs with system or root rights. Nothing in it has been run on a phone by the people and tools that wrote it. docs/PHONE-SCRIPT-v7.16.1.md is the phone script.
- Root Features and app components unlock under a privileged Shizuku. The Root Features tab (before About) and the ENABLE / DISABLE buttons on an app's activities, services, receivers and providers now unlock when Shizuku runs as the system user (UID 1000) or as root (UID 0), as well as in Root mode with su granted. Android allows a single component's state change to UID 0 and UID 1000 but refuses it to the ADB shell (UID 2000), so Shizuku started over ADB still shows them locked with Needs Super User (Root).
- The root theme card stays root-only. Writing a fabricated colour overlay (Pure black, Color spec, More styles and the rest of the Root-only theme controls) needs the root user (UID 0): real root, or a Shizuku server started as root. Under Shizuku as the system user (UID 1000) the card stays locked, since Android lets only UID 0 write these overlays.
- The working-mode badge names the real UID. In Shizuku mode the header now reads Shizuku (UID 0), Shizuku (UID 1000) or Shizuku (UID 2000) to match the server, instead of always claiming UID 2000.
- The Help Guide now explains the UID 1000 / UID 0 unlock in the Root Features chapter, the app-components section and the UID glossary entry, and never calls UID 1000 "root".