# Paired w/o functioning w ultra ear bluetooth speaker

Today i paired (Jolla 1; Build 2.1.1.24) with Ultra Ear Boom 2, but w/o success of further functioning (no sound ).

With other Bluetooth speakers I was having variable success. For example, with SONY SRS-XB30 it was functioning but the volume was very low (similar dimmed as the speaker of Jolla itself). While with JBL Charge 3 it functioned impeccable .

Any idea what was wrong?

What is your experience with Bluetooth speakers?

UPDATE:28.08

The only notable difference between the non-working speaker UE Boom 2 and the working speakers SRS-XB30 and JBL Charge 3 is that Boom 2 is recognized as a headset (at least from the icon), while the other ones as speakers. This is maybe due to the fact, that Boom 2 doesn't support a HSP profile ?!?

Just discovered the quote below in this post [pulseaudio-discuss] Adding support for bluetooth headsets that only have HFP:

Ultimate Ears fails to work with pulseaudio because we only support HSP via the native backend

So, if HFP is only supported wiht ofono, and the device is recognized as a headset, it won't connect. So, why is the loudspeaker recognized as a headset ?!?

The supported profiles are as follow:

Boom 2 : SPP, A2DP, AVRCP, HFP, DID

SRS : HSP, A2DP, AVRCP, HFP, DID

JBL : SPP, HSP, A2DP, AVRCP, HFP, DID

edit retag close delete

Bluetooth is one of the things I find working very reliable with Jolla sbj1.

I have used many models of BT headsets and BT speakers, and pairing and audio work very well.

( 2017-08-19 21:43:26 +0300 )edit

@juceme : well, there are now the UE bloothspeakrs with which it doesnt work reliable ...

( 2017-08-20 10:27:43 +0300 )edit

@HeinrichJolla, an excellent find!

I was not aware that bluetooth layer exports the whole range of supported BT profiles to pulseaudio; somehow I naively thought that channel selection and handling would be done in BT and it would only interface to PA with simple sink/source layer...

I wonder why PA cares about whether the device has HSP/HFP capabilities since it is a speaker anyway when the only thing that's ever used is probably A2DP...

The posting you found about the patch to support HFP-only devices in PA is about an year old, so I wonder if most recent PA versions have this fixed?

( 2017-08-29 08:46:10 +0300 )edit

And as it seems, this indeed has been fixd in PA; https://github.com/pulseaudio/pulseaudio/commit/e1dc75da99afa211465ff8b721ab8f85129226bd

This means it should be available in pulseaudio v10.99.1 release. In SFOS 2.1.1.26 it seems to be pulseaudio-8.0+git12-1.25.2 which I suppose is a bit too old :)

I wonder if you could try to update PA to see if it works? (however losts of things might break...)

( 2017-08-29 09:09:15 +0300 )edit
1

@HeinrichJolla: Great investigation \o/ @juiceme: pkcon get-details pulseaudio gave me pulseaudio-8.0+git5-1.21.2.armv7hl [installed] and the UE Boom 2 is working just fine. (Also recognized as a Headset by the way, exactly as in the questions screenshot )

( 2017-08-30 11:07:17 +0300 )edit

Sort by » oldest newest most voted

i had the exact same problem. Sailfish 2.1.1.24 EA on jolla 1 and jolla tablet with an UE Boom 2. Paired successfully but sound came still from the devices' speaker. As far as I could dig into it, there might be a problem with pulse's bluetooth sink. I could get both, phone and tablet to work with the ue boom by reverting to Sailfish 2.1.0.11 described here: https://together.jolla.com/question/50986/howto-how-to-revert-to-an-earlier-sailfish-os-version/?answer=51003#post-id-51003

more

@Helge : if the reason would be the "pulse's Bluetooth sink", why would other Bluetooth speakers work without problems ?

( 2017-08-23 15:20:04 +0300 )edit

I didn't knew that other bluetooth speakers work. It would be interesting which speaker are functional and what profiles they use. Maybe its profile dependant problem.

The UE Boom uses SPP, A2DP, AVRCP, HFP, DID.

Edit: In this thread: https://together.jolla.com/question/160625/does-jolla-1cintex-hardware-support-a2dp-sink-role/ i thought i found someone with the same problem and tried my luck with "pulsetunnel" but nothing led to the desired result except reverting to the official sfos release.

( 2017-08-23 19:05:12 +0300 )edit

@Helge: as written in my main post: It worked with both SONY SRS-XB30 and JBL Charge 3. With SRS-XB30 the sound was very low, but with JBL Charge 3 it worked perfectly.

So, its a very strange problem.

( 2017-08-25 00:14:11 +0300 )edit

yes, i didn't knew (until your post). Since we have knowledge about some devices working properly and some working bad or even aint working it would be interesting to research the differences of these devices, so that someone smarter than me gets useful informations that could lead him to solve the problem. You could update your question with the supported profiles of your BT Speakers. (On the Jolla: Settings > Bluetooth > turn on Bluetooth and longpress the connection > "show device settings"

( 2017-08-25 02:02:07 +0300 )edit

Dear people! My UE Boom Box is now bluetoothing again! \o/

I updated Sailfish (3.0.3.10) and the Box (10.something). The Profiles read now: SPP, HSP, A2DP, AVRCP, HFP, DID

The Box-Firmware Update did it I think, as HSP was not enabled before. So, check out the firmware update either per app or there is also a windows and mac software available at the support page of ue (scroll all the way down).

Hope you are lucky!

more