summaryrefslogtreecommitdiff
path: root/static
diff options
context:
space:
mode:
Diffstat (limited to 'static')
-rw-r--r--static/faq.html13
1 files changed, 5 insertions, 8 deletions
diff --git a/static/faq.html b/static/faq.html
index 78ef06ac..b5c83ad3 100644
--- a/static/faq.html
+++ b/static/faq.html
@@ -115,13 +115,10 @@
</h3>
<p>GrapheneOS has official production support for the Pixel 2 (legacy), Pixel 2 XL
- (legacy), 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.</p>
-
- <p>Support for the Pixel 4 and Pixel 4 XL is under development. There is a lot of work
- to do and there is no timeline for these having official production support.</p>
+ (legacy), Pixel 3, Pixel 3 XL, Pixel 3a and Pixel 3a XL. Pixel 4 and Pixel 4 XL
+ support is experimental. 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.</p>
<p>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
@@ -298,7 +295,7 @@
around for compatibility. It used to need more extensive changes such as disallowing
access to the serial number but those restrictions are now standard.</p>
- <p>Apps can determine the model of the device (such as it being a Pixel 3) either
+ <p>Apps can determine the model of the device (such as it being a Pixel 4) either
directly or indirectly through the properties of the hardware and software. There
isn't a way to avoid this short of the OS supporting running apps in a virtual machine
with limited functionality and hardware acceleration. Hiding the CPU/SoC model would