Ask Your Question
0

Can't use bluetooth headset anymore - FC23

asked 2016-02-11 08:48:34 -0500

Bruno Finger gravatar image

Since I first installed Fedora 23 on my machine, I got so amazed with it that I deleted all my Ubuntu/Linux Mint installations -- this time I've found a distro which things REALLY works!

This is my first problem: I have a bluetooth headset which always worked. All I need to do is pair it, connect it, then go to audio settings, select it as the output device and choose whether I want A2DP profile or HSP profile.

The problem is that for some reason now these profiles are not available to select, just "Analog Stereo Output", and you can guess that it doesn't work with bluetooth -- the notebook speakers are still being used as the audio output device.

I really don't know what changed that it doesn't work anymore, maybe an update? Maybe some file got written with settings that then were valid but aren't anymore? (after connecting to an HDMI display for example?)

How can I start to investigate this problem?

edit retag flag offensive close merge delete

Comments

Have you check with other bluethoot device, to see if bluethoot still works, it is posible that a new kernel was added on last update, reboot try older kernel and see if that works, if so it is posible that new kernel has no module for you bluethoot device.

aeperezt gravatar imageaeperezt ( 2016-02-11 09:00:37 -0500 )edit

Booting to kernel 4.3.3-300.fc23.x86_64 from 4.3.5-300.fc23.x86_64 and the problem still persists -- I remember that on this kernel, the bluetooth headset was working correctly, so the problem must be somewhere else?

Bruno Finger gravatar imageBruno Finger ( 2016-02-11 09:27:14 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-05-19 18:48:25 -0500

JoshN gravatar image
 same problem here, definitely non kernel. It just drops the whole headset as soon as some audio gets routed to it for some reason, but still shows as connected. Taking a look in the logs, it's complaining about a couple of odd things. the first one is that the headset is recognized by libinput as a keyboard XDDDD but doesn't seem to affect pulseaudio and the bluez module so that may be just a cosmetic issue. 
    Second one is that it keeps losing signal by timeouts and then is completely unable to regain connection. 
    I suspected it had something to do with the fact that my headset actually "exports" two different devices: a high fidelity audio device and the headset one for speaking and phone and whatever. So i've been playing with some options in pulseaudio and so far is working, although I'm not sure why yet. 
   - I'll try to do a bit of research and report here, but in case it takes a while, here is what i did: 
   - installed pavucontrol
   - turned bluetooth off and on so that it connects that first time. 
   - once connected, i went to pavucontrol and on configuration there they were, my bluetooth headphones. I selected the adecuate audio profile (in my case the high fidelity, not the hsp). 
   - shortly afterwards it disconnected again, so again i reset and went to pavucontrol, this time to output devices. 
    here in advanced i changed the latency offset to 0.002. 
   - it disconnected again, but this time, i had two different interfaces when i reset bluetooth. 
    picked the right one and it has been working ever since. 
    why, I couldn't tell. 
    If that also works for you before i figure it out I'll be quite interested in knowing, if only to see it has something to do with those things.
edit flag offensive delete link more

Comments

sorry for the werid formatting, accidental.

JoshN gravatar imageJoshN ( 2016-05-19 18:49:23 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2016-02-11 08:48:16 -0500

Seen: 2,033 times

Last updated: May 19 '16