You are not logged in.
Hi everyone. I'm trying to resolve the flowing issue:
I've successfully paired up and connected my bluetooth headset (airpods) via bluetoothctl, and sound device has appeared in pulseaudio (it's visible at pavucontrol at least).
Right after connection it all goes well for 1-3 seconds, sound is played, but after these several moments it just mutes itself.
In pavucontrol I see that sound really goes to bluetooth headset (I see volume level bar dancing).
BT device:
Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller
Any ideas?
Offline
Also, every time I restart pulseaudio (pulseaudio -k) and connect to headset sound always appears and than disappears again.
Last edited by mingaleg (2018-10-11 19:26:33)
Offline
Do you have bluetooth enabled in systemd?
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline
Do you have bluetooth enabled in systemd?
c00ter, thank you for your interest.
Yes, I have bluetooth.service enabled:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2018-10-15 12:15:09 MSK; 2h 38min ago
Docs: man:bluetoothd(8)
Main PID: 441 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
Memory: 2.8M
CGroup: /system.slice/bluetooth.service
└─441 /usr/lib/bluetooth/bluetoothd
окт 15 12:15:09 mingaleg-frisk systemd[1]: Starting Bluetooth service...
окт 15 12:15:09 mingaleg-frisk bluetoothd[441]: Bluetooth daemon 5.50
окт 15 12:15:09 mingaleg-frisk systemd[1]: Started Bluetooth service.
окт 15 12:15:09 mingaleg-frisk bluetoothd[441]: Starting SDP server
окт 15 12:15:09 mingaleg-frisk bluetoothd[441]: Bluetooth management interface 1.14 initialized
окт 15 12:17:58 mingaleg-frisk bluetoothd[441]: Endpoint registered: sender=:1.111 path=/MediaEndpoint/A2DPSource
окт 15 12:17:58 mingaleg-frisk bluetoothd[441]: Endpoint registered: sender=:1.111 path=/MediaEndpoint/A2DPSink
Offline
This "sounds" like a hardware power-saving issue and, at this point, beyond my ability to troubleshoot. Googling your issue leads to a plethora of responses commonly indicating; A) interference from another device, B) computer hardware power-saving settings in the EFI/BIOS firmware, C) power-savings settings of the headphones themselves. In my Dell Intel/Intel laptop it is necessary to use a modprobe.d configuration file with the settings "options snd_hda_intel power_save=0" in order to keep my remote BT speakers connected in some circumstances.
regards and best of luck
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline
Yes, I've came up to the similar conclusion, thank you. Would investigate in this direction.
Offline
Does setting enable_autosuspend=0 on the btusb module help?
Offline
Does setting enable_autosuspend=0 on the btusb module help?
No effect
Offline