ae0e03a9e03de34e37b768b971d7596d7220a053 |
|
26-Feb-2016 |
Svet Ganov <svetoslavganov@google.com> |
Cleanup of the PackageInstaller API - Frameworks The PackageInstaller app manages side-loading apps as well as permission management. It should be updatable, hence should rely on system APIs to talk to the platform. This is the first step of defining an API boundary. Change-Id: I9814eafd0b22ae03b4b847a7007cdbf14c9e5466
/frameworks/base/core/java/android/os/RemoteCallback.java
|
9c165d76010d9f79f5cd71978742a335b6b8d1b4 |
|
02-Dec-2015 |
Svet Ganov <svetoslavganov@google.com> |
Add optional permission review for legacy apps - framework For some markets we have to allow the user to review permissions for legacy apps at runtime despite them not supporting the new permission model. This is achieved by showing a review UI before launching any app component. If an update is installed the user should see a permission review UI for the newly requested permissions. To allow distinguishing which permissions need a review we set a special flag in the permission flags that a review is required. This flag is set if a runtime permission is granted to a legacy app and the system does not launch any app components until this flag is cleared. Since install permissions are shared across all users the dangerous permissions for legacy apps in review mode are represented as always granted runtime permissions since the reivew requirement is on a per user basis. Whether the build supports permission review for legacy apps is determined by a build constant allowing us to compile away the unnecessary code for markets that do not require a permissions review. If an app launches an activity in another app that has some permissions needing review, we launch the permissions review UI and pass it a pending intent to launch the activity after the review is completed. If an app sends a broadcast to another app that has some permissions needing review, we do not deliver the broadcast and if the sending app is in the foreground plus the broadcast is explicit (has a component) we launch the review UI giving it a pending intent to send the broadcast after the review is completed. If an app starts a service in another app that has some permissions needing review, we do not start the service and if the calling app is in the foreground we launch the review UI and pass it a pending intent to start the service after the review is completed. If an app binds to a service in another app that has some permissions needing review, we schedule the binding but do not spin the target service's process and we launch the review UI and pass it a callback to invoke after the review is completed which spins the service process and completes the binding. If an app requests a content provider in another app that has some permissions needing review we do not return the provider and if the calling app is in the foreground we show the review UI. Change-Id: I550f5ff6cadc46a98a1d1a7b8415eca551203acf
/frameworks/base/core/java/android/os/RemoteCallback.java
|
8ea138cbf12b140d43fd81f4f12fe1a9234f1f25 |
|
27-Jan-2010 |
Dianne Hackborn <hackbod@google.com> |
More work on device admins: - You can now show a dynamic message to the user when asking to have your DeviceAdmin added. - A DeviceAdmin can now provide a warning message that is displayed before a user disables it. - Better ordering (and text) of the policy warnings. - New API to set the maximum failed password attempts before the device wipes itself. - We now store the number of failed unlock attempts in persistent storage. - New managed dialog APIs that will be used by the settings app. Also a little bit of cleanup as I was working on this - removed the long unused MailboxNotAvailableException, fixed a java doc in Messenger.
/frameworks/base/core/java/android/os/RemoteCallback.java
|