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

Commit 25251261 authored by Thomas Stuart's avatar Thomas Stuart
Browse files

update the WATCHDOG_DISCONNECTED_STUCK_VOIP_CALL_MSG message 

WATCHDOG_DISCONNECTED_STUCK_VOIP_CALL_MSG was vague and could mislead users into thinking there is a problem with the VoIP call.  Rather, it is to report apps that are not integrating with telecom correctly.

Bug: 370159602 (update anom msg bug)
Bug: 360298368 (original bug)
Flag: com.android.server.telecom.flags.disconnect_self_managed_stuck_startup_calls
Test: presubmits
Change-Id: I601ec06186cf42489761a24f3abec8aefd68f92b
parent 3d5a63c5

src/com/android/server/telecom/CallAnomalyWatchdog.java

+2 −1
Original line number Diff line number Diff line
@@ -153,7 +153,8 @@ public class CallAnomalyWatchdog extends CallsManagerListenerBase implements Cal 
    public static final UUID WATCHDOG_DISCONNECTED_STUCK_VOIP_CALL_UUID =

            UUID.fromString("3fbecd12-059d-4fd3-87b7-6c3079891c23");

    public static final String WATCHDOG_DISCONNECTED_STUCK_VOIP_CALL_MSG =

            "Telecom CallAnomalyWatchdog caught stuck VoIP call in a starting state";

            "A VoIP call was flagged due to exceeding a one-minute threshold in the DIALING or "

                    + "RINGING state";





    @VisibleForTesting