Blue Square Screen Android Blue Square Screen Cyanogenmod
[Q] Lockscreen problem in Cyanogenmod 10.2 (Samsung galaxy s3 GT-i9300)
- Thread starter Nimschau
- Start date
- #1
I have recently upgraded from Cyanogenmod 10.1 to the latest Cyanogenmod 10.2-20130923 Nightly version and I am facing a problem with the lockscreen.
The lock screen has disappeared and the phone just won't lock. This problem has only happened after updating to the Android 4.3 via Cyanogenmod ROM. I have put the security option as well and tried every possible combination but it just won't show up. Even after setting up the PIN security the phone is still unlocked and it just opens in the homescreen after pressing power or home button.
Please give me a solution to this problem. All the other things seems to work fine.Has any one else faced the same problem?
Thanks,
Nimish
- #2
- #3
There's a lock screen activation button on the quick settings (tiles that come down swiping down on the right side of the screen). It needs to be activated for lock screen to be active.
On logcat, this will only show as:
09-27 14:54:51.290 I/WindowManager( 716): No lock screen!
Either turn that button on, or add that button from settings and turn it on.
- #4
See this:There's a lock screen activation button on the quick settings (tiles that come down swiping down on the right side of the screen). It needs to be activated for lock screen to be active.
On logcat, this will only show as:
09-27 14:54:51.290 I/WindowManager( 716): No lock screen!
Either turn that button on, or add that button from settings and turn it on.
This still didn't fix the problem for me. Anyone else have any ideas? I tried changing the lock types but that had no effect either.
- #5
This still didn't fix the problem for me. Anyone else have any ideas? I tried changing the lock types but that had no effect either.
I was having the same problem, rebooted and it is now locking.
EDIT: Will work for a little while after rebooting and then goes back to not working.
- #6
I also have the same issue where lock screen just stops engaging. It will work fine after a reboot but after a few hours it just stops locking.
- #7
- #8
Using CM 10.2 nightly 20131020.
Lock screen fails to appear on power button after working fine all day.
Reboot fixed it last time, but two reboots later tonight and it is still not appearing.
- "Power button instantly locks" option is ticked,
- pattern lock selected,
- auto lock after sleep set to immediate.
- PowerAmp lock screen is enabled but skips pattern lock on unlock request,
though sometimes it doesn't go into locked mode at all.
I've tried with PowerAmp lock screen completely disabled and also with the Android lock screen option ticked. No joy.
Similarly, I've tried adding the Lock Screen item to the Settings tiles and had no luck with that either.
Hope this is getting fixed soon... ---------- Post added at 09:42 PM ---------- Previous post was at 08:44 PM ----------
Had the same problem from first boot into that build.
I had Tasker running with a profile that is keyed to my house's WiFi SSID. I disabled Tasker but saw the same problem.
On a hunch, I disabled WiFi and a few seconds later I heard the little 'snict' noise of the lock working, followed by the lock screen kicking in. I've re-enabled WiFi and the screen is locking fine now.
Maybe some interaction with a Tasker profile with a WiFi context and keeps device open even if Tasker is disabled as it can still see the same WiFi SSID ?
Digging a little deeper, I was experimenting with Tasker and its only action is to produce an Alert saying "Home" if it sees my WiFi. Critically, the Action has "Show Over Keyguard" ticked. I've just gone through the process of unticking that option, saving the Action, exiting Tasker, dropping and re-enabling WiFi, (so now Lock screen works), and then rebooting (which causes the Tasker Action to create an alert), and the lock screen is working fine now.
So, kind of looks like going anywhere near that option in Tasker will balls up how the lock screen works, and will stick around even after Tasker has exited unless the criteria it is keyed on changes (i.e. the WiFi state).
Hope that helps someone!
Using CM 10.2 nightly 20131020.Lock screen fails to appear on power button after working fine all day.
Reboot fixed it last time, but two reboots later tonight and it is still not appearing.
- "Power button instantly locks" option is ticked,
- pattern lock selected,
- auto lock after sleep set to immediate.
- PowerAmp lock screen is enabled but skips pattern lock on unlock request,
though sometimes it doesn't go into locked mode at all.
I've tried with PowerAmp lock screen completely disabled and also with the Android lock screen option ticked. No joy.
Similarly, I've tried adding the Lock Screen item to the Settings tiles and had no luck with that either.Hope this is getting fixed soon...
- #9
Thank-you - this helped me today!
Couldn't for the life of me figure out why the lockscreen would stop working. I had an exit task on a Tasker profile with an Action where the "Show Over Keyguard" was on. Turning that to off solved the problem.
Using CM 10.2 nightly 20131020.Lock screen fails to appear on power button after working fine all day.
Reboot fixed it last time, but two reboots later tonight and it is still not appearing.
- "Power button instantly locks" option is ticked,
- pattern lock selected,
- auto lock after sleep set to immediate.
- PowerAmp lock screen is enabled but skips pattern lock on unlock request,
though sometimes it doesn't go into locked mode at all.
I've tried with PowerAmp lock screen completely disabled and also with the Android lock screen option ticked. No joy.
Similarly, I've tried adding the Lock Screen item to the Settings tiles and had no luck with that either.Hope this is getting fixed soon...
---------- Post added at 09:42 PM ---------- Previous post was at 08:44 PM ----------
Interesting. I just upgraded to CM 10.2 nightly 20131024.Had the same problem from first boot into that build.
I had Tasker running with a profile that is keyed to my house's WiFi SSID. I disabled Tasker but saw the same problem.
On a hunch, I disabled WiFi and a few seconds later I heard the little 'snict' noise of the lock working, followed by the lock screen kicking in. I've re-enabled WiFi and the screen is locking fine now.
Maybe some interaction with a Tasker profile with a WiFi context and keeps device open even if Tasker is disabled as it can still see the same WiFi SSID ?
Digging a little deeper, I was experimenting with Tasker and its only action is to produce an Alert saying "Home" if it sees my WiFi. Critically, the Action has "Show Over Keyguard" ticked. I've just gone through the process of unticking that option, saving the Action, exiting Tasker, dropping and re-enabling WiFi, (so now Lock screen works), and then rebooting (which causes the Tasker Action to create an alert), and the lock screen is working fine now.
So, kind of looks like going anywhere near that option in Tasker will balls up how the lock screen works, and will stick around even after Tasker has exited unless the criteria it is keyed on changes (i.e. the WiFi state).
Hope that helps someone!
- #10
- #11
See this:There's a lock screen activation button on the quick settings (tiles that come down swiping down on the right side of the screen). It needs to be activated for lock screen to be active.
On logcat, this will only show as:
09-27 14:54:51.290 I/WindowManager( 716): No lock screen!
Either turn that button on, or add that button from settings and turn it on.
Thx, that was it for me. CM10.2 Nigthly (15.11.) Galaxy Mini i9195:good:
- #12
Thx, that was it for me. CM10.2 Nigthly (15.11.) Galaxy Mini i9195:good:
Same problem for me. No tasker app installed. Using cm-10.2-20131127-nightly.
No way to lock the phone
- #13
See this:There's a lock screen activation button on the quick settings (tiles that come down swiping down on the right side of the screen). It needs to be activated for lock screen to be active.
On logcat, this will only show as:
09-27 14:54:51.290 I/WindowManager( 716): No lock screen!
Either turn that button on, or add that button from settings and turn it on.
Woow It Worked!
- #14
Not for me
Inviato dal mio GT-I9300 utilizzando Tapatalk
- #15
same problem with my phone.. running nightly from today... my lockscreen is awaaaay 
(((
- #16
Inviato dal mio GT-I9300 utilizzando Tapatalk
- #17
Running CM 10.2 on Galaxy S3 i535 (VZ). Disabled Tasker and phone locks as expected.
- #18
I have the same problem on the final version, installed over the holiday. Any word on fixes yet? I have not tried searching too deeply however this thread was very specific to my problem and thought it was most appropriate here.
10.2.0-d2spr here with no tasker installed.
Thanks!
- #19
I have the same problem on the final version, installed over the holiday. Any word on fixes yet? I have not tried searching too deeply however this thread was very specific to my problem and thought it was most appropriate here.10.2.0-d2spr here with no tasker installed.
Thanks!
I'm having the same problem, on the final version as well. I flashed about 3 hours ago
Similar threads
Source: https://forum.xda-developers.com/t/q-lockscreen-problem-in-cyanogenmod-10-2-samsung-galaxy-s3-gt-i9300.2456650/
0 Response to "Blue Square Screen Android Blue Square Screen Cyanogenmod"
Post a Comment