Delayed Security Patches for AOSP (Android Open Source Project)
1–10 of 116 posts
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#2XCancel link which will show the thread context if you aren't logged in to Twitter: https://xcancel.com/grapheneos/status/1964561043906048183
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#3"No tags were pushed to AOSP for the July 2025 monthly release of Android. We asked about this on the android-building group but each of our posts was rejected. We emailed people at Google we've previously contacted about mistakes pushing tags but received no response this time."
https://xcancel.com/GrapheneOS/status/1952413110947430786
"July monthly release was not pushed to AOSP and then neither was the August monthly release. September quarterly release hasn't been pushed yet."
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#4̶D̶o̶n̶'̶t̶ ̶b̶e̶ ̶e̶v̶i̶l̶
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#5And so, Google's war on open Android continues.
Fucking hell. Can Google stop being evil for like 5 minutes? It's like they can't go a week without coming up with some new fucked up thing to do to their already tormented mobile ecosystem.
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#6This is entirely unsurprising. It's been clear that Google has been into their Android duopoly-abusive stage for a while now, with more and more of their Android changes moving into GMS or non-AOSP Google apps (like camera, messages, location services, etc) over the last decade. Graphene has been doomed to this fate for a long time, and anyone who thought otherwise was naively optimistic.
The same is clearly coming for Chromium forks, which is why I've always thought the privacy and ad-blocking forks are a joke - if they ever gain enough marketshare, or if google just tires of the public open source charade, they have no chance of maintaining a modern browser on their own.
This is all the more likely now that Google has been emboldened by not having to sell off Chrome for anticompetitive reasons.
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#7Google sold Android to nerds as open source. We thought that mobile operating systems would be won by the "Linux of mobile OSs."
But Google has made sure that didn't happen and we're left with devices more locked down than the proprietary Windows ecosystem we were hoping to leave in the past - and with a company in charge looking to exert even more power over us than Microsoft did.
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#8> We want to make sure that if you download an app from a developer, regardless of where you get it, it's actually from them. That's it.
In what scenario is this a serious threat because I can't think of any.
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#9This is entirely unsurprising. It's been clear that Google has been into their Android duopoly-abusive stage for a while now, with more and more of their Android changes moving into GMS or non-AOSP Google apps (like camera, messages, location services, etc) over the last decade. Graphene has been doomed to this fate for a long time, and anyone who thought otherwise was naively optimistic. The same is clearly coming f…
Just a year prior, I would have been against a decision to force Google to part with either Android or Chrome.
Now, I'm of the opinion that they should have been forced to sell off both, and maybe Chromebooks too, for the good measure.
No company with a direction as vile and openly user-hostile as what Google currently demonstrates should have anywhere near this level of control over the ecosystem.
Re: Delayed Security Patches for AOSP (Android Open Source Project)
#10> We want to make sure that if you download an app from a developer, regardless of where you get it, it's actually from them. That's it. In what scenario is this a serious threat because I can't think of any.
It sounds like EV certificates, and it turned out that in practice no one cared about id verification.