Closed Bug 1037745 Opened 10 years ago Closed 9 years ago

[B2G][Flame][Music] Audio cut out is inconsistent when changing sound volume in settings

Categories

(Firefox OS Graveyard :: AudioChannel, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

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

RESOLVED WORKSFORME
Tracking Status
b2g-v1.4 --- unaffected
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: AdamA, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [273MB-Flame-Support][2.0-exploratory])

Attachments

(1 file)

Attached file logcat.txt
Description: When listening to music through the music app and changing the volume of the ringer, alarm, and media the song cut off is inconsistent. when changing media and ringer the song continues playing and a sample sound is heard. when changing alarm the song cuts out and an alarm sample is played. On the Buri ringer and alarm cut off the song and Repro Steps: 1) Update a Flame to 20140711000201 2) Open music app and start playing a song 3) Open Settings > Sound 4) Change media and ringer volume 5) Change alarm volumne 6) Observe audio Actual: Song cut off is inconsistent between volume changers Expected: It is expected that the song cutoff is consistent between volume changers Environmental Variables: Device: Flame 2.0 (273mb) Moz Ril Build ID: 20140711000201 Gaia: 18c44a1bc31b374ba00a069904465a8d07971a60 Gecko: f880dae4fdbe Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Keywords: slider, ringtone, notification Notes: Repro frequency: 100% See attached: video clip(http://youtu.be/0lPUVLtDc9Y), logcat ----------------------------------- This issue is also occurring on 2.1 Flame, 2.1 Buri, 2.0 Flame(512mb), 2.0 Buri. Environmental Variables: Device: Flame Master Build ID: 20140711040202 Gaia: c47094a26c87ba71a3da4bae54febd0da21f3393 Gecko: 1b1296d00330 Version: 33.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Environmental Variables: Device: Flame 2.0 (512mb) BuildID: 20140711000201 Gaia: 18c44a1bc31b374ba00a069904465a8d07971a60 Gecko: f880dae4fdbe Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Environmental Variables: Device: Buri Master Build ID: 20140711040202 Gaia: c47094a26c87ba71a3da4bae54febd0da21f3393 Gecko: 1b1296d00330 Version: 33.0a1 (Master) MOZ Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Environmental Variables: Device: Buri 2.0 Build ID: 20140711000201 Gaia: 18c44a1bc31b374ba00a069904465a8d07971a60 Gecko: f880dae4fdbe Version: 32.0a2 (2.0) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Actual: Song cut off is inconsistent between volume changers ------------------------------- This issue did not occur in 1.4 Flame, 1.4 Buri, 1.4 Open_C. Environmental Variables: Device: Flame 1.4 Build ID: 20140711000202 Gaia: e273c1f52ed7187e4e0b2d66ed5718f0f20c6eeb Gecko: 896fa800b72d Version: 30.0 (1.4) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Environmental Variables: Device: Buri 1.4 Build ID: 20140711000202 Gaia: e273c1f52ed7187e4e0b2d66ed5718f0f20c6eeb Gecko: 896fa800b72d Version: 30.0 (1.4) MOZ Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Environmental Variables: Device: Open_C 1.4 Build ID: 20140711000202 Gaia: e273c1f52ed7187e4e0b2d66ed5718f0f20c6eeb Gecko: 896fa800b72d Version: 30.0 (1.4) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Actual: No sound preview is played when volume is changed.
Whiteboard: [273MB-Flame-Support][2.0-exploratory]
Status: UNCONFIRMED → NEW
QA Whiteboard: [QAnalyst-Triage?]
Ever confirmed: true
Flags: needinfo?(jmitchell)
Keywords: regression
not nomming as a blocker, issue seems a fringe case (adjusting alarm/ringer volume through settings while listening to sound)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
See Also: → 1096886
This is an audio channel issue, and it actually seems to have gotten worse: if you change the volume of the media channel inside settings, it *stops* the music and doesn't resume automatically. This is pretty bad!
Component: Gaia::Music → AudioChannel
Keywords: qawanted
Summary: [B2G][Flame][Music] Audio cut out is inconsistent when when changing sound volume in settings → [B2G][Flame][Music] Audio cut out is inconsistent when changing sound volume in settings
Hi, It's not the bug that the behaviors of the different type volume changing are inconsistent, it's defined in the UX sound spec [1]. As the media/notification/alarm indicates three different audio channel type, so it's correct that we have different audio competing behavior. [1] https://bug1068219.bmoattachments.org/attachment.cgi?id=8579177#12
However, it's incorrect as Jim said in comment2. We should resume the music after the media sound from setting app ended. So I propose close this bug, and open another bug for the comment2.
You're right; this does seem to obey the UX specs. However, I think this means the specs are wrong. Changing the media volume (content channel) shouldn't *stop* the media playing in the background. I think it should resume immediately, or "play at 20% volume" like some of the other cases in that table. If you want to open a new bug for this, that's fine by me. I can post some of my ideas about audio channel interactions once you do that.
Changing the media volume equals to play another music by setting app, so in this case I think to pause the background music is reasonable. We can't have two policy rule (pause & fading the volume) for the same competing behavior. But, it should be resume immediately after the sounded from setting app ended. --- In addition, I think you can write some comments in bug1068219 for UX, because they're planning to update UX sound spec.
Ok, I'll post my thoughts in that bug. Thanks!
According the comment3, it's not the bug. Close this bug. --- In addition, the problem in comment2 would be solved in bug1222300.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Per comment 8, clear the 'qawanted' keywords.
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: