Closed
Bug 999699
Opened 11 years ago
Closed 11 years ago
[B2G][Open_C][Camera]Countdown timer disappears
Categories
(Core Graveyard :: Widget: Gonk, defect)
Tracking
(blocking-b2g:1.4+, firefox30 wontfix, firefox31 wontfix, firefox32 fixed, b2g-v1.4 fixed, b2g-v2.0 fixed)
People
(Reporter: astole, Assigned: sushilchauhan)
References
()
Details
(Keywords: regression, Whiteboard: [CR 658854])
Attachments
(1 file, 2 obsolete files)
|
2.44 KB,
patch
|
sushilchauhan
:
review+
|
Details | Diff | Splinter Review |
The countdown timer disappears after displaying the first number in the countdown. The countdown does not stop and the picture is still taken, only the timer numbers disappears.
Repro Steps:
1) Update a Open_C/Flame to BuildID: 20140422040203
2) Launch camera app
3) Select the options menu in the top right corner
4) Select Self-Timer and choose any time
5) Take a picture
Actual:
The countdown timer disappears
Expected:
The timer does not disappear until after it has finished counting down
2.0 Environmental Variables:
Device: Open_C 2.0 MOZ
BuildID: 20140422040203
Gaia: f0463704888881b8ed1619e8d4b0d851b0e0311b
Gecko: 1d0496e30feb
Version: 31.0a1
Firmware Version: V1.2-device.cfg
Repro frequency: 3/3, 100%
See attached: Video, logcat
| Reporter | ||
Comment 1•11 years ago
|
||
This issue does not occur on the latest Master build on Buri.
status-b2g-v2.0:
--- → affected
Comment 3•11 years ago
|
||
Unable to test this issue on 1.4 Open C currently.
Camera is blocked by Bug 1000567, displaying only a black screen with non-functional UI.
Can retest when Bug 1000567 is fixed.
1.4 Environmental Variables:
Device: Open C
BuildID: 20140429000201
Gaia: cf590ecb161e7b9fb4ccc672f950072acad62caa
Gecko: 32da83ceb532
Version: 30.0
Base Image: P821A10-ENG_20140410
Keywords: qawanted
QA Contact: jzimbrick
Comment 4•11 years ago
|
||
Can this be reproduced on Flame on master? If so, can we check if this reproduces on Flame on 1.4?
Keywords: qawanted
Updated•11 years ago
|
Keywords: qawanted → regression
Updated•11 years ago
|
blocking-b2g: --- → 1.4+
Updated•11 years ago
|
Component: Gaia::Camera → Graphics: Layers
Product: Firefox OS → Core
Version: unspecified → 30 Branch
Updated•11 years ago
|
Assignee: nobody → sushilchauhan
This is a regression caused by Bugzilla patch: https://bugzilla.mozilla.org/show_bug.cgi?id=993160.
When self-timer ticks and "2" & "1" fade-out, there are multiple containers in those particular frames which need "Intermediate surface" and they do not have any leaves. But HWC works only on leaf layers so we never reach the check at [1]. So it is better to let GPU handle a frame which needs intermediate surface. I checked by reverting this patch, the regression is fixed. I also verified that the original bug reported in Bugzilla # 993160 , does not exist even after reverting the patch, which means Camera preview is using HWC Composition on b2g v1.4 reference device, so we can now safely revert the patch. I will upload the revert of this patch.
[1]: http://mxr.mozilla.org/mozilla-central/source/widget/gonk/HwcComposer2D.cpp#331
Use GPU Composition when a frame needs intermediate surface. It is because HWC composes only leaf layers but not the containers so it is always safer to let GPU handle a frame which needs intermediate surface to make sure HwcComposer2D do not break the feature.
Attachment #8417509 -
Flags: review?(dwilson)
Comment 8•11 years ago
|
||
Comment on attachment 8417509 [details] [diff] [review]
Use GPU Composition when a frame needs intermediate surface.
LGTM
Attachment #8417509 -
Flags: review?(dwilson) → review+
Updated•11 years ago
|
Component: Graphics: Layers → Widget: Gonk
Uploading HG friendly version of reviewed patch.
Attachment #8410538 -
Attachment is obsolete: true
Attachment #8417509 -
Attachment is obsolete: true
Attachment #8417626 -
Flags: review+
Keywords: checkin-needed
Comment 10•11 years ago
|
||
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
Comment 12•11 years ago
|
||
status-b2g-v1.4:
--- → fixed
status-firefox30:
--- → wontfix
status-firefox31:
--- → wontfix
status-firefox32:
--- → fixed
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•