LineageOS 20, based on Android 13 QPR1, arrives stupid quick

There is a lot of quiet work to maintain custom Android builds. Bringing this space to life with players like Paranoid Android and LineageOS, a descendant of OG Cyanogenmod, is a galactic, ethereal hum. On the last day of 2022, the Lineage development team announced a wildly ambitious version bump for Android 13 with LineageOS 20.

In a detailed changelog in a blog post, Lineage sets out some major changes beyond just numbers. One is to change the way numbers change by removing point updates. 20.1 is not shown. It stays 20 forever. This extends to the developer level where the repository is under “Lineage-20” instead of “Lineage-20.0”.


And instead of waiting until April for the annual update, we also get a very fast port this time due to the smaller payload of edits between Android 12 and 13. This upgrade is based on

The biggest addition to Lineage is Aperture, a new camera app in ROM built on Google’s CameraX library. It follows many of the stock playbooks, but is a unique product and a big step up from the modified Camera2 app we used before, it has a native he QR code reader. For audio, the Recorder app Material You has been redesigned and the .WAV recording mode has been upgraded to stereo.

This update keeps a ton of boats afloat as security patches from April to December this year have been integrated into LineageOS 20 and can be applied to devices running versions as far back as 17.1.

LineageOS 20 now supports 20 devices including the Fairphone 4, Pixel 4, 4 XL, 4a, 5, and 5a, plus tons of Motorola and OnePlus devices. Developers looking to add new devices to their boards may be able to take advantage of board-specific common kernels to get a head start. These boards include the Qualcomm Snapdragon 835, 845, 855, 865, and 888. If you have a Snapdragon 820 device, you can get the LineageOS 18.1 kernel.

Full details and installation instructions are still available on Lineage’s website.

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *