HN Debrief

LineageOS Statistics

  • Open Source
  • Mobile
  • Privacy
  • Security
  • Hardware

LineageOS posted a public stats dashboard showing roughly a million opt-in installs by device, country, version, and official versus unofficial build status. The headline numbers startled people. About three quarters of installs appear to be unofficial builds, Waydroid images for running Android apps on Linux desktops are among the largest buckets, and only a minority of installs are on releases still getting security updates. That makes the dashboard less a map of mainstream phone usage and more a snapshot of a fragmented ecosystem held together by ports, forks, and repurposed old hardware.

If you care about Android openness, the bottleneck is no longer just building a good ROM. Device unlock policies, proprietary blobs, and Google-controlled app compatibility now decide whether an alternative OS is viable for normal users.

Discussion mood

Mostly gloomy and nostalgic. People still admire LineageOS for reviving abandoned hardware, but they read these stats as proof that custom Android has been squeezed into a niche by locked bootloaders, proprietary dependencies, app attestation, and the loss of official support for many phones.

Key insights

  1. 01

    Daily-driver reliability now beats freedom

    For many former ROM enthusiasts, the decisive change is not ideology but dependence. Phones now carry banking, payments, work apps, and identity functions, so a setup that occasionally breaks after an update is no longer acceptable. That reframes custom ROM decline as a reliability problem first and a hobby decline second.

    If you want adoption beyond enthusiasts, alternative mobile OS projects need a boringly reliable path for payments, banking, and updates. Without that, they stay on spare devices and old hardware no matter how good the core OS is.

      Attribution:
    • ekr #1
    • pta2002 #1
    • aarmenaa #1
  2. 02

    Bootloader access is the hard choke point

    The most immovable blocker is hardware vendors locking devices down before the ROM community even gets started. Several people pointed to Huawei, BBK brands, Xiaomi, and Samsung procedures that are hostile enough to stop both users and maintainers. If unlocks are blocked and kernel sources or blobs are missing, no amount of community enthusiasm produces support.

    When evaluating Android hardware strategy, treat unlockability and source availability as supply-side prerequisites. A device ecosystem without them will not sustain third-party software, no matter how large the user interest seems.

      Attribution:
    • aguyongithub #1
    • rk06 #1
    • reorder9695 #1
  3. 03

    GrapheneOS has absorbed the serious niche

    A notable part of the old LineageOS audience appears to have consolidated around GrapheneOS rather than disappearing outright. The appeal is not feature breadth. It is narrow device support, stronger security defaults, and less trust in random unofficial builds. That helps explain why LineageOS still has broad mindshare while its official install base looks thin.

    If you are building an alternative platform, a smaller support matrix with high trust can outperform broad but uneven compatibility. Users choosing a primary phone value assurance more than theoretical hardware reach.

      Attribution:
    • NoboruWataya #1
    • pavon #1
    • preisschild #1
  4. 04

    Unofficial ROM distribution looks untrustworthy

    Several comments treated the prevalence of unofficial builds as a security and process problem, not just a branding detail. The common complaint was downloading large binaries from XDA or Telegram posts by unknown maintainers, with weak release hygiene and scattered support channels. That erodes confidence even among people who still want de-Googled devices.

    If you ship software outside mainstream app stores or OEM channels, invest in verifiable distribution, clear release provenance, and a sane issue tracker. Trust collapses fast when install instructions feel like forum archaeology.

      Attribution:
    • empyrrhicist #1
    • fg137 #1
    • red-iron-pine #1
    • bentcorner #1
  5. 05

    LineageOS now functions as Android plumbing

    The big Waydroid numbers and examples like Echo Show, Nintendo Switch, and old tablets suggest LineageOS is increasingly valuable as a reusable Android base for odd hardware and containers. That is less glamorous than being the default phone ROM, but it is strategically important. The project behaves more like infrastructure for ports and forks than a single end-user distribution.

    Do not judge projects like this only by flagship-phone adoption. There is real platform value in being the stable base layer others reuse across containers, embedded devices, and abandoned consumer hardware.

      Attribution:
    • rickdeckard #1
    • notesinthefield #1
    • RajT88 #1
  6. 06

    microG support lag pushed users off official builds

    One concrete reason for unofficial-build share is historical friction around microG. A maintainer confirmed signature spoofing support was merged about two and a half years ago, but users said the earlier stance pushed them onto forks and that the change was poorly announced. Once people move to a fork that solves their practical problem, many never come back.

    Project governance decisions about adjacent tooling can have long half-lives. If you reverse a controversial policy, document it loudly and early or your install base will keep reflecting old grievances.

      Attribution:
    • genpfault #1
    • onli #1
    • timschumi #1
    • dahrkael #1

Against the grain

  1. 01

    The install base is definitely undercounted

    The dashboard only reflects users who opted into reporting, and privacy-minded ROM users are exactly the kind of people likely to disable telemetry. That means the absolute numbers are weak evidence for market size, especially when forks may report elsewhere or not at all. The trend signal is still useful, but the totals should not be treated as census data.

    Use these stats to understand composition, not precise share. If you need to estimate actual user count, adjust for opt-in bias and missing fork telemetry.

      Attribution:
    • jeroenhd #1
    • 28304283409234 #1
    • MYEUHD #1
  2. 02

    Odd device spikes are not necessarily fake

    Suspicious-looking concentrations like the Xiaomi Mi 8 or large unofficial-build counts may reflect real longevity and non-phone use cases rather than bots or click farms. The Mi 8 sold at huge volume and stayed useful for years, and unofficial builds are common on tablets, smart displays, and unsupported devices. Some weirdness in the dashboard is just what a long-lived modding ecosystem looks like.

    Be careful reading anomaly charts as fraud by default. In messy enthusiast ecosystems, skewed device distributions can come from a few durable models and creative repurposing, not manipulation.

      Attribution:
    • rickdeckard #1 #2
    • xbmcuser #1
    • dormento #1

In plain english

bootloader ↩
The low-level software that starts a device and decides what operating system can be installed and run.
GrapheneOS ↩
A security-focused Android-based operating system with a narrow support matrix, mainly targeting Google Pixel phones.
kernel sources ↩
The source code for the operating system kernel, which developers often need to build or adapt software for specific hardware.
LineageOS ↩
An open source Android-based operating system that people install on devices instead of the manufacturer’s original software.
microG ↩
A free software reimplementation of parts of Google Play Services, used to run apps that expect Google components without installing Google’s full package.
OEM ↩
Original Equipment Manufacturer, the company that makes and sells the phone or other hardware.
Play Integrity ↩
Google’s attestation system that lets apps check whether a device and its software environment meet Google-defined trust requirements.
signature spoofing ↩
A mechanism that lets trusted replacement software pretend to apps that it is signed by another software provider, often used to make microG work.
vendor blobs ↩
Closed source hardware-specific binaries from device makers that are needed for things like cameras, radios, or graphics to work.
Waydroid ↩
A tool that runs Android inside a container on Linux systems so desktop or mobile Linux devices can run Android apps.
XDA ↩
XDA Developers, a long-running online forum community focused on Android device modification and custom ROMs.

Reference links

LineageOS documentation and code

Waydroid and containerized Android

Alternative Android projects and user counts

Android device codename references

Modding community history

Market context