Closed Bug 1100277 Opened 11 years ago Closed 8 years ago

[Midori 2.0][Call]The add a call is still mute when the first call is mute

Categories

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

defect

Tracking

(tracking-b2g:backlog, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v1.4 --- affected
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: sync-1, Unassigned)

Details

(Whiteboard: [priority])

Attachments

(1 file)

308.39 KB, image/x-png
Details
FFOS2.0 baseline BuildID: 20140916000205 DEFECT DESCRIPTION: The add a call still is mute when the first call is mute REPRODUCING PROCEDURES: 1.make a call->click "mute" icon 2.add a call again->add a call still is mute -->KO ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: medium REPRODUCING RATE: 5/5 For FT PR, Please list reference mobile's behavior:
Attached image pic
The operation in first call affects the second call. So this bug should be fixed.
blocking-b2g: --- → 2.2?
QA wanted for a branch check.
Keywords: qawanted
Tested with Shallow Flash on 319mb using Engineering builds This bug repro's on Flame KK builds: Flame 2.2 kk, Flame 2.1 KK, Flame 2.0 KK, Flame 2.0 Base Actual Results: Muting 1 call will also mute the second call. Repro Rate: 5/5 Environmental Variables: Device: Flame 2.2 KK BuildID: 20141118035525 Gaia: 4aee256937afe9db2520752650685ba61ce6097d Gecko: 7913c9392c5f Version: 36.0a1 (2.2) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 ----------------------------------------------------------------- Environmental Variables: Device: Flame 2.1 KK BuildID: 20141117201226 Gaia: 1b231b87aad384842dfc79614b2a9ca68a4b4ff3 Gecko: 95fbd7635152 Version: 34.0 (2.1) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 ----------------------------------------------------------------- Environmental Variables: Device: Flame 2.0 KK BuildID: 20141118044626 Gaia: 1ede2666f1e6c1b3fd3b282011caf0cbc59544b0 Gecko: bde95439014c Version: 32.0 (2.0) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 ----------------------------------------------------------------- Environmental Variables: Device: Flame 2.0 Base BuildID: 20141021162107 Gaia: 8c5c956ee6909408e29f375cc7d843a03d92f3d8 Version: 32.0 (2.0) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: croesch
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: croesch
Carrie, what are your thoughts on this? I think that this behavior is to be expected. I checked and AOSP does the same thing as we currently do.
Flags: needinfo?(cawang)
Hi, Actually I think it shouldn't be mute for the second call. Because users decide to initiate the second call. I don't think we should take it as the same context of the first call. It should be a whole new start.
Flags: needinfo?(cawang)
Johan also tried Buru with FxOS 1.4. The behavior is always the same, so this cannot be a blocker. Let's backlog it with tracking-b2g flag and fix whenever we have resource.
blocking-b2g: 2.2? → backlog
tracking-b2g: --- → +
Whiteboard: [priority]
blocking-b2g: backlog → ---
[Tracking Requested - why for this release]:
Priority: P2 → P1
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: