From d981e60c2f2122a69c824ce25eb3b5f39f81755c Mon Sep 17 00:00:00 2001
From: Daniel Micay Official releases are available on the releases page and
installation instructions are on the install page. GrapheneOS has made substantial contributions to the privacy and security of the
- Android Open Source Project, along with contributions to the Linux kernel, LLVM,
- OpenBSD and other projects. Much of our past work is no longer part of the downstream
- GrapheneOS project because we've successfully landed many patches upstream. We've had
- even more success with making suggestions and participating in design discussions to
- steer things in the direction we want. Many upstream changes in AOSP such as removing
- app access to low-level process, network, timing and profiling information originated
- in the GrapheneOS project. The needs of the upstream projects are often different from
- ours, so they'll often reimplement the features in a more flexible way. We've almost
- always been able to move to using the upstream features and even when we still need
- our own implementation it helps to have the concepts/restrictions considered by the
- upstream project and apps needing to be compatible with it. Getting features upstream
- often leads to an improved user experience and app compatibility.Upstream contributions
-
- No Google apps or services
@@ -202,6 +184,24 @@
particular sponsor or company.
GrapheneOS has made substantial contributions to the privacy and security of the + Android Open Source Project, along with contributions to the Linux kernel, LLVM, + OpenBSD and other projects. Much of our past work is no longer part of the downstream + GrapheneOS project because we've successfully landed many patches upstream. We've had + even more success with making suggestions and participating in design discussions to + steer things in the direction we want. Many upstream changes in AOSP such as removing + app access to low-level process, network, timing and profiling information originated + in the GrapheneOS project. The needs of the upstream projects are often different from + ours, so they'll often reimplement the features in a more flexible way. We've almost + always been able to move to using the upstream features and even when we still need + our own implementation it helps to have the concepts/restrictions considered by the + upstream project and apps needing to be compatible with it. Getting features upstream + often leads to an improved user experience and app compatibility.
+