834350 - [B2G][Dialer] Cannot receive subsequent incoming calls after the 1st successful incoming call.

Status: VERIFIED DUPLICATE of bug 818623

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

Description

[mlevin]

Suite Name: Dialer
Test Case #: N/A (Found during Smoketest)
Description: After successfully receiving a 1st incoming call, subsequent incoming calls are not received.

Repro:
1. Update to Unagi build ID 20130124070201
2. Create an incoming call from another device.
3. Ensure User can answer this 1st incoming call on the Unagi.
4. End the call.
5. Keep the Unagi awake and unlocked with the Homescreen viewable.
6. Create a subsequent incoming call from the same device as used in step 2.


Expected:
Unagi should detect the 2nd incoming call, and User should be able to answer it.

Actual (Various):
1. No incoming call detected.
2. Unagi rings but User does not visually see incoming call, plus User has no way of answering incoming call. User must end task Dialer to stop the ringing.
3. Call is seen and heard very briefly then goes away. Cannot answer it.


Repro frequency:
(4/4 on about 15 Unagi devices)

Notes:
Gecko: 49c25ca40020
Gaia: 67a5b7f79b73
Issue also repro's when Unagi is in hibernate mode (screen dark).

Comment 1

[mlevin]

Attachment: Bug 834350

Comment 2

[mlevin]

Log cat attached.

Comment 3

[Allen Maxwell]

Occurred on third call from phone2; regardless if caller answers the first call or not. Additionally, a phone3 was unable to call in. 

Build ID: 20130124070201 
Kernel: Dec 5

Comment 4

[mlevin]

kernel 5 Dec.

Comment 5

[Jason Smith [:jsmith]]

Okay, so this is really bad.

Comment 6

[Jason Smith [:jsmith]]

djf claims this is a known bug and a dupe. Can someone find the dupe?

Comment 8

[mdaniloff]

Unagi build 20130208070201
Kernel 5 Dec 5th

This has been verified fixed, as the user is able to answer the 2nd incoming call as well as the 3rd,4th....

Comment 9

[J Zimbrick]

Verifying as duplicate per comment 7.

Also, issue has been fixed according to bug 818623.

Still appears fixed on an Unagi device running the following build:

Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/af9270e8f205
Gaia: a78ebf426840b5ef08c0cc3e437ad30aba3e2528
Build: 20130318070202