4.5

The Diagnostics tab now shows which restrictions your device actually has — read live, outside the module scope, so they are the real values and not what the hooks show other apps — instead of an empty report that was never going to arrive.

It also says plainly where the hook report is: the LSPosed log. The framework's file store for a module is root-owned, so a hooked process cannot write into it and that screen has no way to receive one. Look for installed N/M hooks in <process> and first hit: <category>.

If you are coming from 4.3 or earlier, 4.4 is the important one: the device-wide categories only worked if you ticked the framework scope entry that actually reaches system_server, and managers disagree about whether that is android, system or system_server. Tick every one your manager offers.

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