Your frustration is understood, but I feer its misplaced. The way you phrased your response suggests you are disappointed that /e/os doesnt behave like you want, when you should actually be frustrated with google for designinjng android that way.
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
I really would like a version of eOS without microG baked in so I can install it in a workspace. Sucks that there’s not an easy option for that
Your frustration is understood, but I feer its misplaced. The way you phrased your response suggests you are disappointed that /e/os doesnt behave like you want, when you should actually be frustrated with google for designinjng android that way.
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