Closed Bug 1153124 Opened 9 years ago Closed 9 years ago

[7715 v2.1][AudioChannel]music play from the unexpected route

Categories

(Firefox OS Graveyard :: AudioChannel, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1157184

People

(Reporter: jingmei.zhang, Assigned: alwu)

Details

STR:

1.plug in a headphone,open fm,pause fm,turn speaker on
2.open music,play music(music come out  from headphone)
3.go back to fm

result: music come out from speaker unexpectedly

expect result:music should come out from headphone
Hi  Alastor,

Issue exist in flame 2.1 too,can you help to check?
Flags: needinfo?(alwu)
No problem :)
Assignee: nobody → alwu
Flags: needinfo?(alwu)
It seems that is the design of the speaker manager API.

> "forcespeaker=true means that this app attempts to force the speaker to be on. This is only honored if 
> the app is currently in the foreground. So if a foreground app calls forcespeaker=true that means that 
> 'speakerforced' in all applications switches to true, and any audio from any application will go to the 
> speaker." [1] 

If you press the "switch to speaker" button, it means all sound will come out from the speaker. It doesn't relate with the playable state of FM. Therefore, it is normal to play music out from the speaker.

If you want to avoid this issue, I think we can modify the FM apps, only enable this functionality when the FM is playing.

How do you think :)?

[1] WebAPI/SpeakerManager : https://wiki.mozilla.org/WebAPI/SpeakerManager
(In reply to Alastor Wu [:alwu] from comment #3)

Yes,see from the speakerManager API,it seems to be so.

But from user perspective,speaker in fm should only be used by fm,it should not affect other sounds.

Thank you for your advice,I will try to modify it in fm :)
I file another bug to more clearly describe this issue. See bug1157184. 
Also close other related bugs.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Correct the status.
Resolution: INVALID → DUPLICATE
You need to log in before you can comment on or make changes to this bug.