Canonical System Image

Since Bluez5, headsets don't reconnect audio when reconnecting

Bug #1537737 reported by Michael Zanetti on 2016-01-25

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	Canonical System Image	Confirmed	High	John McAleely	Canonical System Image backlog
	bluez (Ubuntu)	Won't Fix	Undecided	Unassigned

Bug Description

Pairing a Bluetooth headset (A2DP) seems to work fine. After pairing, the phone successfully switches to transmit audio over Bluetooth. When disconnecting the Headset again, the phone successfully switches audio back to the integrated speaker. However, on a reconnect without pairing, the headset seems to connect properly, but it doesn't route audio any more to the headset. Despite the headset being connected, audio is still routed to the integrated speaker. A reboot does not seem to help. The only way to get back to Bluetooth audio streaming is to delete the device from the settings, and pair it again, which makes it work once again.

Tags:

Pat McGowan (pat-mcgowan) on 2016-01-25

Changed in canonical-devices-system-image:
assignee:	nobody → John McAleely (john.mcaleely)
importance:	Undecided → High
milestone:	none → backlog
status:	New → Confirmed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-03-04:

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

Changed in bluez (Ubuntu):
status:	New → Confirmed

Revision history for this message

TarotChen (tarotchen) wrote on 2016-03-07:

I can reproduce this on krillin-rc274 with following steps:

1.Pair a bluetooth speaker
2.Open the music app and play music
3.Turn off the bluetooth speaker (the playback pauses)
4.Wait a few seconds, then turn on the bluetooth speaker
5.Wait until the speaker reconnects
6.Tap on play button to continue playing

->the sound comes from the phone

7.Close music app
8.Launch music app to play music again

-> now, the sound is routed to Bluetooth speaker

Expected result:
The sound should be routed to bluetooth speaker after step 6

Revision history for this message

Alexandre Payet (alexandre-payet) wrote on 2016-08-01:

I can reproduce this bug on Meizu pro 5 rc-proposed and Nexus 4 rc-proposed (both last revision)

In my case if you disconnect manually from the bluetooth device and reconnect to it (in settings>Bluetooth>device name), then the sound is routed well to bluetooth device

Revision history for this message

Alexandre Payet (alexandre-payet) wrote on 2016-08-02:

log-bug-1537737 .zip Edit (84.0 KiB, application/zip)

Here some logs in attachment (I think in the first 10 minutes)

Explanation :

How it works :
1. Turn on the headset --> bluetooth connects automatically the headset (already paired in the past)
2. Make a call --> dialer-app show the bluetooth icon by default
3. No sound for the call (even in internal phone speaker), if you switch back to phone speaker option the sound is back in internal phone speaker
4. Switch back to bluetooth --> still no sound
5. Disconnect manually from headset and reconnect (in settings>Bluetooth>device name)
6. Make a call --> The sound is now routed to headset

How it should work :
1. Turn on the headset --> bluetooth connects automatically the headset (already paired in the past)
2. Make a call --> dialer-app shows the bluetooth icon by default
3. The sound is routed to the bluetooth headset

Alexandre,

Daniel van Vugt (vanvugt) on 2017-05-04

tags:

added: bluez-touch

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2018-11-12:

Ubuntu Touch is no longer supported.