• 1 Post
  • 31 Comments
Joined 10 days ago
cake
Cake day: March 19th, 2025

help-circle


















  • I’m a bit confused.

    The idea is to contain all non-FOSS apps in a workspace. I assume that I’ll have trouble without microg for some apps in said workspace, which is why I’m looking for a way to put microG in that workspace.

    The rest of the apps will all be FOSS. Thus, I do not see a good reason to bundle MicroG in the base image. I’d like to keep all non-FOSS+Google stuff in one workspace and not have them touch the rest of my apps.

    I’m assuming workspaces are akin to a “namespace” in general Linux terminology.

    The problem you are going to run into though is that google has baked itself into android that you need something to trick android into thinking its operable.

    In stock android, you COULD have a workspace that only uses microg, but considering you otherwise MUST have play services… Why?

    What do you mean? I genuinely do not understand, I thought DeGoogled AOSP would work just fine.


  • Unfortunately, if I’m to use it as my daily driver I will need to use some non-FOSS apps. Mainly the 2FA apps like the ones from MS, Okta, Cisco etc. And Google maps because OSM didn’t work for me. And some chat apps because family. Rather than having MicroG in the base system for just this handful of Big-Tech produced apps, I wanted to contain all of them in a workspace. I don’t actually care about running eOS specifically, it’s just that running GrapheneOS means buying an expensive Pixel device. I want a privacy-foscussed ROM on which I can do this