summaryrefslogtreecommitdiffstats
path: root/services
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Add Binder.getCallingUserHandle()." into jb-mr1-devDianne Hackborn2012-09-071-1/+1
|\
| * Add Binder.getCallingUserHandle().Dianne Hackborn2012-09-071-1/+1
| | | | | | | | Change-Id: I2a7eedfdc7baeeb4c2cd2ca0153aa95e0cf0bf45
* | Merge "Explicitly specify current user everywhere home is started." into ↵Dianne Hackborn2012-09-072-12/+3
|\ \ | |/ | | | | jb-mr1-dev
| * Explicitly specify current user everywhere home is started.Dianne Hackborn2012-09-072-12/+3
| | | | | | | | Change-Id: I58d86136de7f9cef1eaf72793d0e200b852d7355
* | Disable hardcoded wifi display adapter.Jeff Brown2012-09-071-1/+2
| | | | | | | | Change-Id: Id0f7d59b6eafa8794ff7616cf54a0b94ba78c763
* | Merge "Fixing off by one error in the ScreenMagnifier." into jb-mr1-devSvetoslav Ganov2012-09-071-2/+12
|\ \ | |/ |/|
| * Fixing off by one error in the ScreenMagnifier.Svetoslav Ganov2012-09-071-2/+12
| | | | | | | | Change-Id: Ia0ccfb6b354b7a18633e7cf26647c6436ebf5c08
* | Merge "Make mirroring automatic based on Windows on display." into jb-mr1-devJeff Brown2012-09-074-19/+150
|\ \
| * | Make mirroring automatic based on Windows on display.Craig Mautner2012-09-074-19/+150
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tell the display manager whenever a given logical display contains interesting windows. If so, then the display manager arranges to show that content on a physical display, otherwise it ignores the logical display and makes its associated primary physical display mirror the default display. Assign DisplayContents when Displays are added, remove them when Displays are removed, and update the DisplayInfo when Displays change. Change-Id: I36e08ec538055acabe1e24cdd12c40de4e47a158
* | | Merge "Add support for Wifi display." into jb-mr1-devJeff Brown2012-09-078-97/+952
|\ \ \ | |/ /
| * | Add support for Wifi display.Jeff Brown2012-09-078-97/+952
| |/ | | | | | | Change-Id: I99693786cf9d07d07d3400046c55eb4933730b80
* | Merge "installd: fix forward locking symlink" into jb-mr1-devNick Kralevich2012-09-071-1/+6
|\ \
| * | installd: fix forward locking symlinkNick Kralevich2012-09-071-1/+6
| |/ | | | | | | | | | | | | | | installd was not creating a compatibility symlink when installing a forward locked application. Fix. Bug: 7121527 Change-Id: Ied507ab2b759d8658af563e6ac8f0dbb0d286cce
* | Merge "Move verification settings to Settings.Global" into jb-mr1-devrich cannings2012-09-071-6/+6
|\ \
| * | Move verification settings to Settings.Globalrich cannings2012-09-071-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move Settings.Secure.PACKAGE_VERIFIER_ENABLE, Settings.Secure.PACKAGE_VERIFIER_TIMEOUT, Settings.Secure.PACKAGE_VERIFIER_DEFAULT_RESPONSE to Settings.Global.PACKAGE_VERIFIER_ENABLE, Settings.Global.PACKAGE_VERIFIER_TIMEOUT, Settings.Global.PACKAGE_VERIFIER_DEFAULT_RESPONSE, respectively. Bug: 7082362 Change-Id: I21fde031a330563891c0129132f3d6369ac5e7a5
* | | Merge "Fix crash when setting wallpaper from non-primary user." into jb-mr1-devDianne Hackborn2012-09-072-2/+2
|\ \ \
| * | | Fix crash when setting wallpaper from non-primary user.Dianne Hackborn2012-09-072-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When accessing a content provider, there is a check for whether the provider can run in the caller's process; if so, even if the provider is currently published, we return to the caller that it can run locally. This check was broken -- it had an old condition that allowed content providers owned by the system UID to run in any other UID's process. This is wrong, since by definition the other UIDs would not be able to access the data under the original UID. We ran into this because the activity picker is part of the android platform manifest, so runs as the system process. However it needs to run as the user who invoked it, so when coming from the non-primary user we spin up a "system" process running as a uid of that user. Now when that process tries to access the settings provider, the broken check would think that a new instance of the settings provider should be created in the caller's process. Change-Id: I7bf495ed8370cb271bdaec073d5b7dda9e38c546
* | | | Merge "Fix incorrect indexing calculation." into jb-mr1-devCraig Mautner2012-09-071-4/+15
|\ \ \ \ | |_|/ / |/| | |
| * | | Fix incorrect indexing calculation.Craig Mautner2012-09-071-4/+15
| | | | | | | | | | | | | | | | | | | | | | | | Fixes bug 7129583. Change-Id: Ia395a7acded05686668d5b3cee09d49025a9f339
* | | | Merge "Resolve the correct home intent for secondary users" into jb-mr1-devAmith Yamasani2012-09-072-9/+29
|\ \ \ \
| * | | | Resolve the correct home intent for secondary usersAmith Yamasani2012-09-072-9/+29
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | Fix some searches through the Activity stack. This allows SetupWizard to be launched for the second user. Change-Id: Icd306319f511c902557bd9985d80dda228e32d96
* | | | Refer to STAY_ON_WHILE_PLUGGED_IN via the Global namespaceChristopher Tate2012-09-071-2/+2
| |/ / |/| | | | | | | | | | | | | | | | | | | | | | | It moved from System to Global, so writes are not automatically redirected to the new namespace (else apps would start crashing). Bug 7126575 Change-Id: Ief31fcb5a6107a098da04d30d146e16921dee776
* | | Merge "Refer to STAY_ON_WHILE_PLUGGED_IN in the global namespace" into ↵Christopher Tate2012-09-071-6/+6
|\ \ \ | |_|/ |/| | | | | jb-mr1-dev
| * | Refer to STAY_ON_WHILE_PLUGGED_IN in the global namespaceChristopher Tate2012-09-071-6/+6
| |/ | | | | | | | | | | | | This is the one relevant setting that moved from System to Global, a move that we do not automatically redirect on writes. Change-Id: I7b26d0c364695c4a10a7cd477db3dfcfe89d7ef5
* | More multi-user stuff:Dianne Hackborn2012-09-076-259/+414
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - New (hidden) isUserRunning() API. - Maintain LRU list of visited users. - New FLAG_IS_DATA_ONLY for ApplicationInfo. - Clean up pending intent records when force-stopping a user (or package). (Also fixes bug #6880627: PendingIntent.getService() returns stale intent of force stopped app) - Fix force-stopping when installing an app to do the force-stop across all users for that app. - When selecting which processes to kill during a force stop, do this based on the actual packages loaded in the process, not just process name matching. - You can now use --user option in am when starting activities, services, and instrumentation. - The am --user option accepts "current" and "all" as arguments. - The pm uninstall command now uninstalls for all users, so it matches the semantics of the install command. - PhoneWindowManager now explicitly says to start home in the current user. - Activity manager call to retrieve the MIME type from a content provider now takes a user argument, so it will direct this to the proper user. - The package manager uninstall paths are now implemented around PackageSetting, not PackageParser.Package. This allows them to work even if the application's apk has been removed (in which case it only exists as a PackageSetting, not the PackageParser.Package parsed from the apk). Change-Id: I3522f6fcf32603090bd6e01cc90ce70b6c5aae40
* Merge "Fault tolerance in Bluedroid" into jb-mr1-devMatthew Xie2012-09-071-0/+31
|\
| * Fault tolerance in BluedroidSyed Ibrahim M2012-09-061-0/+31
| | | | | | | | | | | | | | | | When bluetooth process gets crashed/killed/stopped by Android system, BluetoothManagerService will re-start AdapterService to recover from the crash appropriately. Change-Id: Iacb1a06a8245089517bbbd57de1378ca8ce4b41e
* | Include primary flag in StorageVolume.Jeff Sharkey2012-09-061-3/+2
| | | | | | | | | | Bug: 7003520 Change-Id: Iaae2ae22253820c954c51e0199c31087bc825f3f
* | Merge "Screen magnification - feature - framework." into jb-mr1-devSvetoslav Ganov2012-09-0612-220/+2619
|\ \
| * | Screen magnification - feature - framework.Svetoslav Ganov2012-09-0612-220/+2619
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change is the initial check in of the screen magnification feature. This feature enables magnification of the screen via global gestures (assuming it has been enabled from settings) to allow a low vision user to efficiently use an Android device. Interaction model: 1. Triple tap toggles permanent screen magnification which is magnifying the area around the location of the triple tap. One can think of the location of the triple tap as the center of the magnified viewport. For example, a triple tap when not magnified would magnify the screen and leave it in a magnified state. A triple tapping when magnified would clear magnification and leave the screen in a not magnified state. 2. Triple tap and hold would magnify the screen if not magnified and enable viewport dragging mode until the finger goes up. One can think of this mode as a way to move the magnified viewport since the area around the moving finger will be magnified to fit the screen. For example, if the screen was not magnified and the user triple taps and holds the screen would magnify and the viewport will follow the user's finger. When the finger goes up the screen will clear zoom out. If the same user interaction is performed when the screen is magnified, the viewport movement will be the same but when the finger goes up the screen will stay magnified. In other words, the initial magnified state is sticky. 3. Pinching with any number of additional fingers when viewport dragging is enabled, i.e. the user triple tapped and holds, would adjust the magnification scale which will become the current default magnification scale. The next time the user magnifies the same magnification scale would be used. 4. When in a permanent magnified state the user can use two or more fingers to pan the viewport. Note that in this mode the content is panned as opposed to the viewport dragging mode in which the viewport is moved. 5. When in a permanent magnified state the user can use three or more fingers to change the magnification scale which will become the current default magnification scale. The next time the user magnifies the same magnification scale would be used. 6. The magnification scale will be persisted in settings and in the cloud. Note: Since two fingers are used to pan the content in a permanently magnified state no other two finger gestures in touch exploration or applications will work unless the uses zooms out to normal state where all gestures works as expected. This is an intentional tradeoff to allow efficient panning since in a permanently magnified state this would be the dominant action to be performed. Design: 1. The window manager exposes APIs for setting accessibility transformation which is a scale and offsets for X and Y axis. The window manager queries the window policy for which windows will not be magnified. For example, the IME windows and the navigation bar are not magnified including windows that are attached to them. 2. The accessibility features such a screen magnification and touch exploration are now impemented as a sequence of transformations on the event stream. The accessibility manager service may request each of these features or both. The behavior of the features is not changed based on the fact that another one is enabled. 3. The screen magnifier keeps a viewport of the content that is magnified which is surrounded by a glow in a magnified state. Interactions outside of the viewport are delegated directly to the application without interpretation. For example, a triple tap on the letter 'a' of the IME would type three letters instead of toggling magnified state. The viewport is updated on screen rotation and on window transitions. For example, when the IME pops up the viewport shrinks. 4. The glow around the viewport is implemented as a special type of window that does not take input focus, cannot be touched, is laid out in the screen coordiates with width and height matching these of the screen. When the magnified region changes the root view of the window draws the hightlight but the size of the window does not change - unless a rotation happens. All changes in the viewport size or showing or hiding it are animated. 5. The viewport is encapsulated in a class that knows how to show, hide, and resize the viewport - potentially animating that. This class uses the new animation framework for animations. 6. The magnification is handled by a magnification controller that keeps track of the current trnasformation to be applied to the screen content and the desired such. If these two are not the same it is responsibility of the magnification controller to reconcile them by potentially animating the transition from one to the other. 7. A dipslay content observer wathces for winodw transitions, screen rotations, and when a rectange on the screen has been reqeusted. This class is responsible for handling interesting state changes such as changing the viewport bounds on IME pop up or screen rotation, panning the content to make a requested rectangle visible on the screen, etc. 8. To implement viewport updates the window manger was updated with APIs to watch for window transitions and when a rectangle has been requested on the screen. These APIs are protected by a signature level permission. Also a parcelable and poolable window info class has been added with APIs for getting the window info given the window token. This enables getting some useful information about a window. There APIs are also signature protected. bug:6795382 Change-Id: Iec93da8bf6376beebbd4f5167ab7723dc7d9bd00
* | | Merge "Event logging for lockdown VPN state changes." into jb-mr1-devJeff Sharkey2012-09-062-0/+16
|\ \ \ | |/ / |/| |
| * | Event logging for lockdown VPN state changes.Jeff Sharkey2012-09-062-0/+16
| | | | | | | | | | | | | | | Bug: 7079350 Change-Id: I3670efe7f09c0fca55552b6a04a2be159b9beb3c
* | | Merge "Restrict lockdown and firewall to AID_SYSTEM." into jb-mr1-devJeff Sharkey2012-09-062-7/+24
|\ \ \ | |/ /
| * | Restrict lockdown and firewall to AID_SYSTEM.Jeff Sharkey2012-09-062-7/+24
| |/ | | | | | | | | Bug: 7076289 Change-Id: Iafa3054335e8b1c3c8c3b8db2a4191d4ed4c8c41
* | Merge "Limit certain actions to default Display." into jb-mr1-devCraig Mautner2012-09-065-80/+112
|\ \ | |/ |/|
| * Limit certain actions to default Display.Craig Mautner2012-09-055-80/+112
| | | | | | | | | | | | | | Stop messing up PhoneWindowManager state when passing in windows from non-default Display. Change-Id: I472f7a13c5e2241fbf1f79ae1c8045fd92af016c
* | Merge changes I4ef284da,Ie8cc69bd into jb-mr1-devDaniel Sandler2012-09-051-14/+1
|\ \ | | | | | | | | | | | | | | | * changes: Make the SystemUI stop the screen saver when a full-screen notification is posted. Do not play sounds or vibes for background users' notifications.
| * | Make the SystemUI stop the screen saver when a full-screen notification is ↵Daniel Sandler2012-09-051-14/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | posted. This keeps all the fullScreenIntent logic (including multiuser implications) in one place. Change-Id: I4ef284daf90464f105780ade1d971e9e081fbbb5
| * | Do not play sounds or vibes for background users' notifications.Daniel Sandler2012-09-051-0/+1
| | | | | | | | | | | | | | | | | | USER_ALL notifications will still play/vibe for any user. Change-Id: Ie8cc69bd1541193ed9c4207ef38a8d4898af0a9d
* | | am 342c6bc8: am 54099555: am 380a8e3d: Merge "Am: Clean mLaunchingProviders ↵Jean-Baptiste Queru2012-09-051-0/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | of all providers started by the client" * commit '342c6bc8e5edb5a0cfa2ad65162d559b7f2ad993': Am: Clean mLaunchingProviders of all providers started by the client
| * \ \ am 380a8e3d: Merge "Am: Clean mLaunchingProviders of all providers started ↵Jean-Baptiste Queru2012-09-051-0/+2
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | by the client" * commit '380a8e3d126374b0205e8452bf2b4b70779e2606': Am: Clean mLaunchingProviders of all providers started by the client
| | * \ \ Merge "Am: Clean mLaunchingProviders of all providers started by the client"Jean-Baptiste Queru2012-09-051-0/+2
| | |\ \ \
| | | * | | Am: Clean mLaunchingProviders of all providers started by the clientVairavan Srinivasan2012-09-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Launching providers is removed from mLaunchingProviders when the client process dies and works as long as the client process had requested just one provider and not otherwise. Fix is to make sure mLaunchingProviders is updated to remove all providers launched by the client process. Change-Id: Ib4b8b44b6a102762a6558f65fb2e6dbf11d725ea
* | | | | | am 11626a91: am 9eb3bd88: am 42a58ecd: Merge "Revert "Watchdog: Improvement ↵Jean-Baptiste Queru2012-09-051-55/+5
|\ \ \ \ \ \ | |/ / / / / | | | | | / | |_|_|_|/ |/| | | | | | | | | | | | | | of debuggability"" * commit '11626a91b6e695e7a8fa9e9a9f1a37df11cfb4e2': Revert "Watchdog: Improvement of debuggability"
| * | | | am 42a58ecd: Merge "Revert "Watchdog: Improvement of debuggability""Jean-Baptiste Queru2012-09-051-55/+5
| |\ \ \ \ | | |/ / / | | | | | | | | | | | | | | | * commit '42a58ecd27783d347242206bcffd4052cf1d5164': Revert "Watchdog: Improvement of debuggability"
| | * | | Revert "Watchdog: Improvement of debuggability"Jean-Baptiste Queru2012-09-041-55/+5
| | | | | | | | | | | | | | | | | | | | This reverts commit 9211b13c3268035b0da0c51ed2d6d5a578d45ff3.
* | | | | Merge "Make battery shutdown temperature configurable" into jb-mr1-devBrian Muramatsu2012-09-041-5/+10
|\ \ \ \ \
| * | | | | Make battery shutdown temperature configurableBrian Muramatsu2012-09-041-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug 7079455 Change-Id: I448f21231bf0548ef975f99482576acb24a1a70e
* | | | | | Merge "update to new SurfaceComposerClient API" into jb-mr1-devMathias Agopian2012-09-042-51/+34
|\ \ \ \ \ \
| * | | | | | update to new SurfaceComposerClient APIMathias Agopian2012-09-042-51/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Change-Id: I8f2c96df56fe3a851b8ec03bb8734db0b6bea3d5
generated by cgit v1.1 at 2025-02-13 07:09:22 +0000