Proximity sensor stops reporting events on arale

Bug #1543948 reported by Alexandros Frantzis on 2016-02-10
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical System Image
High
John McAleely
arale
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/test_sensors_api.cpp in platform-api source tree).

The behavior seems to be specific to arale, I am not able to reproduce on krillin.

description: updated
Jean-Baptiste Lallement (jibel) wrote :

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.

Changed in canonical-devices-system-image:
status: New → Incomplete
Alexandros Frantzis (afrantzis) wrote :

> 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, ... ?

I can reproduce this 100% deterministically, regardless of device state (I have tried various combinations you mention).

Note, that as I mentioned in the description, I can reproduce this just by using the platform-api example directly, after having stopped everything Unity/Mir/Powerd related.

tags: added: display-control
Changed in canonical-devices-system-image:
assignee: nobody → kevin gunn (kgunn72)
kevin gunn (kgunn72) on 2016-05-31
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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers