GrapheOS now officially supports....
[please... something other than Pixel....]
Pixel 9
this post was submitted on 30 Aug 2024
479 points (98.4% liked)
Technology
59593 readers
3041 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
The problem is that (as far as i know) only pixels fulfill their security requirements, for example that the bootloader is not only unlockable but also lockable. But I also would like to have more devices supporting it
Fairphones should be supported imo. CalyxOS relocks the bootloader and they supported the FP5 right after launch.
CalyxOS relocks the bootloader and they supported the FP5 right after launch.
CalyxOS is not a hardened OS, and GrapheneOS requires more than than just relocking the bootloader.
Fairphone's devices do not meet basic security requirements for hardware, firmware and the software device support including drivers. Please look at the hardware requirements at https://grapheneos.org/faq#future-devices and check for yourself how many of those are provided by the Fairphone. Even the Fairphone 5 has a CPU core from 2021 without even PAC and BTI.
Thanks for the info!
Fairphone should sell phones outside of Europe
Unfortunately neither of us get what we want
You can get the previous model (FairPhone 4) in the US through Murena.
Paying full price for a phone that was weak when it released 3 years ago that is also missing most US cell bands and is locked to T-Mobile.
Oh and also the parent company doesn't ship anything to the US, so parts are aftermarket only.
That's not available in the US: that's you can hack together a workaround.
Yup, I looked into them because so many people talked them up, but due to all of those issues you mentioned, I crossed it off my list. I ended up going with Pixel 8 due to long software support, GrapheneOS compatibility, and acceptable repairability, though I would have preferred a PinePhone Pro (if it had better speakers and software support) or FairPhone (if it had better support in the US).
I guess we'll see what happens when my phone goes out of support (so, 6+ years?) or I break it.
gos is open source. If the fairphone people wanted to maintain a fork of GOS for their phones, they could.
And they could discuss w/ GrapheneOS devs about upstreaming changes and collaborating on longer-term support. I highly doubt GOS project has the resources and desire to support another phone line.
Many other devices are supported by GrapheneOS at a source level, and it can be built for them without modifications to the existing GrapheneOS source tree. Device support repositories for the Android Open Source Project can simply be dropped into the source tree, with at most minor modifications within them to support GrapheneOS. In most cases, substantial work beyond that will be needed to bring the support up to the same standards. For most devices, the hardware and firmware will prevent providing a reasonably secure device, regardless of the work put into device support.
if fair phone wanted to, they could, but gos will not volunteer for the work.
And that's completely fair IMO. If FairPhone did do the work and supported US customers as first-class on their platform, I'd probably buy my next phone from them.
Fairphones aren't even anywhere close to meeting the security requirements of GrapheneOS. Daniel Micay explained this many times, most notably in this Reddit thread (before they left Reddit and switched to their own, self-hosted forum) https://redlib.nohost.network/r/GrapheneOS/comments/10b5x4n/has_anyone_managed_to_install_grapheneos_on_a/j67pbny
load more comments
(1 replies)
load more comments
(1 replies)
They will only support Pixels for the foreseeable future, as these are the only devices that meet their hardware security requirements https://grapheneos.org/faq#future-devices
I am currently in the market for a new mobile phone. The current's one battery is basically dead and because of security patches now being about 2 years old I have to replace it whole instead of just getting the battery replaced again.
Pixel with GrapheneOS has been my number one choice for some time but...
- there is no (privacy friendly & legal) replacement for Google Play Protect. My banking app won't work without it as well as one other app I kind of need too.
- I am also just too used to having a phone in the 250-300 EUR range in the sense that I don't have to care about it that much.
It's a "consumable" product for me. Loosing/drowning it is not a big deal, where drowning 800 euros is just hard to justify no matter how much money I make.
I will probably just get the OnePlus Nord 4 instead because of their pledge to do 6 years of updates.
I'm not sure about over in Europe but around here the trick to an affordable Pixel is to just buy last years model since you can usually find them lightly used or even new in the $300 - $400 range and updates are only incremental anyway and since they get 7 years of updates now it should be good for quite a while.
For google play protect yeah thats a bummer, I just use my banks website but I don't know if European banks allow that.
Personally though I love Graphene OS it turned my phone from a device I hated due to anxitey I feel around corporate surveillance into a device I genuinely like again.
i can especially relate to the last part, it's so freeing to feel in control of my phone!
load more comments
(2 replies)
- All of my banking apps work, I have 6 of them.
- You can buy an older Pixel, 5 or 6. They're still great.
load more comments
(1 replies)
Buy used, and/or buy an "a" model.
GrapheneOS is clearly the ideal ROM/OS, but alternatively there is another privacy and security centric ROM that supports a lot more devices, with the trade-off being it's not GrapheneOS.
Check out DivestOS and it's supported device list to see if that's a better fit for you. It's from the same developer as the Mulch and Mull browser forks.
As far SafetyNet/Play Project and other anticonsumer "security attestation" features, some bank apps will work fine, what others won't.
Does their website provide PWA support?
Just buy an older supported device if grapheneos is important to you. Something like a 6 pro would be fine.
To anyone reading this a 6 is a great pick but its worth knowing that the 7 year update promise only began with the pixel 8 so if you buy a 6 in 2024 it probably only has about 2 years of updates left. However they are only like $150 used I think so the value is probably there even if you only get 2 years of use out of it.
What's the point of Goggle's security support when you're buying the phone for GrapheneOS?
To get Android into a fully patched state, you need both firmware updates that come from your phone's vendor, as well as OS patches that come from your OS developer (in this case GrapheneOS). GrapheneOS usually only provides OS updates as long as Google provides firmware updates, because they don't want people to run outdated and potentially insecure devices with old, unpatched firmware. But they have extended update cycles for some EOL devices like the Pixel 4a (5G) and Pixel 5.
7a was the sweet spot for me, even if $300 is frankly a lot by my measure. But I think it was a worthy investment for me.
Would definitely not get a pro since the 7a is already on the edge of what I can use with one hand. Same for 7 but downplayed, I didn't opt for this one because it has a glass back.
300€ is not disposable for me... People are used to buy phones over 800€ but 300€ is already quite a price
load more comments
(3 replies)
Lead dev of grapheneos is extremely toxic in communication. I don't trust someone like that developing the software running on a phone.
EDIT: This comment seems to be particularly controversial, with many people praising GrapheneOS as a project, while ignoring the developers views and actions. Although my opinion of the main developer is negative, the project itself and its goals are great. To clear up some confusion, I want to add to my previous statement:
At first, this seems like the standard "separating art from the artist", however, GrapheneOS is a ton of code, not just art. When it comes to other forms of art, like literature or paintings, an artist maliciously hiding their personal beliefs in their otherwise "unbiased" work might degrade the quality of the final result, but does not have much significant impact outside of that. When it comes to code, programs, OSes, this changes. The artist (programmer) changing their art (code) based on their personal beliefs is not just a degradation in quality, but a security risk for anyone running the code and trusting the developer. Having seen the way the GOS dev speaks about its community and even people in support of him (see Louis Rossman's video), it becomes clear that the mentioned "risk" of malware is very much present. Like many others, I don't have the time to verify the source code of an entire Android rom myself, which means I would have to trust the GOS dev to not insert anything malicious, after the statements he's made. I'd have to trust him after he's grouped a majority of his community into "people who are after him and are swatting him". It's a very real possibility that someone with beliefs like that would add malicious code to his project, and I'm personally not willing to run that risk.
Please note that I am not encouraging people to "go harass the dev", that is an immoral action nobody should be doing. I am trying to inform people of the developers behavior online, past and current, so they can make a decision for themselves whether to run his software on their personal devices.
Honestly, a lot of lead devs in fantastic FOSS software have pretty limited patience. I've read plenty of that guy's discourse, and while I think he could be more diplomatic, I don't see any reason to suspect he's doing anything malicious with the project.
I'm personally totally fine using GrapheneOS. If you aren't, there are plenty of alternatives.
"Limited patience" is understandable, but the behavior of the GrapheneOS dev is completely different. I've personally interacted with them not too long ago, and nothing has changed since the public accusations from a year ago.
That's fair. I personally don't interact with him, nor do I plan to (why would I?), so it really doesn't bother me. As long as the other devs can manage dealing with him and the quality of the code stays high, I'm happy. If the other devs leave the project, I'll look for forks.
~~He isn't on the project since last year.~~ androguru Edit: Sorry, meant "he isn't the project lead since last year". He is still part of the GitHub team and actively developing.
You can still be part of a project without being lead, to be part of the "we." Did he contribute and/or is he part of GrapheneOS, yes? So he's part of the "we."
Or does only the lead developer get the "we?" Wouldn't that make it more of an "I" instead?
load more comments
(2 replies)
It states that he is the "Founder of @GrapheneOS", not the current lead developer. So I don't get your point
His activity on GrapheneOS repositories, issues, etc. indicates he's still very active in development and in the community.
IMO he can contribute all he wants. His PRs will still have to go through someone else (i.e. the new maintainer / lead dev). I don't care if he adds new code. That's much appreciated.
Toxicity is more of an issue if you're the maintainer since you have control over the project.
I know Daniel somewhat from some years back, and calling him extremely toxic is just wrong. He is and has always been rather bad at communication under stress and is clearly on the spectrum in some way. Technically a genius person, but perhaps doesn't have the right set of qualities to lead things, except from a strictly technical pov.
Very good decision from him to withdraw from social media. I hope he manages to contribute in the future.
is clearly on the spectrum in some way
This is not an excuse to behave the way he does.
Very good decision from him to withdraw from social media
He hasn't, still on github, still on HN.
So? Bad people can make good things. We should all stop using Linux because Torvalds is a dick?
as long as they do good work i don't give a shit what they think
might be toxic, but the os is brilliant
load more comments
(3 replies)
view more: next ›