Proximity sensor stops reporting events on arale
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Confirmed
|
High
|
John McAleely | ||
| arale |
New
|
Undecided
|
Unassigned | ||
Bug Description
While using a recent rc-proposed image for arale (r243 from Feb 09 2015) I noticed that if proximity handling is turned on while the sensor is covered (i.e. the initial state is "near"), then only a single, initial "near" event is emitted and then proximity events stop.
Steps to reproduce:
1. Cover proximity sensor
2. Receive phone call or SMS, wait for notification
3. Uncover proximity sensor
Expected: Screen turns on
Actual: Nothing happens, screen stays off
Investigation indicates that the issue is caused by a level lower than USC/powerd, since the behavior can be reproduced by using just platform-api code (e.g., build and run examples/
The behavior seems to be specific to arale, I am not able to reproduce on krillin.
| description: | updated |
| Jean-Baptiste Lallement (jibel) wrote | #1 |
| Changed in canonical-devices-system-image: | |
| status: | New → Incomplete |
| Alexandros Frantzis (afrantzis) wrote | #2 |
| tags: | added: display-control |
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → kevin gunn (kgunn72) |
| Changed in canonical-devices-system-image: | |
| status: | Incomplete → New |
| assignee: | kevin gunn (kgunn72) → John McAleely (john.mcaleely) |
| importance: | Undecided → High |
| Changed in canonical-devices-system-image: | |
| status: | New → Confirmed |
Thanks for your report.
I cannot reproduce this issue with the steps in the description.
Is there anything specific about the initial state of the device?
For example, was it suspended or not, plugged or not, to a wall socket or USB, was the dialler started in background or not running when you received the call, did you turn the screen off with the power button or let it time out, did you previously receive another call or notification, can you reproduce immediately after a reboot, ... ?
Thanks.