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:
@@ -27,8 +27,8 @@ import androidx.preference.PreferenceScreen;
|
||||
import com.android.internal.widget.LockPatternUtils;
|
||||
import com.android.settings.core.PreferenceControllerMixin;
|
||||
import com.android.settings.users.OwnerInfoSettings;
|
||||
import com.android.settingslib.RestrictedLockUtils;
|
||||
import com.android.settingslib.RestrictedLockUtils.EnforcedAdmin;
|
||||
import com.android.settingslib.RestrictedLockUtilsInternal;
|
||||
import com.android.settingslib.RestrictedPreference;
|
||||
import com.android.settingslib.core.AbstractPreferenceController;
|
||||
import com.android.settingslib.core.lifecycle.Lifecycle;
|
||||
@@ -140,6 +140,6 @@ public class OwnerInfoPreferenceController extends AbstractPreferenceController
|
||||
|
||||
@VisibleForTesting
|
||||
EnforcedAdmin getDeviceOwner() {
|
||||
return RestrictedLockUtils.getDeviceOwner(mContext);
|
||||
return RestrictedLockUtilsInternal.getDeviceOwner(mContext);
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user