{"id":174195,"date":"2023-01-01T11:11:06","date_gmt":"2023-01-01T11:11:06","guid":{"rendered":"https:\/\/harchi90.com\/lineageos-20-based-on-android-13-qpr1-arrives-stupid-quick\/"},"modified":"2023-01-01T11:11:06","modified_gmt":"2023-01-01T11:11:06","slug":"lineageos-20-based-on-android-13-qpr1-arrives-stupid-quick","status":"publish","type":"post","link":"https:\/\/harchi90.com\/lineageos-20-based-on-android-13-qpr1-arrives-stupid-quick\/","title":{"rendered":"LineageOS 20, based on Android 13 QPR1, arrives stupid quick"},"content":{"rendered":"
\n
<\/p>\n
There’s shedloads of quiet work that go into keeping a custom Android build alive. It’s the galactic, ethereal hum that makes this vibrant space with players such as Paranoid Android or the descendant of the OG Cyanogenmod, LineageOS. On the last day of 2022, the Lineage devteam is out with a furiously ambitious version bump, giving its take on Android 13 with LineageOS 20.<\/p>\n
\n <\/p>\n
In a verbose changelog of a blog post, Lineage sets out some major changes besides just a number change. For one, it’s changing the way it changes numbers by dropping point updates \u2014 you won’t see a 20.1, it’s just 20 all the way, baby. This goes all the way down to the developer level with repositories going under “lineage-20” and not “lineage-20.0.”<\/p>\n
<\/p>\n
\n
\n
\n
ANDROIDPOLICE VIDEO OF THE DAY<\/strong><\/div>\n<\/div>\n<\/div>\n<\/div>\n
And instead of waiting until April for the annual update, we also get an extremely fast port this time around thanks to a smaller payload of edits between Android 12 and 13. This upgrade is based on QPR1.\u200b \u200b<\/p>\n