clarification

This commit is contained in:
Daniel Micay 2025-05-19 20:15:27 -04:00
parent a270d639e4
commit b15362157c

View File

@ -602,7 +602,7 @@
<ul> <ul>
<li>add NFC auto-turn-off setting to go along with the existing addition of Wi-Fi and Bluetooth auto-turn-off settings</li> <li>add NFC auto-turn-off setting to go along with the existing addition of Wi-Fi and Bluetooth auto-turn-off settings</li>
<li>Private Space: add new setting for disabling delayed locking of storage to make locking work like secondary user end session, similar to the toggle for disabling secondary users running in the background (standard Private Space doesn't work this way to keep fingerprint unlock available after it's locked/stopped)</li> <li>Private Space: add new setting for disabling delayed locking of storage to make locking work like secondary user end session feature we enable, similar to the toggle we add for disabling secondary users running in the background (standard Private Space doesn't work this way to keep fingerprint unlock available after it's locked/stopped)</li>
<li>Private Space: add new setting for blocking sharing the clipboard to and/or from the parent profile and other nested profiles within it</li> <li>Private Space: add new setting for blocking sharing the clipboard to and/or from the parent profile and other nested profiles within it</li>
<li>Private Space: add support for the Install available apps feature we currently enable to support installing apps available in the Owner user to secondary users</li> <li>Private Space: add support for the Install available apps feature we currently enable to support installing apps available in the Owner user to secondary users</li>
<li>Private Space: add support for secondary users including all standard features with the exception of auto-locking support since our implementation of that is too complex/invasive to properly review and test while we're focused on Android 16 porting</li> <li>Private Space: add support for secondary users including all standard features with the exception of auto-locking support since our implementation of that is too complex/invasive to properly review and test while we're focused on Android 16 porting</li>