DivestOS' unprivileged microG implementation

Privacy Project Showcase
25

not possible, their server side connects to the google server side which expects to connect to some google/microg component on your device.

1 Like
26

Do you have any plans of allowing opt-in location access to Microg so that UnifiedNLP works?

27

@Regime6045
not at the moment, but it is on the table todo list

1 Like
28

Hey! There is another LOS-based rom that implements sandboxed google play from GOS called VoltageOS. Maybe it would be handy to fork that instead of writing your own patch?
And thanks for implementing microG this way, love that feature and LOS-based systems in general. It’s the reason I switched from AOSP-based GOS almost without any customization to DOS, but I miss Sandboxed Google Play. Miss being able to set my purchased apps to my work profile the proper way with working license check

29

@jarjensen
I have no intention porting Sandboxed Play. It isn’t just the initial port, but the ongoing maintenance of it (look at their changelogs).
The primary reason for unprivileged microG is its sheer simplicity which allowed me to port it to Android 9 through 13.

1 Like
30

Hi, i just ran into a problem with signature spoofing on a Pixel 5 (redfin) after switching from LineageOS 20 (not the latest update though) to the latest DivestOS 20.

When installing DivestOS via fastboot, adb sideloading prompted “signature verification failed” (Error 21) similar to this post: Signature verification failed · Issue #275 · Divested-Mobile/DivestOS-Build · GitHub

I still continued with the installation instructions and did a factory reset, booted and everything seems to work. With unpriviliged microg enablement toggled, MicroG’s Self-Check says “Your ROM has no native support for signature spoofing. […] check the documentation […]”

  • sha512 hash of the divestos zip was ok

I assume the problem is that i didnt switch from stock to divestos. Any help is welcome

31

@Jeux7ZDw2rzCRQUxM5xN
it sounds like you flashed DivestOS using the LineageOS recovery, as DivestOS recovery aborts entirely on signature failures

please follow the correct steps:

You likely also were not running the latest microG as the instructions note, please give the video a watch: https://divestos.org/videos/tutorial-divestos-enable_microg.webm

1 Like
32

What are the main disadvantages of this over privileged microG (like in CalyxOS)? The two main issues I see here are :

  1. Can’t access location (so no map services which is one of microG’s main features)
  2. No SafetyNet bypass (so no apps that need it)
33

@bqfls
the primary reason for having microG support is allowing apps to run that would typically exit if unavailable and to support push notifications

and location in microG does actually work for itself and to apps calling it directly using Google Play Services. microG simply can’t inject NLP location into the system to benefit non-GMS apps.

as for SafetyNet, that is getting impossible to deal across the board with as Play Integrity becomes more adopted

2 Likes
34

Thanks very much

Re-running the install steps led my to my mistake (reading): I sideloaded the wrong zip (used the same one for “fastboot update” as for “adb sideload”), my bad! :man_facepalming:

But, for future reference: Restoring a Seedvault-Backup, that was created with LineageOS on DivestOS caused several problems. Some Apps (banking, scientific calculator) kept freezing, even after reinstalling them. Also bluetooth pairing wasnt possible with some devices

35

@Jeux7ZDw2rzCRQUxM5xN
Sadly Seedvault isn’t very reliable and restoring across systems is likely to cause such weird problems.
I’ll make a note of it on the website.

1 Like