Make the generic "can't call" error message more specific.
Added support for a bunch of different call fail cases reported via the
CallStateException.
Should make it more informative than the usual "can't call" message.
Test: Added unit tests for throw conditions.
Test: Manually tested scenarios.
Bug: 116453747
Bug: 73902028
Change-Id: Ia3b3d8ecb204d632d2b3e97498d2c1ddf4c2b399
diff --git a/res/values/strings.xml b/res/values/strings.xml
index e909e62..0233555 100644
--- a/res/values/strings.xml
+++ b/res/values/strings.xml
@@ -1792,4 +1792,17 @@
<!-- Message displayed to the user to indicate that a held call has been released /
disconnected. -->
<string name="supp_service_held_call_released">Held call has been released.</string>
+
+ <!-- In-call screen: error message shown when the user has attempted to place a new outgoing
+ call, but there is already a call in dialing state. -->
+ <string name="callFailed_already_dialing">Cannot place a call as another outgoing call is already dialing.</string>
+ <!-- In-call screen: error message shown when the user has attempted to place a new outgoing
+ call while there is already a call in ringing state. -->
+ <string name="callFailed_already_ringing">Cannot place a call as there is an unanswered incoming call. Answer or reject the incoming call prior to placing a new call.</string>
+ <!-- In-call screen: error message shown when the user attempts to place a call, but calling has
+ been disabled using a debug property. -->
+ <string name="callFailed_calling_disabled">Cannot place a call as calling has been disabled using the ro.telephony.disable-call system property.</string>
+ <!-- In-call screen: error message shown when the user attempts to place a call, but calling has
+ been disabled using a debug property. -->
+ <string name="callFailed_too_many_calls">Cannot place a call a there are already two calls in progress. Disconnect one of the calls or merge them into a conference prior to placing a new call.</string>
</resources>
