Canonical System Image

No sound is routed to bluetooth headset after a call

Bug #1519809 reported by Tiago Salem Herrmann
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
In Progress
Undecided
Unassigned
bluez (Ubuntu)
Invalid
High
Simon Fels
ofono (Ubuntu)
In Progress
High
Simon Fels
pulseaudio (Ubuntu)
Won't Fix
High
Simon Fels

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.

Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :
Revision history for this message
Simon Fels (morphis) wrote :

Did you connect the BT headset when you were registered with a telephony network operator?

Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

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.

Revision history for this message
Simon Fels (morphis) wrote :

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
Simon Fels (morphis)
Changed in bluez (Ubuntu):
status: New → In Progress
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

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.

Revision history for this message
Simon Fels (morphis) wrote :

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.

Simon Fels (morphis)
Changed in bluez (Ubuntu):
status: In Progress → Fix Committed
assignee: nobody → Simon Fels (morphis)
status: Fix Committed → Invalid
Changed in ofono (Ubuntu):
assignee: nobody → Simon Fels (morphis)
Changed in pulseaudio (Ubuntu):
assignee: nobody → 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
status: Confirmed → In Progress
Daniel van Vugt (vanvugt)
tags: added: bluez-touch pulse-touch
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Ubuntu Touch is no longer supported.

Changed in pulseaudio (Ubuntu):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.