Hi
I just bought the LBJ Flip3 to use with Mint18 Sarah. The problem is that it the speaker was paired but trying to get any sound out of it is a touch and go thing. It has worked and I have left all the settings intact but on reboot, it was back to square one. Physically plugging in the speaker was OK, its only when I try to get it with bluetooth that is the problem.

First of all, I would have thought it only needed to pair once and the will be connected automatically on startup or reboot and I won't need to go into System Settings/Multimedia to fiddle with any of the audio device settings again. I am totally stumped. The speaker works when its physically plugged in the LineOut audio jack but not on bluetooth. Is there something to do with Mint18??

I would really appreciate help/instructions on how to get the bluetooth working for once and for all.

Thanks so much

if you are using pulse look in pavucontrol and it has a drop down list box to select the out put. try that.

as far as connecting auto - I do not use Bluetooth enough in Linux so... some one else should be able to help you with that.

Thanks for the reply.
Yes I have pavucontrol listing the normal 2.1 speakers and the paired LBJ Flip3.
If the bluetooth is plugged in, its works fine. Only when I try to get it to work via bluetooth that it remained mute. It has worked a couple of times on the same settings, that is why i can't understand why selecting the output device doesn't work.

It just might be the order in which you go through the process from hook up to sound out. Because you've gotten it to work before. Just need to figure out in which order things go. for mute that is like a default setting on lot of systems. When one first boots and logs in it ia auto mute to prevent sound blasting in your ears or room.

My Debian testing has pulseaudio installed, I had to install pulseaudio-module-bluetooth to overcome this issue with a Bose SoundLink mini bluetooth speaker.

Also, if I remember, pairing my Bose SoundLink mini with other devices when Debian is not in use requires it to be manually paired again when trying to use it in Debian after, providing nothing is currently paired with it in which case it cannot be paired with Debian.