348f696d33ffc188459e6318c65c8f9058f8d974 - platform/frameworks/base

commit	348f696d33ffc188459e6318c65c8f9058f8d974	[log] [tgz]
author	Victor Chang <vichang@google.com>	Mon Jan 30 16:19:13 2017 +0000
committer	Victor Chang <vichang@google.com>	Thu Feb 16 20:41:50 2017 +0000
tree	624157c8b8087effe93702f21713b47957c06e7b
parent	e622690efa9d2bc3e2b05def4076613d73db8020 [diff]

Clear DISALLOW_ADD_USER in clearDeviceOwner for all cases

We are not moving the restriction from system to the DO in the end.
clearDeviceOwnerUserRestrictionLocked becomes the permanent solution
for DeviceOwner CTS. Looks like no one setting DISALLOW_ADD_USER
directly in UserManager except DO/PO, and so remove it when DO is
clear

Change-Id: I235bebebd02b5e0d9883eea6dd3a4e49b40fe043
Fix: 33476323
Test: runtest frameworks-services -c com.android.server.devicepolicy.DevicePolicyManagerTest

services/devicepolicy/java/com/android/server/devicepolicy/DevicePolicyManagerService.java[diff]
services/tests/servicestests/src/com/android/server/devicepolicy/DevicePolicyManagerTest.java[diff]

2 files changed

tree: 624157c8b8087effe93702f21713b47957c06e7b