Closed
Bug 1093364
Opened 10 years ago
Closed 10 years ago
[Dialer] Call screen does not display call info and shows a black background
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(blocking-b2g:2.2+, b2g-v2.0 unaffected, b2g-v2.1 unaffected, b2g-v2.2 affected)
RESOLVED
WORKSFORME
blocking-b2g | 2.2+ |
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | unaffected |
b2g-v2.2 | --- | affected |
People
(Reporter: rpribble, Assigned: thills)
Details
(Keywords: regression, Whiteboard: [2.2-Daily-Testing])
Attachments
(2 files)
Description: The call screen shows a black background and does not display the call information, such as the manually dialed number or contact information. Repro Steps: 1) Update a Flame device to BuildID: 20141103040202 (without importing contacts) 2) Receive a text from device B, and send a text in response 3) Receive a call from device B 4) Answer the call, then hang up 5) Enter the dialer, begin typing device B's number 6) Tap the call log tab to check the phone number being dialed 7) Tap back to the dialer tab, finish typing the number and make the call Actual: Call screen shows a black background and no call information. Expected: Call screen shows current background and the call information. Environmental Variables: Device: Flame 2.2 Master KK (full flash) BuildID: 20141103040202 (319 MB) Gaia: bc168c17474dabbcceaa349e9bc7c95654435aec Gecko: 5999e92e89ff Gonk: 48835395daa6a49b281db62c50805bd6ca24077e Version: 36.0a1 (2.2 Master) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 Notes: Same issue as bug 1070066. Repro frequency: 6/6 See attached: Logcat, video
Reporter | ||
Comment 1•10 years ago
|
||
Attaching a screenshot rather than a video.
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Comment 2•10 years ago
|
||
Adding qawanted for branch checks and to clarify STR's, seems to only happen in specific scenarios.
Comment 3•10 years ago
|
||
I was only able to get this one time directly after flashing the Flame to 2.2. *NOTE* I noticed also that in the call log, no calls were getting saved in the call log when this black screen bug occurs. If call logs are getting recorded it seems this black screen bug cannot happen. The reporter also saw this same behavior. My STR: 1. Freshly flash a Flame device to 2.2 latest. 2. Call the Flame device from a second device. 3. When call comes in, the incoming call screen has a black background. Tested with Shallow Flash on 319mb using Engineering builds This bug repro's on Flame KK builds: Flame 2.2 KK Actual Results: Getting black sections on the Call incoming screen. Repro Rate: 1/10 Environmental Variables: Device: Flame 2.2 KK BuildID: 20141104041844 Gaia: 3c50520982560ccba301474d1ac43706138fc851 Gecko: cadcd47db610 Version: 36.0a1 (2.2) Firmware Version: L1TC10011880 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 ----------------------------------------------------------------- ----------------------------------------------------------------- This bug does NOT repro on Flame kk build: Flame 2.1 KK, Flame 2.0 KK Actual Result: Unable to get the call incoming or call outgoing screen to display black sections on it. Repro Rate: 0/10 Environmental Variables: Device: Flame 2.1 KK BuildID: 20141104070645 Gaia: 9d80d556123553e5fd8acd982192e33807e9e1fe Gecko: 0953b46ee9a8 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: 20141104053644 Gaia: fe2167fa5314c7e71c143a590914cbf3771905a8 Gecko: 093de6b632c5 Version: 32.0 (2.0) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → unaffected
status-b2g-v2.1:
--- → unaffected
Flags: needinfo?(jmitchell)
Keywords: qawanted → regression
Comment 4•10 years ago
|
||
nomming for 2.2 - this prevents the user from seeing who is calling which is basic dialer functionality. Unfortunately with such a low repro rate we will not be able to get a regression window.
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → thills
Updated•10 years ago
|
Keywords: regressionwindow-wanted
Assignee | ||
Comment 7•10 years ago
|
||
Hi Johan, I was able to repro this bug (using the first STR with the text message, but not the second method). I tried on the latest master and was not able to repro the problem using the first set of steps. Do you mind trying on latest build and then if you can't repro, I can try and track down what might have fixed it? Also, if I'm supposed to be asking someone else or setting a flag to ask the creator to do it, please let me know :) Thanks, -tamara
Flags: needinfo?(jlorenzo)
Comment 8•10 years ago
|
||
I don't repro either on: Gaia-Rev e64428c5b2dce5db90b75a5055077a04f4bd4819 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/aa72ddfe9f93 Build-ID 20141119160202 Version 36.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental 39 FW-Date Thu Oct 16 18:19:14 CST 2014 Bootloader L1TC00011880 In that case, I'd prefer to ask the creator of this bug because the steps are pretty tricky. Rachel can you reproduce on the latest master?
Flags: needinfo?(jlorenzo) → needinfo?(rpribble)
Comment 9•10 years ago
|
||
(In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #8) > I don't repro either by following the steps in comment 0.
Comment 10•10 years ago
|
||
Rachel is no longer with us, I'll throw this into our QA-Wanted Queue to get someone to attempt a repro on the latest master using the steps in comment 0
Flags: needinfo?(rpribble)
Keywords: qawanted
Comment 11•10 years ago
|
||
Unable to reproduce issue in latest Flame 2.2 build (Full flash, nightly, 319 MB memory). Repro attempts: 0/10 Actual Results: Call screen appears correctly when number is dialed. Device: Flame 2.2 BuildID: 20141120040205 Gaia: 1abe09b4925547699dfdb2d358aed019137c3aa6 Gecko: 6ce1b906c690 Gonk: 48835395daa6a49b281db62c50805bd6ca24077e Version: 36.0a1 (2.2) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Comment 12•10 years ago
|
||
Comment 7, comment 8 and comment 11 are all no-repros in the latest. Let's close this as WFM and re-open if this is seen again.
You need to log in
before you can comment on or make changes to this bug.
Description
•