4.7

Fixes a bootloop. Update if you are on 4.3 - 4.6 and your device really has a device owner or a work profile.

The ownership checks added in 4.3 were also answering system_server's own questions, not just apps'. On a device that genuinely is managed, DevicePolicyManagerService asks about device-owner state on the boot path, got the spoofed answer, and threw at PHASE_LOCK_SETTINGS_READY — taking system_server down in a loop.

Ownership answers now go to apps only; the framework asking itself gets the truth.

If you are stuck in the loop: disable the module (or Zygisk) from your root manager, or adb uninstall com.strawing.duckdevicepolicy while it restarts.

Reported by @MootComb.

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