| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ViewRoot is responsible for calculating the current view's surface's
transparent region and reporting this to the window server, which in
turn notifies Surface Flinger.
To minimize cross-process traffic, ViewRoot keeps track of the
most recent transparent region that it has reported to the window
server, and only sends updates when the region shape changes.
ViewRoot is effectively shadowing the internal state of the window
server, and usually this works fine, because ViewRoot is usually the
only thing that changes this value.
But when the surface is recreated, the window server resets the
transparent region to empty. So in order to properly update the window
server we need to reset our copy of its state to empty too.
Fixes issue #2133090: GL Gears runs at half speed in some cases
|
|
|
|
|
|
|
|
|
|
| |
Track phone service state changes and use a separate timer for out-of-service
since the hunting can timeout on some devices.
Store the timeout value in the config.xml, as it is device/network specific.
Settings App will also change to use the hunting duration to compute the cost
of zero signal.
|
|\
| |
| |
| |
| | |
* changes:
Remove PowerManager.setAutoBrightness()
|
| |
| |
| |
| |
| |
| |
| |
| | |
We will use the System.SCREEN_BRIGHTNESS_MODE Settings value instead.
Add SCREEN_BRIGHTNESS_MODE_MANUAL and SCREEN_BRIGHTNESS_MODE_AUTOMATIC constants.
Change-Id: I01935be3fcb48cf76392d2c594205cb47babc5b2
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fix is alrady in mr2. It does not affect sholes --
this is a trackball only bug.
The selection caret and arrow now take the scale factor and
the height of the title bar into account when preparing the
canvas for drawing.
Clicking the trackball at the end of selecting text no longer
sends a click event.
Requires a companion fix in external/webkit
Fixes http://b/issue?id=2187591
|
|
|
|
|
|
|
| |
Bug #2189714
Reviewed by: ryanpc
Change-Id: I0d74deb6dc8e90e3b0eafd6b3c16b0c557c72873
|
|
|
|
|
| |
Bug: http://b/2186595
Change-Id: Id87533c25cceb0fe3b0845aed10912c937679f45
|
|
|
|
|
| |
Bug: http://b/2186595
Change-Id: Iaba8514276299504af6ab0714577eb37d9608237
|
|\
| |
| |
| |
| | |
* changes:
Throttle camera preview frames to the app. Bug 2180302.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With higher frame rates and larger preview frames, we can easily
flood the application with too much data. This patch fakes the
old camera preview mode by doing continuous one-shot frames.
After the previous frame is handled, if the application hasn't
cleared the preview callback, we start another one-shot preview
frame. With this change, the application should never have more
than one preview frame unless it is explicitly saving references
to them.
modified: core/java/android/hardware/Camera.java
|
| |
| |
| |
| |
| |
| | |
the resubmission warning when back to Google search result.
Fix http://b/issue?id=1490379
Break/reopen http://b/issue?id=1980031
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to workaround an issue where SDP records will fail to register using
sdptool. When we run SystemService.start() it forks sdptool, so if we do this
four times in a row these forked processes can run in parallel, and one or
more of them fails. There is probably some thready safety issue in sdptool
or Bluez that makes it unsafe to run sdptool in parallel.
As a workaround, delay 500ms between each run of sdptool to register SDP
records when starting Bluetooth.
Before this fix it was easy to reproduce problems with service record
registration. If you turn BT off/on multiple times you can see that sometimes
one or more service records are missing. Repro rate is about 20% in my tests.
Result is that remote devices cannot connect to the missing service.
After this fix I am unable to reproduce any missing SDP records, after 30+
cycles of BT on/off. Motorola BT team also ran stress tests overnight with this
fix and were unable to reproduce the missing SDP records.
This is a low risk fix. It does delay some records from being registered
by an additional 1.5 seconds (on top of the 3 second delay we already had),
so if you try and very quickly connect a BT service after turning BT on it
won't work the first time.
Do not merge. (I will use a less hacky fix for MR2/Master)
Change-Id: I305c181c3194e8ce25e3825320cc2e1ef6d3d3cc
Bug: 2180800
DrNo: eastham
Joke: Why can't you play cards in the jungle? Because there's too many cheetas!
|
|
|
|
|
|
| |
Build.VERSION_CODES.ECLAIR as such.
Change-Id: I45af1fe80f6f93a1db8389600dc780af9cedf22c
|
|\
| |
| |
| |
| | |
* changes:
fix sync exponential backoff for expedited syncs
|
| | |
|
| |
| |
| | |
Fix http://b/issue?id=2176656
|
|\ \
| | |
| | |
| | |
| | | |
* changes:
Add LAST_KMSG_KB variable, used to tune the size of /proc/last_kmsg uploads. See bug 2177046.
|
| | |
| | |
| | |
| | | |
See bug 2177046.
|
|/ /
| |
| |
| |
| |
| | |
device
Change-Id: I65d91cdb70df91b67fe84297dd6a94d26a785131
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Do not merge.
Change-Id: I428bc0fc67030f24112f2e9c865824dfaea4897d
DrNo: eastham
Bug: 2089423
Joke: Why was Tigger looking in the toilet? To find Pooh
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Make functions that are meant to be BLUETOOTH_ADMIN really
BLUETOOTH_ADMIN.
Add some missing javadoc for permissions.
The only functional change here is the BLUETOOTH->BLUETOOTH_ADMIN
changes. This is super safe because every system app that uses BT
has both permissions.
Change-Id: Iddc61f9fd5d81fe0171358665a0fa52f2fa02871
DrNo: eastham
Joke: How do you catch a rabbit? Hide behind a tree and make carrott noises.
|
|\ \
| | |
| | |
| | |
| | | |
* changes:
GPS: Fix problem with SUPL when SUPL APN is already active.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use ConnectivityManager.CONNECTIVITY_ACTION broadcast in LocationManagerService
to notify GPS when SUPL connection is ready instead of TelephonyIntents.ACTION_ANY_DATA_CONNECTION_STATE_CHANGED,
which is not sent in all cases.
Expand LocationProvider.updateNetworkState() to include NetworkInfo object.
Fixes bug b/2155661
Change-Id: Iee227ace7d536b36cf7973e3e6a8b7a621ce6565
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
* changes:
Fix issue 2174002: After rejecting Call when device ringtone is mute and playing music, audio is not transfered to BT device.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
playing music, audio is not transfered to BT device.
Added a workarouond to request the A2DP output standby directly to audio hardware when the sink is suspended as it seems that the suspend request often fails.
Also take into account resume requests received while a suspend request is pending.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
Set the Bond State to NONE when we receive a Agent Cancel.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Sometimes during OPP, we can get stuck in Pairing state when the remote
end, cancels the Pairing process - we will just get onAgentCancel
and thus not set the Pairing state properly.
DrNo: Eastham
Bug:2174874
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* changes:
Fixes #2175599. Prevents an NPE when AttachInfo is null.
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This bug was introduced by a change made to query the window's opacity.
Approved by mcleron.
Change-Id: I95319bde72b0faade095bbbbb317e84b9be8efa8
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
* changes:
Make vCard import Photo from vCard file :(
|
| | | |
| | | |
| | | |
| | | | |
Internal issue number: 2174296
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* changes:
Only dismiss search dialog after launching intent.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This fixes an NPE that occurs when launching the intent
tries to access state cleared by onStop.
Bug: 2171752
Change-Id: I29232f2a44d8dfa27b2c79933093c0c8983b2e92
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
* changes:
fix an NPE on a race condition that occurs when unbinding from an authenticator at the samer time that its process dies: bug 2171204
|
| | |_|/
| |/| |
| | | |
| | | | |
authenticator at the samer time that its process dies: bug 2171204
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
There was another way we could ignore the application windows flags
while the lock screen was displayed. This is the infrastructure to
deal with that.
Change-Id: Id8c9cb2f7081df6757ccb797a7cde618e82f7b38
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
Introduce BluetoothAdapter.getDefaultAdapter().
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is the main entry point to the Bluetooth APIs, and returns the default
local Bluetooth adapter.
It replaces context.getSystemService(Context.BLUETOOTH_SERVICE). This was
never in a public SDK release.
DrNo: eastham
Bug: 2158765
Joke: Why can't you play cards in the jungle? Because there's too many cheetas!
Change-Id: Ieed8be009ee5aba621cb69090ee8c8a9c19c840d
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | | |
* changes:
Encourage developers to connect RFCOMM by UUID instead of Channel.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Hide createRfcommSocket(int channel)
Add createRfcommSocketWithServiceRecord(UUID uuid)
Rename listenUsingRfcomm(String,UUID) -> listenUsingRfcommWithServiceRecord(..)
Now we have a complete API for developers to make peer-peer RFCOMM connections
with hard-coding the limited (30) RFCOMM channels, instead using SDP lookup
of an UUID.
This commit addresses two serious bugs:
- Do not throw IOException on accepting an incoming RFCOMM connection with
BluetoothSocket. This was a regression from commit 24bb9b8af4ff6915
- Workaround failure of bluez to update SDP cache when channel changes by
trying to use the same RFCOMM channel on the server every time, instead
of picking server channels randomly. This is a pretty ugly workaround,
and we are still trying to fix the caching issue - but with this
workaround we are at least shippable and apps will work at least until
they start colliding on the 30 RFCOMM channels.
DrNo: eastham
Bug: 2158900
Joke: What did the digital watch say to his mom? "Look mom no hands."
Change-Id: Ia4879943b83afac06b6f1a3f2391cf1628afce7d
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
32 bits
format when the window is 32 bits.
Change-Id: I46762def67fa7d6a331a75fa8660c6422394ccf2
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't hold a lock when the activity thread is telling the activity manager
to release a provider.
This requires that the activity manager now keep a reference count on the
providers, because without the lock it is possible for activity thread to
call in to request the provider again before it has finished telling
about the release.
Change-Id: I5f912903891f4edae85e28819d4e6f14b8f2e688
|
|\ \
| |/
|/|
| |
| | |
* changes:
Fix back button handling in ACTV
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
AutoCompleteTextView.onKeyPreIme() used
getKeyDispatcherState().startTracking(event, this) to start tracking
the back button, but didn't update the state of the event
before checking event.isTracking().
Fixes http://b/issue?id=2167168
"AutoCompleteTextView back button handling is broken"
Change-Id: I2c5f1e761872b9e02d85ff6f958fabd558d041a0
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
* changes:
Turn some logging back on in ConnectionManager
|
| | |
| | |
| | |
| | |
| | |
| | | |
Trimmed a bunch of logging out, but turned it on so we get the critical stuff.
bug: 2168291
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
* changes:
Add zoom functions and sendCommand.
|
| | |
| | |
| | |
| | | |
b2060030
|
|/ / |
|