Proximity sensor is used before incoming call is answered
Bug #1189945 reported by
Seth Forshee
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
powerd |
Fix Released
|
Medium
|
Matt Fischer |
Bug Description
When we have an incoming call powerd enables the proximity sensor before the call has been answered. As a result the screen might turn off when a hand is placed near the screen for the purpose of tapping the "answer call" button. We need to figure out how to determine from ofono that we actually have an active call (not just an incoming call that hasn't been accepted) and wait to turn on the proximity sensor until that happens.
Changed in powerd: | |
assignee: | nobody → Matthew Fischer (mfisch) |
status: | New → In Progress |
Changed in powerd: | |
assignee: | Matthew Fischer (mfisch) → nobody |
status: | In Progress → Triaged |
Changed in powerd: | |
assignee: | nobody → Matthew Fischer (mfisch) |
status: | Triaged → In Progress |
status: | In Progress → Triaged |
status: | Triaged → Fix Released |
To post a comment you must log in.
<awe> there's no direct signal
<awe> however if you monitor the call list
<awe> I think the data you need is conveyed in the Call properties
<sforshee> awe, so we'd have to poll it?
<awe> you'd need to monitor the call list, and once you have an associated call ID, you can monitor signals everytime the properties for that Call change
<awe> sforshee, I haven't looked at it too closely, you may be able to monitor the call list in a similar manner
<awe> so step 1 is figure out if a call has been created
<awe> and step 2 is watch for PropertyChanged events for any calls and if the status is active, you have an active call