From your linked thread: > Restrict the permission to apps in /system/priv-app. This requires to ship microG or two placeholder apps with the ROM (or to allow

From your linked thread: > Restrict the permission to apps in /system/priv-app. This requires to ship microG or two placeholder apps with the ROM (or to allow modification of /system, which is a far worse option). Modifying the permission to be for system apps only is changing one word in the patch (from "dangerous" to "system"), creating a placeholder apps is about writing ~10 lines of XML code and thus could be done in a few minutes. Lineage for MicroG already does this by default: https://github.com/lineageos4microg/docker-lineage-cicd/blob/93cc0e5cb5d47a626f5ef6d072b1954d4808d5ff/src/build.sh#L180 https://github.com/lineageos4microg/docker-lineage-cicd/blob... Restricting the permission to a platform level permission essentially means no other installed apps (after flashing) can spoof this. No toggles are necessary either. This should be a secure setup that is as good as any other ROM. It is possible that users can flash something to /system/priv-app via an update.zip and obtain this permission. However, anything you flash like this can practically already gain root access, so this would almost be a feature if ROMs like lineage implemented this, as then microg's installation would be a small update.zip away. This is opposed to the present setup where microg has to build a completely different rom, although that is another story in itself and likely require some more complications.