HN Debrief

Fairphone 6 and PostmarketOS working main camera

  • Open Source
  • Hardware
  • Mobile
  • Developer Tools

The post is a hands-on writeup about bringing the Fairphone 6 main camera up on postmarketOS, which is a Linux distribution for phones that aims to replace the usual Android stack with a more standard Linux system. The interesting part is not just that photos can now be taken. It is how much hardware enablement still depends on reverse engineering, kernel work, and vendor-specific quirks, right down to camera autofocus and emergency calling certification. That made the story feel less like a product announcement and more like a field report from the front line of making modern phones work on mainline Linux.

If you care about open mobile platforms, the signal here is not "Linux phones are solved" but that mainlining work on newer consumer hardware is finally moving from demos toward usable pieces. For teams betting on repairable or long-lived devices, software openness and upstream driver work now look like the real constraint, not just hardware design.

Discussion mood

Cautiously excited. People admired the technical achievement and liked the idea of a repairable phone running real Linux, but the dominant mood was realism about how incomplete the stack still is and frustration that Fairphone hardware and software quality do not yet justify the premium for many buyers.

Key insights

  1. 01

    Main camera progress is not full usability

    Getting the camera working marks real progress, but it does not erase the gap between a successful hardware bring-up and a phone you can actually rely on. The key added context was that audio and microphone support were still absent from the public compatibility page when people checked, and only later clarified as work in flight being upstreamed. That changes the interpretation of the post. It is a milestone in a live port, not evidence that postmarketOS on the Fairphone 6 is ready for normal users.

    Treat component bring-up posts as pipeline signals, not product-readiness signals. If you are evaluating Linux phones for deployment or personal use, track the device support matrix and upstream status rather than assuming one high-profile feature means the basics are done.

      Attribution:
    • 1dom #1 #2
    • pizzaiolo #1
  2. 02

    Android compatibility is still the trap

    Alternative mobile Linux systems are not mainly blocked by missing apps. They are blocked by how phone hardware support is packaged. Older ports often needed a shadow Android userspace and init system just to talk to vendor drivers, and those binaries were tied to the original kernel and Android release. That locked ports to stale kernels and made every bug fix expensive. Generic Kernel Image and more upstream-friendly Android kernel work help, especially on Pixels, but they only reduce the damage. They do not remove the dependency on vendor cooperation and clean upstream drivers.

    If you want long-lived devices with replaceable operating systems, prioritize platforms with active upstream driver work over raw specs. The strategic asset is not the handset. It is whether its hardware support can survive beyond the vendor Android image.

      Attribution:
    • saidinesh5 #1
    • chaosharmonic #1
  3. 03

    Fairphone value depends on your objective

    Fairphone stops looking overpriced only if you count the things mainstream phone comparisons usually ignore. Repairability, easier part replacement, and supply-chain goals are part of what buyers are paying for. That does not excuse buggy software or rough edges, and owners said those issues are real. The useful framing is that Fairphone is not competing on conventional price-to-performance at all. It is selling ethics and maintainability first, then trying to get close enough on everyday usability.

    Do not compare Fairphone to Google or Apple on benchmark terms alone. If you are choosing devices for a mission-driven team or longevity program, decide upfront whether repairability and sourcing goals are requirements or just nice-to-haves, because that answer changes the economics completely.

      Attribution:
    • boudin #1
    • NoboruWataya #1
    • Telaneo #1
  4. 04

    Phone hardware is no longer the limiting factor

    Several commenters pushed back on the idea that a full Linux phone would only be a novelty because the hardware is too weak. They pointed to modern phones with 6 to 12 gigabytes of RAM, real-world compiling on devices with as little as 3 gigabytes, and demos of NixOS on Fairphone hardware that felt as responsive as low-end Android. That reframes the opportunity. The blocker is not whether phones can run desktop-class workloads at all. It is whether the software stack can expose the hardware cleanly enough to make those workloads dependable.

    If you are exploring phone-as-computer ideas, stop assuming compute is the first failure mode. Focus on driver support, memory pressure in specific toolchains like Rust, and peripheral reliability such as radios, audio, GPS, and cameras.

      Attribution:
    • fsflover #1
    • dminik #1
    • seba_dos1 #1
    • solarkraft #1

Against the grain

  1. 01

    Volunteer bring-up is the wrong model

    The sharpest dissent was that celebrating volunteers reimplementing basic phone support years after release normalizes a broken ecosystem. That view holds that serious mobile operating systems need direct OEM or ODM relationships, not heroic reverse engineering, and points to projects built closer to the Android vendor model as more likely to deliver a polished experience. It is a useful correction because it shifts the goal from technical possibility to institutional leverage.

    If your objective is a reliable open mobile product rather than a research platform, ask first who controls the vendor relationship and test pipeline. Community passion can get hardware booting, but it rarely substitutes for supply-chain access and funded integration work.

      Attribution:
    • zb3 #1 #2
  2. 02

    Desktop Linux on phones may stay niche

    Not everyone bought the bigger vision. One commenter who had tried desktop Linux on phones before said the result felt more like an interesting cybersecurity gadget than a better phone. That skepticism matters because it attacks the implicit premise that openness alone creates broad user value. Many of the imagined uses still need a reason stronger than novelty.

    Pressure-test Linux phone ideas against boring daily tasks, not just what becomes possible in theory. If a use case does not beat Android or iPhone on reliability, convenience, or control for a real user, it will stay a hobbyist feature.

      Attribution:
    • spaqin #1

In plain english

Android userspace ↩
The collection of system services and software layers above the kernel that Android devices rely on to make hardware and apps work.
Generic Kernel Image ↩
An Android project that tries to standardize the core kernel across devices so vendors can add hardware support through separate modules instead of shipping fully custom kernels.
mainline Linux ↩
The official upstream Linux kernel project, as opposed to a vendor-specific or heavily modified fork.
NixOS ↩
A Linux distribution that uses declarative system configuration, making setups reproducible and easier to roll back.
ODM ↩
Original Design Manufacturer, a company that designs and builds products that other brands sell under their own names.
OEM ↩
Original Equipment Manufacturer, the company that builds or brands a device and sells it with software preinstalled.
postmarketOS ↩
A Linux distribution for phones and other mobile devices that aims to keep hardware usable for a long time.
upstreamed ↩
Submitted and accepted into the main official version of a software project, such as the Linux kernel, so the code no longer lives only in a custom fork.

Reference links

Device support and project status

Fairphone product experience

Android kernel and upstreaming references

Use cases and prior discussions

  • What We Don't Have
    A commenter linked this essay to illustrate how more open phones could change humanitarian and community infrastructure use cases.
  • Hacker News item 49201496
    Referenced as another example related to using phones more like general-purpose computers.
  • Hacker News item 43243075
    Linked in a side discussion disputing whether Apple is improving its software direction.
  • Hacker News item 46322556
    Also linked in the Apple side discussion as evidence against optimism about recent iOS direction.