For those that are looking to install GrapheneOS and want to ensure that their banking apps work as intended, here is a curated list of supported apps per country:
I've personally tried Lineage, CalyxOS and Graphene. I'm currently on Graphene because it has the most app compatability and at least has higher security claims than Calyx which is more FOSS/privacy focused with microg vs graphenes sandboxed Google play.
What really got me to switch was once banking apps started failing to work due to microg compatibility. That may or may not have been resolved by now.
If Privacy and avoiding sending any data to Google is your priority I would do Calyx since you can get push notifications through microg without signing into Google and you can get apps anonymously through the aurora store.
However if you want a better user experience I would suggest GrapheneOS with Sanboxed Google Play. It's very solid and I haven't had any issues getting any apps to work thus far.
I do not at least here in the US where I'm located only Google pay and Apple pay are supported. I have heard some Europeans mention their banking apps natively support their own contactless payment when I'm pretty jealous of
I haven't tried it myself, but you could get a Garmin watch and add your cards there. I believe you don't need the phone connected afterwards to make payments.
GrapheneOS only publishes updates for devices with active security updates. Your device is EOL and therefore won't receive any further mainline updates. It still will receive extended support from the Android 14 legacy branch with whatever security patches arrive in upstream AOSP, but unlikely to see device-specific patches nor firmware patches. Your device isn't getting the same care and attention that active devices are receiving nor will it receive any future versions of Android through GrapheneOS.
It's very hard to say. Based on your use case I would say either grapheneOS or calyxOS. I personally have a bit of a soft spot in my heart for CalyxOS but technically speaking graphene likely meets your usecase better.
I use Graphene. I like the Auditor app and the ability to verify that the ROM is unaltered because you can never trust an orphan kernel like all mobile devices. If I ever give up possession of my device, I can verify if it was altered. I also have a way to wipe the device on locked login with no indication that the ROM is being wiped as provided by Graphene.
This is my second iteration of CalyxOS, I used to rock a Pixel 4a and now I'm on a Fairphone 5, and I love it. It's rock solid and never had a compatibility issue, although I heard that some banking apps might misbehave with microg, but not in my experience.
Graphene has pretty much the same approach but instead of supporting microg, has decided to take the route of sandboxing Google Services, which is a better route for compatibility at the expense of letting some of your data leak through once in a while.
/e/OS is a wonderful project on paper, but in my experience it was the one with more issues and bugs: they try to support as many devices and services as possible, providing a full environment that's easy to setup for any user, but having to deal with so may things makes them a little hit or miss sometimes. Nonetheless I still believe they're a great project that brings privacy to the less techy people with a (mostly) working ecosystem.
LineageOS isn't focused on privacy but in extending the life cycle of devices after they've been discontinued, so if your concern is to be private I'd go with something else.
Don't underestimate the bootloader locking feature: once your whole life is connected to one device, you don't want a guy with a USB cable be able to access it in case of loss/theft. DON'T ASK ME HOW I KNOW IT.
May I please ask whether an unlocked bootloader is still bad for privacy and the risk of data loss/theft, if the phone is enrypted?
My understanding is that while being able to mess with the phone (e.g. including installing a new OS) in the presence of an unlocked bootloader, a properly encrypted phone at least protects the data on it.
Did I get that wrong?
Both /e/os and Iode have built in tracker blockers that do a pretty good job at blocking most trackers. Used /e/os with my OnePlus 6t and liked it a lot. Probably the reason I have used these l.
Upgraded to a OnePlus 9 pro and trying out Iode OS. Havent decided if I like it more, or just getting used to it.
Is there a standalone tracker blocker that can be a similar to these that can be ran on any Android OS?
There's this article in a German IT sec blog which compares the more well-known privacy focused ROMs. If you have any way to translate it, you should check it out. It is a really nice addition to the Eylenburg comparison.
i want customization to my os as long as this is possible
I was rocking Ressurection Remix and Xposed on my old Note 4 and customized the hell out of it. I'm on Graphene now and I don't miss it a bit. Maybe a little.
Graphene can be installed on your phone via a web browser on a PC on laptop. You should install it and try it out, it's very easy.
Graphene can be installed on your phone via a web browser
sorry but that's misleading. it only works with chrome (and honestly better keep it that way). do we really expect in the privacy community that people use chrome?
Ubuntu – few applications, unstable: over time, some problems with the volume were, cured only reboot; there is no normal application Telegram (web client that the battery eats).
CalyxOS is subjectively more convenient, F-Droid and RuStore download by machine, F-Droid installs an update machine, RuStore downloads and asks for /e/OS RuStore to download forcibly. Also on both MicroG systems, but on /e/OS, SBPay bent and didn't work, on CalyxOS - no problem. Similar to applications, for example, for renting scooters: on /e/OS some problems, on CalyxOS - no problems. There are fewer problems with CalyxOS.
With Sber, Rosselkhozbank and Unicredit, there are no problems there or there. Russian mail application does not work on any platform.
The only plus/e/OS is what is in GooglePlay, but not in RuStore, it is easier to put: AuroraStore on CalyxOS makes you go out and log in all the time to update the installed applications; on /e/OS, what is installed in your home store, including with Google PlayStore applications is updated without problems by automaton.
Only consider CalyxOS and GrapheneOS. Ideologues will push you exclusively towards GrapheneOS but it's not th be-all solution for all people that they think it is. My current and previous phone are GrapheneOS. It's fine. It does what I want. I don't find it amazing only because it's a phone, not a new discovery. I use GrapheneOS with F-Droid with all anti-features disabled in F-Droid settings and I have all the apps I need.
Lineage will likely wirk with random phones, that dosn't mean it's quality. I say, if a phone OS works on LG, Samaung, Nokia, and a Chinese company phone, I don't trust the stability of the OS.
I see the name e/OS around, I don't hear it ever mentioned in public discussions, I think it's for Fairphone or one of those gimmick name phones.
I've never heard of DivestOS before you mentioning it.
Lineage will likely wirk with random phones, that dosn't mean it's quality. I say, if a phone OS works on LG, Samaung, Nokia, and a Chinese company phone, I don't trust the stability of the OS.
that's just plain bullshit with at most zero backing knowledge. supporting various brands really won't make the software that complicated. the software you install won't need to include compatibility patches of all the supported brands and models, it's routine that system images are customized for the phone, with patches specifically for that phone.
I mean yeah LOS is not the best in quality, but the remaining part does not make sense
DivestOS sounds interesting but I am wary of any "mission-critical" software project (such as the firmware for my primary phone) that relies on a single person, for multiple reasons. Burnout and potential for social engineering by malicious actors being two of them.
GP:s comment made me curious as well. Usually, if multiple hardware vendors are supported there are separate branches with different maintainers. It doesn't necessarily mean that the main codebase is bloated as a result.