4.3

Renamed to DuckDevicePolicy in 4.2 (same package, updates in place, settings and scope kept) and rebuilt the UI: Status / Categories / Diagnostics tabs, with categories split into device-wide and app-facing.

4.3 adds Device-owner / fully-managed checks — hides getDeviceOwner, getDeviceOwnerComponentOnAnyUser, getActiveAdmins, getProfileOwner* and friends. That is what an app reads before refusing a feature because the device is "fully managed" (Google Photos' Locked Folder is the usual one). The app must be in the module scope. A device-wide variant hooking DevicePolicyManagerService is included but off by default.

It also says what it did. Every build now logs installed N/M hooks in <process>, names every row it could not resolve, and logs the first time each category actually fires. Please quote those lines when reporting a problem.

Reminder: the install / uninstall and developer-options categories need System Framework (android) in the scope; from an app's scope they cannot work.

Full changelog: https://github.com/Bouteillepleine/FuckDevicePolicy/blob/main/CHANGELOG.md