871762 - [B2G] [Inari] [Dialer] Call screen does not display when making a call

Status: RESOLVED FIXED

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

Description

[Bob Silverberg [:bsilverberg]]

Attachment: Logcat from the test

Description:
On the current v1.0.1 build on an Inari device, when making a call the call screen does not appear.

Repro Steps:
1) Make a call by typing numbers into the keypad and clicking the green call button. Note the number is used was 18007072533.

Expected:
The call screen appears with the number dialed and the option to hang up the call.

Actual:
The call is made, and can he heard, but the call screen never appears. The user is left at the keypad screen.

This is on an Inari with the commercial build:
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/6e1dbf036d34
Gaia   54dfb62735c81152eef74eb1768e2bf621c0a258
BuildID 20130513070209
Version 18.0

A logcat from this test is attached.

Comment 1

[Bob Silverberg [:bsilverberg]]

Note that I see the same behaviour when launching a call from the Contact details screen - the call is made, but the call screen never appears.

Comment 2

[Marcia Knous [:marcia]]

Haven't been able to reproduce this using:

Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/50726fbdc25e
Gaia   a503d9a1d0a588f3689243c1ddc0f016ede51b9d
BuildID 20130513070206
Version 18.0

I tried both the number Bob listed as well as some other 1-800 numbers, and all of them worked fine.

Comment 3

[Marcia Knous [:marcia]]

It looks as if I mistakenly tested V1 train, trying 1.0.1 Commercial RIL build now.

Comment 4

[Marcia Knous [:marcia]]

Attachment: Screenshot of call being initiated

Tested this time, 1.0.1 build with Comm RIL:

Gecko  http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/6e1dbf036d34
Gaia   54dfb62735c81152eef74eb1768e2bf621c0a258
BuildID 20130513070209
Version 18.0

Seems to still work - maybe an issue with the Engineering build?

Comment 5

[Bob Silverberg [:bsilverberg]]

I was able to verify that this problem *does not* exist with the non-Eng build. I then re-flashed with the same Eng build that had problems earlier, and now it seems fine too. It could be some sort of weird flashing fluke, but the same tests were also failing on our CI with the same errors, so it's a bit of a mystery. I'm going to keep this open for a bit until we can get our CI passing too.

Comment 6

[Bob Silverberg [:bsilverberg]]

Our CI job failed again with the same problem, and I also recreated it locally on my phone. Perhaps it has to do with another test that is run before the dialer tests, but it does seem possible to get the phone into a state where this problem occurs 100% of the time.

Comment 7

[Bob Silverberg [:bsilverberg]]

This is no longer happening either locally or on our CI, so I'm closing the bug. Must have been a problem with a build which is now fixed.