LineageOS: Recent Episodes

View Details

It’s Summer (in the Northern Hemisphere at Least)Hello again! We are trying to give more regular updates, in order to inform you of some changes to our infrastructure, our apps, and our security patching efforts. Over the past few months we have had many contributors tirelessly working on every aspect of the OS, as well as the infrastructure behind it, especially our contributor niclimcy who is responsible for many of the changes listed below.

New Stats PageOne of the biggest updates so far was the rewriting of our stats page by niclimcy, luk1337, and luca020400. The updated application includes a map to view active locations; filtering by country, by carrier, by device model, and by version. We also pruned some data that was clearly spoofed or tampered.

Web Flashing SupportWe are pleased to offer a set of web flash-tools, something that had been requested for many years. Now by accessing the flasher through our download portal, you will be able to use your browser to flash using fastboot, adb, Samsung’s Odin protocol, and Amlogic’s burn mode. Please remember though that this is not a complete flashing process, you still must follow our wiki instructions for your specific device.

These efforts are only possible due to kdrag0n’s amazing work on fastboot.js, yume-chan’s brilliant work on ya-webadb, and r3pwn’s timeless work on libmjolnir - go thank them!

Contributors niclimcy and luk1337 brought these tools into our Updater portal and sent their improvements back upstream in many cases - massive thanks to them!

Wiki Dark ModeThe wiki is the source of truth when it comes to LineageOS, but it was also a source of temporary blindness! Thankfully, niclimcy has remedied this for us by adding built-in dark mode. And we must say, it looks very nice.

Gerrit UpdatesOur code review instance has not only been updated to the latest version, but has also had a few improvements made to it as well. In the past it was required to login with a Google account, but now you will be able to choose between logging in with your Google or your GitHub account.

Issue TrackerOur issue tracker has been recently migrated to GitHub away from GitLab, due to problems with their automatic issue handling, and the inability to sign up without providing a phone number/credit card, among other things. The new issue tracker features many new improvements, including an easy to fill out issue forms, and immediate notification of maintainers when bugs are filed for their devices.

Security UpdatesWith the release of Android 16, Google changed the way it has been handling security patches for Android, by bundling most patches into quarterly releases. We have adapted to these changes by doing the following.

1. For LineageOS versions 21, 22, and 23; we are testing and merging patches from each monthly security bulletin as they are released by Google.
2. For LineageOS versions 18, 19, and 20; we are backporting patches as quickly as possible, and are currently patched through the July 2026 security patch level (SPL).
3. For LineageOS versions 14, 15, 16, and 17; the process of backporting is much more difficult (due to codebase changes), so support is much more hit and miss. LineageOS 16 and 17 have all patches through the November 2025 SPL, and 14 and 15 should be catching up soon.

Please keep in mind though that for some of these older versions, backporting is very complex, so we can’t guarantee complete (or even partial) security. But rest assured we are doing our best to support every Android version as long as we can.

A big thanks to mse1969 for spearheading the efforts, with assistance from Lost-Entrepreneur439, FlameFire, Syphyr and npjohnson!

App UpdatesIt hasn’t just been background updates to the OS, default apps have received several updates as well. Our integrated backup Seedvault solution and the default calendar Etar have both been updated to their latest versions. Twelve, our default music app, has received Ampache support thanks to longtime contributor SebaUbuntu. And finally, Glimpse (our default gallery app) received a few improvements including Double-Tap to seek support in videos, better lock screen handling, support for motion photos, and a setting to remember the last playback position when watching videos.

UpdaterLast blog post we teased massive changes to our Updater app, and thanks to the amazing work of developer pjgowtham and designer Vazguard, we are pleased to unveil it. These changes have implemented Material 3 Expressive, modernized many aspects of the underlying codebase, improved the user experience, and made the app more reliable and efficient. In addition to the above changes, we have made changes to the updater API to expose more information about each individual update, mainly which ASBs are included.

This hopefully means no more “Is the ASB merged yet this month?” questions, as the Updater app will show you the SPL of each new update before you install it!

We also now stream A/B OTA update packages by default, so you’ll notice both less space is necessary, and the updates apply much faster!

The FutureWe’ll keep this one short - Google has released Android 17 to the public. Therefore, LineageOS 24 development is underway. As always, there will be no ETAs provided - but we are progressing nicely!

TranslationsThanks to the work of a team of contributors, we are pleased to announce that we are adding another language to our roster; Please welcome Central Kurdish! And we still need translators (for it and all other languages), so if you are bi-, tri-, or anything lingual please visit our wiki and join us in our efforts to make LineageOS accessible for everyone, everywhere.

Build rosterAdded 23.2 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | LG V60 ThinQ | timelm | pnguyen879 | 23.0 | | Motorola ThinkPhone by motorola | bronco | demon000, elginsk8r | 22.2 | | Motorola edge | racer | ItsVixano | 21 | | Motorola moto g 5G / Motorola moto one 5G ace | kiev | basamaryan, SyberHexen, Vivekachooz | 22.2 | | Motorola moto g 5G plus / Motorola moto one 5G | nairo | ItsVixano, Ivanmeler, SyberHexen, zlewchan | 22.2 | | Motorola moto g50 | ibiza | Onelots | | Motorola one action | troika | Stricted, npjohnson, DaemonMCR | 22.2 | | Motorola one vision / Motorola p50 | kane | Stricted, npjohnson, DaemonMCR | 22.2 | | OSOM OV1 | pyrite | mikeioannina, npjohnson | | Realme GT Neo6 | bale | MisterZtr | | Retroid Pocket 6 | RP6 | AnierinBliss | | SHIFTphone 8 | otter | amartinz, mikeioannina | | Samsung Galaxy A52 4G | a52q | Simon1511 | 22.2 | | Samsung Galaxy A52s 5G | a52sxq | Simon1511 | 22.2 | | Samsung Galaxy A72 | a72q | Simon1511 | 22.2 | | Samsung Galaxy A73 5G | a73xq | Simon1511 | 22.2 | | Samsung Galaxy M52 5G | m52xq | Simon1511 | 22.2 | | Samsung Galaxy S23 | dm1q | DaemonMCR, josip-k, krazey | | Samsung Galaxy Tab S6 Lite 2024 (Wi-Fi) | gta4xlswifi | Linux4 | | Sony Xperia 1 VI | pdx245 | BotchedRPR | | Sony Xperia 10 VII | pdx257 | LuK1337, jmpfbmx | | The Fairphone (Gen. 6) | FP6 | ArianK16a, mikeioannina | | Xiaomi 11 Lite 5G NE / Xiaomi 11 Lite NE 5G / Xiaomi Mi 11 LE | lisa | ItsVixano | 22.2 | | Xiaomi 12S | mayfly | Flower Sea | 23.0 | | Xiaomi 13 Pro | nuwa | Minus | 23.0 | | Xiaomi 13 | fuxi | lolipuru | 23.0 | | Xiaomi Mi 10S | thyme | Alcatraz323, Flicker372 | 22.2 | | Xiaomi Mi 10T / Xiaomi Mi 10T Pro / Xiaomi Redmi K30S Ultra | apollon | Ramisky | 22.2 | | Xiaomi Mi 11 Lite 5G | renoir | ArianK16a | 22.2 | | Xiaomi Mi 11 | venus | ItsVixano | | Xiaomi POCO F2 Pro / Xiaomi Redmi K30 Pro | lmi | SebaUbuntu | 22.2 | | Xiaomi POCO F4 / Xiaomi Redmi K40S | munch | SebaUbuntu | 22.2 | | Xiaomi POCO F6 / Xiaomi Redmi Turbo 3 | peridot | adarshgrewal | | Xiaomi POCO F6 Pro / Xiaomi Redmi K70 | vermeer | Lunark | 23.0 | | Xiaomi Redmi 12C / Xiaomi Redmi 12C NFC / Xiaomi POCO C55 | earth | surblazer | 23.0 | | Xiaomi Redmi K60 Pro | socrates | WenHao2130 | 23.0 | | Xiaomi Redmi Note 10S / Xiaomi Redmi Note 10S NFC / Xiaomi Redmi Note 10S Latin America / Xiaomi POCO M5s | rosemary | surblazer | 23.0 | | Zinwa Q25 Pro | Q25 | electimon, basamaryan, npjohnson, Androbots |

Added 22.2 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | Freebox Pop / TV | nicepool | chrmhoffmann, npjohnson | | LG G5 (International) | h850 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG G5 (T-Mobile) | h830 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG G5 (US Unlocked) | rs988 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG G6 (EU Unlocked - ENG BL) | h870d | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG G6 (EU Unlocked) | h870 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG G6 (T-Mobile) | h872 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG G6 (US Unlocked) | us997 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG V20 (AT&T) | h910 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG V20 (GSM Unlocked - DirtySanta) | us996d | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG V20 (GSM Unlocked) | us996 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG V20 (Global) | h990 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG V20 (Sprint) | ls997 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG V20 (T-Mobile) | h918 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | LG V20 (Verizon) | vs995 | npjohnson, Simex, basamaryan, Androbots, AShiningRay, ROMSG, Geel | 21 | | Smartisan R1 | trident | rtx4d |

View Details

Developer Verification: What it is, and how it affects youWhat is Developer Verification?Android Developer Verification is Google’s requirement, rolling out regionally starting September 2026 (global by 2027), that apps be registered to an identity-verified developer before they can be installed on a “certified” Android device, meaning any device shipping Google Play, Play Services, and the rest of the Google Mobile Services (GMS) suite. This applies regardless of the installation source; whether it is the Play Store, third-party stores, or direct APK sideload.

How does this affect LineageOS and its users?TL;DR: This will not affect LineageOS directly. But it may affect users running the stock ROM on their device.

When the stock ROM is installed on a certified device, package installation will be gated by the package “AndroidDeveloperVerification”, which will check against the developer’s registered/verified signing identity. Google is providing an “advanced flow” opt in for power users to install unverified-developer apps after acknowledging risk and waiting a full day. This is a one-time toggle to disable verification, not something you have to redo every time you wish to install a package.

Why is Google doing this?We don’t actually know. What we have is Google’s stated reasoning, and even if you’re skeptical of the outcome, it’s worth taking at face value.

Google’s public justification is fraud and malware prevention: they claim over 50x more malware comes from sideloaded/internet sources than from the Play Store, and that anonymous, disposable developer identities let bad actors get caught, rebrand, and redistribute the same malware in hours. They’ve also pointed to regulatory pressure (the EU’s DSA, India’s IT Rules, etc.) pushing platforms toward developer traceability generally and framed the rollout order (fraud-heavy markets first: Brazil, Indonesia, Singapore, Thailand) as evidence the fraud rationale is the actual driver rather than a pretext.

That’s the claim. Whether or not it’s the whole story is a separate question.

Critics such as F-Droid, EFF, and “Keep Android Open” point out that this also happens to route every install path through Google-controlled infrastructure, hands Google a kill switch over any app or developer worldwide, and arrives shortly after Google’s antitrust lawsuits.

Both things can be true at once: real fraud is a problem and the restriction of developers is a convenient side effect of solving it this way - and we’re not in a position to pretend we know Google’s internal reasoning. We’re just telling you what they’ve said and what it changes; you can weigh the “why” yourself.

What are we going to do about it?This changes nothing for LineageOS, so we don’t need to take any direct actions. This isn’t a switch Google flips on our behalf, it is enforced by a dedicated application called “AndroidDeveloperVerification” (com.google.android.verifier), which the OS is then told is the designated verification gatekeeper. For curious developers or other ROM maintainers, it is wired up through two framework overlays, config_developerVerificationServiceProviderPackageName and config_developerVerificationPolicyDelegatePackageName.

This is a different situation from Play Integrity: Play Integrity’s attestation logic lives inside Play Services itself, and apps call into it directly for attestation. Developer Verification, by contrast, is its own standalone app that the frameworks are pointed at as a provider.

We have not ever, nor do we intend to ever, ship GMS. That means we’re not subject to the Google Test Suite (GTS) certification Google apps are required to pass. Therefore we have no obligation to install “AndroidDeveloperVerification” or point the aforementioned configurations (overlays) at it.

