Unity8 - Saviq

- listen to all input events
-- disable touch input when proximity sensor enabled and triggered
- read display settings from settings app
- take over display lock DBus interface from powerd
-- along with proximity
- handle auto-brightness
- talk to u-s-c to request screen / brightness changes

USC/powerd - Aguirre

- Listen to input channel events, restart screen-off and dimmer timer after every new event.
- Listen to power key button event - override all timers and all pending screen-state change events.
- Obtain inacitivity timeout numbers from mir based shell. USC to use default values if no session was ever active.
- All the proximity sensor handling, light sensor and actual backlight device communication stays in powerd (USC calls powerd to actually set user/dim brightness)
- Remove display power state changes and input inactivity handling from powerd

Power off dialog design:
https:/ /launchpadlibra rian.net/ 158819734/ poweroff- buttons. png
https:/ /docs.google. com/a/canonical .com/file/ d/0B2mvp37s6lHv MWZ5OVFZM2wtbk0 /edit

kgunn query
- wouldn't timer values also potentially be in settings, e.g. maybe a pre-compile list available to the user on the phone screen always on, 1 min, 5 min, 15 min ? (maybe arbitrary user setting time on desktop?)
- so u-s-c would read settings for timer values ?
- maybe we should do a 30 min malta session on proximity with unity, settings, mir, phonedations ?
   * potential proximity policy
     > proximity sensor only turned on during live communication, so active telepathy session & earpiece audio active
       → it could be used for other things, too, e.g. N9 lets you mute an incoming call or
         alarm by putting your phone on its face
     > proximity policy should determine if telepathy session active & earpiece audio active
        (not u-s-c, trust that proximity policy is trustworhty from u-s-c point of view)
     > activating handsfree turns proximity off
     > in active telepathy session w/ earpiece proximity policy can request screen-off & screen-on based on proximity data
     > proximity policy should request screen-on in end of telepathy session