Failure to wake while certain notifications are active

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set an alarm or receive a handcent notification
2. Try to wake during the alarm/event

What is the expected output? What do you see instead?
It seems to very strongly resist proper wakeup code. I am not sure yet the 
cause under the hood. When my alarm goes off I have to open the slide to 
get the screen to wake so I can shut it off. It has not been consistent in 
response time. It might be that a long lag is occurring, as at times the 
wakeup lag seems to get significant and most so with these certain waiting 
notifications. The cause is a window flag that's meant to preserve 
notifications. Without the flag, the alarm quits immediately because of the 
existence of the custom lockscreen.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by myLockan...@gmail.com on 30 Jan 2010 at 6:28

[GoogleCodeExporter]

it appears that what's happening is our activity is still governing the 
brightness at 0 
and the side keys are blocked if the option is set to do nothing in the alarm 
clock. if 
set to snooze or dismiss that still works and our key presses are handled too. 
so when 
power key is pressed all we get is a wake, we aren't getting that key in the 
lockactivity, so we'd need a screen on receiver to try to intercept that case. 
no idea 
for the handcent case.

Original comment by myLockan...@gmail.com on 30 Jan 2010 at 9:54

[GoogleCodeExporter]

Fixed in the new lifecycle logic in the latest a3 revisions. now dealing with a 
corollary to this where it seems the key event gets dropped and it doesn't 
always 
correspond to a notification

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

• Changed state: Fixed