Most other connections made by the OS itself are made based on your chosen carrier. The OS has a database of APN and other carrier configuration settings diff --git a/static/features.html b/static/features.html index 72b6cb0b..d862c36d 100644 --- a/static/features.html +++ b/static/features.html @@ -602,7 +602,8 @@ data due to being denied, GrapheneOS creates a notification that can be easily disabled. The Sensors permission can be set to be disabled by default for user installed apps in Settings > Privacy.
+ then">> Security & privacy > More security & privacy.The wipe does not require a reboot and cannot be interrupted. It can be set - up at Settings > Security Settings >Security & privacy > Device unlock > Duress Password in the owner profile. Both a duress PIN and password will need to be set to account for different profiles that may have different unlock methods.
diff --git a/static/usage.html b/static/usage.html index aedf644e..b7a36b0c 100644 --- a/static/usage.html +++ b/static/usage.html @@ -376,7 +376,8 @@GrapheneOS disables showing the characters as passwords are typed by default. You can enable this in Settings > - Privacy.
+ Security & privacy > Privacy > Show passwords.Third party accessibility services can be installed and activated. This includes the ones made by Google. Most of these will work but some may have a hard @@ -813,8 +814,9 @@ for each boot via the shared randomized values.
This feature can be disabled via Settings > Security > Secure app - spawning if you prefer to have faster cold start app spawning time and lower + then">> Security & privacy > + Exploit protection > Secure app spawning + if you prefer to have faster cold start app spawning time and lower app process memory usage instead of the substantial security benefits and the removal of the only known remaining direct device identifiers across profiles (i.e. not depending on fingerprinting global configuration, available storage space, etc. @@ -1250,7 +1252,8 @@ prevent inspecting or modifying the app in a weak attempt to hide their code and API from security researchers. GrapheneOS allows users to disable Native code debugging via a toggle in Settings > - Security to improve the app sandbox and this can interfere with apps debugging their + Security & privacy > Exploit protection + to improve the app sandbox and this can interfere with apps debugging their own code to add a barrier to analyzing the app. You should try enabling this again if you've disabled it and are encountering compatibility issues with these kinds of apps.