Closed Bug 947017 Opened 11 years ago Closed 11 years ago

[B2G][Dialer][Buri] While in a call, an incoming call is not displayed

Categories

(Firefox OS Graveyard :: Vendcom, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(firefox28 affected, b2g-v1.2 affected)

RESOLVED FIXED
Tracking Status
firefox28 --- affected
b2g-v1.2 --- affected

People

(Reporter: jschmitt, Unassigned)

References

Details

Attachments

(1 file)

Description: Being in a call and having an incoming call to the device it does display or give indication that a incoming call is being made. Repo: 1. Make a call from device 1 to device 2 2. Accept the call 3. Make a call to device 1 from device 3 Actual: On device 1, there is no display or indication that device 3 is calling. Expected: A notification that device 3 is calling device 1 while being in a call. 1.3 Environmental Variables: Device: Buri v1.3 MOZ RIL BuildID: 20131205040201 Gaia: 1dd0e5c644b4c677a4e8fa02e50d52136db489d9 Gecko: 725c36b5de1a Version: 28.0a1 Firmware Version: V1.2_20131115
Attached file log.txt
Issue reproduces on 1.2 MOZ RIL, however does not reproduce on 1.2 COM RIL Environmental Variables Device: Buri v1.2 Moz RIL Build ID: 20131205004003 Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/af2c7ebb5967 Gaia: 0659f16b9790b1cf9eba4d80743fcc774d2ffe3a Platform Version: 26.0
The root cause looks the same as https://bugzilla.mozilla.org/show_bug.cgi?id=943117#c7 Buri base image lacks a property 'ro.moz.ril.extra_int_2nd_call=true'.
See Also: → 943117
Summary: [B2G][Dialer] While in a call, an incoming call is not displayed → [B2G][Dialer][Buri] While in a call, an incoming call is not displayed
Component: Gaia::Dialer → Vendcom
Hi Vance, could you let buri team know please?
Flags: needinfo?(vchen)
Per bug 943117 comment 17, I believe this issue should be fixed with the latest base image. Ask for QA's help to confirm and close the bug.
Flags: needinfo?(vchen)
Keywords: qawanted
QA Contact: rkunkel
(In reply to Hsin-Yi Tsai [:hsinyi] from comment #5) I was able to reproduce the issue in the latest Buri v1.2 build. While currently in a call the user will not be notified of another incoming call. Environmental Variables: Device: Buri v1.2 Mozilla RIL BuildID: 20131216004002 Gaia: fcf1c2fe020c29da4755621cbffdc1a333a43be9 Gecko: 129ad3c335a5 Version: 26.0 Firmware Version: V1.2_US_20131115
Keywords: qawanted
(In reply to Roland Kunkel [:RolandK] from comment #6) > (In reply to Hsin-Yi Tsai [:hsinyi] from comment #5) > Gaia: fcf1c2fe020c29da4755621cbffdc1a333a43be9 > Gecko: 129ad3c335a5 > Version: 26.0 > Firmware Version: V1.2_US_20131115 Hi Roland, actually there is a newer 1.2 image available now, could you help to use V1.2_20131209 to verify this issue again? Please contact me if you cannot find this new 1.2 image Thanks
Flags: needinfo?(rkunkel)
Keywords: qawanted
(In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #7) > > Hi Roland, actually there is a newer 1.2 image available now, could you help > to use V1.2_20131209 to verify this issue again? > We are currently not able to test with the new base image as per Jason's recommendations. Jason Smith's email to the smoketest team > Let's move back to the old base image then. bug 949535 is too critical to warrant effective usage of the new base > image. However, for this specific case I've flashed to the V1.2_20131209 and latest v1.2 build. This issue does not reproduce with the latest base image and latest Buri v1.2 build. 1.2 Environmental Variables: BuildID: 20131217004001 Gaia: 4f53ba8b3628ac311253fc28dfdf66e7ba6832de Gecko: 129ad3c335a5 Version: 26.0 Base Image: V1.2_20131209
Flags: needinfo?(rkunkel)
Keywords: qawanted
Okay, the above comment implies this is fixed by the new base image then.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: