** Changed in: ubuntu-ux
Status: New = Triaged
** Changed in: ubuntu-ux
Importance: Undecided = High
** Changed in: ubuntu-ux
Assignee: (unassigned) = Olga Kemmet (olga-kemmet)
** Summary changed:
- Screen and input should be disabled with proximity sensor when on greeter
+
Sounds like we need a design decision here.
a) do we keep the current design, where on alerts the proximity sensor is
covered we still light the screen ? or do we keep the screen blanked until the
sensor is uncovered ? (see bfiller's #1 above)
b) if we keep our current design around proximity
** Changed in: canonical-devices-system-image
Assignee: Bill Filler (bfiller) = kevin gunn (kgunn72)
** Changed in: canonical-devices-system-image
Milestone: ww13-2015 = ww17-2015
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: powerd (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
This is a severe issue in my case because:
* Phone is locked in pocket or purse
* Incoming call is not heard or lost
* SMS is sent to caller with default message (I'm busy, I'll call later)
In my case, SMS are expensive, and the people I communicate via
cellphone with do not speak in English, so
** Changed in: canonical-devices-system-image
Milestone: ww09-2015 = ww13-2015
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1291455
Title:
Screen and input should be
It is the opposite, powerd wakes the screen up [1] and telepathy-ofono
enable/disable the proximity sensor based on audio outputs [2] (speaker
mode must keep the screen on):
[1]
http://bazaar.launchpad.net/~phablet-team/powerd/trunk/view/head:/src/powerd.cpp#L257
[2]
IIRC it's telepathy-ofono that wakes the screen up for this still (I
know, not the greatest architecture...), and powerd/u-s-c are
responsible for actually turning it on and off based on proximity. So,
as long as the screen is kept on with proximity enabled by telepathy-
ofono, u-s-c and powerd
** Changed in: canonical-devices-system-image
Assignee: Kevin Gunn (kgunn) = Bill Filler (bfiller)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1291455
Title:
Although touch events really require a capacitive connection so in
pocket events unlikely
** Changed in: canonical-devices-system-image
Assignee: (unassigned) = Kevin Gunn (kgunn)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Another scenario is with incoming text messages. The screen turns on and
the greeter starts processing touch events in the pocket, of which
there will be many. This can lead to apps being launched. This may be a
trigger for the case where the edges no longer function when removing a
phone from
Bumping priority as I just experienced this several times
This could also result in the phone remaining unsuspended while
continuous touch events are being processed.
** Changed in: canonical-devices-system-image
Importance: Undecided = High
** Changed in: canonical-devices-system-image
** No longer affects: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1291455
Title:
Screen and input should be disabled with proximity sensor when on
13 matches
Mail list logo
