Closed Bug 871413 Opened 12 years ago Closed 11 years ago

[System] White screen is displayed shortly on incoming call.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:leo+, b2g18 verified, b2g-v1.1hd fixed)

RESOLVED FIXED
1.1 QE2 (6jun)
blocking-b2g leo+
Tracking Status
b2g18 --- verified
b2g-v1.1hd --- fixed

People

(Reporter: leo.bugzilla.gaia, Assigned: arthurcc)

References

Details

(Keywords: regression, Whiteboard: MiniWW [POVB])

Attachments

(7 files)

1. Title : [System] White screen is displayed shortly on incoming call. 2. Precondition : Run any app (e.g. Clock) except homescreen, browser, dialer. 3. Tester's Action : Use 2nd phone to call 1st phone. 4. Detailed Symptom (ENG.) : On 1st phone, it displays white empty screen shortly before displaying the incoming call screen. 5. Expected : No white screen inbetween should be displayed. 6.Reproducibility: Y 1)Frequency Rate : 100% 7.Gaia Master/v1-train : Reproduced 8.Gaia Revision: 5cbb19e4bb78a7ad879fbe4b9a841e1c35714f5c 9.Personal email id: hanj.kim25@gmail.com This is a regression from Bug 856546.
Debugging Info: I have put some logs as follows. function overlayEventHandler(evt) { console.log('wwwww overlayEventHandler 1, evt.type=' + evt.type); if (attentionScreenTimer && 'mozChromeEvent' != evt.type) { clearTimeout(attentionScreenTimer); console.log('wwwww overlayEventHandler 2, evt.type=' + evt.type); } and it gives the following log when I repro. 05-13 09:02:22.399: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1677 in overlayEventHandler: wwwww overlayEventHandler 1, evt.type=mozChromeEvent 05-13 09:02:22.519: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1677 in overlayEventHandler: wwwww overlayEventHandler 1, evt.type=attentionscreenshow 05-13 09:02:22.519: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1680 in overlayEventHandler: wwwww overlayEventHandler 2, evt.type=attentionscreenshow 05-13 09:02:23.279: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1677 in overlayEventHandler: wwwww overlayEventHandler 1, evt.type=mozChromeEvent 05-13 09:02:23.279: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1677 in overlayEventHandler: wwwww overlayEventHandler 1, evt.type=mozChromeEvent 05-13 09:02:25.109: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1677 in overlayEventHandler: wwwww overlayEventHandler 1, evt.type=mozChromeEvent 05-13 09:02:25.109: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1677 in overlayEventHandler: wwwww overlayEventHandler 1, evt.type=mozChromeEvent 05-13 09:02:25.109: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1677 in overlayEventHandler: wwwww overlayEventHandler 1, evt.type=mozChromeEvent 05-13 09:02:25.679: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1677 in overlayEventHandler: wwwww overlayEventHandler 1, evt.type=attentionscreenhide 05-13 09:02:25.679: E/GeckoConsole(3432): Content JS LOG at app://system.gaiamobile.org/js/window_manager.js:1680 in overlayEventHandler: wwwww overlayEventHandler 2, evt.type=attentionscreenhide
See Also: → 856546
See Also: → 845661
Regression from a tef+ blocker then.
blocking-b2g: --- → tef?
Blocks: 845661
Keywords: regression
See Also: 856546, 845661
Actually, looks like this is a dupe.
Status: NEW → RESOLVED
blocking-b2g: tef? → ---
Closed: 12 years ago
Resolution: --- → DUPLICATE
No longer blocks: 845661
As discussed during San Diego, marking this for Work week.
Whiteboard: MiniWW
blocking-b2g: --- → leo+
Jason, leo claims this bug doesnt seem to be a dup of bug 871374 as this bug is still not fixed with 871374 landed. Can you check this and reopen if it's the case? Thanks.
Flags: needinfo?(jsmith)
Keywords: qawanted
Target Milestone: --- → 1.1 QE2 (6jun)
leo appears to be correct - the Buri guys also saw this bug. Reopening as such.
Status: RESOLVED → REOPENED
blocking-b2g: leo+ → tef?
Flags: needinfo?(jsmith)
Keywords: qawanted
Resolution: DUPLICATE → ---
Wayne we need an assignee here. Can Taipei pick this up today?
I am not seeing this is in candidate ikura device: QC RIL version: "ro.build.firmware_revision=V1.01.00.01.019.120" gaia commit: 50abeb2 Merge pull request #10032 from alivedise/bugzilla/872912_v1.0.1b gecko commit: a6a5487 Bug 875483 - YouTube HTML5 Playback hangs Firefox. r=derf,a=tef+ Can qa do a quick test on buri to check if this is still happening?
Keywords: qawanted
Whiteboard: MiniWW → MiniWW [tef-triage]
Assignee: nobody → arthur.chen
screen grabbed video from bug 871919 video
partner confirms the bug described here is seen in the video on bug 871919 before the incoming call.
Unable to repro issue on Buri Build ID: 20130530070213 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/11b55d3ada71 Gaia: ac293ce59acc3bede083fad1b973794fa8bf0253 No white screen was shown when receiving a phone call while having applications in the background
Keywords: qawanted
Daniel and Jeni are not able to reproduce, so this would have to be POVB. Not making a blocking call, since this is up to our partner as to whether or not they want to block their builds.
Whiteboard: MiniWW [tef-triage] → MiniWW [POVB]
Attachment 756031 [details] looks like over exposure instead of a white screen. What I can reproduce here is a little bit delay of the wallpaper got loaded.
Just tested - this is reproducible on 0507 & 0510 builds, but on 0530 this is not reproduced.
(In reply to Alex Keybl [:akeybl] from comment #14) > Daniel and Jeni are not able to reproduce, so this would have to be POVB. > Not making a blocking call, since this is up to our partner as to whether or > not they want to block their builds. Hi Alex, Was the precondition satisfied when the tests were run? Precondition : Run any app (e.g. Clock) except homescreen, browser, dialer. In other words, the currently displayed app should be any app (e.g. Clock) except homescreen, browser, dialer. Thanks.
Flags: needinfo?(akeybl)
(In reply to Jeni from comment #13) > Unable to repro issue on > Buri Build ID: 20130530070213 > Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/11b55d3ada71 > Gaia: ac293ce59acc3bede083fad1b973794fa8bf0253 > > No white screen was shown when receiving a phone call while having > applications in the background Hi Jeny, Having apps running in background is not enough. The currently displayed app should be any app (e.g. Clock) except homescreen, browser, dialer. Thanks.
Flags: needinfo?(jcouassi)
Attached video Repro video
This video shows a white screen on incoming call on the following build. Mozilla build ID: 20130526070207 QCT Gaia Revision : 4d10e1297b859cacc174c0a54af61a7678d7c32d QCT Gecko Revision : 52341e43539a0e8b9aa77a9128cc3871439b8aa6 Since the whitescreen goes away too fast, let me upload some screenshots from this video after this attachment.
You can see the white screen shortly during the transition. Mozilla build ID: 20130526070207 QCT Gaia Revision : 4d10e1297b859cacc174c0a54af61a7678d7c32d QCT Gecko Revision : 52341e43539a0e8b9aa77a9128cc3871439b8aa6
QAWANTED to TPE QA to confirm on Unagi on v1.0.1 i do not see on buri partner build dated 0530
Keywords: qawanted
I can see that on unagi on v1.0.1, the newest PVT build.
Keywords: qawanted
triage: since the white screen go away really fast. not bad enough to block a release. and not really seeing on buri partner build to make tef+. back to leo+
blocking-b2g: tef? → leo+
Flags: needinfo?(akeybl)
(In reply to Leo from comment #18) > (In reply to Jeni from comment #13) > > Unable to repro issue on > > Buri Build ID: 20130530070213 > > Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/11b55d3ada71 > > Gaia: ac293ce59acc3bede083fad1b973794fa8bf0253 > > > > No white screen was shown when receiving a phone call while having > > applications in the background > > Hi Jeny, > > Having apps running in background is not enough. The currently displayed app > should be any app (e.g. Clock) except homescreen, browser, dialer. > > Thanks. Leo, Apps I had and have running in the background are video, clock, calendar, cost control and unable to get issue to repro. Build ID: 20130530070213
Flags: needinfo?(jcouassi)
Hi Jeni, I think what leo means is to have the app. eg the clock actually running in the foreground when you receive an incoming call. Hi arthur, still on top of this bug?
(In reply to Wayne Chang [:wchang] from comment #25) > Hi Jeni, > I think what leo means is to have the app. eg the clock actually running in > the foreground when you receive an incoming call. > > Hi arthur, > still on top of this bug? Wayne I tested both ways with clock, video, calendar, cost control in the background as well as having clock in the foreground when receiving and incoming call with the Buri device.
It seems a gecko rendering problem, currently I cannot find a solution in gaia. A workaround would be using a darker background to reduce the flashing. Leo, is it okay for you?
Flags: needinfo?(leo.bugzilla.gaia)
A background image is not started to be rendered on the screen until it is in the viewport. A workaround would be to separate the transition to two stages. In the frist stage we force the rendering by moving the element containing the background to the viewport. Then in the second stage we do the real transition. This trick has been used in the settings app.
Etienne, this is the same trick done in the settings app. Could you help review it? Thanks!
Attachment #759054 - Flags: review?(etienne)
Flags: needinfo?(leo.bugzilla.gaia)
Comment on attachment 759054 [details] Link to https://github.com/mozilla-b2g/gaia/pull/10238 All the videos/screenshots of the issue clearly show that the screen is properly rendered (we can see the pickup/hang up buttons). We're just rendering a LightGray background while waiting for the system background. So no need for the .peek hack here. Can you update the PR to include only the CSS change? Black sounds good to me but UX might want to chip in.
Attachment #759054 - Flags: review?(etienne) → review-
The rendering delay does exist even if I used a pre-defined image. But I'm fine with changing the background to black, which is much simpler.
Josh, could you help confirm the default background color of the call screen as the attachment? The color is displayed while we are waiting for the wallpaper loaded and only appears for less than 1 sec. Thanks!
Flags: needinfo?(jcarpenter)
This is a blocker. Please go ahead and land the patch with black and if UX wants something else we can fix it in a separate bug.
Please needinfo firefoxos-ux so we can include bugs like this in our triage and reassign them to available team members as quickly as possible. Josh is no longer taking needinfo so he can focus on other work. Thanks!
Flags: needinfo?(jcarpenter) → needinfo?(firefoxos-ux-bugzilla)
Flags: needinfo?(kyee)
Change the background to black.
Attachment #760824 - Flags: review?(etienne)
Comment on attachment 760824 [details] Link to https://github.com/mozilla-b2g/gaia/pull/10319 Thanks! r=me (e49a2e6d2a8f7a5773dd032ad6527584f34268b7)
Attachment #760824 - Flags: review?(etienne) → review+
This is a visual design call. Flagging Patryk for more info.
Flags: needinfo?(kyee) → needinfo?(padamczyk)
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Attached image Desired Incoming Screen
The desired incoming picture if missing a background should have a translucent black overlay on the wallpaper.
Flags: needinfo?(padamczyk)
The question was, what color should we display _while_ the wallpaper is loading.
The black overlay should have an opacity of 65%
(In reply to Etienne Segonzac (:etienne) from comment #41) > The question was, what color should we display _while_ the wallpaper is > loading. black
Uplifted fd19c108f5d5661cd531eedacd303515ea466d63 to: v1-train: 474e784d5ac2a381092a4896bdb221935ce0159e
Patryk, the original opacity is not changed. The screenshot I attached shows the default color displayed while the wallpaper is loading. After the wallpaper loaded, it looks the same as your attachment.
1.1hd: 474e784d5ac2a381092a4896bdb221935ce0159e
Varified fix on leo 1.1 Mozilla RIL Environmental Variables Build ID: 20130716070204 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/629020cf576b Gaia: fb9362d34260771d4a00b9a0e10a6bbad397bd3b Platform Version: 18.1 RIL Version: 01.01.00.019.138 The user does not see a white empty screen shortly before the incoming call screen.
Clearing old ni? since this is Resolved Fixed.
Flags: needinfo?(firefoxos-ux-bugzilla)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: