When invoked from an anyDensity="false" or pre-Donut app,
View.getLocationOnScreen() returns values in compatibility
mode. This change fixes QuickContact and RemoteViews to
always adjust based on CompatibilityInfo.applicationScale.
Also deprecates an extra previously being used to pass
Rect for QuickContact windows.
Fixes http://b/2306495
Merge commit '9a67c82089e43d37f5038c74b0e1dca8edc4ac8a' into eclair-mr2-plus-aosp
* commit '9a67c82089e43d37f5038c74b0e1dca8edc4ac8a':
Address the multiple resizing during initializing
problem adobe run into.
When a child view is created, we first hide it if
the webview is not ready to draw yet. This will avoid
the multiple resizing notification.
Merge commit 'a2bca7477d803541c5a48cc7624e2b6c305c5970'
* commit 'a2bca7477d803541c5a48cc7624e2b6c305c5970':
docs: update the Bluetooth guide with links to the sample
Merge commit 'a25032a08d1cce601c0a52057bc39d9c7e47bfad' into eclair-plus-aosp
* commit 'a25032a08d1cce601c0a52057bc39d9c7e47bfad':
docs: update the Bluetooth guide with links to the sample
* changes:
docs: update the Bluetooth guide with links to the sample app, scrub the sibling files, and revise the Bluetooth package summary to point to the BT dev guide.
By default, Android's System.out and System.err are implemented by
the AndroidPrintStream subclass of LoggingPrintStream. Until now,
that class has silently discarded the raw bytes it has received.
This causes two problems:
Applications may be accidentally wasting CPU+memory writing to
System.out. By making this output visible, the developers of such
applications can silence the problem at the source.
Application developers may be purposefully writing to these streams
and perplexed by the data's disappearance. For example, the core
library's own java.util.logging.ConsoleHandler sends its log data
into this black hole. By making the data visible, we save the data
and remove an unnecessary sharp edge from our API.
Addresses bug 2317577
Views now will not enter PRESSED state until
ViewConfiguration.getTapTimeout() milliseconds have elapsed. This
prevents scrolls and other gestures from causing views to enter
PRESSED state prematurely.
Quick taps within the same view still work as expected. There is now a
PREPRESSED state flag within View to help track quick taps.
If tapped quickly, views will remain pressed for
ViewConfiguration.getPressedStateDuration().
Tap timeout has been changed to 115ms. Pressed state duration has been
changed to 125ms.
Bluez sends SINK_STATE_CHANGE before onAgentAuthorize, so
we may be already in CONNECTING state. This will happen with
some A2DP kits which don't like us connecting and thus we will
never be able to connect to them.
Bug:2335345
Dr No: Hiroshi
Merge commit '4986934e189032dba43676973038879b5f90a406' into eclair-mr2-plus-aosp
* commit '4986934e189032dba43676973038879b5f90a406':
Remove the IM provider contract class.
Merge commit 'c57930aa679385b87852a9805b971a4fb91c65be'
* commit 'c57930aa679385b87852a9805b971a4fb91c65be':
Added the Protractor algorithm for calculating the minimum cosine distance between gestures
Merge commit 'e96b6838b5a7ec3b4368e2449af9fbf0a8b75f16' into eclair-mr2-plus-aosp
* commit 'e96b6838b5a7ec3b4368e2449af9fbf0a8b75f16':
Added the Protractor algorithm for calculating the minimum cosine distance between gestures
If something had backed up this setting in the 'do nothing' state, a restore of
that dataset could render a device without a hard END key unusable. There's no
clear reason to want to restore this value anyway, so we no longer back it up,
nor apply it at restore time even if the dataset contains it.
Bug: 2326562
Merge commit '43ad522d49dd3f89d7e367112fab64e4d5027bf3' into eclair-mr2-plus-aosp
* commit '43ad522d49dd3f89d7e367112fab64e4d5027bf3':
Add a callback for the ConnectSink Call.
Merge commit '601112f213035851a2fa2c2281c7f56cf767b14a' into eclair-mr2-plus-aosp
* commit '601112f213035851a2fa2c2281c7f56cf767b14a':
Implement the full screen WebView plugin.
This takes care of the conditions where the bluez audio drivers
are not up and we try to make the call to connect the sink.
This would get rid of the hack in Settings app.
Use a NoTitleBar_Fullscreen dialog to implement the
full screen plugin. This runs in the same thread as
WebView (UI in the Browser case). One catch is that
the SurfaceView provided by the plugin needs to be
opaque if it doesn't want to see through the WebView.
The PluginFullScreenHolder translates the events to
the underline WebView. Special treatment in the touch
case as it needs to translate the coordinates.
WebView can't be panned, or double tap to zoom, or
long press to trigger the context menu while having
a full screen plugin.
Inside webkit, we also give the plugin element focus
when it goes to the full screen so that it takes key
events. While handling key events, we don't let it
loose focus or scroll out.
Todo:
When a plugin goes to full screen, we should make
sure the embedded plugin is fully visible. Otherwise
when we translate the touch events back, they will be
outside of the visible rect and will be ignored.
This is part 1 of 2-project check in.
Merge commit 'aab601168caec83cf1ca3f235d3a6b308a5dedaa'
* commit 'aab601168caec83cf1ca3f235d3a6b308a5dedaa':
b/2224837 Changed the plumbing of how alerts/notifications work.
Merge commit 'e9db8335c01aa47799403b59718811ec703cfe61'
* commit 'e9db8335c01aa47799403b59718811ec703cfe61':
check to see if nav cache is up to date on tap
