Closed Bug 1000523 Opened 12 years ago Closed 12 years ago

[B2G][Open_C]When in a phone call, the proximity sensor does not turn off the screen

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
1.4 S6 (25apr)

People

(Reporter: astole, Assigned: timdream)

References

Details

Attachments

(2 files, 1 obsolete file)

Attached file logcat
When in a phone call, the proximity sensor doesn't activate and the screen stays on even when the phone is held up to the user's ear Repro Steps: 1) Update a Open_C to BuildID: 20140423040203 2) Open the dialer app 3) Make a phone call and cover the proximity sensor Actual: The proximity sensor does not disable the screen Expected: The proximity sensor should disable the screen 2.0 Environmental Variables: Device: Open_C 2.0 BuildID: 20140423040203 Gaia: d8904c5af6152f5d647a93a0c31227171ddecd87 Gecko: ac376a4e8174 Version: 31.0a1 Firmware Version: P821A10-ENG_20140410 Repro frequency: 3/3, 100% See attached: logcat, video
Does this happen on a 1.3 Open C base image?
Keywords: qawanted
I checked this issue. This issue is reproduced in master and v1.3 branch
reproduction steps: Step 1: User dials a number -> Proximity sensor is not working Step 2: User presses Send -> Proximity sensor is not working Step 3: Phone is trying to connect the call -> Proximity sensor is not working Step 4: Call is connected -> Proximity sensor starts working If the user put the phone in his/her face before Step 4, the screen is not turn off.
The p-sensor seems to only start 'detect change' after the call has been connected. So if the p-sensor is covered before the call is connected, even after it is connected the screen stays on and may lead to unwanted input.
Flags: needinfo?(timdream)
Component: Vendcom → Gaia::System
Flags: needinfo?(timdream)
Comment on attachment 8411694 [details] [review] mozilla-b2g:master PR#18633 According to Hsinyi, the step 2 described above should be "dialing". Including that in the list of |statechange| event handling should solve the issue when the user put the phone near their face before the phone is "alerting" (when the ringing tone is heard). Note that we are given a |userproximity| event in Gaia but not a DOM property, so will not be able to detect user's face any time before "dialing" (i.e. before user hitting the green button). If we want to keep the sensor on on all times it will drain the battery. We should consider simplifying screen_manager.js and move the logic to somewhere like call screen, if possible.
Attachment #8411694 - Flags: review?(21)
Status: NEW → ASSIGNED
Comment on attachment 8411694 [details] [review] mozilla-b2g:master PR#18633 Looks good to me.
Attachment #8411694 - Flags: review?(21) → review+
Assignee: nobody → timdream
Keywords: qawanted
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.4 S6 (25apr)
Attachment #8660768 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: