My bluetooth headset, Sony sbh60, was easily recognized by openSUSE 42.1 (Plasma 5 desktop). However, I can hear no sound. Any ideas?
What have you tried ?
Nominally in openSUSE gnome and kde, with Leap-42.1, pulse audio will be active. In this case, sound can be controlled on a multimedia application basis with the pulse application “pulse audio volume control” (pavucontrol) including sending the sound from any application to the selected audio output device of one’s choice.
Have you attempted to configure pulse audio (with pavucontrol) to send the sound from your application of choice to your bluetooth headset ?
.
Thanks for your comment. I did as you said and was able to play sounds through my headset. However, the sound is not continuous; that is, there are lots of on-and-offs. Any ways to fix this?
Using pavucontrol, I managed to configure the sound just right by changing the profile from HSP/HFP to AD2P. The problem is solved now. Thank you so much, @oldcpu.
Glad to read of your success. Thankyou for sharing your solution.
.
as an aside… My wife has the same headphones. If the battery is only partially discharged the headphones will pair up and appear to be functional, but there will be no sound. Simply recharging resolves the issue. I lost a lot of time wandering down blind alleys trying to tweak her software before I figured that one out.
Thanks to you all. Had the same problem with my Samsung Level U Pro ANC (7CFD) Bluetooth headset. After reading this and changing the Profile I could finally hear music through the headset.
Thanks again,
-Chuck
I hate updates and my bad memory. I accepted the latest updates… a few days ago and now I can not connect to my Samsung Bluetooth. I mentioned that all I had to do before was make changes to my profile. Well, after these updates I can not find the correct profile nor can i get the system to scan and look for my Samsung Bluetooth headset. Any suggestions or directions???
I am still having trouble connecting. I can power up and not see the Bluetooth symbol and then re-start and obtain the bluetooth symbol. However, I click on connect and it says “the device is unreachable”. As I stated in the Jan 5th message I was able to get connected by changing the profile in Pulse Audio Volume control but now I can not get connected. (In a previous message I said I couldn’t remember witch profile but it was in PAVC) I searched hi and low to find out what Bluetooth connectivity my system has and it is a Broadcom BCM943142HBMPFXH_2. For my latest attempt at fixing this, I installed the b43legacy-firmware. That did not do a thing. It worked before I accepted the updates after Jan 5th.
Anyone more familiar with this Bluetooth communications … your help would be appreciated.
Thanks,
-Chuck
I am no Bluetooth expert. Just the contrary as I typically find Bluetooth to be challenging. Further I am sorry to read of the problems some have wrt Bluetooth and their LEAP.
But having typed the above, I did want to post to note in this thread that not everyone has such problems.
Out of curiosity, I just paired now my Toshiba Satellite Z930 laptop’s bluetooth with my relatively inexpensive QY7 bluetooth headset. My laptop is running openSUSE-42.1 LEAP with the 4.4.49-16-default kernel, and KDE Plasma-5.8.3. After pairing i did have to go to pavucontrol and re-direct the audio from the multimedia application to the Bluetooth headset. But overall, it works well.
I hope those in this thread who are struggling find a solution to their problem.
Well, thanks ‘oldcpu’ (I’m now 70 by the way ;)). Your responses are always welcome. And you did help in the previous message concerning the pavucontrol. I used that back in January and got it to work but this time even though it is seen it won’t connect. Says “The device is unreachable” whether I have it on or off. Now then, I must be off to work but perhaps you could give some pointers as to finding out just what got UpDated in openSuSE between Jan 5th and now. I’m sure that there is a way but I don’t remember.:shame:
Thanks,
-Chuck
I do not see anything even close to resembling that - so someone who is familiar with encountering and solving such an error needs to chime in.
In my case, with KDE, when in the Bluetooth icon I click to “add” a new bluetooth device, it simple scans and scans and scans. Its not enough then to switch on my headset (the first time) but rather I then need to hold on to a button in my headset long enough to put the headset in pairing mode. At that point the headset will show up in the KDE list of viewable bluetooth devices while it is scanning. I then select that device, click on Next, and I get the paring. Then I need to configure the applications to work with the bluetooth headset using pavucontrol.
I also made my KDE bluetooth viewable - although I do not know if that critical.
Yes, that is what I did the first time. However, after the UpDates it didn’t work. I need to find out what was changed after Jan 5th, 2017 that affects the Bluetooth. I’ve started the Blue-devil app and it scans but never finds anything. I click on the Bluetooth symbol on the status line to bring up the configuration, click on Connect and all I get is that it is unreachable. Yes I have started the Bluetooth on my Samsung headset before and after trying the Connect. My Samsung device is listed in the KDE config but all I am getting is that it is unreachable when I click on the Connect.
When I did the first hook up in January, I had to use pavucontrol to get it to work -but- now it does not see it either.
Hello still fighting with this. The system, Leap 42.1, still “sees” my Bluetooth device. I can click on the Bluetooth symbol in that task bar and it will list my headphone. In the dialog box that gets presented I get the following:
Samsung Level U Pro ANC (7CF0) Connect
Audio Device
Address 30:C8:FB:04:7C:F0
Paired: Yes
Trusted: Yes
Adapter: Dakotah-17.TRCompu (hci0)
The “Connect” appears when I mouse over that line. I click on it and get a reply of “Connection to the device failed” or “The device is unreachable”.
Anyone have any suggestions?? Bluetooth should be Bluetooth. I don’t believe that there are specific drivers for any of the devices… I can connect via my Windows 10 part. I have a dual boot machine.
In the config notations it mentions the “pin” but I have not been asked for one nor can I find any place to enter one. The pin is the number in () and the last 4 of the address.
Thanks in advance,
-Chuck
Did you do the pairing? was it successful?
Yes… I forgot to put code tags around my last message. (a senior moment)
This is what the dialog box shows when I click on the Bluetooth Symbol in the task bar. The “Connect” is actually not in red. It appears and disappears when I move my mouse over it. Also it is a button. Couldn’t co-ordinate a screen shot.
Available devices
Samsung Level U Pro ANC (7CF0) Connect
Audio Device
Address 30:C8:FB:04:7C:F0
Paired: Yes
Trusted: Yes
Adapter: Dakotah-17.TRCompu (hci0)
I assumed that the above meant that it was paired. Is there someplace else I should look??
Thanks,
-Chuck
Well darn… I thought AFTER I sent thelast message…
I just turned on the headset and clicked on the Connect. I got a message box that stated:
Samsung Level U Pro ANC (7CF0) (30...
Connection to the device failed.
I could not read past the 3 dots so I do not know what else it says.
Well, I really do try to fix these things myself and I found this:
> bluetoothctl
[NEW] Controller 60:6D:C7:CF:6F:C6 Dakotah-i7.TRComputing [default]
[NEW] Device 30:CB:F8:04:7C:FD Samsung Level U Pro ANC (7CFD)
[CHG] Device 30:CB:F8:04:7C:FD Connected: yes
[CHG] Device 30:CB:F8:04:7C:FD Connected: no
[bluetooth]#
What you are seeing is my clicking on “Connect”, it connecting and then almost immediately disconnecting…??
Thanks,
-Chuck
This problem has apparently been around for a while. Not only on our SuSE but on the others as well. In my searches on the net I found one of our own reports.
The following is a link to it. No I haven’t tried everything yet but I did want to share with others what I have found in case it brings thoughts to a knowledgeable person.
Will let you know after I try this stuff. Right now I must walk my dog. He has been my wonderful interruption(s) for the past two years. A fine GSD/Husky.
Thanks,
-Chuck
In response to my own message… NO. Nothing has “fixed” the problem yet. I am paired, trusted and on, but it connects and then almost immediately disconnects.
ctaylor@Dakotah-i7:~
> bluetoothctl
[NEW] Controller 60:6D:C7:CF:6F:C6 Dakotah-i7.TRComputing [default]
[NEW] Device 30:CB:F8:04:7C:FD Samsung Level U Pro ANC (7CFD)
[CHG] Device 30:CB:F8:04:7C:FD Connected: yes
[CHG] Device 30:CB:F8:04:7C:FD Connected: no
I believe in order to fix it I am going to have to dump all the updates since January 5th… but I don’t know how to do that. 