Cannot place or recieve calls when using in-car bluetooth system

[Stunts]

After working around bug https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158 I was able to pair the phone (BQ Aquaris E4.5) with the car hands-free system.

However, thing don't quite work as expected.
I can use the car's system to place a call using the phone, but The audio is not getting properly routed. After placing the call, I can't hear any sounds (not even the "ringing" noise), I don't get any feedback after the other person has answered the phone, and the other person can't hear me either.

Furthermore, Long after the other person has hung up the call, the phone still looks like the call is ongoing (I have to manually disconnect it).

I can also use the system to answer an incoming call, but the sympthoms are the same. No audio on either end.

Would a debug log be helpful in this situation (https://wiki.ubuntu.com/DebuggingBluetooth)?
Or is something else required?

[Stunts (f-pinamartins)]

I should also add that *before* OTA9 the entire system worked flawlessly, so this is likely related to the update to Bluez5.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[BuffPuff (obelisk)]

I also experienced this since OTA 9 with my Parrot 9200 bluetooth handsfree, it would pair and connect, provide ringing alert, but no voice on both sides. Also no music streaming from the phone app.

When I go to the Parrot menu under "Bluetooth Audio" and manually choose to connect with the (already paird and connected) phone, all was working well, multiple calls, music, audio and GPS sounds.
So maybe it's not presenting itself as an audio capable bluetooth device anymore in the auto-negotiation?

[Mike Jelfs (mike-jelfs)]

Just to add with my Honda - CRV paired with my MX4 have similar issues no sound, though pairs properly and syncs contacts.

[Stunts (f-pinamartins)]

@mike-jelfs:
Please check if this bug also applies in your case:

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178

[Vincas Dargis (talkless)]

Looks like I have created a duplicate:
https://bugs.launchpad.net/ubuntu-rtm/+source/bluez/+bug/1584362

There are some logs attached.

[higuita (higuita)]

bug 1584362 have logs

several people with this problem are also in bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1435040

[Stunts (f-pinamartins)]

Just adding that after OTA13 the issue remains.

[Fred Vkigg (fvkigg)]

One interesting data point is that if you go into the bluetooth menu during the call and disconnect the device then the audio is correctly routed. I suspect the fundamental problem is the same for blue headset and speaker no be automatically routed when autoconnected.

[Stunts (f-pinamartins)]

Would it be interesting for debugging to have a verbose bluetooth log depicting the behaviour highlighted by @fvkigg ?
I can obtain that if there is a chance it can help solve the issue.

[Stunts (f-pinamartins)]

This looks a lot like bug #1546310
But in that case, there seems to be a fix released (OTA10 I assume). Just thought it could be interesting to have it linked here for reference.

[Stunts (f-pinamartins)]

Issue remains after OTA 14.
I have attached a syslog with verbose bluetooth and pulseaudio logs.
The log is trimmed to the reboot just before trying to place a call.
To further help, the device that fails to show audio name is "Honda HFT". I have attempted two calls, both failed to route the audio.
Although it is not in this log, if I ask the phone to transfer the audio to the phone's speakers, I can confirm that the call is taking place. It's just that the audio is not routed to the HFT system.