- refactored hwlayers and change view property animations to use a reference counted trigger
- cleaned up RecentsConfiguration, and move it into classes using it
- moved task bar animations back into TaskBarView
- refactoring enter/exit animations to use an animation context
Change-Id: Ia66b622b094f22145c2fab07c2a9bdfd62344be2
This was causing strange indentation.
The change also clarifies how to get the supported output sizes in the
ImageReader flow: Although the doc (correctly) instructed the developer to use
StreamConfigurationMap#getOutputSizes(int) with an ImageReader, this instruction
appeared after the bulleted list of output types. Since all other items in that
list specify that getOutputSizes(Class<?>) should be used, the reader shouldn't
be expected to read beyond the list only in this specific case.
Bug: 15574400
Change-Id: Id952b46ae52322d75abbcaffea678d5ba50b22a5
- add missing Material preferencePanelStyle / preferenceHeaderPanelStyle /
preferenceListStyle / preferenceFragmentListStyle / preferenceFragmentPaddingSide
- add needed material dimens
- fixed PreferenceFragment.Material
- done it for the normal and light theme
Change-Id: Ib25288a499ab6b1ee42b2d0c72a2e5a1be084e5f
* commit '870b4c31c58aefaed1de3912e7dfe0fc6cc46f17':
Fixing issue where we do not get the task rects, and therefore have no transitions. (Bug 15610655)
Added a log based interpolator (it's faster in the beginning and smoother
at the finish than the decelerate interpolator)
Scaled the timing and opacity of the falloff ripple based on the size
of the outer bounding radius. Backing circles aren't as apparent for
Smaller touch targets.
BUG: 15591274
This makes our terminology consistent with the existing BluetoothHeadset profile
Also updated arguments to Context.bindService()
Change-Id: I27cc5a6fde256b1f5dccca53a7a15ec8f58691c2
Bug: 15432556
The api council asks to change the interface to an abstract class
and clarify the clearClientCertPreferences api. This change addresses
these.
Change-Id: I7979788c7c041bacbfef5ea4d94309f91279ef22
This change allows TTS V2 API client applications to honor the
"default TTS locale" set by the user in the TTS settings.
Note that the TTS V1 API uses 3 character country/language codes
for locale encoding. It's the only system component that does
that. TTS V2 uses the standard, valid Locale objects. The default
TTS locale setting was stored as a 3 character locale string with
"-" as the separator.
This change switches the TTS locale setting format to the output of
Locale.toString() call (on a valid Locale object). Methods used for
reading this value can interpret both forms and try to return a valid
Locale object as an output.
Change-Id: Ice2e6c25a43eb9dd6e17d371ee582c2dae3329c9
