[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
Ubuntu Touch is no longer supported. ** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel 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 Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Won't Fix 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/canonical-devices-system-image/+bug/1519809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Tags added: bluez-touch pulse-touch -- You received this bug notification because you are a member of Kernel 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 Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Fix Committed 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/canonical-devices-system-image/+bug/1519809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: ofono (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: Fix Committed => Invalid ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: ofono (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: ofono (Ubuntu) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Committed ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: ofono (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel 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 Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Fix Committed 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/canonical-devices-system-image/+bug/1519809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
There are two connections for HFP. One is the service level connection which is used for exchanging AT commands which is setup all the device the device is connected on HFP even if no call is active. This way we also accept/decline calls. The second connection is the actual SCO channel fo sending the audio data which is opened as soon as the headset_head_unit profile for the PA bluetooth audio card is set. -- You received this bug notification because you are a member of Kernel 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: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
With latest pulseaudio from silo 9 the call is routed correctly, but I still can't control the incoming call with the headset, and I hear the device ringtone, and not the headset one. My guess here is that HFP is only working during an active call, since I can hangup an active call with the headset button but I can't accept a call while it's ringing. I am attaching the syslog. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4527689/+files/syslog -- You received this bug notification because you are a member of Kernel 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: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Changed in: bluez (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel 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: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
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 Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Attachment added: "dbus.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525332/+files/dbus.log -- You received this bug notification because you are a member of Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
-- You received this bug notification because you are a member of Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525333/+files/syslog -- You received this bug notification because you are a member of Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
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 Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
Did you connect the BT headset when you were registered with a telephony network operator? -- You received this bug notification because you are a member of Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Attachment added: "cards.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525338/+files/cards.txt -- You received this bug notification because you are a member of Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Attachment added: "hciconfig.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525231/+files/hciconfig.txt -- You received this bug notification because you are a member of Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519809] Re: No sound is routed to bluetooth headset after a call
** Attachment added: "bluetoothctl.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525230/+files/bluetoothctl.txt -- You received this bug notification because you are a member of Kernel 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