What can you do about it?If you sideload GApps packages, be aware that a GApps package could choose to bundle “AndroidDeveloperVerification” and enable it. We’re not aware of any reason an aftermarket GApps package would opt into that, since doing so would restrict what its own users can sideload. If your GApps provider ever does, you can simply switch to a different package.

So it’s a separate app… for now. Could Google move the functionality into Play Services?They absolutely could. If that happens, we’ll do what we already do for a number of annoying Play Services-provided over-the-air update implementations: disable it globally.

What have we (LineageOS) done about all of this?We have signed the “Keep Android Open” petition alongside a number of other FOSS foundations and organizations with the hope of supporting independent developers.

The LineageOS Team

View Details

23.2 Halftime ReleaseHello again!

The last few months have been quite the endeavor, as we have been busy rebasing and updating LineageOS, on not one but two large AOSP releases. Nevertheless, we have persevered and are pleased to present LineageOS 23.2.

Changes in AOSPOver the last few years, AOSP has been shifting to a quarterly release cadence, meaning that new features and bug fixes are released every three months. Google recently announced that AOSP will be shifting to a biannual release cadence, meaning that the latest fixes and features will drop every six months now.

Android Security Bulletins will still be released, and picked to all supported LineageOS versions monthly.

While this change does not significantly alter our development process, it is worth noting that LineageOS will adopt a six-month cadence, with work on each new point release starting every six months.

What’s ChangedWhen you install or update to this release, you will immediately notice the new UI and color scheme. This is because LineageOS is now officially using Google’s Material Expressive design system which focuses on expressive colors, and emotive design elements.

In addition, you may notice the updated UI of the Quick Settings panel, which now contains fully customizable tiles, which in our opinion are much more pleasant to use! In this release, you will also find an expanded dark theme, and more powerful file utilities surrounding private spaces.

Updated AppsThis release mainly focuses on the Material Expressive design language, and in the interest of keeping up with these guidelines, we have been working diligently at updating the default apps to Material Expressive.

UpdaterContributor pjgowtham has been hard at work on updating the Updater app, and when those changes are merged, you will be treated to a completely redesigned UI, improved update management, delightful animations and various bugs fixed. It wasn’t quite ready for the 23.2 launch, but will be soon, so be on the lookout!

Other appsIn addition to the Updater, Twelve (the default music app), Deskclock and ExactCalculator have received Material 3 Expressive updates, which brings them into the modern era. Stay tuned for similar updates to the other default apps!

Development ToolsIn the previous release changelog, we teased some development tools that were in the midst of being reviewed. These have now been merged, and developers have some new tools in their arsenal:

• beautify_rro.py: Beautifies multiple existing RROs given a directory.
• generate_rro.py: Extracts RROs from a prebuilt overlays directory.
• update_certificates.py: Updates app certificates given a stock dump directory.
• decompile_cil.py: Extracts sepolicy rules from a prebuilt SELinux image.
• extract_aconfig.py: Extracts config files from stock dumps.
• match_manifest_tarball.py: Matches kernel (or source) tarball releases against public Git history.

Leadership ChangesAfter roughly seven years with Lineage, and another five with CyanogenMod, we’re sad to announce Rashed is stepping away from the project to spend more time offline. We wish him the best!

We’re also glad to announce that the current directors group have voted Nolen Johnson (npjohnson) in as the ninth director. Welcome!

DeprecationsOverall, we feel that the 23.2 branch has reached feature and stability parity with 23.0 and isready for initial release.

We will still allow new LineageOS 21 submissions to be forked to the organization, but we will continue our policy of no longerallowing newly submitted LineageOS 21 devices to ship.

LineageOS 23.2 will launch building for a decent selection of devices, with additional devices tocome as they meet the requirements specified by theCharter and aremarked as ready for builds by their maintainer.

Updating to LineageOS 23.2 from LineageOS 23.0To update, please follow the update guide for your device by clicking on it here and then on “Update to a newer build of the same LineageOS version”.

If you’re coming from an unofficial build, you need to follow the good ole’ install guide for yourdevice, just like anyone else looking to install LineageOS for the first time. These can be found here by clicking on your device and then on “Installation”.

Please note that if you’re currently on an official build, you DO NOT need to wipe.

Upgrading to LineageOS 23.2 from LineageOS 22.2 or priorTo upgrade, please follow the upgrade guide for your device by clicking on it here and then on “Upgrade to a higher version of LineageOS”.

If you’re coming from an unofficial build, you need to follow the good ole’ install guide for yourdevice, just like anyone else looking to install LineageOS for the first time. These can be found here by clicking on your device and then on “Installation”.

Please note that if you’re currently on an official build, you DO NOT need to wipe your device,unless your device’s wiki page specifically dictates otherwise, as is needed for some devices withmassive changes, such as a repartition.

Developers, Developers, DevelopersOr, in this case, maintainers, maintainers, maintainers. We want your device submissions!

If you’re a developer and would like to submit your device for officials, it’s easier than ever.Just follow the instructions here.

The above also applies to people looking to bring back devices that were at one point official butare no longer supported - seriously - even if it’s not yet completely compliant, submit it! Maybewe can help you complete it.

After you submit, within generally a few weeks, but in most cases a week, you’ll receive somefeedback on your device submission; and if it’s up to par, you’ll be invited to our communicationsinstances and your device will be forked to LineageOS’s official repositories.

Don’t have the knowledge to maintain a device, but want to contribute to the platform? We have lotsof other things you can contribute to.For instance, our apps suite is always looking for new people to helpimprove them, or you cancontribute to the wiki by addingmore useful information & documentation.Gerrit is always open for submissions! Onceyou’ve contributed a few things, send an email to devrel(at)lineageos.org detailing them, and we’llget you in the loop.

Also, if you sent a submission that didn’t get a response in the last few months, please follow up,we’ve swapped providers again!

Generic TargetsWe’ve talked about these before, but these are important, so we will cover them again.

Although we’ve had buildable generic targets since 2019, to make LineageOS more accessible todevelopers, and really anyone interested in giving LineageOS a try, we’ve documented how to usethem in conjunction with the AndroidEmulator/Android Studio!

Additionally, similar targets can now be used to build GSI in mobile, Android TV configurations,and Android Automotive making LineageOS more accessible than ever todevices using Google’sProject Treble.We won’t be providing official builds for these targets, due to the fact the user experience variesentirely based on how well the device manufacturer complied with Treble’s requirements, but feelfree to go build them yourself and give it a shot!

Please note that Android 12 (and by proxy all later Android versions) diverged GSI and Emulatortargets. Emulator targets reside in lineage_sdk_$arch, while GSI targets reside inlineage_gsi_$arch.

Additionally, experimental targets now exist for QEMU-based virtual machine software (libvirt,UTM, etc). Instructions on building and utilizing these targets can be found onthe Wiki.

TranslationsBilingual? Trilingual? Anything-lingual?

If you think you can help translate LineageOS to a different language, jump over toour wiki and have a go!If your language is not supported natively in Android, reach out to us on Crowdin and we’ll takethe necessarysteps to include your language.For instance, LineageOS is the first Android custom distribution that has complete supportfor the Welsh (Cymraeg) language thanks to its community of translators.

Please, contribute to translations only if you are reasonably literate in the target language;poor translations waste both our time and yours.

