Im considering buying a new phone and i don’t really consider a Pixel. I really like Fairphones approach, with the self repairable stuff. Even though they don‘t have a headphone jack. But well… I can’t change it. I’ll definitely go with the adapter over wireless headphones.
But to my question: What private OSes are there? Fairphone sells FP4s with eOS, how is that? And does it work on the FP5? GrapheneOS only works on Google Pixels right?
As somebody that might be changing phone sometime this year and to cover all the possibilities, do we have a recent comparison of all these projects?
Yes! There is a really helpful (from a privacy and security standpoint) comparison chart here. It also includes GrapheneOS and “stock” Android.
deleted by creator
/e/OS is often a month or more behind on Android updates (including security). Unacceptable I think.
Some info about patch history here: https://www.divestos.org/pages/patch_history
General comparison table of Android ROM features: https://eylenburg.github.io/android_comparison.htm
Don’t forget iodéOS!
DivestOS is a good option
There are only a few to consider. /e/os if you want it easy or DivestOS if you want it most secure and private. All the other possibilities have disadvantages compared to these.
Please be aware that you should buy FP5 as FP4 has huge hardware issues and the support is a dissapointment.
/e/ is announced as ‘degoogled’ but that’s not 100 % true (and not nearly as well). For example MicroG connects to Google as well as connectivity backup check. Patch level is far behind AOSP. The App Lounge uses clean APK for some apps which is very risky. Communication is a problem and they do not react like they should for example when Mike Kuketz analysed /e/ and found several problems.
The community is huge and they support many devices.
DivestOS is better in most points but is managed by one person alone. MicroG is not included by default (if you need it) and multi sim support is a problem.
You can disable microg connecting to google servers, but basically you get a standard gms free experience, with most apps simply not working from play store. They list in the wiki how and why they connect to google: https://github.com/microg/GmsCore/wiki/Google-Network-Connections
A completely google free experience would be unusable for “normal” people, so they somewhat right as they target “normal” users. I also don’t like /e/, but because they are deliberately obfuscating a lot of things in their documentation, and they try to sell their os as something genuine, but it’s mostly just AOSP with microG.
DivestOS is the way to go.
I’m on CalyxOS, it works great. Locked bootloader, ability to block connection of devices when screen is locked (defeating cellebrite’s method of choice), work profiles and firewalls etc.
Yeah Fairphones all are fair and whatnot until you find out their software isn’t fair and they don’t give a shit about managing security properly nor collaborating with others such as GrapheneOS.
I use MicroG LineageOS which is in my opinion comparable with graphene os and is supported by a lot more devices.
Graphene and Lineage are the most uncomparable custom roms. Have and look at security and privacy and the type of Google Play handling.
See https://eylenburg.github.io/android_comparison.htm to geht a first idea
Yes, GrapheneOS only works on Pixel devices, because the project has some pretty extensive hardware security requirements: https://grapheneos.org/faq#future-devices
The Fairphone is a highly insecure device, which comes nowhere close to the (hardware) security of a Pixel. On top of that, the Fairphone company doesn’t even know how to maintain their own Fairphone OS. The verified boot implementation is fundamentally broken and very misleading, since it’s signed with the publically available (!!!) AOSP test private keys. This is such a blatant disregard of security practices, that should have made it impossible to certify their devices. It’s not a surprise either that Fairphone regularly misses important Android security patches, or delivers them months later. That’s also why GrapheneOS will never support devices like the Fairphone. There are more issues with Fairphone’s misleading update policy that I haven’t covered in detail.
I highly recommend against purchasing such insecure, and poorly maintained hardware. DivestOS is the best option for “damage control”, if you already own a Fairphone. Its developer actually cares about users and their security, and the OS is properly signed.
I’ve never heard of Fairphone and have only barely heard of DivestOS.
There are several degoogled OS options for the Fairphone models, with different levels of degoogling and privacy: LineageOS, CalyxOS, DivestOS, iodéOS and /e/OS.
Most of these are based on LineageOS (I understand that CalyxOS isn’t, but I might be wrong). I personally use iodéOS and I like the helpful developers, the ability to remove / replace any of the apps preinstalled with the system, and the iodé blocker which blocks trackers, adds and any connection you want to at a system level.
Fairphones can also run CalyxOS if you want to look into that
May i know why you do not like the pixel phones?
They are expensive and I don’t want to give money to Google
They are expensive
Sometimes you get what you pay for, and…
I don’t want to give money to Google
I get that, but your purchase (the entire Pixel department, to be honest) is a drop in the ocean to their profits. They won’t notice you not buying one at all. You’re handicapping yourself in the mobile security arena (not being able to install GrapheneOS) to take the high ground and not effect a tech giant.
That aside, if you really don’t want to give Google, buy one from a reseller and not from the Google Store.
If you don’t want to give money to Google, why not take money from Google?
Then, once you’ve offset enough money, then you can buy a Pixel at an overall loss on Google’s side.
They are way cheaper than fairphones where I live.
Sorry I wasn’t comparing to fairphones. I was comparing the minimum you’d have to pay for a phone that has everything you could possibly need with the only difference being a not-that-great camera. So like a budget Xiaomi phone that I use.
I highly encourage everyone to buy their pixel phones for grapheneos secondhand. there’s enough pixel fanbois out there you should be able to deprive any corporation of the money of your sale by buying a like new condition last generation pixel (Like an 8 now that the 8a and 9 are out)
Yeah that’s not a bad idea
Recently bought a used Pixel for just under $200.
I refuse to buy new when a 1-2 year old flagship is 1/3 the price of new.
Especially since when was the last time you got a phone that impressed you? Like phones haven’t been getting better they’ve been getting more gimmicky
Yup. Bought a secondhand 7a for ~$250. Maybe I should have looked for an 8, but honestly I don’t think the 7a is too bad all considered.
they sometimes retail at a loss around the holiday season.
I dont know. Its not that I dislike pixels, I just liked the concept of Fairphones. And I just never thought about google phones because I thought google and privacy don’t match, even if I have a different OS installed.
Depending on your linux knowledge, you may want to use real linux (postmarketOS). But beware, the amount of things that require closed source OSs like android or ios isnt 0. banking apps for example arent accepting of non proprietary phones yet. I dont know about emulation though.
Not true. I’m a Tangerine customer and have no issues at all with their app on Graphene.
That is one usecase. I‘d be a little more thoughtful about my first sentence if I were you.
That one use case literally invalidates the claim that banking apps don’t work. Your banking app might not work, but mine does.
Thats not how logic works my friend. If 99 people cant get it to work and you do, that makes the claim not invalid but either you lie or you have an „unusual“ setup. The claim still holds true in most cases.
Instead of waltzing over someone like this, you could try and show interest in their usecase and how to troubleshoot the underlying problem. That would be making the world a better place.
I’m not here to troubleshoot this issue. I don’t have the technical skill or understanding of this platform to do so.
I’m sure I’m not the only one with a working banking app. We don’t all use mainstream banks, right? There are options and I’m sure I’m not alone in this.
Thanks for insinuating I’m a liar though. That’s nice.
I’m on a Pixel 8 with GrapheneOS and a working banking app with no special fuckery because I genuinely don’t know enough about android to deviate from what’s offered in the stock Graphene experience other than using the FUTO keyboard and customizing basic settings just like everyone else.
For emulation there is Waydroid. I’ve never tried to run bank apps with it, but everything else worked smoothly.
Thanks for mentioning it. I heard about waydroid but havent tried it yet.
I’ve used it in multi windows mode with a libhoudini (installed thru a script, I think it was this) (had no luck with libndk) on desktop (x86) because some android apps are not compiled for x86. No need for it on an arm devices.
If you have a dual gpu setup, enable software render because it got issue with dual gpus (see here).
I daily drove a Oneplus 6 with PostmarketOS for a few months. While it was very cool and gave me a bunch of freedom compared to android, I missed things like always having proper mobile UIs and a working camera. It is my understanding that the fairphone 4 is in a similar state of support, if a bit worse. Can recommend it though if you like using linux and don’t need banking or a camera from your phone.
Thanks for chiming in. I agree that pmos is not a perfect drop in alternative for android yet. but for me it is 1. not necessary to have a perfect copy and 2. not a permanent situation since pmos is picking up steam, same as the rest of linux. So I believe cameras will become usable at some point and banking apps will probably also come around at some point. The more people use it, the faster imo.
Every few months or so there is news of what hurdle has been overcome getting the camera on the oneplus 6 to work. So you might be right there.
FP4 with CalyxOS works perfectly.
Graphene does only work on the pixel devices. What makes it special is that you can lock the bootloader again after installing it, which with things like lineage, you cannot do. I have never used /e/OS but i use lineage as my daily and it can be installed on FP
Honestly trusting the bootloader feels very risky
Ok what is your alternative? Android Verified Boot with a secure hardware keystore like the Google Titan M2 is basically the best thing you can get.
Strong encryption with a password you know only. The password should have a high enthropy
This is unrelated. You want to familiarize yourself with the concept of OS integrity and how it is different from data encryption. You can have a passphrase that encrypts your data alongside having access to these hardware features.
I’d be more worried about the ROM that runs before the bootloader that you can’t inspect, or possible hardware implants if you don’t trust the bootloader shipped to you from the vendor.
I don’t trust it not to be flawed
GrapheneOS uses pixels because not even Google employees can break into it.
Yes. Insider Attack Resistance is pretty awesome.
It has very minimal code and its implemented in a robust manner. Unlike UEFI and the desktop implementation of secure boot, it does work well and it has not yet been exploited on pixels. Its way better to have any kind of OS integrity check than none.
In that case, have fun coding up your own bootloader and flashing it onto the device. If you can’t trust the bootloader, then you can’t trust anything at all from the operating system that sits on top of it, because it could be compromised. If you can’t trust a bootloader, then the only thing you can trust is a pen and a piece of paper.
why dont we just put uefi on phones
Phones don’t use an IBM-PC architecture. You’d need a phone based on an architecture phones aren’t usually based on or You’d need to re-engineer UEFI to work for an architecture it wasn’t designed for
UEFI has supported ARM for years now…
And “phones don’t use UEFI”
True but it feels like obscurity via obscurity.
A huge park of the bootloader stack is opensource…
https://android.googlesource.com/platform/system/core/+/master/fastboot/
What makes it special is that you can lock the bootloader again after installing it
I’m not sure why this is considered special. You can also re-lock the bootloader with CalyxOS, iodéOS and DivestOS. This is a Pixel thing, not a GrapheneOS thing.
Okay, I was not aware of that, so thanks for the information.
It’s also possible to relock the bootloader on a handful of Motorola and fairphones, at least as part of the Calyx install procedure
