this post was submitted on 21 Mar 2025

1 points (100.0% liked)

Privacy Guides

19767 readers

1 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.

You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...

Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!

This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.

Moderation Rules:

We prefer posting about open-source software whenever possible.
This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
No soliciting engagement: Don't ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don't repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 2 years ago

MODERATORS

do regular apps work with eOS? (sh.itjust.works)

submitted 4 months ago by HenriVolney@sh.itjust.works to c/privacyguides@lemmy.one

26 comments fedilink hide all child comments

all 27 comments

sorted by: hot top controversial new old

[–] Neptr@lemmy.blahaj.zone 1 points 4 months ago (3 children)

eOS is just Android, so Android apps work.

That aside, eOS has a history of being often behind on security patches and updates, so it is highly recommend to avoid it.

[–] HenriVolney@sh.itjust.works 0 points 4 months ago (1 children)

Are there any other Android based OS that are neither Google nor flawed?

[–] Neptr@lemmy.blahaj.zone 0 points 4 months ago (1 children)

GrapheneOS

[–] HenriVolney@sh.itjust.works 0 points 4 months ago (1 children)

Thanks. Does it work on a Nokia 7.2 though?

[–] Neptr@lemmy.blahaj.zone 1 points 4 months ago

Sadly it only works on Google Pixel. I'd recommend LineageOS, but the images aren't signed so you can't lock the bootloader.

[–] skarn@discuss.tchncs.de -1 points 4 months ago

That also depends a lot. Often (e.g. on Fairphone) the stock ROM may lag behind way worse than e/OS.

So if a user has reasons to avoid a Pixel, or just wants to improve their privacy without replacing their device, e/OS may be a marked improvement even on security.

[–] Pherenike@lemmy.ml -1 points 4 months ago (2 children)

I've been on eOS for four years and I have never had a single security incident. You people love to parrot the same shit over and over

[–] mybuttnolie@sopuli.xyz 1 points 4 months ago

I never use seatbelt and I still haven't been in a car accident

[–] Cheradenine@sh.itjust.works 1 points 4 months ago (1 children)

Just because you have not had a problem does not mean they aren't behind on patches.

Table here web.archive.org/web/20250115203332/https://eylenburg.github.io/android_comparison.htm

[–] Pherenike@lemmy.ml -1 points 4 months ago* (last edited 4 months ago)

I didn't say they weren't. I simply think that the implications for the average user often get blown out of proportion, because I've heard from absolutely no one who uses eOS on the forums for example that they've had a problem with their phones derived from that delay.

[+] bad_news@lemmy.billiam.net 0 points 4 months ago (1 children)

[deleted]

[–] Baaahb@feddit.nl 0 points 4 months ago (1 children)

Unless that app requires google play services...

[–] Cheradenine@sh.itjust.works 0 points 4 months ago (1 children)

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.

[–] Baaahb@feddit.nl 0 points 4 months ago (1 children)

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.

[–] marauding_gibberish142@lemmy.dbzer0.com 0 points 4 months ago (1 children)

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?

[–] Baaahb@feddit.nl 0 points 4 months ago (1 children)

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.

[–] marauding_gibberish142@lemmy.dbzer0.com 0 points 4 months ago (1 children)

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

[–] Baaahb@feddit.nl 0 points 4 months ago* (last edited 4 months ago) (1 children)

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.

[–] marauding_gibberish142@lemmy.dbzer0.com 0 points 4 months ago (1 children)

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.

[–] Baaahb@feddit.nl 0 points 4 months ago (1 children)

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.

[–] marauding_gibberish142@lemmy.dbzer0.com 0 points 4 months ago (1 children)

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

[–] Baaahb@feddit.nl 0 points 4 months ago (1 children)

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.

[–] marauding_gibberish142@lemmy.dbzer0.com 0 points 4 months ago* (last edited 4 months ago) (1 children)

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

[–] Baaahb@feddit.nl 0 points 4 months ago (1 children)

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.

[–] marauding_gibberish142@lemmy.dbzer0.com 0 points 4 months ago (1 children)

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.

[–] Baaahb@feddit.nl 1 points 4 months ago (1 children)

There are significant portions of android that are effectively under google monopoly, in truth, if not technically in fact.

First android is a phone OS, don't assume desktop rules really apply the same way. There's not tons of use for a workspace here, or at least not in my personal experience. Its my phone, my phone IS my workspace.

