Closed
Bug 1111880
Opened 11 years ago
Closed 11 years ago
[Call home screen]When in a call tapping going to home screen then card view causes home screen to black out for up to 10 seconds
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(b2g-v2.0 unaffected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | affected |
b2g-v2.2 | --- | affected |
People
(Reporter: rmitchell, Unassigned)
References
()
Details
(Whiteboard: [2.2-exploratory-2])
Attachments
(1 file)
104.96 KB,
text/plain
|
Details |
Description:
When in a call tapping going to home screen then card view closing apps or if blank swiping on the empty screen can causes home screen to black out for up to 10 seconds
Repro Steps:
1) Update a Flame to 20141215040201
2) Make a call > after call connects tap the home button
3) Hold home button for card view > close out all open apps
4) Tap the top of the screen, if screen does not go black pull down notification menu
5) With menu on screen hold home button > swipe card view > on hope screen tap top of screen again
note: if steps are not yielding result let phone set on home screen for a few moments (5-10 seconds)
Actual:
(Describe the behavior you actually observed)
Expected:
(Describe the behavior you expected to have observed)
Environmental Variables:
Device: Flame 2.2 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141215040201
Gaia: e2a3e606675c346b6e6f35351a458040be599b09
Gecko: f14dcd1c8c0b
Gonk: 263b5f41f7733c5577fb101eb4dc8ac5c11cfa8d
Version: 37.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Repro frequency:3/5
See attached:logcat, video clip:https://www.youtube.com/watch?v=jy7cPENQpCs
Flags: needinfo?(dharris)
Actual:
Screen goes black for 5-10 seconds
Expected:
Screen stays with no black screen
Issue was affected in 2.1 flame
bytes remaining is accurate
Flame 2.1
Environmental Variables:
Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141215001202
Gaia: 97873dca486abf4162a3345e71b375806937bdec
Gecko: ec87f4f41d3d
Gonk: 263b5f41f7733c5577fb101eb4dc8ac5c11cfa8d
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
issue is not affected in 2.0 flame
there is no way to access the notification tray in this version
Flame 2.0
Environmental Variables:
Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141212000203
Gaia: f3b9806f687fbbd7eba6b0e1f6ebb8bde09840ea
Gecko: 32f9fae79b89
Gonk: 263b5f41f7733c5577fb101eb4dc8ac5c11cfa8d
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Comment 2•11 years ago
|
||
I think this is by design. The issue here is that your middle finger gets in front of the proximity sensor (located 1/5 of an inch at the left of the front camera). Because of that and as you're in a call, the screen turns off.
I checked, we have the same behavior on a Buri with 1.4.
We might want to change the behavior, I needinfo Carrie to chime in.
Flags: needinfo?(cawang)
Keywords: qawanted
I agree that this looks like the proximity sensor is being triggered. Waiting on the NI from comment 2 before closing this bug.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Comment 4•11 years ago
|
||
Striking QA-Wanted tag because there is already a specific NI to the needed person.
Keywords: qawanted
Comment 5•11 years ago
|
||
Hi,
I think in this case it's the proximity sensor. However, I found that if user closes the APP in task manager, the call is still connected. I think this is the weird part. If the APP is killed, how come the call is still working?
Flags: needinfo?(cawang)
Comment 6•11 years ago
|
||
You're able to close the Dialer (called Phone) app but I don't think you're able to close the CallScreen app. You can get back to the callscreen by dragging down the notification panel. Do you think we should change that, Carrie?
Comment 7•11 years ago
|
||
Hi Johan,
I retried it on the device and found that the screenshot in the task manager is not the call screen. So it makes sense to keep the call connected in the notification. I think we are fine with the current behavior. Thanks!
Comment 8•11 years ago
|
||
Per comment 7.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•