LineageOS 24.0 Released on Android 17: Canvas, New Devices, and a Refreshed Installation Approach

The LineageOS team unveiled build 24.0 on October 11, 2026, based on Android 17. The release ships with a new image editor called Canvas, reworked Twelve and Jelly apps, and Material Design 3 Expressive styling. On A/B-partition devices, streaming installation is now enabled by default, and the list of supported models has grown — notably with the Pixel 10 lineup. For hardware running Linux 4.4 and 4.9 kernels, official support requests are accepted only in the 22.2 branch.

What’s New in the System and Apps

Porting the project’s features onto the Android 17 base began after the platform’s June release and wrapped up faster than the developers had anticipated. According to them, preparatory work for sweeping Android code changes in earlier versions helped speed things along. The project had announced the start of LineageOS 24 development back in the summer. The 24.0 branch is now considered ready for its first release and comparable to 23.2 in stability and feature set.

A substantial portion of the built-in apps has been migrated to Material Design 3 Expressive. The headline addition is Canvas, an image editor with cropping, white balance adjustment, filters, and other basic tools. It works alongside the Glimpse gallery and the Aperture camera app.

• Twelve: loading of large music libraries is faster; the activity tab now shows the most-played albums and genres. A playback freeze with hardware audio offload enabled has been fixed, and Jellyfin compatibility has improved.
• Jelly: the browser can now handle PWA-like apps via shortcut creation.
• Etar and Seedvault: the calendar and backup tool have been updated to the latest upstream versions; some LineageOS fixes were contributed back to those projects.
• Catapult: animations and icons in the Android TV launcher have been reworked. A battery indicator has been added for mobile devices and handheld consoles.
• SetupWizard: the initial setup wizard has been fully moved to Material Design 3 Expressive, with updated screens and animations and a reworked step sequence. Builders can add pages for peripherals and device-specific features.
• WebView: the component has been updated to version 155.0.8059.30.

Streaming Updates and Automated Recovery

The Updater app has received a new Material Design 3 Expressive interface, improved animations, and explanations for each installation stage. The action sequence has been reworked, and the interface now adapts to tablets and TVs.

On A/B-partition devices, streaming updates are now enabled by default. The team claims this significantly cuts installation time, though no numeric benchmarks were provided.

Streaming A/B updates write data into the inactive system slot as the download progresses. There’s no need to keep the full update package as a separate file before installing, so no extra space is consumed in the user data partition.

For devices without A/B partitions, the recovery maintenance procedure has changed: after a successful system update, the recovery partition updates automatically on the next boot.

Flashing Directly from the Browser

Tools are now available at flash.lineageos.org that use WebUSB to communicate with a compatible device straight from the browser. They support ADB, Fastboot, the Amlogic Burn protocol, and Samsung Odin. This reduces reliance on separate desktop utilities.

Compatibility depends on the device, browser, computer OS, and USB connection. Browser tools are only an additional option: the LineageOS Wiki instructions for a specific model remain the primary supported method.

Before flashing, it’s important to back up data, verify the device model and selected files, and then follow the tool’s and documentation’s instructions. The project explicitly warns about the risks of installing third-party systems.

Which Devices Were Added

In the official list, new models appear alongside those migrated from previous branches. Below are only the LineageOS 24.0 entries with no prior version listed in the “Moved from” column:

• Google: Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, Pixel 10a.
• OnePlus: OnePlus 15, OnePlus 15T, OnePlus Pad 3 Pro, OnePlus Pad 4.
• Realme: Realme 9 5G, Realme Q5, Realme GT7 Pro, Realme GT7 Pro Racing Edition.
• Samsung: Galaxy Tab S7+ (LTE/5G and Wi-Fi).
• Amazon: Fire Max 11.
• AYN: Thor.
• SDMC: DV9135.

At the same time, new devices appeared in older branches: LineageOS 23.2 gained the LG Velvet 5G and LG Wing, while LineageOS 22.2 picked up the AYN Odin (M0 and M2), Freebox Pop / TV with Realtek Wi-Fi/Bluetooth, and Google ADT-2. These models are not among the LineageOS 24.0 newcomers.

The full device catalog on the project’s website contains supported versions, exact variants, and installation instructions. Other models will receive 24.0 builds as maintainers become ready and project requirements are met.

Restrictions for Linux 4.4 and 4.9 Kernels

New requests for official support of devices with Linux 4.4 and 4.9 kernels are accepted only for LineageOS 22.2. This rule applies even though some such models have already been ported to 23.2 and 24.0. The reason is the large number of complex workarounds that must be carried into new Android versions.

LineageOS 22.2 will continue receiving builds and monthly security fixes as long as Google publishes bulletins for Android 15. New devices for this branch can still be proposed for official support.