Build rosterAdded 23.2 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | ASUS ZenFone 8 | sake | DD3Boh, mikooomich | 23.0 | | F(x)tec Pro¹ X | pro1x | BadDaemon, bgcngm, mccreary, npjohnson, qsnc, tdm | 23.0 | | Fairphone 4 | FP4 | mikeioannina | 23.0 | | Fairphone 5 | FP5 | mikeioannina | 23.0 | | Google Pixel 4 XL | coral | mikeioannina, npjohnson | 23.0 | | Google Pixel 4 | flame | mikeioannina, npjohnson | 23.0 | | Google Pixel 4a 5G | bramble | mikeioannina | 23.0 | | Google Pixel 4a | sunfish | mikeioannina | 23.0 | | Google Pixel 5 | redfin | mikeioannina | 23.0 | | Google Pixel 5a | barbet | mikeioannina | 23.0 | | Google Pixel 6 Pro | raven | mikeioannina | 23.0 | | Google Pixel 6 | oriole | mikeioannina | 23.0 | | Google Pixel 6a | bluejay | mikeioannina | 23.0 | | Google Pixel 7 Pro | cheetah | mikeioannina | 23.0 | | Google Pixel 7 | panther | mikeioannina | 23.0 | | Google Pixel 7a | lynx | mikeioannina, niclimcy | 23.0 | | Google Pixel 8 Pro | husky | mikeioannina | 23.0 | | Google Pixel 8 | shiba | mikeioannina | 23.0 | | Google Pixel 8a | akita | mikeioannina | 23.0 | | Google Pixel 9 Pro Fold | comet | mikeioannina | 23.0 | | Google Pixel 9 Pro XL | komodo | mikeioannina | 23.0 | | Google Pixel 9 Pro | caiman | mikeioannina | 23.0 | | Google Pixel 9 | tokay | mikeioannina | 23.0 | | Google Pixel 9a | tegu | mikeioannina | 23.0 | | Google Pixel Fold | felix | mikeioannina | 23.0 | | Google Pixel Tablet | tangorpro | LuK1337, mikeioannina, npjohnson | 23.0 | | Lenovo Z5 Pro GT | heart | themard, optionaltoast | 23.0 | | Lenovo Z6 Pro | zippo | Lucchetto, themard, einargednochsson | 23.0 | | Motorola defy 2021 | bathena | Deivid Ignacio Parra (Deivid21), Francisco Sanchez (Fraaxius) | 23.0 | | Motorola edge 20 pro | pstar | npjohnson, SGCMarkus | 23.0 | | Motorola edge 20 | berlin | npjohnson, SGCMarkus | 23.0 | | Motorola edge 2021 | berlna | SyberHexen | 23.0 | | Motorola edge 2024 | avatrn | elginsk8r | 23.0 | | Motorola edge 30 fusion | tundra | themard, electimon | 23.0 | | Motorola edge 30 neo | miami | marcost2 | 23.0 | | Motorola edge 30 | dubai | themard, sb6596, Demon000 | 23.0 | | Motorola edge 40 pro / Motorola moto X40 / Motorola edge+ (2023) | rtwo | sgcmarkus, themard | 23.0 | | Motorola edge s / Motorola moto g100 | nio | dianlujitao | 23.0 | | Motorola moto e7 plus / Lenovo K12 | guam | Rajin Gangadharan (GRajin), Deivid Ignacio Parra (Deivid21) | 23.0 | | Motorola moto g 5G - 2024 | fogo | mikeioannina | 23.0 | | Motorola moto g power 2021 | borneo | Syed Fawwaz Hussain (Fazwalrus), Deivid Ignacio Parra (Deivid21) | 23.0 | | Motorola moto g stylus 5G (2022) | milanf | AnierinBliss | 23.0 | | Motorola moto g stylus 5G | denver | Vivekachooz | 23.0 | | Motorola moto g10 / Motorola moto g10 power / Lenovo K13 Note | capri | Deivid Ignacio Parra (Deivid21), Sultanahamer | 23.0 | | Motorola moto g200 5G / Motorola Edge S30 | xpeng | themard, rogers2602 | 23.0 | | Motorola moto g30 / Lenovo K13 Pro | caprip | mikeioannina, Deivid Ignacio Parra (Deivid21) | 23.0 | | Motorola moto g32 | devon | Dhina17, mikeioannina, Deivid Ignacio Parra (Deivid21) | 23.0 | | Motorola moto g34 5G / Motorola moto g45 5G | fogos | mikeioannina | 23.0 | | Motorola moto g42 | hawao | Dhina17, mikeioannina, Deivid Ignacio Parra (Deivid21) | 23.0 | | Motorola moto g52 | rhode | Dhina17, mikeioannina, tomoms, Deivid Ignacio Parra (Deivid21) | 23.0 | | Motorola moto g82 5G | rhodep | AnandSuresh02, sevenrock | 23.0 | | Motorola moto g84 5G | bangkk | mikeioannina | 23.0 | | Motorola moto g9 play / Motorola moto g9 / Lenovo K12 Note | guamp | DelightReza, Deivid Ignacio Parra (Deivid21) | 23.0 | | Motorola moto g9 power / Lenovo K12 Pro | cebu | Deivid Ignacio Parra (Deivid21) | 23.0 | | Nothing Phone (1) | Spacewar | zlewchan, ko_ko_konb | 23.0 | | Nothing Phone (2) | Pong | chandu078 | 23.0 | | Nubia Mini 5G | TP1803 | ArianK16a, npjohnson | 23.0 | | OnePlus 11 5G | salami | bgcngm | 23.0 | | OnePlus 12 | waffle | chandu078 | 23.0 | | OnePlus 12R | aston | inferno0230 | 23.0 | | OnePlus 13 | dodge | bgcngm, chandu078, dianlujitao, ItsVixano | 23.0 | | OnePlus 13R | giulia | chandu078, madmax | 23.0 | | OnePlus 7 Pro / OnePlus 7 Pro (T-Mobile) | guacamole | LuK1337, elginsk8r | 23.0 | | OnePlus 7 | guacamoleb | shantanu-sarkar | 23.0 | | OnePlus 7T / OnePlus 7T (T-Mobile) | hotdogb | LuK1337, Onelots | 23.0 | | OnePlus 7T Pro | hotdog | qsnc | 23.0 | | OnePlus 8 / OnePlus 8 (T-Mobile) | instantnoodle | jabashque | 23.0 | | OnePlus 8 Pro | instantnoodlep | LuK1337 | 23.0 | | OnePlus 8T / OnePlus 8T (T-Mobile) | kebab | LuK1337, mikeioannina | 23.0 | | OnePlus 9 / OnePlus 9 (T-Mobile) | lemonade | mikeioannina, tangalbert919, ZVNexus | 23.0 | | OnePlus 9 Pro / OnePlus 9 Pro (T-Mobile) | lemonadep | LuK1337, bgcngm, mikeioannina | 23.0 | | OnePlus 9R | lemonades | DaemonMCR, Tuan Anh | 23.0 | | OnePlus 9RT | martini | basamaryan | 23.0 | | OnePlus Ace 3 Pro | corvette | chandu078, LucasBlackLu | 23.0 | | OnePlus Ace 3 | astonc | inferno0230 | 23.0 | | OnePlus Ace 3V | audi | anky894 | 23.0 | | OnePlus Ace 5 | giuliac | chandu078, madmax | 23.0 | | OnePlus Nord 4 | avalon | anky894 | 23.0 | | OnePlus Nord 5 | lexus | grepfox | 23.0 | | OnePlus Nord CE 2 Lite 5G | oscaro | Vivekachooz | 23.0 | | OnePlus Nord CE 3 Lite 5G / OnePlus Nord N30 5G | larry | Vivekachooz | 23.0 | | OnePlus Nord CE4 | benz | inferno0230 | 23.0 | | OnePlus Nord N20 | gunnar | tangalbert919 | 23.0 | | OnePlus Nord N200 | dre | tangalbert919, elginsk8r | 23.0 | | OnePlus Pad 2 Pro / OnePlus Pad 3 | erhai | LuK1337, bgcngm | 23.0 | | OnePlus Pad Pro / OnePlus Pad 2 | caihong | inferno0230 | 23.0 | | Razer Edge 5G / Razer Edge WiFi | nicole | AnierinBliss, balika011, mikeioannina, npjohnson | 23.0 | | Realme 10 Pro 5G | luigi | Vivekachooz | 23.0 | | Realme 9 Pro 5G / Realme 9 5G / Realme Q5 | oscar | Vivekachooz | 23.0 | | Samsung Galaxy A21s | a21s | DaemonMCR | 23.0 | | Samsung Galaxy A71 | a71 | Haky86 | 23.0 | | Samsung Galaxy F62 / Samsung Galaxy M62 | f62 | Linux4 | 23.0 | | Samsung Galaxy Note10 5G | d1x | Rocky7842, Linux4 | 23.0 | | Samsung Galaxy Note10 | d1 | Linux4 | 23.0 | | Samsung Galaxy Note10+ 5G | d2x | Linux4 | 23.0 | | Samsung Galaxy Note10+ | d2s | Linux4 | 23.0 | | Samsung Galaxy S10 5G | beyondx | Linux4 | 23.0 | | Samsung Galaxy S10 | beyond1lte | Linux4 | 23.0 | | Samsung Galaxy S10+ | beyond2lte | Linux4 | 23.0 | | Samsung Galaxy S10e | beyond0lte | Linux4 | 23.0 | | Samsung Galaxy S20 (4G/5G) | x1s | ExtremeXT, fcuzzocrea | 23.0 | | Samsung Galaxy S20 FE (Exynos) | r8s | CmdCtrlDevic3 | 23.0 | | Samsung Galaxy S20 FE (Snapdragon) / Samsung Galaxy S20 FE 5G | r8q | ata-kaner | 23.0 | | Samsung Galaxy S20 Ultra (5G) | z3s | ExtremeXT, fcuzzocrea | 23.0 | | Samsung Galaxy S20+ (4G/5G) | y2s | ExtremeXT, fcuzzocrea | 23.0 | | Samsung Galaxy Tab A7 10.4 2020 (LTE) | gta4l | chrmhoffmann | 23.0 | | Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) | gta4lwifi | chrmhoffmann | 23.0 | | Samsung Galaxy Tab S6 Lite (LTE) | gta4xl | haggertk, Linux4 | 23.0 | | Samsung Galaxy Tab S6 Lite (Wi-Fi) | gta4xlwifi | Linux4, haggertk | 23.0 | | Samsung Galaxy Tab S7 (LTE) | gts7l | bgcngm | 23.0 | | Samsung Galaxy Tab S7 (Wi-Fi) | gts7lwifi | bgcngm | 23.0 | | Solana Saga | ingot | mikeioannina, npjohnson, tomoms | 23.0 | | Sony Xperia 1 II | pdx203 | hellobbn | 23.0 | | Sony Xperia 1 III | pdx215 | hellobbn | 23.0 | | Sony Xperia 1 IV | pdx223 | Tuan Anh | 23.0 | | Sony Xperia 1 V | pdx234 | hellobbn | 23.0 | | Sony Xperia 10 IV | pdx225 | LuK1337, jmpfbmx | 23.0 | | Sony Xperia 10 Plus | mermaid | LuK1337 | 23.0 | | Sony Xperia 10 V | pdx235 | jmpfbmx, LuK1337 | 23.0 | | Sony Xperia 10 | kirin | LuK1337 | 23.0 | | Sony Xperia 5 II | pdx206 | kyasu, hellobbn | 23.0 | | Sony Xperia 5 III | pdx214 | kyasu, hellobbn | 23.0 | | Sony Xperia 5 IV | pdx224 | Tuan Anh, wolfhechel | 23.0 | | Sony Xperia 5 V | pdx237 | kyasu, hellobbn | 23.0 | | Sony Xperia XA2 Plus | voyager | LuK1337 | 23.0 | | Sony Xperia XA2 Ultra | discovery | LuK1337 | 23.0 | | Sony Xperia XA2 | pioneer | LuK1337, jmpfbmx | 23.0 | | Xiaomi 12 Pro | zeus | Adrianyyy, ArianK16a | 23.0 | | Xiaomi 12 | cupid | Adrianyyy, ArianK16a | 23.0 | | Xiaomi 12S Pro | unicorn | Adrianyyy, ArianK16a | 23.0 | | Xiaomi 12S Ultra | thor | Adrianyyy, ArianK16a | 23.0 | | Xiaomi 12T Pro / Xiaomi Redmi K50 Ultra | diting | Adrianyyy, ArianK16a | 23.0 | | Xiaomi MIX Fold 2 | zizhan | Adrianyyy, ArianK16a | 23.0 | | Xiaomi Mi 10 Pro | cmi | luffitys | 22.2 | | Xiaomi Mi 10 | umi | 0xCAFEBABE, przekichane | 23.0 | | Xiaomi Mi 10T Lite 5G / Xiaomi Mi 10i 5G / Xiaomi Redmi Note 9 Pro 5G | gauguin | Penguin766, Lynnrin | 23.0 | | Xiaomi Mi 9T / Xiaomi Redmi K20 (China) / Xiaomi Redmi K20 (India) | davinci | ArianK16a | 23.0 | | Xiaomi Mi Note 10 / Xiaomi Mi Note 10 Pro / Xiaomi Mi CC9 Pro | tucana | SanyaPilot | 23.0 | | Xiaomi POCO F3 / Xiaomi Redmi K40 / Xiaomi Mi 11X | alioth | SahilSonar, SebaUbuntu, althafvly, chrmhoffmann | 23.0 | | Xiaomi POCO F5 (Global) / Xiaomi POCO F5 (India) / Xiaomi Redmi Note 12 Turbo | marble | Adrianyyy, ArianK16a | 23.0 | | Xiaomi POCO F5 Pro / Xiaomi Redmi K60 | mondrian | Adrianyyy, ArianK16a | 23.0 | | Xiaomi Redmi 3S / Xiaomi Redmi 3X / Xiaomi Redmi 4 (India) / Xiaomi Redmi 4X / Xiaomi Redmi Note 5A Prime / Xiaomi Redmi Y1 Prime | Mi8937 | 0xCAFEBABE | 23.0 | | Xiaomi Redmi 4A / Xiaomi Redmi 5A / Xiaomi Redmi Note 5A Lite / Xiaomi Redmi Y1 Lite | Mi8917 | 0xCAFEBABE | 23.0 | | Xiaomi Redmi 7A / Xiaomi Redmi 8 / Xiaomi Redmi 8A / Xiaomi Redmi 8A Dual | Mi439 | 0xCAFEBABE | 23.0 | | Xiaomi Redmi Note 10 Pro / Xiaomi Redmi Note 10 Pro (India) / Xiaomi Redmi Note 10 Pro Max (India) | sweet | basamaryan, danielml3 | 23.0 | | Xiaomi Redmi Note 13 Pro 5G / Xiaomi Redmi Note 13 Pro 5G (India) / Xiaomi Redmi Note 13 Pro 5G (China) / Xiaomi POCO X6 5G / Xiaomi POCO X6 5G (India) | garnet | adarshgrewal | 23.0 | | Xiaomi Redmi Note 7 Pro | violet | 0xCAFEBABE | 23.0 | | Xiaomi Redmi Note 8 / Xiaomi Redmi Note 8T | ginkgo | Skyblueborb, mikeioannina, programminghoch10 | 23.0 |

Added 23 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | LG V60 ThinQ | timelm | pnguyen879 | 22.2 | | Xiaomi POCO F6 Pro / Xiaomi Redmi K70 | vermeer | Lunark |

Added 22.2 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | Google Jamboard [Android TV] | baracus | npjohnson, webgeek1234 | | Google Jamboard [Tablet] | baracus_tab | npjohnson, webgeek1234 | | Nubia X | nx616j | rtx4d | | Xiaomi Mi Note 2 | scorpio | Onelots | 18.1 |

View Details

23 - Primetime ReleaseHey there! Welcome back!

This last year has been a whirlwind to say the least, but we have remained dedicated to bringingan updated LineageOS based on Android 16 to the masses!

We’ve been hard at work rebasing all of our changes and features since Android 16’s release in June.Android 16’s first release mainly contained iterative improvements and some UI/UX refinements, butdue to our previous efforts adapting to Google’s UI-centric adjustments in Android 12 through 14,we were able to rebase onto Android 16’s code-base faster than anticipated. Yes you read that right:We’re early this year!

Other components have complicated our release and security patching efforts, but we’ll get to thatshortly.

Google’s Patch Cadence, and LineageOS Going ForwardFirstly, what even is an ASB? Or a QPR? ASB (Android Security Bulletin) – Google’s monthly roundup of newly fixed securityvulnerabilities across the Android ecosystem. Distributed as a list of patches and security branchupdates for older but still supported Android versions, with the current version tagged monthly.These updates let projects like ours and OEMs stay aligned with Google’s security baseline. * QPR (Quarterly Platform Release)* – Mid-cycle updates to a given Android version, landing everyfew months. QPRs bring not just security fixes but also bug fixes, performance improvements, andfeature changes (like Material 3 Expressive in 16 QPR1).

