am: 8b788b2194 -s ours
am skip reason: change_id If3f574bc15dedcd7880be605667297d257175c8d with SHA1 89eaa93af9 is in history
Change-Id: I066c4422eb1ae87f0e5943063201466756b3891e
* changes:
Enroll for the correct user
Do not updateActiveGroup on a handler
Launch ConfirmDeviceCredential with actual userId
Settings should be per-profile
The setting is per-user and the source of truth is in BiometricService.
Keyguard's cache needs to be updated when user switch occurs
Fixes: 5268106
Test: Builds
Change-Id: I8a5678375989221e5b502fa683697cf4ca664def
When this code got refactored the check for severe warnings
accidentally had the time remaining being compared against the percentage
value of the severe warning threshold. Unfortunately this meant that
it was impossible to mark the severe level warning as shown and could
result in multiple triggerings. This change makes it so everything
is compared with the appropriate type of value again.
Test: PowerUI Tests pass
Bug: 129730217
Change-Id: Ic8bdabf1c70e49d117210bb80f1ca0a0d7684617
This method must not return to the caller until complete, otherwise
weird race conditions may occur.
Bug: 110907543
Test: Builds
Change-Id: Ia82671b34fac3662928012d8c709143efdf92266
Fixes: 129905318
Bug: 110907543
Test: Set up work profile, use BiometricPromptDemo to allow device
credentials. Work profile demo app now requests work profile
password.
Change-Id: Iec53966c6ad87021fdaa1808a1814a4abfbf89bb
This is a preparation to fix an issue that IME cannot enable light
navigation bar on direct-reply.
The initial state of StatusBar client is provided as return values of
IStatusBarService#registerStatusBar(). However, the way for the
client to receive the return values is to rely on "out" parameters in
the Binder method as follows.
void registerStatusBar(IStatusBar callbacks,
out List<String> iconSlots,
out List<StatusBarIcon> iconList,
out int[] switches,
out List<IBinder> binders,
out Rect fullscreenStackBounds,
out Rect dockedStackBounds);
The issue is that if I want to add a new parameter into
StatusBarManagerService to fix Bug 122439339, then it needs to be
notified back to the client via one of these out values, e.g. a new
element in "switches", which is hard to understand and maintain.
It'd be better to introduce a dedicated return object as follows.
RegisterStatusBarResult registerStatusBar(IStatusBar callbacks);
This is a purely mechanical code clean-up. Hence there should be no
behavior change.
Bug: 122439339
Test: presubmit
Change-Id: Ib1c0ae8f591ca09d0bce7a39f85ba57aad386e47
- Previous logic of checking queue to wait or not has race as queue can be
emptied while posted task is not complete.
- Do not check queue and always wait for new post to complete.
Bug: 129896850
Test: Run the test many times
Change-Id: Ie0e4447cf997cbe343c7e00a8dfd0757b061b547
(cherry picked from commit 819d7406ac)
Expose at most 1 camera ID per facing for all logical-physical camera ID
groups.
Test: Build and read docs
Bug: 113705942
Change-Id: I86a06562eafd600d351d8db2582a613b3323404c