security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

Pixel 4a is released

Browse Source
This commit is contained in:
Daniel Micay 2020-08-13 06:56:16 -04:00
parent aa14116973
commit fbea64c1ef
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
static/faq.html
View File

@ -167,15 +167,16 @@
USB-C audio.</p> USB-C audio.</p>
<p>Support for the Pixel 4 and Pixel 4 XL is currently less mature, but those along <p>Support for the Pixel 4 and Pixel 4 XL is currently less mature, but those along
with the upcoming Pixel 4a will become the recommended devices due to longer support with the Pixel 4a (once it's supported) will become the recommended devices due to
and incremental security improvements for the device support code and firmware. On the longer support and incremental security improvements for the device support code and
Pixel 4 and 4 XL, support for fingerprint unlock as a secondary unlock mechanism has firmware. On the Pixel 4 and 4 XL, support for fingerprint unlock as a secondary
been removed and replaced with IR-based 3D facial scanning. GrapheneOS plans to extend unlock mechanism has been removed and replaced with IR-based 3D facial scanning.
secondary unlock support with the option of 2-factor authentication using a secondary GrapheneOS plans to extend secondary unlock support with the option of 2-factor
PIN or passphrase required for fingerprint / face unlock. It's likely this will be authentication using a secondary PIN or passphrase required for fingerprint / face
implemented first for fingerprint unlock, so that's another consideration. The Pixel unlock. It's likely this will be implemented first for fingerprint unlock, so that's
4a will likely have a fingerprint scanner instead of the dual infrared face scanning another consideration. The Pixel 4a has a fingerprint scanner instead of the dual
cameras.</p> infrared face scanning cameras, so it would share the same implementation as the past
generation devices.</p>
<h3 id="future-devices"> <h3 id="future-devices">
<a href="#future-devices">Which devices will be supported in the future?</a> <a href="#future-devices">Which devices will be supported in the future?</a>