have fairphone looked into supporting GrapheneOS? what exactly is missing there other than "it's not Pixel"?
[flagged]
Fairphone 6 wide camera experimental Linux support
11–20 of 90 posts
Re: Fairphone 6 wide camera experimental Linux support
#12Earlier quoted context omitted.
[flagged]
Fairphone hasn't talked about GrapheneOS at all, instead opting to be in bed with Murena and /e/os, so I doubt they've even bothered to read the list of hardware requirements. They didn't bother with the Fairphone 6, which was released barely a year ago.
[flagged]
Re: Fairphone 6 wide camera experimental Linux support
#13Earlier quoted context omitted.
Fairphone hasn't talked about GrapheneOS at all, instead opting to be in bed with Murena and /e/os, so I doubt they've even bothered to read the list of hardware requirements. They didn't bother with the Fairphone 6, which was released barely a year ago.
[flagged]
>GrapheneOS smearing Fairphone as not secure in 3..2..1..
GrapheneOS would love to support more devices, that "smearing" is explaining that a company doesn't make secure devices, which is completely correct criticism.
Fairphone for various reasons is not able to or willing to achieve the hardware requirements. It's not easy to create some of the worlds most secure devices.
Re: Fairphone 6 wide camera experimental Linux support
#14have fairphone looked into supporting GrapheneOS? what exactly is missing there other than "it's not Pixel"?
It would take extensive work to achieve the hardware requirements and the capability for an OEM that isn't able to develop their own chips with Memory tagging enforcement (mte) which the Snapdragon 8 Elite used in the upcoming Motorola phones will have. It won't be cheap and it won't be easy.
Google has set the bar high with their security features.
Re: Fairphone 6 wide camera experimental Linux support
#15Does the article seem AI-written/assisted to anyone else? Some parts that stood out to me: > A phone camera is not a single device. On Qualcomm SoCs, the capture path is a chain: > The bus register base moved from 0xa00 to 0x1800, and encapsulating that offset shift accounted for most of the work. > It gated the AHB register bus used by the whole camera complex, including the CCI. Without it, register accesses silent…
It is almost certainly AI-written. Very odd writing style, also the repo README is Claude-generated.
Re: Fairphone 6 wide camera experimental Linux support
#16Does the article seem AI-written/assisted to anyone else? Some parts that stood out to me: > A phone camera is not a single device. On Qualcomm SoCs, the capture path is a chain: > The bus register base moved from 0xa00 to 0x1800, and encapsulating that offset shift accounted for most of the work. > It gated the AHB register bus used by the whole camera complex, including the CCI. Without it, register accesses silent…
Before AI slop, I rarely saw humans make so many words bold and explicitly mention all affected filenames. On the latter point, humans try to convey the main ideas, while LLMs tend to enumerate the files they changed.
Since this post has a lot of terms in bold and enumerates filenames, yes, it seems at least ai-assisted.
Re: Fairphone 6 wide camera experimental Linux support
#17have fairphone looked into supporting GrapheneOS? what exactly is missing there other than "it's not Pixel"?
[flagged]
I don't have anything to do with GrapheneOS (only using it on a phone), but the security of Fairphone is not great, like many other Android phones it does not have a separate secure enclave to store secrets, but instead relies on a TrustZone-based TEE, which is often vulnerable to side-channel attacks (e.g. see the recent attack where a lot of MediaTek phones could be decrypted in seconds, even in BFU). Note: iPhone has had a secure enclave since iPhone 5s (2013), Pixel since 3 (Titan M, 2018), and Samsung flagships since S21 (I think? Knox Vault, 2021).
They also do firmware updates very irregularly even though Qualcomm does monthly bulletins and Fairphone's firmware is known to be full of CVEs. They also have a bad history of updating Linux kernels, e.g. Fairphone 4 is on an ancient Linux kernel. Fairphones also miss modern security mitigation techniques like MTE.
To be fair, this applies to many Android phones outside Google Pixel and Samsung flagships.
Aside from that, repairability is nice, but the most common early failures on the Fairphone 6 seem to be broken volume buttons, for which Fairphone does not offer a replacement and an issue where the logic board dies during charging, which is also not user-replaceable.
---
Ps. perhaps you could use substantive arguments the next time? E.g. which points of the GrapheneOS lists of requirements do you think are irrelevant and why are they irrelevant?
Re: Fairphone 6 wide camera experimental Linux support
#18Earlier quoted context omitted.
Fairphone hasn't talked about GrapheneOS at all, instead opting to be in bed with Murena and /e/os, so I doubt they've even bothered to read the list of hardware requirements. They didn't bother with the Fairphone 6, which was released barely a year ago.
[flagged]
Fairphone 6 does not fulfill the hardware requirements (secure enclave, MTE, etc.), nor software requirements (monthly firmware updates, etc.). So there is nothing that GrapheneOS can do at this point. The ball is in Fairphone's court if they want this, but Fairphone seems more interested to cooperate with /e/OS, whose CEO proclaims security hardening is for pedophiles and spies (thereby fueling the narratives that support chat control and such nonsense).
One of the underlying reasons is probably that the Fairphone hardware and software is developed/maintained by a Chinese ODM (T2Mobile), so the question is if Fairphone even has the know-how to make such a phone. Heck, they have failed to fix bugs that have been plaguing people for months (e.g. regular dropping of all connections when using IPv6 on certain routers).
Motorola is going to make devices that fulfill the requirements and GrapheneOS is cooperating with them.
Re: Fairphone 6 wide camera experimental Linux support
#19have fairphone looked into supporting GrapheneOS? what exactly is missing there other than "it's not Pixel"?
[flagged]
Different priorities. GrapheneOS prioritizes very strong security (inside a very specific model that includes treating the user as an attack vector to be protected against). Fairphone prioritizes repairable hardware (and actually makes their own hardware). On a finite budget (of both money and time and people), prioritizing either one of these will undermine the other.