| b23346639b66783c1662fd8ffa5345ef5cef336c |
|
23-Mar-2016 |
Russell Brenner <russellbrenner@google.com> |
Add new protection level for setup wizard
Adds PROTECTION_LEVEL_SETUP, a privileged permission for use only by
the setup wizard.
Bug: 20016740
Change-Id: Ib95e349c54d5d12465bf43162975dfb628ef2434
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| 2a1376d9dfb362a18ba110d8e172f96021f1d879 |
|
23-Feb-2016 |
Svet Ganov <svetoslavganov@google.com> |
Expose removed permissions flag as system API
There are some permissions that were removed from the platform
and guard nothing but legacy apps may be checking them before
calling APIs. Hence, these apps should get the permissions as
expected despite them being a no-op. To address this the platform
declares removed permissions as normal permissions that are hidden
such that legacy apps can always get them. These permissions are
not shown in the UI. Play needs a way to filter out these
permissions like the platform as they have permissions UI too.
bug:23361760
Change-Id: I10f442dfc09a299ddc5480d8bf2db0bd786aec62
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| 3e0be7440bf40f5d81581077bc4f5f47e57b88b7 |
|
08-Aug-2015 |
Svet Ganov <svetoslavganov@google.com> |
Do not show removed permissions in the UI - framework
bug:23043018
Change-Id: Ia5cf49f299eda627d9fde2b34498812afcb3a6d5
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| cfbfafe1b9ca2fd135a4fb6b528b3829830803bf |
|
22-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #22303510: Additional permissions aren't properly...
...disabled after toggling them off
Keep track of whether a permission that has been declared by an app
was able to actually be installed in the system, along with an API
to find this information so that system UI can tell whether that
permission is of interest.
Also clean up some of the permission debug output.
Change-Id: If4541bedb857789b255bb18f03cad155dcda0b95
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| a90c8def2c6762bc6e5396b78c43e65e4b05079d |
|
08-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Add new "preinstalled" permission flag.
This allows you to specify that a permission can be granted to
any pre-installed system app (not just privileged ones).
And as long as I am doing this, clean up the old "system" permission
flag, renaming it to "privileged" which is what it really is today,
deprecating the old names. And switch the platform's permission
declarations to use the new name.
Change-Id: Iabf484746af232144786851ec7fe90e3de9dddb2
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| 3e7d977ff7c743713f0ad6336a039d7760ba47d1 |
|
07-Jul-2015 |
Svetoslav <svetoslavganov@google.com> |
Grant installer and verifier install permissions robustly
bug:22248271
Change-Id: I3a47ae9a112ba7d88b421fcb5f9651d1168ba7a5
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| de15edaa9bf486a4050bb067317d313fd807bb10 |
|
01-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #21589105: Scope WRITE_SETTINGS and SYSTEM_ALERT_WINDOW...
...to an explicit toggle to enable in Settings
Add a new permission flag, saying the permission can be automatically
granted to pre-api-23 apps. Apply this to SYSTEM_ALERT_WINDOW.
Change-Id: I24a0ceabe7e9f5e458a864d30eda2696ad14a699
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| 6d2c0e5ee2f717d4a5c00df08aca21c76eea8278 |
|
23-Jun-2015 |
Svetoslav Ganov <svetoslavganov@google.com> |
Remove not needed contacts related permissions.
This reverts commit ed5ff51b2ca7c051e2719dfc8a8a083e6208848e.
Change-Id: If2407e4e474a438d95e1b7ad1aa6f441bb3ace08
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| e9b78fdbbef558f5e84f88397daf990dcc2e29cb |
|
13-Aug-2014 |
Jeff Sharkey <jsharkey@android.com> |
Fix javadoc on PROTECTION_FLAG_APPOP.
Change-Id: I36e339ac2c6e6842441fd2572b0b8cda24bd34ca
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| 33f5ddd1bea21296938f2cba196f95d223aa247c |
|
22-Jul-2014 |
Dianne Hackborn <hackbod@google.com> |
Add permissions associated with app ops.
Change-Id: I575ad7a3ceea59486ca601f69760b14f6269511d
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| 2ca2c8787130506d350d997c18bbc274faf88e37 |
|
17-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
More adjustments to permissions.
- 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
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| e639da7baa23121e35aa06d6e182558e0e755696 |
|
22-Feb-2012 |
Dianne Hackborn <hackbod@google.com> |
New development permissions.
These are permissions that an application can request, but won't
normally be granted. To have the permission granted, the user
must explicitly do so through a new "adb shell pm grant" command.
I put these permissions in the "development tools" permission
group. Looking at the stuff there, I think all of the permissions
we already had in that group should be turned to development
permissions; I don't think any of them are protecting public APIs,
and they are really not things normal applications should use.
The support this, the protectionLevel of a permission has been
modified to consist of a base protection type with additional
flags. The signatureOrSystem permission has thus been converted
to a signature base type with a new "system" flag; you can use
"system" and/or "dangerous" flags with signature permissions as
desired.
The permissions UI has been updated to understand these new types
of permissions and know when to display them. Along with doing
that, it also now shows you which permissions are new when updating
an existing application.
This also starts laying the ground-work for "optional" permissions
(which development permissions are a certain specialized form of).
Completing that work requires some more features in the package
manager to understand generic optional permissions (having a
facility to not apply them when installing), along with the
appropriate UI for the app and user to manage those permissions.
Change-Id: I6571785c6bb5f6b291862b7a9be584885f88f3a5
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| 9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|
| 54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/content/pm/PermissionInfo.java
|