PinePhone review after a month of daily driving

Original Article ↗ Hacker News Discussion ↗

An in-depth review of the PinePhone as a daily driver sparks broader debate over the viability of “pure Linux” phones as real phones rather than hobbyist devices. Commenters praise its openness, hackability, SSH access, and low cost, but report chronic problems with call reliability, notifications, performance, battery life, and immature software stacks compared with even decade‑old Android or feature phones. The thread situates PinePhone, Librem 5, and similar efforts within the larger challenge of building ethical, open, and well-supported mobile hardware in an ecosystem dominated by tightly integrated, proprietary SoCs and subsidized mainstream smartphones.

PinePhone as Linux Device vs. Phone

  • Many see PinePhone as a great mobile Linux box (SSH access, full distro, scripting, hotspot, GPS, carputer, ticket/QR display), but a poor phone.
  • Core complaint: unreliable calls/SMS (missed or failed calls, modem quirks). Some report random crashes or freezes.
  • Several emphasize that PinePhone is explicitly marketed as a developer/hacker device, not a consumer-ready daily driver.

Performance, UX, and Software Maturity

  • Users describe laggy lock screens, input drops, flaky notifications, and weak battery life, especially on the original PinePhone.
  • PinePhone Pro fixes a lot of lag but runs hot and drains faster.
  • Experiences vary strongly by OS:
    • PostmarketOS with SXMO is often cited as the only truly “snappy” option.
    • Phosh gets mixed reports: sluggish on PinePhone for some, but snappy on other hardware.
    • Plasma Mobile and some default images are described as notably slow/unstable.
  • Text input, keyboard behavior, and touch editing are recurring pain points across Linux mobile UIs.

Storage and SD Card Booting

  • Booting different OSes from SD cards is praised for simplicity, experimentation, and easy backups.
  • Others warn commodity SD cards have poor write endurance; recommend “endurance” or industrial cards, or eMMC/SSD where possible.
  • Some report SD corruption and failures on heavy-use systems; others report years of trouble-free use.

Alternatives and Comparisons

  • Multiple users end up preferring:
    • De-Googled or custom-ROM Android phones (LineageOS, Ubuntu Touch, Droidian, postmarketOS on mainstream handsets).
    • Librem 5, which some claim is workable as a daily driver, though expensive and with its own issues.
    • Feature phones for reliable calls, paired with PinePhone as a data device.
    • PDAs/tablets or e-ink Android devices for “phone without modem” use.

Openness, Hardware, and Modems

  • Strong desire for open, privacy-respecting phones clashes with:
    • Closed cellular modems and wireless chipsets.
    • High development and certification costs, tiny volumes, and SoC vendor NDAs.
  • Some argue expecting cheap, fully open, polished phones is unrealistic under current industry and regulatory constraints.
  • There is ongoing low-level work (e.g., alternative modem firmware, ModemManager GPS fixes), but legal and technical limits prevent fully open basebands.

Use Cases, Expectations, and Philosophy

  • Split between people who:
    • Rarely use voice calls and are fine with a “pocket Linux computer that sometimes phones.”
    • Consider reliable telephony, emergency calls, and mainstream apps mandatory.
  • Some criticize “Linux on phone” culture as fragmented and NIH; others counter that diversity and experimentation are inevitable in a volunteer-driven ecosystem.