[automerger skipped] [RESTRICT AUTOMERGE] Trim the activity info of another uid if no privilege am: 02382b56 -s ours am: 975805ba -s ours am: 40a630ab -s ours

am skip reason: subject contains skip directive

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20532949



Change-Id: Idaa55fbec036865b75680b1b13a12c506ed37d7e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

* changes:
  Remove smartspace offset
  Bouncer - Fix activity launch

[automerger skipped] [RESTRICT AUTOMERGE] Trim the activity info of another uid if no privilege am: 02382b56 -s ours am: 975805ba -s ours

am skip reason: subject contains skip directive

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20532949



Change-Id: I8e99bf9c9196a06b8e614313280888482e90c5e1
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

[automerger skipped] [RESTRICT AUTOMERGE] Trim the activity info of another uid if no privilege am: 02382b56 -s ours

am skip reason: subject contains skip directive

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20532949



Change-Id: I5c34b698b41a2fa638d689fb6400e60ca8927600
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

End-to-end implementation (across all layers of both System UI and the
shared library) for supporting a picker state for affordances, allowing
config implementations on the system UI to easily convey whether their
affordance should be hidden on the device or should be marked as
disabled and show a dialog with instructions for re-enablement.

Bug: 256695447,256695925,256695924
Test: unit tests still pass. Was able to see on a tablet that doesn't
support NFC that wallet is gone as an option and, when I deselected all
home devices, the home affordance was disabled with the correct
instruction dialog when picked. Then, marking at least one home device
as favorite, the picker allowed me to select "home" again.

Change-Id: I77637f28cdacecaa02ab33603bbc008a501d03d1
Merged-In: I77637f28cdacecaa02ab33603bbc008a501d03d1

Test: treehugger
Bug: 253647225
Bug: 258031539
Bug: 259884346
Change-Id: I43fdeaf2a308c11abf1064652e3fd11f5aec0e54

Bug: 259549854
Test: manual
Change-Id: I94617054d9b074f8f95e8d534aeb9df5d325436d

For foldables, the smartspace content is too low when the large clock
is showing. Move up to provide a bit more space.

Fixes: 245614151
Test: manual - review layout for wide devices
Change-Id: I4dff7875a7872db979e1cca3fcb1e9d5ed2fd056

Additionally log whether unlocking was allowed when
BiometricUnlockController determines which unlock MODE
to use.

Also log additional fingerprint errors in
KeyguardUpdateMonitorLog.

Test: adb shell settings put global systemui/buffer/BiometricLog
Bug: 250392997
Change-Id: I3b87325f7fdeb3a0d53a2573cd6aae93907bb81c

New versions of ConstraintLayout can optimize the constraint set. In this test we were asserting that two constraintsSets were the same despite being specified in different ways (in different xmls).

version 2.2.0-beta05 ended up optimizing some constraints, making the test fail, despite no (apparent) visual differences.

Bug: 259933125
Bug: 259261262
Test: presubmits
Change-Id: Icaf6691865b286e960374eae9d3588e13a1087ab

The bouncer view delegate was not being created soon enough, resulting
in the dismiss action being dropped and not run after a succesful
auth.

Fixes: 259666226
Test: manual, follow steps in bug
Change-Id: If2dbfc35379d6c1b0f46575ab9e4e4bb0769ce6f

Some unresizable apps are launched in freeform in freeform display,
but the override windowing mode of this task needs to be left
UNDEFINED. Otherwise, the task would remain freeform even when the
display transitions from freeform to fullscreen.

On the other hand, fullscreen unresizable apps need to remain
fullscreen regardless of the windowing mode of the display.

Also, with this CL, the same unresizable policies are applied in
fullscreen display too as the display could be freeform later
anyway.

Bug: 185427982
Test: atest WmTests:TaskLaunchParamsModifierTests
Change-Id: I7279be115d88731566c19be691ff562d5885a3af

The activity info could be from another uid which is different
from the app that hosts the task. The information should be
trimmed if the caller app doesn't have the privilege.

Bug: 243130512
Test: verified locally
Test: atest RecentTasksTest
Change-Id: Ia343ac70e5bb9aeae718fca6674e1ca491a14512
Merged-In: Ia343ac70e5bb9aeae718fca6674e1ca491a14512
(cherry picked from commit fa8d6362)

Will accept setVisibilityChanged#isNotVisible. When dream appears, for whatever
reason, expansion is set to 0 which is BOUNCER_VISIBLE. This propagates
FULLY_SHOWN to callback listeners (for both with feature flag off and
on). In the same code path, bouncer#hide is called. The difference
between the old bouncer and the new bouncer is that visibility was
conflated so because the bouncer was already invisible, we did not
propagate this data to the callback listener that visibility is hidden.

I have separated this callback from when we set visibility with the
actual state flow. Instead,
call setVisibiltyChanged whenever show() or hide() is called for the
interactor.

Fixes: b/259081158
Test: Added a unit test.
Test: Set screen saver and show screen saver when charging. Open screen
saver a bunch of times from unlocked state and locked state to observe
that touches are not lost. I have observed the bug behavior without my change.

Change-Id: I56d535c0422337f09f009960d8e4117ec30ae9c1

Merge "Update dream battery drain monitoring to exclude when charging is being artificially limited." into tm-qpr-dev

Before, when TaskFragmentOrganizerController#onTransactionHandled()
is called, we will always call #validateAndGetState(), which call throw
an exception for racing condition like organizer process died.

Bug: 207070762
Test: atest WmTests:TaskFragmentOrganizerControllerTest
Change-Id: I04d37ecab4a37a616167ce4e6ca98c668f1254da

The current implementation doesn't allow changing the default
launch size when it doesn't fit the display. However, lots of apps
have important UI pieces on top or bottom, so having a window height
larger than the display height can degrade the usability of such
app a lot.

More and more laptops have horizentally longer displays these days,
so this problem is getting more common. I think any adjustment
will be small enough not to affect apps' layouts much. Also, this
logic cannot make the app smaller than the min sizes defined by
the system or apps.

Bug: 185427982
Test: atest WmTests:TaskLaunchParamsModifierTests
Change-Id: I53171bba183e5f00be3118d41c57731b5e3d5e19