Okay, why are you telling me this?You’ll notice we are choosing to release LineageOS 23.0, and not 23.1. That’s because it’s based onAndroid 16’s initial release (what we’ll call QPR0), even though QPR1 has already rolled out toPixels. The catch? Google never pushed QPR1’s source to AOSP. They’ve said it’ll come “in the comingweeks” (source),but right now only contracted partners have access. And to answer the immediate question, thelikelihood that any custom ROM will ever be a contracted Google partner is near 0.

On top of that, Google’s handling of ASBs has shifted (source). July was empty for the first time since theprogram began, August had a single patch, and September omitted patches for several listedvulnerabilities, with fixes shared privately to partners under embargo. The result is that AOSPsecurity updates are no longer released in full on a monthly basis. Instead, only vulnerabilities deemed “high risk” (i.e. actively exploited in the wild)will be published by Google in the monthly ASBs, and even then, the underlying patches are often notmade public immediately.

On a quarterly cadence, Google now issues larger security bulletins that include patches forvulnerabilities originally discovered in prior months. These quarterly bulletins coincide with QPRs(Quarterly Platform Releases), which bundles those security fixes together with feature updates,but have so far not been pushed to AOSP at the time of release.

This is why you’ve seen the LineageOS 22.2 security patch level remain reflective of August well into September.

In short: this cadence is now the norm, and we need to adapt.

And I heard that Google stopped pushing Pixel source?Yes, Google has pulled back here too. Pixel kernels are now only offered as history-strippedtarballs, available privately on request, with no device trees, HALs, or configs. Thanks toprojects like CalyxOS, Pixels will likely remain well supported, but they’reno longer guaranteed “day one” devices for LineageOS. Pixel devices are now effectively no easier tosupport than any other OEM’s devices.

In short, this just makes things harder, not impossible.

How does this affect LineageOS? And me?It means we adapt. Instead of waiting indefinitely for QPR1’s source, we’re shipping 23.0 now on“QPR0”, with the publicly available ASB patches applied, and we’ll only attest to a security patchlevel once we have access to all of its fixes. When QPR1 (and future QPRs) eventually land in AOSP,we’ll merge or rebase as appropriate.

This does mean some features (like Material 3 Expressive) aren’t here yet. But it ensures usersget timely builds, the most complete security fixes we can legally access, and a clear path forwardwithout being stuck in limbo.

This will likely be the expected norm for Android 17 and beyond, so expect more .0 releases in thefuture!

TL;DR:* Google no longer pushes monthly tags and patches to AOSP; and most fixes/security patches are nowpushed quarterly, if at all. * Security patch levels may occasionally lag: we only increment them once all patches are public. * LineageOS 23.0 is based on Android 16 “QPR0” because QPR1’s source isn’t public yet. + Because of this some headline features (like Material 3 Expressive) will come later, oncesources drop. * Pixel support continues, but with reduced source access, they’re no longer guaranteed, let aloneon day one.

Legacy DevicesThe bad news extends a bit further here, though it’s less surprising than the earlier sections.

Google’s increased reliance on newereBPF features has made supportingdevices with older Linux kernels increasingly difficult. Android 16 “QPR0” “requires Linux 5.4 andabove, and at the time of writing, the necessary features have only been properly backported as farback as 4.14.

Unfortunately, LineageOS 22.2 still supports many devices running 4.4 and 4.9. As ofnow, no complete backports of the required features exist for these kernels. The silver lining isthat, unlike the massive device loss we saw moving off LineageOS 18.1, these versions could besalvaged if someone were to take on the work of adapting the backports. If you do succeed, pleasereach out to devrel(at)lineageos.org, we’d be happy to review it!

We’re currently targeting only shipping kernels that have 1:1 eBPF backports to make them featureequivalent to Linux 5.4 from here on out to avoid compatibility issues.

Back to the Good Stuff!* Security patches from September 2024 to August 2025 have been merged to LineageOS 20 through 23.0. * SeedVault and Etar have both been updated to their newest respective upstream version, withmultiple fixes having been sent back to the relevant upstream repos! * WebView has been updated to Chromium 140.0.7339.51. * Contributor demon000 (Cosmin Tanislav) has started work on an awesome set of tools to assistmaintainers in device bringups from scratch! They’re still in-progress, but are staged to make alot of our efforts significantly easier and more streamlined - so stay tuned! Maybe a rarenon-yearly blog post? ;) * Contributor 0xCAFEBABE has extended support for various VirtIO configurations(QEMU/crosvm/UTM/libvirt, etc.) targets! Though these aren’t supported officially, there is anawesome, comprehensive guide for building and utilizing these targets onthe Wiki. There is even a newer one allowing you to runLineageOS in a UTM virtual machine on anApple Silicon Mac! * Contributor 0xCAFEBABE has added support for Cuttlefish targets! * Contributor 0xCAFEBABE has extended support for devices booting Android on the mainline Linuxkernel! This will allow us to in theory boot LineageOS on almost all devices supported by theLinux kernel. It’s in early phases, but very promising, with several successful device portsalready available on the LineageOS GitHub organization! Check the search term “mainline” on theorganization’s search bar. * LineageOS is now nearly Android.mk free! Googleannounced their move from make tosoong many years ago, pushing developers to migrate from Android.mk to Android.bp, and hasstarted blocking Android.mk in many locations of the source tree. + While converting these is a seemingly simple task - in practice it involved countless hours ofconverting conditional checks, regression testing, and thousands of individual patches. As ofthis writing, LineageOS introduces less than 10 Android.mk files at a platform level,and many of these are in the process of being converted. In short - we’re ready for when Googlekills support for Android.mk. + 0xCAFEBABE also created a build target for converting frommk to bp, a WIP feature toassist developers in migrating to soong! * Both the Charging Control, and Fast Charge Control features have received many updates andimprovements. * A new set of ringtones and alarms from Plasma Mobile have been included.

Application UpdatesLineageOS isn’t just about the OS itself: our suite of core apps continues to evolve as well. Thiscycle brings some major improvements:

Aperture (Camera)Our camera app, Aperture, has been rewritten from the ground up. The rewrite makes the app mucheasier to maintain, while also bringing new features:

• Support for JPEG Ultra HDR, RAW, and simultaneous RAW+JPEG capture.
• A redesigned notification island with dynamic colors, and new indicators (JPEG Ultra HDR, RAW,battery, thermal throttling).

Keep your system updated (or keep updating the app if you’re using the app standalone), since weplan to introduce more features and improvements over time (believe it or not, nowadays the onlyobstacle is Google’s CameraX library, which has slowed down the development of certain componentswhich we use in Aperture). We do have some plansto overcome this though.

Twelve (Music Player)Our music player, Twelve, didn’t need a full overhaul this year, but it did get some polish andsome new features:

• Added a “Play random songs” button for quicker library playback.
• Updated the Now Playing screen with playback statistics (for the nerds and audiophiles outthere).
• Added the ability to rescan the local media store, so newly added music shows up withoutneeding a reboot.
• Expanded Jellyfin integration, including suggestions, favorites, and better thumbnailhandling.
• Added MIDI playback support.

New App, Again?We’re excited to debut Catapult, our brand-new custom launcher for Android TV. Catapult is builtwith the same principles we bring to the rest of LineageOS: clean, simple, functional design, withthoughtful user experience at its core.

Why build a new launcher? For years, Android TV and Google TV users have been stuck with preloadedlaunchers that aggressively push advertising and recommendations users can’t control. Catapultchanges that. It strips away the clutter, gives you back your home screen, and lets you decide whatbelongs front and center.

With Catapult, you get a fast, intuitive interface that focuses on your apps and your content:no forced feeds, no “sponsored” rows, just a launcher that works the way you expect.

We’re also planning to add more features in the future, you’ll see them appear as you keep yourdevice up to date, stay tuned!

Extended QEMU-Based Virtual Machine SupportLineageOS has long been a favorite for developers and tinkerers, and with 23.0 we’ve expandedsupport for virtualized environments. Thanks to extended QEMU integration spearheaded by developer0xCAFEBABE, it’s now easier than ever to run LineageOS in VMs for testing, debugging, or justexploration. This means developers can spin up consistent environments on their desktops withoutneeding dedicated hardware, and testers can reproduce tricky issues with greater reliability.Whether you’re validating patches or just curious to see how LineageOS runs under the hood, thetooling is smoother and more accessible.

If interested, take a look on the Wiki. You can runLineageOS via libvirt on Linux/Windows, and on anApple Silicon Mac with UTM.

Additionally, LineageOS now supports Cuttlefishbuild configurations, which are similar to the emulator family of targets, but has extraemulated peripherals, so as to act more like a real device! You can view a list of all the differenceshere.

Mainline Kernel SupportAnother big milestone in 23.0 is our improved support for devices running Linux mainline kernels.

While Android has historically relied on heavily modified vendor kernels, the ecosystem is shiftingtoward mainline for long-term stability and maintainability.

With 23.0, developer 0xCAFEBABE has spearheaded an effort to extend compatibility for devicescapable of booting the mainline Linux kernel, and we’ve made it easier for maintainers to bringtheir devices closer to upstream with inheritable common trees. The end result? For now, nothing,but in the future, we will hopefully be able to boot Android on almost any device that issupported by the mainline Linux kernel.

This effort should help keep devices alive well past the point where their proprietary componentsstop working with newer Android releases.

See the following repos if interested! (1,2,3,4)

Careful CommonizationSeveral of our developers have worked hard on SoC-specific common kernels to base on that can bemerged on a somewhat regular basis to pull in the latest features/security patches to savemaintainers additional effort.

Go check them out and consider basing your device kernels on them!

Supported SoCs right now are:

| SoC (system-on-chip) | Kernel Version | Android Version | | --- | --- | --- | | Qualcomm MSM8998/MSM8996 | 4.4 | 13, 14, 15 | | Qualcomm MSM8953 | 4.9 | 13, 14, 15 | | Qualcomm SDM845 | 4.9 | 13, 14, 15 | | Qualcomm SM8150 | 4.14 | 13, 14, 15, 16 | | Qualcomm SDM660 | 4.19 | 13, 14, 15, 16 | | Qualcomm SM8250 | 4.19 | 13, 14, 15, 16 | | Qualcomm SM8350 | 5.4 | 13, 14, 15, 16 | | Qualcomm SM8450 | 5.10 | 13, 14, 15, 16 | | Qualcomm SM8550 | 5.15 | 13, 14, 15, 16 | | Qualcomm SM8650 | 6.1 | 14, 15, 16 | | Qualcomm SM8750 | 6.6 | 15, 16 |

Moreover, many legacy devices require interpolating libraries that we colloquially refer to as“shims” - these have long been device and maintainer managed, but this cycle we have decided tocommonize them to make the effort easier on everyone and not duplicate effort!

You can check it out here andcontribute shims that you think other devices may need or add additional components to additionalshims and compatibility layers provided via Gerrit!

DeprecationsOverall, we feel that the 23.0 branch has reached feature and stability parity with 22.2 and isready for initial release.

We will allow new LineageOS 21 submissions to be forked to the organization, but we will no longerallow newly submitted LineageOS 21 devices to ship.

LineageOS 23.0 will launch building for a decent selection of devices, with additional devices tocome as they meet the requirements specified by theCharter and aremade ready for builds by their maintainer.

Upgrading to LineageOS 23.0To upgrade, please follow the upgrade guide for your device by clicking on it here and then on “Upgrade to a higher version of LineageOS”.

If you’re coming from an unofficial build, you need to follow the good ole’ install guide for yourdevice, just like anyone else looking toinstall LineageOS for the first time. These can be found at the same placehere by clicking on your device and then on “Installation”.

Please note that if you’re currently on an official build, you DO NOT need to wipe your device,unless your device’s wiki page specifically dictates otherwise, as is needed for some devices withmassive changes, such as a repartition.

Download portalWhile it has been in the making for quite a while and already released two years ago, it’s stillrelevant to this blog post.Our download portal has been redesigned and gained a fewfunctional improvements:

• Dark mode
• Downloads of additional images (shown for all devices but not used on all of them, read theinstructions to know which ones you need for your device’s installation!)
• Verifying downloaded files (see here) - if you go withany download not obtained from us, you can still verify it was originally signed by us and thusuntampered with

