- Aug 11, 2011
-
-
Justin Ho authored
Bug: 5076695 Change-Id: I0f572f3bdba702df20074f6bec99bdb73ee146b8
-
Adam Powell authored
-
Gilles Debunne authored
-
Eric Laurent authored
-
Justin Ho authored
-
Eric Laurent authored
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
-
Adam Powell authored
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
-
Justin Ho authored
Bug: 5076695 Change-Id: Ie34b1ccb2c0e9d1ba7c6c5af64719f87cb270edd
-
Justin Ho authored
-
Justin Ho authored
-
Gilles Debunne authored
Change-Id: Ib0e259dd20546855899bf091f694e41e7051fecb
-
Kenny Root authored
-
Debashish Chatterjee authored
-
Chet Haase authored
-
Romain Guy authored
-
Matthew Xie authored
-
Dianne Hackborn authored
-
Dianne Hackborn authored
-
Romain Guy authored
Bug #5150923 Change-Id: I765d8e4d63a1fee7a12b9c2992bec67b4b6d1131
-
Chet Haase authored
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
-
Marco Nelissen authored
-
Chet Haase authored
-
Marco Nelissen authored
Change-Id: I6c0c267fbb546b6db544e5ddb03e65276895e0e0
-
Ben Murdoch authored
-
Debashish Chatterjee authored
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
-
Robert Greenwalt authored
-
Justin Ho authored
Bug: 5076695 Change-Id: I00aa88ff0c7927bb416ef88c35cd7cb39105e520
-
Justin Ho authored
Bug: 5076695 Change-Id: I0943e34e978aeebc4d1194a9bff8bfb4bd7543c4
-
Dave Burke authored
-
Chet Haase authored
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
-
Dave Burke authored
This reverts commit a04cda99. Conflicts: include/gui/SurfaceTexture.h libs/gui/SurfaceTexture.cpp Change-Id: Ib655016462c496ee2a27f7cb33a6e8b18cfe684a
-
Daniel Sandler authored
-
Daniel Sandler authored
-
Daniel Sandler authored
-
Daniel Sandler authored
-
Ben Murdoch authored
Bug: 5150575 Change-Id: I36f8dd59f630d77ea3f4ef6271f4cbaaaa3df0ad
-
Kristian Monsen authored
-
Adam Powell authored
Merge "Fix bug 5122319 - When action bar tabs run out of space they should collapse in to a spinner."
-
Adam Powell authored
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
-
Daniel Sandler authored
Bug: 5118028 Change-Id: I5517d79624020aa7ceeabf251581b3baf2f7b080
-