Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 398c61da authored by Naveen Kalla's avatar Naveen Kalla
Browse files

Add precise disconnect cause to CS call metrics 

Precise Disconnect cause gives more visibility to the
exact cause of call failures

Bug: 120729393
Test: Manually made CS calls and checked the dumpsys to ensure the
      precise disconnect cause is populated properly

Change-Id: I9cbc3661986db66f4285544354b6ba8d43aa8707
Merged-In: I9cbc3661986db66f4285544354b6ba8d43aa8707
parent 68a5be13

proto/src/telephony.proto

+4 −0
Original line number Diff line number Diff line
@@ -1945,6 +1945,10 @@ message TelephonyCallSession { 


      // This field is true for Conference Calls

      optional bool is_multiparty = 5;



      // Detailed cause code for CS Call failures

      // frameworks/base/telephony/java/android/telephony/PreciseDisconnectCause.java

      optional int32 precise_disconnect_cause = 6;

    }



    // Single Radio Voice Call Continuity(SRVCC) progress state

src/java/com/android/internal/telephony/metrics/TelephonyMetrics.java

+2 −0
Original line number Diff line number Diff line
@@ -445,6 +445,7 @@ public class TelephonyMetrics { 
                    for (RilCall call : event.calls) {

                        pw.println(call.index + ". Type = " + call.type + " State = "

                                + call.state + " End Reason " + call.callEndReason

                                + " Precise Disconnect Cause " + call.preciseDisconnectCause

                                + " isMultiparty = " + call.isMultiparty);

                    }

                    pw.decreaseIndent();
@@ -1474,6 +1475,7 @@ public class TelephonyMetrics { 
        }

        call.callEndReason = conn.getDisconnectCause();

        call.isMultiparty = conn.isMultiparty();

        call.preciseDisconnectCause = conn.getPreciseDisconnectCause();

    }



    /**