What happens here is now pretty clear:
The car gets disconnected but the rfcomm/sco channels aren't. Due to
that the audio card is still kept in PulseAudio which in turn lets the
UI think it can still use it.
However what is not clear yet is why this happens. The attached syslog
sadly doesn't show the point where the device disconnection happen. This
could be a problem in bluetoothd itself failing to handle a rfcomm/sco
channel disconnection or the kernel never sending the right event for
this.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
** Changed in: telephony-service (Ubuntu)
Status: New => Invalid
** Tags added: bluetooth
--
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/1487889
Title:
After disconnnecting from car bluetooth, audio is still routed to
bluetooth
Status in Canonical System Image:
Confirmed
Status in bluez package in Ubuntu:
Confirmed
Status in telephony-service package in Ubuntu:
Invalid
Bug description:
MX4 r96
This has been happening fro a few weeks
Phone automatically connects to the car, you don't have to make or receive a
call
Leave the car and disconnect
Place a call
The audio starts out using the phone as expected, after a few seconds the
audio switches to bluetooth
You can manually change the audio in the UI
This happens until you reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487889/+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
