Hello,
As of yesterday, my OnePlus One seems to be unlocking itself at bootup. It makes the "knack-knock" un-lock sound (high->low) just after the bootlogo screen, and fails to show the lock screen when it is first turned on.
After it has booted, it goes straight to the home screen, and I can use the phone as if it weren't locked: It is now in some kind of bugged state where the screen lock doesn't work - the screen will stay on until it runs out of batteries, and if I press the power button then the screen turns off but doesn't lock.
The first time I press the HOME button however, then the phone immediately LOCKS (albeit without playing a sound) and displays the usual PIN-entry screen. I can then enter my 8-digit PIN as normal and it will unlock ("knack-knock") . It is now out of the bugged state and will lock properly ("knock-knock") after it has been asleep for however many seconds I have configured it to lock. It is now perfectly normal until next time it reboots.
If I DON'T enter a PIN on that first lock-screen then it stays in the bugged state: After a few seconds of displaying the lock screen, the screen turns off, it plays the unlock "knack-knock" again, and when I press the power button we are back to the same state as first boot - my home screen is available, I can read my emails etc, but I have never entered a passcode!
I haven't installed any new apps recently, and I have auto-update apps turned off. I can't seem to stop Google Play from updating, though.
There is an update available: "XNPH05Q Incremental" - I tried taking a backup and installing this, but the screen-unlock problem remained.
Turning off "Use custom lock screen" didn't help either..
The phone IS rooted, but I don't have anything particularly suspicious installed.. A full list of packages on my phone is here:
So my question is: a) Has anyone here seen this before? (google has so far been of no help)
b) Which of the apps/modules I have installed could be causing this? (which should I try uninstalling first?)
or c) how can I find out who/what is causing this? (Is there any way to track calls to com.android.internal.policy.impl.LockScreen, for example?)
Cheers
As of yesterday, my OnePlus One seems to be unlocking itself at bootup. It makes the "knack-knock" un-lock sound (high->low) just after the bootlogo screen, and fails to show the lock screen when it is first turned on.
After it has booted, it goes straight to the home screen, and I can use the phone as if it weren't locked: It is now in some kind of bugged state where the screen lock doesn't work - the screen will stay on until it runs out of batteries, and if I press the power button then the screen turns off but doesn't lock.
The first time I press the HOME button however, then the phone immediately LOCKS (albeit without playing a sound) and displays the usual PIN-entry screen. I can then enter my 8-digit PIN as normal and it will unlock ("knack-knock") . It is now out of the bugged state and will lock properly ("knock-knock") after it has been asleep for however many seconds I have configured it to lock. It is now perfectly normal until next time it reboots.
If I DON'T enter a PIN on that first lock-screen then it stays in the bugged state: After a few seconds of displaying the lock screen, the screen turns off, it plays the unlock "knack-knock" again, and when I press the power button we are back to the same state as first boot - my home screen is available, I can read my emails etc, but I have never entered a passcode!
I haven't installed any new apps recently, and I have auto-update apps turned off. I can't seem to stop Google Play from updating, though.
There is an update available: "XNPH05Q Incremental" - I tried taking a backup and installing this, but the screen-unlock problem remained.
Turning off "Use custom lock screen" didn't help either..
The phone IS rooted, but I don't have anything particularly suspicious installed.. A full list of packages on my phone is here:
So my question is: a) Has anyone here seen this before? (google has so far been of no help)
b) Which of the apps/modules I have installed could be causing this? (which should I try uninstalling first?)
or c) how can I find out who/what is causing this? (Is there any way to track calls to com.android.internal.policy.impl.LockScreen, for example?)
Cheers
Our lab has found and imported it.
RépondreSupprimerAlso visit my webpage :: best deer antler spray bodybuilding (Bernice)