Fixing where call goes from disconnecting to active to disconnecting state.

- Adding disconnecting state to telecom used to communicate that a call is
being disconnected to InCall UI (rather than it existing only as a state
in the InCall UI).

Bug: 17821930
Change-Id: I6c2d9521915ba154c0468eea62c12c30060edd2e

1 files changed, 12 insertions, 0 deletions

diff --git a/telecomm/java/android/telecom/CallState.java b/telecomm/java/android/telecom/CallState.java
index 7690847..bd9223a 100644
--- a/telecomm/java/android/telecom/CallState.java
+++ b/telecomm/java/android/telecom/CallState.java
@@ -100,6 +100,16 @@ public final class CallState {
      */
     public static final int ABORTED = 8;
 
+    /**
+     * Indicates that the call is in the process of being disconnected and will transition next
+     * to a {@link #DISCONNECTED} state.
+     * <p>
+     * This state is not expected to be communicated from the Telephony layer, but will be reported
+     * to the InCall UI for calls where disconnection has been initiated by the user but the
+     * ConnectionService has confirmed the call as disconnected.
+     */
+    public static final int DISCONNECTING = 9;
+
     public static String toString(int callState) {
         switch (callState) {
             case NEW:
@@ -120,6 +130,8 @@ public final class CallState {
                 return "DISCONNECTED";
             case ABORTED:
                 return "ABORTED";
+            case DISCONNECTING:
+                return "DISCONNECTING";
             default:
                 return "UNKNOWN";
         }