What LineageOS 24.0 actually ships on the first day

What happened

The LineageOS project's changelog 32 says the 24.0 branch has reached feature and stability parity with 23.2 and is ready for an initial release based on Android 17. It says 24.0 will launch builds for a selection of devices, with more as maintainers meet the charter. It also says that even where some Linux 4.4 and 4.9 devices were ported to 23.2 or 24.0, the project will accept only LineageOS 22.2 submissions for those kernels. LineageOS 22.2 continues to receive builds and monthly security patches until Google stops distributing official Android 15 security bulletins. On 23.2 and 24.0 the project says it is shipping kernels with a 1:1 eBPF backport that build fully without GCC. Android Police's account of the same release says the first stable build includes security patches from August 2025 through October 2026, and that a browser-based WebUSB installer can talk to a device from the browser. The project, in that account, still says the device wiki is the supported installation method and that the browser tool is an additional option. The paper filing the changelog isFutureweb.

What the browser tool is not

Android Police says the WebUSB tools can use several existing protocols and that compatibility depends on the device, the browser, the operating system, and the USB connection. That is an option. It is not a promise that every phone on the wiki can be installed from a browser, and this page does not print an install sequence. The desk isMobile.

What LWN is doing in the file

LWN's wire item is a third account that LineageOS 24 was released. The project's changelog is the record of the kernel policy and the parity claim. This page does not import LWN's wording beyond the fact of that account. ColorOS 17's vendor schedule is a different mobile document from the same day,what the October 13 ColorOS 17 schedules actually date.

Why it matters on this desk

The dependency is which old phones get Android 17 from this project and which are told to stay on the Android 15 branch. The project's own line is that 4.4 and 4.9 kernels remain on 22.2 because those trees are hard to keep pulling forward. What an app sandbox stops, on a phone that does get a build, iswhat an app sandbox stops.

What this page will not import

This page does not list every device, does not tell anyone how to unlock a bootloader, and does not treat a browser installer as the new default. A Pixel refurbished listing is a different phone fact,what Google's Pixel 9 refurbished listing changes.

Where the accounts overlap

The changelog and Android Police overlap on an initial Android 17 release and on a browser installer that does not replace the wiki. The kernel cutoff is the project's sentence. LWN overlaps on the release existing. They do not overlap on a claim that every unofficial port is now official. The project says kernels it ships on 23.2 and 24.0 have a 1:1 eBPF backport and build without GCC. That is a kernel rule, not an install guide. This page does not describe how WebUSB talks to a bootloader. The project says kernels it ships on 23.2 and 24.0 have a 1:1 eBPF backport and build without GCC. That is a kernel rule, not an install guide. Android Police names example devices, including Pixel phones and the OnePlus 13. The changelog's rule is still that the set grows as maintainers qualify devices.

What to watch next

A further changelog that adds devices, or a notice that Google has stopped Android 15 bulletins and 22.2's patch promise has ended, would change the record. A tutorial would not. What a version number has to mean, when 24.0 and 22.2 are both current for different kernels, iswhat a version number has to mean.

What would change the record

A reversal that accepts 4.4 and 4.9 kernels on 24.0, or a statement that the wiki is no longer the supported path, would change it. A device count from a secondary article that the project has not published would not replace the changelog's rule that more devices come as maintainers are ready. Android Police names example devices, including Pixel phones and the OnePlus 13. The changelog's rule is still that the set grows as maintainers qualify devices. Android Police names example devices, including Pixel phones and the OnePlus 13. The changelog's rule is still that the set grows as maintainers qualify devices. This page does not describe how WebUSB talks to a bootloader. The project says kernels it ships on 23.2 and 24.0 have a 1:1 eBPF backport and build without GCC. That is a kernel rule, not an install guide.

What stays an initial release

What stays specific is LineageOS 24.0 at parity with 23.2 for an initial device set on Android 17, a hard stop on new 4.4 and 4.9 submissions above 22.2, monthly 22.2 patches until Google stops Android 15 bulletins, and a browser installer that Android Police says is optional beside the wiki. LWN is the third account of the release. This page does not describe how WebUSB talks to a bootloader. The project says kernels it ships on 23.2 and 24.0 have a 1:1 eBPF backport and build without GCC. That is a kernel rule, not an install guide. Android Police names example devices, including Pixel phones and the OnePlus 13. The changelog's rule is still that the set grows as maintainers qualify devices.