[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-bluetooth
Subject:    Changed default configuration in bluez 4.97 and higher?
From:       Karol Babioch <karol () babioch ! de>
Date:       2012-01-25 18:37:16
Message-ID: 4F204BDC.1010007 () babioch ! de
[Download RAW message or body]

Hi,

I'm wondering whether there has been made any change to the default
configuration of bluez 4.97 and/or 4.98? I've looked at the changelog,
but combined with the release notes it looks to me as they were "simple"
bug fixing releases. At least there is no mention of a change of the
default configuration or something like that.

However I'm experiencing trouble with these releases using my bluetooth
headset (A2DP). To be honest I'm using gnome-bluetooth and not that
experienced with the command line tools, but starting with 4.97 it is no
longer possible to use my headset as an audio output device, although it
is possible to discover it and to connect to it. But after the
connection has been established it doesn't even get recognized by
PulseAudio.

I now got it working again by adding "Enable=Socket" in the audio.conf
file. However I'm not sure whether this was changed intentional, because
it worked out-of-the-box beforehand and I guess a basic A2DP setup is
supposed to do so.

There are at least two other guys affected by this, see [1]. So before
filing a bug in the bug tracking system of my distribution and asking
for inclusion of the above option, I would like to know why this was
changed and whether this is intentional or not.

[1]
https://mailman.archlinux.org/pipermail/arch-general/2012-January/024386.html

Best regards,
Karol Babioch


["signature.asc" (application/pgp-signature)]
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[prev in list] [next in list] [prev in thread] [next in thread]