3 ms·

As you can see at pixel 9 pro's (https://download.lineageos.org/devices/caiman/changes https://download.lineageos.org/devices/caiman/changes)[los changes], it w

by Vax- 26d ago

As you can see at pixel 9 pro's (https://download.lineageos.org/devices/caiman/changes https://download.lineageos.org/devices/caiman/changes)[los changes], it was updated around Aug 18th (or at least that's when the string bump happened), so although ~2 weeks late (assuming the security patch was released at August 1st, which I'm not sure if it really works this way), it's not as bad as you said. But yeah GOS is probably the better choice for pixels, depending on the user's prefs of course. Btw I noticed similar pattern for other devices that support los, like xiaomi ones.

grapheneos 26d ago
Your response doesn't address what we said. You linked to a page showing LineageOS had a release in August 2026 which does not show it has shipped all the recent standard Android and Pixel security patches, which it hasn't done. The latest releases of LineageOS for Pixels do not provide the June 2026 and later updates to the firmware, kernel, drivers and HALs because those have only been provided for Android 17 since it was released and LineageOS isn't yet based on Android 17. Separately from that, since Lineage is still based on Android 16 QPR2 it also doesn't include the many privacy and security patches not backported from Android 17. Android ships many security patches as part of the QPR2 and yearly releases which are not backported to older releases. The backports to older releases are increasingly incomplete. Years ago, they stopped backporting any Low and Moderate severity patches to older releases and more recently they've been scaling back the amount of High and Critical severity patches which are backported. An official policy announcement was made to OEMs that they'd no longer backport many High and Critical severity patches where an LLM discovered the vulnerability internally due to the large volume of patches. Pixels move to the latest OS releases and that means the firmware, kernel, driver and HAL code is only provided for those. It's most difficult for the major yearly releases due to the new API level but it's not trivial for QPR1, QPR2 and QPR3 either.

by Vax- 26d ago

grapheneos 26d ago

Your response doesn't address what we said. You linked to a page showing LineageOS had a release in August 2026 which does not show it has shipped all the recent standard Android and Pixel security patches, which it hasn't done. The latest releases of LineageOS for Pixels do not provide the June 2026 and later updates to the firmware, kernel, drivers and HALs because those have only been provided for Android 17 since it was released and LineageOS isn't yet based on Android 17. Separately from that, since Lineage is still based on Android 16 QPR2 it also doesn't include the many privacy and security patches not backported from Android 17. Android ships many security patches as part of the QPR2 and yearly releases which are not backported to older releases. The backports to older releases are increasingly incomplete. Years ago, they stopped backporting any Low and Moderate severity patches to older releases and more recently they've been scaling back the amount of High and Critical severity patches which are backported. An official policy announcement was made to OEMs that they'd no longer backport many High and Critical severity patches where an LLM discovered the vulnerability internally due to the large volume of patches. Pixels move to the latest OS releases and that means the firmware, kernel, driver and HAL code is only provided for those. It's most difficult for the major yearly releases due to the new API level but it's not trivial for QPR1, QPR2 and QPR3 either.