[Dialer] in a conference call going from dialer back to conference call screen gives visual error

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
4 years ago
4 years ago

People

(Reporter: rmitchell, Unassigned)

Tracking

({regression})

unspecified
ARM
Gonk (Firefox OS)
regression

Firefox Tracking Flags

(b2g-v2.0 unaffected, b2g-v2.1 affected, b2g-v2.2 unaffected)

Details

(Whiteboard: [2.1-exploratory-3], URL)

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8515370 [details]
logcat_20141031_1633.txt

Description:
in a conference call going from dialer back to conference call screen gives dialer to stick on screen for a few seconds after going back to call screen.


Repro Steps:
1) Update a Flame to 20141031001201
2) make a conference call 
3) go to home screen then dialer 
4) Go back to call screen 


Actual:
graphical error occurs 


Expected:
no graphical error 

Environmental Variables:
Device: Flame 2.1
Build ID: 20141031001201
Gaia: f89c7b12c36572262c9ea76058694a139b1a8634
Gecko: 50d48f8a04c7
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 34.0 (2.1)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Repro frequency:100%
See attached:logcat video clip:https://www.youtube.com/watch?v=XbWNyU9rVlc
Flags: needinfo?(jmitchell)
(Reporter)

Comment 1

4 years ago
This issue Does not occur on flame 2.2 (319mb)(Kitkat Base)(Full Flash) or  2.0 (319mb)(Kitkat Base)(Full Flash)

no graphic issues 

Flame 2.2

Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141031061804
Gaia: a07994714f0552f89801d6097982308d8b0a1ee1
Gecko: 6bd2071b373f
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 36.0a1 (2.2)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

 
Flame 2.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141031000201
Gaia: 7b8df9941700c1f6d6d51ff464f0c8ae32008cd2
Gecko: 82a6ed695964
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 32.0 (2.0)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
NI to dialer owner for blocking call
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(jlorenzo)
I don't see what's the issue per the video. I tried to repro on 2.1 [1] and 2.2 [2] both side by side at the same time and I didn't notice a difference. Your video shows a single call of 11 minutes, maybe it's the related to the duration?

RJ, can you check again on today's build? 

[1] Gaia-Rev        027a7de0c95320cea0579bfd1a4ceef3e9038f34
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/ffecb2be228b
Build-ID        20141103001220
Version         34.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  39
FW-Date         Thu Oct 16 18:19:14 CST 2014
Bootloader      L1TC00011880

[2] Gaia-Rev        c2c55870de22d596de4f41612c0b44090f90ebad
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/0b81c10a9074
Build-ID        20141102160202
Version         36.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141102.191812
FW-Date         Sun Nov  2 19:18:23 EST 2014
Bootloader      L1TC00011880
Flags: needinfo?(jlorenzo) → needinfo?(rmitchell)
(Reporter)

Comment 4

4 years ago
the error was a black blip on the top right of the screen, on the video it was very brief, But it does not seem to be occurring on today's build.

Environmental Variables:
Device: Flame 2.1
Build ID: 20141103001220
Gaia: 027a7de0c95320cea0579bfd1a4ceef3e9038f34
Gecko: ffecb2be228b
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 34.0 (2.1)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Flags: needinfo?(rmitchell)
Good! Can you mark this bug as RESOLVED->WORSFORME then?
Flags: needinfo?(rmitchell)
(Reporter)

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(rmitchell)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.