由于修改系统锁屏界面,风格,导致SystemUI和Keyguard改动比较大。结果发现重启后,无法锁屏、
还原所有改动,无果。遂只能跟踪锁屏源码逻辑,结果发现:doKeyguard: not showing because device isn't provisioned and the sim is not locked or missing
找到log位置:
private void doKeyguardLocked(Bundle options) {
………………
if (!lockedOrMissing && !provisioned && !antiTheftLocked) {
if (DEBUG) {
Log.d(TAG, "doKeyguard: not showing because device isn't provisioned"
+ " and the sim is not locked or missing");
}
return;
}
………………
}
继续跟踪lockedOrMissing,provisioned,antiTheftLocked变量值
找到final boolean provisioned = mUpdateMonitor.isDeviceProvisioned();
provisioned == false,正是这个值导致doKeyguardLocked提前return
那么isDeviceProvisioned作用是什么呢,我们跟踪isDeviceProvisioned()函数,如下:
public boolean isDeviceProvisioned() {
if (mDeviceProvisioned == false) {
Log.d(TAG, "isDeviceProvisioned get DEVICE_PROVISIONED from db again !!");
return (0 != Settings.Global.getInt(
mContext.getContentResolver(), Settings.Global.DEVICE_PROVISIONED, 0));
} else {
Log.d(TAG, "mDeviceProvisioned == true");
return mDeviceProvisioned;
}
}
发现其实读取的是SettingProvider的 Settings.Global.DEVICE_PROVISIONED;
继续跟踪的 Settings.Global.DEVICE_PROVISIONED的值,发现在provision的 DefaultActivity中,Settings.Global.DEVICE_PROVISIONED被写入1.
到这里问题已经很明了了;也有正常情况下第一次开机provision(开机引导)完成后,会把Settings.Global.DEVICE_PROVISIONED置为1
而我们把开机引导过程给去掉了,导致Settings.Global.DEVICE_PROVISIONED一直为0,以至无法锁屏;
Settings.Global.DEVICE_PROVISIONED这个值在系统中引用的地方不少,如其他应用有类似问题,原因也可能如此。
好了,问题解决了。如有不对之处,还望指出,谢谢。