3

I recently updated to the CM 12.1-20151024-NIGHTLY-d851 build (I have an LG G3, D851) and also flashed gapps with the a recent "nano" version. Since then, I have noticed that the lock screen does not work at ALL. Whether I choose PIN or swipe or whatever, it will not lock the phone. (The option for "none" disappeared too, but it became available again after removing an active guest session on the phone.)

I've tried rebooting the phone after choosing different lock screen settings and enabling the PIN again. I also tried updating to 12.1-20151101-NIGHTLY-d851 (thinking maybe it was a nightly bug that got fixed). I also reverted to the earlier working version of gapps, but that did not help. And let's not mention the other "solutions" I stumbled across via Google which did not help either. The phone simply will not lock at all. This is driving me crazy.

The only thing I can think of is that it MIGHT be related to an error I saw while flashing my phone during the upgrade: unable to mount /radio (or something like that).

What can I try next?

EDIT -- UPDATE: The other day my lock screen started working again, without me having to change anything. I suspect that the problem was due to some type of app that has an ability to block the lock screen (for example, I think Google Maps can disable the lock screen temporarily so you're not fiddling with unlocking your phone while driving, as that would be rather dangerous). I'm guessing some app (hopefully not malware!) was blocking the lock screen and got updated in the background, and it started working again. I have no clue how to verify this. At least I did not have to downgrade or flash back to an earlier builld. I am presently running the 12.1-20151104-NIGHTLY-d851 build.

EDIT #2 -- UPDATE #2: I just noticed in my quick settings (i.e. the pull-down from the top of the screen) that there is now an icon to turn lock screen on/off. I guess this is a new addition that I failed to notice, and 99% sure this is what caused the "problem" -- which was really a feature. I must have accidentally tapped it off and then back on before even noticing it was there.

5
  • 1
    I'd flash back the last build you had that was stable.
    – Ethan Z
    Nov 2, 2015 at 20:09
  • @EthanZ I'll give it a shot; I'm just afraid it might make the phone unbootable as I have read from others than downgrading has caused problems as well. Oh well, I've had to deal with this kind of stuff before. Will report back later.
    – fronzee
    Nov 2, 2015 at 20:13
  • Yeah. Its a risk. Your choice if you want to take it or just flash the new nightly tonight.
    – Ethan Z
    Nov 2, 2015 at 20:14
  • @EthanZ See, the thing is: I flashed the Oct 24 nightly and then the Nov 1 nightly. If the problem was with the nightly build and the issue was basic lock screen security, I can't imagine it wouldn't have been fixed in that time. Makes me wonder if the problem is somewhere else.
    – fronzee
    Nov 2, 2015 at 21:11
  • @EthanZ I flashed the new nightly (12.1-20151104-NIGHTLY-d851) and the lock screen is still not working. If nobody else chimes in with any other solutions I guess I will try flashing back to the last build where it was working, but that was a few months ago and I'm not sure what might happen.
    – fronzee
    Nov 4, 2015 at 15:30

1 Answer 1

2

Answering my own question here, so I can mark it as the solution. (I also posted this in the original question as EDIT #2).

I just noticed in my quick settings (i.e. the pull-down from the top of the screen) that there is now an icon to turn lock screen on/off. I guess this is a new addition that I failed to notice, and 99% sure this is what caused the "problem" -- which was really a feature. I must have accidentally tapped it off and then back on before even noticing it was there.

1
  • Thanks for posting. Just got into this a day ago, and like you, this was driving me crazy.
    – Marcel
    Jan 1, 2016 at 20:54

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .