summaryrefslogtreecommitdiffstats
path: root/wifi
diff options
context:
space:
mode:
authorBrian Colonna <bcolonna@google.com>2011-09-26 13:52:25 -0400
committerBrian Colonna <bcolonna@google.com>2011-09-27 12:45:13 -0400
commit267cb2b284626f910cf64352bfc494d0f8d3dc42 (patch)
tree8bde36d869b3485f8bc3a63219e3f0f3403ffa5d /wifi
parent64061c38f064e89822475a152b675dea87bd9eb0 (diff)
downloadframeworks_base-267cb2b284626f910cf64352bfc494d0f8d3dc42.zip
frameworks_base-267cb2b284626f910cf64352bfc494d0f8d3dc42.tar.gz
frameworks_base-267cb2b284626f910cf64352bfc494d0f8d3dc42.tar.bz2
Fix 5323545 - FaceLock no longer appears when taking a call
Prior to this fix if the screen was off and a call was received, the onScreenTurnedOn() callback would bring up the FaceLock service, which would cover the phone interface. It now requires the call state to be CALL_STATE_IDLE to start FaceLock. When the phone interface closes, the user is left at the backup lock screen. Bringing FaceLock up after a call ends does not seem like the correct thing to do. While working near the FaceLock callback code, the sleepDevice() callback was removed because it is no longer used (Fix 5327896). Some cleanup was also done with regards to KeyguardViewManager. FaceLock calls were being made from the KeyguardViewManager in onScreenTurnedOn() and onScreenTurnedOff() via an interface to LockPatternKeyguardView. This level of indirection was removed because it can just be handled inside of the corresponding calls in LockPatternKeyguardView. Likewise the FaceLock functionality inside of hide() in KeyguardViewManager is now in onDetachedFromWindow() in LockPatternKeyguardView. Overall this is much cleaner, especially considering interfacing through KeyguardViewBase was a bit of a hack. Patch Set 2: - Now using KeyguardUpdateMonitor to get phone state - Removed unnecessary wrapper functions for hiding / viewing FaceLock area - These were really only there because at one point I was calling them from KeyguardViewManager and the naming was confusing - Removed if(DEBUG) from a couple of log messages that are actually warnings that shouldn't show up and I want to know if they happen even if I don't have DEBUG set to true Change-Id: Id7befc47dd421156ff6cdb3aaf62fc76fe9cfad2
Diffstat (limited to 'wifi')
0 files changed, 0 insertions, 0 deletions