[B2G][Window Mgmt]Opening an app then covering and uncovering the proximity sensor when in a call leads back to call screen

RESOLVED WONTFIX

Status

Firefox OS
Vendcom
RESOLVED WONTFIX
4 years ago
4 months ago

People

(Reporter: astole, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)

Details

(Whiteboard: [2.0-flame-test-run-2], URL)

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8442906 [details]
logcat

If a call is made then, while in the call, an app is opened, covering and uncovering the proximity sensor opens the call screen instead of the app. Also, covering and unconvering the proximity sensor while in the Camera or Gallery app during a call causes the status bar to disappear.

Repro Steps:
1) Update a Flame to BuildID: 20140618000203
2) Make or receive a call
3) Press the home button
4) Open an app (Camera app used in ex.)
5) Cover then uncover the proximity sensor

Actual:
The call screen is displayed

Expected:
The opened app from step 4 is displayed

2.0 Environmental Variables:
Device: Flame 2.0
BuildID: 20140618000202
Gaia: 83844c7679b3b9f6e7f1116c1eeec2d1e7a64eec
Gecko: 55679dc2e72b
Version: 32.0a2
Firmware Version: v121-2

Repro frequency: 100%
See attached: logcat, video
This issue DOES reproduce on Flame 2.1, Flame 1.4, Flame base v121-2, Flame base v10G-2, Flame Pre-Base v10f-3

After opening an app while in a call, then covering and uncovering the proximity sensor will cause the phone to display the call screen

Flame 2.1

Environmental Variables:
Device: Flame Master
Build ID: 20140618040513
Gaia: 431aed0a7c7560c6eacd35ea69aa0a7a4ebe72c7
Gecko: 37f08ddaea48
Version: 33.0a1 (Master) 
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Flame 1.4

Environmental Variables:
Device: Flame 1.4
Build ID: 20140618000203
Gaia: 3bdd037ec1a11abebe16a5d7f6ff0d863e80bc07
Gecko: 523491fa3339
Version: 30.0 (1.4) 
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0


Flame Base v121-2

Environmental Variables:
Device: Flame 1.3
Build ID: 20140610200025
Gaia: e106a3f4a14eb8d4e10348efac7ae6dea2c24657
Gecko: b637b0677e15318dcce703f0358b397e09b018af
Version: 28.0 (1.3) 
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0


Flame Base v10G-2

1.3 Environmental Variables:
Device: Flame 1.3
BuildID: 20140520094859
Gaia: a73235d23685e9898f40647cebd83b3fcbfd0117
Gecko: Unknown
Version: 28.0
Firmware Version: v10G-2
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0


Flame Pre-Base v10f-3

Environmental Variables:
Device: Flame 1.3
Build ID: 20140505215459
Gaia: ec462dc62979dae593b4ad96ac3851ccbafe1813
Gecko: b637b0677e15318dcce703f0358b397e09b018af
Version: 28.0 (1.3) 
Firmware Version: v10F-3
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0

_________________________________________________________________________________________

This issue does NOT reproduce on Buri 2.1, Buri 2.0, or Buri 1.4

After opening an app while in a call, then covering and uncovering the proximity sensor will cause the phone to properly display the last app opened

Buri 2.1

Environmental Variables:
Device: Buri Master
Build ID: 20140618073003
Gaia: 336c30b6147cdd9122ad0b2bbffb81eb869a9ec2
Gecko: 1cea544c74c5
Version: 33.0a1 (Master) MOZ
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Buri 2.0

Environmental Variables:
Device: Buri 2.0
Build ID: 20140618063014
Gaia: 83844c7679b3b9f6e7f1116c1eeec2d1e7a64eec
Gecko: 883d156210cf
Version: 32.0a2 (2.0) MOZ
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Buri 1.4

Environmental Variables:
Device: Buri 1.4
Build ID: 20140618063004
Gaia: fc74015d26bcbc3e31a45d34cb65777112a35982
Gecko: fab72d8aa2e0
Version: 30.0 (1.4) MOZ
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
____________________________________________________________________________________

This issue does NOT reproduce on Open C 2.1, Open C 2.0, or Open C 1.4

There is no proximity sensor available on the Open C

Open_C 2.1

Environmental Variables:
Device: Open_C Master
Build ID: 20140618040513
Gaia: 431aed0a7c7560c6eacd35ea69aa0a7a4ebe72c7
Gecko: 37f08ddaea48
Version: 33.0a1 (Master) 
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Open_C 2.0

Environmental Variables:
Device: Open_C 2.0
Build ID: 20140618000202
Gaia: 83844c7679b3b9f6e7f1116c1eeec2d1e7a64eec
Gecko: 55679dc2e72b
Version: 32.0a2 (2.0) 
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Open_C 1.4

Environmental Variables:
Device: Open_C 1.4
Build ID: 20140618000203
Gaia: 3bdd037ec1a11abebe16a5d7f6ff0d863e80bc07
Gecko: 523491fa3339
Version: 30.0 (1.4) 
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v1.4: --- → affected
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
Flags: needinfo?(ktucker)
The Flame 2.0 is missing the User Agent and I need a video attached to this issue.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(dharris)
(Reporter)

Comment 3

4 years ago
Providing video and user agent per needinfo so clearing needinfo for dharris.

Flame 2.0 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Flags: needinfo?(dharris) → needinfo?(ktucker)
This appears to be a base image issue. Francis lee can you look into this issue please?
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage+]
Component: Gaia::System::Window Mgmt → Vendcom
Flags: needinfo?(ktucker) → needinfo?(frlee)

Updated

4 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]

Comment 5

4 years ago
hi All,

would it be possible that you can try base image v122 and see if this issue can be reproduced?
https://intranet.mozilla.org/QA/B2G_Tips_and_Tricks#Flashing_Base_Build_Image
Flags: needinfo?(frlee)
QA Wanted for comment 5.
QA Whiteboard: [QAnalyst-Triage+][lead-review+]
Keywords: qawanted
This issue reproduces on Flame 2.1 (base v122), and Flame 1.3 (base v122).

Base image: Flame 1.3
Build ID: 20140616171114
Gaia: e1b7152715072d27e0880cdc6b637f82fa42bf4e
Gecko: e181a36ebafaa24e5390db9f597313406edfc794
Version: 28.0 (1.3)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0

Flame Master
Build ID: 20140630040201
Gaia: de14e61098b742251b34f856e48649db8bed552c
Gecko: b6408c32a170
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Actual Results:
Issue reproduces as described above. Phone returns to "in a call" screen when an app is opened and the user covers/uncovers the proximity sensor.
QA Whiteboard: [QAnalyst-Triage?]
Keywords: qawanted
Make sure to needinfo your lead when marking a bug with triage?
Flags: needinfo?(ekramer)
Tagging jmitchell@qanalydocs.com needinfo.
Flags: needinfo?(ekramer) → needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)

Updated

4 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]

Comment 10

4 months ago
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.