Comment 3 for bug 1364453

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.