Closed
Bug 894836
Opened 13 years ago
Closed 12 years ago
[Buri][Contacts]It was blinking,when you select Gmail.
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect, P1)
Firefox OS Graveyard
Gaia::E-Mail
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: sync-1, Unassigned)
References
Details
(Whiteboard: [mozilla-triage])
AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.158
Firefox os v1.1
Mozilla build ID:20130709070206
Created an attachment (id=459394)
log
DEFECT DESCRIPTION:
It was blinking,when you select Gmail.
REPRODUCING PROCEDURES:
1.Launch contacts,settings,select Gmail
2.press Email box,screen was blinking--->KO1
3.When you browse to the bottom,you will find the top of the screen was white----->KO2
EXPECTED BEHAVIOUR:
The MS should displayed normally
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
SWV171+ZZ
USER IMPACT:
Mid
REPRODUCING RATE:
5/5
For FT PR, Please list reference mobile's behavior:
Comment 1•13 years ago
|
||
We discussed this during triage and since this doesn't seem to impede functionality, we recommend not blocking v1.1 on this.
As an aside, I've spoken with Milan and he's going to try to reproduce. A video of the behaviour here would greatly help :)
Whiteboard: [mozilla-triage]
Comment 2•13 years ago
|
||
Yes, video would help a lot, I'm not sure what I'm looking for. I did a quick test with Hamachi and it seems to be working nicely, I'll try and find a Leo phone.
Comment 3•13 years ago
|
||
I'm wondering if this is related, possibly a dupe of bug 873937.
Comment 4•13 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #3)
> I'm wondering if this is related, possibly a dupe of bug 873937.
I seems a different problem. I saw similar rendering problem, but it happened only when hw composer is enabled. When I made a rom to disable HW composer, this rendering problem do not happen.
Comment 5•13 years ago
|
||
When I saw flashing at Settings app on hamashi, adb logcat outputed following log. From the log, rendering failed in hw composer by some reasons.
> E copybit : copyBits failed (Invalid argument)
> E copybit : 0: src={w=320, h=480, f=1, rect={0,0,320,50}}
> E copybit : dst={w=320, h=480, f=12, rect={0,20,320,50}}
> E copybit : flags=00020000
> E copybit : 1: src={w=320, h=480, f=1, rect={0,70,320,390}}
> E copybit : dst={w=320, h=480, f=12, rect={0,90,320,390}}
> E copybit : flags=00020000
> E msm7627a.hwcomposer: drawLayerUsingCopybit: copybit stretch failed
Comment 6•13 years ago
|
||
And when I get "adb shell dmesg", the log have following log. It seems that mdp failed to get drawing image by some reason.
> <3>[ 1369.650784] mdp_ppp: could not retrieve image from memory
> <3>[ 1369.996126] mdp_ppp: could not retrieve image from memory
> <3>[ 1371.580464] mdp_ppp: could not retrieve image from memory
> <3>[ 1371.594463] mdp_ppp: could not retrieve image from memory
> <3>[ 1371.613079] mdp_ppp: could not retrieve image from memory
Comment 7•13 years ago
|
||
sync-1, can you provide a video, logcat log and dmesg log of when the problem happens.
Flags: needinfo?(sync-1)
Comment 9•13 years ago
|
||
Triage with partners - agree non blocking
(In reply to Andrew Overholt [:overholt] from comment #1)
> We discussed this during triage and since this doesn't seem to impede
> functionality, we recommend not blocking v1.1 on this.
>
> As an aside, I've spoken with Milan and he's going to try to reproduce. A
> video of the behaviour here would greatly help :)
blocking-b2g: leo? → ---
Comment 11•13 years ago
|
||
I can reliably reproduce the copybit failure while importing vcard contacts off the sdcard. Video available in bug 896698.
Comment 12•13 years ago
|
||
If this is anything like bug 901395, this is fixed by updating the partner build
Flags: needinfo?(dwilson)
Updated•12 years ago
|
Flags: needinfo?(sync-1)
Comment 13•12 years ago
|
||
resolving WFM based on comment 12 and nothing like this having been reported for some time. (APZ paint glitches are something different.)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•