kernel-packages team mailing list archive

[kevin gunn <kevin.gunn@xxxxxxxxxxxxx>]

>Fix 1: I think the policy for screen management is simple,
> never turn the display on if proximity is detected, it should 
> not be specific to SMS or calls.

So you are saying we should have the proximity sensor on all the time ?
I disagree, first that's a power drain. Second, people will complain about the screen blanking off just interacting with the device.
The right answer is to get the policy correct in the first place and filter the events properly into those that you want to turn on the display and those you don't.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552371

Title:
  Unexpected display on

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  NOTE: kgunn suggests this bug be about 1) not 2) here

  1)
  I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI
  I also see the tablet display turn on while lying idle on the desk.

  2)
  I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended.

  I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer.
  The proximity sensor is also not honored when this happens, if its covered the screen still comes on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions