Proximity sensor kept active after call ended

Bug #1518385 reported by Víctor R. Ruiz
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
kevin gunn
powerd (Ubuntu)
Confirmed
High
Alexandros Frantzis

Bug Description

Test case.
- Open the dialer app.
- Make a call.
- Accept the call in the receiver phone.
- Leave the phone for a minute.
- Finish the call on the receiver phone.

Expected result.
- Leaving the phone for a minute must not dim the screen.
- After the call is finished, the proximity sensor must be deactivated.

Actual result.
- After a minute the screen dims.
- After the call is finished, the proximity sensor is active.

current build number: 27
device name: krillin
channel: ubuntu-touch/stable/bq-aquaris.en

Víctor R. Ruiz (vrruiz)
description: updated
description: updated
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

confirmed with krillin rc-proposed 184

Changed in canonical-devices-system-image:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → kevin gunn (kgunn72)
milestone: none → ww02-2016
Revision history for this message
kevin gunn (kgunn72) wrote :

this feels very similar to recent bug about flashing during a phone call

no longer affects: unity8 (Ubuntu)
Changed in powerd (Ubuntu):
assignee: nobody → Alexandros Frantzis (afrantzis)
importance: Undecided → High
Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

This is different from bug #1531158 and it describes two different behaviors.

> Expected - Leaving the phone for a minute must not dim the screen.
> Actual - After a minute the screen dims.

(I am assuming this is referring to the case when a call is active)

USC/Powerd currently implement the behavior as stated in the requirements doc [1]. In particular, the use case: "answer call, let the inactivity timer of 60secs turn off screen [YES] proximity cover/uncover should turn on the screen [YES]".

> Expected - After the call is finished, the proximity sensor must be deactivated.
> Actual - After the call is finished, the proximity sensor is active.

This is a known issue. There are some technical/architectural issues that have stopped us from providing a better behavior. Currently, ending a call is treated (almost) like a notification arrival, which enables proximity, turns on the screen (if screen is not covered) and enables a short inactivity timeout (15s).

[1] https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in powerd (Ubuntu):
status: New → Confirmed
Changed in canonical-devices-system-image:
milestone: ww02-2016 → ww08-2016
kevin gunn (kgunn72)
Changed in canonical-devices-system-image:
milestone: ww08-2016 → backlog
tags: added: display-control
Revision history for this message
kevin gunn (kgunn72) wrote :

@alf - should this be covered under ota12 with the repowerd release?

Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

> @alf - should this be covered under ota12 with the repowerd release?

Repowerd properly implements "After the call is finished, the proximity sensor must be deactivated.", so yes.

However, repowerd does not implement "Leaving the phone for a minute must not dim the screen.", since it contradicts the policy document, as noted in a previous comment.

kevin gunn (kgunn72)
Changed in canonical-devices-system-image:
milestone: backlog → 12
Changed in canonical-devices-system-image:
milestone: 12 → 13
Changed in canonical-devices-system-image:
status: Confirmed → Fix Committed
Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.