touch-packages team mailing list archive

[Tiago Salem Herrmann <tiago.herrmann@xxxxxxxxxxxxx>]

Looks like the bug is easily reproducible when the device gets connected before it's registered to the network, but I was able to reproduce the problem after connecting it manually after it's registered as well, but in this case, not always reproducible.
One thing I noticed (not sure if related) is that sometimes I get the ringtone as a2dp, sometimes I don't get nothing, and the device supports hfp, but it doesn't work on bluez5 as it seems. It does work on bluez4.

-- 
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