Ich habe mal ein wenig die Suchmaschinen strapaziert und festgestellt, daß das wohl ein
altbekannter Bug (nicht nur bei maemo) ist. Schuld soll das Bluetooth-Profil A2DP sein, das ja vom Voyager Pro+ unterstützt wird. Es wird folgendes empfohlen:
So far, it looks like it is a problem with A2DP.
I came across forums in the Android community where people were upset when A2DP support was added for them. It was messing up connections with their carkits, headsets, etc. and also messing up their phone's audio system and whatnot.
My in-car bluetooth handsfree module supports A2DP so it was promising that it could be the problem. I uncommented and changed the "Disabled=" line in /etc/bluetooth/audio.conf to be:
Disable=Control,Source,Sink
in order to disable A2DP. Rebooted and travelled in the car a few times; had a couple of phone conversations; so far no issues. Perhaps others could try this to see if they stop having this bug as well.
Gruß Willi
Edit:
Ich habe die Empfehlung mal umgesetzt und konnte das beschriebene Problem seitdem trotz intensiver Headset-Nutzung nicht mehr beobachten. Scheint also ein guter Tip zu sein.
