The current shadow of the cast icon is darker because the two shadows
were blending together to darken the shadow. The text's shadow is not
blended.
Bug: 257997891
Test: Manually tested
Change-Id: Ia371bbeb9859a224da134770c7e99c4556960a6c
Before, when there is no ActivityEmbedding, the transition is requested
later when the previous top Activity is paused to resume the Task top,
which works ok. But when there is ActivityEmbedding, the organizer may
request WCT that trigger visibility update before a transition is
requested, which cause a flicker.
When startActivity with FLAG_ACTIVITY_REORDER_TO_FRONT to bring an
existing activity to the front, we should call prepareAppTransition
early to make sure the following activity visibility change is tracked.
Fix: 255701223
Test: verify with FLAG_ACTIVITY_REORDER_TO_FRONT app
Change-Id: I65d4ffd1c17d6817c073122447e620a2fbb514a1
The clock complication comes with internal paddings that make the
spacing with the complications below too large, even without any layout
engine margin. Without a better solution, add a y translation to the
clock so reduce the spacing, and also change its text size to dp unit
so it doesn't respond to system text size change, which would mess up
the translation.
Test: https://screenshot.googleplex.com/BLfQEhA6i2t4qyu
Test: https://screenshot.googleplex.com/BbuvDvfmahtNy5U
Bug: 257553229
Change-Id: I7350981a28af590f6e70fb4fab004d5180cda502
This change adds a new attribute in the complication layout params to
allow constraint on width or height, depending on its direction.
Smartspace is added a constraint width so not to overflow.
Bug: 258455314
Fix: 258455314
Test: atest ComplicationEngineTest
Test: atest ComplicationLayoutParamsTest
Test: on device create a meeting with a long title and see that
smartspace does not overflow
Change-Id: Ie5a1278810ac77a8aa3f0046970642919c46f7ed
- update complication weights so home controls, media entry chip, and
smartspace are always shown below the clock
- instead of applying the bottom padding to home controls at the layout
engine level in order to center align with smartspace, apply to the
home controls chip view, which prevents the layout engine from giving
an exception to adding padding to a root node
Bug: 259264239
Bug: 259719867
Test: https://screenshot.googleplex.com/BZNatvxHFHxqxaS
Test: https://screenshot.googleplex.com/9gxsLUZWTFy7sGX
Change-Id: Icfcc3653ad7eb52e707c8289803188388484666e
Test: Verified the api can now be called when the phone is not locked
down.
Bug: 245778799
Change-Id: I0f0ee0d33312efc4b27fe6d525c7500d366fb3dc
Merged-In: I0f0ee0d33312efc4b27fe6d525c7500d366fb3dc
The methods ShadeController was calling in CentralSurfaces are now
in ShadeController. A small amount of interaction between the two
classes had to remain, but it's now a small interface instead of a
direct dependency on CentralSurfaces. This work is far from done,
but the dependency was removed and atest passed, so it seemed like
a good place to stop and review.
Bug: 249277686
Test: manual and atest
Change-Id: Ide5c6f1964a83073f39323c083ea1ccc281bc8fe
Fixes the problem about launching a letterboxed app
from home having the "App isn't installed" message.
Fixes: 260188035
Test: Launch apps from Home and check they all start without the
"App isn't installed" message
Change-Id: I2cd2059933b33b13a0958ed410757373ca77611d
Since WallpaperController won't change wallpaper target if the
closing target is in transition, the adjustWallpaperWindows
won't change any state when transition is ready but spend the
time to traverse.
The entry points from AR#setVisibility->requestUpdateWallpaperIfNeeded
and transition finish->commitVisibility->postApplyAnimation
->FINISH_LAYOUT_REDO_WALLPAPER are already enough to update.
Bug: 260059642
Bug: 258880446
Test: WallpaperControllerTests
Change-Id: I6b48099c455c2987c74b31b9d6d7d06d484a7c56
(cherry picked from commit 46332a8e65)
Current implementation only returns the Volumes for the current user.
In case of Cloned user this causes issues as Cloned user uses Media
Provider of User 0, thereby returning only Volume 0, causing problems in
assigning projectIds, and affecting storage calculation.
The projectId assignement happens via
MediaProvider.updateExternalStorageFileQuota.
Bug: 235321217
Test: atest android.appsecurity.cts.StorageHostTest
Change-Id: I617bae9b201fd66d7b62b6cbd1c48b9f276f1924
(cherry picked from commit 4e65c53b43)
Merged-In: I617bae9b201fd66d7b62b6cbd1c48b9f276f1924
Originally, if the window container can not be animated or controlled
by remote, the intermediate ChangeInfo are just ignored during
calculating TransitionInfo. So they can be skipped earlier at creation.
For example when launching an activity in a task, there may be 10
ChangeInfo: 2 activities + Task + TaskDisplayArea + Display +
5 DisplayArea.
With this change, the 5 DisplayArea will be ignored (if their
organizers are not active): Root, WindowedMagnification,
HideDisplayCutout, OneHanded, and FullscreenMagnification.
Then in collect(), it no longer needs to traverse 30+ DisplayArea
for creating the intermediate parent ChangeInfo. That would also
speed up calculateTargets and calculateTransitionInfo because
less ChangeInfo to look up.
Also simplify getTopVisibleWallpaper (called in collect()) a bit by
eliminating unnecessary overhead of forAllWindows.
Bug: 260059642
Test: atest TransitionTests
Change-Id: I15f3ccd5af2fe70f71c88d6d8676661c312aef2e
Requested override configuration can be adjusted in Core when some
policies such as task min size are applied.
Bug: 185427982
Test: SplashScreenTests#testSetBackgroundColorActivity_FreeformWindow
Change-Id: If9fb9e26fff9cfe448e0b8fdd87e13429ec63f87
1. setReady may be called multiples times from
WindowOrganizerController#startTransition and
DisplayContent#executeAppTransition. If the state is the same,
there is no need to request traversal.
2. When collecting a change if the group is not ready, the
visibility, config, lifecycle events and setReady=true will
trigger traversal as well.
Bug: 260059642
Test: atest SyncEngineTests
Test: Start next activity and finish current activity.
The slice of trace "finishActivity" should not contain
"performSurfacePlacement".
Change-Id: I8cc0c70bb8c2da504cc53379ea107c13d8bdd197
This also fixes issue with rotating on tablets where PiP might go out
of bounds.
What happens is sometimes the rotation of screen has not issued the
callback yet and onInsetsChanged gets called causing regression and
mixing up all calculations based on the configuration change that
is being applied too early. Basically ordering issue of callbacks.
Bug: 254869973
Test: manually, tried with logs statements that confirmed it works as expected
regardless of the order in which the events callbacks are received
Change-Id: Ie1ac5e94559643028229c7829b35905b175425d2
There is no need to insets the divider bar with taskbar when IME showing
because there are no rounded corners at the bottom. This also avoids the
problem of task bar height not changing when IME floating.
Bug: 257011088
Test: Manual check the task bar does draw to bottom when IME floating
and restore when IME hidden.
Change-Id: Iba5bbf5247e34f0063e67ddcd0a0b3deb8f772fb
This reverts commit 16dc6c68f7.
Reason for revert: Testing tablet specific failure seen in b/260618001. This is part of DM+Platinum monitor rotation. The revert won't be submitted if proven otherwise.
Change-Id: I73a2d5a871f714fdfe15d55af9cc52a5f295452c
Bug: 259724339
Test: atest DockObserverTest
Test: flashed and factory reset, then verified dock state gets updated after setup
Change-Id: I71d99d69d4592f8bf3c261494053a8b9470f8f4d
* Previously we were only initializing nav mode for
EdgeBackGestureHandler and never updating state in
TaskbarDelegate
Fixes: 260226345
Test: Wrote new tests,
killed sysui process and dump state in terminal and
observe nav mode matches between NavigationModeController
and TaskbarDelegate
Change-Id: I637fbf759ab86cd9ff25875e24dca9327fee35fa
