Closed
Bug 961154
Opened 12 years ago
Closed 11 years ago
When a second incoming call occurs, it does not turn the screen on
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(b2g-v1.3 affected, b2g-v1.4 affected)
RESOLVED
FIXED
2.0 S6 (18july)
People
(Reporter: selkabule, Assigned: rik)
References
Details
(Whiteboard: permafail [planned-sprint])
Attachments
(3 files)
Description:
When the user is on an active call and opens the speaker and wait for the screen to go to sleep, make a call with a third device to the test device. The screen doesn't automatically turn on informing the user there’s a second call
Repro Steps:
1) Updated Buri 1.3 Moz Ril
2) Make a Call from another device to DUT
3) Answer the call and open the speaker
4) Let the device screen go to sleep
5) From a third device make a call to a DUT
Actual:
There is no visual indication that there’s an incoming call
Expected:
The screen should automatically turn on, to inform the user for an incoming call
Environmental Variables
Device: buri 1.3 Moz Ril
Build ID: 20140117004005
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/2c033140eff4
Gaia: a81ccdc53e45a6adeaae423e104e91bcc1e12b0e
Platform Version: 28.0a2
Device firmware version: V1.2-device.cfg
Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/8489/
See attached: Logcat
Reporter | ||
Comment 1•12 years ago
|
||
This issue was Verified fix On bug#915071 But issue still reproduces on buri 1.2
1.2
Environmental VariablesDevice:
Build ID: 20140114004002
Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/42a1c35fc831
Gaia: 539a25e1887b902b8b25038c547048e691bd97f6
Platform Version: 26.0
Device firmware version: V1.2-device.cfg
Comment 2•12 years ago
|
||
Does this reproduce on a Leo 1.3 build? Trying to isolate if this is a device-specific bug.
Keywords: qawanted
Reporter | ||
Comment 3•12 years ago
|
||
This issue reproduces on Leo 1.3
Environmental Variables
Device: Leo 1.3 moz ril
Build ID: 20131120062258
Gecko: http://hg.mozilla.org/mozilla-central/rev/597287004ff5
Gaia: c26480b22ce28c812c347290dd4bad090d83db6f
Platform Version: 28.0a1
Firmware Version: v10d
There is no visual indication that there’s an incoming call
Comment 4•12 years ago
|
||
Okay - does this reproduce on 1.1?
Reporter | ||
Comment 5•12 years ago
|
||
This issue reproduces on both Leo1.1 and buri1.1
1.1
Environmental Variables
Device: buri 1.1 moz ril
Build ID: 20140115041456
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/0a2e7ed17611
Gaia: 6ff3a607f873320d00cb036fa76117f6fadd010f
Platform Version: 18.1
Firmware Version: v1.2-device.cfg
Leo 1.1
Environmental Variables
Device: Leo 1.1 moz ril
Build ID: 20131218041200
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/bdac595a4e46
Gaia: 6ff3a607f873320d00cb036fa76117f6fadd010f
Platform Version: 18.1
Firmware Version: v10d
Updated•11 years ago
|
Whiteboard: burirun1.3-2 → burirun1.3-2, burirun1.3-3
Updated•11 years ago
|
Whiteboard: burirun1.3-2, burirun1.3-3 → burirun1.3-2, burirun1.3-3, burirun1.4-1
Updated•11 years ago
|
Whiteboard: burirun1.3-2, burirun1.3-3, burirun1.4-1 → permafail
Updated•11 years ago
|
status-b2g-v1.4:
--- → affected
Assignee | ||
Comment 8•11 years ago
|
||
This has (at least) two duplicates, the last one being opened during Flame test run. Let's fix it!
Assignee: nobody → anthony
Target Milestone: --- → 2.0 S6 (18july)
Assignee | ||
Updated•11 years ago
|
Whiteboard: permafail → permafail [planned-sprint]
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•11 years ago
|
Summary: [B2G][Dialer] When a second incoming call occurs, it does not turn the screen on → When a second incoming call occurs, it does not turn the screen on
Assignee | ||
Comment 9•11 years ago
|
||
Attachment #8458812 -
Flags: review?(drs+bugzilla)
Assignee | ||
Comment 10•11 years ago
|
||
I tried to factor the screen management suites but couldn't get it to work. If you have a way to do so, I'll happily do it.
Comment 11•11 years ago
|
||
LGTM. I attached a patch that does this refactor, but it's incomplete and causes conflicts in names, such as "mockCall" in different scopes, so you might want to fix that and re-request review.
Comment 12•11 years ago
|
||
Comment on attachment 8458812 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/21939
Clearing review until the refactor is done. If you don't like the way I did it, feel free to re-request with the PR as-is.
Attachment #8458812 -
Flags: review?(drs+bugzilla)
Assignee | ||
Comment 13•11 years ago
|
||
Comment on attachment 8458812 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/21939
Thanks for giving it a try. I took a look at it and renaming extraCall to mockCall makes the tests less readable imho. I'd like to go with something DRY but it has to stay readable. Julien proposed to pass a function that returns the call under test but that also feels more boilerplate than necessary for tests.
Attachment #8458812 -
Flags: review?(drs+bugzilla)
Updated•11 years ago
|
Attachment #8458812 -
Flags: review?(drs+bugzilla) → review+
Assignee | ||
Comment 14•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Removing the affected flag for 2.1 as this was closed a long time ago. Another bug should be opened if this issue is occuring again.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
status-b2g-v2.1:
affected → ---
Flags: needinfo?(dharris)
You need to log in
before you can comment on or make changes to this bug.
Description
•