Closed Bug 1050204 Opened 10 years ago Closed 9 years ago

When other device hungs up call I can see a wrong screen

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.1 affected, b2g-v2.2 ?, b2g-master fixed)

RESOLVED WORKSFORME
tracking-b2g backlog
Tracking Status
b2g-v2.1 --- affected
b2g-v2.2 --- ?
b2g-master --- fixed

People

(Reporter: lolimartinezcr, Unassigned)

References

Details

Attachments

(3 files)

Flame
2.1 
Gecko-8d0205c
Gaia-bea8355

Reproducible: 100%

Prerequisites: Call established.

STR:
Other device hunp up call

Actual result:
"Unable to make a phone call now. Cannot make a call. If you are already dialing, please hang up first" Screen. 

Expected result:
Dialer application screen.
Attached image 2014-08-07-12-48-01.png
QA Wanted for branch checks.
Keywords: qawanted
I was unable to repro on today's Flame 2.1.  Can you please provide full envirovmental variables?  Also, are you on 512MB or 319MB?

BuildID: 20140808091209
Gaia: c97d1b6c3094e854377b6affa5f46b8d4b7316ce
Gecko: f40c3647561c
Platform Version: 34.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Flags: needinfo?(lolimartinezcr)
Attached file call_error_screen
This bug repro's on: Flame 2.1, Flame 2.0, Flame 1.4, Buri 2.1

Actual Results: Dialing and getting a message saying "Unable to make a phone call now" "Cannot make a call. If you are already dialing, please hang up first."

STR:
1. Launch Dialer.
2. Type 555-555-5555 and tap the call button.
3. User sees the connecting screen for a second
4. User then sees the error message.

Repro Rate: 5/5

***Note: On Buri, I had to call and wait through the voice message saying could not complete the call as dialed. Eventually it hung up the call then I got the text error message bug.

Environmental Variables:
Device: Flame Master
BuildID: 20140810234109
Gaia: 19ed3c9e78eaf234cc08484bde6998ae21552ba5
Gecko: a9b43778f0c2
Version: 34.0a1 (Master) 
Firmware Version: v123
------------------------------------------------
Environmental Variables:
Device: Flame 2.0
BuildID: 20140811023109
Gaia: edaefce424b78505a82a79cc7a2b5eef9b5e53d3
Gecko: 7e808b6ae5b4
Version: 32.0 (2.0) 
Firmware Version: v123
------------------------------------------------
Environmental Variables:
Device: Flame 1.4
BuildID: 20140811081112
Gaia: d47fecdcaa4aefb754561114edd22fb23a92b98d
Gecko: fbee340d0830
Version: 30.0 (1.4) 
Firmware Version: v123
------------------------------------------------
Environmental Variables:
Device: Buri Master
BuildID: 20140810234109
Gaia: 19ed3c9e78eaf234cc08484bde6998ae21552ba5
Gecko: a9b43778f0c2
Version: 34.0a1 (Master) 
Firmware Version: v1.2device.cfg
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: croesch
Was unable to reproduce with 2 phones calling each other and the non DuT hanging up during the call.
[Blocking Requested - why for this release]: seems like we should block on this - user will get an error message when the called party hangs-up.
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
(In reply to Loli from comment #1)
> Created attachment 8469199 [details]
> 2014-08-07-12-48-01.png

(In reply to Chris Kreinbring [:CKreinbring] from comment #3)
> I was unable to repro on today's Flame 2.1.  Can you please provide full
> envirovmental variables?  Also, are you on 512MB or 319MB?
> 
> BuildID: 20140808091209
> Gaia: c97d1b6c3094e854377b6affa5f46b8d4b7316ce
> Gecko: f40c3647561c
> Platform Version: 34.0a1
> Firmware Version: V123
> User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Device: Flame Master
BuildID: 20140812055843
Gecko-329b2e4
Gaia-da11dba
Version: 34.0a1 (Master)
Flags: needinfo?(lolimartinezcr)
Cody - I'm confused by the testing results above - I think you might be talking about a different bug than what's filed here. Can you specify what the branch checks are against the original STR as filed?
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(croesch)
Keywords: qawanted
Unable to reproduce issue establishing a call between two devices then having the non test device hang up the call. I've tried making them known contacts, Being on different screens when the hang up occurs, Switching up which phone dials out. No luck.

1. Is this a custom build by chance?

2. If not a custom build, is there any other information that you can provide that may be of use in reproing this bug? 

-Builds tested-

Environmental Variables: Nightly build
Device: Flame Master
BuildID: 20140812040201
Gaia: e78e62125eb43c3a28cdc047987ba54430694a2f
Gecko: b53c2753ce9a
Version: 34.0a1 (Master) 
Firmware Version: v123
-----------------------------------------------

Environmental Variables: Engineering build
Device: Flame Master
BuildID: 20140811230755
Gaia: e78e62125eb43c3a28cdc047987ba54430694a2f
Gecko: b53c2753ce9a
Version: 34.0a1 (Master) 
Firmware Version: v123
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(croesch) → needinfo?(lolimartinezcr)
Attached video VID_0001.3gp
Flags: needinfo?(lolimartinezcr)
(In reply to Loli from comment #11)
> Created attachment 8472149 [details]
> VID_0001.3gp

I have attached video about this issue.
Loli, can you provide the information about your build that Cody asked in comment #10?
Flags: needinfo?(lolimartinezcr)
(In reply to Dietrich Ayala (:dietrich) from comment #13)
> Loli, can you provide the information about your build that Cody asked in
> comment #10?


Device: Flame Master
BuildID: 20140813061840
Gecko:d5a4ba9
Gaia:80a41e0
Version: 34.0a1 (Master) 
Git commit: 80a41e0b
Flags: needinfo?(lolimartinezcr)
Lets nom if someone else can repro the same. Backlog till then.
blocking-b2g: 2.0? → backlog
QA Contact: croesch
I'm unable to find the exact builds by ID provided by original reporter on PVT website.
I tested with a Flame 2.1 build on 8/7 when this bug was originally filed, and wasn't able to repro it. Repro rate: 0/5
I also rolled back to v122 firmware and put the same build on top of it and repro rate was 0/5.

Comment 5 was trying to get the same error message with different repro steps. Un-setting tracking flags to reflect actual testing results.

This issue could be carrier specific, device specific (from what I know there are 2 different kinds of Flames?), or build specific. In any case we at QA Wanted are unable to reproduce so I'm removing the qawanted tag.

Tested on:
Device: Flame
BuildID: 20140807055019
Gaia: 079c5f85875b0f2eb341ca9fd375f1b905ed7157
Gecko: bf5cbb36f4d2
Version: 34.0a1 (2.1 Master)
Firmware v123 / v122
User Agent Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
We can't repro this on v3.0.
Status: NEW → RESOLVED
Closed: 9 years ago
status-b2g-v2.2: --- → ?
Resolution: --- → WORKSFORME
See Also: → 1042484
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: