summaryrefslogtreecommitdiffstats
path: root/services
Commit message (Collapse)AuthorAgeFilesLines
* Allow two SurfaceViews inbetween the app and the wallpaper.Pal Szasz2010-09-031-0/+1
| | | | | | | | | | | | | | | | | | | | | When two SurfaceViews are used by an application, which is transparent and uses the wallpaper, only one of the SurfaceViews will be visible. The problem is that when trying to find the correct location for the wallpaper, the window manager locates the activity window and skips every window below it which is related. For the first SurfaceView this will be ok, since the SurfaceViews's attached window is the previous window. However for the second SurfaceView this condition will fail (the 2nd SurfaceViews attached window is not the previous window (which is the 1st SurfaceView)). The fix adds an extra check which detects this usecase (the windows are related if the attached window is the same as the attached window of the previous window). Change-Id: I368e9dd53455dc310f48d6d8c0be68350ff2b79e
* Revert "Shutdown when capacity is 0% and no charging or when battery is dead"Jean-Baptiste Queru2010-08-311-16/+4
| | | | | | | | | | | | | This reverts commit fd04143a47770256dabcfa4d8447127b3ec8b2bf. This break most automated tests because with this change, if the device is fully charged, it will simply turn off the screen, regardless if USB is connected to hsot PC or not; so for our tests, most of them are always connected to host PC, and fully charged 99% of the time, as soon as the screen turns off, the front-end test Activity will be suspended. Change-Id: I1e6590611af43812f1bac223dd31570d1d90cfc5
* Shutdown when capacity is 0% and no charging or when battery is deadImre Sunyi2010-08-261-4/+16
| | | | | | | | | | | Android framework does not shutdown when battery capacity is 0% and a charger is attached (USB or AC). This handling is incomplete since a charger might very well be attached but charging has stopped because USB suspended or the charging algorithm has stopped because of battery safety handling. Also shutdown when battery is reported 'dead'. This might happen although charging is present. Change-Id: If328260ebf4d38f912e4d2fad204431cbb19c993
* Add an API to request route to an IPv6 host.Banavathu, Srinivas Naik2010-08-191-2/+33
| | | | | | | Add API to create a route to an IPv6 host through a particular interface. Change-Id: I7649051e94832576e02b5f5ad17abe093d21d48e
* Merge "Make the LED colors when charging customizable by the vendor"Jean-Baptiste Queru2010-08-171-10/+21
|\
| * Make the LED colors when charging customizable by the vendorKenneth Andersson2010-08-031-10/+21
| | | | | | | | | | | | | | | | This commit will make the default LED colors in the NotificationManager for battery charge customizable via overlays. The blink on/off times are customizable in the same manner. Change-Id: I57ce93656cc4080f5b99554df0ada44c5b31e959
* | Revert "InputMethodService: Fix ignore case in showInputMethodPickerFromClient"satok2010-08-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit f2e67a5779d404b4791c6ab5b0d30dfb2c463514. Open Source Project CL: https://review.source.android.com/#change,16419 This change unexpectedly started preventing users from changing Input-Method. How to reproduce 1. Long press "?123" button in LatinIME 2. Select "Input method" 3. No window will open. Change-Id: Ie0d4b58900a9b06aa9d43f9fa0bea5165294fa30
* | InputMethodService: Fix ignore case in showInputMethodPickerFromClientVairavan Srinivasan2010-08-111-0/+1
| | | | | | | | | | | | | | | | Fix to avoid posting MSG_SHOW_IM_PICKER in showInputMethodPickerFromClient when ignoring the request from the client. Change-Id: Iff8a0809aea892b4493d5cffbb91adba2d74414e
* | InputMethodManagerService: Fix acore crash on boot upSrilakshmi Punuru2010-08-111-5/+5
| | | | | | | | | | | | | | | | At bootup, while starting the service, if the default Input Method is not set, it is trying to disable the icon even before the statusbar variable and the input method icon are initialized. Hence, initializing them before building the input method list. Change-Id: Ibde2ca3bd379d6620d84b75662ffad1a95a24fc6
* | Merge "Fix isUsbMassStorageConnected() will always return true"Jean-Baptiste Queru2010-08-111-1/+1
|\ \
| * | Fix isUsbMassStorageConnected() will always return trueTony Wu2010-08-101-1/+1
| |/ | | | | | | | | | | | | After UMS mounted, isUsbMassStorageConnected() will always return true even if USB is disconnected. It's because mUmsEnabling will always be ture. Change-Id: Ib24b2359ea2684eb0a9faeb880f383e87630e6e1
* | Merge "frameworks/base: Swap width and height of temporary buffer only with ↵Jean-Baptiste Queru2010-08-111-1/+1
|\ \ | | | | | | | | | orientation change"
| * | frameworks/base: Swap width and height of temporary buffer only withOmprakash Dhyade2010-08-101-1/+1
| |/ | | | | | | | | | | | | | | | | | | | | orientation change Current code swaps the width and height by assuming that aspect ratio of the buffer width and height will be same as that of the layout clip width and height. That is not always true. Change the check to orientation change. Change-Id: Ie387f3a7369025427484e4173cbde7a08df2b9d7
* | Merge "Sort the IME list before showing to user"Kenny Root2010-08-101-9/+13
|\ \ | |/ |/|
| * Sort the IME list before showing to userMac Wang2010-07-231-9/+13
| | | | | | | | | | | | The original list is unsorted so the order is random to users. For users who installed two or more Chinese IMEs, they may see Chinese IME, English IME, Chinese IME. That's odd to users.
* | Clear preferred activities when home process crashesMattias Larsson2010-07-301-1/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | If the "default" Home application has been replaced with a third-party app that is repeatedly crashing at start-up, there is no way for the user to clear the preferred activities or uninstall the bad application. If we clear the package preferred activities when the application crashes, the user will be prompted with the ResolverActivity at the next boot and can try using the app again or choose to use another Home application. Change-Id: I8ba8e95e6752916d50515d96c117d3084fa980fd
* | fix inaccurate copyrightsJean-Baptiste Queru2010-07-292-2/+0
| | | | | | | | Change-Id: I33b0f68f2da34ca4728211d83159cf32a127f6dd
* | Merge "move native services under services/"Jean-Baptiste Queru2010-07-2668-0/+26022
|\ \
| * | move native services under services/Mathias Agopian2010-07-2268-0/+26022
| |/ | | | | | | | | | | | | | | moved surfaceflinger, audioflinger, cameraservice all native services should now reside in this location. Change-Id: Icd7336f7289db35df9c8c1857a5122bb8a6f1c86
* | frameworks/base: Implement Mutual exclusion in BroadcastReceiverVairavan Srinivasan2010-07-221-4/+6
|/ | | | | | | Invoke forceStopPackageLocked after acquiring a lock on ActivityManagerService.this. Change-Id: I75a85da03418a87c26b89360cebd3bccc6a25e46
* Merge "replaced deprecated setButton Methods"Romain Guy2010-07-203-3/+7
|\
| * replaced deprecated setButton MethodsChristian Mehlmauer2010-07-203-3/+7
| | | | | | | | Change-Id: I8361377cda18ae060a53b84702a2cf9b6f3e8365
* | Remove the window from being a target for motion events when it is destroyed.Maciej Białka2010-07-191-0/+7
|/ | | | | | | | If window was destroyed when touch was pressed this destroyed window was still considered as a target for motion events. In some cases this could result with hang up inside event dispatch procedure. Change-Id: I2ede17a40b14b2f509ab3d2560abb65292324f45
* am 5827d3ea: Merge "Properly note the current active restore set\'s token" ↵Dianne Hackborn2010-06-241-1/+1
|\ | | | | | | | | | | | | | | | | into froyo Merge commit '5827d3eaf3c53d1dc3ab0d638d935c219a5515a6' into froyo-plus-aosp * commit '5827d3eaf3c53d1dc3ab0d638d935c219a5515a6': Properly note the current active restore set's token
| * Properly note the current active restore set's tokenChristopher Tate2010-06-241-1/+1
| | | | | | | | | | Bug: 2796780 Change-Id: Iad601ed96ae73cf34910a276350712e6af19bb4e
* | am 57f4503e: Work on issue # 2778549: Idle FRF72 is awake 18 mins more than ↵Dianne Hackborn2010-06-171-11/+57
|\ \ | |/ | | | | | | | | | | | | | | ERE27 in 13hr test Merge commit '57f4503e1a129d6a648f2378d36a060998a577a0' into froyo-plus-aosp * commit '57f4503e1a129d6a648f2378d36a060998a577a0': Work on issue # 2778549: Idle FRF72 is awake 18 mins more than ERE27 in 13hr test
| * Work on issue # 2778549: Idle FRF72 is awake 18 mins more than ERE27 in 13hr ↵Dianne Hackborn2010-06-171-11/+57
| | | | | | | | | | | | | | | | | | | | test Modify UIModeManager to not get location updates every thirty minutes. Instead it gets one once a day, and requests a new update when airplane mode is turned off or the time zone changes. Change-Id: I8044c27b5cd77709e4b872e2e8edd352f23e4af1
* | merge from open-source masterThe Android Open Source Project2010-06-152-0/+3
|\ \ | | | | | | | | | Change-Id: Ib9ec3f3b7418d064b643577156d7d16688b3048d
| * \ Merge "Fix that InputDeviceReaderThread that got killed during startup"Jean-Baptiste Queru2010-06-152-0/+3
| |\ \
| | * | Fix that InputDeviceReaderThread that got killed during startupChristian Petersson2010-06-062-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | InputDeviceReaderThread could be killed if a key or touch event was received before initiation made by PolicyThread was made. To solve this, the start call for the InputDeviceReader thread was delayed until initalization of the PolicyThread was done in the WindowManagerService. Change-Id: Ifa7de7ccfadd66ecc2b14c6273e9be32b8e0cb4a
* | | | merge from open-source masterThe Android Open Source Project2010-06-151-1/+1
|\ \ \ \ | |/ / / | | | | | | | | Change-Id: I4d7b0ec9895d8b090e0cdf2efb6731358a5d087c
| * | | Merge "Replaced deprecated String Constructor"Jean-Baptiste Queru2010-06-141-1/+1
| |\ \ \
| | * | | Replaced deprecated String ConstructorChristian Mehlmauer2010-05-251-1/+1
| | |/ / | | | | | | | | | | | | Change-Id: I91874093d69e230850c695b92da5f91391030d44
| * | | Merge "Fix for deadlock between StatusBarService and NotificationManagerService"Jean-Baptiste Queru2010-06-091-14/+19
| |\ \ \ | | |/ / | |/| |
| | * | Fix for deadlock between StatusBarService and NotificationManagerServiceObi Okafor2010-03-111-14/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A ServerThread holding a lock on mQueue in StatusBarService invoked a callback in NotificationManagerService which required a lock on mNotificationList. At the same time, a BinderThread holding a lock on mNotificationList was attempting to post a message to StatusBarService which requires lock on mQueue. The fix is to release the lock on mQueue in handleMessage() before running the actions at the end of the method.
| * | | Corrected debug message in WindowManagerJohan Alfven2010-05-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When WindowManager reports "Key dispatching timed out" it prints out information about the window state that was present at the time the key was sent to that window. There is a minor error in the class representing the recorded window state so that the currently focused window is printed instead of the recorded focused window. Change-Id: I29a5471ef725e30f812ffd57fd4597ce81c0c7f2
| * | | Remove ProximityAlerts Receiver when last ProximityAlert expires.Sean Foy2010-05-111-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove the ProximityAlerts update Receiver when the last ProximityAlert expires. Fixes issue 6900. Change-Id: Ida1970c084e71df47b204c64986a065cb75d0c13
| * | | Merge "Corrected repeat count for key repeat in input device."Dianne Hackborn2010-05-111-9/+26
| |\ \ \
* | \ \ \ am f4a502a2: Merge "Don\'t adjust lights if screen or button brightness is ↵Mike Lockwood2010-06-101-2/+8
|\ \ \ \ \ | | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | changed when the screen is off." into froyo Merge commit 'f4a502a235e9f9ea0bcd2d5ca4981dc6e1a619c4' into froyo-plus-aosp * commit 'f4a502a235e9f9ea0bcd2d5ca4981dc6e1a619c4': Don't adjust lights if screen or button brightness is changed when the screen is off.
| * | | | Merge "Don't adjust lights if screen or button brightness is changed when ↵Mike Lockwood2010-06-101-2/+8
| |\ \ \ \ | | | | | | | | | | | | | | | | | | the screen is off." into froyo
| | * | | | Don't adjust lights if screen or button brightness is changed when the ↵Mike Lockwood2010-06-101-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | screen is off. Change-Id: I798a240374c3a739e1f1eaf36fa9fdef8416f2a2 BUG: 2758292 Signed-off-by: Mike Lockwood <lockwood@android.com>
* | | | | | am 8f2ca788: Merge "Fix bug 2757693 - Multi-touch coordinates can jump when ↵Adam Powell2010-06-101-0/+2
|\ \ \ \ \ \ | |/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a finger goes down." into froyo Merge commit '8f2ca788f369892370477212cf9e7a67721a8c16' into froyo-plus-aosp * commit '8f2ca788f369892370477212cf9e7a67721a8c16': Fix bug 2757693 - Multi-touch coordinates can jump when a finger goes down.
| * | | | | Merge "Fix bug 2757693 - Multi-touch coordinates can jump when a finger goes ↵Adam Powell2010-06-101-0/+2
| |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | down." into froyo
| | * | | | | Fix bug 2757693 - Multi-touch coordinates can jump when a finger goes down.Adam Powell2010-06-091-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Change-Id: I26bd54cec739ca8d91d2c2b18b90134f20dbd907
* | | | | | | am a2c6d5bf: do not merge: cherry-picked ↵Nick Kralevich2010-06-101-1/+6
|\ \ \ \ \ \ \ | |/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 929b4855b8208d36272769e8eeaa6cd2823b94c0 from master branch Merge commit 'a2c6d5bf308181c019ade0aac6d25fe33dc3d76c' into froyo-plus-aosp * commit 'a2c6d5bf308181c019ade0aac6d25fe33dc3d76c': do not merge: cherry-picked 929b4855b8208d36272769e8eeaa6cd2823b94c0 from master branch
| * | | | | | do not merge: cherry-picked 929b4855b8208d36272769e8eeaa6cd2823b94c0 from ↵Nick Kralevich2010-06-101-1/+6
| |/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | master branch Change-Id: Ie20371234a531f65f523682a0d0c27394dc30afa
* | | | | | am 75b6a6b9: Merge "Fix 2737842: Disable KeguardManager API if device policy ↵Jim Miller2010-06-082-37/+68
|\ \ \ \ \ \ | |/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | is enabled" into froyo Merge commit '75b6a6b972e6b18143fd629d3d9c824c442c5f4c' into froyo-plus-aosp * commit '75b6a6b972e6b18143fd629d3d9c824c442c5f4c': Fix 2737842: Disable KeguardManager API if device policy is enabled
| * | | | | Fix 2737842: Disable KeguardManager API if device policy is enabledJim Miller2010-06-082-37/+68
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds notification to find out when the device policy has changed. When an admin adds or changes a policy, we get notified and reset the state of keyguard to be enabled. It also moves disabling keyguard into the TokenWatcher.acquired() method to avoid disabling keyguard when a policy doesn't permit it. This avoids reference counting issues in TokenWatcher and hence relieves the ordering issue. There is one remaining caveat. An application that uses KeyguardManager to disable keyguard will need to disable keyguard again after any policy change. Tested: Install and run app that disables keyguard with no admin. Result: keyguard is enabled/disabled as expected. Enable admin and set quality = "something" after installing & running app. Result: keyguard is enabled. Change admin password quality to "unspecified" and re-run app (per caveat). Result: keyguard is disabled. Change admin password quality to "something" again. Result: keyguard is enabled. Disable admin : Result: keyguard is enabled until app runs again (per caveat). Added minor cosmetic changes after review. Change-Id: I302f2b01446bf031f746b0f3e8b5fd7a6cc0e648
* | | | | am bde25c20: Merge "Fix 2737842: disable keyguard API when device policy is ↵Jim Miller2010-06-071-18/+43
|\ \ \ \ \ | |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | enabled." into froyo Merge commit 'bde25c207731783a62e3611586fe05cd35add0d9' into froyo-plus-aosp * commit 'bde25c207731783a62e3611586fe05cd35add0d9': Fix 2737842: disable keyguard API when device policy is enabled.
| * | | | Merge "Fix 2737842: disable keyguard API when device policy is enabled." ↵Jim Miller2010-06-071-18/+43
| |\ \ \ \ | | | | | | | | | | | | | | | | | | into froyo
generated by cgit v1.1 at 2025-11-26 18:46:27 +0000