touch-packages team mailing list archive

[Launchpad Bug Tracker <1384396@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

During a call, the screen gets stuck "off" if the user gets near the
proximity sensor within about 1/8th second of enabling the loudspeaker
function.

This seems fairly unlikely to happen during regular use, but it's
probably worth fixing anyway.  I'd suggest medium or low bug priority.

Steps to reproduce the issue:
1. Start a call.
2. Ensure the front of the phone isn't near anything.
3. Tap the loudspeaker icon at the same time as waving a hand over the proximity sensor.

Expected result: One function or the other should activate, but not
both.  Either enable the loudspeaker and keep the screen on, or turn the
screen off without the loudspeaker.

Actual result: Loudspeaker turns on and the screen turns off, then the
screen gets stuck off and doesn't respond to proximity or touches.
However, this can be recovered by pressing the power button (screen will
turn back on without triggering the welcome/unlock screens, regardless
of how long it has been off).

** Affects: dialer-app (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: rtm14 ue
-- 
race condition between loudspeaker and proximity sensor
https://bugs.launchpad.net/bugs/1384396
You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu.