RestrictedLockUtils was split into ...Internal
This means that in some cases RestrictedLockUtils has to be used and in some RestrictedLockUtilsInternal. This causes a lot of trivial code changes. I also updated the ordering of the imports in all affected files. Bug: 110953302 Test: Built make -j RunSettingsRoboTests Change-Id: I9bdf8b89134f853bae4f38c81af436715c73e924
This commit is contained in:
@@ -67,6 +67,7 @@ import com.android.settings.overlay.FeatureFactory;
|
||||
import com.android.settings.users.UserDialogs;
|
||||
import com.android.settingslib.RestrictedLockUtils;
|
||||
import com.android.settingslib.RestrictedLockUtils.EnforcedAdmin;
|
||||
import com.android.settingslib.RestrictedLockUtilsInternal;
|
||||
|
||||
import org.xmlpull.v1.XmlPullParserException;
|
||||
|
||||
@@ -645,12 +646,12 @@ public class DeviceAdminAdd extends Activity {
|
||||
private EnforcedAdmin getAdminEnforcingCantRemoveProfile() {
|
||||
// Removing a managed profile is disallowed if DISALLOW_REMOVE_MANAGED_PROFILE
|
||||
// is set in the parent rather than the user itself.
|
||||
return RestrictedLockUtils.checkIfRestrictionEnforced(this,
|
||||
return RestrictedLockUtilsInternal.checkIfRestrictionEnforced(this,
|
||||
UserManager.DISALLOW_REMOVE_MANAGED_PROFILE, getParentUserId());
|
||||
}
|
||||
|
||||
private boolean hasBaseCantRemoveProfileRestriction() {
|
||||
return RestrictedLockUtils.hasBaseUserRestriction(this,
|
||||
return RestrictedLockUtilsInternal.hasBaseUserRestriction(this,
|
||||
UserManager.DISALLOW_REMOVE_MANAGED_PROFILE, getParentUserId());
|
||||
}
|
||||
|
||||
|
Reference in New Issue
Block a user