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
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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
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.
--
You received this bug
Just adding that after OTA13 the issue remains.
--
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/1578176
Title:
Cannot place or recieve calls when using in-car bluetooth
bug 1584362 have logs
several people with this problem are also in bug
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-
settings/+bug/1435040
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Looks like I have created a duplicate:
https://bugs.launchpad.net/ubuntu-rtm/+source/bluez/+bug/1584362
There are some logs attached.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
@mike-jelfs:
Please check if this bug also applies in your case:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Just to add with my Honda - CRV paired with my MX4 have similar issues
no sound, though pairs properly and syncs contacts.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
I should also add that *before* OTA9 the entire system worked
flawlessly, so this is likely related to the update to Bluez5.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
12 matches
Mail list logo
