Closed Bug 957207 Opened 12 years ago Closed 12 years ago

[B2G][Dialer] Unable to close or hang up the dialer when we dialing out a second call

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v1.2 unaffected, b2g-v1.3 affected)

RESOLVED WORKSFORME
Tracking Status
b2g-v1.2 --- unaffected
b2g-v1.3 --- affected

People

(Reporter: selkabule, Unassigned)

Details

(Whiteboard: dogfood1.3)

Attachments

(1 file)

Attached file Dialer bug cat log.txt
Description: When making a secound call on the device. The user is not able to close the or terminate the call in proceses. The call will be stuck in the banner and the user can navigate through the device but unable to use the dialer untill the device is restarted Repro Steps: 1) Updated Buri1.3 2) Launch the dialer 3) Call(123) 4) Tap on the add call icon 5) Select a saved contact and tap on the number to make the call 6) Select OK from the dialog "Unable to make asecond call there a call in prosses" 7) Tap on the banner to return to the dialer to end the call in process Actual: The user cannot hang up or close the call untill restarting the device Expected: The user must be able to close the phone call when selecting the red hang up button any time in the call Environmental Variables Device: buri1.3 Moz Ril Build ID: 20140107004001 Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/71ad7ff30010 Gaia: ff5f06dd321f7d2bf4a5b311ded2c56e865d4f83 Platform Version: 28.0a2 Notes: Repro frequency: 100% Test Suite Name: Dialer See attached: video clip(http://www.youtube.com/watch?edit=vd&v=GYIq1_3ZQAg), logcat
This issue does nor reproduce buri1.2 Moz Ril Environmental Variables Device: buri1.2 Moz Ril Build ID: 20140106004001 Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/d552c08a72d0 Gaia: 8441587c3b352e052fee07665c21fd192540f19f Platform Version: 26.0
blocking-b2g: --- → 1.3?
I've worked with Salem on this bug and it turned out that the behavior observed here is caused by a OS crash. It's a same crash that we are seeing all over the place now... https://crash-stats.mozilla.com/report/index/97d6c85f-f8a9-459c-ba55-627fb2140107 I am duping this bug to bug 952170 where we track this crash
Status: NEW → RESOLVED
blocking-b2g: 1.3? → ---
Closed: 12 years ago
Resolution: --- → DUPLICATE
oops, wrong bug, reverting...
Status: RESOLVED → REOPENED
blocking-b2g: --- → 1.3?
Resolution: DUPLICATE → ---
Okay, speaking of this bug now. There is another conference call bug which got fixed with the new base image (bug 943117). Having confirmed with Naoki that conference call feature works better with the new image, we've retested this bug using new image (20131209) and this issue doesn't reproduce (worked with the reporter to make sure STR are correct) So this particular issue can be closed for now, and it probably would make sense to test conference call using new base image... Device: Buri v1.3 Mozilla RIL BuildID: 20140107004001 Gaia: ff5f06dd321f7d2bf4a5b311ded2c56e865d4f83 Gecko: 71ad7ff30010 Version: 28.0a2 Firmware Version: 20131209
Status: REOPENED → RESOLVED
blocking-b2g: 1.3? → ---
Closed: 12 years ago12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: