Looks like I've found the reason for this. Seems to be the timing which is somehow different on your side to what I saw before. Will give some more details later today where to get the updated pulseaudio packages from to test on your side.
** Tags added: bluetooth-ota9 bluez5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1519809 Title: No sound is routed to bluetooth headset after a call Status in bluez package in Ubuntu: New Bug description: After the latest update to bluez5 no sound is routed to the connected bluetooth headset after a call is ended. Steps to reproduce: 1) connect a bluetooth headset 2) Receive a call 3) End the call 4) Try to play music Expected behavior: Music is routed to the connected headset Current behavior: No sound is routed, although music player behaves as it was playing normally. Additional info. If you receive a second call, the audio is again routed normally to the headset after it's finished. Just tried with old images with bluez4 and it works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp