LineageOS 17.1 based on Android 10 is now officially available

If you call yourself a custom ROM veteran, you definitely have heard about LineageOS. LineageOS traces its roots back to CyanogenMod, the custom ROM that became popular on the HTC Dream/T-Mobile G1, the first Android smartphone available for purchase. CyanogenMod, in turn, went on to become one of the most popular custom ROMs available across a plethora of devices, and several of the key developers and maintainers of the project went on to establish LineageOS when Cyanogen decided to stop supporting CyanogenMod. LineageOS picked up the reins with LineageOS 13.0 and LineageOS 14.1 releases, and the project has continued along over the years. Now, LineageOS is marking its major version bump up to LineageOS 17.1 with Android 10 as the base.

LineageOS XDA Forums

Why Lineage 17.1 and not 17.0?

Android 10’s source code made its way to AOSP in September 2019, and the LineageOS team has been hard at work to bring forward their ROM and its features to the new Android version base. AOSP, though, had undertaken massive refactoring in certain areas, which made porting over take longer than anticipated. AOSP also introduced features like the new Permissions Hub, which conflicted with the custom ROM’s PrivacyGuard feature, forcing them to drop it. Both of these changes meant that the team had to work harder and take more time for bringing up the ROM as a whole to Android 10.

Meanwhile, the December 2019 Android Security Bulletin was released by Google, and the LineageOS team decided to rebase on the more feature-filled Google Pixel 4/4XL tag of AOSP. Owing to this, the team has also decided to jump up on the subversion, going from 17.0 to 17.1. For the future too, if there is any large scale rebasing undertaken onto a different tag, the team will jump up on the subversion number.

As a consequence of this jump, the team will be locking all Lineage-17.0 branches to contributions on their Gerrit, and abandoning existing 17.0 changes. Developers are still free to cherry-pick changes to 17.1, though.


Administrative and maintenance changes

The jump up to official LineageOS 17.1 means that most of the current build resources will now focus on building these new updates for supported devices. This has the expected side-effect of diverting resources from older builds. With the 17.1 branch reaching feature and stability-parity with 16.0, it will become the most recent and most actively developed branch, with regular nightly builds for supported devices commencing from January 31, 2020. Consequently, 16.0 will be moved to weekly builds, while 15.1 will be deprecated from automated builds.

LineageOS 17.1 will launch building for a small selection of devices, with additional devices to come as they are marked as both Charter compliant and ready for builds by their maintainer.

The Lineage team is also bringing over focus to their Wiki refresh. The LineageOS Wiki was recently extended and device maintainers were given significantly more options to customize their device’s individual installation, update, and upgrade instructions. As of LineageOS 17.1, maintainers will be expected to run through the full instructions on their device wiki and verify that the information holds true for their device. This renewed focus on the wiki is in light of the building up changes to AOSP, such as System-As-Root, A/B Partition Scheme, and Dynamic Partitions, which have the combined effect of obsoleting the instructions many of us have been following for years from memory — those instructions are now either no longer valid or are missing very critical steps. For example, the Heimdall (Samsung flashing tool) instructions were horribly outdated, so these have been updated to reflect new information. So if you are making the jump to LineageOS 17.1 or are just generally interested in custom ROMs, it would still be a good idea to check out your device’s Wiki page.


New features in LineageOS 17.1

LineageOS 17.1 brings over several new features to the ROM family:


Further changes

Lineage Recovery

Lineage is also making the switch to Lineage Recovery as the defacto solution to install LineageOS. Lineage Recovery will be built by default for all officially supported devices. The team mentions that this change was done purely to streamline their own processes and not to dissuade users away from other custom recoveries. Device maintainers retain the freedom to recommend alternative recovery on their device’s Wiki page alongside full instructions for usage.

AOSP’s Permission Hub and LineageOS’s PrivacyGuard

We’ve talked about this change in the past, and now the change is finally here. LineageOS 17.1 drops support for the homebrewed PrivacyGuard implementation in favor of AOSP’s Permission Hub as the team was unable to port the PrivacyGuard framework to Android 10. Google did not release Permissions Hub with Android 10, but the code for it still exists within AOSP. So, the Lineage team forked it and now presents that as the solution as it is claimed to be almost equivalent in features, but conflicted in attempts to co-exist alongside PrivacyGuard.

Rooting — no addonsu binary support

As a byproduct of the removal of PrivacyGuard and the switch over to Permission Hub, the addonsu binary that was usually offered as a simple root access solution is no longer feasible, as we had informed before. Users interested in root have the option to use ADB root, or flash compatible third-party solutions such as Magisk. The team clarifies that this does not mean that any particular third-party solutions are endorsed as officially supported — so you still need to be mindful of the root solution working harmoniously with your ROM.

