You're viewing a single thread.
Yes, all of the various degoogled Androids work with normal apps
Unless that app requires google play services...
Doesn't eOS use microG or something to get around that?
I have never used eOS because they are always behind on security patches, but I had always heard it worked Ok.
It does but its not perfect. I love my phone, but its absolutely not for people who dont want to tinker with shit that breaks unexpectedly.
- Can I install MicroG in a different workspace and not on the main system?
- Can I install Google play if needed on said workspace?
I want to keep all apps that need Google play separate from FOSS and I want MicroG to only be present in the namespace/workspace they are in. Is this possible?
- no. Microg is baked in to try and get around the portions of google bullshit thats baked in.
- yes, I have play services running because I cannot not have android auto.
Not in /e/os far as i can see. Maybe in aosp somehow? Frankly, I am not exactly a fan of many of the decisions Murena made. They're motherfuckers about letting me do the things I actually want in the system, for example: just update my apps, dont notify me. I do not care unless you broke or can't update. But no, I have to dismiss every successful app update.
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
That's good information. Like I said, I have not used it.
By in large there is no difference to notice, riiiiight up till you get to invisible google integrations. A lot of people wont notice stuff like this, but android auto relys on google servers and big G managed to break microG for a couple days and we cannot cast to our Chromecast (ever :( )
Is that related to Google bricking (and now releasing a patch) the older Chromecasts? Or is this a separate issue?
Separate. Not entirely sure how it works but another user in thread brought it up, sec...
Skarn: Actually, no. e/OS includes MicroG, so even most app requiring Google services work just fine. What really doesnt't work is Casting videos to a Chromecast, and anything requiting Play Integrity certification like Revolut.
Thought he provided more info, but yeah. Chromecast just does not function cause its basically in google walled garden.
It does! And you can disable microg if you want like I have.
Actually, no. e/OS includes MicroG, so even most app requiring Google services work just fine. What really doesnt't work is Casting videos to a Chromecast, and anything requiting Play Integrity certification like Revolut.
I am fully aware of what the fairphone I'm on is able to do. Thank you for assuming I dont have experience with what I'm talking about.
The biggest one was when play Services updated back kn December and broke maps for me, specifically on android auto.
Whether you knew better or not, I mostly wanted to provide slightly more accurate information for whoever might have been reading the thread.