For more than a decade, LineageOS has served as the beating heart of the custom Android ROM community — a volunteer-driven project that takes Google’s open-source Android code and reshapes it into a privacy-focused, bloatware-free alternative for dozens of smartphone models. Now, with the release of LineageOS 22.1 based on Android 15, the project is delivering one of its most ambitious updates yet. But buried within the celebratory changelog is a sobering message: the team is smaller than ever, device support is narrowing, and the long-term viability of the project is no longer guaranteed.
The announcement, published on the official LineageOS blog, details the jump from LineageOS 21 (based on Android 14) to LineageOS 22.1 (based on Android 15 QPR2). The team notably skipped the 22.0 designation entirely, opting to launch directly on the quarterly platform release that Google shipped in early 2025. This decision reflects a pragmatic approach: rather than building on an initial Android 15 base and then scrambling to rebase when Google’s quarterly patches introduced breaking changes, the LineageOS developers waited for a more stable foundation before pushing builds to users.
A Feature-Rich Release Built on Android 15 QPR2
LineageOS 22.1 is not merely a rebasing exercise. The project has introduced a substantial set of new features and refinements that go well beyond what stock Android 15 offers. Among the most notable additions is a redesigned volume panel that now supports streaming-device volume control, allowing users to adjust the volume on Chromecast and other cast-enabled devices directly from the system volume dialog. The SeedVault backup application, a privacy-oriented alternative to Google’s cloud backup, has been updated to version 15 with significant architectural improvements. The weather service integration has been overhauled with a new default provider, and the Glimpse gallery app now ships as the default photo viewer, replacing the aging Aperture gallery component for browsing duties while Aperture retains its role as the system camera.
Under the hood, the team has made meaningful changes to how the system handles itself. The Updater app now has the ability to automatically migrate users from LineageOS 21 to 22.1 via a standard over-the-air update, a feature that dramatically lowers the barrier for less technical users who might otherwise need to manually flash a new ROM. There are also new charging controls — including a user-configurable charging limit — baked into the system, a feature that many OEMs still fail to offer. The icon pack system, known as Flavors, has been expanded with new options, and the setup wizard now includes a more polished interface for configuring default applications during initial device configuration.
The Creeping Crisis of Device Support
Yet for all the technical polish, the most consequential paragraphs in the LineageOS 22.1 announcement have nothing to do with features. The project’s maintainers are sounding an alarm about sustainability. As stated directly in the project’s changelog post, the number of active maintainers has been declining steadily. Device support — always the lifeblood of a custom ROM project — is contracting as a result. LineageOS 22.1 launches with builds for a smaller roster of devices than its predecessor, and the team has acknowledged that some previously supported hardware may not receive 22.1 builds at all unless new volunteers step forward to maintain them.
This is not a new problem, but it is an accelerating one. The custom ROM ecosystem has been under pressure for years as Android devices have grown more complex. Modern smartphones ship with intricate hardware abstraction layers, proprietary firmware blobs for cellular modems, camera image signal processors, and neural processing units that are extraordinarily difficult to support without vendor cooperation. Google’s own efforts to modularize Android through Project Treble and later Project Mainline have helped to some degree, but they have not eliminated the fundamental challenge: every new device requires dedicated, ongoing maintenance from a knowledgeable volunteer who owns the hardware and is willing to invest dozens of hours per month in unpaid labor.
Why Volunteers Are Burning Out
The maintainer shortage is symptomatic of broader dynamics within the open-source mobile community. In the early days of CyanogenMod — LineageOS’s predecessor — custom ROMs offered capabilities that stock Android simply lacked: theming engines, granular permission controls, performance tuning, and extended device lifespans well beyond what manufacturers provided. Today, stock Android has absorbed many of those features. Google’s Pixel devices receive seven years of updates. Samsung and OnePlus have extended their support windows to four or more years. The urgency that once drove users to custom ROMs has diminished, and with it, the pipeline of enthusiastic new contributors.
The project’s leadership has been transparent about the stakes. The changelog post explicitly invites new contributors — not just device maintainers, but developers who can work on the core platform, designers, technical writers, and infrastructure engineers. The message is clear: LineageOS is not in immediate danger of disappearing, but its trajectory is unsustainable without fresh blood. The team has also pointed users toward its wiki and contributor documentation, attempting to lower the onboarding barrier for prospective volunteers.
Privacy and Degoogling Remain Core Selling Points
Despite the existential pressures, LineageOS continues to occupy a unique and important niche. For users who want to run Android without Google Mobile Services — a practice commonly known as “degoogling” — LineageOS remains one of the most accessible and well-documented options available. The project does not ship with any Google applications or services by default, giving users a clean slate to decide exactly what software runs on their devices. This is a meaningful differentiator in an era of increasing concern over data collection, targeted advertising, and the concentration of personal information within a handful of technology conglomerates.
The inclusion of SeedVault as the default backup solution underscores this philosophy. Unlike Google’s backup service, which stores data on Google’s servers, SeedVault allows users to back up their device data to storage they control — a USB drive, a self-hosted Nextcloud instance, or any WebDAV-compatible server. The update to SeedVault 15 in LineageOS 22.1 brings improved reliability and broader app-data compatibility, making the degoogled experience more practical for daily use. For journalists, activists, security researchers, and privacy-conscious professionals, these are not abstract benefits — they are operational requirements.
The Technical Underpinnings of the Android 15 Rebase
From a purely technical standpoint, the rebase onto Android 15 QPR2 gives LineageOS users access to the full suite of platform improvements Google introduced in its latest major release. These include enhanced notification management, improved passkey support, more granular privacy controls for camera and microphone access, and refinements to the predictive back gesture system. LineageOS layers its own customizations on top of these, including its long-standing Privacy Guard feature, expanded quick-settings tile options, and system-level call recording where legally permitted — a feature Google has progressively restricted in stock Android.
The project has also continued to refine its build infrastructure. LineageOS maintains an impressive automated build system that compiles and signs official builds for every supported device on a regular cadence. The infrastructure required to do this — build servers, signing keys, download mirrors, and an over-the-air update delivery system — represents a significant operational commitment. The team runs this entirely on donated resources and volunteer labor, a fact that makes the project’s longevity all the more remarkable and its sustainability challenges all the more pressing.
What Comes Next for the Custom ROM Movement
LineageOS is not the only player in the custom ROM space, but it is by far the largest and most influential. Projects like GrapheneOS focus exclusively on Pixel devices with a hardened security model, while /e/OS (now Murena) targets a consumer-friendly degoogled experience. CalyxOS occupies a middle ground with verified boot and a curated app ecosystem. But none of these projects match LineageOS’s breadth of device support or its role as an upstream source for other custom ROMs. Many smaller projects base their work directly on LineageOS’s code, meaning that the health of LineageOS has cascading effects across the entire custom Android ecosystem.
The release of LineageOS 22.1 is, on its surface, a triumph — a testament to what a dedicated group of volunteers can accomplish without corporate backing or commercial incentives. The feature set is robust, the Android 15 rebase is thorough, and the user experience continues to improve. But the project’s own words betray an undercurrent of anxiety. The team knows that software projects do not die from a single catastrophic event; they die slowly, as maintainers drift away and the gap between what needs to be done and who is available to do it grows wider with each release cycle. For the millions of users who depend on LineageOS to keep aging devices alive, to protect their privacy, or simply to run Android on their own terms, the message in this changelog is as much a call to action as it is a celebration.
WebProNews is an iEntry Publication