> After some more experimentation with this fix, I noticed a strange behavior > on Nexus4. <snip> > ... 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 "remind" the Nexus4 display that the brightness has changed.
An update: In the latest package release 2016.08.2+16.10.20160823.1-0ubuntu1 I have provided a workaround for the Nexus 4, by applying the last normal brightness value before letting autobrightness take over when turning on the display. This is not ideal, but it's what powerd did in the past, and fixes Nexus 4 to have a quick reaction time. Note that this workaround applies only to Nexus 4. Other devices use the autobrightness setting directly when turning on the display (and autobrightness is enabled, of course), providing a smoother display-on experience. -- 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 adapt To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
