This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
I'm well aware of the range, that's not a problem. The problem is that
this setup worked perfectly from January until June, which is when I
went on vacation and installed 9.04. I did however not touch my home
directory - any .gnome/ directories or gconf settings you want me to
clear/check?
Is
Hi Fredrik,
I don't think there's something in your .gnome directories that might be
causing this or could give us some hint.
When you installed 9.04 several components have changed, including the
kernel. Something in the bluetooth stack in the kernel might be causing
this or even in the btusb
how do you setup your headset? using alsa or pulseaudio?
on the other front, your shorter range issue is probably due to your
adapter (some out there are really crapware).
--
[Jaunty] regression: bluetooth headset playback quality - choppy every
two-three minutes
I start by pairing using the gnome toolbar applet.
I put the MAC address of my adapter in .asoundrc as outlined above.
I execute 'gconftool -t string -s /system/gstreamer/0.10/default/musicaudiosink
alsasink device=bluetooth' to get music to my headset.
I'm guessing pulseaudio isn't in that
Pulseaudio isn't in that chain, you're right. You're using the bluetooth
ALSA plugin directly.
Regarding the range there are classes of bluetooth adapters each being
able to reach different ranges.
Is it possible for you to try Karmic with gnome-bluetooth (instead of
bluez-gnome) and pulseaudio?
