Re: Re: bluetooth audio
Thanks! -- WLM
Re: bluetooth audio
Luis Mochan wrote: > After a recent update/upgrade in debian/bookworm my bluetooth > earphones and my bluetooth earphones stopped working. > I found a solution in the discussion of at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997862=no=no=no > > related to bug #997862 which seemed to work for me, that is, > installing a package libspa-0.2-bluetooth. FYI: Same is up on the pulseaudio devel list Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones
Re: Bluetooth audio periodic disconnect
Bhasker C V wrote: > Hi all, > I am on bullseye. > I have tried and tested this with many headphones > > When on bluetooth the audio gets periodically disconnected and > re-connects > to audio after 5 seconds. > During the time the bluetooth per-say does not get disconnected but just > the audio stops and then starts again in 5 seconds. > I have already set laptop-mode tools to blacklist usb power management > for > my usb adapter. > There are no issues with bluetooth lag or connection issues. My > headphones > connect fine and work fine except for the intermittent disconnects. > > Please could someone help me fix this ? > One option would be to get debian stable somehow and try if it is reproducible there. Another option would be to look at what the underlaying systems are doing there. For example start pulse audio with -vvv to get more output or inspect the data flow. Use dbus-monitor --system and --session or other to inspect dbus event. All components in the chain could cause the issue - kernel/driver, systemd, dbus, pulse and bluez. You have to find out which system is causing the connection drop. I am on buster and I play recently more with bluetooth and the phone. I noticed that when I connect two profiles (A2DP and HFP) the audio is lagging. When A2DP or HFP is connected only, audio is fine. When I make a call via HFP and I finish the call, connection to phone drops. >From what you write, I assume you use A2DP and may be it is pulse not able to process or too sensitive, but this suggestion is just fortune telling. I am personally disappointed by the move to bluez5 in the whole linux world - not that bluez4 was OK, but after a lot of effort things were working. Now bluez5 is better, but other systems are still improving to match the new design - we pay the price. regards
Re: Bluetooth audio problem
On Sat, Mar 23, 2019 at 08:24:30AM -0500, Nicholas Geovanis wrote: > On Fri, Mar 22, 2019 at 9:29 AM Mark Fletcher wrote: > > > > > So this turned out to be a weirdie -- if I dropped the "sudo" my > > original command worked. > > So now, suddenly from that update that started this thread, if I run the > > pactl command as an unprivileged user, it works fine. > > > Is it possible that you had previously started pulseaudio as root, and > could no longer communicate with it as an unprivileged user? > I ask this having been a pulseaudio victim myself sometimes. > > Hmm, interesting idea, but the situation I was previously in pertained over a period since Stretch became Stable until shortly before my original mail in this thread (sometime in February if I recall correctly). Over, naturally, multiple reboots. For that period, I had to use sudo when issuing the pactl command (in Jessie and previously, the pactl command wasn't necessary at all). So I guess I could have had some sort of configuration which repeatedly put me in that situation on every reboot, and the update that "created the problem" actually fixed whatever *that* problem was... otherwise, no I don't think so. Thanks for the suggestion though Mark
Re: Bluetooth audio problem
On Fri, Mar 22, 2019 at 9:29 AM Mark Fletcher wrote: > > So this turned out to be a weirdie -- if I dropped the "sudo" my > original command worked. > So now, suddenly from that update that started this thread, if I run the > pactl command as an unprivileged user, it works fine. Is it possible that you had previously started pulseaudio as root, and could no longer communicate with it as an unprivileged user? I ask this having been a pulseaudio victim myself sometimes. > Mark > >
Re: Bluetooth audio problem
On Fri, Mar 22, 2019 at 08:44:46PM +0100, deloptes wrote: > Mark Fletcher wrote: > > > So this turned out to be a weirdie -- if I dropped the "sudo" my > > original command worked. > > > > So now, suddenly from that update that started this thread, if I run the > > pactl command as an unprivileged user, it works fine. I have no idea why > > it changed but I'm just happy I have it working again. > > you can mark also as solved, if solved > True, I could have. But I don't think it will kill interested people who follow after to read a 3-mail thread to see the resolution.
Re: Bluetooth audio problem
Mark Fletcher wrote: > So this turned out to be a weirdie -- if I dropped the "sudo" my > original command worked. > > So now, suddenly from that update that started this thread, if I run the > pactl command as an unprivileged user, it works fine. I have no idea why > it changed but I'm just happy I have it working again. you can mark also as solved, if solved
Re: Bluetooth audio problem
On Sun, Mar 03, 2019 at 06:04:05PM +0100, deloptes wrote: > Mark Fletcher wrote: > > > Hello > > > > Since upgrading to Stretch shortly after it became stable, I have had to > > execute the following after a reboot before being able to connect to > > bluetooth devices using the Gnome bluetooth applet: > > > > $ sudo pactl load-module module-bluetooth-discover > > > > Now, when I run the above command it is erroring out with: > > > > xcb_connection_has_error() returned true > > Connection failure: Connection refused > > pa_context_connect() failed: Connection refused > > > > > When I want to debug pulse I do > > echo "autospawn = no" > ~/.pulse/client.conf > > kill PA and run it from command line with -v option you can also > use --log-level (man pulseaudio) > > perhaps you can see what is the problem there. If not it might be dbus issue > with permissions - check the dbus settings > > Also some times it helps to remove the ~/.pulse directory and restart > pulseaudio. > So this turned out to be a weirdie -- if I dropped the "sudo" my original command worked. So now, suddenly from that update that started this thread, if I run the pactl command as an unprivileged user, it works fine. I have no idea why it changed but I'm just happy I have it working again. Mark
Re: Bluetooth audio problem
Mark Fletcher wrote: > Hello > > Since upgrading to Stretch shortly after it became stable, I have had to > execute the following after a reboot before being able to connect to > bluetooth devices using the Gnome bluetooth applet: > > $ sudo pactl load-module module-bluetooth-discover > > Without that command, needed once only after each reboot, the Gnome > applet is unable to connect to any bluetooth audio devices, eg my > headphones to be used as an audio sink, or my iPhone to be used as an > audio source. Once that command has been issued once, everything works > as it should, and continues to do so until the next reboot. > > I've been away for a couple of weeks and so hadn't installed updates to > my stretch installation for something like 3 weeks, until Saturday this > week when I installed updates. Unfortunately I didn't pay enough > attention to exactly what was upgraded but I _believe_ I saw udev in the > list of things getting upgraded. > > Now, when I run the above command it is erroring out with: > > xcb_connection_has_error() returned true > Connection failure: Connection refused > pa_context_connect() failed: Connection refused > > Googling for this has only turned up old information which does not seem > to relate to the problem I am facing. In most cases the context is audio > not working; in my case audio output through speakers plugged into the > sound card is working fine, USB mic connected by a wire is working > fine, the only problem is anything bluetooth. > > Bluetooth on this machine is provided by a USB bluetooth dongle which I > have been using for ages. > > Can anyone suggest steps to diagnose? > When I want to debug pulse I do echo "autospawn = no" > ~/.pulse/client.conf kill PA and run it from command line with -v option you can also use --log-level (man pulseaudio) perhaps you can see what is the problem there. If not it might be dbus issue with permissions - check the dbus settings Also some times it helps to remove the ~/.pulse directory and restart pulseaudio. regards
