| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
* changes:
docs: setup new SDK documentation for 2.0 and change sdk build version to 2.0... move upgrading doc into a new guide for "updating" with the new manager tools and remove the previous updating doc from the dev guide. set up preliminary download page and guide for installing the full SDK. add the requirements doc in sdk/ for all general purposes. revise the download 'thank you' message.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
move upgrading doc into a new guide for "updating" with
the new manager tools and remove the previous updating doc
from the dev guide. set up preliminary download page and guide
for installing the full SDK. add the requirements doc in sdk/
for all general purposes. revise the download 'thank you'
message.
bug: 2160782
|
| | |
| |
| |
| |
| |
| |
| | |
This reverts commit 3d0726b4d8a30e57852b70f1dcf4d8d20508cd1e
Change-Id: Ie1ce5d09cc0b799ef0799f30eedc95f0ca5d3fad
DrNo: jerrryw
|
| |\ \
| | |
| | |
| | |
| | | |
* changes:
Remove STOPSHIP comment.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Change-Id: I2492bffe57bded65fdbef5cf98e22cef3937e537
DrNo: eastham
Bug: 2089423
Joke: Why don't anteaters get sick? Because they're full of anty-bodies!
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
SDK doc change per http://b/2158141 - adds new res wizard to L10N tutorial. Changed image links to use @docRoot.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Changed image links to use @docRoot.
Change-id: If30c5e20bbbb0dd4a6eb0563ede2767d110e1c2e
Bug: 2158141
|
| | |_|/
|/| |
| | |
| | |
| | | |
Bug: http://b/2186595
Change-Id: Id87533c25cceb0fe3b0845aed10912c937679f45
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
7 more ringtones. Now with more Dr. No!
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* changes:
Another fix for #2186897: Cannot unlock the device by swiping
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This was probably a side-effect of the divide by zero exception,
but we'll be safe anyway.
Change-Id: I875200febb9b3090d12f170066b2bea74c9f77f8
|
| |\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | | |
* changes:
Fix issue #2186709: Can't unlock the device for a while
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Iac5342254036cc286ad502dba943520f55ea2405
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: http://b/2186595
Change-Id: Iaba8514276299504af6ab0714577eb37d9608237
|
| |/ / / /
| | | |
| | | |
| | | | |
Fixes http://b/2186076
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
* changes:
Futher reduce the logging of EriManager.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There was another log statement that was poluting radio logs.
bug: 2180891
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* changes:
Work on issue #2144454: Inconsistent swipes...
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This introduces some hacks in the framework to try to clean up the
data we are getting from the touch screen. There are two main things
being done here:
1. Look for changes in position that are unreasonably large, and
ignore them. This is intended to eliminate the spurious jumps that
often happen when releasing.
2. Add some simple adaptive averaging of the touch data. If the
difference between the last and next point is large enough, we
disable the averaging; otherwise we average up to the last 5 points.
The goal is to get rid of the noise of small movements so that things
like taps don't look like short flings, while still responding quickly
to rapid movement.
For averaging pressure, we also weight each averaged coordinate by
the reported pressure at that point. This is intended to keep the
coordinates closer together during a release, when the pressure is
going down and the accuracy decreasing. It may also result in some
other interesting artifacts, but hopefully nothing problematic.
Change-Id: I1369e9ab015c406946a45c2d72547da9c604178f
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
* changes:
Add a little logging to diagnose wifi cycle bug
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
Hiroshi approved (with serious code review).
bug: 2171575
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* 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
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
* changes:
Continue caching "POST" result so that we won't get the resubmission warning when back to Google search result.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
the resubmission warning when back to Google search result.
Fix http://b/issue?id=1490379
Break/reopen http://b/issue?id=1980031
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Allow the ERI overlay file to specify the text for any built-in strings.
Currently only the hard-coded strings are used for those.
Bug: 2170881
Change-Id: I5d6169696a4558e62587585e17f908f823c54a2b
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* changes:
Reduce the amount of EriManager Logging.
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It was filling the radio log with noise. Added a VDBG set to false to preserve the logging
but deactivate it.
bug: 2180891
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* changes:
Revert "egl: temporarily also include eglTerminate->eglInitialize hack for 8k"
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit ed5ecdba36648973be3033a045e2ece8bf039e4a.
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | |
| | | | | |
| | | | | | |
* changes:
Fix race condition in WindowManagerService.disableKeyguard()
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
TokenWatcher.acquire() synchronizes on mTokens, not this,
so we need to synchronize on mKeyguardDisabled in disableKeyguard()
to synchronize properly with reenableKeyguard().
This should fix b/2180142 (Stuck in enable keyguard when receiving phone call)
Change-Id: Iad66a2748c7fbf2c516fdb8a00988696719ea80c
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
| |\ \ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | | |
* changes:
Delay 500ms between each registering each SDP record using sdptool.
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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!
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
* changes:
Fix issue #2179931: Power key to wake up frequently ignored when in dock app
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The dock app is forcing the screen to a particular brightness level. This
causes the window manager to often call into the power manager with the
new brightness. This causes us to go in to updateLightsLocked() to figure
out and apply the real brightness to use. When the screen is off the
real brightness always remains 0, but even if it didn't change from the
last one we would start an animation which would when done put the system
to sleep and fight with the user trying to turn the device on.
Now, if the new target brightness is the same as the last one, we leave the
animation as-is -- either running or not as appropriate.
Change-Id: I067d55ea2b39e294c5d5291587a4d8727c0b8083
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Build.VERSION_CODES.ECLAIR as such.
Change-Id: I45af1fe80f6f93a1db8389600dc780af9cedf22c
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
* changes:
fix sync exponential backoff for expedited syncs
|
| | | | | |
|
| | |/ /
|/| |
| | |
| | |
| | |
| | | |
Copied current.xml to 5.xml.
Change-Id: I5eaa806eef9a9a3135b021d7db179325ff7663fc
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
Add new RenderScript sample: ImageProcessing.
|
| | | | |
| | | |
| | | |
| | | | |
Change-Id: I5e482bbc34911c940a3a74258f8f8549b1939bc4
|
| |/ / /
| | |
| | |
| | | |
Approver: jerryw
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since the StatusBarPolicy is run in the System Process and shouldn't therefore call into
the Telephony process we decided to make sure all the needed info was passed along with the
original notifications.
bug: 2173053
|
| | | |
| | |
| | | |
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.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* changes:
Fix for 2177367: Reduce duration of vibrate in RotaryLockScreen
|
| | |/ / /
| | | |
| | | |
| | | | |
BUG=2177367
|
