Bluetooth headset connecting, but not working at all after 5.0.x -> 5.1.0x upgrade

[rsoto]

REPRODUCIBILITY: 100%
OS VERSION: 5.1.0.8
HARDWARE: Xperia 10 II
UI LANGUAGE: French
REGRESSION: Yes

DESCRIPTION:

Bluetooth headset/headphones which were working perfectly until and including 5.0.x can be paired and connected to the phone, but there is no audio output.

PRECONDITIONS:

Install 5.1.0.8, pair and connect the bluetooth headset, then try to use it, e.g. play some music

STEPS TO REPRODUCE:

1. Install 5.1.0.8 on Xperia 10 ii via Settings

2. Connect the bluetooth device (or delete it and pair it again, no change)

3. Try to play something (anything) from the phone, such as music or videos

EXPECTED RESULT:

Audio output from the headphones

ACTUAL RESULT:

Audio output still from the built-in speaker, not the headphones

MODIFICATIONS:

None. Installing or uninstalling the AppSupport Bluetooth app from the Jolla Store changes nothing about this behaviour

ADDITIONAL INFORMATION:

I already tried:

• Rebooting
• Unpairing and re-pairing of the Bluetooth device
• Changing the ‘class’ of the Bluetooth device back and forth (Headset/Multimedia, etc)
• Installing and uninstalling AAS Bluetooth
• Connecting and disconnecting the Bluetooth device every now and then
• Restarting obex: systemctl --user restart obex

To no avail

[jojomen]

Thank you for the report! It would be useful if you could provide some logs. I’m assuming you use the headset exclusively in SFOS, but did you install the new AppSupport Bluetooth?

Also, I think having some logs would help developers. Even if you didn’t install AAS Bluetooth, you will find good instructions here:

AppSupport Bluetooth feedback thread

Hi, The Bluetooth bridge for AppSupport is finally in a fairly stable shape, so it is now available in the Jolla Store for cbeta users only. How much further it goes, and how quickly, depends on your feedback. IMPORTANT: Don’t install this on an Xperia 10V. See the note below for details. What it is The AppSupport Bluetooth Bridge shares the phone’s Bluetooth controller between Sailfish OS and AppSupport. It acts as a router, so each Bluetooth device can be handled by either Sailfish OS or Ap…

[rsoto]

Hi! Thanks for the reply. Would you mind elaborating on which logs I should provide?

95% of the time I use the headset with SFOS, so I haven’t really tried the AppSupport stuff yet

[jojomen]

I’m not the expert, and I just realized the link I gave you is specific to AAS Blutetooth.

Pinging @abranson for assistance.

[abranson]

Just a hunch, but did you try to manually start obexd as described in the release notes? That seems to have a broader impact than we first thought.

[rsoto]

Thanks for the hint, but nope. I just updated the ‘Additional Information’ section on my original post to reflect this.

[rolandtreiber]

I’m experiencing this too on 5.0.0.76 Jolla C2 however it works for me once after pairing.
The symtoms:
Connecting a bluetooth headset (Soundcore P3i), works as expected.
Disconnect → Reconnect → Shows as connected but no sound is going through the headset.
I’m very new to Sailfish and the phone itself (received it yesterday), so happy to extract logs and give more context, but pls tell me the steps. (I’m familiar with arch based desktop linux distros, so not completely a newbie )

Update:
It doesn’t appear to be an audio sink selection issue but a bluetooth discoverability one.
Upon freshly connecting the headset, it shows in the list, but once reconnecting, it no longer shows.

Restarting the bluetooth subsystem seems to be a valid workaround, albeit a very inconvenient one.