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
This inlcudes the changes to use latest private space icon and update
the illustrations in private space setup and settings.
Change made to update illustrations dynamically between light and dark
theme.
Recordings link:
b/332867167#comment3
Bug: 332867167
Test: Manual
Change-Id: I6387c9991ec9bb419f446431926f99843f92c859
This change replaces the auto advancing screens shown during private
space setup flow with a single loading screen.
Recording: b/332652637#comment3
Bug: 332652637
Test: Manual
Change-Id: I470e5c6ece16cfefd0734d3daadf1d8efe963f63
This change adds canAddPrivateProfile() check to enable/disable
Private space delete controller in Reset options.
Matches the availability to delete private space from reset
options with the conditions used to show the private space entry point.
In Settings Reset options preference to delete private space will be
shown only when private space creation is allowed on the device or if
private space already exists on the device.
Bug: 330396315
Test: ResetOptionsDeletePrivateSpaceControllerTest
Change-Id: I63232556f7927aeb07b73e8732bbb8b1d2423456
With this change it is checked if face unlock is supported as a class2
or class3 biometrics on the device.
If face is convenience biometrics then face unlock for
private space controller is not added.
Bug: 329044103
Test: atest UtilsTest and verified Face unlock is not added if face is convenience
Change-Id: I6e1a6557774be1173ad3ee7ff7b14d51f9fe1716
This reverts commit d2c91b587e.
Reason for revert: Landing the original cl as the test passes locally with changes and failed test looks to be flaky and not related to the change.
Failure is not seen in the ABTD test run results with this CL b/331935387#comment10
Change-Id: I744e11a04b70e265c5dcfe5aa8db7237561f3a08
This reverts commit 7b0b26ec92.
Reason for revert: b/331935387. ACA has already verified the revert.
Change-Id: Idf28854f25c4bad3563408dbb7b5c84f0cdbe2f2
At the end of PS setup just before showing the final sucess screen this
change adds a new screen with loading layout which enables profile quiet
mode.
After enabling quiet mode checks if user is stopped before removing the
loading layout screen. Until user is stopped loading screen will be
shown.
Bug: 329042236
Bug: 328393532
Test: Manual verify new delay screen is shown
Change-Id: Iac3fd2f0f5c75a64719fbce32ff4dbfb533322d5
Change is made to show customised icon in Toast message shown by using
Toast.makeCustomToastWithIcon()
Screenshots :
go/ss/AcaRQUJQfh79wDw.png
go/ss/5j4oD8xydwX7HTX.png
Bug: 329391204
Bug: 309575523
Test: Manual
Change-Id: I336d7d0419b1de60024e584e943a725662b446a9
In this change we disable:
1. Security Center Entry point
2. PrivateSpaceAuthenticationActivity
when private profile is not present and cannot be added.
Additionally, the intent exposing PrivateSpaceAuthenticationActivity
is also non-exported and changed to a better name.
Bug: 328578044
Test: Manual build and flash
Change-Id: I13d298316c6d719d0b06e4969989ea1da83dd4c6
This takses care to add an entry point in Settings->System->Reset
options->Delete private space when private space feature is supported on
the device. Entry point appears both when private space exists and also
when private is not created.
On selecting asks for user authentication and on successful
authentication using device lock shows a dialog asking for
confirmation and calls for deletion private space.
Based on this entrypoint it would not be possible to guess if private
space exists on the device.
Recording link : b/329041740#comment3
Bug: 329041740
Test: atest ResetOptionsDeletePrivateSpaceControllerTest and verified
this doesn't give away existence of private space
Change-Id: I9a5b908e7a3f9edaf609cf7e6a87f9842d689ce6
Change to add message in the dialog shown on selecting to choose a new
profile lock for private space.
screenshot : go/ss/ASkBCFJuCzp7dkf.png
Bug: 330218365
Test: Manual. Diaog shown as per UX mock
Change-Id: I17f4d7ebf515dc7c95fcae7a5ec5edeb9918ded3
For private space lock setup as part of both PS setup and separate lock
form private space settings we need to show only traditional unlock
factors and Fingerprint but not show Face enrolment even on devices
where Face unlock is supported by hardware.
Once LSKF is enrolled it should be followed by Fingerprint enrollment
flow and after that Face enrollment should not be shown and exit lock
setup flow.
Currently for separate profile lock setup ACTION_SET_NEW_PASSWORD intent
is used in private space setup.
With this intent the options of LSKF+fingerprint+Face is shown in
devices supporting both fingerprint and face hardware. After the LSKF
ennrollment BiometricEnrollActivity is started which continues with
fingerprint and Face enrollment.
With this change we are passing an extra along with the intent to enroll
fingerprint only. Based on the intent extra value if set even if hardware
support exists the lock enrollment for the profile will support only
LSKF and fingerprint enrollment but not start Face enrollment.
User will still have the option to enroll Face from the dedicated settings
entrypoint in private space settings.
Recording link : b/323839067#comment4
Bug: 323839067
Test: Manual, verified option for face enrollment is shown or not shown
based on the intent extra. When extra is not passed the behaviour will be
default.
Change-Id: Idf92084052e02df9ca89f288c618796750e563e6
This a layer of flag guarding only for the implementation of Private Space features excluding the APIs. The MVP flag allow_private_profile still guards all the features including the APIs.
Bug: 326060689
Test: Manual - a few verifications that some feeatures are unavailable when this flag is disabled
Test: Run presubmits and verify that nothing breaks
Change-Id: I05f7e2f20c6132b33484bb133ce03a933ece485f
