GrapheneOS – Break Free from Google and Apple
51–60 of 967 posts
Re: GrapheneOS – Break Free from Google and Apple
#52Does anyone have a good grasp of the differences between GOS and /e/OS? I'm buying a Fairphone soon and was wondering what both are like
Consider this (by Graphene OS): https://discuss.grapheneos.org/d/24134-devices-lacking-stand... /e/OS community talking about it: https://community.e.foundation/t/article-from-grapheneos-abo... And then maybe this: https://eylenburg.github.io/android_comparison.htm Hope that helps.
Sure they have hardened everything but realistically, that's not the main threat for your average user.
Their top contribution to android is the sandboxed Google Play, by far.
Re: GrapheneOS – Break Free from Google and Apple
#53Many are complaining about banking app compatability, but I've never felt compelled to use anything other than my browser for banking. What's the big deal with the banking apps? Am missing out on some huge advantage here?
Re: GrapheneOS – Break Free from Google and Apple
#54We need Linux OSes and phones to catch up to really break free from this duopoly. Only when there is enough traction, essential infrastructure like banks will start supporting Oses like that. It's a chicken and egg kind of problem.
Why start from scratch?
Re: GrapheneOS – Break Free from Google and Apple
#55I've been using GrapheneOS for about 3 years now. For the most part, it works very well. I don't have any issues with banking apps, nor any other closed source apps. I'm using two profiles both with sandboxed Google play installed. I'm logged in into my private Google account on the work profile. However, there was one case that lead me to thinking about ditching grapheneos to this day. I installed Uber on my phone a…
Re: GrapheneOS – Break Free from Google and Apple
#56While I admire GrapheneOS and its goals, I feel that until we free the proprietary baseband processors and their RTOS from the grips of Qualcomm and friends it's a pyrrhic victory, at best .
Re: GrapheneOS – Break Free from Google and Apple
#57What about device attestation? Will you be able to run banking apps and Netflix et. al.? For me the biggest concern is that while you may be able to use and run your own device, you will be locked out of most propietary services. Much like how more and more websites simply don't work with Firefox anymore.
Re: GrapheneOS – Break Free from Google and Apple
#58Re: GrapheneOS – Break Free from Google and Apple
#59While I admire GrapheneOS and its goals, I feel that until we free the proprietary baseband processors and their RTOS from the grips of Qualcomm and friends it's a pyrrhic victory, at best .
When there isn't a perfect solution, the next best thing is... the next best thing :-).
Re: GrapheneOS – Break Free from Google and Apple
#60Does anyone have a good grasp of the differences between GOS and /e/OS? I'm buying a Fairphone soon and was wondering what both are like
/e/OS (and similar "non-LineageOS" ROMs really) instead focus more on de-Googling. They're still generally security focused, but the priority is less "someone's after you" and more "corporate surveillance is kinda scary innit". The aim is less to avoid someone actively trying to drain your phone of data and more to prevent your phone from passively sending everything it can possibly find to the Big G's ad machine (as well as whatever other trackers get snuck into apps.) Because of this, they usually have better depreciation timelines and support a lot more devices compared to GOS who only support the Pixel line (which is an increasingly awful set of phones truth be told); their scope is much smaller.
Finally, it's worth noting that the GOS community is absurdly toxic to anyone doing anything privacy-related that isn't under the banner of GOS. It's extremely maximalist, tends to get very upset at other projects whenever they get attention (see sibling reply to this, where they pretty much melted down because an outlet dared to recommend a Fair phone+/e/OS) and the projects official channels have generally encouraged this sort of behavior. It doesn't really damage the software itself, but it's worth considering.