Currently mResizedWhileNotDragResizing flag is not cleared after
reporting resize to client, which causes sending lots of resize
messages and relayouts on app side.
This CL introduces another flag to track reporting to app.
Bug: 28696195
Change-Id: Ib5b6ea3e5f499c96057182f4b20583734dea56c4
- Added ActivityOption to mark a starting activity as a taskOverlay
activity. That is the activity will always be the top activity of the
task and doesn't cause the task to be moved to the front when it is added.
- Only set the starting window state of the ActivityRecord to shown if
window manager actually showed the starting window for the activity.
Avoids incorrectly trying to remove starting window for an activity that
didn't show any.
- When starting additional activity in a task, transfer the starting
window from the top most activity with a starting window. It is possible
the top most window does have a starting window like in the case of the
forcedResized activity.
- Only ensure visiblity of an activity we are starting in a task whose top
activity is a task overlay. They need to start in the visible-paused state
and not the resumed state which just causes extra churn in the system.
- Always add additional starting activities in a task with an overlay
activity below the overlay activity.
Bug: 28751186
Change-Id: I3624a4313ae9c406d42c67a3537f67ad685791af
We need to incorporate task bounds when calculating the inset hint
so we don't specify something wrong to the client which we correct
immediately after.
Bug: 28697105
Change-Id: I23cec7d6cc62a4d982e0796a867e803d4cce0803
Previously we were only updating configuration for the top activity in
the stack during resizing. This caused an activity behind the top
translucent activity to continue to display in the old configuration
and also get relaunched without window preservation when the top
translucent activity is finished.
We now make sure all activities at all below a translucent activity
have their configuration updated during resizing.
Bug: 28762547
Change-Id: I0926ac6db088cdf3f6a225c552dbfbe944830f68
The background bounds were not correctly applied
when an animation was running, leading to flickers
of the scrim. Left and right should always be applied
immediately.
Change-Id: Iff9979d6e1c472a1dec20e76436a19a44c170cad
Fixed: 28000150
When clicking on a suppressed child and the child is autocancelled
we need to cancel the summary as well for them if it also has
the flag to auto cancel.
Change-Id: I25bfa7ad79afd406cc647ad6683d0b49c949f909
Fixes: 28642637
am: 0b019a3d02
* commit '0b019a3d028990a9832188d3ef2c9540e5d37f40':
Avoid weird line wrapping by removing columns and forcing line breaks between the links
Change-Id: Ifba667194d2e2f04a9824945d5100cdea01a9c77
am: 592b36a326
* commit '592b36a326216cd2442c47da9608ca2afd7e4d16':
Avoid weird line wrapping by removing columns and forcing line breaks between the links
Change-Id: I54b1282f6ef2d92251a4624c8f439499831af1a6
We were not keeping track when an app that set an app op restriction
dies to clean up after that. As a result we may end up with stale
restrictions that will be there until the device reoots - not cool.
This change adds remote binder death tracking and simplifies the
code as adding the formed would have made more complex.
bug:28770536
Change-Id: I7dcaafba2354843a0cdf0206ab1f96625edc5120
am: a0acf474e9
* commit 'a0acf474e9db6e1a444d7e48b520b48ded8fcdce':
Avoid weird line wrapping by removing columns and forcing line breaks between the links
Change-Id: I337e5167eb9191f674c6cc397d61925c334c3b72
But make sure that we don't allow Shell or other apps
to disable an active profile or device owner.
Also limit exactly what states Shell can switch apps
between, similar to Settings UI.
This is required for some CTS tests
Bug: 27924655
Change-Id: I958f0d1de7f0bc1f5a0cbf853d57dfdeb2f9ad59
This allows the launcher to know how to handle HOME press properly
when a video is playing in the background. Without this, the Launcher
dismisses it's UI.
Launcher CL: https://googleplex-android-review.git.corp.google.com/#/c/1043435/
BUG: 28173127
Change-Id: Iab0c5013fc41f79a6fd45f49904edd0d0f9c17ff
Sometimes, a persistent app should be the top app (recents). Make sure
such an app can use the top-app cpuset.
bug 28317812
bug 28794389
Change-Id: I756cec3fbab8cc552a6d90c007aa2e07f6b78dbc
TRIM_MEMORY_UI_HIDDEN > TRIM_MEMORY_RUNNING constants, so we only
need to throw away the wallpaper if we are actually running low on
memory.
Bug: 28769940
Change-Id: I8aa27d081bbcc2eff553e9420b2b9b0920f3781f
- Move logic to determine app switch etc. into ActivityMetricsLogger.
- Make sure the notify the tracker in startActivityFromRecentsInner
Bug: 27295491
Change-Id: Ic68058c88917e3f37183dded2f13cb35055323ee
