Brightness setting does not persist across reboots

We'll need to store this somewhere; probably in the "com.ubuntu.touch.system" schema alongside the auto-brightness flag setting?

In order to fail gracefully on non-touch (ie unity7), indicator-power would need to check g_settings_schema_source_lookup() to see if the schema's installed.

Yeah, and the shell needs to proxy the setting to u-s-c.

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.

@charlesk,

Yeah com.ubuntu.touch.system schema is the best place for it.

Unity8 shell proxying the value could come later and then we could remove the IbBrightnessUscreenControl from indicator-power but that looks a bit more involved.

This isn't a deal-breaker, but consider the future case of a Touch split greeter (or the desktop case where it's a current reality). What should the starting device brightness be on boot?

It seems like you are intending to store this value per-user inside the user session's gsettings database, which may not be accessible by boot time (in the split greeter cases -- encrypted home directories and all that). Even storing in AccountsService would feel weird, since this is kind of a device-wide setting, right?

mterry: we have a plan cooking for post-rtm to address these issues of system-wide settings vs. user-settings and split greeter.

I agree that this should be a systemwide preference and that it's not in this patch.

In this patch it's grouped with the existing auto-brightness setting, which should probably *also* be a systemwide one post-RTM.

This bug was fixed in the package gsettings-ubuntu-touch-schemas - 0.0.3+14.10.20140912-0ubuntu1

---------------
gsettings-ubuntu-touch-schemas (0.0.3+14.10.20140912-0ubuntu1) utopic; urgency=low

  [ Charles Kerr ]
  * Add 'brightness' setting to com.ubuntu.touch.system (LP: #1364453)
 -- Ubuntu daily release <email address hidden> Fri, 12 Sep 2014 18:52:08 +0000