Support setting DeviceOwner for the manager app

[xiaoqiclock]

The app already supports ADB via Shizuku, but some features are exclusive to DeviceOwner.

Also, unlike ADB permissions which are lost after a reboot, DeviceOwner persists. It would be useful to add a DeviceOwner setup option in the authorization flow.

[Baidaidai-GFWD-origin]

Hello @xiaoqiclock ,

Thank you for suggesting the addition of Device Owner support. I have carefully read your request and also briefly looked into its implementation approach and typical use cases.

Before explaining why we may still prefer Shizuku instead of making Device Owner one of the core capabilities of Rootless Store, I would first like to clarify the positioning of Rootless Store.

Rootless Store is essentially closer to a GUI-based Termux than to a system-tweaking tool designed for specific scenarios. Its goal is to allow users to run various shell scripts, or execute ELF binaries with ADB-level permissions, provided that the device has already been authorized. In the upcoming 0.0.9 release, we are even experimenting with adding Python support, so that Rootless Store can better support server-side tasks, automation, and a broader range of development workflows.

Therefore, compared with stacking features in a “toolbox” style, we prefer to provide extensible capabilities similar to a DSL. The former is usually more dependent on specific functions and fixed scenarios, while the latter better aligns with Rootless Store’s design direction in terms of reusability, composability, and replaceability.

As for Device Owner, it is more related to system management tools or system APIs, and does not fully fall under the traditional idea of privilege escalation. Its core logic usually needs to be carried by an app, and it often relies on users manually selecting options or completing one-time configuration steps to achieve a specific goal. This operation-driven model does not fully align with the reusable, replaceable, and composable capability structure that Rootless Store aims to provide.

So unfortunately, Rootless Store is unlikely to add Device Owner-related features at this stage. That said, this is still a very valuable suggestion. As a type of tool for exploring the boundaries of the Android system, it certainly has value as an independent project. In the future, we may consider creating a separate project specifically for this kind of system-toolbox functionality, but it most likely will not be hosted within Rootless Store itself.

Finally, thank you again for your valuable feedback and suggestions!