Un/lock screen issue

[GoogleCodeExporter]

What steps will reproduce the problem?

1.Lock device
2.Unlock device
3.

What is the expected output? What do you see instead?

expected output: device unlocking and screen lighting up
see instead: nothing! Only a black screen. (every button in urensponsible). 
Sometimes device auto-reboots.

What version of MiniCM you are using? On what device (X10mini, X10minipro,
X8)? 

X10mini with MiniCM10-4.0.0

Are you using Compcache/Zram?

No. No.

Are you overclocking/undervolting?

No.

What app(s) are involved in the problem?

I have no idea.

Have you tried rebooting your device?

Yes. Rebooting doesn't fix it. Neither unchecking Auto Brightness / Ultra 
Brightness

Original issue reported on code.google.com by Kokopip...@gmail.com on 6 Sep 2012 at 12:12

[GoogleCodeExporter]

Happens to me too on MiniCM10-4.0.1 on an X10 Mini, so it looks like 
MiniCM10-4.0.1 is also affected

Original comment by jan.migu...@googlemail.com on 28 Sep 2012 at 12:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Just upgraded my Xperia X8, happens to me also on a brand new 
MiniCM10-4.0.1-shakira

Original comment by surmoo...@gmail.com on 5 Nov 2012 at 4:47

[GoogleCodeExporter]

Anyone found a workaround to avoid this behavior?

Original comment by mrtn.fre...@gmail.com on 8 Nov 2012 at 5:41

[GoogleCodeExporter]

well, disabling the lock-screen fixed it for me

Original comment by jan.migu...@googlemail.com on 8 Nov 2012 at 5:49

[GoogleCodeExporter]

disabling lockscreen did worked for me too, but it's not that convenient when 
in a pocket. :(

Original comment by Kokopip...@gmail.com on 8 Nov 2012 at 9:39

[GoogleCodeExporter]

I've disabled the Weather Widget in the lock screen by 

System Settings > Lockscreen > Weather > Display Weather > (Clear this checkbox 
and disable this completely)

and now phone seems to be working properly. Too early to say if that fixed the 
trouble 100%, but definitely much, much better responses now, and phone behaves 
normally as far as I can tell (around 1-2 hr use since change and no issues so 
far).

This keeps the lock screen (=avoids troubles when phone in pocket) and at the 
same time seems to be responding fine when unlocking, so far.

Hope it helps.

Original comment by surmoo...@gmail.com on 9 Nov 2012 at 10:08

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

In my Xperia X10 Mini, I have turned off the weather information on the lock 
screen. But still the problem arise. (Using MiniCM10-4.0.1-robyn)

Original comment by yehan...@gmail.com on 10 Dec 2012 at 2:38

[GoogleCodeExporter]

I have the same issue (x10 mini pro + MiniCM10-4.0.1) and I realised that when 
you press a first time the back arrow, the screen says black but if you wait 
about 20 seconds without touching your mobile and then press the back arrow 
again, the screen finally wakes up and you can use your phone as normal.  Every 
time you press the arrow while the screen is black resets the 20 seconds timer.

It seems that something else (maybe a process or something) is 'sleeping' and 
needs to be woken up or something before accessing the phone again.  But it 
isn't always sleeping as sometimes I can unlock the phone right away.

And no, the weather fix above doesn't change anything.

I hope this helps a bit fixing the issue.

Original comment by laurent....@gmail.com on 12 Dec 2012 at 2:48

[GoogleCodeExporter]

I agree with @laurent. In my Xperia X10 mini, I think the phone is waking up 
correctly but the screen doesn't come up. I say so because after unlocking the 
phone, though the screen doesn't come up, if I touch the unlocking area I can 
feel the vibration as expected. And if I drag my finger to the normal unlocking 
position, it vibrates again.

Normally we can think that the phone is unlocked now. I'm sure it is unlocked 
because after doing what I said above I cannot feel the vibrate I feel when I'm 
touching the unlock screen. That means I'm simply touching my desktop (or 
wherever I was before the screen locked).

And another thing, if you want to get rid of this thing, you can wait 20 
seconds as @laurent said. But if you are in a hurry, simply press your lock 
button (it will lock the phone again and/or return to the display off mode). 
Then try unlocking it again, This time your display will come up as normal.

Original comment by yehan...@gmail.com on 13 Dec 2012 at 2:59

[GoogleCodeExporter]

Nice findings there @yehan !!!  

I can confirm the following:

    - lock the phone (or leave it to lock itself after some time)
    - try to turn the screen on with the back arrow (but nothing happens)
    - press the top button to lock the phone again (even tho it 'seems' already locked as the screen is black)
    - click on the back arrow again -> the screen lights up

Original comment by laurent....@gmail.com on 13 Dec 2012 at 8:07

[GoogleCodeExporter]

Got the same issue with my Xperia X10 Mini Pro (MiniCM10-4.0.1-mimmi and 
nAa-jb-02).

Is there any hope for a fix soon?

Original comment by Hinz.Mi...@googlemail.com on 3 Jan 2013 at 5:03

[GoogleCodeExporter]

@Yehan yep, that worked for me, hope there is a hotfix soon...

Original comment by werard...@gmail.com on 19 Jan 2013 at 11:52

[GoogleCodeExporter]

Also have this issue with my X10 mini pro. Only seems to affect the default 
'slide to unlock' screen. If i set an unlock pattern I don't have the problem.

Original comment by bob.mcle...@gmail.com on 21 Mar 2013 at 2:29

[GoogleCodeExporter]

Here is what worked for me:

1.) Disable the lock screen.
2.) Press the power button on the x10 mini to lock/unlock. It works without any 
delay. Sometimes I have to press the back and power button to unlock.

No issues thereafter. It has been working fine ever since.

Original comment by krishist...@gmail.com on 16 Aug 2013 at 11:59

[GoogleCodeExporter]

@Bob: Awesome, it didn't occure to me this might be just this particular 
lockscreen type's issue. I can confirm here that the other lockscreen types 
(gesture, pin, ...) seem to be perfectly responsive so far.

Original comment by vladimir...@gmail.com on 17 Oct 2013 at 8:38