LineageOS 22

Original Article ↗ Hacker News Discussion ↗

Device longevity & hardware choices

  • Many users report multi-year use of phones/tablets thanks to LineageOS (e.g., Xperia Z1/Z1 Compact, Moto X4, OnePlus, older Samsung tablets).
  • Some still buy hardware primarily on likelihood of LineageOS support; Pixels, certain Motorolas, older OnePlus, some Samsung A-series and Xperia devices are mentioned.
  • Xiaomi is widely criticized: complicated, rate-limited Windows-only bootloader unlock, long waiting periods, heavy bloat/adware; several advise avoiding the brand.
  • Samsung gets mixed reviews: great screens and hardware, but custom bootloader and North American restrictions make unlocking/flashing harder or risky.
  • Fire tablets are attractive for price but often unrootable on newer models, leaving them sluggish and “virtually unusable” on stock OS.

Security, updates & binary blobs

  • Users debate risks of using outdated stock Android on tablets: webview/browser exploits, ad-based drive‑by attacks, and botnet enrollment are cited.
  • LineageOS is seen as extending device life with newer Android and security patches, but:
    • Hardware is often tied to a specific kernel via proprietary drivers/firmware.
    • Lack of mainlined drivers and NDA-encumbered userspace blobs limit how far old devices can be carried forward.
  • Some blame this on Linux’s unstable driver ABI; others argue it’s primarily OEM business choices, not kernel policy.

Installation experience

  • Overall process is described as stable over the years; A/B devices add a few fastboot and sideload steps.
  • Samsung flashing often requires Odin on Windows; Heimdall on Linux/macOS exists but is unreliable for some.
  • LineageOS 22 builds roll out over days/weeks; users track pending builds via the project’s CI.

Apps, banking & attestation

  • Messaging: WhatsApp and Signal generally work fine; WhatsApp can warn about an “unsupported ROM” but still runs, even without Google services (via direct APK).
  • Banking and payment apps:
    • Situation varies by country and bank. Some work even on rooted devices; others refuse to run on any custom ROM or rooted phone.
    • Many use Google SafetyNet/Play Integrity attestation; apps may block LineageOS entirely despite browsers still being accepted for the same services.
    • Workarounds include Magisk and similar tools, but LineageOS as a project explicitly refuses to bake in any bypass, citing risk of Google retaliation.
    • Some users keep a second “stock” device (Pixel/iPhone/iPad) solely for banking or mandatory apps; others rely on web interfaces where possible.
  • There is concern that growing reliance on hardware attestation will make custom ROMs increasingly impractical, with calls for regulatory or consumer‑rights action.

Backups, launchers & tools

  • SeedVault is mentioned but limited by app opt‑out.
  • Swift Backup (with root) + Syncthing to a home server is recommended as a modern Titanium Backup replacement.
  • Many dislike the /e/OS/Bliss launcher, preferring alternatives such as Lawnchair (available via third‑party F-Droid repos).
  • Prebuilt LineageOS system apps (e.g., Twelve) are obtainable from community mirrors.

Android development model & project health

  • Android 15’s trunk-based development and frequent QPRs are said by LineageOS to increase rebase workload and cause some older devices to be dropped mid‑cycle.
  • Others note that incremental QPRs can also make rebasing smoother compared to one huge annual drop, particularly for projects with fewer deep changes.
  • Enthusiasm among users remains high, but some worry about long‑term sustainability and the compounded pressure from OEM blobs, Google churn, and attestation.