Closed
Bug 826175
Opened 13 years ago
Closed 11 years ago
[Dialer] Sometimes the call screen would not show for incoming call
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect, P1)
Tracking
(blocking-basecamp:-, b2g18+)
Tracking | Status | |
---|---|---|
b2g18 | + | --- |
People
(Reporter: shawnjohnjr, Assigned: rudyl)
Details
(Keywords: regression)
Reproduce steps:
1. Pair with Bluetooth headset
2. Make an incoming call via external line
3. Use Bluetooth headset to answer call
4. User cannot answer call via Bluetooth headset
Reporter | ||
Comment 1•13 years ago
|
||
We dumped that SystemMessageInternal.
We found bluetooth-dialer-cmmand {"command":"ATA"} indeed passed to dialer. But dialer does not process this message.
01-03 16:58:43.057 108 108 I Gecko : -- SystemMessageInternal 1357203523066 : Broadcasting bluetooth-dialer-command {"command":"ATA"}
01-03 16:58:43.067 108 108 I Gecko : -- SystemMessageInternal 1357203523071 : Asking to open {"uri":"app://communications.gaiamobile.org/dialer/index.html#keyboard-view","manifest":"app://communications.gaiamobile.org/manifest.webapp","type":"bluetooth-dialer-command"}
01-03 16:58:43.178 108 108 I Gecko : -- SystemMessageInternal 1357203523189 : received SystemMessageManager:Message:Return:OK bluetooth-dialer-command for app://communications.gaiamobile.org/dialer/index.html#keyboard-view @ app://communications.gaiamobile.org/manifest.webapp
Reporter | ||
Comment 2•13 years ago
|
||
We found this issue related to older version of
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•13 years ago
|
||
We found this issue resolved after commit 1d4957886c09d.
We don't know why it breaks.
commit 1d4957886c09d87416b653318d008000fd9a3e0a
Merge: c14a1e7 5d090cf
Author: Ryan VanderMeulen <ryanvm@gmail.com>
Date: Wed Jan 2 21:02:40 2013 -0500
Merge the last PGO-green inbound changeset to m-c.
Reporter | ||
Comment 4•13 years ago
|
||
Re-clarify:
It's related to gaia commit.
commit ea325f75486a636d851bd6181caf5f7fa2e25904
Merge: 2718ae8 e783142
Author: David Scravaglieri <dscravaglieri@mozilla.com>
Date: Thu Jan 3 00:09:00 2013 -0800
Merge pull request #7279 from dscravag/nightly2
Nightly 2013-01-03
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Reporter | ||
Updated•13 years ago
|
blocking-basecamp: --- → ?
Updated•13 years ago
|
blocking-basecamp: ? → +
Priority: -- → P1
Target Milestone: --- → B2G C4 (2jan on)
Updated•13 years ago
|
Assignee: nobody → ehung
Comment 5•13 years ago
|
||
(In reply to Shawn Huang from comment #4)
> Re-clarify:
> It's related to gaia commit.
> commit ea325f75486a636d851bd6181caf5f7fa2e25904
> Merge: 2718ae8 e783142
> Author: David Scravaglieri <dscravaglieri@mozilla.com>
> Date: Thu Jan 3 00:09:00 2013 -0800
>
> Merge pull request #7279 from dscravag/nightly2
>
> Nightly 2013-01-03
This shouldn't be the cause...it's nightly release commit.
Reporter | ||
Comment 6•13 years ago
|
||
Agreed with Alive. Another symptom is that in-call window does not show up. We still see window.open failed.
Comment 7•13 years ago
|
||
Rudy will help on this issue, he resolved a related issue before.
Assignee: ehung → rlu
Comment 8•13 years ago
|
||
I tried to reproduce this bug many times, but still not sure the root cause. However, it would be easier to reproduce it with the following steps:
1. Launch Dialer app.
2. Back to home screen
3. Launch another app, such as Settings app
4. Make a call from another phone
Expected behaviour:
Call screen is shown and can hear ring tone
Actual results:
Sometimes there're ring tones but no call screen, sometimes no ring tone and no call screen, and sometimes we can see call screen and hear ring tone.
Assignee | ||
Comment 9•12 years ago
|
||
I still cannot reproduce the "no call screen" issue.
Used pvt build 2013-01-06 for unagi
------------------------
https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi_betatest/2013/01/2013-01-06-23-02-04/
Will add "qawanted" for more help.
Dear QAs,
Please note that we encountered a call screen issue, as Comment 8 by Gina, we might need your help to reproduce it.
Keywords: qawanted
Assignee | ||
Comment 10•12 years ago
|
||
Change the summary for now to let us focus on call screen issue first and then the BT related issues.
Summary: [Dialer]Cannot answer phone call via Bluetooth Handsfree due to dialer does not respond to bluetooth-dialer-command "ATA" → [Dialer] Sometimes the call screen would not show for incoming call
Updated•12 years ago
|
QA Contact: mozillamarcia.knous
Comment 11•12 years ago
|
||
I can't reproduce it in pvt b2g18 build of 2013-1-7
can gina help with providing more device information
Flags: needinfo?(gyeh)
Comment 12•12 years ago
|
||
Got information from Gina Yeh.
This happened only in Mozilla Central v20 trunk.
This should not be bb+ now.
However, leave this for triage to decide.
blocking-basecamp: + → ?
Flags: needinfo?(gyeh)
Updated•12 years ago
|
Reporter | ||
Comment 13•12 years ago
|
||
Test with PTS HFP test case AG_ATA related test case, it still cannot pass. It looks like ATA command was been ignored to due to callScreen has not been loaded.
Reporter | ||
Comment 14•12 years ago
|
||
For specific Bluetooth case, see Bug 828118.
Assignee | ||
Comment 15•11 years ago
|
||
Close this old bug since we don't see this anymore.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•