Closed
Bug 825653
Opened 12 years ago
Closed 11 years ago
Power save mode turns off by itself
Categories
(Firefox OS Graveyard :: Gaia::System, defect, P3)
Tracking
(blocking-basecamp:+)
People
(Reporter: jdm, Assigned: rudyl)
Details
(Keywords: regression)
Attachments
(1 file)
STR: 1. Enable power save mode 2. If it doesn't turn itself back off immediately, turn off the screen and leave your phone for up to 30 minutes. The power save mode is consistently disabled every time I next turn my phone on.
Reporter | ||
Comment 1•12 years ago
|
||
12/12/12 nightly build, for the record.
Comment 2•12 years ago
|
||
Triage: QAWANTED to confirm. since reporter on an old build. if reproduced, please renom. Thanks
blocking-basecamp: ? → -
Keywords: qawanted
Comment 3•12 years ago
|
||
Confirming, I see this using today's nightly 20130102. Renominating. Gecko version is 0c64ef06796c Gaia is ee64aed4ffe4
blocking-basecamp: - → ?
Comment 4•12 years ago
|
||
Triage: BB+, P3, C4 - broken feature. likely a regression
blocking-basecamp: ? → +
Keywords: regression
Priority: -- → P3
Target Milestone: --- → B2G C4 (2jan on)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → rlu
Comment 5•11 years ago
|
||
Rudy, can you provide an update on this one?
Assignee | ||
Comment 6•11 years ago
|
||
Yes, the patch is on the way, will send the pull request later after more testing. Thanks.
Assignee | ||
Comment 7•11 years ago
|
||
We would disable the power save mode when the battery level goes to be > "powersave.threshold". However, we should NOT to disable the power save mode when "powersave.threshold" is set to 0.
Attachment #698682 -
Flags: review?(alive)
Comment 8•11 years ago
|
||
Comment on attachment 698682 [details]
pullRequest 7323
r=me \O/
Attachment #698682 -
Flags: review?(alive) → review+
Assignee | ||
Comment 9•11 years ago
|
||
Close this with, https://github.com/mozilla-b2g/gaia/commit/2972142320b74c12c130e044b62c691dea158f8b
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 10•10 years ago
|
||
I am affected by the issue described in comment #0. I am running Boot2Gecko 2.1.0.0-prerelease, which sounds like it might be newer than tag B2G_1_0_0_20130115070201 referenced in comment #9. I therefore propose the issue has either not been completely fixed or has been reintroduced after the fix.
You need to log in
before you can comment on or make changes to this bug.
Description
•