If they can get it to work on non-Google devices, I will consider it. Right now Graphene compatibility is extremely limited. Besides, I basically have to give Google money to avoid Google.
๐คช
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
If they can get it to work on non-Google devices, I will consider it. Right now Graphene compatibility is extremely limited. Besides, I basically have to give Google money to avoid Google.
๐คช
Yeah, it's kind of wild and ironic that one of the most private OSes requires a Google phone.
Not only that but it relies on the Pixel's black box "Titan" security chip, that google pinky-promised to open source but never did...
The Titan security chip is not a black box. The Titan M1 gas been scrutinazed by blackhat: https://dl.acm.org/doi/fullHtml/10.1145/3503921.3503922
Just because something is not open source does not mean you can't verify it (no, i'm not shilling closed slurce; no i don't think closed > open; no i don't think closed source is more secure)
'Just reverse engineer it bro'
Have people forgotten about the used market? Buying things second hand is the way.
Doesn't change that this only runs on Pixel devices. I simply don't want a Pixel device for various reasons. Used or not, Graphene won't run officially on a Sony, a Fairphone, etc.
If the security benefits of a pixel is less important then the fact Google made it then GOS is simply not meant for you.
Its silly people complain about it being only compatible for pixels but never seem to blame other android brands for making significantly less secure phones. The responsibility should be put on phone makers to create secure phones that meet GOS requirements, not to expect GOS to make a less secure OS.
The whole AOSP environment is very Google centric so its pretty weird to think because your not buying a pixel that you are somehow avoiding Google.
I have more considerations than security, like a headphone jack and other details. But you have my upvote anyways, because you make a lot of sense. I agree with you. ๐
I do agree that the lack of a headphone jack absolutely kills me. It's a reason I haven't pulled the trigger either way on a new phone yet. On the one hand, I want a secure degoogled phone that maintains a lot of functionality with GOS. On the other, I want a modern phone with a headphone jack a la Sony. I go back and forth constantly.
For what its worth, my Sony Xperia 1 VI didn't come with a lot of google apps and it was easy enough to get rid of those. Obviously play services and some other stuff remain, so it's not a degoogled phone, but it's alright. Sony asks for some analytics stuff, but that's all very easy to deny.
Sony also makes it very easy to root, unlock and flash your phone, with an official guide on how to do that. It's not as easy as installing graphene OS, but I'm sure somebody will built lineage or something for it at some point
Edit: Here are links to the official documentation, Sony makes it pretty easy to built and flash AOSP
This is great info, thank you so much! That definitely gives me more things to consider
still pricey as fuck in my country. barely any pixels here.
I'm always wary of buying second hand phones. How healthy is that battery going to be?
It is possible to replace them, with a little research. Or just taking them to a phone repair shop if you're too anxious for that
My country's second hand market sucks donkey balls. Import fees are crazy if you even dare to use Amazon instead of cheap Chinese shop. I just wanna scream.
Damn, that really sucks, I'm sorry :(
Buy a Pixel second hand. Then you're just reimbursing someone who already made that mistake. ;)
Just research ahead and don't buy one with a known hardware defect such as the 5As which are notorious for frying motherboards and screens. Went through 5 of them with the extended warranty over my phones life and they all died while in my hand abruptly. Less than a year or life per device almost always failing around 8 months for me.
If grapheneOS wasn't so damn good I would've left pixels after that, Pixel XL abruptly died, 2XL had both cameras and the fingerprint sensor die out of nowhere, then the 4 5As. On an 8a right now and love it so fingers crossed it lasts!
If they had a user repairable device that ran it I'd buy it in a heartbeat
YES :D
For people looking to change and are worried about banks bullshit here is a link to a list of currently supported bank apps.
This is stupid helpful, thank you. I wouldn't have thought to look this up on my own but now that I know it I'm a good bit more likely to try Graphene on my next phone. This is way more apps than I would have guessed.
I personally have to toggle on Exploit protection compatibility mode in App info to get some of my banking apps to work
My bank apps all work fine. Just keep your physical bank cards on you because Google Wallet won't work with credit cards, NFC or transport passes. Your gig tickets and membership cards will load fine though.
You probably don't want Google rummaging through your purchase history anyway. I certainly don't miss it.
Really helpful, thanks. Just curios, does this list apply also for LineageOS + MicroG ?
I couldn't tell you. The page / list was made for graphene and I don't know the technical differences between running that and lineage + micro g so not sure if the same list could apply. Sorry.
I would like to switch, but there are a couple of points that are still holding me back right now:
Charge limits, on LOS I can root the phone, install ACC and still use the OTA updates, if I apply the patch afterwards. (Will be resolved in A15)
Option for sandboxed MicroG, IMO privacy is also very important for security, and people should be able to decide if they like more privacy or more security.
Option for rooting sandboxed apps from outside. IMO I, and a person, like to have full control over my phone. Trust often comes with control. If I choose to trust one app to have root access to another app in order to inspect it, then this should be possible. Sandboxing could allow one app to have root access to individually chosen other apps, thus limiting the impact compared to system-wide root access. Maybe offer rooting gated behind a separate hardware token authentication. (sudo like) A lot there can be improved IMO, while still providing it and making it more secure in general.
I know that my understanding of security and privacy might be different from what GrapheneOS understands, but as a long time Linux Admin, I don't like black boxes, I like to peek into them, modify or patch them, when they do something I don't want them to do, etc. So that when I enter personal information into them, I am still in control what happens to them, at least that is my desire.
Taking control away from the user in order to "improve security" might be a valid approach to some, but it is not something I have much trust in.
I don't mind giving graphene a try but I'll be honest, I have the following issues:
It's impossible to brick a Pixel while flashing GrapheneOS, thanks to their super easy to use Web-based installer, and Google's great support for alternative operating systems, which also makes the installation process easier and safer.
If you mess anything up, you can always restart from the beginning and get it fixed. You can't break a Pixel during flashing.
Why not buy a used one? I plan on picking one up from ebay or something.
There's also CalyxOS if you don't want to run anything Google on your phone at all, but still have functional apps and such.
I mean, Graphene does that too, by default. It just has the app store available to be installed in their apps updater. If you don't go there to install it by yourself, it's a Google-less device by default.
Woot! Welcome to the club! Fuck Google!
Does RCS work reliably on Graphene? I thought Google was fucking with RCS quietly for those on custom ROMs or other things.
I don't use RCS myself, but there are recent posts on the GOS forums and it appears to be working fine once all of the prerequisites are installed.
People contemplating moving to graphene, do be aware that banking etc. absolutely can be a major PITA on graphene as well. Several official apps used where i live cannot work in graphene, even with sandboxed play services installed, making day-to-day life functionally impossible with graphene. Luckily reverting to stock android is easy, although I probably wouldn't have bought a pixel phone if I was planning on using stock OS.
Banking compatability by country. In my experience even banking apps not mentioned also work. https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
Isn't it only Google Wallet that doesn't work? I actually cancelled a bank account I had because their app only worked with Google Wallet. Some banks roll their own NFC payment thing.
I'm on CalyxOS btw, not Graphene.
GraphmemeOS