From d88c3fbaffc0330fd2bb6ce48047680d9540229b Mon Sep 17 00:00:00 2001 From: Santos Cordon Date: Tue, 8 Oct 2013 17:00:19 -0700 Subject: update dialpad state more often. Noticed while testing proximity sensor that we do not update the dialpad state sufficiently. We have increased the amount of places in the code where the dialpad comes up since we first introduced the proximity code and the callbacks wheren't updated. This manifested in situations where the proximity sensor was off at time when it should have been on. Repro: be in a call, answer a second call (call waiting), bring up dialpad, hangup second call. The dialpad would go away but the prox sensor still thought it was up. This change moves the callback to proximity sensor to the exact place where dialpad is shown/hidden in order to catch all instances. bug:11006867 Change-Id: I7651b4769d035b9bc68d226da3ffb3aea8986e58 --- InCallUI/src/com/android/incallui/InCallActivity.java | 2 ++ 1 file changed, 2 insertions(+) (limited to 'InCallUI/src/com/android/incallui/InCallActivity.java') diff --git a/InCallUI/src/com/android/incallui/InCallActivity.java b/InCallUI/src/com/android/incallui/InCallActivity.java index ac21d52a2..58db132a6 100644 --- a/InCallUI/src/com/android/incallui/InCallActivity.java +++ b/InCallUI/src/com/android/incallui/InCallActivity.java @@ -389,6 +389,8 @@ public class InCallActivity extends Activity { mDialpadFragment.setVisible(false); mCallCardFragment.setVisible(true); } + + InCallPresenter.getInstance().getProximitySensor().onDialpadVisible(showDialpad); } public boolean isDialpadVisible() { -- cgit v1.2.3