Study reveals scale of data-sharing from Android mobile phones:
Even when minimally configured and the handset is idle, with the notable exception of e/OS, these vendor-customized Android variants transmit substantial amounts of information to the OS developer and to third parties such as Google, Microsoft, LinkedIn, and Facebook that have pre-installed system apps. There is no opt-out from this data collection.
I happen to be using /e/ OS for the last ~2 years on all my #android phones and quite pleased to read it.
@xerz @kravietz it's unfortunate that the authors don't separate stock LineageOS from LineageOS with the "Optional" (but usually recommended) GApps. /e/ did get a lot of crap (validly) for not removing all traces of Google connections from their forks of Lineage, which they eventually dealt with.
https://web.archive.org/web/20210303061041/https://infosec-handbook.eu/blog/e-foundation-final-look/
@keverets @xerz
There’s one important point to that which I only recalled as we started talking about it (I haven’t used Lineage for a couple of years).
The original LineageOS #Android doesn’t have signature faking patch and its devs consistently reject it, so unless you want to stick to apps from F-Droid only you only have two choices - either install GApss, or use Lineage4MicroG, which is a fork of LineageOS.
On the latter you could freely use F-Droid apps and mainstream apps from Aurora Store, but it had more limited hardware support as compared to original LineageOS.
With /e/ you don’t really even have to think about any of that, it just works.