←back to thread

The Fairphone (Gen. 6)

(shop.fairphone.com)
155 points DavideNL | 7 comments | | HN request time: 0.936s | source | bottom
Show context
pickledoyster ◴[] No.44375563[source]
available with /e/OS too https://shop.fairphone.com/the-fairphone-gen-6-e-operating-s...

As I near the eol of my daily driver, I'm considering a Fairphone, but what it's missing is a folding card holder, like the Satechi wallet stand for iPhone. Putting the phone in horizontal mode on a table and using a bt keyboard is how I do a lot of my writing

replies(4): >>44375611 #>>44375865 #>>44375950 #>>44377060 #
IlikeKitties ◴[] No.44375865[source]
This question always comes up:

The Reason GrapheneOS isn't made for Fairphones Officially is that Fairphones lack a lot of base requirements for official support:

https://grapheneos.org/faq#future-devices

There's nothing preventing anyone from making a 3rd Party port of GrapheneOS to Fairphones, it just seems no one does.

replies(1): >>44376366 #
1. jeroenhd ◴[] No.44376366[source]
Which features specifically do Fairphones miss? It seems to me like most of those requirements are all part of the (mostly open-source) software stack. The Fairphone uses a standard Qualcomm chip that should work as well or as badly as a Pixel SoC.

The "Complete monthly Android Security Bulletin patches without any regular delays longer than a week for device support code (firmware, drivers and HALs)" part isn't even true for Pixels.

replies(2): >>44376443 #>>44376464 #
2. IlikeKitties ◴[] No.44376443[source]
> The Fairphone uses a standard Qualcomm chip that should work as well or as badly as a Pixel SoC.

I suspect it's the features of the titan m2 security chip. It's a pretty cool piece engineering [0].

[0] https://www.androidauthority.com/titan-m2-google-3261547/

replies(1): >>44377696 #
3. gruez ◴[] No.44376464[source]
>The "Complete monthly Android Security Bulletin patches without any regular delays longer than a week for device support code (firmware, drivers and HALs)" part isn't even true for Pixels.

Doesn't the ASB get published at the same time as pixel updates? So by definition it's up to date.

replies(1): >>44377671 #
4. jeroenhd ◴[] No.44377671[source]
Yes, but vulnerabilities don't always get backported to older (supported) devices immediately. I distinctly recall one case where an Android CVE was patched months later on one Pixel model compared to the others that were in support. However, because search engines have all become terrible in the age of AI, I can only find vague references.

I did, for instance, find a case where Google Project Zero published a blog post on a vulnerability while their Pixel 6 was still four days away from the first updates: https://9to5google.com/2023/03/20/pixel-6-march-2023-update/

I myself regularly find my Pixel only noticing updates half a month later unless I manually check while my Samsung tablet notifies me immediately once my quarterly update is available. It's quite annoying to have to check for updates manually every week, but I suppose updates are technically available.

5. jeroenhd ◴[] No.44377696[source]
The tech is impressive, but not exactly Google exclusive. If the ROM developers intend to only support devices with Pixel exclusive features like the Titan chips, they might as well say they're not interested in supporting non-Google phones.
replies(2): >>44379054 #>>44390755 #
6. IlikeKitties ◴[] No.44379054{3}[source]
This is a misunderstanding. It's just that Google Pixel are the only devices that have this level of hardware security engineering AND are open to thirdparty roms like grapheneos to a decent degree.

Samsung Flagships and Iphones seem to have similar level of security engineering in them (Pixels use Samsung CPUs essentially) but aren't open to the required degree for third party roms.

There's nothing else on the Market that delivers on that Level. The GrapheneOS guys are working with someone one a potential custom phone to get the required level of hardware security but nothing has materialized. Companies like Fairphone are free to deliver hardware that is competitive in the security space and i'm sure that the grapheneos team will consider them then. But until anyone else does i'll keep buying whatever phone grapheneos wants me to buy, i don't care.

7. mendelmaleh ◴[] No.44390755{3}[source]
here's a pretty good thread about compatibility:

https://grapheneos.social/@GrapheneOS/114721666000552094