A reminder: Follow the LineageOS Wiki to the letter! If an image islisted on the download portal that the wiki doesn’t ask you to use, ignore it! It is likely thereso the maintainer can point power-users at it if needed.

WikiThe LineageOS Wiki has also been expanded over the years and nowoffers, in addition to the known and tested instructions for all supported devices, someimprovements:

• The device overview allows filtering for various attributes you might be interested in a device(please note that choosing a device only based on that list still does not guarantee any devicesupport beyond the point of when you chose it)
• The device overview now lists variants of a device and other known marketing names in a morevisible way, also allowing for different device information and instructions per variant to beshown
• The installation instructions have been paginated, giving users less chance to skip a sectioninvoluntarily

In addition to that we’d like to take this time to remind users to follow instructions on theirdevice’s respective Wiki Pagegiven the complexity introduced by AOSP changes like System-As-Root, A/B Partition Scheme, DynamicPartitions, and most recently Virtual A/Bfound on the Pixel 5 and other devices launching with Android 11, the instructions many of you areused to following from memory are either no longer valid or are missing very critical steps.As of 16.0, maintainers have been expected to run through the full instructions and verify theywork on their devices. The LineageOS Wiki was recently further extended, andmaintainers were given significantly more options to customize their device’s specificinstallation, update, and upgrade instructions.

Developers, Developers, DevelopersOr, in this case, maintainers, maintainers, maintainers. We want your device submissions!

If you’re a developer and would like to submit your device for officials, it’s easier than ever.Just follow the instructions here.

The above also applies to people looking to bring back devices that were at one point official butare no longer supported - seriously - even if it’s not yet completely compliant, submit it! Maybewe can help you complete it.

After you submit, within generally a few weeks, but in most cases a week, you’ll receive somefeedback on your device submission; and if it’s up to par, you’ll be invited to our communicationsinstances and your device will be forked to LineageOS’s official repositories.

Don’t have the knowledge to maintain a device, but want to contribute to the platform? We have lotsof other things you can contribute to.For instance, our apps suite is always looking for new people to helpimprove them, or you cancontribute to the wiki by addingmore useful information & documentation.Gerrit is always open for submissions! Onceyou’ve contributed a few things, send an email to devrel(at)lineageos.org detailing them, and we’llget you in the loop.

Also, if you sent a submission that didn’t get a response in the last few months, please follow up,we’ve swapped providers again!

Generic TargetsWe’ve talked about these before, but these are important, so we will cover them again.

Although we’ve had buildable generic targets since 2019, to make LineageOS more accessible todevelopers, and really anyone interested in giving LineageOS a try, we’ve documented how to usethem in conjunction with the AndroidEmulator/Android Studio!

Additionally, similar targets can now be used to build GSI in mobile, Android TV configurations,and Android Automotive making LineageOS more accessible than ever todevices using Google’sProject Treble.We won’t be providing official builds for these targets, due to the fact the user experience variesentirely based on how well the device manufacturer complied with Treble’s requirements, but feelfree to go build them yourself and give it a shot!

Please note that Android 12 (and by proxy all later Android versions) diverged GSI and Emulatortargets. Emulator targets reside in lineage_sdk_$arch, while GSI targets reside inlineage_gsi_$arch.

Additionally, experimental targets now exist for QEMU-based virtual machine software (libvirt,UTM, etc). Instructions on building and utilizing these targets can be found onthe Wiki.

TranslationsBilingual? Trilingual? Anything-lingual?

If you think you can help translate LineageOS to a different language, jump over toour wiki and have a go!If your language is not supported natively in Android, reach out to us on Crowdin and we’ll takethe necessarysteps to include your language.For instance, LineageOS is the first Android custom distribution that has complete supportfor the Welsh (Cymraeg) language thanks to its community of translators.

Please, contribute to translations only if you are reasonably literate in the target language;poor translations waste both our time and yours.

Build rosterAdded 23 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | F(x)tec Pro¹ X | pro1x | BadDaemon, bgcngm, mccreary, npjohnson, qsnc, tdm | 22.2 | | Fairphone 4 | FP4 | mikeioannina | 22.2 | | Fairphone 5 | FP5 | mikeioannina | 22.2 | | Google Pixel 4a 5G | bramble | mikeioannina | 22.2 | | Google Pixel 5 | redfin | mikeioannina | 22.2 | | Google Pixel 5a | barbet | mikeioannina | 22.2 | | Lenovo Z5 Pro GT | heart | themard, optionaltoast | 22.2 | | Lenovo Z6 Pro | zippo | Lucchetto, themard, einargednochsson | 22.2 | | Motorola defy 2021 | bathena | Deivid Ignacio Parra, Francisco Sanchez | 22.2 | | Motorola edge 20 | berlin | npjohnson, SGCMarkus | 22.2 | | Motorola edge 2021 | berlna | SyberHexen | 22.2 | | Motorola edge 30 fusion | tundra | themard, electimon | 22.2 | | Motorola edge 30 neo | miami | marcost2 | 22.2 | | Motorola edge 30 | dubai | themard, sb6596, Demon000 | 22.2 | | Motorola edge 40 pro / Motorola moto X40 / Motorola edge+ (2023) | rtwo | sgcmarkus, themard | 22.2 | | Motorola moto e7 plus / Lenovo K12 | guam | Rajin Gangadharan, Deivid Ignacio Parra | 22.2 | | Motorola moto g 5G - 2024 | fogo | mikeioannina | 22.2 | | Motorola moto g power 2021 | borneo | Syed Fawwaz Hussain (Fazwalrus), Deivid Ignacio Parra | 22.2 | | Motorola moto g stylus 5G (2022) | milanf | AnierinBliss | 22.2 | | Motorola moto g stylus 5G | denver | Vivekachooz | 22.2 | | Motorola moto g10 / Motorola moto g10 power / Lenovo K13 Note | capri | Deivid Ignacio Parra, Sultanahamer | 22.2 | | Motorola moto g200 5G / Motorola Edge S30 | xpeng | themard, rogers2602 | 22.2 | | Motorola moto g30 / Lenovo K13 Pro | caprip | mikeioannina | 22.2 | | Motorola moto g32 | devon | Dhina17, mikeioannina | 22.2 | | Motorola moto g34 5G / Motorola moto g45 5G | fogos | mikeioannina | 22.2 | | Motorola moto g42 | hawao | Dhina17, mikeioannina | 22.2 | | Motorola moto g52 | rhode | Dhina17, mikeioannina, tomoms | 22.2 | | Motorola moto g82 5G | rhodep | AnandSuresh02, sevenrock | 22.2 | | Motorola moto g84 5G | bangkk | mikeioannina | 22.2 | | Motorola moto g9 play / Motorola moto g9 / Lenovo K12 Note | guamp | DelightReza, Deivid Ignacio Parra | 22.2 | | Motorola moto g9 power / Lenovo K12 Pro | cebu | Deivid Ignacio Parra | 22.2 | | Nothing Phone (2) | Pong | chandu078 | 22.2 | | Nubia Mini 5G | TP1803 | ArianK16a, npjohnson | 22.2 | | OnePlus 11 5G | salami | bgcngm | 22.2 | | OnePlus 12R | aston | inferno0230 | 22.2 | | OnePlus 7 Pro / OnePlus 7 Pro (T-Mobile) | guacamole | LuK1337, Tortel | 22.2 | | OnePlus 7 | guacamoleb | shantanu-sarkar | 22.2 | | OnePlus 7T / OnePlus 7T (T-Mobile) | hotdogb | LuK1337 | 22.2 | | OnePlus 7T Pro | hotdog | qsnc | 22.2 | | OnePlus 8 / OnePlus 8 (T-Mobile) | instantnoodle | jabashque | 22.2 | | OnePlus 8 Pro | instantnoodlep | LuK1337 | 22.2 | | OnePlus 8T / OnePlus 8T (T-Mobile) | kebab | LuK1337, mikeioannina | 22.2 | | OnePlus 9 / OnePlus 9 (T-Mobile) | lemonade | mikeioannina, tangalbert919, ZVNexus | 22.2 | | OnePlus 9 Pro / OnePlus 9 Pro (T-Mobile) | lemonadep | LuK1337, bgcngm, mikeioannina | 22.2 | | OnePlus 9R | lemonades | mikeioannina | 22.2 | | OnePlus 9RT | martini | mikeioannina, basamaryan | 22.2 | | OnePlus Nord CE 2 Lite 5G | oscaro | Vivekachooz | 22.2 | | OnePlus Nord CE 3 Lite 5G / OnePlus Nord N30 5G | larry | Vivekachooz | 22.2 | | OnePlus Nord CE4 | benz | inferno0230 | 22.2 | | OnePlus Pad 2 Pro / OnePlus Pad 3 | erhai | LuK1337, bgcngm | 22.2 | | Realme 10 Pro 5G | luigi | Vivekachooz | 22.2 | | Realme 9 Pro 5G / Realme 9 5G / Realme Q5 | oscar | Vivekachooz | 22.2 | | Samsung Galaxy A21s | a21s | DaemonMCR | 22.2 | | Samsung Galaxy F62 / Samsung Galaxy M62 | f62 | Linux4 | 22.2 | | Samsung Galaxy Note10 5G | d1x | Rocky7842, Linux4 | 22.2 | | Samsung Galaxy Note10 | d1 | Linux4 | 22.2 | | Samsung Galaxy Note10+ 5G | d2x | Linux4 | 22.2 | | Samsung Galaxy Note10+ | d2s | Linux4 | 22.2 | | Samsung Galaxy S10 5G | beyondx | Linux4 | 22.2 | | Samsung Galaxy S10 | beyond1lte | Linux4 | 22.2 | | Samsung Galaxy S10+ | beyond2lte | Linux4 | 22.2 | | Samsung Galaxy S10e | beyond0lte | Linux4 | 22.2 | | Samsung Galaxy S20 FE / Samsung Galaxy S20 FE 5G | r8q | ata-kaner | 22.2 | | Samsung Galaxy Tab A7 10.4 2020 (LTE) | gta4l | chrmhoffmann | 22.2 | | Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) | gta4lwifi | chrmhoffmann | 22.2 | | Samsung Galaxy Tab S6 Lite (LTE) | gta4xl | haggertk, Linux4 | 22.2 | | Samsung Galaxy Tab S6 Lite (Wi-Fi) | gta4xlwifi | Linux4, haggertk | 22.2 | | Samsung Galaxy Tab S7 (LTE) | gts7l | bgcngm | 22.2 | | Samsung Galaxy Tab S7 (Wi-Fi) | gts7lwifi | bgcngm | 22.2 | | Solana Saga | ingot | mikeioannina, npjohnson, tomoms | 22.2 | | Sony Xperia 1 II | pdx203 | hellobbn | 22.2 | | Sony Xperia 1 III | pdx215 | hellobbn | 22.2 | | Sony Xperia 1 V | pdx234 | hellobbn | 22.2 | | Sony Xperia 10 IV | pdx225 | LuK1337, jmpfbmx | 22.2 | | Sony Xperia 10 Plus | mermaid | LuK1337 | 22.2 | | Sony Xperia 10 V | pdx235 | jmpfbmx, LuK1337 | 22.2 | | Sony Xperia 10 | kirin | LuK1337 | 22.2 | | Sony Xperia 5 II | pdx206 | kyasu, hellobbn | 22.2 | | Sony Xperia 5 III | pdx214 | kyasu, hellobbn | 22.2 | | Sony Xperia 5 V | pdx237 | kyasu, hellobbn | 22.2 | | Sony Xperia XA2 Plus | voyager | LuK1337 | 22.2 | | Sony Xperia XA2 Ultra | discovery | LuK1337 | 22.2 | | Sony Xperia XA2 | pioneer | LuK1337, jmpfbmx | 22.2 | | Xiaomi 12 Pro | zeus | Adrianyyy, ArianK16a | 22.2 | | Xiaomi 12 | cupid | Adrianyyy, ArianK16a | 22.2 | | Xiaomi 12S Pro | unicorn | Adrianyyy, ArianK16a | 22.2 | | Xiaomi 12S Ultra | thor | Adrianyyy, ArianK16a | 22.2 | | Xiaomi 12S | mayfly | Flower Sea | 22.2 | | Xiaomi 12T Pro / Xiaomi Redmi K50 Ultra | diting | Adrianyyy, ArianK16a | 22.2 | | Xiaomi 13 Pro | nuwa | Minus | 22.2 | | Xiaomi 13 | fuxi | lolipuru | 22.2 | | Xiaomi Mi 9T / Xiaomi Redmi K20 (China) / Xiaomi Redmi K20 (India) | davinci | ArianK16a | 22.2 | | Xiaomi Mi A3 | laurel_sprout | Skyblueborb | 22.2 | | Xiaomi POCO F5 (Global) / Xiaomi POCO F5 (India) / Xiaomi Redmi Note 12 Turbo | marble | Adrianyyy, ArianK16a | 22.2 | | Xiaomi POCO F5 Pro / Xiaomi Redmi K60 | mondrian | Adrianyyy, ArianK16a | 22.2 | | Xiaomi Redmi 12C / Xiaomi Redmi 12C NFC / Xiaomi POCO C55 | earth | surblazer | 22.2 | | Xiaomi Redmi 3S / Xiaomi Redmi 3X / Xiaomi Redmi 4 (India) / Xiaomi Redmi 4X / Xiaomi Redmi Note 5A Prime / Xiaomi Redmi Y1 Prime | Mi8937 | 0xCAFEBABE | 22.2 | | Xiaomi Redmi 4A / Xiaomi Redmi 5A / Xiaomi Redmi Note 5A Lite / Xiaomi Redmi Y1 Lite | Mi8917 | 0xCAFEBABE | 22.2 | | Xiaomi Redmi 7A / Xiaomi Redmi 8 / Xiaomi Redmi 8A / Xiaomi Redmi 8A Dual | Mi439 | 0xCAFEBABE | 22.2 | | Xiaomi Redmi K60 Pro | socrates | WenHao2130 | 22.2 | | Xiaomi Redmi Note 10 Pro / Xiaomi Redmi Note 10 Pro (India) / Xiaomi Redmi Note 10 Pro Max (India) | sweet | basamaryan, danielml3 | 22.2 | | Xiaomi Redmi Note 10S / Xiaomi Redmi Note 10S NFC / Xiaomi Redmi Note 10S Latin America / Xiaomi POCO M5s | rosemary | surblazer | 22.2 | | Xiaomi Redmi Note 7 Pro | violet | 0xCAFEBABE | 22.2 | | Xiaomi Redmi Note 8 / Xiaomi Redmi Note 8T | ginkgo | Skyblueborb, mikeioannina, programminghoch10 | 22.2 |

