Bug: 5064702
This change improves compatibility with standard touch device
drivers. All existing touch device IDC files will need to
be updated because the input system now assumes that the
touch device drivers implement the multitouch input
protocol correctly and use the appropriate axes.
Change-Id: I93aad0e011efea74fbc7fa3da31f7967aff8136c
Before this change, CPU and memory usage for an audio effect were
registered and checked against the limit by audio policy manager
upon effect instantiation. Even if an effect was not enabled
it would prevent another effect to be created if the CPU load budget
was exceeded, which was too restrictive.
This change adds a method to register/unregister CPU load only when
an effect is enabled or disabled.
It also adds a mechanism to place all effects on the global output mix
in suspend state (disabled) when an effect is enabled on a specific session.
This will allow applications using session effects to have the priority
over others using global effects.
Also fixes some issues with suspend/restore mechanism:
- avoid taking actions when an effect is disconnected and was not enabled.
- do not remove a session from the suspended sessions list when corresponding
effect chain is destroyed.
Change-Id: I5225278aba1ae13d0d0997bfe26a0c9fb46b17d3
Fix bug 5144738 - Allow user to define pressed state asset for action
bar. Added android:actionBarItemBackground theme attribute. This
allows themes to define item pressed states for the action bar
independent of the standard selectableItemBackground.
Fix bug 5145416 - Custom view in action bar should use themed context
when inflating resource ID. Also applies to tab custom views.
Fix bug 5135550 - Tab divider height / Color should match spec. Added
actionBarDivider theme attribute. Similar to actionBarItemBackground
above, this allows apps to maintain proper contrast when the bar has a
different contrast profile than the rest of the activity.
Fix bug 5154778 - Theme.Holo.Light.DarkActionBar in themes.xml and
search_bar.xml are still referencing the deprecated title_bar_shadow
when we should be pointing to ab_solid_shadow_holo
Change-Id: I5ef0084de28a7c2d2fa02ae1752884feab0f8523
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
Pass the flags about what information changed in the remote
control client in the intent used by the remote control display.
Also pass the IRemoteControlClient to verify it is still current
before sending the intent.
Marked some logs as to be removed before release.
Change-Id: Ib3aa22d061e5dfaf80a9c4c78774c931a2cf0fbd
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
