6 ms·
Simple. Fairphone doesn't want GOS. Forking GOS and porting it to a new device is a huge and unreasonable ask for an individual user. Even less so when you inc
by Telaneo 5d ago
Simple. Fairphone doesn't want GOS.
Forking GOS and porting it to a new device is a huge and unreasonable ask for an individual user. Even less so when you include the fact that you'll need to keep it up to date.
- fc417fc802 5d agoI understand that bringing AOSP to an unsupported device is a huge endeavor. But fairphone already has the driver situation sorted out. What's the complexity here? (Genuine question, I'd like to correct any misconceptions about the android ecosystem that I have.)
- josephg 5d agoWhy? Because of drivers? Don’t they already have Linux drivers for the fairphone? I wonder if fable or astra could wire everything up.
- imkac 5d agoAs a company that often lies, they won’t spend a single penny on this.
- fsflover 4d agoUnsubstantiated accusations are against the HN guidelines.
- microtonal 5d agoLLMs do not solve every problem. You are dependent on Qualcomm for hardware firmware updates and apparently they charge quite a bit extra if you want continuous monthly security updates [1]. This is possibly one of the reasons that smaller OEMs like Fairphone do not update firmware regularly and instead choose to keep their customers vulnerable to many known CVEs. [1] https://news.ycombinator.com/item?id=48079791 https://news.ycombinator.com/item?id=48079791
- fc417fc802 5d agoThey're getting remarkably good at reverse engineering. I wonder if the relevant firmware updates can be provided by the user or OEM or if they're blobs that have to be signed by qualcomm?
- grapheneos 5d agohttps://news.ycombinator.com/item?id=49669636 https://news.ycombinator.com/item?id=49669636