** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613871
Title:
Regression: In dark conditions autobrightness
Little feedback everything is working ok apart from on first boot. If
you are in a dark room on a first boot it will not adapt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613871
Title:
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613871
Title:
Regression: In dark conditions autobrightness
> After some more experimentation with this fix, I noticed a strange behavior
> on Nexus4.
> ... but the N4 display sometimes doesn't react to this high brightness
> setting, remaining
> at an arbitrary lower brightness setting instead. It seems that it takes a
> screen content
> update to
This bug was fixed in the package repowerd -
2016.08.2+16.10.20160823.1-0ubuntu1
---
repowerd (2016.08.2+16.10.20160823.1-0ubuntu1) yakkety; urgency=medium
* New 2016.08.2 release
- Fix "Regression: In dark conditions autobrightness does not
adapt" (LP: #1613871)
--
On krillin and arale, this appears to be fixed by silo 31. The fix
actually allows the brightness to update even faster, by toggling
autobrightness off then immediately back on. By doing that, it can
update in less than a second instead of the usual 4.5 seconds. And it
actually does update now
After some more experimentation with this fix, I noticed a strange
behavior on Nexus4. When autobrightness is enabled and the screen turns
on under bright light, the updated repowerd autobrightness algorithm
transitions the brightness to a high value (as expected), but the N4
display sometimes
The problem was that the autobrightness algorithm was too slow to react
to the first light values after being enabled. This caused both the
related issues mentioned in comments in this bug (taeibot65's and
jibel's).
The fix is in silo 31 and in the process of being merged:
** Branch linked: lp:~ci-train-bot/repowerd/repowerd-ubuntu-yakkety-
landing-031
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613871
Title:
Regression: In dark conditions autobrightness does not
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613871
Title:
Regression: In dark conditions autobrightness does
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: repowerd (Ubuntu)
Status: New => In Progress
** Changed in: repowerd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of
11 matches
Mail list logo