Added 22.2 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | ASUS ZenFone 8 | sake | DD3Boh, mikooomich | 20 | | ASUS Zenfone 5Z (ZS620KL) | Z01R | ThEMarD | 22.1 | | LG Style3 | style3lm | rtx4d | | LG Velvet | caymanslm | rtx4d | | Motorola moto g 5G / Motorola moto one 5G ace | kiev | basamaryan, Jleeblanch, SyberHexen, Vivekachooz | 22.1 | | Motorola moto g 5G plus / Motorola moto one 5G | nairo | ItsVixano, Ivanmeler, SyberHexen, zlewchan | 22.1 | | Nokia 6.1 (2018) | PL2 | npjohnson | 22.1 | | Nokia 7 plus | B2N | Tuan Anh | | Nokia 8 | NB1 | Tuan Anh | 21 | | Nothing Phone (1) | Spacewar | zlewchan, ko_ko_konb | 22.1 | | Nubia Red Magic 5G (Global) / Nubia Red Magic 5G (China) / Nubia Red Magic 5S (Global) / Nubia Red Magic 5S (China) | nx659j | zlewchan | 20 | | Nubia Red Magic Mars | nx619j | Cyborg2017, rtx4d | 22.1 | | Nubia Z17 | nx563j | BeYkeRYkt | 21 | | Nubia Z18 | nx606j | Cyborg2017, rtx4d | 22.1 | | OnePlus 12 | waffle | chandu078 | | OnePlus 5 | cheeseburger | qsnc | 22.1 | | OnePlus 5T | dumpling | qsnc | 22.1 | | OnePlus Nord N20 | gunnar | tangalbert919 | | OnePlus Nord N200 | dre | tangalbert919 | 21 | | Samsung Galaxy A52 4G | a52q | Simon1511 | 22.1 | | Samsung Galaxy A52s 5G | a52sxq | Simon1511 | 22.1 | | Samsung Galaxy A72 | a72q | Simon1511 | 22.1 | | Samsung Galaxy A73 5G | a73xq | Simon1511 | 22.1 | | Samsung Galaxy M52 5G | m52xq | Simon1511 | 22.1 | | Samsung Galaxy Tab A 8.0 (2019) | gtowifi | lifehackerhansol | 21 | | Vsmart Joy 3 / Vsmart Joy 3+ | casuarina | Tuan Anh, nhglong | | Xiaomi Black Shark | shark | rtx4d, tdrkDev | 22.1 | | Xiaomi MIX Fold 2 | zizhan | Adrianyyy, ArianK16a | | Xiaomi Mi 11i / Xiaomi Redmi K40 Pro / Xiaomi Redmi K40 Pro+ / Xiaomi Mi 11X Pro | haydn | ikeramat | 22.1 | | Xiaomi Mi 8 Explorer Edition | ursa | bgcngm | 22.1 | | Xiaomi Mi 8 Pro | equuleus | bgcngm | 22.1 | | Xiaomi Mi 8 | dipper | infrag | 22.1 | | Xiaomi Mi MIX 2S | polaris | bgcngm | 22.1 | | Xiaomi Mi MIX 3 | perseus | bgcngm, rtx4d | 22.1 | | Xiaomi Mi Note 10 / Xiaomi Mi Note 10 Pro / Xiaomi Mi CC9 Pro | tucana | SanyaPilot | | Xiaomi POCO F1 | beryllium | bgcngm, warabhishek | 22.1 | | Xiaomi POCO X3 NFC | surya | Shimitar, TheStrechh, ikeramat | 21 | | Xiaomi POCO X3 Pro | vayu | SebaUbuntu | 20 | | ZTE Axon 9 Pro | akershus | rtx4d, tdrkDev |

View Details

22 - Cheers to the Next Level!Hey there! Welcome back!

This year, we’re running way ahead of schedule, thanks to a boost in contributors, reinvigorated passion of others, and the new project leads joining the fold.

We’ve been hard at work since Android 15’s release in September, adapting our unique features to this new version of Android. Android 15 introduced several complex changes under the hood, but due to our previous efforts adapting to Google’s UI-centric adjustments in Android 12 through 14, we were able to rebase onto Android 15’s code-base faster than anticipated.

Additionally, this is far-and-away the easiest bringup cycle from a device perspective we have seen in years. This means that many more devices are ready on day one that we’d typically expect to have up this early in the cycle!

Last, but not least, we even had enough time and resources to introduce not one, but two newexciting apps! The first one, Twelve, will replace our aging music app, while the other one,Camelot, will let you view PDF files.

Versioning RemindersAs always, while we’re aligned with AOSP’s versioning, but Android’s move to trunk-based development, and the subsequent growth in size of Android’s QPRs (Quarterly Platform Releases) have made our job magnitudes harder! As a byproduct we must rebase our entire code-base every 3 months. Sadly, Google also has a habit of introducing deprecations or outright removing code that older devices rely on with little advanced notice during these. Since these older devices may lose support mid-cycle, we have opted to restore the dot versioning to our branding. This launch will be LineageOS 22.1, incrementing that sub-version every QPR by .1, so expect to see 22.2 as well.

Going forward, this aligns well with Google’s newly introduced concept of minor SDK releases. Now, you’ll be able to distinguish the minor version of Android you’re installing. Assuming the 25Q4 release is Android 16 QPR2, it should correspond to LineageOS 23.2, and so on.

Additionally, maintainers will also be expected to check-in at each QPR to assure that their device still functions will all the changes carried. Don’t be disheartened if your device falls out of support during a QPR, it may just take some time to bring it up to par!

Welcome to LineageOS 22.1, based on Android 15 QPR1. Enjoy the new features, and, as always, happy flashing!

New Features!* Security patches from March 2024 to November 2024 have been merged to LineageOS 19.1 through 22.1. * SeedVault and Etar have both been updated to their newest respective upstream version. * WebView has been updated to Chromium 131.0.6778.200. * Contributor demon000 (Cosmin Tanislav) has reworked our extract utilities, heavily optimizing them. He was able to optimize most devices down from ~180 seconds to extract, all the way down to roughly ~30 seconds. + He also rewrote our extract utilities from scratch in Python, making them far more extensible, and even faster, clocking in closer to 6 seconds! A 30x speed improvement! Maintainers can swap to this implementation at their leisure throughout this cycle. * Contributor 0xCAFEBABE also added support for virtIO (QEMU/crosvm/UTM, etc.) targets! Though these aren’t supported officially, there is an awesome, comprehensive guide for building and utilizing these targets on the Wiki.

New App?Our default music app, Eleven, has been included since CyanogenMod 12.1, making it one of the oldestapps in the LineageOS apps suite. Unfortunately, as you might have noticed, it has been neglectedfor quite some time. Given its age, its codebase was also old and not compliant with modernAndroid’s guidelines.

So, we took the opportunity to replace it with a new music app, Twelve. Is this yet another musicapp? Yeah, it is, but we promise we made sure to provide a nice out-of-the-box experience forLineageOS users that aren’t looking for more advanced alternatives. It will be available startingfrom LineageOS 22.1 and onwards.

Twelve includes all the features you’re used to from Eleven, plus:

• A modern Material You design
• Proper landscape and tablets experience
• Support for most of the existing music library server protocols
  • Subsonic
  • OpenSubsonic (Ampache, Navidrome, Nextcloud Music, etc.)
  • Jellyfin
• Support for streaming protocols like HLS, DASH, and SmoothStreaming
• Improved search
• Improved Android Auto support
• Playback resumption support (either from a device reboot or a new Bluetooth connection)
• More Visualizer presets
• Skip silence option

We’re also planning to add more features in the future, you’ll see them appear as you keep yourdevice up to date, stay tuned!

Another new app!?Yes, you’ve heard that right, despite being less interesting than Twelve.

Starting from LineageOS 22.1, the OS will bundle a native reader app for PDF files which,surprisingly, Jelly (our browser app) and WebViews cannot handle (for now).

The app uses the same Jetpack PDF library used on recent Google Chrome and Files by Google releases,so there’s really nothing outstanding to mention about it: it’s just a simple PDF reader, have funreading your very important documents!

Careful CommonizationSeveral of our developers have worked hard on SoC-specific common kernels to base on that can be merged on a somewhat regular basis to pull in the latest features/security patches to save maintainers additional effort.

Go check them out and consider basing your device kernels on them!

Supported SoCs right now are:

| SoC (system-on-chip) | Kernel Version | Android Version | | --- | --- | --- | | Qualcomm MSM8998/MSM8996 | 4.4 | 13, 14, 15 | | Qualcomm MSM8953 | 4.9 | 13, 14, 15 | | Qualcomm SDM845 | 4.9 | 13, 14, 15 | | Qualcomm SM8150 | 4.14 | 13, 14, 15 | | Qualcomm SDM660 | 4.19 | 13, 14, 15 | | Qualcomm SM8250 | 4.19 | 13, 14, 15 | | Qualcomm SM8350 | 5.4 | 13, 14, 15 | | Qualcomm SM8450 | 5.10 | 13, 14, 15 | | Qualcomm SM8550 | 5.15 | 13, 14, 15 |

Additionally, many legacy devices require interpolating libraries that we colloquially refer to as “shims” - these have long been device and maintainer managed, but this cycle we have decided to commonize them to make the effort easier on everyone and not duplicate effort!

You can check it out here and contribute shims that you think other devices may need or add additional components to additional shims and compatibility layers provided via Gerrit!

DeprecationsOverall, we feel that the 22.1 branch has reached feature and stability parity with 21 and is ready for initial release.

We will allow new LineageOS 20 submissions to be forked to the organization, but we no longer will allow newly submitted LineageOS 20 devices to ship.

