Closed Bug 1171862 Opened 10 years ago Closed 10 years ago

[FLAME-L] Screen flashes when tapping on it

Categories

(Core Graveyard :: Widget: Gonk, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
FxOS-S2 (10Jul)

People

(Reporter: ericcc, Assigned: jerry)

References

Details

(Whiteboard: [FLAME-L-LOCALBUILD])

Attachments

(1 file)

### STR 1. Open Settings -> Download -> tap on white space 2. Also happening on other apps. ### Actual https://youtu.be/H9vVGLPg978 Screen flashes ### Version Local build Build ID 20150601113003 Gaia Revision 59b859d1cdce2619d4fbf84558b3db376aded83b Gaia Date 2015-06-01 03:11:33 Gecko Revision n/a Gecko Version 41.0a1 Device Name flame Firmware(Release) 5.0 Firmware(Incremental) eng.viralwang.20150601.111147 Firmware Date Mon Jun 1 11:13:04 CST 2015 Bootloader L1TC00011L60
1. Also happening in Gallery apps
Jerry, can you please check this problem?
Flags: needinfo?(hshih)
Assignee: nobody → hshih
Flags: needinfo?(hshih)
Status: NEW → ASSIGNED
After turning off the hardware composer, I don't see the the problem as comment 0. I need to check the hwc function at our new flame-l environment.
Component: Gaia::System::Window Mgmt → Widget: Gonk
Product: Firefox OS → Core
Summary: [FLAME-L][Settings] Screen flashes when tapping on it → [FLAME-L] Screen flashes when tapping on it
Hi Ken, The hwc on flame-l seems broken. I test with a simplified app which only have 1 color-layer and the screen is flickering. Since it only use color-fill feature, I don't think we have fence sync problem. Do we have hwc driver support for flame-l?
Flags: needinfo?(kchang)
FWIW, flame-l is using an Android base version (5.0) that's different from the version that's being supporting in CAF for Lollipop (5.1). Color fill is a HWC feature that only Gecko uses, so it's not surprising that it would have issues on an unsupported base.
Hi Michael, We query the color-fill feature and get the supported value here[1], but it seems still have problem for this function. https://hg.mozilla.org/mozilla-central/annotate/e7e69cc8c07b/widget/gonk/HwcComposer2D.cpp#l122
If it helps, we can probably disable colorfill since we have a fork of the hwc hal for the flame-l port - https://github.com/mozilla-b2g/hardware_qcom_display/tree/foxfone-one-lollipop . Alternately, you might be able to find a fix for this issue in CAF. If you do, that fix can be cherry-picked over.
Finally, I know what's going on here! We have a mismatch HWC_BLIT define value between gecko and hal. Just like https://bugzilla.mozilla.org/show_bug.cgi?id=1127585#c12, I would like to use the higher value for HWC_BLIT. So I will create a pull request to https://github.com/mozilla-b2g/hardware_qcom_display/commits/foxfone-one-lollipop later.
Flags: needinfo?(kchang)
See Also: → 1127585
Comment on attachment 8630946 [details] [review] Fix the mismatched HWC_BLIT value for flame-l device Perfect. Good find.
Attachment #8630946 - Flags: review?(mwu) → review+
I am not sure who can handle this pull request.
Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → FxOS-S2 (10Jul)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: