[opensuse-factory] Workarounds for Buggy Bluetooth Audio
I have problems with getting all my Bluetooth audio device pairing and working when first paired, and these steps nearly always get them to work, so I was wondering whether there is a root cause that can be pinned down and fixed as a bug report. Device: Mee Audio Air-Fi Rumble Headphone 1. No sound when paired. 2. Open Audio and Video system settings module in KDE. 3. Wait for it to appear, and select Air-Fi Rumble in Device Preference > Audio Playback and click Test. 4. Test audio plays and now audio works. Device: Bluedio Wireless Headset 1. No sound when paired. 2. Device not activated in Audio and Video system settings module in KDE. 3. Select Audio Hardware Setup > Soundcard > Bluedio 4. Toggle Profile to A2DP Sink (device not activated with this selection, but will be with HSP/HFP!) 5. Device will still be greyed out in Device Preference. Unpair and pair device again. 6. Device will show up in Device Preference, but without audio. 7. Select Bluedio and press the Test button. 8. Test audio plays and now audio works. I am not sure why both devices are treated differently, but it is certain that the Air-Fi is the more expensive device. Thoughts?
On Tuesday 2017-08-15 02:11, Chan Ju Ping wrote:
I have problems with getting all my Bluetooth audio device pairing and working when first paired, and these steps nearly always get them to work, so I was wondering whether there is a root cause that can be pinned down and fixed as a bug report.
Device: Mee Audio Air-Fi Rumble Headphone Device: Bluedio Wireless Headset
I am not sure why both devices are treated differently, but it is certain that the Air-Fi is the more expensive device.
Thoughts?
Not sure what exactly the KDE tools do, but if you use (just) bluetoothctl and pulseaudio - I can tell how if needed - is the success rate better? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-08-15 06:45, Jan Engelhardt wrote:
Not sure what exactly the KDE tools do, but if you use (just) bluetoothctl and pulseaudio - I can tell how if needed - is the success rate better?
How? :-) Wiki page perhaps? There is no BT stack in XFCE to my knowledge, so I would like to try another means. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Tuesday 2017-08-15 15:21, Carlos E. R. wrote:
On 2017-08-15 06:45, Jan Engelhardt wrote:
Not sure what exactly the KDE tools do, but if you use (just) bluetoothctl and pulseaudio - I can tell how if needed - is the success rate better?
How? :-)
Wiki page perhaps?
There is no BT stack in XFCE to my knowledge, so I would like to try another means.
# bluetoothctl BT# power on -- at this point, devices paired in the past are usable -- BT# agent on BT# default-agent BT# discoverable on BT# pairable on BT# scan on BT# pair XX:XX:XX:XX:XX:XX after that, the sound device should show up in `pavucontrol` and be usable from media players when they are set to use libpulse. Likewise, Internets shared by BT devices should show in the NetworkManager tray icon menu now. If not, use `rfkill` to unblock(enable) more software layers. rfkill is the most fine grained operation there is; other ways are rightclick NM tray icon, or use of the Fn special laptop keys for coarse grain dis-/enable. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 17 August 2017 01:34:10 +08 Jan Engelhardt wrote:
# bluetoothctl BT# power on -- at this point, devices paired in the past are usable --
BT# agent on BT# default-agent BT# discoverable on BT# pairable on BT# scan on BT# pair XX:XX:XX:XX:XX:XX
It works until here after I unpaired the device.
after that, the sound device should show up in `pavucontrol` and be usable from media players when they are set to use libpulse.
Device does not appear here, and is also not found in the audio module in KDE's System Settings. So unfortunataly, not as good as the workaround I have now. I should add I misused the word "pair/unpair" for the word "connect/ disconnect" which may have led to some misunderstanding. I have no problem pairing the device, and connecting to it. Just no luck with audio.
On Saturday 2017-08-19 15:06, Chan Ju Ping wrote:
On Thursday, 17 August 2017 01:34:10 +08 Jan Engelhardt wrote:
# bluetoothctl BT# power on -- at this point, devices paired in the past are usable --
BT# agent on BT# default-agent BT# discoverable on BT# pairable on BT# scan on BT# pair XX:XX:XX:XX:XX:XX
It works until here after I unpaired the device.
Right, I had another go with another sound device, and that reminded me of all the things still needed to be done. 1. ensuring pulseaudio-bluetooth is installed (may need restart?) 2. (maybe bluetooth.service also needs a restart?) 3. bluetoothctl needs to be run as normal user, not root 4. after pair XX, [bluetooth]> info D0:E7:82:64:21:90 Device D0:E7:82:64:21:90 Name: Cone Alias: Cone Class: 0x040000 Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) Modalias: bluetooth:v00F2p0001d0001 Obviously, the device in question needs an audio sink (A2DP) to work in the first place..., 5. BT> connect XX:XX... Hopefully things work. If not, `journalctl -u bluetooth.service` might help if only to reveal permission errors. On error, sad things like bluetoothd[13692]: Sap driver initialization failed. bluetoothd[13692]: sap-server: Operation not permitted (1) bluetoothd[13692]: a2dp-sink profile connect failed for D0:E7:82:64:21:90: Protocol not available (=> pulseaudio-bluetooth not installed) could show. Or, when successful: : Endpoint registered: sender=:1.397 path=/MediaEndpoint/A2DPSource : Endpoint registered: sender=:1.397 path=/MediaEndpoint/A2DPSink : /org/bluez/hci0/dev_D0_E7_82_64_21_90/fd0: fd(22) ready : /org/bluez/hci0/dev_D0_E7_82_64_21_90/fd1: fd(22) ready -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, 25 August 2017 02:03:49 +08 Jan Engelhardt wrote:
Right, I had another go with another sound device, and that reminded me of all the things still needed to be done.
1. ensuring pulseaudio-bluetooth is installed (may need restart?) 2. (maybe bluetooth.service also needs a restart?)
3. bluetoothctl needs to be run as normal user, not root
4. after pair XX, [bluetooth]> info D0:E7:82:64:21:90 Device D0:E7:82:64:21:90 Name: Cone Alias: Cone Class: 0x040000 Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) Modalias: bluetooth:v00F2p0001d0001
Obviously, the device in question needs an audio sink (A2DP) to work in the first place...,
5. BT> connect XX:XX...
Hopefully things work. If not, `journalctl -u bluetooth.service` might help if only to reveal permission errors.
On error, sad things like
bluetoothd[13692]: Sap driver initialization failed. bluetoothd[13692]: sap-server: Operation not permitted (1) bluetoothd[13692]: a2dp-sink profile connect failed for D0:E7:82:64:21:90: Protocol not available (=> pulseaudio-bluetooth not installed)
could show. Or, when successful: : Endpoint registered: sender=:1.397 path=/MediaEndpoint/A2DPSource : Endpoint registered: sender=:1.397 path=/MediaEndpoint/A2DPSink : /org/bluez/hci0/dev_D0_E7_82_64_21_90/fd0: fd(22) ready : /org/bluez/hci0/dev_D0_E7_82_64_21_90/fd1: fd(22) ready
Sorry for the late reply. Since this email, bluetooth audio has been working far more consistently. It would seem that I just need to wait for a bit after pairing and the audio will Just Work (TM), presumably because stuff is being loaded in the background out of sight. Also, I got new Bluetooth headphones that seem to work far better than either of my previous devices. Yay for progress!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID:
On Tuesday 2017-08-15 15:21, Carlos E. R. wrote:
On 2017-08-15 06:45, Jan Engelhardt wrote:
Not sure what exactly the KDE tools do, but if you use (just) bluetoothctl and pulseaudio - I can tell how if needed - is the success rate better?
How? :-)
Wiki page perhaps?
There is no BT stack in XFCE to my knowledge, so I would like to try another means.
# bluetoothctl BT# power on -- at this point, devices paired in the past are usable --
BT# agent on BT# default-agent BT# discoverable on BT# pairable on BT# scan on BT# pair XX:XX:XX:XX:XX:XX
after that, the sound device should show up in `pavucontrol` and be usable from media players when they are set to use libpulse.
Unfortunately, it does not work for me. I assume it has to be done as root (because you wrote '# bluetoothctl', not "> ..." minas-tirith:~ # bluetooth bluetooth-sendto bluetoothctl minas-tirith:~ # bluetoothctl [NEW] Controller 00:19:0E:05:6B:46 minas-tirith-0 [default] [NEW] Device 00:24:7D:66:42:C9 Mobilis in mobile 5220 [NEW] Device 28:CC:01:9B:62:C7 MobilisInMobile [NEW] Device 41:00:00:00:87:F1 Avenzo AV604 [bluetooth]# power on [CHG] Controller 00:19:0E:05:6B:46 Class: 0x0c010c Changing power on succeeded [CHG] Controller 00:19:0E:05:6B:46 Powered: yes [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# discoverable on Changing discoverable on succeeded [CHG] Controller 00:19:0E:05:6B:46 Discoverable: yes [bluetooth]# pairable on Changing pairable on succeeded [DEL] Device 41:00:00:00:87:F1 Avenzo AV604 [DEL] Device 28:CC:01:9B:62:C7 MobilisInMobile [DEL] Device 00:24:7D:66:42:C9 Mobilis in mobile 5220 [CHG] Controller 00:19:0E:05:6B:46 Class: 0x000000 [CHG] Controller 00:19:0E:05:6B:46 Powered: no [CHG] Controller 00:19:0E:05:6B:46 Discovering: no [CHG] Controller 00:19:0E:05:6B:46 Discoverable: no [DEL] Controller 00:19:0E:05:6B:46 minas-tirith-0 [default] [bluetooth]# scan on No default controller available [bluetooth]# I try as user, I can not even start: cer@minas-tirith:~> bluetoothctl [bluetooth]# power on No default controller available [bluetooth]# power off No default controller available [bluetooth]# I restart "bluetooth.service" as root, then try to repeat the sequence as user, same problem: [bluetooth]# power on bluetoothd... No default controller available [bluetooth]# Notice that bluetooth worked on this same hardware some releases ago, till XFCE removed the BT stack. I used it to transfer files to a phone. minas-tirith:~ # zypper se pulseaudio-bluetooth ... Loading repository data... Reading installed packages... No matching items found. minas-tirith:~ # minas-tirith:~ # rpm -qa | grep -i pulseaudio pulseaudio-bash-completion-9.0-2.3.1.x86_64 pulseaudio-9.0-2.3.1.x86_64 pulseaudio-module-lirc-9.0-2.3.1.x86_64 pulseaudio-utils-32bit-9.0-2.3.1.x86_64 pulseaudio-lang-9.0-2.3.1.noarch pulseaudio-utils-9.0-2.3.1.x86_64 xfce4-panel-plugin-pulseaudio-0.2.3-3.2.x86_64 pulseaudio-module-gconf-9.0-2.3.1.x86_64 pulseaudio-module-bluetooth-9.0-2.3.1.x86_64 pulseaudio-module-jack-9.0-2.3.1.x86_64 pulseaudio-module-zeroconf-9.0-2.3.1.x86_64 pulseaudio-module-x11-9.0-2.3.1.x86_64 minas-tirith:~ # I remove and re-insert the USB-BT dongle and try again. This time I can not pair: cer@minas-tirith:~> bluetoothctl [NEW] Controller 00:19:0E:05:6B:46 minas-tirith-0 [default] [NEW] Device 00:24:7D:66:42:C9 Mobilis in mobile 5220 [NEW] Device 28:CC:01:9B:62:C7 MobilisInMobile [NEW] Device 41:00:00:00:87:F1 Avenzo AV604 <======== [bluetooth]# power on [CHG] Controller 00:19:0E:05:6B:46 Class: 0x0c010c Changing power on succeeded [CHG] Controller 00:19:0E:05:6B:46 Powered: yes [bluetooth]# default-agent No agent is registered [bluetooth]# discoverable on Changing discoverable on succeeded [CHG] Controller 00:19:0E:05:6B:46 Discoverable: yes [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller 00:19:0E:05:6B:46 Discovering: yes [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [CHG] Device 41:00:00:00:87:F1 RSSI: -60 [bluetooth]# scan off [CHG] Device 41:00:00:00:87:F1 RSSI is nil Discovery stopped [CHG] Controller 00:19:0E:05:6B:46 Discovering: no [bluetooth]# scan on Discovery started [CHG] Controller 00:19:0E:05:6B:46 Discovering: yes [CHG] Device 41:00:00:00:87:F1 RSSI: -67 [CHG] Device 41:00:00:00:87:F1 RSSI: -76 [CHG] Device 41:00:00:00:87:F1 RSSI: -67 [CHG] Device 41:00:00:00:87:F1 RSSI: -75 [CHG] Device 41:00:00:00:87:F1 RSSI: -67 [CHG] Device 41:00:00:00:87:F1 RSSI: -75 [CHG] Device 41:00:00:00:87:F1 RSSI: -67 [CHG] Device 41:00:00:00:87:F1 RSSI: -76 [CHG] Device 41:00:00:00:87:F1 RSSI: -67 [CHG] Device 41:00:00:00:87:F1 RSSI: -80 [CHG] Device 41:00:00:00:87:F1 RSSI: -68 [CHG] Device 41:00:00:00:87:F1 RSSI: -81 [CHG] Device 41:00:00:00:87:F1 RSSI: -72 [CHG] Device 41:00:00:00:87:F1 RSSI: -63 [CHG] Device 41:00:00:00:87:F1 RSSI: -75 [CHG] Device 41:00:00:00:87:F1 RSSI: -61 [CHG] Device 41:00:00:00:87:F1 RSSI: -74 [CHG] Device 41:00:00:00:87:F1 RSSI: -65 [bluetooth]# pair 41:00:00:00:87:F1 Attempting to pair with 41:00:00:00:87:F1 Failed to pair: org.bluez.Error.AlreadyExists [CHG] Device 41:00:00:00:87:F1 RSSI: -73 [CHG] Device 41:00:00:00:87:F1 RSSI: -81 [CHG] Device 41:00:00:00:87:F1 RSSI: -71 [CHG] Device 41:00:00:00:87:F1 RSSI: -63 [CHG] Device 41:00:00:00:87:F1 RSSI: -54 [CHG] Device 41:00:00:00:87:F1 RSSI: -63 [CHG] Device 41:00:00:00:87:F1 RSSI: -82 [CHG] Device 41:00:00:00:87:F1 RSSI: -66 [bluetooth]# info 41:00:00:00:87:F1 Device 41:00:00:00:87:F1 Name: Avenzo AV604 Alias: Avenzo AV604 Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: Headset HS (00001131-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) Modalias: bluetooth:v000Fp0000d0000 RSSI: -66 [CHG] Device 41:00:00:00:87:F1 RSSI: -76 [CHG] Device 41:00:00:00:87:F1 RSSI: -68 [CHG] Controller 00:19:0E:05:6B:46 Discoverable: no [CHG] Device 41:00:00:00:87:F1 RSSI: -76 [CHG] Device 41:00:00:00:87:F1 RSSI: -66 [CHG] Device 41:00:00:00:87:F1 RSSI: -75 [CHG] Device 41:00:00:00:87:F1 RSSI: -65 [CHG] Device 41:00:00:00:87:F1 RSSI: -76 [CHG] Device 41:00:00:00:87:F1 RSSI: -63 [CHG] Device 41:00:00:00:87:F1 RSSI: -55 [CHG] Device 41:00:00:00:87:F1 RSSI: -63 [CHG] Device 41:00:00:00:87:F1 RSSI: -78 [CHG] Device 41:00:00:00:87:F1 RSSI: -67 [CHG] Device 41:00:00:00:87:F1 RSSI: -80 [CHG] Device 41:00:00:00:87:F1 RSSI: -68 [CHG] Device 41:00:00:00:87:F1 RSSI: -78 [CHG] Device 41:00:00:00:87:F1 RSSI: -66 [CHG] Device 41:00:00:00:87:F1 RSSI: -74 [CHG] Device 41:00:00:00:87:F1 RSSI: -62 [bluetooth]# scan off [CHG] Device 41:00:00:00:87:F1 RSSI is nil Discovery stopped [CHG] Controller 00:19:0E:05:6B:46 Discovering: no [bluetooth]# I interpret is as the BT stack already paired in the past with the headphone. But why doesn't pair? The headphones is asking me (by voice, non stop) to enter the code '0000' in the computer, so it is seeing it. [bluetooth]# show Controller 00:19:0E:05:6B:46 Name: minas-tirith.valinor Alias: minas-tirith-0 Class: 0x0c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0529 Discovering: no [CHG] Device 41:00:00:00:87:F1 Connected: yes [CHG] Device 41:00:00:00:87:F1 UUIDs: 00001108-0000-1000-8000-00805f9b34fb [CHG] Device 41:00:00:00:87:F1 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb [CHG] Device 41:00:00:00:87:F1 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Device 41:00:00:00:87:F1 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Device 41:00:00:00:87:F1 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb [CHG] Device 41:00:00:00:87:F1 UUIDs: 00001131-0000-1000-8000-00805f9b34fb [CHG] Device 41:00:00:00:87:F1 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [Avenzo AV604]# Why has the prompt changed to "[Avenzo AV604]"? Is it connected? [Avenzo AV604]# info 41:00:00:00:87:F1 Device 41:00:00:00:87:F1 Name: Avenzo AV604 Alias: Avenzo AV604 Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: Headset HS (00001131-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) Modalias: bluetooth:v000Fp0000d0000 [Avenzo AV604]# Well, yes, it is connected! When, how? What did I do? Well, pavucontrol show it under "Configuration", the profile is deactivated. It offers two: Headset Head Unit (HSP/HPP) and I hear something about "Call active, Phone 1" Or I can change to "High Fidelity Playback (A2DP Sink)" I play a video, but I don't hear it on the phone, it is going to the laptop speakers. Ah, I have to go to the "Playback" tab and change the output device Mplayer is using. :-) Well, it does work, thanks. :-) A bit complicated, though... - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlnZP8oACgkQja8UbcUWM1xi5QD+L3HAH9ukXhiuudPY38HTLCIe LMtQIKZRxJXuh9sWSxgA/jUTSUQZmrdTrJs6AvH2wcSjc4Yj2XdhzNRUJ2Qu20kx =G4Gd -----END PGP SIGNATURE-----
On Saturday 2017-10-07 22:57, Carlos E. R. wrote:
after that, the sound device should show up in `pavucontrol` and be usable from media players when they are set to use libpulse.
Unfortunately, it does not work for me. I assume it has to be done as root (because you wrote '# bluetoothctl', not "> ..."
I (later) figured you need the normal user for bluetoothctl, because that would be the program to spawn (if not running yet) and/or connecting to the pulseaudio instances -- which root has none of, but the user does.
I try as user, I can not even start:
cer@minas-tirith:~> bluetoothctl [bluetooth]# power on No default controller available
Yeah don't know how that happens. But with the mess that modern desktop systems are, it does not surprise me. (I don't even trust Windows to get this right all times, which is why so many single-user systems run with a semi-admin account all the time.) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-10-08 00:59, Jan Engelhardt wrote:
On Saturday 2017-10-07 22:57, Carlos E. R. wrote:
after that, the sound device should show up in `pavucontrol` and be usable from media players when they are set to use libpulse.
Unfortunately, it does not work for me. I assume it has to be done as root (because you wrote '# bluetoothctl', not "> ..."
I (later) figured you need the normal user for bluetoothctl, because that would be the program to spawn (if not running yet) and/or connecting to the pulseaudio instances -- which root has none of, but the user does.
I try as user, I can not even start:
cer@minas-tirith:~> bluetoothctl [bluetooth]# power on No default controller available
Yeah don't know how that happens. But with the mess that modern desktop systems are, it does not surprise me. (I don't even trust Windows to get this right all times, which is why so many single-user systems run with a semi-admin account all the time.)
I got it working in the end, but it is all very confusing and I don't know how to repeat. I had to unplug-replug the adapter to try again. Pairing failed initially, because computer and earphones had already been paired in the past. Then the paired, but I don't know what I did that caused it. And sound played. I exited "bluetoothctl" program, powered off and on the earphones, and they paired automatically. Maybe the "bluetoothctl" magic only needs been done once per session unless I disconnect the dongle. Maybe also after hibernation. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
In data martedì 15 agosto 2017 02:11:03 CEST, Chan Ju Ping ha scritto:
I have problems with getting all my Bluetooth audio device pairing and working when first paired, and these steps nearly always get them to work, so I was wondering whether there is a root cause that can be pinned down and fixed as a bug report.
Device: Mee Audio Air-Fi Rumble Headphone
1. No sound when paired. 2. Open Audio and Video system settings module in KDE. 3. Wait for it to appear, and select Air-Fi Rumble in Device Preference > Audio Playback and click Test. 4. Test audio plays and now audio works.
Device: Bluedio Wireless Headset
1. No sound when paired. 2. Device not activated in Audio and Video system settings module in KDE. 3. Select Audio Hardware Setup > Soundcard > Bluedio 4. Toggle Profile to A2DP Sink (device not activated with this selection, but will be with HSP/HFP!) 5. Device will still be greyed out in Device Preference. Unpair and pair device again. 6. Device will show up in Device Preference, but without audio. 7. Select Bluedio and press the Test button. 8. Test audio plays and now audio works.
I am not sure why both devices are treated differently, but it is certain that the Air-Fi is the more expensive device.
Thoughts? Is this Leap or TW? For leap, you may kindly join your experience here: https://bugzilla.suse.com/show_bug.cgi?id=991612
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 19 August 2017 21:03:13 +08 stakanov wrote:
Is this Leap or TW? For leap, you may kindly join your experience here: https://bugzilla.suse.com/show_bug.cgi?id=991612
TW. But it could work with Leap? No harm in giving it a shot.
participants (5)
-
Carlos E. R. -
Carlos E. R. -
Chan Ju Ping -
Jan Engelhardt -
stakanov