touch-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

saviq, right now there doesn't seem to be any way to 'read' the
brightness from u-s-c. So on startup, in order to know what the
brightness level is, indicator-power calls u-s-c's setUserBrightness()
to the default level suggested by powerd.

If the brightness was stored as a readwrite property in a schema
somewhere, then i-power and u-s-s could simply read it at startup.

Moreover, it would allow u-s-s to decouple itself from i-power, as both
could listen for schema changes to know when the brightness level
changed. u-s-c doesn't emit "userBrightnessChanged" signals, so right
now u-s-s delegates its brightness work to i-power so that they don't
overwrite each other's changes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1364453

Title:
  Brightness setting does not persist across reboots

Status in “indicator-power” package in Ubuntu:
  Confirmed
Status in “unity-system-compositor” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  When altering the brightness setting, it is always reset to the
  default value after a reboot. It is expected that changing the setting
  should persist across reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1364453/+subscriptions