Bug 17412818
Bug 16398271
The Visibility Transition must not run against children that
are already disappearing or there will be, for example, a double
fade-out effect. Before this change, if a parent matched another
view, it would prevent its child from disappearing.
This change also removes using the overlay for children that have
been removed from the view hierarchy indirectly. This prevents
ListView and RecyclerView children from being added to the overlay.
Change-Id: Iac0610f0939da8643b98812ee1ec1c8d1d70a215
TV input services are now required to call these methods to
unblock/block the screen.
Bug: 17364845
Change-Id: Ifb435900d7f61785198dba2e255a2d24dbf44dc6
Bug 17406204
Chrome needs to be notified when the shared element
should be hidden. The alpha setter can be overridden,
but setTransitionAlpha cannot. By setting alpha as
well as transitionAlpha, we get the immediate effect
from transitionAlpha along with enabling a trigger
for Chrome's shared element to hide.
Change-Id: I6ecb44872fd237afe89dbb36e43aa50c98693b52
* commit 'a8733153b889b8e627b834bb05f36dc9ce391bbe':
Ensuring that we retry if the callback for animation started comes before the Recents activity starts. (Bug 17316671)
* commit '3004eee618c3fad547768210f9252bad5abb0f69':
Removing unnecessary delays, ensuring transition thumbnail is the size of the header. (Bug. 16987565)
* commit '27e9505991500e9d5afee7fa485686905bbcf991':
Ensuring that we retry if the callback for animation started comes before the Recents activity starts. (Bug 17316671)
* commit '04682c2fa9f825cb2d09b6303c2b9b3b24e6bd19':
Removing unnecessary delays, ensuring transition thumbnail is the size of the header. (Bug. 16987565)
Surfaces were being modified after destroy(). The check for mSurface
being null was not done while holding window the window manager lock.
This change adds locking to the surface modification methods.
Fixes bug 17383628.
Change-Id: I12ebbddc0f2cd7b43659370fac2c4fb053999bb5
Make changes to Telecomm API per review guidelines in bug:
* Rename componentName to packageName and getComponentName to
getPackageName in StatusHints
* Hide "ROUTE_ALL" and fix misspelling in AudioState
* Change getHandle to getAddress and remove getHandlePresentation in
ConnectionRequest
Bug: 17329632
Change-Id: I8b3666cc22d24f470c940825c77a7b4d0701dc16
Default device and carrier disabled.
Device to be overlayed in device/<xxx> dirs.
Carrier overlayed in this project.
Bug: 17365969
Change-Id: I95d58e934fc85506287069ddd71af4a5b7594bfb
Also include capture format in recognition event
if capture is available for streaming. It was only
included if trigger was contained in event.
Bug: 17409062
Bug: 16731718
Change-Id: I5bf566e6bda57f23c870b4a1293e9b6d15d51e5a
Add a new activity attribute, resumeWhilePausing, that allows an
activity specifying it to immediately start running without waiting
for the previous activity to pause. The recents activity is updated
to use this.
The implementation of this is ultimately fairly simple -- if we are
in the path of resuming such an activity, and find that we first need
to pause the existing activity, then within the activity manager we
do the regular pause flow but act like it has immediately finished
pausing right then so that we can immediately go on to the resume.
To make this clean, we tell the activity when asking it to pause that
it should not come back and tell us it is done, because we aren't in
any way waiting for it.
One potentially important change I needed to make here is the pause
callback no longer provides the saved persistent state, because we
now can't count on that callback happening. I don't think there was
really any utility in this anyway -- all modern apps will have their
save state flow happen as part of stopping, not pausing, so we'll
only capture that saved state when the stop is reported back anyway.
And since we do send the saved state back when stopping, it would
always blow away whatever we had gotten at the pause.
Finally, update the documentation for AppTask.startActivity(), and
fix the implementation handling that to be cleaner -- we need to
deal with inTask first before getting in to "oh noes add NEW_TASK
if this isn't coming from a calling activity" flow.
Change-Id: Ia1da0fac90d7bdbaafdda2e34850d795ce17a39f
