Lockscreen restores after calls in certain cases

[GoogleCodeExporter]

Known scenarios:
  * Speakerphone/Bluetooth is active, screen was allowed to go to sleep and 
remain asleep for 5 or more seconds, causing system to initialize the 
lockscreen again. 
  * Any call ends by the other party while screen is asleep (not always, 
still trying to determine if it has anything to do with whether a lockscreen 
was in place when the call came in)

Original issue reported on code.google.com by myLockan...@gmail.com on 16 Feb 2010 at 5:22

[GoogleCodeExporter]

this looks like it is completely fixed by air-tight call event logic I finished 
in the 
latest a3 revision. The only case left to be tweaked at all would be the 
miss/ignore 
scenario. what we are doing with that currently is just letting the phone app 
peel 
itself back leaving the lockscreen, but without any wake flag. meaning you 
can't back 
key out of it. should be able to fix this as we implement the rest of the 
customizations 

Original comment by myLockan...@gmail.com on 25 Feb 2010 at 9:35

• Changed state: Fixed