Deprecation of Styles API

The Styles API is also now getting deprecated in favor of AOSP’s ThemePicker app. The team claims complete feature parity, and even feature superiority with ThemePicker.


Upgrade instructions for LineageOS 17.1

If you are on official LineageOS 16 and your device is present on the list of officially supported devices for LineageOS 17.1, you would still need to manually update your device as per instructions present on your device’s specific wiki page. The LineageOS updater app generally does not support upgrades from one version of LineageOS to another, so users have to make a conscious decision to update instead of being surprised by an OTA.

Device-specific instructions can vary, but for most devices we checked, the update instructions rely on using the adb reboot sideload command, and then adb sideload /”filepath” command. The Lineage team also mentions that updating within the official release channel builds does not require the user to wipe their device; but moving from an unofficial build to official LineageOS will require a device wipe from recovery.

It is very likely that you will be able to install LineageOS through a custom third-party recovery, but that is not the recommended upgrade method from the developers, so your mileage may vary on a per-device basis. Be sure to check your device’s wiki, its support page, and our own forums to ensure that you follow the correct methods to upgrade to avoid any issues.

You should also note that your ROM installation will not include Google Apps, for the simple reason that those apps are proprietary. You need to sideload a separate GApps package, with a heavy preference towards the GApps package recommended by your device maintainer/developer, because of the reasons we explain in a separate PSA. As a side note, Open GApps also released their official Android 10 flashable packages recently.

Your ROM will also not ship with a default root solution, as we explain in the preceding paragraphs. You need to separately flash third-party solutions.


LineageOS 17.1 – Official builds for supported devices

The following is the official build roster for batch 1 of the LineageOS 17.1 rollout:

Device and Forum Link Device codename and Wiki Link Maintainer
ASUS Zenfone 6 (ZS630KL) I01WD luca020400, OrdenKrieger
BQ Aquaris X bardock eloimuns, Quallenauge, Team aquaris-dev
BQ Aquaris X Pro bardockpro Quallenauge, Team aquaris-dev
Fairphone FP2 FP2 chrmhoffman
Google Nexus 6 shamu Elektroschmock, npjohnson
Google Pixel sailfish intervigil, razorloves
Google Pixel XL marlin intervigil, razorloves
HTC One 2014 m8 bgcngm
HTC One 2014 Dual-SIM m8d bgcngm
LG G2 (AT&T) d800 Kapricomus, Arnau, YoDevil
LG G2 (T-Mobile) d801 Kapricomus, Arnau, YoDevil
LG G2 (International) d802 Kapricomus, Arnau, YoDevil
LG G2 (Canadian) d803 Kapricomus, Arnau, YoDevil
LG G3 (AT&T) d850 firebird11, HardStyl3r
LG G3 (Canada) d852 firebird11, HardStyl3r
LG G3 (International) d855 firebird11, HardStyl3r
LG G3 (Korea) f400 firebird11, HardStyl3r
LG G3 (T-Mobile) d851 firebird11, HardStyl3r
LG G3 (Verizon) vs985 firebird11, HardStyl3r
LG G5 (Global) rs988 npjohnson
LG G5 (International) h850 npjohnson
LG G5 (T-Mobile) h830 npjohnson
LG V20 (AT&T) h910 npjohnson
LG V20 (Global) h990 npjohnson
LG V20 (Sprint) ls997 npjohnson
LG V20 (T-Mobile) h918 npjohnson
LG V20 (US Unlocked) us996 npjohnson
LG V20 (Verizon) vs995 npjohnson
Motorola Moto Z griffin DD3Boh, erfanoabdi, shr3ps, stargo, vache
Motorola Moto G6 Plus (XT1926-2/3/5/6/7/8/9) evert Jleeblanch
Motorola Moto G7 river erfanoabdi, Nolen Johnson (npjohnson), SyberHexen
Motorola Moto G7 Plus (XT1965-2/3/6) lake Jleeblanch
Motorola Moto X4 payton erfanoabdi
Motorola Moto Z2 Force nash erfanoabdi, npjohnson
Motorola One Power (XT1942-1/2) chef Hasaber8
OnePlus 3/3T oneplus3 dianlujitao
OnePlus 6 enchilada luca020400, LuK1337
OnePlus 6T fajita LuK1337
OnePlus 7 Pro guacamole LuK1337, Tortel
Razer Phone cheryl mikeioannina
Samsung Galaxy S4 Active (GT-I9295) jactivelte arco, npjohnson, side
Samsung Galaxy S4 (SGH-I337) jflteatt arco, npjohnson, side
Samsung Galaxy S4 (SCH-R970/C/X,  SPH-L720) jfltespr arco, npjohnson, side
Samsung Galaxy S4 Value Edition (GT-I9515/L) jfvelte arco, npjohnson, side
Samsung Galaxy S4 (SCH-I545) jfltevzw arco, npjohnson, side
Samsung Galaxy S4 (GT-I9505/G, SGH-I337M, SGH-M919) jfltexx arco, npjohnson, side
Samsung Galaxy Tab S5e Wi-Fi (SM-T720) gts4lvwifi bgcngm, LuK1337
Sony Xperia 10 kirin LuK1337
Sony Xperia 10 Plus mermaid LuK1337
Sony Xperia XA2 pioneer cdesai, LuK1337, Stricted
Sony Xperia XA2 Ultra discovery LuK1337
Xiaomi Mi 6 sagit ArianK16a, Elektroschmock
Xiaomi Mi 8 dipper infrag
Xiaomi Mi Mix 2 chiron mikeioannina, wight554
Xiaomi Mi Mix 2S polaris bgcngm
Xiaomi POCO F1 beryllium bgcngm, warabhishek
Lenovo ZUK Z2 Plus z2_plus DD3Boh

