Ahh, so this will just give Google reason to remove any type of base and unlocking.
they don’t need reasons anymore… they do whatever and don’t get punished, as do all major corporations.
Anyone know which Pixels, and if GrapheneOS would mitigate it?
[the fix] It’s included in the Pixel Update Bulletin for September 2026 released on 2026-09-15 and will be included in the upcoming release of GrapheneOS.
So GrapheneOS is going use the security patch Google provides or will they implement a fix in parallel on their own?
I ask because my theory is that even if you use GrapheneOS, since it’s android you are still going to be reliant on google code releases.
But I’m also hoping that’s not the case,this will be a good test to see if security patches will be dependent on Google or not.
The answer to your question is literally in the third reply on that link.
Thanks for the heads up!
[Edit: Why the fuck is this app installing a Harry Potter Audible ad on my phone? Fuck you Google.]
what are you talking about
“Harry Potter Audiobook Packs Instantly customize your Pixel with Harry Potter Audiobook Packs to celebrate the release of Harry Potter: The Full-Cast Audio Editions on Audible. One tap changes your wallpaper, icons, and sounds with elements from the audiobooks - no wand required. To begin your journey to Hogwarts, all eligible Pixel users will receive a two-month Audible free trial.(2)”
(Source: https://support.google.com/pixelphone/thread/466181739/september-2026-pixel-drop?hl=en)
Why the hell is this garbage being bundled woth my OS?
Why the hell is this garbage being bundled woth my OS?
Would like to know if the most recent update lays ground work for the developer attestation program or if that is installed against my will regardless.
I’ve heard that’s installed through Google Play Services so you get it even if your phone is no longer receiving timely security updates from the manufacturer. How considerate of them…
There’s no such thing as privacy.
We shouldn’t have lived our lives for these businesses and nations, we’re slaves and we helped create it all.
We traded our privacy for free stuff.
We traded our human freedom for escapism and disconnection too.
I can’t help by view the common citizen like hooker being fed drugs by a pimp so that the hooker will keep working for him. It’s the same cycle and the same method…
And Graphene thinks that they’re secure.
Is this just cynicism, or is there a history of CVEs before patches exist? This is the first headline I’ve seen like this.
And Graphene is moving to Motorola anyway.
Not moving to, but adding them as I understand it.
Pixel 11 downgraded something such that GrapheneOS will not be ported to it; it remains to be seen if any future Pixels will meet Graphene’s standards.
Edit: Memory tagging extensions introduced with Pixel 8 series are missing from Pixel 11.
Every time I hear about a pixel release it’s something being downgraded from the previous versions lol
Pixel 11 will likely be improved to meet our requirements. Android 17 QPR2 Beta 4 added back MTE support after our initial thread about this. It turns out hardware support does exist. It’s not clear why it was entirely unavailable and disabled in firmware at launch. There may be something wrong with it which has to be worked around in firmware. It may have simply not been implemented yet. We’re now optimistic that we’ll be able to support those alongside the Motorola devices.<
Nice! Thanks for the correction.
That’s called a zero day.
