1158092 - [Dialer] Dial an invalid phone number 111 or 000, and the phone will hang up by itself.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Dialer, defect)

Description

[zouyi(Leave from Mozilla)]

Attachment: logcat_2125.txt

[1.Description]:
[Flame v2.2 & v3.0][Nexus5 v2.2 & v3.0][Dialer] Launch dialer app. Dial an invalid phone number 111 or 000. The device will hang up by itself, then device will display "Unable to make a phone call now" page.
Occur time :21:25
See attachment logcat_2125.txt and 2125.mp4

[2.Testing Steps]: 
1.Launch dialer app.
2.Dial an invalid phone number 111 or 000.

[3.Expected Result]: 
2.It will say this is an invalid phone number.

[4.Actual Result]: 
2.The device will hang up by itself, and display unable to make a phone call now.

[5.Reproduction build]: 
Flame 2.2 version(Affected):
Build ID               20150423002502
Gaia Revision          b838d0e7c163e66660dcb6e387d8339944a7a30e
Gaia Date              2015-04-23 02:32:46
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/8dce56574f28
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150423.035703
Firmware Date          Thu Apr 23 03:57:16 EDT 2015
Bootloader             L1TC000118D0

Flame 3.0 version(Affected):
Build ID               20150423160207
Gaia Revision          0c5e2ee1173f3c53379ef3cd10de714836258fe8
Gaia Date              2015-04-23 16:10:10
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/22a157f7feb7
Gecko Version          40.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150423.193607
Firmware Date          Thu Apr 23 19:36:18 EDT 2015
Bootloader             L1TC000118D0

Nexus5 2.2 version(Affected):
Build ID               20150423002502
Gaia Revision          b838d0e7c163e66660dcb6e387d8339944a7a30e
Gaia Date              2015-04-23 02:32:46
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/8dce56574f28
Gecko Version          37.0
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150423.035409
Firmware Date          Thu Apr 23 03:54:27 EDT 2015
Bootloader             HHZ12f

Nexus5 3.0 version(Affected):
Build ID               20150423160207
Gaia Revision          0c5e2ee1173f3c53379ef3cd10de714836258fe8
Gaia Date              2015-04-23 16:10:10
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/22a157f7feb7
Gecko Version          40.0a1
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150423.192918
Firmware Date          Thu Apr 23 19:29:36 EDT 2015
Bootloader             HHZ12f

[6.Reproduction Frequency]: 
Always Recurrence,10/10

[7.TCID]: 
Free Test

Comment 1

[zouyi(Leave from Mozilla)]

Attachment: 2125.mp4

Comment 2

[Eric Chang [:ericcc] [:echang]]

Hi Zouyi, Could you try again with RIL debug flag turn on? Thank you.

1. Turn on RIL debug flag in Settings.
2. Reboot
3. Get adb logcat

Comment 3

[Johan Lorenzo [:jlorenzo]]

3 digits numbers can be valid in some countries (like 911 in the US). Like Eric suggested, we need a RIL logcat to see if it's a carrier issue or not.

Comment 4

[Lance（leave from Mozilla）]

If you insert CMCC card, call the "111", the device will say that the number is vacant number. But if you insert CU card, device will hang up by itself, and display "Unable to make a phone call now" page.

See attachment:1732.txt
Fail rate:5/5

Device: Flame 3.0 version(Fail):
Build ID               20150426160201
Gaia Revision          b4c949cdc780893897c9b45c1adea46e2eb694ff
Gaia Date              2015-04-24 16:13:40
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/37d60e3b8be6
Gecko Version          40.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150426.193323
Firmware Date          Sun Apr 26 19:33:34 EDT 2015
Bootloader             L1TC000118D0

Comment 5

[Lance（leave from Mozilla）]

Attachment: logcat_1732.txt

Comment 6

[Eric Chang [:ericcc] [:echang]]

Hi HsinYi, Could anyone help us to check the log for issue, thanks.

Comment 7

[Eric Chang [:ericcc] [:echang]]

Hi Lance, Is that also the same case in a Nokia or an Android/iOS? It might be a carrier issue.

Comment 8

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Lance from comment #5)
> Created attachment 8597901 [details]
> logcat_1732.txt

The behaviour could vary with carriers.

Here's quick update on logcat_1732.txt

5 Dial requests were received on gecko which delivered those to modem successfully.
For the 1st, 4th and 5th, right after the success response of Request_dial, an empty call list was received from modem/rild that implied the call was disconnected automatically. From the gecko's viewpoint, it's released by network.

For 2nd and 3rd runs, the log pointed that gecko received 'hangUp' requests. Did you accidentally press hangup button during the test run?

Comment 9

[Lance（leave from Mozilla）]

(In reply to Eric Chang [:ericcc] [:echang] from comment #7)
> Hi Lance, Is that also the same case in a Nokia or an Android/iOS? It might
> be a carrier issue.

We have tried calling the 111 on LG and HTC, and device will hang up by itself, but LG and HTC can't display "Unable to make a phone call now" page after we hang up this call.

Comment 10

[Lance（leave from Mozilla）]

(In reply to Hsin-Yi Tsai [:hsinyi] from comment #8)
> (In reply to Lance from comment #5)
> > Created attachment 8597901 [details]
> > logcat_1732.txt
> 
> The behaviour could vary with carriers.
> 
> Here's quick update on logcat_1732.txt
> 
> 5 Dial requests were received on gecko which delivered those to modem
> successfully.
> For the 1st, 4th and 5th, right after the success response of Request_dial,
> an empty call list was received from modem/rild that implied the call was
> disconnected automatically. From the gecko's viewpoint, it's released by
> network.
> 
> For 2nd and 3rd runs, the log pointed that gecko received 'hangUp' requests.
> Did you accidentally press hangup button during the test run?

Hi Tsai,

For the 2nd and 3rd time, call  "000". Then device will say that the number is vacant number, so we tap hang up to end call. 
For the 1st, 4th and 5th time, call "111", it will hang up by itself, then display "Unable to make a phone call now" page.

Comment 11

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Lance from comment #10)
> (In reply to Hsin-Yi Tsai [:hsinyi] from comment #8)
> > (In reply to Lance from comment #5)
> > > Created attachment 8597901 [details]
> > > logcat_1732.txt
> > 
> > The behaviour could vary with carriers.
> > 
> > Here's quick update on logcat_1732.txt
> > 
> > 5 Dial requests were received on gecko which delivered those to modem
> > successfully.
> > For the 1st, 4th and 5th, right after the success response of Request_dial,
> > an empty call list was received from modem/rild that implied the call was
> > disconnected automatically. From the gecko's viewpoint, it's released by
> > network.
> > 
> > For 2nd and 3rd runs, the log pointed that gecko received 'hangUp' requests.
> > Did you accidentally press hangup button during the test run?
> 
> Hi Tsai,
> 
> For the 2nd and 3rd time, call  "000". Then device will say that the number
> is vacant number, so we tap hang up to end call. 
> For the 1st, 4th and 5th time, call "111", it will hang up by itself, then
> display "Unable to make a phone call now" page.

Thanks for the further explanation. Then I would say the gecko log matches the whole behaviour. In addition, based on comment 9, it's due to carrier behaviour.

Comment 12

[BMO Automation]

Firefox OS is not being worked on