LineageOS 22.1 will launch building for a decent selection of devices, with additional devices to come as they are marked as bothCharter compliant and ready for builds by their maintainer.

Upgrading to LineageOS 22.1To upgrade, please follow the upgrade guide for your device by clicking on it here and then on “Upgrade to a higher version of LineageOS”.

If you’re coming from an unofficial build, you need to follow the good ole’ install guide for your device, just like anyone else looking toinstall LineageOS for the first time. These can be found at the same place here by clicking on your device and then on “Installation”.

Please note that if you’re currently on an official build, you DO NOT need to wipe your device, unless your device’s wiki page specifically dictates otherwise, as is needed for some devices with massivechanges, such as a repartition.

Download portalWhile it has been in the making for quite a while and already released a year ago, it’s still relevant to this blog post.Our download portal has been redesigned and gained a few functional improvements:

• Dark mode
• Downloads of additional images (shown for all devices but not used on all of them, read the instructions to know which ones you need for your device’s installation!)
• Verifying downloaded files (see here) - if you go with any download not obtained from us, you can still verify it was originallysigned by us and thus untampered with

A reminder: Follow the LineageOS Wiki to the letter! If an image is listed on the download portal that the wiki doesn’t ask you to use, ignore it! It is likely there so the maintainer can point power-users at it if needed.

WikiThe LineageOS Wiki has also been expanded throughout the year and now offers, in addition to the known and tested instructions for all supported devices, some improvements:

• The device overview allows filtering for various attributes you might be interested in a device (please note that choosing a device only based on that list still doesnot guarantee any device support beyond the point of when you chose it)
• The device overview now lists variants of a device and other known marketing names in a more visible way, also allowing for different device information and instructions per variant to be shown
• The installation instructions have been paginated, giving users less chance to skip a section involuntarily

In addition to that we’d like to take this time to remind users to follow instructions on their device’s respective Wiki Pagegiven the complexity introduced by AOSP changes like System-As-Root, A/B Partition Scheme, Dynamic Partitions, and most recently Virtual A/Bfound on the Pixel 5 and other devices launching with Android 11, the instructions many of you are used to following from memory are either no longer valid or are missing very critical steps.As of 16.0, maintainers have been expected to run through the full instructions and verify they work on their devices. The LineageOS Wiki was recently further extended, andmaintainers were given significantly more options to customize their device’s specific installation, update, and upgrade instructions.

Developers, Developers, DevelopersOr, in this case, maintainers, maintainers, maintainers. We want your device submissions!

If you’re a developer and would like to submit your device for officials, it’s easier than ever. Just follow the instructions here.

The above also applies to people looking to bring back devices that were at one point official but are no longer supported - seriously - even if it’s not yet completely compliant, submit it! Maybe we can help you complete it.

After you submit, within generally a few weeks, but in most cases a week, you’ll receive some feedback on your device submission; and if it’s up to par, you’ll be invited to our communicationsinstances and your device will be forked to LineageOS’s official repositories.

Don’t have the knowledge to maintain a device, but want to contribute to the platform? We have lots of other things you can contribute to.For instance, our apps suite is always looking for new people to help improve them, or you can contribute to the wiki by addingmore useful information & documentation. Gerrit is always open forsubmissions! Once you’ve contributed a few things, send an email to devrel(at)lineageos.org detailing them, and we’ll get you in the loop.

Also, if you sent a submission that didn’t get a response in the last few months, please follow up, we’ve swapped providers again!

Generic TargetsWe’ve talked about these before, but these are important, so we will cover them again.

Though we’ve had buildable generic targets since 2019, to make LineageOS more accessible to developers, and really anyone interested in giving LineageOS a try, we’ve documented how to use them in conjunction with the Android Emulator/Android Studio!

Additionally, similar targets can now be used to build GSI in mobile, Android TV configurations, and Android Automotive making LineageOS more accessible than ever todevices using Google’s Project Treble. We won’t be providingofficial builds for these targets, due to the fact the user experience varies entirely based on how well the device manufacturer complied with Treble’srequirements, but feel free to go build them yourself and give it a shot!

Please note that Android 12 (and by proxy Android 13/14/15) diverged GSI and Emulator targets. Emulator targets reside in lineage_sdk_$arch, while GSI targets reside in lineage_gsi_$arch.

Additionally, an experimental target now exists for virtIO (QEMU/crosvm/UTM, etc.) targets. Instructions on building and utilizing these targets can be found on the Wiki.

TranslationsBilingual? Trilingual? Anything-lingual?

If you think you can help translate LineageOS to a different language, jump over toour wiki and have a go!If your language is not supported natively in Android, reach out to us on Crowdin and we’ll take the necessarysteps to include your language.For instance, LineageOS is the first Android custom distribution that has complete supportfor the Welsh (Cymraeg) language thanks to its community of translators.

Please, contribute to translations only if you are reasonably literate in the target language;poor translations waste both our time and yours.

Build rosterAdded 22.1 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | ASUS Zenfone 5Z (ZS620KL) | Z01R | ThEMarD | 21 | | Banana Pi M5 (Android TV) | m5 | stricted | 21 | | Banana Pi M5 (Tablet) | m5_tab | npjohnson, stricted | 21 | | Dynalink TV Box 4K (2021) | wade | npjohnson, bgcngm, stricted, webgeek1234, deadman96385, trautamaki, luca020400, aleasto | 21 | | Essential PH-1 | mata | haggertk, npjohnson, tomoms | 21 | | F(x)tec Pro¹ X | pro1x | BadDaemon, bgcngm, mccreary, npjohnson, qsnc, tdm | 21 | | F(x)tec Pro¹ | pro1 | BadDaemon, bgcngm, intervigil, mccreary, npjohnson, tdm | 21 | | Fairphone 4 | FP4 | mikeioannina | 21 | | Fairphone 5 | FP5 | mikeioannina | 21 | | Google ADT-3 | deadpool | bgcngm, npjohnson, stricted, webgeek1234, deadman96385, trautamaki, luca020400, aleasto | 21 | | Google Chromecast with Google TV (4K) | sabrina | npjohnson, stricted | 21 | | Google Pixel 2 XL | taimen | chrmhoffmann, Eamo5, npjohnson, jro1979 | 21 | | Google Pixel 2 | walleye | chrmhoffmann, Eamo5, npjohnson, jro1979 | 21 | | Google Pixel 3 XL | crosshatch | mikeioannina, razorloves | 21 | | Google Pixel 3 | blueline | mikeioannina, razorloves | 21 | | Google Pixel 3a XL | bonito | mikeioannina, npjohnson | 21 | | Google Pixel 3a | sargo | mikeioannina, npjohnson | 21 | | Google Pixel 4 XL | coral | Eamo5, mikeioannina, npjohnson | 21 | | Google Pixel 4 | flame | Eamo5, mikeioannina, npjohnson | 21 | | Google Pixel 4a 5G | bramble | mikeioannina | 21 | | Google Pixel 4a | sunfish | mikeioannina | 21 | | Google Pixel 5 | redfin | mikeioannina | 21 | | Google Pixel 5a | barbet | mikeioannina | 21 | | Google Pixel 6 Pro | raven | mikeioannina | 21 | | Google Pixel 6 | oriole | mikeioannina | 21 | | Google Pixel 6a | bluejay | mikeioannina | 21 | | Google Pixel 7 Pro | cheetah | mikeioannina | 21 | | Google Pixel 7 | panther | mikeioannina, neelc | 21 | | Google Pixel 7a | lynx | mikeioannina, niclimcy | 21 | | Google Pixel 8 Pro | husky | mikeioannina | 21 | | Google Pixel 8 | shiba | mikeioannina | 21 | | Google Pixel 8a | akita | mikeioannina | 21 | | Google Pixel 9 Pro Fold | comet | mikeioannina | | Google Pixel 9 Pro XL | komodo | mikeioannina | | Google Pixel 9 Pro | caiman | mikeioannina | | Google Pixel 9 | tokay | mikeioannina | | Google Pixel Fold | felix | mikeioannina | 21 | | Google Pixel Tablet | tangorpro | LuK1337, mikeioannina, neelc, npjohnson | 21 | | Google Pixel XL | marlin | npjohnson, electimon | 21 | | Google Pixel | sailfish | npjohnson, electimon | 21 | | HardKernel ODROID-C4 (Android TV) | odroidc4 | bgcngm, stricted | 21 | | HardKernel ODROID-C4 (Tablet) | odroidc4_tab | bgcngm, npjohnson, stricted | 21 | | Motorola edge 20 pro | pstar | npjohnson, SGCMarkus | 21 | | Motorola edge 20 | berlin | npjohnson, SGCMarkus | 21 | | Motorola edge 2021 | berlna | SyberHexen | 21 | | Motorola edge 30 | dubai | themard, sb6596, Demon000 | 21 | | Motorola edge 40 pro / Motorola moto X40 / Motorola edge+ (2023) | rtwo | sgcmarkus, themard | 21 | | Motorola edge s / Motorola moto g100 | nio | dianlujitao | 21 | | Motorola moto e7 plus | guam | Rajin Gangadharan | 21 | | Motorola moto g power 2021 | borneo | Fazwalrus | 21 | | Motorola moto g200 5G / Motorola Edge S30 | xpeng | themard, rogers2602 | 21 | | Motorola moto g30 | caprip | mikeioannina | 21 | | Motorola moto g32 | devon | Dhina17, mikeioannina | 21 | | Motorola moto g42 | hawao | Dhina17, mikeioannina | 21 | | Motorola moto g52 | rhode | Dhina17, mikeioannina | 21 | | Motorola moto g6 plus | evert | jro1979 | 21 | | Motorola moto g7 play | channel | SyberHexen, deadman96385, erfanoabdi, npjohnson | 21 | | Motorola moto g7 plus | lake | jro1979, npjohnson | 21 | | Motorola moto g7 power | ocean | SyberHexen, erfanoabdi, npjohnson | 21 | | Motorola moto g7 | river | erfanoabdi, npjohnson, SyberHexen | 21 | | Motorola moto g9 / Motorola moto g9 play / Lenovo K12 Note | guamp | DelightReza | 21 | | Motorola moto g9 power / Lenovo K12 Pro | cebu | Deivid Ignacio Parra | 21 | | Motorola moto x4 | payton | erfanoabdi, ThEMarD, electimon | 21 | | Motorola moto z2 force / Motorola moto z (2018) | nash | erfanoabdi, npjohnson, qsnc | 21 | | Motorola moto z3 play | beckham | jro1979 | 21 | | Motorola moto z3 | messi | npjohnson | 21 | | Motorola one action | troika | Stricted, npjohnson | 21 | | Motorola one vision / Motorola p50 | kane | Stricted, npjohnson | 21 | | Nokia 6.1 (2018) | PL2 | npjohnson | 21 | | Nokia 6.1 Plus | DRG | npjohnson | 21 | | Nubia Mini 5G | TP1803 | ArianK16a, npjohnson | 21 | | OnePlus 11 5G | salami | bgcngm | 21 | | OnePlus 5 | cheeseburger | qsnc | 21 | | OnePlus 5T | dumpling | qsnc | 21 | | OnePlus 6 | enchilada | LuK1337 | 21 | | OnePlus 6T | fajita | EdwinMoq | 21 | | OnePlus 7 Pro | guacamole | LuK1337, Tortel | 21 | | OnePlus 7 | guacamoleb | shantanu-sarkar | 21 | | OnePlus 7T Pro | hotdog | qsnc | 21 | | OnePlus 7T | hotdogb | LuK1337 | 21 | | OnePlus 8 Pro | instantnoodlep | LuK1337 | 21 | | OnePlus 8 | instantnoodle | jabashque | 21 | | OnePlus 8T | kebab | LuK1337, mikeioannina | 21 | | OnePlus 9 Pro | lemonadep | LuK1337, bgcngm, mikeioannina | 21 | | OnePlus 9 | lemonade | mikeioannina, tangalbert919, ZVNexus | 21 | | OnePlus 9R | lemonades | mikeioannina | 21 | | OnePlus 9RT | martini | mikeioannina | 21 | | Radxa Zero (Android TV) | radxa0 | bgcngm, npjohnson, stricted | 21 | | Radxa Zero (Tablet) | radxa0_tab | bgcngm, npjohnson, stricted | 21 | | Razer Phone 2 | aura | mikeioannina, npjohnson | 21 | | Razer Phone | cheryl | mikeioannina, npjohnson | 21 | | Realme 10 Pro 5G | luigi | Vivekachooz | 21 | | Realme 9 Pro 5G / Realme 9 5G / Realme Q5 | oscar | Vivekachooz | 21 | | SHIFT SHIFT6mq | axolotl | amartinz, joey, mikeioannina | 21 | | Samsung Galaxy A71 | a71 | Haky86 | 21 | | Samsung Galaxy F62 / Samsung Galaxy M62 | f62 | Linux4 | 21 | | Samsung Galaxy Note10 5G | d1x | Rocky7842, Linux4 | 21 | | Samsung Galaxy Note10 | d1 | Linux4 | 21 | | Samsung Galaxy Note10+ 5G | d2x | Linux4 | 21 | | Samsung Galaxy Note10+ | d2s | Linux4 | 21 | | Samsung Galaxy S10 5G | beyondx | Linux4 | 21 | | Samsung Galaxy S10 | beyond1lte | Linux4 | 21 | | Samsung Galaxy S10+ | beyond2lte | Linux4 | 21 | | Samsung Galaxy S10e | beyond0lte | Linux4 | 21 | | Samsung Galaxy Tab A7 10.4 2020 (LTE) | gta4l | chrmhoffmann | 21 | | Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) | gta4lwifi | chrmhoffmann | 21 | | Samsung Galaxy Tab S5e (LTE) | gts4lv | bgcngm, LuK1337 | 21 | | Samsung Galaxy Tab S5e (Wi-Fi) | gts4lvwifi | LuK1337, bgcngm | 21 | | Samsung Galaxy Tab S6 Lite (LTE) | gta4xl | haggertk, Linux4 | 21 | | Samsung Galaxy Tab S6 Lite (Wi-Fi) | gta4xlwifi | Linux4, haggertk | 21 | | Sony Xperia 1 II | pdx203 | hellobbn | 21 | | Sony Xperia 1 III | pdx215 | hellobbn | 21 | | Sony Xperia 1 V | pdx234 | hellobbn | 21 | | Sony Xperia 10 Plus | mermaid | LuK1337 | 21 | | Sony Xperia 10 | kirin | LuK1337 | 21 | | Sony Xperia 5 II | pdx206 | kyasu, hellobbn | 21 | | Sony Xperia 5 III | pdx214 | kyasu, hellobbn | 21 | | Sony Xperia 5 V | pdx237 | kyasu, hellobbn | 21 | | Sony Xperia XA2 Plus | voyager | LuK1337 | 21 | | Sony Xperia XA2 Ultra | discovery | LuK1337 | 21 | | Sony Xperia XA2 | pioneer | LuK1337, Stricted, cdesai | 21 | | Walmart onn. TV Box 4K (2021) | dopinder | npjohnson, bgcngm, stricted, webgeek1234, deadman96385, trautamaki, luca020400, aleasto | 21 | | Xiaomi Mi 5 | gemini | bgcngm, ikeramat | 21 | | Xiaomi Mi 5s Plus | natrium | LuK1337 | 21 | | Xiaomi Mi 6 | sagit | ArianK16a, Nanhumly | 21 | | Xiaomi Mi 8 Explorer Edition | ursa | bgcngm | 21 | | Xiaomi Mi 8 Pro | equuleus | bgcngm | 21 | | Xiaomi Mi 8 | dipper | infrag | 21 | | Xiaomi Mi MIX 2 | chiron | mikeioannina | 21 | | Xiaomi Mi MIX 2S | polaris | bgcngm | 21 | | Xiaomi Mi MIX 3 | perseus | bgcngm, rtx4d | 21 | | Xiaomi POCO F1 | beryllium | bgcngm, warabhishek | 21 |

