1. f8373b5 DPM Test: DA and PO cannot call DPM.reboot() by Mahaver Chopra · 9 years ago
  2. bf60f72 Device or profile owner can let another app manage app restrictions by Esteban Talavera · 9 years ago
  3. 3ab6f2e DA receiver should be protected with BIND_DEVICE_ADMIN. by Makoto Onuki · 9 years ago
  4. a31ebbc Add DO API to get wifi mac address by Makoto Onuki · 9 years ago
  5. c8a5a55 DPM.isDeviceOwnerApp() and getDeviceOwner() now check calling user by Makoto Onuki · 9 years ago
  6. 1a2cd74 More work on layered user restrictions. by Makoto Onuki · 9 years ago
  7. 219bbaf Revert "Do not call into ActivityManager from DPMS within DPMS lock" by Makoto Onuki · 9 years ago
  8. 53de36f Do not call into ActivityManager from DPMS within DPMS lock by Makoto Onuki · 9 years ago
  9. 6d2beef Merge "Add DPM.getUserRestrictions()" by Makoto Onuki · 9 years ago
  10. 3a3092f Add DPM.getUserRestrictions() by Makoto Onuki · 9 years ago
  11. 803d675 Do not allow DO and PO running on the same user. by Makoto Onuki · 9 years ago
  12. 068c54a Layer user restrictions by Makoto Onuki · 9 years ago
  13. a52562c setDeviceOwner() now requires a full component name. by Makoto Onuki · 9 years ago
  14. a4f1197 First cut of user restriction layering. by Makoto Onuki · 9 years ago
  15. d932f76 Refactor DPMS tests to be able to test more different cases. by Makoto Onuki · 9 years ago
  16. b643fb0 Use a factory class for dependency injection, add more tests. by Makoto Onuki · 9 years ago
  17. f76b06a Test more DPM APIs. by Makoto Onuki · 9 years ago
  18. cc4bbeb Make DPM/DPMS unit-testable by Makoto Onuki · 9 years ago