No, Graphene... No, I don't think I will. Google refusing to support this phone for longer than 4 years is not my problem. Especially considering that this is the last Pixel to ship with a 3.5mm port.
=> More informations about this toot | More toots from serebit@floss.social
@serebit
So, what are you going to do now? Shame that DivestOS has ended, otherwise there would be other options similar to Pixels for a Graphene-like setup.
=> More informations about this toot | More toots from w8l@scalie.zone
@w8l @serebit DivestOS was a harm reduction project, not a highly hardened OS protecting people's privacy and security to anywhere near the extent GrapheneOS does. It didn't provide most of the privacy and security features available in GrapheneOS and was still based on Android 13 when it was recently discontinued. It's not possible to provide the same thing on insecure hardware without basic security patches and not supporting the basic building blocks we use such as hardware memory tagging.
=> More informations about this toot | More toots from GrapheneOS@grapheneos.social
@w8l @serebit
DivestOS was based on LineageOS so a big part of what they had to do was making up for how LineageOS reduces security. It was primarily aimed at harm reduction on end-of-life devices missing firmware and most driver patches along with basic hardware-based security features. DivestOS never portrayed itself as a GrapheneOS alternative.
Here's a third party comparison of Android-based OSes:
https://eylenburg.github.io/android_comparison.htm
There's an older version with DivestOS:
https://eylenburg.github.io/old/android_comparison_2024old.htm
=> More informations about this toot | More toots from GrapheneOS@grapheneos.social
@w8l @serebit All we did is add a notification for 4th and 5th gen Pixels about them being end-of-life and therefore insecure. It's shown once after boot and people can dismiss it. It doesn't stop people using the devices and we intend to still keep them working with occasional updates. Since it's not secure regardless, we don't intend to keep providing the AOSP security backports indefinitely. We provided them for a long time for 4th gen for the legacy Android 13 branch and that's over now.
=> More informations about this toot | More toots from GrapheneOS@grapheneos.social This content has been proxied by September (3851b).Proxy Information
text/gemini