LineageOS is a free and open-source operating system based on the Android mobile platform, functioning as a custom firmware distribution for smartphones, tablets, and other devices.[1]Developed as the direct successor to the renowned CyanogenMod custom ROM, LineageOS emerged in December 2016 following the abrupt shutdown of Cyanogen Inc., the company behind CyanogenMod, which had shifted focus to a commercial version called Cyanogen OS.[2][3]This transition allowed the original open-source community to continue the project under a new name, emphasizing non-proprietary development without corporate interference.[2]Key Features and PhilosophyLineageOS prioritizes user control and privacy, offering extensive customization options such as theming, gesture controls, and built-in privacy guards to limit app permissions and data tracking.[1]Unlike stock Android distributions from manufacturers, it excludes proprietary Google applications by default, allowing users to install open-source alternatives or add Google Mobile Services separately if desired.[4]The project includes Unix command-line tools, developer utilities, and monthly security patches to extend device usability beyond official vendor support periods, often for several years.[1]Community and SupportMaintained by a global volunteer community of developers and contributors, LineageOS draws from the largest open-source Android effort, with builds rigorously tested for stability and performance.[1]As of November 2025, it officially supports over 100 devices from more than 20 manufacturers, including recent flagships like the Google Pixel 9a, OnePlus 13, and Samsung Galaxy A71, with ongoing additions through community ports.[5][6]The latest major release, LineageOS 23, is built on Android 16 and introduces enhancements like streamlined app suites and improved future-proofing for kernel compatibility across diverse hardware.[7][5]This community-driven approach has made LineageOS one of the most popular custom ROMs, downloaded millions of times and fostering ongoing innovation in mobile open-source software.[3]
History
Origins and Launch
LineageOS emerged as a direct response to the abrupt shutdown of CyanogenMod's infrastructure by Cyanogen Inc. in late 2016. Cyanogen Inc., which had formed in 2013 to commercialize aspects of the popular custom ROM while maintaining its open-source roots, faced mounting financial pressures and internal conflicts over its shift toward proprietary services and partnerships, including an exclusive licensing deal with ZUK Mobile for devices like the ZUK Z1. On December 24, 2016, the company announced it would cease operations and support for CyanogenMod by December 31, leaving millions of users without updates and prompting concerns among the developer community about the project's commercialization drift away from its non-profit origins.[8][9]In the wake of this decision, a group of former Cyanogen Inc. developers, led by co-founder Steve Kondik (known online as Cyanogen), quickly forked the CyanogenMod codebase to preserve its community-driven ethos. Kondik, who had departed Cyanogen Inc. earlier that month amid disagreements over the company's direction, rallied key contributors to establish LineageOS as a non-profit successor on December 24, 2016—the same day as the shutdown announcement. The project was positioned as a free, open-source Android distribution emphasizing user privacy, customization, and long-term device support without corporate interference, explicitly rejecting the ad-supported or service-tied models that had alienated parts of the original community.[10][11]LineageOS officially launched with its inaugural blog post on December 24, 2016, promising continuity with CyanogenMod's legacy while introducing stricter governance for sustainability. The first official builds, LineageOS 14.1 based on Android 7.1 Nougat, became available as nightly releases starting January 23, 2017, initially supporting a select group of devices including the Google Nexus 6P (angler), Nexus 5X (bullhead), Nextbit Robin (robin), Motorola Moto G4 (athene), Moto G4 Plus (osprey), and Xiaomi Mi 4c (libra). These early builds focused on stability and broad compatibility, drawing from CyanogenMod's extensive device tree to ensure a smooth transition for existing users.[11][12]Early adoption was rapid, reflecting the strong user base inherited from CyanogenMod. Within the first month of builds, LineageOS achieved over 500,000 active installations, surging past 1 million by mid-March 2017, with the OnePlus One emerging as the most popular device among early adopters. This growth underscored the demand for an independent, privacy-focused alternative in the custom ROM ecosystem.[13][14]
Key Events and Milestones
In April 2018, the LineageOS team launched an April Fools' prank featuring the fictional "LOSCoins" cryptocurrency wallet app and a persistent "LOSGenuine" security notification in builds, intended to satirize blockchain hype and counterfeit software concerns within the FOSS community. The prank, however, drew significant criticism for its intrusive nature, requiring users to reflash devices or root to remove the notification, prompting an official apology from the developers who acknowledged its poor execution and removed it from subsequent builds.[15]Later in 2018, LineageOS emphasized privacy enhancements by updating its privacy policy to clarify data disclosure practices in the Gerrit code review system and introducing per-app network restrictions, allowing users to limit Wi-Fi and mobile data access for individual applications to reduce unwanted tracking. These changes built on the project's commitment to optional root access, enabling advanced customization without compromising default security for standard users.[16]Throughout 2018, LineageOS addressed key security challenges in the Android ecosystem by merging monthly security patches from Google, including fixes for critical vulnerabilities such as those in multimedia processing libraries reminiscent of earlier threats like Stagefright, ensuring supported devices received timely protections against exploits targeting media handling and system components. The project also responded proactively to broader Android threats, such as privilege escalations and remote code execution risks, through community-driven vulnerability assessments and rapid build updates.Significant milestones marked LineageOS's growth, including over 3 million active installations by 2019. In 2021, the project expanded compatibility to additional device categories, such as more tablets and mid-range devices, enhancing accessibility for diverse hardware.[17] By late 2024, LineageOS 22 integrated Android 15 (QPR1), delivering modern features like improved privacy controls and performance optimizations to over 100 legacy devices, underscoring the ROM's role in bridging generational gaps in software updates.[18]In 2025, LineageOS advanced sustainability initiatives by prioritizing device longevity through prolonged support for older hardware, reducing electronic waste via open-source updates that extend usability beyond manufacturer timelines, as evidenced in changelogs for versions 22 and 23. Collaborations with hardware communities and maintainers further promoted eco-friendly practices, such as optimized power management and resource-efficient builds, aligning with broader efforts to foster sustainable mobile ecosystems.[7][19]
Version History
LineageOS 14.1, the inaugural version, was released on January 22, 2017, and based on Android 7.1 Nougat. It emphasized stability and reliability as the successor to CyanogenMod, with initial builds focusing on core functionality and device compatibility without major new features. Support for version 14.1 ended on February 24, 2019.[20]Version 15.1 followed on February 26, 2018, built on Android 8.1 Oreo, introducing key enhancements such as Project Treble compatibility to facilitate vendor updates and smoother transitions to future Android versions. Additional improvements included better notification handling and adaptive battery features from Oreo. End-of-life for 15.1 occurred on February 25, 2020.[20]LineageOS 16.0 launched on March 1, 2019, on Android 9 Pie, bringing gesture-based navigation options and digital wellbeing tools for usage management. It also enhanced privacy with refined app permissions. The version reached end-of-life on April 26, 2022.[20]Subsequent releases, LineageOS 17.1 (Android 10, released April 1, 2020) and 18.1 (Android 11, released April 1, 2021), incorporated scoped storage for better file access control and live captions for media accessibility. LineageOS 17.1 ended support in February 2022, while 18.1 was sunset on March 5, 2024, following the cessation of Android 11 security patches by Google.[20][21]LineageOS 19.1, based on Android 12L and released in April 2022, added approximate location toggles and improved one-handed mode. It was succeeded by version 20 on December 31, 2022, running Android 13, which featured per-app language settings and enhanced photo picker privacy. Support for version 20 remains active as of November 2025.[22][7]LineageOS 21 debuted on February 14, 2024, on Android 14, with additions like predictive back gestures and stronger blocks against monetization practices in apps. It also updated several bundled applications for better integration.[23]LineageOS 22, based on Android 15, was released on December 31, 2024, introducing satellite messaging support where hardware allows and a streamlined default app suite for reduced bloat. Security updates extend through mid-2026.[20]As of November 2025, the latest version is LineageOS 23.0, released on October 11, 2025, and built on the initial release of Android 16. It includes updated privacy dashboard enhancements and ongoing security merges up to August 2025, with further devices added post-launch.[7]
LineageOS operates as a community-driven project under the governance outlined in its official charter, which establishes a board of directors responsible for approving significant changes and maintaining project direction. This structure ensures collaborative decision-making while upholding the principles of openness and accessibility derived from its foundation on the Android Open Source Project (AOSP). The project, managed through LineageOS LLC, prioritizes independence from commercial influences, allowing developers worldwide to contribute without proprietary constraints dominating the development process.[24][1]The codebase of LineageOS is released under permissive open-source licenses to facilitate broad reuse and modification. Most components, including the core Android framework, are licensed under the Apache License 2.0, which permits commercial use, modification, and distribution with minimal restrictions. The Linux kernel, however, falls under the GNU General Public License (GPL) version 2 or later, requiring derivative works to be open-sourced. All contributions are submitted and reviewed through the Gerrit code review system, where maintainers evaluate patches for quality, compatibility, and adherence to project standards before merging them into the main repositories.[25][26][27]LineageOS adopts a cautious approach to proprietary software, limiting the inclusion of binary blobs—non-open-source firmware components from device manufacturers—to only those essential for hardware functionality, such as drivers for cameras, radios, or sensors. These blobs are explicitly documented in each device's proprietary-files.txt file within the device tree, enabling transparent extraction from official firmware during builds. The project actively encourages the community to pursue fully open-source replacements for these components, aligning with broader free software ideals, though complete elimination remains challenging for many devices due to vendor restrictions.[28]To sustain operations, LineageOS relies entirely on voluntary community donations collected via PayPal and Patreon, which fund critical infrastructure like build servers, mirrors, and hosting without accepting corporate sponsorships that could compromise its neutrality. This model contrasts sharply with commercial Android variants from OEMs, which frequently embed advertisements, bloatware, and telemetry for analytics and monetization; LineageOS delivers a clean, telemetry-free OS by default, free from such intrusions to enhance user privacy and control.[29][30][1]
Build and Contribution Process
Building LineageOS from source requires a Unix-based development environment, preferably Ubuntu 22.04 LTS or later, with at least 32 GB of RAM (64 GB recommended for complex builds) and 400 GB or more of free storage space to accommodate the source code and build artifacts.[31] Essential tools include the repo command-line utility for managing Android Open Source Project (AOSP) repositories, Git for version control, and device-specific trees for hardware integration.[32] Developers must also install build dependencies such as Python 3, OpenJDK 17 (included in source for LineageOS 21 and later), and various libraries like bc, bison, and flex via the package manager.[32]The build process begins with initializing the repository. Create a working directory, such as ~/android/lineage, and install the repo tool by downloading it from Google's storage: curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo, ensuring ~/bin is in the PATH.[32] Then, initialize the LineageOS manifest with repo init -u https://github.com/LineageOS/[android](/page/Android).git -b lineage-23.0 --git-lfs, specifying the desired branch (e.g., lineage-23.0 for Android 16-based builds).[32] Sync the sources using repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags, which downloads approximately 200-300 GB of code and can take several hours depending on internet speed and hardware.[32]After syncing, set up the build environment by running source build/envsetup.sh from the source root, which loads functions like lunch and brunch.[32] Select the target device and variant with lunch lineage_<device-codename>-userdebug, where <device-codename> is the specific device's identifier (e.g., bacon for OnePlus One).[32] To incorporate device-specific configurations, clone and apply the relevant device tree, kernel sources, and vendor blobs into the appropriate directories (e.g., device/<manufacturer>/<device>, kernel/<manufacturer>/<device>, and vendor/<manufacturer>/<device>).[33] Finally, compile the ROM using brunch lineage_<device-codename> for an automated build or m -j$(nproc) with Ninja for faster parallel compilation, producing output files like boot.img and lineage-<version>-<device>-UNOFFICIAL.zip in $OUT.[32]Contributions to LineageOS involve using Git for local changes and Gerrit for code review and submission. Developers make modifications in their local repository, stage files with git add, commit with git commit -m "descriptive message", and upload via repo upload (or git push origin HEAD:refs/for/<branch> for specific projects), which sends the change to https://review.lineageos.org for peer review.[27] The review process uses scoring labels: +1 for looks good, +2 for approval (restricted to maintainers), -1 for needs work, and -2 to block submission; verified labels (+1/-1) confirm build and boot success, often automated via Jenkins CI/CD pipelines.[27] Approved changes are merged into the upstream repositories by project leads.[27]Device maintainers own the device tree repositories, responsible for porting support, merging upstream changes, extracting and updating vendor blobs (proprietary binaries for hardware compatibility), and ensuring kernel sources from manufacturers are integrated correctly.[33] The core team oversees platform-wide modifications, such as framework updates, while maintainers handle device-specific integrations via public GitHub repositories linked during submission.[33] To become a maintainer, contributors submit a port by emailing [email protected] with links to stable device, vendor, and kernel trees, committing to ongoing maintenance.[33]Common challenges in the build and contribution process include managing vendor partitions, which require extracting blobs using tools like extract-files.sh from a stock device to avoid proprietary lock-ins, and sourcing compatible kernel trees, often released under GPL by manufacturers but needing patches for LineageOS compatibility.[34] These issues can lead to build failures if blobs are outdated or kernels lack necessary drivers, necessitating manual debugging and community collaboration. For users on non-Ubuntu hosts, containerized environments like Docker can be used to replicate the required setup.[34]
Features
Customization Options
LineageOS emphasizes user personalization through a variety of built-in customization options that extend beyond stock Android, allowing users to tailor the interface to their preferences without compromising core functionality. The theme engine, a successor to the CyanogenMod Theme Engine, enables the application of custom themes, including icon packs, wallpapers, and accent colors, via the ThemePicker app integrated into the system settings. This feature supports overlay-based theming using Runtime Resource Overlays (RRO), facilitating changes to system visuals such as colors and fonts with minimal performance impact. [35]The status bar and quick settings panel offer granular tweaks to enhance usability and aesthetics. Users can adjust the clock position (left, center, or right), select from various battery styles (e.g., percentage, circle, or hidden), and customize network traffic indicators or signal icons. Quick settings tiles can be rearranged, resized, or hidden, with options for column count and brightness slider placement, all accessible directly from the Settings app. These modifications allow for a streamlined experience, such as prioritizing frequently used toggles like Wi-Fi or flashlight.Lock screen and navigation customizations provide flexibility in interaction and display. Options include enabling always-on display with customizable content like clock styles or notifications, configuring custom gestures for quick actions (e.g., double-tap to wake or media controls), and remapping hardware buttons for navigation or app launching. Fingerprint authentication can be set to wake and unlock simultaneously, and lock screen notifications can be tuned for visibility (icons only, brief, or detailed) while maintaining security. Navigation modes support gesture-based controls with adjustable sensitivity and pill size, or traditional button layouts with remappable functions.The default Trebuchet launcher includes built-in personalization for the home screen and app organization. Users can adjust grid sizes (e.g., 4x5 or 5x5) for icons and folders, customize the app drawer with vertical or horizontal scrolling and label toggles, and set up gesture shortcuts like double-tap to lock or swipe for notifications. Hidden and protected apps features allow selective visibility in the drawer, and themed icons adapt to wallpaper colors via Material You integration.For further modifications, LineageOS is fully compatible with Magisk, enabling rootless modules through its systemless framework. This allows users to apply tweaks like ad-blocking or UI enhancements via modules without altering the system partition, preserving OTA update compatibility and reducing potential privacy risks associated with full root access.
Security and Privacy Enhancements
LineageOS delivers monthly security bulletins merged directly from the Android Open Source Project (AOSP), ensuring all supported devices receive timely patches for known vulnerabilities. These updates are typically rolled out faster than those provided by many original equipment manufacturers (OEMs), reducing the exposure window to exploits. Furthermore, LineageOS extends security support beyond standard OEM timelines, with versions like LineageOS 18.1 receiving patches for over three years from initial release, and newer builds often supported for up to five years depending on community maintenance.[1][7][36]LineageOS relies on Android's native permission framework for apppermissionmanagement, allowing users to revoke or toggle permissions on a per-app basis, including access to sensors (such as location and microphone), network connectivity, and clipboard operations. This provides precise control over app data access. In addition, the project continues to enhance privacy touchpoints, such as updates to the Trust interface for monitoring device integrity, as seen in LineageOS 23 (released October 2025).[7]Unlike stock Android distributions, LineageOS excludes built-in telemetry and removes Google data collection services by default, prioritizing user privacy from the outset. For compatibility with apps requiring Google Play Services, users can optionally install microG, an open-source implementation that avoids proprietary tracking mechanisms while enabling essential functionalities like push notifications.[1][37]LineageOS implements verified boot via Android Verified Boot 2.0 (AVB), cryptographically verifying the integrity of the boot partition and system images to prevent tampering. SELinux operates in enforcing mode by default, applying mandatory access controls to restrict processes and mitigate privilege escalations from vulnerabilities. Additional exploit mitigations include AOSP's hardened memory allocator (Scudo), which guards against heap overflows and use-after-free errors common in memory corruption attacks.[38][39]The Auditor app, available as an optional tool, allows users to verify device certification status and perform integrity checks on the system. For users employing root access, LineageOS supports integration with evasion tools like Magisk modules to hide modifications from apps that detect custom ROMs or root, maintaining compatibility with banking and other security-sensitive applications.[40]
Developer Tools
LineageOS offers enhanced Android Debug Bridge (ADB) capabilities tailored for developers, including built-in support for wireless debugging over Wi-Fi, which eliminates the need for a physical USB connection. This feature, available in developer options on LineageOS 18.1 and later, allows pairing via a secure code and IP address for seamless remote access to the device's shell.[41] Additionally, logcat functionality is integrated with standard ADB commands, enabling filtered log capture for specific buffers like radio logs using flags such as -b radio, which aids in targeted debugging of system events, crashes, and application behavior.[42]For root access, LineageOS historically provided its own lightweight su binary through the addonsu package, granting elevated privileges for advanced modifications. However, starting with LineageOS 17.1, the project discontinued official support for this implementation, recommending third-party tools like Magisk instead, which facilitates systemless root modifications to preserve OTA update compatibility and avoid tampering with core system files.[43]Kernel customization in LineageOS is facilitated by open access to device-specific kernel sources hosted on GitHub, enabling developers to download, modify, and compile tailored kernels for performance tuning or feature additions. Overclocking options are accessible via compatible applications such as Franco Kernel Manager, which, on rooted devices, allows real-time adjustments to CPU and GPU frequencies when the underlying kernel supports such configurations.[44][45]Modifications to the Hardware Abstraction Layer (HAL) are a key aspect of extending LineageOS to custom or unsupported hardware, with developers able to adapt interface definitions in repositories like android_hardware_libhardware to ensure proper integration of proprietary drivers and sensors. This process involves editing device trees during the build to align HAL implementations with specific chipsets, supporting features like cameras, fingerprints, or GNSS without altering the core Android framework.[46]LineageOS supports multiple build variants to accommodate development needs, including engineering (eng) builds that incorporate extra debugging symbols, default root access, and verbose logging for in-depth analysis, contrasting with production user builds optimized for stability. These eng variants also enable compatibility with advanced tools like Lauterbach Trace32 for low-level kernel and hardwaredebugging via JTAG interfaces, particularly useful during porting or troubleshooting boot issues.[47][34]
Integrated Applications
LineageOS ships with a suite of open-source applications developed in-house or upstreamed from the community, emphasizing lightweight functionality and privacy without proprietary dependencies. The core apps include Trebuchet as the default launcher, which supports customizable grids, hidden and protected app features, and tablet-optimized workspaces for multitasking.[48][49]The Etar calendar serves as the default scheduling app, featuring a clean Material Design interface, event reminders, and seamless integration with SeedVault for encrypted backups of calendar data to local or remote storage.[23][50] SeedVault, LineageOS's built-in backup solution, enables users to restore apps, settings, and files across devices while prioritizing end-to-end encryption and selective data export.[51]For media management, LineageOS includes the Twelve music player as of version 22.1, replacing the long-standing Eleven app; Twelve offers Material You theming, landscape mode support, advanced streaming protocols like HLS and DASH, enhanced search with Android Auto compatibility, and options such as skip silence and visualizer presets.[50] The Jelly browser provides a minimalistic WebView-based experience optimized for low-resource devices, focusing on basic navigation, bookmarking, and ad-free rendering without telemetry.[52][53]The Glimpse galleryapp handles photo and video organization with privacy in mind, including on-device editing tools for cropping, filters, and metadata removal to avoid cloud uploads or tracking.[23][54] Over-the-air updates are managed via the LineageOS Updater app, which facilitates secure downloads, signature verification, and seamless installation without rebooting to recovery.[55][56]By default, LineageOS excludes all Google applications to maintain a de-Googled environment, though users can optionally install Google Apps (GApps) packages post-installation for Play Store access or opt for the microG variant, which provides open-source implementations of Google services like push notifications and location APIs.[4][57]With the release of LineageOS 22 in late 2024, the project introduced a streamlined applications suite, updating core tools like Etar and SeedVault to their latest upstream versions while replacing legacy components such as the Eleven music player with Twelve and adding Camelot, a native PDF viewer powered by the Jetpack library for secure, offline document handling.[50] This refresh removed deprecated elements like certain audio effects modules to reduce bloat and enhance compatibility with Android 15.
Device Support
Supported Devices
As of November 2025, LineageOS officially supports over 100 devices, with the wiki listing a total of 254 devices across official, unofficial, and discontinued (EOL) categories, encompassing a wide range of smartphones and tablets from manufacturers including Samsung, Google, OnePlus, Xiaomi, Motorola, and legacy flagships from brands like LG and Sony.[58] This extensive compatibility allows users to extend the lifespan of older hardware while providing modern Android versions on newer models, with builds derived from the Android Open Source Project (AOSP).[1]Supported devices are categorized into three main types: official stable builds, unofficial community-maintained ports, and end-of-life (EOL) devices. Official builds are those vetted and hosted on the LineageOS website and wiki, offering reliable over-the-air (OTA) updates and nightly releases for select models.[58] Examples include the Google Pixel 9 series, OnePlus 13, Samsung Galaxy A71, and Motorola Moto G series, which receive regular feature and security enhancements.[6] Unofficial builds, developed by independent contributors, extend support to additional hardware not meeting official standards but still functional for enthusiasts; these are often shared on forums like XDA Developers.[59] EOL devices represent older models where support has ceased due to lack of maintainer activity or upstream incompatibilities, though archived builds may remain available for download until removed to prevent security risks from outdated patches.[60]Inclusion in official support requires adherence to specific criteria, including a committed maintainer responsible for ongoing bug fixes, merging security updates, and ensuring hardware compatibility with AOSP frameworks such as kernel drivers and proprietary blobs.[33] Devices must also pass quality control checklists outlined in the LineageOS charter, emphasizing stable performance, sufficient hardware resources (e.g., at least 2GB RAM for basic functionality), and regular update cycles to align with Android's quarterly platform releases and monthly security bulletins.[24] Without sustained maintainer involvement, devices risk demotion to unofficial status or full EOL declaration.[61]Recent expansions have included ports for foldable devices, such as community-maintained unofficial builds for the Samsung Galaxy Z Fold 5 in early 2025, building on experimental efforts from 2024 to adapt LineageOS to dual-screen architectures and hinge hardware.[62] These additions highlight growing interest in supporting innovative form factors, though official endorsement remains selective due to the complexities of foldable-specific features like multi-window optimization.Device trees, which define hardware configurations for building LineageOS, are hosted in public repositories on GitHub under the LineageOS organization for officially supported models, enabling transparency and community contributions.[63] Developers can fork these trees to create or maintain unofficial ports, ensuring verifiable compatibility through open-source code reviews.[64]
Installation and Recovery
Installing LineageOS requires specific prerequisites to ensure compatibility and avoid hardware conflicts. Users must first unlock the device's bootloader, a process that typically wipes all data and voids manufacturer warranties, as it allows installation of custom software.[65] Additionally, a custom recovery such as Lineage Recovery or Team Win Recovery Project (TWRP) must be installed via fastboot commands after enabling USB debugging and OEM unlocking in the device's developer options.[65] These steps confirm the device runs the latest stock firmware to prevent partition inconsistencies during flashing.[65]The primary installation methods include sideloading the LineageOS ZIP file via Android Debug Bridge (ADB) from a connected computer or applying over-the-air (OTA) updates directly in recovery mode. For a clean installation, users boot into recovery, perform a full wipe of the data and cache partitions (and system if upgrading from a different ROM), then sideload the ROM package using the command adb sideload lineage-*.zip.[65]OTA updates from recovery are recommended for existing installations, where users select "Apply Update" and choose the downloaded ZIP without wiping data unless upgrading major versions.[66] Full wipe installs are advised for initial setups or troubleshooting, ensuring no remnants from previous operating systems interfere.[67]LineageOS Recovery, the official custom recovery tool, provides essential features for maintenance and installation. It supports backup and restore operations for key partitions like boot, system, and data, allowing users to create Nandroid-style backups before modifications.[68] For devices with A/B partitioning schemes, the recovery handles seamless updates by flashing to inactive slots without downtime, and it integrates addon.d scripts for preserving critical files during wipes.[68] This recovery is based on the Android Open Source Project (AOSP) recovery but includes enhancements like improved file management and error handling for custom ROM environments.[68]After installation, the device reboots into LineageOS, launching an initial setup wizard similar to stock Android, guiding users through language selection, Wi-Fi connection, and account configuration. To add Google applications, users must flash a compatible GApps package (such as Open GApps or MindTheGapps) immediately after the ROM via recovery's "Apply Update" option, before the first reboot, to integrate services like the Play Store.[67] Verification involves checking the build number in Settings > About phone to confirm the correct version and ensuring core functions like camera and connectivity work; if issues arise, re-flashing or checking logs via ADB is recommended.[66]Common issues during installation include bootloader relocking attempts, which can brick the device if performed on a custom ROM, as it enforces OEM signature verification incompatible with LineageOS.[69]Data loss is inherent in bootloader unlocking and full wipes, so comprehensive backups via ADB or cloud services are essential beforehand to prevent permanent erasure of photos, apps, and settings.[67] Device compatibility should be verified against the official supported list for model-specific quirks.[70]
Community and Impact
Reception
LineageOS has been widely praised for extending the lifespan of Android devices well beyond typical manufacturer support periods. In 2025, the project continues to deliver updates to hardware released nearly a decade ago, such as the Google Pixel 2 series from 2017, bringing modern Android 15 features to otherwise obsolete phones. A Wired review emphasized how this longevity revives old devices for practical uses like media players or secondary gadgets, underscoring LineageOS's role in reducing electronic waste through software sustainability. Additionally, a 2025 Android Authority hands-on test commended its clean, minimalist user interface, which avoids bloatware for smoother performance, and noted significant battery life improvements from fewer background cloud syncs compared to stock Android implementations.[71][72][73]Despite these strengths, LineageOS faces criticisms, particularly around reliability and feature parity. Unofficial community builds often encounter occasional bugs, such as compatibility issues with banking apps or NFC payments due to bootloader modifications. Official builds, while more stable, lack proprietary device features; for instance, Pixel-exclusive tools like Call Screen and advanced camera modes (e.g., portrait effects or RAW capture) are unavailable, limiting appeal for users reliant on hardware-specific optimizations. The installation process also demands technical knowledge, including unlocking bootloaders and flashing via recovery, which can intimidate non-expert users.[73]Adoption metrics reflect strong community engagement, with official statistics reporting over 4.3 million active installations globally as of November 2025, spanning diverse devices and regions like Brazil and China leading in usage. LineageOS maintains high popularity on forums such as XDA Developers, where threads on builds, troubleshooting, and device compatibility attract thousands of participants monthly. Compared to stock Android, it provides superior out-of-the-box privacy by excluding Google apps and telemetry, enabling users to opt into services selectively; however, this customization comes with a steeper learning curve, positioning it as ideal for privacy-focused or modding enthusiasts rather than casual consumers.[74]The project's impact extends to the broader Android ecosystem, demonstrating the viability of prolonged software maintenance and prompting OEMs to extend their own update commitments. This is evident in Google's policy of seven years of OS and security updates for Pixel devices starting from the Pixel 8 series in 2023, a shift that aligns with the long-term support model popularized by custom ROMs like LineageOS.
Forks and Derivatives
/e/OS is a direct fork of LineageOS designed with a strong emphasis on privacy, featuring pre-installed microG services to enable compatibility with apps requiring Google Play Services while minimizing data collection.[75] Developed by the e Foundation, /e/OS replaces Google-dependent components with open-source alternatives and includes a suite of de-Googled applications, such as its own cloud services and app store.[75] This fork addresses user concerns over telemetry and vendor lock-in by scrubbing Google connections from core elements like the WebView implementation.[76]CalyxOS represents another privacy-oriented derivative that builds extensively on LineageOS components, though it is primarily based on the Android Open Source Project (AOSP) with added security enhancements.[77] It prioritizes de-Googling by integrating microG for limited Google service compatibility, alongside tools like Signal for secure communication and system-level privacy patches.[77] Unlike standard LineageOS, CalyxOS supports verified boot relocking on compatible devices to bolster hardware security.[78]Indirect derivatives like crDroid extend LineageOS by incorporating additional customizations, such as enhanced animations and performance tweaks, while maintaining close synchronization with the upstream codebase.[79] Similarly, Resurrection Remix focuses on extreme customization options, pulling in security patches and features from LineageOS to offer users extensive UI modifications and theming capabilities.[80]Notable projects include LineageOS for microG, which integrates microG directly into the OS and introduced a patch in September 2025 to improve Play Integrity API responses, enhancing compatibility with banking and other security-sensitive applications.[37] Integrations with Ubuntu Touch have also emerged, particularly on devices like the F(x)tec Pro1 X, where LineageOS serves as an alternative boot option alongside the Linux-based Ubuntu Touch for users seeking dual-OS flexibility.[81]Forks and derivatives often arise to introduce specialized features, such as improved privacy controls, extended support for end-of-life devices, or niche adaptations like better banking app verification through Play Integrity fixes and potential IoT optimizations in select builds.[37] As of 2025, over 20 active forks and derivatives continue to thrive, with many providing ongoing maintenance for devices dropped from official LineageOS support, thereby extending the lifecycle of older hardware.[76][77]