How so? I doubt many ROMs are based on code that isn’t part of an Android release. Surely GrapheneOS devs can just use the Android 16 branch once it’s released to make an Android 16 version of GrapheneOS.
Nobody’s saying that Google won’t give them the code, though. Nothing is moving to closed source, Google just isn’t going to be showing the current work-in-progress code for the next release to the public.
How so? I doubt many ROMs are based on code that isn’t part of an Android release. Surely GrapheneOS devs can just use the Android 16 branch once it’s released to make an Android 16 version of GrapheneOS.
Well if they move large portions of the project to closed source aosp would have to diverge if google isn’t going to give them the code.
Google is still planning on giving them the code; that’s in the article
Nobody’s saying that Google won’t give them the code, though. Nothing is moving to closed source, Google just isn’t going to be showing the current work-in-progress code for the next release to the public.