| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I608363fc29cf6bce2439089e33d82f36f82986f9
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The new trace feature/code in 4.0.4, which will dump the app stack
trace every 500ms if an app can't be launched within 500ms, is
holding the global ActivityManagerService lock unnecessarily. It
slows down the app's startup.
Change-Id: I91fbb043912b4d1fcf3e80d8ac4e61cd20ad89d1
Solution: move the trace file write operations out of sync block.
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
http://review.cyanogenmod.com/#/c/18206/2 was
missing a few QCOM_HARDWARE #ifdefs even though its origin
was CAF. So far, 18206 has only had positive effects on
certain QCOM devices, and is a noop or breaks things on
non-QCOM.
Per discussion with arcee - #ifdef the rest as QCOM
Change-Id: I46684ef5e6c580137104ad81b4faf58858bbfdd3
|
| |
| |
| |
| |
| |
| |
| | |
play music via headset -> notification comes in -> music volume gets set to 0 ->
notification gets played -> music resumes with wrong (much lower) volume
Change-Id: I3961ed48d0687bacb60ee8d4ddc82575f06c908e
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
During setPreviewWindow call camera_preview_window instance will
be passed to the HAL. camera_preview_window instance will never change when
ANativeWindow is updated. Hence HAL tries to use old preview window
handle not knowing that the preview window is updated. Added the
check in camera interface to reset the preview handle based on
whether ANativeWindow instance is changed or not.
CRs-Fixed: 341892
Change-Id: I6743f24cbd4467025d6fe21098c7ce6813017d5e
Frameworks: Allow CameraService to set window when preview is not running
Change-Id: Iab3f652ed3a7639c660e85c98a837215985a3296
Camera: Enable metadata callback after snapshot
Change-Id: I734fc596b7549d4dcc00aee466e1c4be02e38c8d
CRs-fixed: 346728
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Android 4.0 cannot form multitouch events from multiple input
devices. So it is not possible to report one touchpoint from the
stylus position and, at the same time, another touchpoint from a
finger touch. Instead, when a new input device starts up the currently
active input is cancelled. This is highly undesirable while writing
with the pen.
The easiest solution is to ignore non-stylus touch events while the
stylus is within range (hovering) of the touchscreen. For example,
N-trig digitizers implement this in hardware. But wacom digitizers do
report pen data simultaneously with touch data. This patch disables
(non-stylus) touch input within 50ms of stylus data. On my Galaxy
Note this is necessary to make stylus input usable.
Change-Id: I9f458d85d8bf83d6cf03b467d46ce066fd55b7e0
|
|\ \ \
| | | |
| | | |
| | | | |
button without lockscreen" into ics
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
without lockscreen
Contributed by Andrea Arcangeli <andrea@cpushare.com>
Change-Id: I8fe581ae51b38b65540eaefba6c051101fd63021
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Enabled use of hardware switch for rotation lock
on android tablets containing this feature
such as the acer iconia a500
Change-Id: Iaaecf3c6e8ae74ae9f5aefffa2c9b7d547ef0119
|
|/ /
| |
| |
| |
| |
| | |
Modify rotation animation to use a screenshot instead of a black screen.
Change-Id: I71563680f5d7cb355dd50b8873fa1b420a131512
|
|/
|
|
|
|
|
|
| |
Adds Quiet hours support and ability to configure the led if the
device supports multiple colors for the Light - enabled via overlay
with default as 'false'
Change-Id: I905dde400ba0780066f2b2a20142eaa27e158655
|
|\
| |
| |
| | |
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.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Timestamp doesn't contain date info, therefore we need to construct it
and adjust it if daylight savings applies.
Change-Id: I931ff0f2ba93ab8172f2cbc69926aba1eab2778a
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
into ics
* changes:
Do not dispatch context selection events to non-visible fragments.
Fix potential NPE when saving fragment state.
Distance max set incorrectly
Fix for too many binder calls in packagemanager
Issue: Foreground activity performs [Resume] and [Pause] when any process died in sleep mode.
Prevent empty overflow popup when there are no overflow items.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The distance max used in the MotionRange is calculated
incorrectly.
Looks like a copy-and-paste error.
Change-Id: I2b6daab088df0fb69e05682b67ca33524ff35987
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The packagemanager uses a ParceledListSlice to send back its lists
of installed packages and apps. The list slice has a method append
which, in addition to adding the item to the list, also returns true
if the list has passed a size limit (about 1/4 of the total possible
IPC parcel size) to let the caller know that he should send the
slice. However, when used by the pm, it has an extra ! that makes it
send whenever it ISN'T over this limit instead (and conversely, not
send if it is under). This causes a lot more calls than needed since
it sends tiny one item slices instead of larger ones. This patch
removes the extra ! making it behave correctly.
Change-Id: I8db46d380a25406b55f3214aee1505e81949acc5
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
died in sleep mode.
Step to Reproduce
1) Turn off device’s screen. (Sleep mode)
2) Kill any process.
A. Engineer Version: kill [PID]
B. User Version: am force-stop [Package Name]
3) Foreground activity proceed [Resume] and [Pause] consecutively.
Reason: Since ICS version, activity goes to stopped status when screen turns off.
stopIfSleepingLocked( ) makes activity to stopped status but, pauseIfSleepingLocked( ) was used in GB
and, activity keep paused status and, this problem did not occur.
This change give effect to resuming activity when any process was killed.
Because, resume is proceed without exception for activity status.
The exception only filtered for [ActivityState.PAUSED] in sleep or shutdown mode.
and, resume complete flow when activity status was [ActivityState.STOPPED].
Solution for this issue:
We think that exception’s condition have to change if stopped activity status is intended in sleep mode.
According to activity life cycle, activity can not resume from stop status.
Also check [ActivityState.STOPPING]. :)
Change-Id: Icca3366ac30ffa3b18f6e2393e4d7309089ef26a
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A filtering check in writeLPr() mistakenly includes the first application UID
(10000) with the result that the package with UID 10000 is missing from
packages.list. This patch fix the error.
Change-Id: I3651beb346290db8e09317391b95a77aed1946b6
Signed-off-by: Magnus Eriksson <eriksson.mag@gmail.com>
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- LPA volume is sometimes reversed while doing volume Up&DOwn.
- Two different threads are trying to set volume, one by invoking
setSessionVolume() and other by invoking setStreamVolume().
But currently only setStreamVolume() is mutex protected. This
is leading to race condition and volume set second is getting
applied first.
- Fix is to acquire mutex in setSessionVolume() before setting
volume.
CRs-Fixed: 360973
Change-Id: I02ac979bf83c4f3589deb5c83ae816179735aa2b
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
Change-Id: I7ef9a98f5fcba4d156256e4a8cbc24d58df0c549
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | | |
Change-Id: Ibcd2ef50c536e99bce8f406525599987484f99cc
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
If an activity has bound servicesor content providers,
updateLruProcessInternalLocked will be called recursively with
the oomAdj flag set, resulting in several recalculations of oomAdj
with unchanged data. Doing it at the end of the top level call to
updateLruProcessInternalLocked should be sufficient.
Change-Id: I95e27011e1d3519f256a9bd756cbb18d43e8db29
|
| |
| |
| |
| |
| |
| |
| |
| | |
This adds an option to modify the device hostname used
in ip resolution. This is useful when connecting to the
android device in a dynamic dhcp environment.
Change-Id: I44e4771f4415a32fe66867d4dd90f1ad138341e1
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- When DVI monitor is connected, audio service should not be notified
- remove the redundant changes to check HDCP during boot up
- On connect, check for HDCP/DVI mode and handle audio accordingly
Change-Id: I2af352570eddd4820a9d5ee232f4e2f351c0c524
CRs-fixed: 324931
Update HDMI Notification mechanism and minor cleanup
-- Update HDMI notification mechanism to be based on switch
node, /devices/virtual/switch/hdmi
-- Remove unused SurfaceComposerClient object.
-- Use path /sys/devices/virtual/graphics instead of symlink
/sys/class/graphics
-- Remove support for intents HDMI_CABLE_CONNECTED,
HDMI_CABLE_DISCONNECTED, HDMI_CONNECTED, HDMI_DISCONNECTED.
-- Add support in AudioPolicyManager to handle non HDMI modes.
CRs-fixed: 325697
(cherry picked from commit dd1ef209a42794415b1a06ff947028b26f028fa9)
Change-Id: I07dc58c700b8a2f4c7e086c688e277ce66b3e4c3
HDMIService: Minor fixes in the HDMI Service
- When the cable is connected, set the best mode for HDMI,
no need to store the current best mode, as this can cause
issues when a different TV is connected.
- start the HDMIDaemon from the Service, this will help ensure
HDMI Mirroring works after framework reboot
CRs-fixed: 333941 333497
(cherry picked from commit eb4ade6e6908c49a2e624a71ff1265e14c0b4ec7)
Conflicts:
services/java/com/android/server/HDMIService.java
Change-Id: Ic87d1703065a284878e7e9c8adac3afb6def56ec
HDMIService: getModeOrder to return order based on resolution
- getModeOrder function used to return order based on the resolution,
modified that to be based on the best resolution
This fixes the problem where the HDMI TV used to support 1080p@30Hz
but still it was picking 1080p@24Hz
- mCurrentMode stores the current display mode on HDMI, reset it when
the cable is disconnected
(cherry picked from commit 91cb5160ca2b4aaee7cc8c01f6d7162e9c55d67a)
Change-Id: I3efbe385603560330600eab3adeb0da1f1e102aa
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
* The visible pointer icon when hovering or drawing with the stylus is
quite annoying when trying to actually draw with it. Turn it off by
default and add an option to turn it on.
Change-Id: I98b6e1ea929019ef12dbd4b2991c6c96c52cef5c
|
|/
|
|
| |
Change-Id: I210c1db65f8b5c41dcbcd559c0e7e0a53dd2df7f
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When using the transform value, read only last 4 bits
of it regarding the change of
transform value in Layer::setGeometry().
Change-Id: Icdb2c9d8c283867a273e9633a7a563516f6af637
Depends-on: 120066
|
|\ \
| | |
| | |
| | | |
into ics
|
| |/
| |
| |
| | |
Change-Id: I50f54c70c8b6bc808fa59ce589b0480780cc811b
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
-Fix the scissor computation for top and bottom frame in S3D.
-Fix the artifacts seen in top-bottom case by clearing the
color buffer with scissor applied.
CRs-fixed: 346986
(cherry picked from commit 241b5b6b41fa4e1b2eca3565fd27b454a6aff262)
Change-Id: I8fb98007f67351009762c4494e260142b998ddb5
|
| |
| |
| |
| | |
Change-Id: Ia6e67983008eca505cead7cd4cb196627f5e2f77
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Set sys.orientation.landscape to 1 when in landscape and to 0 when
in portrait orientation for devices that have rotating capacitive
buttons.
Change-Id: I5cf86834d3e09ead515e9de31391904d5aff3107
Signed-off-by: Evan McClain <aeroevan@gmail.com>
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is not QCOM specific, enable the feature for all
- Disable easily the iowait busy feature by a flag
This sysfs ondemand feature requires kernel >= 2.6.35
- Add a DBG flag to remove the on/off spams, only keep the notifications
I/CpuGovernorService( 2332): intent action: android.intent.action.SCREEN_ON
I/CpuGovernorService( 2332): intent action: android.intent.action.SCREEN_OFF
Change-Id: Ib1b393caaa5608f54cc8525ea3657fcab0dbf7fe
|