More devices should be making the transition soon to LineageOS 17.1, so keep an eye on our frontpage as we will run regular stories on the same.


New features in LineageOS 16.0 branch

In addition to the latest branch, the older LineageOS 16.0 branch is also seeing a few major changes:


LineageOS 16 – Official builds for supported devices

While maintainers work towards bringing up devices to official LineageOS 17.1 based on Android 10, you can still find automated weekly builds for these devices that are supported for LineageOS 16:

LineageOS 16 Official Build List. Tap/click to expand.

Device and Forum Link Device codename and Wiki Link Maintainer
ASUS ZenFone 3 (ZE520KL, ZE552KL) zenfone3 makorn645
Asus Zenfone Max Pro M1 X00TD SagarMakhar
Asus Zenfone Max Pro M2 X01BD Bauuuuu, kubersharma001
BQ Aquaris X bardock eloimuns, Quallenauge, Team aquaris-dev
BQ Aquaris X Pro bardockpro Quallenauge, Team aquaris-dev
BQ Aquaris X2 zangya eloimuns, Kra1o5, Team aquaris-dev
BQ Aquaris X2 Pro zangyapro eloimuns, Kra1o5, Team aquaris-dev
Essential PH-1 mata haggertk, intervigil, jrior001, rashed
Fairphone 2 fp2 chrmhoffmann
Google Nexus 6 shamu Elektroschmock, npjohnson
Google Pixel sailfish intervigil, razorloves
Google Pixel XL marlin intervigil, razorloves
Honor 5X kiwi BadDaemon, dobo, joelh
Honor View 10 berkeley LuK1337
Huawei P20 Pro charlotte LuK1337
LeEco Le 2 s2 codeworkx, Rk585
LeEco Le Max2 x2 tortel, ThEMarD
LeEco Le Pro3/Le Pro3 Elite zl1 codeworkx
Lenovo P2 kuntao mikeioannina, highwaystar
Lenovo Yoga Tab 3 Plus YTX703F Quallenauge, Vladimir Oltean
Lenovo Yoga Tab 3 Plus LTE YTX703L Quallenauge, Vladimir Oltean
Lenovo ZUK Z1 ham sb6596
LG G3 (Sprint) ls990 firebird11, HardStyl3r
Motorola Moto G7 river erfanoabdi, npjohnson, SyberHexen
Motorola Moto X 2014 (XT1092/3/5/6/7) victara linckandrea, Tortel
Nextbit Robin ether javelinanddart, mikeioannina, npjohnson
Nubia Z17 nx563j BeYkeRYkt
OnePlus One bacon jrior001, npjohnson
OnePlus 2 oneplus2 OzzysCmAcc, aviraxp
OnePlus 3 oneplus3 dianlujitao
OnePlus 5 cheeseburger codeworkx, jrizzoli, xingrz, amartinz, jumoog
OnePlus 5T dumpling amartinz, codeworkx
OPPO F1 (International) f1f highwaystar
OPPO Find 7a/7s find7 mikeioannina
OPPO R5/R5s (International) r5 maniac103
OPPO R7s (International) r7sf celoxocis
OPPO R7 Plus r7plus maniac103
Realme 3 Pro RMX1851 karthick111, nibaji, darshan1205
Samsung Galaxy A3 2016 (SM-A310F/M/N0/Y) a3xelte danwood76, Stricted
Samsung Galaxy A5 2016 (SM-A510F/M/Y/K/L/S/8) a5xelte danwood76, Stricted
Samsung Galaxy A5 2017 (SM-A520F/DS/W) a5y17lte filiprrs, raymanfx
Samsung Galaxy A7 2017 (SM-A720F/DS) a7y17lte filiprrs, raymanfx
Samsung Galaxy Note 3 (SM-N9005/P) hlte haggertk, npjohnson
Samsung Galaxy Note 3 (SM-N9008V) hltechn haggertk, npjohnson
Samsung Galaxy Note 3 (SM-N900K/L/S) hltekor haggertk, npjohnson
Samsung Galaxy Note 3 (SM-N900T/V/W8) hltetmo haggertk, npjohnson
Samsung Galaxy S III Neo Dual-SIM (GT-I9300I) s3ve3gds fcuzzocrea, PythonLimited
Samsung Galaxy S III Neo Samsung Camera(GT-I9301I/Q) s3ve3gjv fcuzzocrea, PythonLimited
Samsung Galaxy S III Neo Sony Camera (GT-I9300I/Q) s3ve3gxx fcuzzocrea, PythonLimited
Samsung Galaxy S5 Active klteactivexx javelinanddart
Samsung Galaxy S5 LTE (G900AZ/F/M/R4/R7/T/V/W8,S902L) klte haggertk
Samsung Galaxy S5 LTE (G9006V/8V) kltechn haggertk
Samsung Galaxy S5 LTE (G900I/P) kltedv haggertk
Samsung Galaxy S5 LTE (SCL23) kltekdi haggertk
Samsung Galaxy S5 LTE (G900K/L/S) kltekor haggertk
Samsung Galaxy S5 LTE-A lentislte cvxda, sassman
Samsung Galaxy S5 LTE Duos (G9006W/8W) kltechnduo haggertk
Samsung Galaxy S5 LTE Duos (G900FD/MD) klteduos haggertk
Samsung Galaxy S5 Neo s5neolte danwood76, Stricted
Samsung Galaxy S5 Plus kccat6 cvxda, sassmann
Samsung Galaxy Tab S2 8.0 Wi-Fi (2016) gts28vewifi mccreary, syphyr, luca020400
Samsung Galaxy Tab S2 9.7 Wi-Fi (2016) gts210vewifi syphyr, luca020400
Sony Xperia Z3 z3 Tom1000, Myself5
Sony Xperia Z3 Compact (D5803/D5833) z3c ArianK16a
Wileyfox Storm kipper jrior001
Wileyfox Swift crackling jrior001
Xiaomi Mi 5 gemini bgcngm, defer, h2o64
Xiaomi Mi 5s capricorn LuK1337
Xiaomi Mi 5s Plus natrium LuK1337
Xiaomi Mi A1 tissot flex1911, TheScarastic
Xiaomi Mi Mix lithium balika011, blunden
Xiaomi Mi Note 2 scorpio joe2k01
Xiaomi Mi Note 3 jason dianlujitao
Xiaomi Redmi 3S/X land Isaac Chen
Xiaomi Redmi 4/X santoni Isaac Chen
Xiaomi Redmi Note 4 mido aryankedare
Yandex Phone amber HighwayStar, vm03

