GrapheneOS is targeting the release of Android Q as the starting point for truly reviving the project. Only a fraction of the past privacy/security work has been ported to Android Pie, largely because it made more sense to wait for momentum to pick up before diving back into it.
Conversation
Replying to
I haven't been very successful at getting back control over everything stolen from the project, and the community hasn't been restored to anything close to what it was before. Many people aren't aware the project continued, or that the people stealing the old name are scammers.
1
1
Regardless, I'm going to need the smaller and more fragmented community to start stepping up and making substantial contributions to the project this month. This project only makes sense if the existing work can be preserved and substantial progress can be made towards the goals.
1
2
The current state is acceptable because it didn't make sense to immediately revive everything and expect it would have momentum. The expectations are set much higher for this fresh start with Android Q. It's a very broad project with lots of depth, not something for one person.
5
Replying to
are automatic upgrades already implemented into GrapheneOS? also is it possible to manualy install the basic Google stuff over it (store/services/framework)?
1
1
> are automatic upgrades already implemented into GrapheneOS?
Yes, there have been automatic updates from the release of the project. See grapheneos.org/usage and grapheneos.org/releases for details. There's not much documentation on the site at this point but it covers this.
1
2
Show replies