Find your Device with an SMS or online with the help of FMDServer. This applications goal is to track your device when it’s lost and should be a…
Find your Device with an SMS or online with the help of FMDServer. This applications goal is to track your device when it’s lost and should be a…
/e/ is not very degoogled. DivestOS or GrapheneOS would be better choices, then maybe CalyxOS.
Why is /e/ not very degoogled? It is through and through.
Here is a thorough analysis of /os’s security and privacy.
https://www.kuketz-blog.de/e-datenschutzfreundlich-bedeutet-nicht-zwangslaeufig-sicher-custom-roms-teil6/
Tldnr: it’s alright but but grapheme, divestos or calyxos should be preferred if those are available on your device.
Problematic seems the unique device id /e os generates and sends on every update and also security updates for the integrated webview browser have been severely out of date in the past.
Looks like a good and careful analysis. While I speak German, its a lot to take here, so cannot say much about the articles content (besides some of the concepts are way above my head and understanding).
But the article/analysis doesn’t seem to support your claim “not very degoogled”? (Edit: I changed this phrase, it was wrongly phrased.)
The /e/os ID you mentioned, has nothing to do with Google, as the update information is sent to /e/os servers I guess (which in itself is concerning, I’m not saying otherwise). I personally don’t see a need to switch to any of the other services (they pretty much also support microG and I can’t install them anyway I guess).
Ok, yeah, you’ve got a point I think. But one could argue if microg is enabled by default, at least some info might leak to google as their push servers are contacted and a device id is created (even if the data is anonymized to some extend.). (Depending on if these settings are enabled by default in microg which I am not sure of).
Here’s some info from the divestOS faq (cmp.: https://divestos.org/pages/faq):
"Anything important I should know about microG?¶
It goes on to provide some guidelines if you want to use microg:
How should I configure microG?¶
"Depending on the apps you want to use there are a few different ways you can use microG.
So depending on your thread model, you still would want to disable some of the options in microg to have absolutely no leakage of data to google. For example I am not comfortable any more with using push notifications since it was revealed that state actors use this info to tail users communications.
There is no android ROM that is fully degoogled without losing out on much of base Android’s functionality. See the table I link under the other person’s comment. I have also heard that /e/ OS falls behind on package updates from its forks of other projects, many of its default apps.
/e/ does quite a good job removing Google’s presence from Android. It’s been awhile since I watched it, but this techlore video does a good breakdown of it.
Edit: actually that’s not the one I was thinking of, I’ll keep trying to find it, but it broke down the actually network connections that different degoogled ROMs were making and /e/ did very well.
Edit 2: couldn’t find the video, it’s lost somewhere in my watch history from 2+ years ago. In any case, even jumping to lineage from stock android is a great move, and /e/ makes many improvements on Lineage in removing further dependence on google code. Better to use a phone you already have than to purchase a new device just to run software that has security features you likely don’t need. It makes me think of buying a car for it’s top speed of 160 mph when you’re only ever going to be driving the speed limit.
https://eylenburg.github.io/android_comparison.htm
I’m not sure what your point is with this reply?
I’ve seen that page before, it’s helpful for getting your bearings with the different android ROMs, but take a look down towards the bottom at the “Supported Devices” section, and also compare the /e/ section to the “Stock Android” section.
Here is an alternative Piped link(s):
this techlore video
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.