1240915 - [Aries-L] Proximity sensor does not turn off the display during a call.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Vendcom, defect)

Description

[Martin Shuman [:Marty]]

Attachment: logcat_lollipop-proximity-sensor.txt

Description:
The proximity sensor does not appear to be functioning on the Aries-L builds. When in a call, the display will not turn off, and touch input is still accepted when something should be blocking the proximity sensor during a call.

Repro Steps:
1) Update a Aries to 20160118142711
2) Make or receive a call with the DUT
3) Move something (Fingers, head, etc.) in front of the device to block the proximity sensor.

Actual:
The proximity sensor does not turn off the display and does not disable touch input.

Expected:
The proximity sensor turns off the display and disables touch input when in a call.

Environmental Variables:
Device: Aries-L 2.6 [Full Flash]
Build ID: 20160118142711
Gaia: 3fdecb198ed277770b765ad8be84f0ecf4a36a91
Gecko: cc15740ff7d4b73522cef4f171d2d7d3045b30f9
Version: 46.0a1 (2.6)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

Repro frequency: 10/10
See attached: Logcat, Video

Comment 1

[Martin Shuman [:Marty]]

This issue does NOT occur on the latest Aries Dogfood KitKat build
The proximity sensor turns off the display and disables touch input when in a call.

Environmental Variables:
Device: Aries 2.6
BuildID: 20160119110105
Gaia: 43852628a9d506c65525cceb5789b257cc939fe8
Gecko: b67316254602a63bf4e568198a5c7d3288a9db27
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 46.0a1 (2.6) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

Comment 2

[:gerard-majax]

I got confirmation that blobs needs an update (which will happen soon) to fix proximity sensor.

Comment 3

[:gerard-majax]

(In reply to Alexandre LISSY :gerard-majax from comment #2)
> I got confirmation that blobs needs an update (which will happen soon) to
> fix proximity sensor.

I was wrong. Turns out a simple stop/start sequence of sensorservice is enough. And that keeps the Camera happy (when sensorservice is not running, it often crashes, as reportd in bug 1239679).

Comment 4

[BMO Automation]

Firefox OS is not being worked on