Closed
Bug 1250924
Opened 8 years ago
Closed 8 years ago
[Aries] Adjusting the volume turns the screen black
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
mozilla47
Tracking | Status | |
---|---|---|
firefox47 | --- | fixed |
People
(Reporter: kats, Assigned: kats)
References
()
Details
(Keywords: regression, Whiteboard: [2.6-Daily-Testing][Spark])
Attachments
(1 file, 1 obsolete file)
This is a follow-up from bug 1245925 which I landed a patch for and which fixed the issue for me. However others are still seeing this issue. The description below is cloned from bug 1245925 and I modified the build info to reflect the build on which verification failed. +++ This bug was initially created as a clone of Bug #1245925 +++ Description: When the user adjusts the volume, the device screen turns almost completely black, only displaying the volume meter at the top of the screen. The screen stays black until the volume meter times out. This appears to occur anywhere on the phone except at the lockscreen, where this issue doesn't seem to occur. Repro Steps: 1) Update a Aries to 20160216105618 2) Unlock the device 3) Adjust the volume up, then wait for the displayed volume meter to time out 4) Adjust the volume down, then wait for the displayed volume meter to time out 5) Repeat steps 3 and 4 several times Actual: When the volume is adjusted, the device screen goes entirely black, except for the volume meter. Expected: The volume meter is displayed, and all other elements of the device are properly visible beneath the meter. Environmental Variables (from bug 1245925 comment 17): Device: Aries 2.6 BuildID: 20160216105618 Gaia: 4f0e2a1a42a2d049b6fe8f4f095cdcdf0fd5465c Gecko: 6ea654cad929c9bedd8a4161a182b6189fbeae6a Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Comment 1•8 years ago
|
||
A build from today I made does expose the issue.
Comment 2•8 years ago
|
||
HWComposer disabled, rebooted several times, not reproduced. HWCompower enabled, 100% repro.
Comment 3•8 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #2) > HWComposer disabled, rebooted several times, not reproduced. > HWCompower enabled, 100% repro. Ok, false alarm, something else is at play here.
Comment hidden (typo) |
Updated•8 years ago
|
Assignee: bugmail.mozilla → rjesup
Status: NEW → ASSIGNED
Comment hidden (typo) |
Comment hidden (typo) |
Assignee | ||
Updated•8 years ago
|
Assignee: rjesup → bugmail.mozilla
Assignee | ||
Comment 7•8 years ago
|
||
Since I am still unable to repro this and don't really want to spend more time on this bug, I'm going to set the pref to 0 on b2g which disable displayport expiry and should fix the problem.
Assignee | ||
Comment 8•8 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/37847/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/37847/
Attachment #8726187 -
Flags: review?(lissyx+mozillians)
Comment 9•8 years ago
|
||
Comment on attachment 8726187 [details] MozReview Request: Bug 1250924 - Disable displayport expiry on B2G because it causes the screen to go back while adjusting volume. r?gerard-majax https://reviewboard.mozilla.org/r/37847/#review34693 ::: b2g/app/b2g.js:1028 (Diff revision 1) > +pref("apz.displayport_expiry_ms", 0); // causes issues on B2G, see bug 1250924 Tested locally with |user_pref("apz.displayport_expiry_ms", 0);| and so far it looks to fix :)
Attachment #8726187 -
Flags: review?(lissyx+mozillians) → review+
Comment 12•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/702b8da8e312
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
You need to log in
before you can comment on or make changes to this bug.
Description
•