Yep same here. Also they’re not capable of installing grapheneos which is kind of a deal breaker for me.
Isn’t that up to the GrapheneOS devs?
The GrapheneOS team makes their hardware security requirments very clear.
Its up to the hardware manufactures to include a few additional components used for securely storing keys, so far Google Pixles are the only consistent line of products that do so.
So… they chose to make a very Pixel-specific OS and you’re mad at Fairphone?
It’s not about being pixel specific. They built high security OS that uses HW components to deliver that high security. It can’t be delivered without them. These components are not google patented nor does GrapheneOS demands they use the exact pixel ones. GrapheneOS just refuses to lower security to support phones that lack these components, because manufacturers wanted to save maybe a $1 per phone by not including them at the expense of user security.
I think I had this all wrong. Fairphone isn’t / doesn’t want to be an enthusiast DIY brand at all (like framework for laptops) but a mainstream brand that’s eco-friendlier* and non-exploitative.
So of course they will not care much about niche features like other ROMs or audio jacks. The privacy focused, tech-savvy or feature focused buyers are not their target.
*IC and PCB related footprint is still roughly 80% of the FP4 and FP has little to no control on those processes, according to an independent study.