Added 21 devices

| Device name | Wiki | Maintainers | Moved from | | --- | --- | --- | --- | | Fairphone 3 / Fairphone 3+ | FP3 | teamb58, dk1978 | 20 | | LG G7 ThinQ (G710AWM/EM/EMW) / LG G7+ ThinQ | judyln | lifehackerhansol | | LG G7 ThinQ (G710N) | g710n | lifehackerhansol | | LG G7 ThinQ (G710ULM/VMX) | g710ulm | lifehackerhansol | | LG V35 ThinQ | judyp | Juleast | | LG V40 ThinQ | judypn | Tuan Anh | | Lenovo Z5 Pro GT | heart | themard, optionaltoast | 20 | | Lenovo Z6 Pro | zippo | Lucchetto, themard, einargednochsson | 20 | | Motorola edge | racer | erfanoabdi, Jleeblanch, SyberHexen, DD3Boh | 20 | | Motorola moto g 5G / Motorola moto one 5G ace | kiev | SyberHexen, Jleeblanch, Vivekachooz | 20 | | Motorola moto g 5G plus / Motorola moto one 5G | nairo | SyberHexen, Ivanmeler | 20 | | NVIDIA Jetson Nano [Android TV] / NVIDIA Jetson Nano 2GB [Android TV] | porg | webgeek1234, npjohnson | 20 | | NVIDIA Jetson Nano [Tablet] / NVIDIA Jetson Nano 2GB [Tablet] | porg_tab | webgeek1234, npjohnson | 20 | | NVIDIA Jetson TX2 [Android TV] / NVIDIA Jetson TX2 NX [Android TV] | quill | webgeek1234 | 20 | | NVIDIA Jetson TX2 [Tablet] / NVIDIA Jetson TX2 NX [Tablet] | quill_tab | webgeek1234 | 20 | | NVIDIA Shield TV (2015 / 2015 Pro / 2017 / 2019 Pro) [Android TV] / NVIDIA Jetson TX1 [Android TV] | foster | webgeek1234, npjohnson | 20 | | NVIDIA Shield TV (2015 / 2015 Pro / 2017 / 2019 Pro) [Tablet] / NVIDIA Jetson TX1 [Tablet] | foster_tab | webgeek1234, npjohnson | 20 | | NVIDIA Shield TV (2019) [Android TV] | sif | webgeek1234, npjohnson | 20 | | Nintendo Switch v1 [Android TV] / Nintendo Switch v2 [Android TV] / Nintendo Switch Lite [Android TV] / Nintendo Switch OLED [Android TV] | nx | makinbacon, npjohnson, webgeek1234 | | Nintendo Switch v1 [Tablet] / Nintendo Switch v2 [Tablet] / Nintendo Switch Lite [Tablet] / Nintendo Switch OLED [Tablet] | nx_tab | makinbacon, npjohnson, webgeek1234 | | Nokia 8 | NB1 | Tuan Anh | | Nubia Red Magic Mars | nx619j | Cyborg2017, rtx4d | 20 | | Nubia Z18 Mini | nx611j | Cyborg2017 | 20 | | Nubia Z18 | nx606j | Cyborg2017, rtx4d | 20 | | OnePlus Nord N10 | billie | danascape | | OnePlus Nord N200 | dre | tangalbert919 | 20 | | Samsung Galaxy A52 4G | a52q | Simon1511 | 20 | | Samsung Galaxy A52s 5G | a52sxq | Simon1511 | 20 | | Samsung Galaxy A72 | a72q | Simon1511 | 20 | | Samsung Galaxy A73 5G | a73xq | Simon1511 | 20 | | Samsung Galaxy M52 5G | m52xq | Simon1511 | 20 | | Samsung Galaxy Tab A 8.0 (2019) | gtowifi | lifehackerhansol | 20 | | Solana Saga | ingot | mikeioannina, npjohnson | | Sony Xperia XZ2 Compact | xz2c | dtrunk90 | 20 | | Sony Xperia XZ2 Premium | aurora | dtrunk90 | 20 | | Sony Xperia XZ2 | akari | dtrunk90 | 20 | | Sony Xperia XZ3 | akatsuki | dtrunk90 | 20 | | Xiaomi 11 Lite 5G NE / Xiaomi 11 Lite NE 5G / Xiaomi Mi 11 LE | lisa | ItsVixano | 20 | | Xiaomi Black Shark | shark | rtx4d, tdrkDev | | Xiaomi Mi 10 Pro | cmi | luffitys | | Xiaomi Mi 10 | umi | 0xCAFEBABE, przekichane | | Xiaomi Mi 10S | thyme | Alcatraz323, Flicker372 | | Xiaomi Mi 10T / Xiaomi Mi 10T Pro / Xiaomi Redmi K30S Ultra | apollon | Ramisky, SebaUbuntu | 20 | | Xiaomi Mi 10T Lite 5G / Xiaomi Mi 10i 5G / Xiaomi Redmi Note 9 Pro 5G | gauguin | Hridaya, Lynnrin | 20 | | Xiaomi Mi 11 Lite 5G | renoir | ArianK16a | 20 | | Xiaomi Mi 11 Pro | mars | Flower Sea | 20 | | Xiaomi Mi 11i / Xiaomi Redmi K40 Pro / Xiaomi Redmi K40 Pro+ / Xiaomi Mi 11X Pro | haydn | AdarshGrewal, erfanoabdi | 20 | | Xiaomi Mi 9T / Xiaomi Redmi K20 (China) / Xiaomi Redmi K20 (India) | davinci | ArianK16a | 20 | | Xiaomi POCO F2 Pro / Xiaomi Redmi K30 Pro | lmi | SebaUbuntu | 20 | | Xiaomi POCO F3 / Xiaomi Redmi K40 / Xiaomi Mi 11X | alioth | SahilSonar, SebaUbuntu, althafvly | 20 | | Xiaomi POCO F4 / Xiaomi Redmi K40S | munch | SebaUbuntu | | Xiaomi POCO M2 Pro / Xiaomi Redmi Note 9S / Xiaomi Redmi Note 9 Pro (Global) / Xiaomi Redmi Note 9 Pro (India) / Xiaomi Redmi Note 9 Pro Max / Xiaomi Redmi Note 10 Lite | miatoll | dereference23, ItsVixano | 20 | | Xiaomi POCO X3 NFC | surya | Shimitar, TheStrechh | 20 | | Xiaomi Redmi 12C / Xiaomi Redmi 12C NFC / Xiaomi POCO C55 | earth | surblazer | | Xiaomi Redmi 7 / Xiaomi Redmi Y3 | onclite | Dhina17 | 20 | | Xiaomi Redmi K60 Pro | socrates | danielml | | Xiaomi Redmi Note 10 Pro / Xiaomi Redmi Note 10 Pro (India) / Xiaomi Redmi Note 10 Pro Max (India) | sweet | basamaryan, danielml3 | 20 |

View Details

So long, and thanks for all the fish

View Details

Lets have a drink!

View Details

X_X

View Details

XIX

View Details

Ohai there, it's been a while

View Details

Backstreet's back again

View Details

Changes since Mar 01, 2019

View Details

Sharks ahead

View Details

Changes since Sep 17, 2018

View Details

Your feedbacks

View Details

Changes since July 19th, 2018

View Details

That's... why I'm here

View Details

Changes since May 25th, 2018

View Details

Security and knowledge

View Details

Changes since April 1st, 2018

View Details

April Fools 2018

View Details

What it is, and how it affects you

View Details

Disruptive innovations

View Details

Your apps, better

View Details

Oh my! Finally Oreo

View Details

Happy birthday to us

View Details

Changes since September 23rd

View Details

Here's what you told us

View Details

Changes since August 8th 2017

View Details

It's your time

View Details

Changes since July 3rd 2017

View Details

Changes since June 12th 2017

View Details

Changes since 31st May 2017

View Details

What it is, and how it affects you

View Details

Changes since 15th May 2017

View Details

Changes since 2nd May 2017

View Details

Changes since 18th April 2017

View Details

W/C 3rd April

View Details

W/C 20th March

View Details

New mascot and a new way of development

View Details

W/C 6th March

View Details

W/C 27th Feb 2017

View Details

W/C 20th Feb 2017

View Details

W/C 13th Feb 2017

View Details

W/C 6th Feb 2017

View Details

All systems operational

View Details

Build slaves, mirrors, and builds

View Details

We aren't going anywhere.