d86b8fea43ebb6e5c31691b44d8ceb0d8d3c9072 |
|
03-Jun-2017 |
Jeff Sharkey <jsharkey@android.com> |
Annotate @SystemApi with required permissions. Most @SystemApi methods should be protected with system (or higher) permissions, so annotate common methods with @RequiresPermission to make automatic verification easier. Verification is really only relevant when calling into system services (where permissions checking can happen on the other side of a Binder call), so annotate managers with the new @SystemService annotation, which is now automatically documented. This is purely a docs change; no logic changes are being made. Test: make -j32 update-api && make -j32 offline-sdk-docs Bug: 62263906 Change-Id: I2554227202d84465676aa4ab0dd336b5c45fc651
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
3b8b46f3a46ccf35a6bb6a828af0f2d011cc9abe |
|
13-Feb-2017 |
Andrew Scull <ascull@google.com> |
Service for OEM lock management. The new service separates OEM lock management from the implementation. Currently, a user restriction (DISALLOW_OEM_UNLOCK) and the persistent data block have been used to implement OEM lock management. In future, other implemention will be used e.g. a secure element. The new API also allows for a signature to be passed when changing whether the device is allowed to be OEM unlocked by the carrier which can be used for cryptographic protection of the flag. Bug: 34766843 Test: gts-tradefed run gts -m GtsOemLockServiceTestCases -t com.google.android.oemlock.gts.OemLockServiceTest Test: cts-tradefed run cts -m CtsPermission2TestCases -t android.permission2.cts.PrivappPermissionsTest Change-Id: I01660d7605d297f273d43436ca03d64ff611b6cf
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
c86c88f76f733c03f681bd47b64c9e44c5a81f68 |
|
01-Dec-2016 |
Charles He <qiurui@google.com> |
Remove IPersistentDataBlockService from system-api. Change-Id: I55e46c0815e4ef84b4d7a752cc72407f893ab569 Test: manual Bug: 33238174
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
a629c772f4a7a5ddf7ff9f78fb19f7ab86c2a9c2 |
|
24-Nov-2016 |
Charles He <qiurui@google.com> |
Prevent writing to FRP partition during factory reset. Avoid potential race condition between FRP wipe and write operations during factory reset by making the FRP partition unwritable after wipe. Bug: 30352311 Test: manual Change-Id: If3f024a1611366c0677a996705724458094fcfad
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
c48b20f8f1d3e07e8a931b195669b0ab8895006c |
|
11-Aug-2016 |
Esteban Talavera <etalavera@google.com> |
Do not toggle OEM unlock if bootloader unlocked Bug: 30681215 Change-Id: Ia0fd55dd7b6b731d6f5733fc733621e99bd7b153
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
f8880561e67e1da246970b49b14285efd4164ab1 |
|
26-Feb-2016 |
Jeff Sharkey <jsharkey@android.com> |
When system server goes down, crash apps more. Similar to first patch, but now using new "rethrowFromSystemServer()" method which internally translates DeadObjectException into DeadSystemException. New logic over in Log.printlns() now suppresses the DeadSystemException stack traces, since they're misleading and just added pressure to the precious log buffer space. Add some extra RuntimeInit checks to suppress logging-about-logging when the system server is dead. Bug: 27364859 Change-Id: I05316b3e8e42416b30a56a76c09cd3113a018123
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
74e9b18b2de2127e081b170cdd4622193cfb7543 |
|
22-Feb-2016 |
Andres Morales <anmorales@google.com> |
Add SystemApi for retrieving device flash lock state Bug: 26039090 Change-Id: Ib51c4862d897cc91a0788379c761ed49a2adf271
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
09ad6bfe9619ff7a61209131f1f3182d53d840d0 |
|
02-Jun-2015 |
Craig Lafayette <craiglafa@google.com> |
Remove FRP wipe support for device initializers - Remove ManagedProvisioning NFC parameter key from DevicePolicyManager - Remove wipeIfAllowed from PersistentDataBlockManager Bug: 21558883 Change-Id: I59354b7bb1ef7e0b0346ff9a7d1654780231dff0
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
66445a639dc134d09393f5069b7683ec36d4cd07 |
|
27-Mar-2015 |
Craig Lafayette <craiglafa@google.com> |
Reset protection in PersistentDataBlockManager Add method to allow authorized data block wipe in support of factory reset protection. This will allow ManagedProvisioning to respond to and pass factory reset protection challenges during automated device setup. - Adds the wipeIfAllowed method to clear the data block - Creates a protected-broadcast to send to allowed package Bug: 19792435 Change-Id: I897f2ea2afb1222a1fc8ac49290ee45ea4d3f2d7
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
396181b0cb0d8b83c6abde333963b2acf871272f |
|
13-Aug-2014 |
Andres Morales <anmorales@google.com> |
Mark PDBManager as a SystemApi This will allow us to XTS test these APIs Change-Id: Ife942f73580ea24eb6801b079b642d7c67107ab0
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
963295ea105314e28e4ca9563aa09cb7440de4c3 |
|
11-Jul-2014 |
Andres Morales <anmorales@google.com> |
Permit settings to "wipe" the persistent partition One of the requirements is that when the user does a factory reset through settings, all data on the persistent partition should be cleared. This adds one last API method that allows settings to wipe the partition. Bug: 14288780 Change-Id: Ib87ee741d1e5195814516ae1d66eb7c4cf754dcf
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|
68d4acd205e8c2da524e62734ca42847306cc029 |
|
02-Jul-2014 |
Andres Morales <anmorales@google.com> |
Service for reading and writing blocks to PST partition Permits apps with permission android.permission.ACCESS_PERSISTENT_PARTITION to obtain a read and write data blocks to the PST partition. Only one block ever exists at one time in PST. When a client writes another block, the previous one is overwritten. This permits storing a block of data that will live across factory resets. Change-Id: I8f23df3531f3c0512118eb4b7530eff8a8e81c83
/frameworks/base/core/java/android/service/persistentdata/PersistentDataBlockManager.java
|