Bad Things(tm) happen if some of the lifecycle interfaces on IActivityThread are
oneway but others are not [notably, out-of-order method delivery, i.e.
catastrophe]. This change makes the methods added for backup-agent management
oneway like the rest of the API.
When TextView handles a mouse move as a scroll, scroll the
underlying textfield/textarea. Also do not hide the cursor
while scrolling within a text input. Requires a change to
external/webkit.
Initial commit for review.
Integrated comments after patch set 1 review.
Fixed lockup in AudioFlinger::ThreadBase::exit()
Fixed lockup when playing tone with AudioPlocyService startTone()
* changes:
Make intent broadcasts in "am" synchronous (they wait until exit). Clean up error handling and reporting in "am". Make the usage message for "am" more informative.
Clean up error handling and reporting in "am".
Make the usage message for "am" more informative.
Make it easier to turn on logging in GoogleHttpClient.
use by SearchDialog. SearchDialog wants to be able to say a dropdown should
not always be visible but still let it ignore outside touch when it does
show.
Fixes http://b/1997170
Merge commit '98a44df4b4cc8cd28276ad888a7e17f81353ae44'
* commit '98a44df4b4cc8cd28276ad888a7e17f81353ae44':
* Revert the change that I introduced while refactroing in SurfaceView#dispatchTouchEvent
* changes:
* Revert the change that I introduced while refactroing in SurfaceView#dispatchTouchEvent * Don't scale back the event if the canvas is used in SurfaceView.
Before, if a column contained null, MatrixCursor.getString()
returned the string "null", and the get<Number>() methods
threw exceptions.
Now, getString() returns null, and get<Number>() return 0.
Fixes http://b/issue?id=1996628
Merge commit '11b822d2a91ea17c34c0cb1c11e80a9a30d72864'
* commit '11b822d2a91ea17c34c0cb1c11e80a9a30d72864':
Simplify density compatibility to a boolean.
Instead of a list, we now just have a single boolean indicating whether an
application is density aware, and this set set to true by default as of
Donut.
Merge commit '7228d0fdd7fd151f033b09044a9ba94b2bc06b74'
* commit '7228d0fdd7fd151f033b09044a9ba94b2bc06b74':
Resetting the setLanguage() call to its intended behavior after change 8089
Merge commit 'b551fb872be9b758c7793f56398d25a74d4a404c'
* commit 'b551fb872be9b758c7793f56398d25a74d4a404c':
Always call ensureImeVisible when the text field is clicked. We want this
Merge commit '5e21a11f00e3e65f6d7681e2519677329f0a92b2'
* commit '5e21a11f00e3e65f6d7681e2519677329f0a92b2':
Work around StateListDrawable padding in search suggestions
Merge commit '6de72ea39c9c00a2dc5ec539bf5733020c4db52f'
* commit '6de72ea39c9c00a2dc5ec539bf5733020c4db52f':
Proactively set mVisible attribute in startSearch and stopSearch (not just in message handler).
* changes:
Resetting the setLanguage() call to its intended behavior after change 8089 which works around the bug where a language cannot be set if the default language (which is loaded upon initialization) isn't eng-USA.
* changes:
Always call ensureImeVisible when the text field is clicked. We want this regardless of whether dropDownAlwaysVisible is true or not, as long as the popup is showing and is potentially obscuring the IME.
Sometimes when searching, some of the suggestions had no left padding.
The left-hand side icons were flush with the left edge of the screen.
The problems was that setting a StateListDrawable as a background
will always set the padding of a View, because of a problem in
DrawableContainer.
DrawableContainer.DrawableContainerState.getConstantPadding()
will always return a Rect if mVariablePadding is false, which
makes DrawableContainer.getPadding() return true, which
causes View to change the padding.
As a workaround, we use setVariablePadding(true) on the background
that we create.
Fixes http://b/editIssue?id=1984813
This way someone can call searchManger.startSearch() and immediately have searchManger.isVisible() reflect
the correct value.
Fixes failing tests and bug 1993675
Fix for http://b/issue?id=1703971. Because the browser overlays
the WebTextView over textfields, it intercepts all the touch
events, which was preventing the page from scrolling. This
change passes the move events back to the WebView to make
the page scroll.
Before, SQLiteDatabase.updateWithOnConflict() method generated
syntactically invalid SQL if the ConflictAlgorithm was non-null.
For example, it would generate
"UPDATE OR REPLACEshortcuts SET ...",
when it should be "UPDATE OR REPLACE shortcuts SET ...".
Fixes http://b/issue?id=1995470
