3 ms·

Yeah, they haven't posted about shutting down on twitter. It was posted in the matrix room: > We previously let the community know we need Android partner acce

Yeah, they haven't posted about shutting down on twitter. It was posted in the matrix room: > We previously let the community know we need Android partner access in order to port to Android 16 early and for other reasons. We have not received Android partner access. Now that Android 16 has been released, it has become clear that we are going to need it more than before going forward. At the moment, it's clear that GrapheneOS development will be unable to continue in the way it was going before. This the last call for people to share partner access with us if you want to see GrapheneOS continue. Otherwise, be prepared for the final release of GrapheneOS to be today. It's up to the people who have this access to decide if they want the project to go on after today. In order to continue without this, we would need to do substantially more work that we have not had to do previously.

ysnp 1y ago
EDIT: More context from the GrapheneOS team on their public Twitter communications >In the past, the main issue with AOSP was them forking AOSP apps into Google apps and then sometimes abandoning the AOSP apps. This increased over time, leaving behind a bunch of legacy apps we need to replace. There have been similar issues to this, but all things we can handle. >They've added more and more functionality to Google Play which ends up being considered required, but they haven't ever gone out of the way to gut parts of AOSP. Android 16 has changed this. They ripped out all of the device repositories, despite promising to do the opposite. More contextual information potentially coming from a community member (not GrapheneOS) on their forum: >Google apparently hasn't released the kernel code and Pixel device specific code yet, and GrapheneOS team seem to be panicking over that latter part right now, as Google seemingly have removed that code from the AOSP tree entirely, possibly permanently. The next few days will be exciting.

ysnp 1y ago

EDIT: More context from the GrapheneOS team on their public Twitter communications >In the past, the main issue with AOSP was them forking AOSP apps into Google apps and then sometimes abandoning the AOSP apps. This increased over time, leaving behind a bunch of legacy apps we need to replace. There have been similar issues to this, but all things we can handle. >They've added more and more functionality to Google Play which ends up being considered required, but they haven't ever gone out of the way to gut parts of AOSP. Android 16 has changed this. They ripped out all of the device repositories, despite promising to do the opposite. More contextual information potentially coming from a community member (not GrapheneOS) on their forum: >Google apparently hasn't released the kernel code and Pixel device specific code yet, and GrapheneOS team seem to be panicking over that latter part right now, as Google seemingly have removed that code from the AOSP tree entirely, possibly permanently. The next few days will be exciting.