Closed
Bug 911685
Opened 12 years ago
Closed 12 years ago
[Buri] It's hard to control device through touching screen.
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: echu, Unassigned)
Details
Attachments
(2 files)
It's hard to use device with this build. See from attached video that oftentimes after touching one item, screen will keep flash back and forth.
Gaia: 9fb5802df60a9081846d704def01df814ed8fbd4
Gecko: http://hg.mozilla.org/mozilla-central/rev/b6c29e434519
BuildID 20130901040215
Version 26.0a1
Only happen if update full image, not found if only update Gaia and Gecko after updating partner's build.
I believe the recommended method of flashing is to flash the base build 1.1 and flash only our gecko/gaia on top. Could you confirm this please, mwu?
Flags: needinfo?(mwu)
Comment 4•12 years ago
|
||
Yeah. Gaia and Gecko only updates are supported configuration, though your bug actually looks related to some missing patches in our gonk-patches repo. A bot on CAF went crazy recently and we had to remove patches. We're going to put them back soon - things may improve after that. Please see bug 912090 to follow along.
Flags: needinfo?(mwu)
Hi Michael,
After clarified the problem with other coworkers, this issue is found after I update full image of Buri from PVT, which will clear partner's image. So there might be something incompatible with moz system image with Buri hardware part(I might not using correct terms). But if I only update gaia and gecko on top of partner's image, no such issue.
I wonder if we often track this kind of issue or just focus on partner image + Moz's gaia and gecko?
Flags: needinfo?(echu)
Comment 7•12 years ago
|
||
Gaia and gecko only flashing is the recommended way to update. Full system builds also work, but you should avoid them unless you need to debug system libraries. We import certain patches to be more compatible with vendor code, but it's difficult to keep track of everything.
Thank you, Michael, I will close the issue.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•