unity-api-bugs team mailing list archive

[Yuan-Chen Cheng <yc.cheng@xxxxxxxxxxxxx>]

Analysis:

- powerd control backlight by using android library through hybris.
- powerd currently have dbus method that can adjust brightness, and it will remember the value of brightness if the value is set via dbus method. currently the dbus method only allow process with root account to use.
- indicator-power control backlight by find the backlight device throught udev matching rule.

Proposed solution:

- modify the powerd to allow method call from non-root process (indicator-power run by account phablet)
- modify indicator-power to check whether the bus name that powerd use is claimed. If yes, it use dbus method to control backlight. Or else it fall back to udev matching rule to find backlight device node.

-- 
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to indicator-power.
https://bugs.launchpad.net/bugs/1287599

Title:
  As deivce comes back from lock, the back-light level becomes max
  instead of the last set value

Status in The Power Indicator:
  New

Bug description:
  Currently powerd is control the backlight on/off, and indicator-power
  is control how bright is should be.

  The backlight brightness level should be consistent within those two
  process. (Currently not)

  To reproduce:

  On n4 with dev channl rel 194
  1. open power indicator (or app "System Settings", choose battery and set the brightness)
  2. set the brightness level to certain point (make it lower so that you can see it more clearly)
  3. press power button to lock the device
  4. press power button to unlock the device

  Expected result:
  Brightness level is the one we set in the indicator

  Current result:
  Brightness level is always in a value that's relative high.

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