Closed Bug 1036402 Opened 10 years ago Closed 10 years ago

During voice call with BTSCO connected, switch to Receiver/speaker, then volume change is not working

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.0+, b2g-v1.4 affected, b2g-v2.0 fixed, b2g-v2.1 fixed)

RESOLVED FIXED
2.0 S6 (18july)
blocking-b2g 2.0+
Tracking Status
b2g-v1.4 --- affected
b2g-v2.0 --- fixed
b2g-v2.1 --- fixed

People

(Reporter: vasanth, Assigned: dkuo)

References

()

Details

(Whiteboard: [caf priority: p2][CR 691045])

Attachments

(1 file)

(deleted), text/x-github-pull-request
alive
: review+
Details
Steps to Reproduce:
------------------
1. Connect and pair BTSCO device
2. Make MO voice call
3. Through call screen UI, switch from BTSCO to Receiver/speaker.
4. Try to change volume and observe volume didn't change in Receiver/speaker.
5. Seems BTSCO volume gets changed wrongly even though we switched to Receiver/Speaker 
(UI shows 16 range BTSCO volume bar used during #4 but UI would only show 6 range volume bar for Receiver/speaker)
Component: Gaia::System → Bluetooth
Component: Bluetooth → Gaia::System
QA Wanted for branch checks.
Keywords: qawanted
Tim, can your team take a look here? I don't think we have a BT setup in SF.
Flags: needinfo?(timdream)
Whiteboard: [CR 691045] → [caf priority: p2][CR 691045]
QA Contact: rkunkel
(In reply to Jason Smith [:jsmith] from comment #1)
> QA Wanted for branch checks.

This issue DOES reproduce on the latest 2.0 and 1.4 branches:

Environmental Variables:
Device: Flame 2.0 - Memory 273
BuildID: 20140707000200
Gaia: ef67af27dff3130d41a9139d6ae7ed640c34d922
Gecko: f53099796238
Version: 32.0a2
Firmware Version: V122
2.0 - Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Buri 2.0
BuildID: 20140709000201
Gaia: 1dd043857399c713e3b509c0ed31bdf20326f08b
Gecko: 0b5f757da75a
Version: 32.0a2
Firmware Version: V1.2-device.cfg
2.0 - Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Flame 1.4 - Memory 273
BuildID: 20140707000200
Gaia: 5c9e1e4131d3ac8915ed88b72bb66dc7d97be6a0
Gecko: 2d0c15450488
Version: 30.0
Firmware Version: V122
1.4 - Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Switching between Bluetooth handsfree device, receiver, and speaker, the user is presented with a 16 range BTSCO volume bar for BTSCO/Receiver/Speaker, however, changing the volume had no effect on the audio levels for the Receiver/Speaker.

-

This issue does NOT reproduce on the latest 2.1 Flame branch:

Environmental Variables:
Device: Flame 2.1 - Memory 273
BuildID: 20140707040201
Gaia: 93daa354671a698634a3dc661c8c9dcb7d824c31
Gecko: 1dc6b294800d
Version: 33.0a1
Firmware Version: V122
2.1 - Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Switching between Bluetooth handsfree device, receiver, and speaker the user is presented with a 16 range volume bar that reacts as expected when lowered/raised to different audio levels in each mode.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
blocking-b2g: 2.0? → 2.0+
Looks like an issue in sound manager, taking it.
Assignee: nobody → dkuo
Assigned to Dominic, thanks!
Status: NEW → ASSIGNED
Flags: needinfo?(timdream)
Attached file patch (deleted) —
Okay, I think this patch should fix the problem, Alive, would you please review it? thanks.
Attachment #8454232 - Flags: review?(alive)
Comment on attachment 8454232 [details]
patch

+++++
Attachment #8454232 - Flags: review?(alive) → review+
Thanks for the speedy review, Alive!

master: c47094a26c87ba71a3da4bae54febd0da21f3393
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Flags: in-moztrap?(ychung)
New test case needs to be added. There is no existing test case.
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Test case added in moztrap:

https://moztrap.mozilla.org/manage/case/14377/
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(ychung)
Flags: in-moztrap+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: