Lock functionality fails to start when certain apps are active (alpha 3 test version)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to lock the phone while browser, dolphin browser, or facebook are on 
screen
2. Try to unlock

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

The lock override is not creating correctly at sleep. Instead the OS is 
putting it off, such that it happens at screen on. So in custom lock mode, 
you see the lockscreen for a moment then the normal first-start screen 
force off happens, making you think it failed to wakeup. In the regular 
mode, you end up just seeing the dummy unLockScreen, that you normally 
don't see since it is created while screen is off. To proceed you have to 
sleep then wake again. This is the last remaining significant quirk on the 
alpha 3 test builds.

Original issue reported on code.google.com by myLockan...@gmail.com on 27 Jan 2010 at 8:51

[GoogleCodeExporter]

Need to test, the currently available 0127 build appears to resolve all cases 
of this 
except the case of user pressing power to send it to sleep, but then pressing 
power 
again to re-wake immediately. the quick succession confuses the power manager. 
in the 
logs we are seeing "set screen state 0" and a line about ignoring user action 
while 
going to sleep. it appears it is ignoring the 2nd press even though myLock 
still tries 
to process the wakeup, the OS overrides it. sometimes the soft-keys remain lit 
at that 
point.

Original comment by myLockan...@gmail.com on 28 Jan 2010 at 7:47

[GoogleCodeExporter]

cpu wake lock has resolved this, i had to determine the right times to open and 
close 
it so that we could fully start, then release it once we had gained focus on 
the 
lockscreen window.

Original comment by myLockan...@gmail.com on 4 Feb 2010 at 7:40

• Changed state: Fixed