Second, android makes the assumption that you want basic functionality like email, and internet use, and messaging, location info for mapping, etc, so all of that got coded directly in to the OS. yeah you can use Firefox but can you uni stall chrome? Can you unintstall gmail? Often the answer is no, as you aren't the admin of your phone, the carrier is and they have deals with google.

There are attempts to work around this, AOSP is one of them, but the fact that its a thing in the first place illustrates what I'm trying to say.

Third, among those things google has an effective monopoly on is their app store. Its incredibly difficult to, as a normal person who is not especially technically inclined, to make heads or tails of fdroid, or worse to have to find your own app store.

Thus, /e/os is stuck. Package microg, or dont provide access to the google app store for their consumer focused devices, or use google play services.

Packaging microg was easily the best option from the perspective of a business that wants to sell a functional device.

As to the specifics of AOSP folk, they're basically the arch nerds of android. I love them but I dont understand much. I do know that it does not seem as though AOSP as a ROM is widely used, and that many of the projects around deGoogled android are basically single person communities, in that one person does all the work and burns out (Linege) or are... toolbags is the term I'm going to diplomatically use. Specifically graphene where the admin wound up being a toolbag, bad enough for Louis Rossman to do a video on.

[–] marauding_gibberish142@lemmy.dbzer0.com 1 points 4 months ago

I think we are still miscommunicating, partly due to my fault.

There's not tons of use for a workspace here, or at least not in my personal experience. Its my phone, my phone IS my workspace.

When I said "workspaces" what I meant is a "Work Profile" - you know, the kind of thing you manage with the shelter app and that companies use MDM for to manage their company-specific apps.

Second, android makes the assumption that you want basic functionality like email, and internet use, and messaging, location info for mapping, etc, so all of that got coded directly in to the OS. yeah you can use Firefox but can you uni stall chrome? Can you unintstall gmail?

Android doesn't make these decisions, Google does. It is a common misconception that Google ships AOSP with Pixel. They do not.

Third, among those things google has an effective monopoly on is their app store. Its incredibly difficult to, as a normal person who is not especially technically inclined, to make heads or tails of fdroid, or worse to have to find your own app store.

If you don't want Google apps, either install a custom ROM or get root access (I hear KernelSU is making great progress). I don't think your point is valid, you're talking about stock ROMs. I'm not. And God help people who buy from a carrier, that's probably the worst way to get a mobile phone.

Don't want to use PlayStore? Use Accrescent + Obtanium + F-Droid + Aurora (preferably in that order). There is no longer a reason to have playstore installed on your device unless one of these FOSS projects die or you paid for apps from the playstore before. I'm perfectly comfortable with using these instead of the pre installed spyware they ship me.

There are attempts to work around this, AOSP is one of them, but the fact that its a thing in the first place illustrates what I'm trying to say.

AOSP is not a workaround, it's what Google bases their OS on (what they ship with the Pixel) along with other manufacturers. Yes, Google writes a lot of AOSP but it is FOSS and available to anyone. Otherwise Huawei wouldn't be able to make Android devices at all.

Thus, /e/os is stuck. Package microg, or dont provide access to the google app store for their consumer focused devices, or use google play services.

eOS is FOSS. Murena is the business. And no, I don't agree - they could have at least given us an option (like LineageOS does) to either have microG or not have it in the base image. This is not a hard thing to do.

I suppose I can just rip MicroG out and only install it in a "Work Profile" but not having to do that would be a great QoL upgrade.

I do know that it does not seem as though AOSP as a ROM is widely used

Giving credit where it is due: due to Google's efforts in making project Treble compatibility mandatory along with further enhancements to the Android software ecosystem, you can technically run AOSP's (or really, any ROM's) GSI on any phone you can unlock the bootloader to. That is only possible on the Pixels, older OnePluses, some Motorolas and some Nothing Phones in the US, excluding Murena's phones and some other niche manufacturers. There are caveats due to proprietary firmware but that's where we are right now.

In conclusion: I would have liked an eOS without MicroG pre-installed. I suppose I could rip it out but I'm afraid I'll miss some artifacts. But that's a minor worry. I'm sorry for the long note.

How authors of software projects behave has never been my concern when evaluating their projects technically. I'm no expert, but I'll pay tribute to Gr******OS for everything that they have done for the community; hardened Malloc by itself is a great advancement in the Linux kernel. Unfortunate that two people like them at the forefront of FOSS have disagreements, but I do not care. I hope both of them live long and healthy and bring FOSS even greater achievements.