121–130 of 415 posts
Earlier quoted context omitted.
Pixel's "deep integration with Google" is in the OS, so if you replace the OS with GrapheneOS, there is no deep integration anymore.
Yes, but I made an argument about /e/OS and GrapheneOS. You never knows what will work or stop working.
Earlier quoted context omitted.
Even on non-pixel devices, unless you really want to use the /e/ "ecosystem, there are probably better options like LineageOS for microG iodéOS. (/e/ used to be heavily based on an outdated version of LineageOS for microG. I'm not sure what the current state is after I settled on second-hand pixel with graphene)
iodé is available for my device as well, but it looked fairly similar to /e/OS to me (and the latter has an official partnership with my phone's manufacturer). What makes it a better option - should I switch?
I worked at Google before, so I trust Google more than these random organizations that claim they are better than Google at handling sensitive info.
I don't think these projects claim they've got better infrastructure for handling private data, just that they won't sell it to advertisers. I trust Google are experts at handling my data, I just don't want them to.
The irony of advertising a privacy-enabled de-googled system, and then telling me that my Firefox browser is not support, and that I should use Edge, Opera or Chrome instead.... Browsing: https://e.foundation/installer/ Reply: https://imgur.com/a/al1Q9DM
I have been using e/OS but moved away when an upgrade to the next version required to manually wipe the device. I could cope with the little inconveniences of a degoogled phone, but wiping the device myself following a unclear procedure was too much for me. My phone is not a hacking subject. It's a tool. Still, it worked reasonably well and I would have upgraded and kept using it if the upgrade had been easier.
I am on e/OS since 2021 with a FP3 and, for what is worth, I never had to reinstall, wipe or anything. My phone just had it's 5th birthday and it has been a single continuous set of updates. I know the versions differ by model, so perhaps your model was not as well supported.
There's absolutely no reason to use /e/ when GrapheneOS exists. https://eylenburg.github.io/android_comparison.htm
Earlier quoted context omitted.
There are more OSS devs active on Android ROMs than OSS devs working on independent mobile OSes. We are running out of time, and we are misallocating ressources. It's like bailing out water from the Titanic. We should prepare the lifeboats instead.
(GNU/)Linux on mobile is the true sustanable, independent OS. It relies on the existing, strong Linux development, natively runs existing Linux apps and guarantees you lifetime updates. What else do you need? Sent from my Librem 5.
I’m being gently snarky, of course, but the goal shouldn’t be an MVP that nerds who are deeply into privacy or FOSS or hate Google can tolerate - it should be something that disinterested normies could seamlessly and happily use.
Earlier quoted context omitted.
(GNU/)Linux on mobile is the true sustanable, independent OS. It relies on the existing, strong Linux development, natively runs existing Linux apps and guarantees you lifetime updates. What else do you need? Sent from my Librem 5.
If mobile Linux runs through the same kind of tortuous adoption and rejection cycle that desktop Linux is still doing, then it's a non starter before it begins.