search bring up global search. This still respects the case where an
app has chosen to disable search entirely by overriding
onSearchRequested() to return false.
I do not believe any changes to the SearchManager documentation
(http://developer.android.com/reference/android/app/SearchManager.html#HowSearchIsInvoked)
are necessary, because this documentation already indicates that
pressing the search button within an app that does nothing special with
regard to search can bring up global search.
Merge commit '3e3439d5ba0cf5eda060c4991219c32af917fc5b'
* commit '3e3439d5ba0cf5eda060c4991219c32af917fc5b':
Fixes#1847219. Add a new API to load fonts from arbitrary files: Typeface.createFromFile(String/File).
Merge commit 'e51f3a012b146d57a01b9f7cc7c043b9da3c600d'
* commit 'e51f3a012b146d57a01b9f7cc7c043b9da3c600d':
Check the size of the data to write for STATIC AudioTrack objects.
* changes:
Check the size of the data to write for STATIC AudioTrack objects. Extracted actual writing from write jni function so it can be reused in an upcoming change.
Merge commit 'da33d0d139531ff184a1a339b734de00f1cc0743'
* commit 'da33d0d139531ff184a1a339b734de00f1cc0743':
Fixes 1844680. Interrupted scrolling could lead to rendering artifacts. The ListView was invalidating itself in opaque mode but before the drawing could happen, it was getting rid of its scrolling cache, thus becoming translucent again.
Merge commit 'c70b64441029b9748eea7f260f1b3521dc58eb91'
* commit 'c70b64441029b9748eea7f260f1b3521dc58eb91':
Fixes#1846038. DrawableContainer was wrongly returning its opacity by ignoring the visibility of the currently selected layer. This change simply reports a TRANSPARENT opacity if there is no currently selected layer of if the selected layer is not visible. Otherwise it reports the opacity computed by the state class.
* changes:
Fixes 1844680. Interrupted scrolling could lead to rendering artifacts. The ListView was invalidating itself in opaque mode but before the drawing could happen, it was getting rid of its scrolling cache, thus becoming translucent again.
* changes:
Fixes#1846038. DrawableContainer was wrongly returning its opacity by ignoring the visibility of the currently selected layer. This change simply reports a TRANSPARENT opacity if there is no currently selected layer of if the selected layer is not visible. Otherwise it reports the opacity computed by the state class.
Merge commit '7e3e04c144182c6807c66646b3f988beaba1720e'
* commit '7e3e04c144182c6807c66646b3f988beaba1720e':
* update all metrics data when updating density.
* changes:
* update all metrics data when updating density. * Keyboard should use DisplayMetrics from Resource rather than getting it from WindowManager as the display metrics can differ under compatibility mode.
Merge commit 'a2ea1d376524346e3f601694751e423ce2711d6b'
* commit 'a2ea1d376524346e3f601694751e423ce2711d6b':
Fixes#1596240. Optimize invalidate/draw passes by marking opaque views and avoiding drawing them. Whenever a View requests an invalidate its parent check whether the view is opaque or not. When the view is not opaque, the framework behaves as it used to. However, when a view is opaque, the parent marks itself as being dirty because of an opaque view. Its parent then does the same, and so on. When the framework then starts drawing the views, it does not draw views marked as dirty opaque. If a view is dirty opaque and receives an invalidate request from a non-opaque view, it then clears the dirty opaque flag and behaves as before.
Merge commit 'e292086e6b5124a8e6b9435609d41c9ab2ef5e22'
* commit 'e292086e6b5124a8e6b9435609d41c9ab2ef5e22':
Fix 1799207. With the new local dns, we should allow the host without any PERIOD. Otherwise http://go won't work properly.
* Keyboard should use DisplayMetrics from Resource rather than getting it from WindowManager as
the display metrics can differ under compatibility mode.
Merge commit 'e41d81948e1f8e89c19ae30037b260ae3b2adea2'
* commit 'e41d81948e1f8e89c19ae30037b260ae3b2adea2':
Improve the rendering speed of the lock screen by reporting the appropriate opacity for the background wallpaper.
* changes:
Fixes#1596240. Optimize invalidate/draw passes by marking opaque views and avoiding drawing them. Whenever a View requests an invalidate its parent check whether the view is opaque or not. When the view is not opaque, the framework behaves as it used to. However, when a view is opaque, the parent marks itself as being dirty because of an opaque view. Its parent then does the same, and so on. When the framework then starts drawing the views, it does not draw views marked as dirty opaque. If a view is dirty opaque and receives an invalidate request from a non-opaque view, it then clears the dirty opaque flag and behaves as before.
