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 Googl

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.