In the 23.2 and 24.0 branches, the project ships kernels with a full port of the necessary eBPF capabilities, GCC-free builds, and other mandatory features. The mere fact that a new system boots on an old kernel doesn’t mean the build will be accepted into the official list.

Security Fixes

According to the announcement, patches covering the period from August 2025 through October 2026 are included in LineageOS branches from 18.1 to 24.0. For versions on Android 14 and newer, starting with LineageOS 21, the team merges full security bulletins and updates the corresponding patch level string.

For LineageOS 18.1, 19.1, and 20.0, fix porting will continue, but the patch level string won’t be changed: Google no longer provides a full set of patches for these versions whose compliance can be verified. Therefore, porting individual patches doesn’t equal the full security level of current Android.

Older branches 15.1, 16.0, and 17.1 have received fixes through November 2025. Some December patches proved difficult to port; the developers invite contributors to submit suitable changes for review.

The diagram accompanying the announcement lists the following dates and statuses:

For branches 18.1 and newer, the diagram shows July 2026, while the announcement text mentions fixes through October. The project doesn’t explain the discrepancy. Based on this data, one cannot conclude that every build of each listed branch already has the same October patch level.

How to Upgrade to LineageOS 24.0

Users of official builds should open their device’s page in the LineageOS Wiki and select “Upgrade to a higher version of LineageOS.” Typically, data doesn’t need to be wiped during such a transition. Exceptions are listed in the instructions for each model: for example, wiping may be required when the partition layout changes significantly.

Switching between major versions shouldn’t automatically be treated as a routine Updater update. For instance, the instructions for the ASUS ZenFone 8 require manual installation via recovery and ADB and explicitly state that Updater blocks packages from a different LineageOS version. Users should follow the procedure for their specific model.

When upgrading from an unofficial build, the project requires following the initial installation instructions — the “Installation” section. Old guides and videos may not account for modern layout mechanisms: system-as-root, A/B, dynamic partitions, and Virtual A/B.

The wiki has been visually refreshed, the FAQ expanded, and, according to the announcement, Samsung instructions have been migrated from Odin/Heimdall to the open-source samloader-rs tool. Choose the utility and action sequence based on the current page for your device.

Shared Kernels and Compatibility Layers

For device maintainers, the project develops shared kernels for specific processor families. They can serve as a foundation and be regularly merged with security fixes and new features. The announcement lists the following options:

This is a list of shared kernels for development, not ready-made ROMs for every device with the listed chips. Support for a specific model must be verified separately.

The team has also begun consolidating shims — intermediate compatibility libraries required by many older devices. Previously they were mostly maintained separately per model; a shared set reduces duplicated work.

Experimental Boot on Computers

The project retains universal builds for Android Emulator and Android Studio, as well as GSIs for mobile devices, Android TV, and Android Automotive. Official ready-made GSIs won’t be released: quality depends on how well the device manufacturer met Project Treble requirements.

Starting with Android 12, build targets for emulators and GSIs are separated. The announcement lists the following identifiers, where $arch denotes the architecture:

• lineage_sdk_$arch — emulator
• lineage_gsi_$arch — GSI
• lineage_cf_$arch — Cuttlefish

Separate variants exist for QEMU-based virtual machines, including use with libvirt and UTM. Over the past year, their quality has noticeably improved according to the team.

A new experimental variant is designed to run directly on hardware. The developers reported successful booting on standard x86-64 PCs, Apple Silicon Macs, Qualcomm Snapdragon X laptops, and the NVIDIA DGX Spark. These are early results: they don’t imply full support for all computers in those families.

Code Checks, Accessibility, and Translations

For most app repositories and some core components, pre-merge checks are automated: formatting, lint, clang-format, pre-commit, and REUSE licensing verification. After changes are merged, GitHub Actions publishes APKs and other build artifacts.

The a11y project conducted an accessibility audit of the entire installation process and the LineageOS app suite. Based on the results, navigation and the recovery interface have already begun changing. More than 40 contributors also completed accessibility training in development; the team plans to present detailed audit results later.

LineageOS invites developers to propose new devices and restore support for models that previously had official builds. Participation is possible even without device maintainership: the project accepts app changes, documentation, and translations. Among the translators’ achievements, the team highlights full Welsh language support.

Bottom Line

LineageOS 24.0 expands the capabilities of built-in apps and simplifies system maintenance: basic photo editing is available in Canvas, and update installation has a clearer interface. For device owners, the main prerequisite for upgrading remains an available official build and up-to-date instructions for their specific model. Users of models with old kernels can continue receiving fixes in LineageOS 22.2 within the announced support window.