summaryrefslogtreecommitdiffstats
path: root/core/res/AndroidManifest.xml
Commit message (Collapse)AuthorAgeFilesLines
* Add multi user support for bluetoothMatthew Xie2012-10-041-0/+7
| | | | | | | | Create a BLUETOOTH_STACK permission to share between all users of Bluetooth apk. Bluetooth Manager binds to apk of current user bug 6925422 Change-Id: I2df5546e977c2d77bc66d97d12479d933826922a
* Merge "Make the theme for choose account and choose account type dialogs ↵Jatin Lodhia2012-09-281-1/+1
|\ | | | | | | same." into jb-mr1-dev
| * Make the theme for choose account and choose account type dialogs same.Jatin Lodhia2012-09-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Contacts app uses a custom account picker which calls the system account picker when an account needs to be added. The system accout picker invokes choose accout type dialog which overlays over the system acccount picker. Because these two dialog boxes use different themes, he one behind is wider than the one in foreground and ends up looking like a thin black strip protruding from the two sides. Bug: 6980517 Change-Id: Ia8b23767d995dcbe1a58087cb4bfbee140c2c744
* | Merge "Fix issue #7211769 and #7244492, thrash around on #7226656." into ↵Dianne Hackborn2012-09-281-1/+2
|\ \ | | | | | | | | | jb-mr1-dev
| * | Fix issue #7211769 and #7244492, thrash around on #7226656.Dianne Hackborn2012-09-281-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #7211769: Crash dialog from background user has non-working "report" The report button now launches the issue reporter for the correct user. Also for crashes on background users, either disable the report button, or simply don't show the dialog depending on the build config. Issue #7244492: Bugreport button in Quick Settings doesn't actually do anything Now they do. Issue #7226656: second user seeing primary user's apps I haven't had any success at reproducing this. I have tried to tighten up the path where we create the user to ensure nothing could cause the user's applications to be accessed before the user it fully created and thus make them installed... but I can't convince myself that is the actual problem. Also tightened up the user switch code to use forground broadcasts for all of the updates about the switch (since this is really a foreground operation), added a facility to have BOOT_COMPELTED broadcasts not get launched for secondary users and use that on a few key system receivers, fixed some debug output. Change-Id: Iadf8f8e4878a86def2e495e9d0dc40c4fb347021
* | | Use updatable file for premium-sms filterRobert Greenwalt2012-09-281-0/+6
|/ / | | | | | | | | | | | | The data is really to big for a gservices-driven secure setting. bug:7221402 Change-Id: Ie3d4a1a0aeb69b9ef8fad360fa7ec32e927644e8
* | Global gesture to toggle Accessibility system-wide.Svetoslav Ganov2012-09-271-0/+6
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. This change adds a global gesture for enabling accessibility. To enable this gesture the user has to allow it from the accessibility settings or use the setup wizard to enable accessibility. When the global gesture is enabled the user can long press on power to bring the global actions dialog and then hold with two fingers for a few seconds to enable accessibility. The appropriate feedback is also provided. 2. The global gesture is writing directly into the settings for the current user if performed when the keyguard is not on. If the keygaurd is on and the current user has no accessibility enabled, the gesture will temporary enable accessibility for the current user, i.e. no settings are changed, to allow the blind user to log into his account. As soon as a user switch happens the new user settings are inherited. If no user change happens after temporary enabling accessibility the temporary changes will be undone when the keyguard goes away and the device will works as expected by the current user. bug:6171929 3. The initialization code for the owner was not executed due to a redundant check, thus putting the accessibility layer in an inconsistent state which breaks pretty much everything. bug:7240414 Change-Id: Ie7d7aba80f5867b7f88d5893b848b53fb02a7537
* Fix issue #7213113: Remove old intent resolverDianne Hackborn2012-09-211-0/+1
| | | | | | | Also make the query package restart broadcast protected like the documentation says it should be. Change-Id: I445166111318a02f2f2b1ab0dff9c641a441c20b
* Fire "dreaming started" and "dreaming stopped" broadcasts.John Spurlock2012-09-191-0/+15
| | | | | | | | | | | | | | | | | | Dream manager now fires broadcast intents when entering + exiting dreamland (except when testing). Power manager can now listen for dreams ending, using polling only as a backstop. Also: - Bullet-proof dream-manager/dream against known failure modes - Add new read/write dream permissions - Refactor dream-manager to delegate work + state management into a new DreamController class, via a handler Bug:6999949 Bug:7152024 Change-Id: I986bb7812209d8c95ae1d660a5eee5998a7b08b1
* Fix API review bugs.Dianne Hackborn2012-09-171-4/+4
| | | | | | | | | 7173152 API REVIEW: android.content.pm.PackageUserState 7172969 API REVIEW: android.app.PendingIntent 7172730 API REVIEW: android.content.Context 7172726 API REVIEW: android.manifest.permission Change-Id: Iad470256d3b5ca5596487f6a699ec1871457c3b5
* More adjustments to permissions.Dianne Hackborn2012-09-161-23/+15
| | | | | | | | | - New "cost money" flag can be put on a permission to have this emphasized in the UI. - Some further re-organization of permissions to better match UX spec. Change-Id: I450ac739eff6b90e7c7fc39589d68db82b61f897
* More multi-user stuff.Dianne Hackborn2012-09-151-0/+2
| | | | | | | | | | | | | | | | | | | | - New public APIs to find out when a user goes to the foreground, background, and is first initializing. - New activity manager callback to be involved in the user switch process, allowing other services to let it know when it is safe to stop freezing the screen. - Wallpaper service now implements this to handle its user switch, telling the activity manager when it is done. (Currently this is only handling the old wallpaper going away, we need a little more work to correctly wait for the new wallpaper to get added.) - Lock screen now implements the callback to do its user switch. It also now locks itself when this happens, instead of relying on some other entity making sure it is locked. - Pre-boot broadcasts now go to all users. - WallpaperManager now has an API to find out if a named wallpaper is in use by any users. Change-Id: I27877aef1d82126c0a1428c3d1861619ee5f8653
* Merge changes I69689a73,Iaaef6d41,I7e3cb47a,I42307f58 into jb-mr1-devGeremy Condra2012-09-131-0/+6
|\ | | | | | | | | | | | | | | * changes: DO NOT MERGE Push event logging down into libcore.EventLogger DO NOT MERGE Added event logging for config installation failures. DO NOT MERGE Create intermediate directories when installing config data. DO NOT MERGE Add components for the Android Config Updater to system server.
| * DO NOT MERGE Add components for the Android Config Updater to system server.Geremy Condra2012-09-121-0/+6
| | | | | | | | | | | | | | | | This adds the necessary bits to verify and install configuration updates using system server. It also includes the cert pinning updater as the first user. Change-Id: I42307f58074157b33b6e01216aab10022340d449
* | Bring back new permission organization.Dianne Hackborn2012-09-131-277/+564
|/ | | | Change-Id: I83e7dd06989ab7b0116bcff5ad52d36e01b851d1
* Merge "Fix bug #7141044 GlobalActions dialog (power off / airplane mode / ↵Fabrice Di Meglio2012-09-111-1/+2
|\ | | | | | | sound off) should be RTL aware" into jb-mr1-dev
| * Fix bug #7141044 GlobalActions dialog (power off / airplane mode / sound ↵Fabrice Di Meglio2012-09-101-1/+2
| | | | | | | | | | | | | | | | off) should be RTL aware - add android:supportsRtl="true" to the manifest for system_process Change-Id: I9794f6880c883d91751d0037646253810b086d46
* | Animations for user switching.Dianne Hackborn2012-09-101-0/+7
|/ | | | | | | | | | | | | | | The window manager now has a facility to provide a full-screen animation, which the activity manager uses every time a user switch happens. The current animation is just a simple dumb slide until we get a design from UX. Also some cleanup: moved the portrait task animations to the default config so we always have an animation for them, and finally got the java symbol stuff out of public.xml. Change-Id: I726f77422b2ef5f2d98f961f8da003e045f0ebe8
* Add new wifi display discovery API.Jeff Brown2012-09-081-0/+2
| | | | | | | | | The API is quite simple. There are a few extra functions on DisplayManager to scan, connect and disconnect from wifi displays and get status, and a single protected broadcast sent when the status changes. Change-Id: Ic91dbab5ee818e790b27fa32e1a1e93788793be0
* Add permissions to control and configure wifi display.Jeff Brown2012-09-071-0/+16
| | | | Change-Id: I54af6da53b7243516becd6a3d5985c0feda6c225
* Screen magnification - feature - framework.Svetoslav Ganov2012-09-061-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Notify verifiers that verification is completerich cannings2012-08-301-0/+1
| | | | | | | | | | Send the Intent.ACTION_PACKAGE_VERIFIED to all verifiers when verification is complete (either one verifier verified the package or a timeout occurred). Details of what occurred is in a new extra, PackageManager.EXTRA_VERIFICATION_RESULT. Bug: 7048930 Change-Id: I4f9855a29b0eb6d77f469891402c69e2e8922945
* Access to all users' external storage.Jeff Sharkey2012-08-301-0/+7
| | | | | | | | System services holding this permission have external storage bound one level higher, giving them access to all users' files. Bug: 7003520 Change-Id: Ib2bcb8455740c713ebd01f71c9a2b89b4e642832
* Start implementing concept of "running" users.Dianne Hackborn2012-08-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | The activity manager now keeps track of which users are running. Initially, only user 0 is running. When you switch to another user, that user is started so it is running. It is only at this point that BOOT_COMPLETED is sent for that user and it is allowed to execute anything. You can stop any user except user 0, which brings it back to the same state as when you first boot the device. This is also used to be able to more cleaning delete a user, by first stopping it before removing its data. There is a new broadcast ACTION_USER_STOPPED sent when a user is stopped; system services need to handle this like they currently handle ACTION_PACKAGE_RESTARTED when individual packages are restarted. Change-Id: I89adbd7cbaf4a0bb72ea201385f93477f40a4119
* Add permission checks for Verification API callsrich cannings2012-08-281-1/+0
| | | | | | | | | | Ensure that only applications with android.Manifest.permission.PACKAGE_VERIFICATION_AGENT can call application verification APIs, like PackageManager.verifyPendingInstall and PackageManager.extendVerificationTimeout Bug: 7049083 Change-Id: I5fc28b37e864d67cd319a1ed9d03a90dd15ad052
* Remove permission requirement for some UserManager callsAmith Yamasani2012-08-221-1/+1
| | | | | | | Update javadocs to be explicit about permissions. Minor fixes in UserManagerService Change-Id: I0d355e0a60e5dbdb49ed06091111d480ff249f3d
* UserHandle to UserSerialNo mappingAmith Yamasani2012-08-171-1/+9
| | | | | | | | | Use AtomicFile for usermanager files. Added a MANAGE_USERS permission that apps (signature permission) can use to create/query/modify/remove users. Change-Id: I5cf232232d0539e7508df8ec9b216e29c2351cd9
* Change directory permission to "signature|system"Subir Jhanb2012-08-161-1/+1
| | | | Change-Id: I53dea6984b4577803fdead5caad0112503d2b4e5
* Add a new permission to have access to Gal ProviderSubir Jhanb2012-08-081-0/+7
| | | | | | BUG:6897999 Change-Id: Ie60963b7f3911b402b971e794178754e1b4f0a43
* Add APIs for interacting across users.Dianne Hackborn2012-08-021-0/+19
| | | | | | | | | | | | | | | | - Expose the existing Context.sendBroadcast() as Context.sendBroadcastAsUser(). - Add new android:singleUser attribute for services. - Add new INTERACT_ACROSS_USERS_FULL permission for full system-level access to cross-user interface (allows sendBroadcastAsUser() to send to any receiver). - Add new INTERACT_ACROSS_USERS_FULL permission for more restricted cross-user interaction: this is required for android:singleUser, and allows you to use sendBroadcastAsUser() but only to send to your own receivers. Change-Id: I0de88f6718e9505f4de72e3f45d29c0f503b76e9
* Network data activity change intent for network interfaces.Haoyu Bai2012-07-171-0/+6
| | | | | | | | The activity notification is received from netd, an intent DATA_ACTIVITY_CHANGE is then raised for other part of the system to consume. Change-Id: Idfcc4763c51c5b314c57f546c12557082f06bebf
* Non persistent adapter servicefredc2012-07-161-0/+5
| | | | | | | | | | | | | | | | | | Change-Id: Ib13d5c77416e58161df0e04d7a15ec0dddbde8b5 Conflicts: core/java/android/bluetooth/BluetoothInputDevice.java Conflicts: core/java/com/android/internal/app/ShutdownThread.java services/java/com/android/server/SystemServer.java Conflicts: services/java/com/android/server/SystemServer.java services/java/com/android/server/pm/ShutdownThread.java
* Removing a workaround for incorrect window position on window move.Svetoslav Ganov2012-07-161-0/+13
| | | | | | | | | | | | | | | | | | | | | | 1. The window manager was not notifying a window when the latter has been moved. This was causing incorrect coordinates of the nodes reported to accessibility services. To workaround that we have carried the correct window location when making a call from the accessibility layer into a window. Now the window manager notifies the window when it is moved and the workaround is no longer needed. This change takes it out. 2. The left and right in the attach info were not updated properly after a report that the window has moved. 3. The accessibility manager service was calling directly methods on the window manager service without going through the interface of the latter. This leads to unnecessary coupling and in the long rung increases system complexity and reduces maintability. bug:6623031 Change-Id: Iacb734b1bf337a47fad02c827ece45bb2f53a79d
* Further work on MediaRouterAdam Powell2012-06-111-6/+0
| | | | | | | | | | Remove volume control and tracking. This will be handled by extensions to existing audio and media APIs for now. Tweak/refine other aspects of the API. Pass the router to callbacks for easier future-proofing. Add group/ungroup callback methods. Change-Id: Ib69e76e5f46280a9002b545bcf4cbc7b839844ee
* Docs (mostly): enumerate JELLY_BEAN target SDK changes.Dianne Hackborn2012-06-061-2/+1
| | | | | | | | | | | Okay this isn't entirely docs. I have un-hidden the new permission for binding to accessibility services; we were going to go out with it hidden since it didn't go into factory ROM, but now that we are doing other things we might as well expose it. Also changed a log from E to W, since it is not an error. Change-Id: I9226c95e3b63e12218fe41dc3f4290d9824a9e5c
* Merge "Add MediaRouter API." into jb-devAdam Powell2012-06-031-0/+6
|\
| * Add MediaRouter API.Adam Powell2012-06-011-0/+6
| | | | | | | | | | | | | | | | This is just the initial state tracking. Still to go is actually triggering Bluetooth A2DP correctly and tracking process state in the system server. Change-Id: I33031d52799d6e2d7208910da833831085cc3677
* | For JB, the READ_EXTERNAL_STORAGE permission is not enforced by default. It ↵Adrian Ludwig2012-06-011-6/+6
|/ | | | | | may be enforced by default in future releases. Developers have the option of enabling enforcement to test their application and some may begin to include this permission on applications. To avoid user confusion, the permission is placed in the development tools group. Change-Id: Id27ba241db0253eac774401aaaa6e5c4340588d7
* Revert "Make the protectionLevel of framework permissions consistent and ↵Adrian Ludwig2012-06-011-559/+272
| | | | | | | | | | | | | related to sensitive user data. Dangerous permissions are applied only where sensitive user data may be exposed." This reverts commit a8a200278dcc232eabd4550f814439c94857c47c. Conflicts: core/res/AndroidManifest.xml core/res/res/values/strings.xml Change-Id: I3f76d93a6ffde031bf82c2afea315ebcdbc179e3
* New UI for account pickerAlice Yang2012-05-291-1/+1
| | | | | | | | | | | | | - Added radio buttons to indicate the selected item - "Add account" is one of the list options instead of a button - Removed icons - Added "Cancel" and "OK" buttons - Use dialog theme - Omit description text by default Bug 6505441 Change-Id: I672a11481ee99e183142142bddf8f97b7b149d37
* Fixing the build for real.Svetoslav Ganov2012-05-161-1/+2
| | | | Change-Id: I792d029c7fff4d96fbe238ff4b3f268cb8603b95
* Adding some missing files.Svetoslav Ganov2012-05-161-0/+7
| | | | Change-Id: I991d8bf815a7e57dc1cbad384e15aa21bef0c7c7
* Hide SET_KEYBOARD_LAYOUT permissions.Jeff Brown2012-05-071-1/+2
| | | | | Bug: 6427036 Change-Id: Idbb442ad8071b2ca4acf247b135c7aba0830cf70
* Finish up issue #6249094: Display permissions based on relevance to private dataDianne Hackborn2012-05-061-37/+82
| | | | | | | | | | | | | | | Added bitmaps for permission group icons. We had to pick either icons for a dark or light background, and it had to be light for settings, so the installer theme has gone back to dark. Tweaked the permission groups to match the icons. Redid the group priorities to make them correct (they were written with higher priorities being less important). Fixed bug where priority was not being used for system apps. Change-Id: Ia3d3f0c1614a11b4cfd11682ce9e6c9f87d75c06
* Reorganizing permissions into groups oriented around user-understandable ↵Adrian Ludwig2012-05-021-270/+518
| | | | | | | | | concepts. These groups are assigned priority for sort-order when displayed to users, and use the new permissionGroupFlags to indicate whether they contain personalInfo. Change-Id: I27e81912e08b8d7766b8ce449b4b3bd6473d8f07
* Add new APIs for permission group flags and priorities.Dianne Hackborn2012-04-301-7/+6
| | | | Change-Id: I2d476c6aa9dbd05407ec49be45986f42d2acf9e7
* Migrate ringtone playback to SystemUI.Jeff Sharkey2012-04-271-0/+5
| | | | | | | | | | | | | Introduce IRingtonePlayer, which handles playback for both Ringtone objects and Notifications. SystemUI now hosts this player, which it registers with AudioService. It also keeps MediaPlayer instances warm, and cleans them up after stop() or Binder death. Move both Ringtone and NotificationManagerService to play back audio through this new interface. Bug: 6376128, 6350773 Change-Id: I1dcb86d16ee3c4f07cdb2248d33dcff4ead3609a
* Make audio routing Intents protectedMike Lockwood2012-04-261-0/+7
| | | | | | | | | | | | | | These intents should only be sent by the system: android.intent.action.HEADSET_PLUG android.intent.action.ANALOG_AUDIO_DOCK_PLUG android.intent.action.DIGITAL_AUDIO_DOCK_PLUG android.intent.action.HDMI_AUDIO_PLUG android.intent.action.USB_AUDIO_ACCESSORY_PLUG android.intent.action.USB_AUDIO_DEVICE_PLUG Change-Id: I7be41892a9c4e619ca3e1c892fad6f1f2714c74f Signed-off-by: Mike Lockwood <lockwood@google.com>
* Move RINGTONE_PICKER to handle external storage.Jeff Sharkey2012-04-251-10/+0
| | | | | | | | To give RINGTONE_PICKER external storage access, move it from system to MediaProvider. Fix OOBE when getRingtoneUri() kicked requery(). Bug: 6346701 Change-Id: I837002eef0580b8cdd8920a27b068c745995a8a3
* Merge "New API to allow third-party apps to bind widgets"Michael Jurka2012-04-241-0/+7
|\
generated by cgit v1.1 at 2025-02-09 11:14:04 +0000