I tried to reproduce this under similar conditions with a headset as I don't have access to any carkit at the moment but didn't had success. There are two possible reasons for this:
* the device doesn't get disconnect any stays connected as device for bluez * the device disconnects properly but the upper stack (telepathy-ofono, telephony-service, pulseaudio) doesn't recognize this correctly I will try to get this reproduced next week with my own carkit at home. Tiago also mentioned there was a major rework of the code part in telepathy-ofono recently (ota6?) handling these things. He will attach a package without this rework included to let us verify if this is the reason for the behavior we see here or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service 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 telephony-service package in Ubuntu: New 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/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
