Autoconnected BT headphones, but sound coming from phone speakers

General
#1

I have been using Urbanista Stockholm Plus Bluetooth headphones for two years, and they function as expected. Connects and disconnects from my Xperia 10 III when it should and so on.
Now I have gotten myself a pair of JBL Wave Flex. The problem is that they don’t act as they should.

Expected:

  1. Start headphones
  2. Pair
  3. Connect
  4. Sound coming from headphones
  5. Turn off headphones
  6. Turn on headphones
  7. Auto-connect
  8. Sound coming from headphones

Actual:

  1. Start headphones
  2. Pair
  3. Connect
  4. Sound coming from headphones
  5. Turn off headphones
  6. Turn on headphones
  7. Auto-connect
  8. Sound coming from PHONE SPEAKER

Solution: Forget headphones and re-pair.

I cannot reproduce the problem on two Android devices, only in Sailfish OS.

I have tried pairing using bluetoothctl but with the same result.

Any ideas why this happens and is this a known issue with or without workarounds? I know Bluetooth is a bit shaky in SFOS but I have not seen this particulary case though.

Thank you for your time! /klarre

#2
  1. you have to check if the correct profile is used (can be done in the gui Settings >> BT >> Type)
  2. you have to fix the profile/set up the headphones in the command line, where you can specify the profile, you want to connect - usually A2DP)

Alternatively:

  1. there is a tool AudioOutput - where you can choose the desired output (assumes you have A2DP in BT with the device)
  2. You can also wipe the directory /var/lib/bluetooth/ and reboot, but then all your devices will have to be paired and setup again.

I suggest try playing with the gui a bit.

#3

Hi deloptes,
thanks for catching up this post. Again a few months later, now I ran into exact the same plot like klarre (I also run Xperia 10 iii, since this night on Sauna: SFOS 4.6.0.13).

Also the workaround with unpairing and re-pairing works. But of course, this isn’t cool for everyday use.

I installed Audio Output Chooser from HenkKalkwater.

What I found: my bt-devive (a soundcore space A40) is shown as an audio sink in the Output tool, when it is freshly paired. After toggling bt (i.e. turn bt off and on again), the A40 pairs again as expected (bt-types: SDP, SPP, A2DP, AVRCP, HFP, PBAP, MAP, DID).

Same can be seen on terminal. After fresh pairing:

[defaultuser@Wahl ~]$ pacmd list-sinks|grep "device.description"
device.description = "Droid sink primary output"
device.description = "Droid sink deep_buffer"
device.description = "Null-Ausgabe"
device.description = "Soundcore Space A40"
[defaultuser@Wahl ~]$

After bt-toggling:

[defaultuser@Wahl ~]$ pacmd list-sinks|grep "device.description"
device.description = "Droid sink primary output"
device.description = "Droid sink deep_buffer"
device.description = "Null-Ausgabe"
[defaultuser@Wahl ~]$

For some reason the A40 is not re-registered as audio sink. Especially strange is, that this is not the case with other bt-devices on the same SFOS (my Xperia 10 iii). I can use a bt-box (Marshall) and my car audio system (Dacia) as expected (see post from klarre).

Any ideas or solutions are highly appreciated! :relaxed:

Thanks folks.

Cheers Simon

#4

I never managed to solve the problem but worked around it by writing a shell script that performed all the steps of unpairing and pairing each time I ran it. Unfortunately, I dropped my Xperia on the stone floor and it broke, so the script is gone and I cannot share it.

#5

I have the same problem, but with a usb dac headset

#6

:dizzy_face: oh no! Sorry for you!