4 ms·

GrapheneOS is in dire need of an OEM partner access which can provide them with the latest source which Google has put behind a paywall. Otherwise, GrapheneOS w

GrapheneOS is in dire need of an OEM partner access which can provide them with the latest source which Google has put behind a paywall. Otherwise, GrapheneOS will not be able to continue the development and eventually shut down

47282847 1y ago
It sounds like early access will speed things up for them/their users. I read nothing in the thread about a general inability to continue nor the danger of having to shut it down? I very much applaud the goal of trying to be up to date within a few days of new releases and I hope they find both good devs and gain access. I can also see how that may impact morale in the longer term if they don’t.
- DoctorOW 1y ago
  The rumor is that Android will be going almost completely closed source. If that happens, there'll be no new releases.
- udev4096 1y ago
  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.

47282847 1y ago

It sounds like early access will speed things up for them/their users. I read nothing in the thread about a general inability to continue nor the danger of having to shut it down? I very much applaud the goal of trying to be up to date within a few days of new releases and I hope they find both good devs and gain access. I can also see how that may impact morale in the longer term if they don’t.

DoctorOW 1y ago
The rumor is that Android will be going almost completely closed source. If that happens, there'll be no new releases.
udev4096 1y ago
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.