Now tapping anywhere on the notification/clock/status end of
the system bar will bring up the notification panel.
Swiping up anywhere in that region works as well.
This change also adds visual touch feedback to the panel
trigger area.
Bug: 4723688
Change-Id: I5e24fea1231b798c41ddd48c0c42c283c92ebe65
Previously, setting custom animations on a LayoutTransition would cause
those animations to be run not only for changing views in the container, but
for the parent hierarchy of those views as well. This can lead to unexpected
behavior, as seen in the ApiDemos LayoutAnimations and LayoutAnimationsHideShow.
This change changes the behavior so that the parent hierarchy is animated by
the default animations (which change the bounds and scrollX/Y fields) instead
of custom animations.
Change-Id: I9a04d97fabbc34dc0d5809eb3fd8ac08e0801d7c
Content provider does not directly use this intent. But it is fired by
the contacts app to request the voicemail source to fetch voicemail
audio of a single voicemail message.
The constant needs to live in the contracts file to serve as a common
definition between contacts and voicemail source apps.
Bug: 5114261
Change-Id: Ibf7b2a4c871d3561d2ca50d03f8182352fadd3ab
When removing an item from the Recents list such that the list went from
larger than the screen to smaller (bringing the first item completely into view)
there was an artifact where the list would jump briefly, just prior to running
the transition to animate the remaining items into place.
The problem was that the custom ScrollView classes in the Recents app were
manipulating the scrollX/Y values of the items as a side-effect of any resize
of the list. Meanwhile, the LayoutTransition was manipulating both the size and
the scroll position of the list. The transition's scroll values would get clobbered by
the app's side-effect operation, causing the jump that we'd see on the screen.
The fix was to disable the side-effect operation during a layout transition.
Change-Id: I17f3f05d0e8a792e41bd46869ee700f128e63216
collapse in to a spinner.
When tabs are not given the option of dropping to their own row,
collapse them into a spinner when they would measure too large to be
visible all at once.
Fix bug 5095167 - zombie tabs return when they shouldn't when activity
handles its own orientation changes
Change-Id: I074419d99a22aa5dd1cbc00a66e600ec5cb0b54a
* Clear-all button (X) fades in and out
* "No notifications" text fades in after a few sec
* Swipe-out velocity can be much higher, dramatically
reducing perceived jankiness in clearing notifications
Bug: 5150699
Change-Id: Ic7e5254fee57724c42b6437d1c4ed8a700615208
* changes:
fix a crasher in SurfaceTexture::updateTexImage()
rework dequeueBuffer()'s main loop.
error out when SurfaceTexture APIs are called while not connected
...by once and for all making all of the code deal appropriately with
expected partial reads. We also now produce a properly conformant
underlying 'tar' EOF sequence [which will be compressed to almost
nothing] to doubly bulletproof the end-of-archive logic.
Fixes bug 5133658
Change-Id: I24a785574861d64ef10fc727b9f6b235575696b0
we now make sure to drain the buffer queue on disconnect.
this happens only when in synchrnous mode. in async mode
we clear all buffers except the head of the queue.
for extra safety we also catch the null pointer
in updateTexImage (which should never happen) and return
an error.
Bug: 5111008
Change-Id: I5174a6ecbb0de641c6510ef56a611cbb4e9e1f59
this simplifies the code a bit and also makes sure
we reevaluate mAbandoned and mConnectedApi each time
we come back from waiting on mDequeueCondition
Change-Id: I1f8538b62ad321b51ed79d953b700036daba796d
- also log a warning when freeAllBuffers is called with a non empty buffer queue
- rename freeAllBuffers to freeAllBuffersLocked
Change-Id: Idb71fdcf233b9ccae62d5a2a7c3c4bad2501d877
