Provisioning (MDM setup) by QR code - compatible with 15-qpr2

[h-mdm]

Mobile device management application can be installed on GrapheneOS using the QR code provisioning workflow: https://h-mdm.com/quick-start/#device

To test the feature:

Create an account in one of the MDM systems (for a free account in the Headwind MDM cloud, click "Sign in" at https://h-mdm.com/).
Prepare the QR code for the MDM provisioning
Tap 6 times on the welcome screen after the factory reset, scan the QR code, and follow the setup wizard.

This version has been tested on GrapheneOS 15-qpr2 and all conflicts are resolved, so could be merged smoothly.

[de0u]

I am not a member of the GrapheneOS development team and do not speak for the project. But I suspect the project might prefer a cleaned-up commit history based on using rebase to squash some of the commits.

Also, I wonder whether embedding the QR-scanner code in binary form is the best approach from a maintainability perspective. Do other GrapheneOS uses of QR scanning embed that package that way?

[oppressor1761]

Asaik Android Enterprise requires Device Policy app to act as dpc. Does gos have it?

[MoChahadeh]

I was wondering if there are any updates on this PR, or regarding MDM support on GOS in general.

[de0u]

Updates to the PR would be visible in the PR.

At present this particular PR has two identified issues that have not been responded to in a year. Though I do not speak for the GrapheneOS project, I strongly suspect that forward progress on MDM support for GrapheneOS will require either substantial adjustments to this PR or a fresh PR.

Discussion about MDM support for GrapheneOS in general should take place on the discussion forum (e.g., https://discuss.grapheneos.org/d/13587-mdm-on-grapheneos/).

The GrapheneOS developers want PR threads to be used to coordinate issues directly about PRs, e.g., new code, feedback on submitted code, etc., not to be used for open-ended discussions, and not for "Are there any updates?" posts or "I want this too!" posts. PR threads that attract status inquiries and/or lobbying are likely to be locked, made private, or deleted.

[thestinger]

This needs to be reopened against 16-qpr2 or the upcoming 17 branch. It was only closed as a consequence of deleting the legacy 15-qpr2 branch.

[thestinger]

I figured out a way to do that myself by temporarily restoring 15-qpr2 and changing this to 16-qpr2. There's a minor merge conflict to resolve but the main blocker is that it needs major cleanup and changes to meet our requirements.

[MoChahadeh]

@thestinger I already implemented it on 16-qpr2 in my fork and built the OS with it, working without issues, I can open a PR for it:
github.com/MoChahadeh/platform_packages_apps_SetupWizard2/tree/16-qpr2