After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 611939 - A Plugin to set Bluetooth headset sound preferences
A Plugin to set Bluetooth headset sound preferences
Status: RESOLVED DUPLICATE of bug 593752
Product: gnome-bluetooth
Classification: Core
Component: wizard
2.29.x
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-bluetooth-general-maint@gnome.bugs
gnome-bluetooth-general-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2010-03-05 19:59 UTC by Prudhvi Tella
Modified: 2010-03-08 15:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Prudhvi Tella 2010-03-05 19:59:06 UTC
After pairing a new headset in the wizard, the last panel asking the user to select few properties related to sound preferences as follows:


Which profile would you like to use?
a) Telephony (HSP/HFP)
b) High Fidelity Playback (A2DP)


Do you want to use XXX as your current input/output now?

a) Yes
b) No


Are there plans to include this type of feature? If there is no one working on this, and it is something upstream would like, I am willing to write a gnome-bluetooth plugin for this feature.
Comment 1 Marc-Andre Lureau 2010-03-05 22:09:44 UTC
The user should not have to bother with that. I am not sure if PulseAudio already handle the switching magically in upstream. On the N900 it works like a charm (well, I think ;)
Comment 2 Prudhvi Tella 2010-03-05 23:40:57 UTC
On Ubuntu, it does not work automatically though. When a user pairs a headset, the intent is most likely to use it immediately. So, giving them a chance to set that option is better than exiting silently. The only "magic" PulseAudio (since 9.15) does is to use Bluetooth for clients that report as "phone" media, there is no other auto route/profile in place based on role.
Comment 3 Bastien Nocera 2010-03-08 11:37:10 UTC
(In reply to comment #1)
> The user should not have to bother with that. I am not sure if PulseAudio
> already handle the switching magically in upstream. On the N900 it works like a
> charm (well, I think ;)

Actually they should. The use case of a phone is very different from a desktop/laptop computer. Would you be happy if the music paused when you unplugged your headphones on a computer? Probably not. Is that what it should do when you unplug it from a phone/music player. Yes.

(In reply to comment #2)
> On Ubuntu, it does not work automatically though. When a user pairs a headset,
> the intent is most likely to use it immediately. So, giving them a chance to
> set that option is better than exiting silently. The only "magic" PulseAudio
> (since 9.15) does is to use Bluetooth for clients that report as "phone" media,
> there is no other auto route/profile in place based on role.

As discussed by mail some time ago, this is a good idea, and no-one is working on it right now. The plugin should live in gnome-media, and try to reuse as much of gnome-volume-control's current code as possible.

See also bug 593752

*** This bug has been marked as a duplicate of bug 593752 ***
Comment 4 Marc-Andre Lureau 2010-03-08 12:02:54 UTC
(In reply to comment #3)
> (In reply to comment #1)
> > The user should not have to bother with that. I am not sure if PulseAudio
> > already handle the switching magically in upstream. On the N900 it works like a
> > charm (well, I think ;)
> 
> Actually they should. The use case of a phone is very different from a
> desktop/laptop computer. Would you be happy if the music paused when you
> unplugged your headphones on a computer? Probably not. Is that what it should
> do when you unplug it from a phone/music player. Yes.
> 

Are you sure? We are talking about A2DP vs HSP/HFP here.

Last week I was trying to buy an A2DP headset in Barcelona. Guess what, none of the seller really know what it is! so... I don't think it should really be exposed to the user. 

Instead, the profile change should just happen when you are using the headset to listen to music/movie, and you are switching to a phone context.
Comment 5 Bastien Nocera 2010-03-08 15:25:37 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #1)
> > > The user should not have to bother with that. I am not sure if PulseAudio
> > > already handle the switching magically in upstream. On the N900 it works like a
> > > charm (well, I think ;)
> > 
> > Actually they should. The use case of a phone is very different from a
> > desktop/laptop computer. Would you be happy if the music paused when you
> > unplugged your headphones on a computer? Probably not. Is that what it should
> > do when you unplug it from a phone/music player. Yes.
> > 
> 
> Are you sure? We are talking about A2DP vs HSP/HFP here.

No, we're talking about making a device with HSP/HFP the default for VoIP applications, and A2DP devices the default for music applications.

> Last week I was trying to buy an A2DP headset in Barcelona. Guess what, none of
> the seller really know what it is! so... I don't think it should really be
> exposed to the user. 
> 
> Instead, the profile change should just happen when you are using the headset
> to listen to music/movie, and you are switching to a phone context.

Anyway, that's all mentioned in the dupe.