• Announcements
  • Explanation of recent changes to AOSP and the lack of major impact on GrapheneOS

othemad
Does not excuse them from using the search function (or in some cases, literally just scrolling down the page a small bit).

othemad People keep asking about this because our worst nightmare is waking up one day to the news that GrapheneOs has been discontinued.

That would be bad!

That said, even if GrapheneOS suddenly halted today, there would still be some months during which it would arguably remain the most-secure Android variant, so there would be some time to decide what to do. And even if some Google change slowed down GrapheneOS development by some weeks per cycle continuing to run it would probably make sense.

Meanwhile, hopefully people who treasure GrapheneOS are making financial donations, and also hopefully contributing in other ways, such as being polite and constructive on this forum, researching facts instead of amplifying unsubstantiated rumors, citing sources, searching before posting, ... If developers can spend less time arguing against misconceptions they can spend more time developing.

such volunteer explanation clarification realeaving stress from security concerned users shows GOS involvement and care

def worth an extra donat
really.

woddahSehT I think this part of the post answers your question:

The small subset of the OS developed via AOSP main moving away from it won't have a major impact on GrapheneOS. It did not provide us with early access to the code we need for porting GrapheneOS to an upcoming release before the day it gets released. That already required having partner access.

othemad People keep asking about this because our worst nightmare is waking up one day to the news that GrapheneOs has been discontinued.

I think the worst case would be that it takes longer to release GrapheneOS after an update to AOSP. Even if this were the case in the future it's probably not dramatic for most users.

5 days later