summaryrefslogtreecommitdiffstats
path: root/services
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Complete implementation of the advanced print options." into klp-devSvetoslav2013-10-281-6/+14
|\
| * Complete implementation of the advanced print options.Svetoslav2013-10-281-6/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Implemented the advanced printer options integration. Now a print service may declare an advanced print options activity which may be launched by the user if the current printer supports advanced print options. These options are visible only to the print service that added them and it is the only party that will interpret the options. 2. Fixed a couple of bugs in the saved print jobs parsing. One was that if there are more than one page range, a half of the print job properties was not properly parsed. The other was that the media size constructor was using incorrect argument order, thus creating a media size with wring width. 3. Fixed and edge case where old print jobs and their docs can get stuck in the spooler. If the app did not write the requested pages we were not showing an error message, rather just finish the activity without canceling the print job and this print job is stuck in the spooler. Now we show an error message and the user may retry, cancel. If the user cancels the print job is also cancelled, thus no leftover in the spooler. 4. Fixed the background color of the print dialog to meet UX spec. bug:11241800 Change-Id: I352440bc86aec824a805883fc9579d96a06d11e6
* | Merge "Fix issue #11391003: Allow dumpsys meminfo to be used with native ↵Dianne Hackborn2013-10-281-14/+69
|\ \ | | | | | | | | | processes" into klp-dev
| * | Fix issue #11391003: Allow dumpsys meminfo to be used with native processesDianne Hackborn2013-10-251-14/+69
| | | | | | | | | | | | Change-Id: I005e4dc763deafac95dc3aa6261c06d1808fdaff
* | | Merge "Always re-evaluate kernel alarm setpoints when a new alarm is added" ↵Christopher Tate2013-10-281-8/+3
|\ \ \ | |_|/ |/| | | | | into klp-dev
| * | Always re-evaluate kernel alarm setpoints when a new alarm is addedChristopher Tate2013-10-281-8/+3
| |/ | | | | | | | | | | | | | | ...even if the new one is later than some other existing alarms. Bug 11392699 Change-Id: I80dccd76300acb4729f0337665b91e897a770571
* | Merge "Change order of operations so flag is not overwritten" into klp-devCraig Mautner2013-10-281-1/+1
|\ \ | |/ |/|
| * Change order of operations so flag is not overwrittenCraig Mautner2013-10-251-1/+1
| | | | | | | | | | | | | | | | | | | | The effects of the flag, Intent.FLAG_ACTIVITY_TASK_ON_HOME was being overwritten by the call immediately after it was set. Changing the order of operations leaves the effect intact. Fixes bug 11376962. Change-Id: I27371e0efeb0c08d1e14514a9e3a63157f6d34d8
* | Merge "Fix issue #11374840: adb shell am startservice not working any more" ↵Dianne Hackborn2013-10-251-10/+0
|\ \ | | | | | | | | | into klp-dev
| * | Fix issue #11374840: adb shell am startservice not working any moreDianne Hackborn2013-10-251-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The startService() and stopServie() calls had a redundant check for the incoming user ID being valid, but with its own custom implementation that doesn't match the normal handleIncomingUser flow. In fact, for both of these we are going to do handleIncomingUser anyway when we get to retrieveServiceLocked(), so there was just no need for this. Change-Id: I14409a03781a14a5f1a786aceb31dcc77efb062c
* | | Merge "Add a method to set a list of uids for a wake lock" into klp-devMarco Nelissen2013-10-251-0/+15
|\ \ \
| * | | Add a method to set a list of uids for a wake lockMarco Nelissen2013-10-251-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cherrypicked from master. b/9464621 Change-Id: Ia6a9d36d55129ae87d3ec070fbf10dc02f4b6cb4
* | | | Merge "Do not take screenshots when launching activities..." into klp-devCraig Mautner2013-10-251-1/+4
|\ \ \ \ | |/ / / |/| | |
| * | | Do not take screenshots when launching activities...Craig Mautner2013-10-241-1/+4
| | |/ | |/| | | | | | | | | | | | | | | | | | | Unless they are in another task. Fixes bug 11374158. Change-Id: I961d4ce9520bc84a182806db2ccb072501c8357a
* | | Merge "Have the package manager write mimetype of preferred activities to ↵Erin Dahlgren2013-10-241-2/+11
|\ \ \ | |_|/ |/| | | | | xml." into klp-dev
| * | Have the package manager write mimetype of preferred activities to xml.Erin Dahlgren2013-10-241-2/+11
| | | | | | | | | | | | | | | Issue: 11372979 Change-Id: I5ea4e94c978845426e2650946d0bba076d161c19
* | | Merge "Track window position with task position." into klp-devCraig Mautner2013-10-243-19/+39
|\ \ \
| * | | Track window position with task position.Craig Mautner2013-10-243-19/+39
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Windows were previously ordered by TaskStack/ActivityStack order. This change provides a data structure in DisplayContent that tracks task movement. Previously Recents and Home activity windows were always adjacent because they were on the same stack. With this change windows from other activities can be placed between the two. Fixes bug 11338594. Change-Id: Ie34443ff22f330d015141d97db79370c54920d28
* | | Merge "Support different watchdog timeouts for different entities" into klp-devChristopher Tate2013-10-242-37/+87
|\ \ \
| * | | Support different watchdog timeouts for different entitiesChristopher Tate2013-10-242-37/+87
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to be able to perform very lengthy operations on some threads (e.g. the I/O thread responsible for installing multi-gigabyte APKs) but still have long-run deadlock/hang detection applied to those threads. Previously the watchdog mechanism applied the same policy to all monitored threads: unresponsive after 60 seconds => restart the system. Now, each monitored entity can have its own independent timeout after which the watchdog declares deadlock and restarts the runtime. The halfway-finished intermediate thread stacks are dumped based on the specific entity's declared timeout, not the global 30 second checking interval. With that new mechanism in place, the Package Manager's lengthy-I/O thread watchdog timeout is raised to 10 minutes. Bug 11278188 Change-Id: I512599260009c31416b2385f778681e5b9597f05
* | | Merge "Disable time consuming debugging code." into klp-devCraig Mautner2013-10-241-1/+1
|\ \ \
| * | | Disable time consuming debugging code.Craig Mautner2013-10-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Scanning bitmaps for monochromicity takes time. Lots of time. Don't do it. Fixes bug 11366278. Change-Id: I7a8ad42751311fc39efc27fb4c51522fc1ba0523
* | | | Merge "Improve Jank for translucent activities" into klp-devAdam Lesinski2013-10-241-17/+3
|\ \ \ \ | |_|_|/ |/| | |
| * | | Improve Jank for translucent activitiesAdam Lesinski2013-10-231-17/+3
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous jank improvement only worked when closing an app, not when bringing one forward (hitting home button). This should cover the specific case that is being missed: Having the Home task being brought to front over a translucent window, with a wallpaper behind both tasks. bug:11253262 Change-Id: I200ef6fe2dda8d9ab4e1f82059b4f888c59007f4
* | | Merge "Search further than one task for fullscreen." into klp-devCraig Mautner2013-10-231-18/+38
|\ \ \
| * | | Search further than one task for fullscreen.Craig Mautner2013-10-231-18/+38
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | When a non-fullscreen task over home launches another non-fullscreen task then the home task might not be displayed. Looking all the way down the task stacks until reaching a visible, fullscreen activity or home provides the right information. Fixes bug 11273803. Change-Id: I8dab0956c1cda06ddb7850ea3ffac7f6a223c6ad
* | | Decouple IME_ACTIVE and IME_VISIBLE for hardware keyboards.John Spurlock2013-10-231-2/+6
| |/ |/| | | | | | | | | | | | | Reserve IME_VISIBLE for when software keyboards are actually showing. Bug:11186297 Change-Id: I4e09a7de353e564bd1a97dadd603d3104254fa56
* | Merge "Fix issue #11278906: Some wm commands fail on shell users" into klp-devDianne Hackborn2013-10-231-38/+64
|\ \
| * | Fix issue #11278906: Some wm commands fail on shell usersDianne Hackborn2013-10-231-38/+64
| | | | | | | | | | | | | | | | | | Binder.clearCallingIdentity makes everything better. Change-Id: I31cd9478c857553b3cf1ea54d5b4987571788796
* | | Merge "Fix issue #11323037: Android apk incorrectly marked as running in app ↵Dianne Hackborn2013-10-233-25/+59
|\ \ \ | | | | | | | | | | | | processes" into klp-dev
| * | | Fix issue #11323037: Android apk incorrectly marked as running in app processesDianne Hackborn2013-10-223-25/+59
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The android package is now a special case, not being added to the package list when creating a multi-process component. There is no need, since this package is actually the framework itself which must be loaded in every process. Also cleaned up some of the procstats dump output to help see what is going on here. Change-Id: If65d35ecd562f3154bdebfded69c454af6ce8c96
* | | Merge "Edge case: overriden system package moved & became privileged in OTA" ↵Christopher Tate2013-10-222-7/+13
|\ \ \ | | | | | | | | | | | | into klp-dev
| * | | Edge case: overriden system package moved & became privileged in OTAChristopher Tate2013-10-222-7/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because properly continuing permission grants post-OTA has changed policy to include privilege considerations based on install location, make sure that we re-evaluate when we determine that the apk has moved from its pre-OTA location. Bug 11271490 Change-Id: I6c09986e2851a67504268b289932588457c05dfc
* | | | Don't use transient states for wallpaper animation.Craig Mautner2013-10-223-11/+10
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The WindowManagerService member mLowerWallpaperTarget is not stable throughout an app transition. Relying on it to be stable causes the intra-wallpaper animation to start out right but after the windows have been relayed out there is no longer a lower wallpaper target. This causes the wallpaper to start tracking the animation of the current wallpaper target rather than remain stable. Switching to a new variable that saves the state of wallpaper animation at the start of the animation fixes bug 11240590. Change-Id: I336a59c47665fcf61019f567b8663956ff0e4940
* | | Merge "Check for home activity when switching focus." into klp-devCraig Mautner2013-10-221-10/+16
|\ \ \ | |/ / |/| |
| * | Check for home activity when switching focus.Craig Mautner2013-10-221-10/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When finishing or stopping an activity the code was automatically refocusing to the next activity on the same stack independent of the task's onTopOfHome flag. When the activity eventually finished or stopped it would then honor the onTopOfHome flag. This fix examines the onTopOfHome flag and arranges the focus correctly if home is the next activity to run. Fixes bug 11318263. Change-Id: I73a8f5e82de04b01acaffe366b085f9e475e1451
* | | Merge "Make sure mFocusedStack is never the home stack." into klp-devCraig Mautner2013-10-221-11/+14
|\ \ \
| * | | Make sure mFocusedStack is never the home stack.Craig Mautner2013-10-221-11/+14
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were circumstances where mFocusedStack could be assigned the home stack. If this were ever to occur then all subsequent tasks would be put on the home stack. This fix ensures that there is no way that mFocusedStack will ever be assigned to the home task. Fixes bug 11271189. Change-Id: I7ddd9b6bcbf2787cbe2f44b461ad057ae2241f00
* | | Merge "Do not delete stacks that are not empty." into klp-devCraig Mautner2013-10-221-1/+6
|\ \ \
| * | | Do not delete stacks that are not empty.Craig Mautner2013-10-211-1/+6
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The possibility existed that an activity was set to a task that it was already being set to. If that were to happen, and it was the only activity in the only task of the stack the stack would be deleted. This fixes that situation and logs it as well to confirm that it does fix bug 11272935. Logging to be deleted upon successful monkey run exhibiting the log. Change-Id: I436fdcc9a3734adad81d3ef90f29b93b3ac4dfcd
* | | Merge "Fix issues catching up to touch events after a short pause." into klp-devJeff Brown2013-10-221-1/+1
|\ \ \
| * | | Fix issues catching up to touch events after a short pause.Jeff Brown2013-10-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the app spends more than half a second responding to a touch event, the input dispatch eventually decides to stop sending it events until it catches up. (This is when the ANR clock starts.) However, due to a bug in the timing logic, if the app eventually does respond again we would resume delivery but only send one event at a time until the queue was completely drained again. This meant it could take a long time to catch up and process all events. The problem is that we were comparing the current time with the waiting event time. So when events became older than half a second, we would simply stop streaming and end up serialized. This change fixes the timing logic such that the streaming timeout is based on the delivery time of the waiting event rather than the event time itself. Now we only stop streaming when it has been over half a second since the waiting event was delivered so we resume streaming immediately as soon as some waiting events are handled. Bug: 11278743 Change-Id: Ic8c68ee372a07f7caa4168eefcabf9b8a8ad5d87
* | | | Merge "Preserve window sizes when rebatching alarms" into klp-devChristopher Tate2013-10-221-11/+24
|\ \ \ \
| * | | | Preserve window sizes when rebatching alarmsChristopher Tate2013-10-211-11/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The existing code wasn't retaining the requested window bounds, if any, and so could wind up rebatching alarms into much longer potential delivery windows than originally demanded by the caller. This could wind up delivering alarms outside their designated windows entirely. Bug 11324357 Change-Id: I4d418cd08702e397b3c7692b412d4bf51d5d9e4b
* | | | | Merge "Fix jank for translucent window transitions" into klp-devAdam Lesinski2013-10-221-0/+14
|\ \ \ \ \ | |_|_|_|/ |/| | | |
| * | | | Fix jank for translucent window transitionsAdam Lesinski2013-10-211-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a translucent window is closing, the transition animation to Launcher is janky because Launcher is expected to be 'opening' but it has always been open underneath the translucent window. Therefore, the animation applied to the translucent app appears janky. bug:11253262 Change-Id: I9b6af3291d119e6927401f63785b12f25573f4eb
* | | | | Merge "Make setting PAC require CONNECTIVITY_INTERNAL" into klp-devJason Monk2013-10-211-2/+17
|\ \ \ \ \ | |_|/ / / |/| | | |
| * | | | Make setting PAC require CONNECTIVITY_INTERNALJason Monk2013-10-211-2/+17
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also disables all setting of PAC networks through the internal AsyncChannel methods. PAC can only be saved through addOrUpdateNetwork for permission checks. Bug: 11316946 Change-Id: I51016b578080c342a5e5d536ea9a3fdd4fe16644
* | | | Merge "Fix priv-app edge case across OTAs" into klp-devChristopher Tate2013-10-213-5/+15
|\ \ \ \ | |/ / / |/| | |
| * | | Fix priv-app edge case across OTAsChristopher Tate2013-10-183-5/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In this case: 1. Privileged system app FOO is overlain by an installed update, 2. FOO was replaced during an OTA, 3. The new in-system FOO introduced new privileged permission requests that had not been requested by the original FOO, 4. the update version of FOO still had a higher version code than the new FOO on the system disk, and 5. the update version of FOO had been requesting these same (newly- added-to-system-apk) permissions all along; then the newly-added privileged permission requests were incorrectly being refused. FOO should be able to use any privileged permission used by the APK sited on the system disk; but instead, it was only being granted the permissions used by the *original* version of FOO, even though the system FOO now attempted to use them. Still with me? The fix is to (a) properly track privileged-install state when processing known-to-be-hidden system packages, and (b) to tie the semantics of the permission grant more explicitly to that evaluated state, rather than using the prior (rather fragile) fixed-up privilege calculation applied to the overlain apk's parse records. Bug 11271490 Change-Id: Id8a45d667e52f3b5d18109e3620d5865f85bb9c9
generated by cgit v1.1 at 2025-02-19 01:07:16 +0000