Confirm managed call when there are ongoing self-managed calls.
When the user places a managed call while there are ongoing self-managed
calls, the system will now display a dialog giving the user the option of
NOT placing the managed call, or placing the managed call and disconnecting
the ongoing self-managed call(s).
This is done by stopping the outgoing call during startOutgoingCall and
bringing up a dialog to confirm whether the user wants to place the call.
If they chose to place the call, ongoing self-mgds calls are disconnected,
the call is added, and the NewutgoingCallBroadcast is sent as usual.
If the user chooses not to start the call, the call is cancelled.
Test: Manual
Bug: 37828805
Change-Id: I8539b0601cf5f324d2fb204485ee0d9bbf03426d
diff --git a/res/values/strings.xml b/res/values/strings.xml
index 2363a1d..58e5284 100644
--- a/res/values/strings.xml
+++ b/res/values/strings.xml
@@ -252,4 +252,8 @@
<string name="notification_channel_incoming_call">Incoming calls</string>
<!-- Notification channel name for a channel containing missed call notifications. -->
<string name="notification_channel_missed_call">Missed calls</string>
+
+ <!-- Alert dialog content used to inform the user that placing a new outgoing call will end the
+ ongoing call in the app "other_app". -->
+ <string name="alert_outgoing_call">Placing this call will end your <xliff:g id="other_app">%1$s</xliff:g> call.</string>
</resources>