Closed Bug 1065177 Opened 10 years ago Closed 6 years ago

[Dialer] Receiving another incoming call while already in a call does not wake the screen from sleep mode

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

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

RESOLVED WONTFIX
Tracking Status
b2g-v1.4 --- affected
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected
b2g-v2.5 --- affected

People

(Reporter: rpribble, Unassigned)

References

()

Details

(Whiteboard: [2.1-flame-test-run-2][2.1-flame-test-run-3][2.5-aries-test-run-4])

Attachments

(3 files)

Description:
If the DUT is in a call on speaker and the screen is asleep, then receives another incoming call, the screen will remain asleep and will not wake up and the user. A beep alert will be heard, but if the user misses the beep, the screen remains dark and they will not be visually alerted.

Repro Steps:
1) Update a Flame device to BuildID: 20140908000204
2) Call the DUT from another device
3) Answer the call and set the DUT to speaker, and wait for the screen to sleep
4) Call the DUT from a third device
5) Observe beeps but screen remain dark
  
Actual:
Screen remains asleep when getting an incoming call while already in a call.

Expected: 
Screen wakes and visually alerts user as well as audibly.
  
Environmental Variables:
Device: Flame 2.1 (319MB)
BuildID: 20140908000204
Gaia: a8e4d26555e5713ec6c72270cfd0cfabc096a0d3
Gecko: 746f24f9d21d
Version: 34.0a2 (2.1)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
  
Notes:
  
Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/8489/
See attached: Video, logcat
Setting qawanted for branch checks, or I wll do them and capture a video in the morning.
Keywords: qawanted
We added this in bug 961154.
Keywords: qawanted
This issue also occurs on the Flame v2.2, Flame v2.0, Flame v1.4, and Open_C v2.2.

Device: Flame Master (319mb)
BuildID: 20140910040203
Gaia: 8e02f689b0fc39cb6ccdc22d02ed7e219c58faa7
Gecko: 152ef25e89ae
Version: 35.0a1 (Master)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Device: Flame 2.0 (319mb)
BuildID: 20140910000203
Gaia: 3f4c635106c5364228782d12b1cb76b0c105b971
Gecko: 02a5b9234c13
Version: 32.0 (2.0)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Device: Flame 1.4
BuildID: 20140908000203
Gaia: 2ee5b00bfbb8a67a967094804390b4afce8ecf54
Gecko: a3e8df746cd8
Version: 30.0 (1.4)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Device: Open_C Master
BuildID: 20140910040203
Gaia: 8e02f689b0fc39cb6ccdc22d02ed7e219c58faa7
Gecko: 152ef25e89ae
Version: 35.0a1 (Master)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Screen remains asleep when getting an incoming call while already in a call.
No beep alert is heard on v1.4.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
Attached file Logcat.txt
Not blocking on this bug, the phone call can be answered and does not ruin anything with the current phone call. Just a minor visual recognition bug
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
We'd still like to take a look at this since it should work.
So apparently I was confused and we need the system app to turn the screen on. The callscreen app can't do that on its own.

So the real fix would be similar to bug 1024341.
See Also: → 1024341
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(dharris)
Whiteboard: [2.1-flame-test-run-2] → [2.1-flame-test-run-2][2.1-flame-test-run-3]
Updating tracking flag based on comment 3
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
I can repro this bug on latest Flame v2.5 and Aries KK v2.5.
STR:
Same STR and actual result as comment 0.
Repro rate: 10/10.
See video:"Aries_v2.5.3gp"
See log:"logcat_1123.txt"
Found Time: 11:23

Device Info:
Flame v2.5(affected):
Build ID               20151123163948
Gaia Revision          5839f17dedc757947c9531dc0d66c3c49119f5ea
Gaia Date              2015-11-20 22:47:58
Gecko Revision         http://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/3a45ca93dd447e046baa2c7590f60ae008e438f8
Gecko Version          44.0a2
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.worker.20151123.155405
Firmware Date          Mon Nov 23 15:54:14 UTC 2015
Firmware Version       v18D v4
Bootloader             L1TC000118D0

Aries KK v2.5(affected):
Build ID               20151123164502
Gaia Revision          5839f17dedc757947c9531dc0d66c3c49119f5ea
Gaia Date              2015-11-20 22:47:58
Gecko Revision         http://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/3a45ca93dd447e046baa2c7590f60ae008e438f8
Gecko Version          44.0a2
Device Name            aries
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.worker.20151123.155500
Firmware Date          Mon Nov 23 15:55:07 UTC 2015
Bootloader             s1
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage+][lead-review+][MGSEI-Triage+]
Whiteboard: [2.1-flame-test-run-2][2.1-flame-test-run-3] → [2.1-flame-test-run-2][2.1-flame-test-run-3][2.5-aries-test-run-4]
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: