David Parker wrote:
> It turns out this may have been a hardware issue all along. When I got
> the new PC a few weeks ago, I just plugged the USB Bluetooth adapter into
> a port on the front and went from there. It turns out that I had chosen a
> USB 3.1 port, which can cause interference and co
It turns out this may have been a hardware issue all along. When I got the
new PC a few weeks ago, I just plugged the USB Bluetooth adapter into a
port on the front and went from there. It turns out that I had chosen a
USB 3.1 port, which can cause interference and connection issues with
Bluetoot
David Parker wrote:
> # dbus-send --print-reply --system --dest=org.bluez
> /org/bluez/hci0/dev_9B_1F_48_B8_55_F6 org.freedesktop.DBus.Properties.Get
> string:org.bluez.Device1 string:TxPower
This is a property of the device. I am not sure if it is visible onlywhen
connected. I am sure I have see
Hello,
That's a good question. "Audio" is not listed even when the earbuds are
connected and working. I have no explanation for that.
It looks like TxPower is not an available string in the dbus-send output:
# dbus-send --print-reply --system --dest=org.bluez
/org/bluez/hci0/dev_9B_1F_48_B8_55
David Parker wrote:
> # hciconfig -a
> hci0: Type: Primary Bus: USB
> BD Address: 5C:F3:70:8C:B7:98 ACL MTU: 1021:8 SCO MTU: 64:1
> UP RUNNING PSCAN
> RX bytes:62062 acl:40 sco:0 events:3178 errors:0
> TX bytes:499936 acl:776 sco:0 commands:1088 errors:38
> Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0x
Hello,
I need to correct my previous statements; I was previously running Stretch,
not Jessie. I hooked up my old hard drive and verified the versions I was
using before:
bluez 5.43-2+deb9u1
pulseaudio-module-bluetooth 10.0-1+deb9u1
Everything worked under those versions, on Debian 9.
I'll giv
David Parker wrote:
> I'm starting to suspect that this is mostly a bluetooth issue and not
> really a PA one. I struggle to get these earbuds connected whether
> PulseAudio is involved or not. I can trust them and pair them just fine,
> but the actual connection generally fails, and when it doe
Hi,
I'm starting to suspect that this is mostly a bluetooth issue and not
really a PA one. I struggle to get these earbuds connected whether
PulseAudio is involved or not. I can trust them and pair them just fine,
but the actual connection generally fails, and when it does work, it
doesn't stay
David Parker wrote:
> Thanks for the additional information. Unfortunately, the connection
> problems have returned and I haven't made any progress in solving them.
> When I kill the pulseaudio process, it simply restarts itself and I'm
> unable to stop this behavior, so I therefore can't run it
Hello,
I followed the instructions at
https://wiki.ubuntu.com/DebuggingBluetooth#On_Ubuntu_Desktop and was able
to capture verbose logging for both pulseaudio and Bluetooth. When my
device disconnects I see corresponding errors like "bluetoothd: Abort:
Connection timed out (110)" but I don't know
Correction: The "-d" for debugging to a file was for bluetoothd, not PA.
On Wed, Oct 2, 2019 at 10:10 AM David Parker wrote:
> Thanks for the additional information. Unfortunately, the connection
> problems have returned and I haven't made any progress in solving them.
> When I kill the pulseau
Thanks for the additional information. Unfortunately, the connection
problems have returned and I haven't made any progress in solving them.
When I kill the pulseaudio process, it simply restarts itself and I'm
unable to stop this behavior, so I therefore can't run it manually with the
-vvv to fur
David Parker wrote:
> This issue seems to not be fixed entirely, after all. Yesterday, the
> earbuds would pair but not connect when I powered them on. I had to
> connect them manually each time, using either bluetoothctl or
> blueman-manager. At one point they disconnected, and subsequent atte
This issue seems to not be fixed entirely, after all. Yesterday, the
earbuds would pair but not connect when I powered them on. I had to
connect them manually each time, using either bluetoothctl or
blueman-manager. At one point they disconnected, and subsequent attempts
to reconnect them result
Mark Fletcher wrote:
> On Tue, Sep 24, 2019 at 01:21:03PM -0400, David Parker wrote:
>> Ok, I think I may have solved the connectivity issue. Some additional
>> Googling revealed that GDM starts an instance of PulseAudio, and that
>> conflicts with the PulseAudio server used by the Bluetooth devi
On Tue, Sep 24, 2019 at 01:21:03PM -0400, David Parker wrote:
> Ok, I think I may have solved the connectivity issue. Some additional
> Googling revealed that GDM starts an instance of PulseAudio, and that
> conflicts with the PulseAudio server used by the Bluetooth device. The
> steps to stop GD
Ok, I think I may have solved the connectivity issue. Some additional
Googling revealed that GDM starts an instance of PulseAudio, and that
conflicts with the PulseAudio server used by the Bluetooth device. The
steps to stop GDM from starting PulseAudio can be found online, and I've
adapted them
Oh man, it turns out the original issue is still there, too. The earbuds
stayed connected for about 15 minutes, but suddenly the sound got really
choppy and distorted, and then went silent, and then they disconnected and
this was in syslog:
Sep 24 12:02:58 debian bluetoothd[627]: Start: Connectio
Thanks for the advice. I unpaired the earbuds, removed my ~/.config/pulse
directory, rebooted, then used bluetoothctl to trust, pair, and connect
them again. It seems to have worked (they have been connected for about 10
minutes and have not disconnected yet), but I am still having a few issues
w
David Parker wrote:
> But I just got a new PC and installed Buster on
> it, and now I struggle just to get the earbuds paired and connected
if there are problems with the GUI in Gnome use bluetoothctl for pairing
There are also few options you may try
David Parker wrote:
> What's most frustrating about all of this is that I was able to get them
> paired, connected, and used as the default output with very little hassle
> under Debian 9. I'm not sure what's changed in 10, but I've been trying
> to get this working for days and I'm out of ideas.
21 matches
Mail list logo
