Placing a call or having a call end while screen is asleep results in one time lockscreen while using custom lockscreen mode

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Make a call then end it, or receive a call and have other party end it 
while screen is asleep
2. Wake up the screen
3. This next wakeup results in the default lockscreen instead of the custom 
lockscreen

What is the expected output? What do you see instead?
The suspected cause of this error is a problem with not receiving the 
screen off broadcast because screen off is happening during the call when 
we have paused the broadcast receivers. For the placed call, it seems the 
fact that device is unlocked is not being properly detected so the failure 
to place the custom lockscreen occurs because the screen off logic believes 
that the custom lockscreen already exists.

Alpha 3 pre-release test build exhibits this issue with implementation of 
the key-customizable customLockscreen.

Original issue reported on code.google.com by myLockan...@gmail.com on 17 Jan 2010 at 5:55

[GoogleCodeExporter]

coded the services as subclass of new mediator class which passes reaction 
functions 
for phone call start and stop events along with screen wake or sleep. this 
totality of 
reaction allowed us to eliminate the bug by reacting with new lockscreen to the 
combination of circumstances that caused this case

Original comment by myLockan...@gmail.com on 23 Jan 2010 at 11:45

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****