When battery drops below a certain level, power saver is enabled and cuts some functionnalities, like Wi-Fi. If the user re-enables it, it will get re-disabled later by the power saver, which is not very nice from a user experience point of view.
We would certainly take a patch on this. Josh what would be the right behavior to manage the conflict between Power Savings and Networks
blocking-basecamp: ? → -
tracking-b2g18: --- → +
User intent trumps automatic settings. If I manually turn WiFi back on after Power Saver mode disables it, it should stay on. I've clearly communicated my intent.
Whiteboard: BerlinWW, interaction, UX-P2
This issue should have been fixed with Bug 825653. Close it for verification.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(In reply to Rudy Lu [:rudyl] from comment #3) > This issue should have been fixed with Bug 825653. > Close it for verification. That bug is not slated to be uplifted to v1-train but this bug is. We should either: 1) re-evaluate tracking-b2g:+ on this bug 2) flag bug 825653 for tracking-b2g:? 3) land the portion of the patch that fixes this issue to v1-train
I think that patch has landed on v1-train and v1.0.1? https://github.com/mozilla-b2g/gaia/commit/2972142320b74c12c130e044b62c691dea158f8b Thanks.
(In reply to Rudy Lu [:rudyl] from comment #5) > I think that patch has landed on v1-train and v1.0.1? > https://github.com/mozilla-b2g/gaia/commit/ > 2972142320b74c12c130e044b62c691dea158f8b > > Thanks. yes, you are correct! $ git branch --contains 2972142320b74c12c130e044b62c691dea158f8b * master v1-train v1.0.1
status-b2g18: --- → fixed
status-b2g18-v1.0.1: --- → fixed
You need to log in before you can comment on or make changes to this bug.