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

Commit 9e63b17f authored by Tyler Gunn's avatar Tyler Gunn
Browse files

Update cant_call_due_to_no_supported_service wording. 

This string was used in the past when SIP calling was not available due
to it being disabled.  However, this situation now more commonly happens
when a watch relies on bluetooth to place calls; if bluetooth is turned
off the same generic message will arise.  Given this is the more common
case, changing wording.

Flag: NONE string resources are not flaggable.
Test: Manual test.
Fixes: 341979014
Change-Id: Ic46c78d83d254b448263332a3b64282948765fd3
parent 28786e78

res/values/strings.xml

+5 −3
Original line number Diff line number Diff line
@@ -290,9 +290,11 @@ 


    <!-- Error message shown to the user when an outgoing call cannot be placed because there no

         calling service is present on the device which supports this call type.

         This is typically encountered when the user tries to dial a SIP/VOIP call, but there are

         no calling services present which support SIP calling. [CHAR LIMIT=none] -->

    <string name="cant_call_due_to_no_supported_service">Call cannot be placed because there are no calling accounts which support calls of this type.</string>

         This can happen on a device such as a watch or tablet which provides calling using a

         service that may not be available all the time.  For example, a watch may rely on Bluetooth

         to be enabled for calling to work; when Bluetooth is disabled calling would not work.

         [CHAR LIMIT=none] -->

    <string name="cant_call_due_to_no_supported_service">Can\'t make call. Check your device\'s connection.</string>



    <!-- Error message shown to the user when an outgoing call cannot be placed due to an ongoing

         phone call in a third-party app.  For example: