Why should I be annoyed with Google if eOS bundles microG in the base image? I’m not frustrated with eOS, I just would have liked if they could give me a choice.
The choice is google or microg. If you are cool doing Goole things, pick any other phone. If you have a different alternative that actually give full android functionality, including things like the google search built into the default android launcher, lemme know.
I don’t need any of that. All I need isa privacy-focussed ROM which allows me the ability to install MicroG in a different workspace without bundling it in the base image. I think I’m being misunderstood
Possibly, maybe probably. If you dont want to degoogle, why use /e/os? Thats basically the explicit purpose. /e/is fills the same need as any degoogled ROM but is prepackaged on fairphone devices, no need to buy a pixel in order to use graphene. If you just want android, and the ability to use microg when you want and not when you dont, just use a normal android device.
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
Right, I think this is where we are misommunicating.
I use my fairphone as my daily. I also have to use OKTA, and stuff. And I dont use microg for them cause they don’t talk to google. I suppose technically the apps dont use microg, just like they dont use google.
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?
Alternatively, you can use microg to handle all your google bullshit to sign yourself in locally and actually use the services that require google without actually signing in to google.
Frankly, it sounds more like you want an Ubuntu/Linux (not android Linux) phone or something, but I’m not able to advise on that.
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.
Why should I be annoyed with Google if eOS bundles microG in the base image? I’m not frustrated with eOS, I just would have liked if they could give me a choice.
The choice is google or microg. If you are cool doing Goole things, pick any other phone. If you have a different alternative that actually give full android functionality, including things like the google search built into the default android launcher, lemme know.
I don’t need any of that. All I need isa privacy-focussed ROM which allows me the ability to install MicroG in a different workspace without bundling it in the base image. I think I’m being misunderstood
Possibly, maybe probably. If you dont want to degoogle, why use /e/os? Thats basically the explicit purpose. /e/is fills the same need as any degoogled ROM but is prepackaged on fairphone devices, no need to buy a pixel in order to use graphene. If you just want android, and the ability to use microg when you want and not when you dont, just use a normal android device.
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
Right, I think this is where we are misommunicating.
I use my fairphone as my daily. I also have to use OKTA, and stuff. And I dont use microg for them cause they don’t talk to google. I suppose technically the apps dont use microg, just like they dont use google.
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?
Alternatively, you can use microg to handle all your google bullshit to sign yourself in locally and actually use the services that require google without actually signing in to google.
Frankly, it sounds more like you want an Ubuntu/Linux (not android Linux) phone or something, but I’m not able to advise on that.
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.
What do you mean? I genuinely do not understand, I thought DeGoogled AOSP would work just fine.