This contains the change to show a different fragment on private space
creation error based on the error code returned by UserManager.
On private space create error checks for the returned error code and if
PS is not supported on the device showns error screen containing a link to Help
Center atricle to find out more about the reason for profile creation
failure.
ACTION_PRIVATE_SPACE_SETUP_SPACE_ERRORS metric is logged with the error
code on create error else 0 on sucessful space creation.
Recording: b/340130375#comment17
Bug: 340130375
Test: Manual
Flag: android.multiuser.show_different_creation_error_for_unsupported_devices
Change-Id: Ifa0345fb6aad64599009f8aa79d168f57fd35c03
Enable/disable the search tile content and hide illustration
in Hide Private Space Settings page based on the config value.
By default the config value is set to true which will be used in Pixel
to show the illustration and search tile content.
OEM can set value of config_enableSearchTileHideIllustrationInPrivateSpace in the device
overlay file to false to disable it and with this change it is taken
care to hide them if the config value is false
Screenshot:
go/ss/56WxtgXd5NSqVFm.png
Bug: 346612477
Test: Manual
Flag: android.multiuser.private_space_search_illustration_config
Change-Id: Ia9fbdebd9a220f4d995369d662a75989f07a2916
With this change when secondary unlock factor for private space is
initiated from settings page only the option to set traditional unlock
factors will be shown and biometric option will not be shown.
User will return to private space unlock settings screen. User should be
able to manually set up biometrics form its dedicatated settings entry
point after authentication.
Recording:
b/332850595#comment7
Flag: android.multiuser.modify_private_space_secondary_unlock_setup_flow
Bug: 332850595
Test: Manual
Change-Id: I8feb8c23300ddb537c428f3675178c5ff49932d1
This change removes the TODO comment that was tracking to move over to
Biometric intent KeyguardManager.createConfirmDeviceCredentialIntent.
The hidden KeyguardManager.createConfirmDeviceCredentialIntent is being
used by various frameworks clients and is still avialable for use in settings.
Bug: 304796434
Test: Manual
Flag: EXEMPT removing todo
Change-Id: I5566d56e743e88afbcca0c4167c8a797e41b1a97
Change made to fix accessibility issue for talkback to announce correct
number in the list numbers as suggeste in b/333672369#comment4
Bug: 333672369
Test: Manual
Change-Id: I7f4ed0b39a40040c1185809e0b348d12e1eabf29
Fix for Null pointer exception to add null checks before calling
unRegisterReceiver for broadcast and startActivity.
Bug: 346233086
Test: Manual
Change-Id: I0941c34c3f5912c57abc9497809962ed0954ac06
This reverts commit 5fd6d6435b.
Reason for revert: As per b/343166689#comment4 this change as this is not needed based on the feedback from leads review.
Change-Id: Iad31aafbce5f3f9fc37fdd8fb4d5582cfae9d8b7
With this change the temp GAIA education screen is removed from private
space setup code and adds a new loading screen with "Just a sec" title
in the activity while the gms intent in launched to fix blank screen issue.
Screenrecording link:
b/336822960#comment7
Bug: 336822960
Test: Manual
Change-Id: I9ee41835b39c194fefb970321b7a9d5a30f87306
All activities that use biometric login through the CDCA class show a
Settings icon in the prompt. This cl adds a capability for the client of
the CDCA to set icon and icon description as extras to the unlock
intent.
Screenshot: http://shortn/_OpKTYFtddM
Bug: 333528540
Test: Manually verified on the device
Change-Id: Id7b5a3fe575069bef1810769e4f437e717d2d3c6
Currently, the changes to disable private space settings app component
are located in SettiingsInitialize.java. These get triggered when
ACTION_USER_INITIALIZE is received by the settings app inside the
private profile user. However, we are stopping the private profile user
at the end of the setup flow. This can lead to a scenario wherein
ACTION_USER_INITIALIZE is relayed by the system server but not received
by the private space settings app, since it was stopped. To over come
this issue, we move the changes to disable the private space settings
app component inside the private space setup flow (right after the user
is created and started).
Bug: 342165140
Test: atest PrivateSpaceMaintainerTest#createPrivateSpace_psDoesNotExist_setsPrivateSpaceSettingsComponentDisabled
Flag: ACONFIG android.multiuser.enable_private_space_features NEXTFOOD
Change-Id: Ib9baac1e9d835ea5a27c15d499e10615b84cf97b
Add a footer note to private space auto lock settings page that apps in
private space may need to be authenticated unlock when a separate lock
is set for private space.
Screenshot:
go/ss/7fE8epun3A2hgq4.png
Bug: 343166689
Test: Manual
Change-Id: I18c650eba128da512116a3166babb49f7ef33bb3
After creation of private space value of auto-lock setting is explicitly
set to lock on device restarts. Just before the end of the setup flow
the auto-lock setting is changed to auto-lock on device lock before the
last screen of private space setup.
Bug: 342398315
Test: atest PrivateSpaceMaintainerTest
Change-Id: I8eeb0058c7ecb31d6e30b4cc78ec5877ed316f75
Currently we fire ALL_APP intent for System Launchers at the
end of PS setup flow, even when the system launcher (NexusLauncher)
was not the default Launcher.
In such cases, the user is moved to NexusLauncher, but they cannot
unlock PS (only default launcher can do it), leading to crashes.
To fix this, we do not fire the intent in case non system Launcher
has the HOME role.
Bug: 331722929
Test: Manual build and flash
Flag: NA
Change-Id: I77353474cc74028d72508c433c89b6116b4148bd
so that the correct colors are applied when the system contrast is
changed.
Bug: 335712994
Test: manual
Change-Id: I2f6ba3360fc4935db302e8d89f4df8d200a43a29
This is a regression caused by ag/26661827
Fix: 333872544
Test: manual
Test: atest PrivateSpaceSafetySourceTest
Change-Id: I0465899af3745fa39eab8806dbceb347d70b0aa3
When private space is deleted from private space settings launched from
the All apps settings cog the settings sub activity is not cleared and
visibile in recents.
With this change it is taken care to remove and clear the sub settings
task hosting the Private space settings page when private space does not
exist and to make sure the activity is removed if it is the last
activity in that stack.
Bug: 333538964
Test: Manual
Change-Id: I22ba8ca8d2947c6604280cf398cd47434038d542
This change sets line break strategy and the max lines limit for the
private space setup choose lock screen header
Screenshot:
go/ss/8CFXUAUkKXAZiPM.png
Bug: 331538317
Test: Manual
Change-Id: I8c8bd8d130dc0d61d050d274ac0b734a6c5e3d21
With this change logs which can reveal private space existence when
private space is locked are removed.
Bug: 334040689
Test: Manual
Change-Id: I09e01db839569ca5cc995b72ece6fe25916788a8
This change takes care to launch the private space setup in whole screen
on Fold device whenever the device is unfolded.
Screenshot: go/ss/6D9EwMaLp7LFbsH.png
Recording: b/324260315
Bug: 324260315
Test: Manual
Change-Id: I5bc7b7c8fbc880b6274ddd287a8a169b49843f1b
With this change the value of Secure settings SKIP_FIRST_USE_HINTS is
set for private profile after creation of profile in PS setup flow.
The value is set for the profile user so that first launch of an app in
private space will not display introductory hints.
Bug: 325596557
Test: PrivateSpaceMaintainerTest
Change-Id: I63a967bba052a3dcb4742c95b89c6da19aba74d5
This includes to verify return value of startProfile to check if profile
is started successfully. If startProfile failed for any reason then
delete the created profile and return false for createPrivateProfile().
Bug: 313926659
Test: atest PrivateSpaceMaintainerTest
Change-Id: I493cb3a41cef8bdc1be42fe328c4f7bd04944b94
