Ubuntu Touch is no longer supported.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Won't Fix
--
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
** Tags added: bluez-touch
--
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:
Incomplete
Status in Mir:
Invalid
Just remembered that Mir actually doesn't control the backlight at all.
That's USC/repowerd communicating with the kernel.
** Changed in: mir
Status: New => Invalid
** Changed in: mir
Milestone: 0.25.0 => None
** Changed in: mir (Ubuntu)
Status: Confirmed => Invalid
--
You
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
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:
Incomplete
Case 1 has been resolved with recent sensor control fixes as far as I can tell.
Will mark incomplete to see if there are any lingering issues with update 12.
** Changed in: canonical-devices-system-image
Status: Confirmed => Incomplete
** Changed in: canonical-devices-system-image
The "home" button accidentally turning the screen on is confirmed in
this thread:
https://plus.google.com/u/0/108188125572924200710/posts/aBuWYcnSyQt?cfem=1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
On the MX4 specifically there is also the issue with the "home" button
staying active for about 30sec when the display was turned off, when
shoving the phone into your pocket it is easy to create a button press
event if you do not wait long enough.
--
You received this bug notification because
It could be useful to have these logs when it occurs
/var/log/syslog
/var/log/upstart/powerd.log
--
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
Aquaris M10, running first update after purchase. Screen comes on to
lock prompt, stays on and even pressing power button it goes off for 1
second then back on again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: mir
Milestone: 0.23.0 => 0.24.0
--
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
I can confirm that my Nexus 7 also awakens on its own for no apparent
reason.
Environment information
Ubuntu 15.04 (r425)
Nexus 7 (2013) flo
rc-proposed channel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mir (Ubuntu)
Status: New => Confirmed
--
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
** Changed in: canonical-devices-system-image
Assignee: Michał Sawicz (saviq) => Stephen M. Webb (bregma)
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Milestone: None =>
** Tags added: display-control
** Changed in: canonical-devices-system-image
Assignee: Pat McGowan (pat-mcgowan) => Michał Sawicz (saviq)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11
--
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
** Also affects: unity-system-compositor
Importance: Undecided
Status: New
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-system-compositor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
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
If 1) happens without keyboard or mouse attached that definitely counts
as a bug
As for proximity - the main issue is there's no API to query the current state
of the sensor (as Alexandros mentioned).
However done properly the power drain should be minimal as it should only be
turned on during
@kevin I agree with your comment in 7 that the policies should be
correct then we dont have the issue
--
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
** Description changed:
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
> 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.
There is a third, ideal way which would be to check the proximity value
just before
>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
When a keyboard connects, it doesn't turn on the display, the user needs to
type on a key
The headset may be turning on the display because the connection triggers the
volume slider OSD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
For case 1 I always back out of emergency calls or wherever it got to and
manually turn it off.
For case 2 yes it dims and turns off.
My hypothesis was that case 1 is caused by some variant of case 2 since
it seems to be a relatively new phenomenon and I can't think of anything
else that can
@pat - also does the screen dim/blank at after expected expiry in the case of
#1) ?
and second, same question in the case of #2) ?
--
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
26 matches
Mail list logo
