| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | | |
A lot of applications (e.g. QuickTime, mkvmerge) apparently does not like the 64-bit timestamp and will fail to open the file.
This reverts commit 893586d4b7a0dbea070404323837ef4f0a7c9b79
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allows the time it takes for the back key to kill an app
to be customized via overlay.
Change-Id: Iaa43f81ee448ae7a7663254a830011a0bca5e60f
|
|/ / /
| | |
| | |
| | | |
Change-Id: I26a48a1422060a19c76fbc83af95ae7649442bf0
|
|\ \ \
| | | |
| | | |
| | | | |
visible." into ics
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Ignore mKeyboardVisible in PowerManagerService::applyKeyboardState if
KEYBOARD_BRIGHT_BIT is already set in mPowerState. Previously, if the
keyboard were to hide after setting mPowerState, but before running
applyKeyboardState, then the keyboard backlight would remain off at the
next slide event since mPowerState is unchanged.
- Always set mLightSensorKeyboardBrightness in
PowerManagerService::lightSensorChangedLocked to a sensor-based value,
instead of 0 when the keyboard is hidden. This ensures
mLightSensorKeyboardBrightness is sensible on slide events since it may
not be recomputed timely.
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | | |
Change-Id: Ib8390a8815a97ffdbacd2c11af9c70c59180ea61
|
|\ \ \ \ |
|
| | |_|/
| |/| | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I4c19918a1f5f7e793d402aae23694b181f5766a5
|
|\ \ \ \ \
| |/ / / / |
|
| |/ / /
| | | |
| | | |
| | | | |
Change-Id: I579c0bf3a43d5e348c08cae96f13a4683f41d7ab
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
SearchView uses SearchManager.APP_DATA to pass data between the origin activity
and the search activity. This works for text searches (keyboard), but it's not
implemented by voice recognition searches. The method createVoiceAppSearchIntent
initializes a empty bundle that is filled with the QUERY parameter.
This patch adds the SearchManager.APP_DATA parameter if is present, let the
search activity access to the data passed by the origin activity
Change-Id: Ie88d32578d0a9dd01c464098a636a61397e89926
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Adding multiple UUID tags to a profile allows us to share a single NFC tag across multiple devices.
NFC tag writing works as before.
NFC tag reading is expanded to check the UUID and the UUID tags of a profile.
When reading unknown profiles, the user is asked to attach the tag to an exising profile.
The NFC tag itself stays untouched.
Patch Set 1:
* initial commit
Patch Set 2:
* rebase
* remove getProfileByTag() and use getProfile()
* rename tag to secondary uuid
Patch Set 3:
* rename "tag" leftovers
Change-Id: I284f8a823ced48d3b88ce3b3a1e83152cb145d2d
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I574c0315f0cadc65b064aa621e0f35160a369b2d
|
| |_|/ /
|/| | |
| | | |
| | | |
| | | | |
And datacall parameters, too
Change-Id: Ifc6f959044622bab2e7198ad15ce6f56dde370f7
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | | |
Change-Id: Ida791dca1fbfdc2beccf6ff727b67df56f1956a4
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
consistant on Tablets (2/2)
Change-Id: Ia1a703ce213fa7698a2fb8e1679eefccd521962b
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add a padding to the brightness control on both sides to make it easier
to reach the min/max brightness.
Change-Id: Ia42444321f82aaac97c0c442796dec551b1bcd65
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Related to : http://review.cyanogenmod.com/#/c/17561/1
Change-Id: Iace302f95cc73fa18bb6348d7739123f5529a41e
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
into ics
|
| |/ / /
| | | |
| | | |
| | | | |
Change-Id: Ibc2ea21b136aa390a371fa997c07c7dae7d83676
|
|\ \ \ \
| |_|/ /
|/| | | |
|
| |/ /
| | |
| | |
| | | |
Change-Id: Id9fb3dff7c3353d88013508e9dd573d17cf3e9fb
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove full overload of processUnsolicited and have it work with the
requests unknown by the RIL superclass. Pass everything else upwards,
unmodified.
Change-Id: I129120995c17b45c17dd50b77f281de352c20ae2
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I02f8e5e4a80b5fad999140cd65ae9e745e13c028
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This patch implements two simple performance enhancements, which
might benefit devices. They are completely opt-in by setting
the following variables.
* TARGET_BOOTANIMATION_PRELOAD: will preload the bootanimation
zip to memory; this is handy on devices where the storage
might be slow. By preloading it, we get quick access to the
zip file, and the animation doesn't stutter.
* TARGET_BOOTANIMATION_TEXTURE_CACHE: allows maintainers to
force texture cache on/off.
Also fixes the sign warnings related to int / size_t comparison
Change-Id: Ie92d1b0aa90b43ba39c368a2a33657a60c3a64b5
|
|/ / / /
| | | |
| | | |
| | | | |
Change-Id: Icf47a486a800f22c0fa837603f718d2893539e97
|
|\ \ \ \ |
|
| | |/ /
| |/| | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
into ics
|
| |/ / /
| | | |
| | | |
| | | | |
Change-Id: I7b6b3b93f66285f45db2752c7bde1385d87ec416
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Timestamp doesn't contain date info, therefore we need to construct it
and adjust it if daylight savings applies.
Change-Id: I931ff0f2ba93ab8172f2cbc69926aba1eab2778a
|
|\ \ \
| | | |
| | | |
| | | | |
into ics
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: Ic6f72fba542e1421631826d9bcd86340064c942b
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The format of /data/misc/wifi/ipconfig.txt is this one
<version>
<netA_key1><netA_value1><netA_key2><netA_value2>...<EOS>
<netB_key1><netB_value1><netB_key2><netB_value2>...<EOS>
On the defy, i had an error on boot regarding a missing "id" in NetworkStats,
so i compared on another device...
It appears that defy one format was :
<version><EOS>
<netA_key1><netA_value1><netA_key2><netA_value2>...<EOS>
I dont know exactly what caused this format error,
maybe because the quota and usage stats are enabled on it.
Change-Id: I4cf70fe88688341b8eea007a08910acb6f4fcff7
|
|\ \ \ \ |
|
| | | | | |
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Issue Description:
When do monkey test on some applications, there is big probability get ANR issue. one example is as following:
adb shell monkey -p com.google.android.street -v 500000
Root Cause:
situation 1. InputDispatcher Thread calls findTouchedWindowTargetsLocked routine, there is a AMOTION_EVENT_ACTION_DOWN event
and it can find a splittable touched window for this event , then mTouchState.split set to true.
situation 2. WMS Thread calls setInputWindows routine and all TouchedWindows associated with mTouchState are removed ,
mTouchState.split status still keep true.
situation 3. InputDispatcher Thread calls findTouchedWindowTargetsLocked routine, there is a AMOTION_EVENT_ACTION_POINTER_DOWN event
and it can find found touched window, exit window loop in following code :
if (windowInfo->visible) {
if (! (flags & InputWindowInfo::FLAG_NOT_TOUCHABLE)) {
isTouchModal = (flags & (InputWindowInfo::FLAG_NOT_FOCUSABLE
| InputWindowInfo::FLAG_NOT_TOUCH_MODAL)) == 0;
if (isTouchModal || windowInfo->touchableRegionContainsPoint(x, y)) {
if (! screenWasOff
|| (flags & InputWindowInfo::FLAG_TOUCHABLE_WHEN_WAKING)) {
newTouchedWindowHandle = windowHandle;
}
break; // found touched window, exit window loop
}
}
situation 4. The following code will have problem after situation 3 in below conditions:
newTouchedWindowHandle doesn't support split , isSplit is true ( last time touched window is splittable )
mTempTouchState.getFirstForegroundWindowHandle will always return NULL due to situation 2
// Figure out whether splitting will be allowed for this window.
if (newTouchedWindowHandle != NULL
&& newTouchedWindowHandle->getInfo()->supportsSplitTouch()) {
// New window supports splitting.
isSplit = true;
} else if (isSplit) {
// New window does not support splitting but we have already split events.
// Assign the pointer to the first foreground window we find.
// (May be NULL which is why we put this code block before the next check.)
newTouchedWindowHandle = mTempTouchState.getFirstForegroundWindowHandle();
}
The window says it does not want to support splitting, so the touches should go to one of the previously split windows except
that there are none, which result to "goto Unresponsive" in findtouchedWindowTargetsLocked routine.
This is not the correct behavior because the user did actually touch something.
situation 5. InputDispatcher Thread will call dispatchOnce repeated to try to dispatch this AMOTION_EVENT_ACTION_POINTER_DOWN event,
then ANR timeout ( 5000ms ) will be exceeded after several times "goto Unresponsive"in findtouchedWindowTargetsLocked routine.
Solution:
In situation 4 we should drop the touch. If the newly touched window was splittable then we wouldn't drop the touch.
It's only when the newly touched window was not splittable where we will drop the touch.
Change-Id: Iab2c06ce0597ac77eb886ccd9d84646c86723bdb
Author: Jeffrey Brown <jeffbrown@android.com>
Author: Erjun Ding <erjunx.ding@intel.com>
Author: Zhenghua Wang <zhenghua.wang@intel.com>
Author: Jack Ren <jack.ren@intel.com>
Author: Bruce Beare <bruce.j.beare@intel.com>
Conflicts:
services/input/InputDispatcher.cpp
|