diff --git a/static/build.html b/static/build.html index aa9a7de4..fffd872d 100644 --- a/static/build.html +++ b/static/build.html @@ -31,7 +31,7 @@
  • Install
  • Build
  • Usage
  • - +
  • FAQ
  • Releases
  • Source
  • Donate
  • diff --git a/static/contact.html b/static/contact.html index 33a546e8..f23bb3e8 100644 --- a/static/contact.html +++ b/static/contact.html @@ -31,7 +31,7 @@
  • Install
  • Build
  • Usage
  • - +
  • FAQ
  • Releases
  • Source
  • Donate
  • diff --git a/static/donate.html b/static/donate.html index 3d1dd32d..3e82d531 100644 --- a/static/donate.html +++ b/static/donate.html @@ -31,7 +31,7 @@
  • Install
  • Build
  • Usage
  • - +
  • FAQ
  • Releases
  • Source
  • Donate
  • diff --git a/static/faq.html b/static/faq.html index a3ca10bc..be38605d 100644 --- a/static/faq.html +++ b/static/faq.html @@ -46,6 +46,40 @@

    Table of contents

    + + +

    + Which devices are supported? +

    + +

    GrapheneOS has official production support for the Pixel 2, Pixel 2 XL, Pixel 3, + Pixel 3 XL, Pixel 3a and Pixel 3a XL. The release tags for these devices have official + builds and updates available. These devices meet the stringent privacy and security + standards and have substantial upstream and downstream hardening specific to the + devices.

    + +

    Many other devices are supported by GrapheneOS at a source level, and it can be + built for them without modifications to the existing GrapheneOS source tree. Device + support repositories for the Android Open Source Project can simply be dropped into + the source tree, with at most minor modifications within them to support GrapheneOS. + In most cases, substantial work beyond that will be needed to bring the support up to + the same standards. For most devices, the hardware and firmware will prevent providing + a reasonably secure device, regardless of the work put into device support.

    + +

    GrapheneOS also supports generic targets, but these aren't suitable for production + usage and are only intended for development and testing use. For mobile devices, the + generic targets simply run on top of the underlying device support code (firmware, + kernel, device trees, vendor code) rather than shipping it and keeping it updated. It + would be possible to ship generic system images with separate updates for the device + support code. However, it would be drastically more complicated to maintain and + support due to combinations of different versions and it would cause complications for + the hardening done by GrapheneOS. The motivation doesn't exist for GrapheneOS, since + full updates with deltas to minimize bandwidth can be shipped for every device and + GrapheneOS is the only party involved in providing the updates. For the same reason, + it has little use for the ability to provide out-of-band updates to system image + components including all the apps and many other components.