Closed
Bug 872428
Opened 11 years ago
Closed 11 years ago
[Bluetooth][Certification]Audio path does not route to Bluetooth SCO
Categories
(Firefox OS Graveyard :: Bluetooth, defect)
Tracking
(blocking-b2g:tef+, firefox22 wontfix, firefox23 wontfix, firefox24 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)
RESOLVED
FIXED
blocking-b2g | tef+ |
People
(Reporter: shawnjohnjr, Assigned: shawnjohnjr)
References
Details
(Whiteboard: [target:5/15][fixed-in-birch] QARegressExclude)
Attachments
(3 files, 3 obsolete files)
1.16 KB,
patch
|
Details | Diff | Splinter Review | |
1.16 KB,
patch
|
Details | Diff | Splinter Review | |
1.16 KB,
patch
|
Details | Diff | Splinter Review |
While testing AG_ACS, we found audio path does not output to correct path in v1.0.1.
After patch of Bug 830213 applied, the code of audio path shall also be changed.
Assignee | ||
Updated•11 years ago
|
Severity: normal → blocker
Assignee | ||
Updated•11 years ago
|
Blocks: bt-certi-blocking
Assignee | ||
Updated•11 years ago
|
Whiteboard: [status:needs patch][target:5/15]
Assignee | ||
Updated•11 years ago
|
blocking-b2g: --- → tef?
Assignee | ||
Comment 1•11 years ago
|
||
This is must have patch, otherwise BT SCO audio path get screw up.
Attachment #749738 -
Flags: review?(rlin)
Attachment #749738 -
Flags: review?(mwu)
Assignee | ||
Updated•11 years ago
|
Whiteboard: [status:needs patch][target:5/15] → [status:needs review][target:5/15]
Comment 2•11 years ago
|
||
Comment on attachment 749738 [details] [diff] [review]
Patch1:V1 for b2g18-v101
Review of attachment 749738 [details] [diff] [review]:
-----------------------------------------------------------------
The patch looks to me. But needs mwu to give r+.
Attachment #749738 -
Flags: review?(rlin)
Assignee | ||
Comment 3•11 years ago
|
||
Attachment #749749 -
Flags: review?(mwu)
Assignee | ||
Comment 4•11 years ago
|
||
b2g18 version
Assignee | ||
Comment 5•11 years ago
|
||
For central, b2g18 patch, if aData is empty Bluetooth address, it shall do setForce to None. Without this, it can also cause serious audio path missing problem.
Updated•11 years ago
|
blocking-b2g: tef? → tef+
Assignee | ||
Comment 6•11 years ago
|
||
I've tested the following scenarios:
Scenario A:
1. Connected BT headset, during call session, turn off BT headset
2. Check audio path correctly switch back to earpiece
Scenario B:
1. Connected BT headset, during call session, switch to speaker, turn off BT headset
2. Check audio path correctly switch back to speaker
3. Switch to earpieces again and check audio path routed to earpieces
Scenario C:
1. Turn off Bt headset, make a phone call, during the call session, turn on BT headset
2. Check audio path correctly switch back to BT headset
3. Switch to speaker again check path to speaker
blocking-b2g: tef+ → tef?
Assignee | ||
Comment 7•11 years ago
|
||
Sorry, update comment but touch blocking-b2g:tef+.
Comment 9•11 years ago
|
||
Comment on attachment 749749 [details] [diff] [review]
Patch1:V1 for central,
Review of attachment 749749 [details] [diff] [review]:
-----------------------------------------------------------------
::: dom/system/gonk/AudioManager.cpp
@@ +144,5 @@
> const char* aTopic,
> const PRUnichar* aData)
> {
> if (!strcmp(aTopic, BLUETOOTH_SCO_STATUS_CHANGED)) {
> + if (NS_strlen(aData) > 0) {
Testing for *aData would be the fastest way, though perhaps not the most obvious.
Attachment #749749 -
Flags: review?(mwu) → review+
Comment 10•11 years ago
|
||
Comment on attachment 749738 [details] [diff] [review]
Patch1:V1 for b2g18-v101
This looks identical to the m-c patch + bug 862306. I'm going to request tef+ for bug 862306 so you can uplift that.
Attachment #749738 -
Flags: review?(mwu)
Updated•11 years ago
|
Whiteboard: [status:needs review][target:5/15] → [status:needs landing][target:5/15]
Assignee | ||
Updated•11 years ago
|
Attachment #749749 -
Attachment is obsolete: true
Assignee | ||
Updated•11 years ago
|
Attachment #749758 -
Attachment is obsolete: true
Assignee | ||
Updated•11 years ago
|
Attachment #749749 -
Attachment description: Patch1:V1 for central → Patch1:V1 for central,
Assignee | ||
Updated•11 years ago
|
Attachment #749738 -
Attachment is obsolete: true
Assignee | ||
Comment 11•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #750247 -
Attachment description: Bug 872428 - Fix missing setForceUse to BT SCO for audio path, r=mwu, a=tef+ → b2g18-v101:Bug 872428 - Fix missing setForceUse to BT SCO for audio path, r=mwu, a=tef+
Assignee | ||
Comment 12•11 years ago
|
||
Assignee | ||
Comment 13•11 years ago
|
||
Assignee | ||
Comment 14•11 years ago
|
||
Note: b2g18v101 patch depend on bug 862306. So bug 862306 needs to uplift first.
Comment 15•11 years ago
|
||
Whiteboard: [status:needs landing][target:5/15] → [status:needs landing][target:5/15][fixed-in-birch]
Comment 16•11 years ago
|
||
(In reply to Shawn Huang from comment #14)
> Note: b2g18v101 patch depend on bug 862306. So bug 862306 needs to uplift
> first.
bug 862306 has been landed.
Comment 18•11 years ago
|
||
(In reply to Shawn Huang from comment #17)
> Hello Ryan, can you help to uplift?
As usual, once birch is merged to m-c next, I'll take care of the uplift, yes.
Flags: needinfo?(ryanvm)
Comment 19•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
status-b2g18:
--- → affected
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → affected
status-firefox22:
--- → wontfix
status-firefox23:
--- → wontfix
status-firefox24:
--- → fixed
Resolution: --- → FIXED
Whiteboard: [status:needs landing][target:5/15][fixed-in-birch] → [status:needs uplift][target:5/15][fixed-in-birch]
Comment 20•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/5001c6dc28c9
https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/f1c7ac4070e2
Whiteboard: [status:needs uplift][target:5/15][fixed-in-birch] → [target:5/15][fixed-in-birch]
Comment 21•11 years ago
|
||
Unable to verify. Lack of resources. Need Bluetooth PTS tool to verify.
Marking as QARegressExclude.
Whiteboard: [target:5/15][fixed-in-birch] → [target:5/15][fixed-in-birch] QARegressExclude
You need to log in
before you can comment on or make changes to this bug.
Description
•