Much like LineageOS 17.1 builds, we should see more devices making their way onto the weekly LineageOS 16 build roster.


Support LineageOS

LineageOS is and has always been a community effort, riding on the back of volunteers dedicating their own resources for the general good of the community. If you want to contribute to LineageOS, there are multiple ways to do so.

Becoming a device maintainer

The primary way you can help LineageOS grow to more devices is to maintain the ROM for devices that you can. If you’re a developer and would like to submit your device for official support, you can follow the instructions present over here. Once you submit, you’ll receive some feedback on your submission. If it’s up to par, you will be invited to Lineage’s communication channels, and your device resources will be forked to LineageOS’s official repository.

Providing translations

Alternatively, you can also provide translations for different languages through Crowdin. The team mentions that even if your language is not officially supported in Android, you can reach out to the team and they’ll take steps to include your language. However, the team requests that you should submit translations only if you have reasonable proficiency in the language.

Donations

Running automated builds for such a wide roster of devices takes resources. You can contribute towards some of these costs by donating to LineageOS through their PayPal or Patreon.

Donate to LineageOS: via PayPal ||| via Patreon


This article was updated at 4:35 PM EST on April 10, 2020, to add the Google Nexus 6, Google Pixel, Google Pixel XL, BQ Aquaris X, and BQ Aquaris X Pro to the list of devices with official LineageOS 17.1 builds.

Read This Next

Load more