* changes:
DO NOT MERGE [1.5/N] side fps bouncer - Update UdfpsKeyguardViewControllerBaseTest
1/N sideFPs bouncer, separate altBouncer callback
Refactor file from java => kotlin
Bug: 247694441
Test: adb shell settings put global systemui/buffer/ShadeLog DEBUG echoes the logs to logcat
Test: adb shell settings put global systemui/buffer/NotifHeadsUpLog DEBUG echoes the logs to logcat
Test: adb logcat -s "NotificationStackScroll:*" "systemui.shade:*" shows
these added logs
Change-Id: I85c6402da9417e637cdb61ae05de9b7cfa7297de
Creates new setting on SFPS to require screen on before unlocking a
device. Also sets up toggles for this setting at the end of fingerprint
enrollment and on the fingerprint settings page, and adds test to verify
expected behavior.
Test: atest KeyguardUpdateMonitorTest#testStartsListeningForSfps_whenKeyguardIsVisible_ifRequireScreenOnToAuthEnabled
Fixes: 249169615
Fixes: 245343077
Fixes: 248530806
Change-Id: Ibc55dfa6667ec281add11a2665fceb073974ccb0
Merged-In: I4aa716fb5b288ef6f92a5c403a1fd5e586e889d0
It shouldn't run tests on its own. Only its
extending classes should run.
Test: atest AAAPlusPlusVerifySysuiRequiredTestPropertiesTest
Bug: 237362467
Change-Id: Ib03445206098949c6e0b09a948e4caf92c4b9be3
The issue case is launching an existing embedded activity with
clear-task and then a new activity is started in a new task fragment.
E.g. resume left panel -> finish right panel -> create right panel.
And the transition starts until the right panel is drawn instead of
the drawn starting window. That would feel a noticeable delay.
This is mainly for showing starting window on a task with embedded
activities, but also generalizes the common cases.
1. Move mSharedStartingData from ActivityRecord to Task.
So if there is a new embedded activity launched in the task, it
doesn't need to take care whether/when to assign the field. And
no need to traverse all embedded activities in the task to make
sure the shared starting data is up to date.
2. Move startingDisplayed from ActivityRecord to StartingData.
The state of flag startingDisplayed is covered by the lifetime
of StartingData. So it no longer needs to reset the flag.
This also provides the ability to know whether the starting
window is drawn or not without based on an activity or window.
With above changes, any activity without owned starting window can
know if the shared starting window is ready to execute transition.
Also use a non-empty reference activity in createRemoteAnimationTarget,
so the OPENING transition animation won't be skipped (the right panel
is the top non-finishing activity but it hasn't a child window yet).
Bug: 255688302
Test: atest ActivityRecordTests#testStartingWindowInTaskFragment
Change-Id: I7adeed8801ea3a837afa3d46f1975cf6c5b3f99a
Divider size and insets value might be changed when config changed,
we should update them too otherwise divider would keep same area
on SplitLayout but actually view area become small or large.
Bug: 256117210
Test: manual
Test: pass existing tests
Change-Id: I6532f41c58848797f14ae17cb26f1ae734c53573
ActivityGroup has been deprecated since Android H, but there are still
apps using it. When it is used, the child Activity will not have its own
corresponding ActivityRecord. If we treat it as normal Activity, there
will be issue because we can't find Task with its token, nor reparent it
with its token.
Skip child Activity (the one launched in ActivityGroup) for any
lifecycle event.
Fix: 256533615
Test: manually verify
Change-Id: Ibccf1575c3b229a0912f843f6468a6c3e24a893f
This specifically refers to the taskbar that can be expanded or
minimized, which changes the bottom inset, but PiP remained in it's
original position. This change will move it down if it was already by
the bottom edge, or move it up just enough to be within the movement
bounds.
Bug: 256560961
Test: manually
Test: http://recall/-/ekEuGtt9d9HWqkUtAzpHx8/dSTq2oAg1k85bpIZRBDLIH
Change-Id: I487be6f54b2f9afae8d18df8cf6456858704c703
The AltBouncer callback should only
handle events relevant to any alternate
bouncer (ie: show and hide). Other callbacks
like setQsExpanded and onTouch should be moved
out to a different callback since they're not
relevant to all alternate bouncers.
This CL also converts UdfpsKeyguardViewController to
kotlin and, when the modern bouncer is enabled,
uses the BouncerInteractor for the bouncerExpansion
to determine whether to show the UDPFS affordance
or not.
Test: atest UdfpsKeyguardViewControllerTest
Test: atest UdfpsKeyguardViewControllerWithCoroutinesTest
Test: wallet activity shows udfps affordance
Test: tapping home controls affordances
shows udfps bouncer
Test: tapping notification w/ intent shows
udfps bouncer
Bug: 237362467
Change-Id: Ibb9b55e6b1a629e28f523ac62058f7e5cf40faed
Merged-In: Ibb9b55e6b1a629e28f523ac62058f7e5cf40faed
Change file name in its own CL to preserve the history. This CL
should only be merged with the followup CL.
Test: See ag/20272142
Bug: 237362467
Change-Id: Ic598a4ad88aa64d05d90e66d0f07cb7eb06c76cd
Merged-In: Ic598a4ad88aa64d05d90e66d0f07cb7eb06c76cd
This reverts some logic for setting the touchable region that was made
in ag/17050822.
Bug: 254681548
Test: presubmit
Change-Id: I929dd28c782992445882a2d61105aa3e5a0a99bc
(cherry picked from commit 3823c8c062)
