The opaque flag is necessary for the compositor to blend the layers
correctly and prevent translucent pixels from showing the layer
underneath during animations.
Test: manually punch holes in apps and verify opaque apps don't show the layer underneath
Test: automated tests to follow
Bug: 198924563
Change-Id: I1116c51b2efd4e9c0fe2acbca080291f3950245c
After the device is setup, if the smartspace component is not
available/initialized, don't attempt to start a session.
Fixes: 199986217
Test: atest LockscreenSmartspaceControllerTest
Change-Id: I36d6f75b37cc5f5274b1cea3a35338f6da424a20
(cherry picked from commit 076aad912e)
There was discrepancy between how null values and empty strings were
treated in KeyguardIndication and KeyguardIndicationController. This
could lead to a crash in systemui. Modify the
KeyguardIndicationController to match the logic in KeyguardIndication.
Bug: 201339576
Test: KeyguardIndicationControllerTest
Change-Id: I8b7b4d7b33b1ee809df17e64347c816f65a50727
Make sure to traverse all organized parent tasks when dispatching task
info chagned after committing activity visibility. Remove queuing task
info changed in Task#ensureActivitiesVisible because it is not actually
committing activity visibility.
Fix: 200139190
Test: pass existing tests
Test: manual check the repro steps in bug
Change-Id: I869dfa85c4e488e20b4dc7aa1a77d258362081b6
Removes activity launch flags that cause the injected location settings
to launch in a new task. This improves animations and settings support
for different form factors.
Fixes: 197608838
Fixes: 197608555
Test: manual
Change-Id: If2deb44058f7d7786a27310d4430f2e83879baa9
To enable more voice-oriented in-app user journeys, Google Assistant
needs to access more information regarding the visible activities
via the Voice Interaction Session. Thus, we provide the APIs to receive
the changed visible activities in Voice Interaction Session.
Bug: 178244510
Test: atest CtsVoiceInteractionTestCases
Test: atest CtsVoiceInteractionTestCases --instant
Change-Id: I019d09fee8105ae1eadbc76803f46fd8b1948f6b
* changes:
Extends to support the restricted setMaxHeight() for illustrationPreference.
Fix the bounds of the illustration view is larger than the background view in a foldable device.
When the snapshot surface is created, it should remain at its
original position.
When the animation starts, change animation bounds should be at the
start bounds relative position.
Bug: 196173550
Test: atest WmTests:RemoteAnimationControllerTest
Test: Test with demo app full -> split with RTL enabled.
Change-Id: I3cb44e1f222870f51105bfaa98fc4febaafec03b
Fix issue where the initial snapshot used to create a
resultant SkImage instance with an SkImageFilter applied
was not initialized.
Fixes: 201312688
Test: Re-ran CTS tests
Change-Id: I2440a161c70076850479c562c7c9e6dc8d756236
Because the background attribute used to have a different use some apps still set it and it means we could run transitions with unexpected background colors
Test: Existing
Fixes: 200763116
Merged-In: Id42f52760cb9a681c6c33f3c261d7db5e2f71af3
Change-Id: Id42f52760cb9a681c6c33f3c261d7db5e2f71af3
See bug comment #9 for an in-depth explanation.
Test: New unit tests.
Test: I created a test app that sends an ongoing call notification
then removes it 200ms later, and I confirmed that the bug is triggered
without this CL, and is fixed with this CL.
Bug: 199600334
Change-Id: I0f681ccfe55597490bee0d4b190f9fb2c38e28f2
(cherry picked from commit cd755525c4)
Merged-In: I0f681ccfe55597490bee0d4b190f9fb2c38e28f2
