Comment 4 for bug 1013044
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I'm not seeing anything special in the module list that would hint at autoconnection of the new bluetooth devices, unless that's a new feature in a new PulseAudio or if you had compiled it yourself. Regardless, I can't reproduce this here with my laptop and Android phone (though it's using ICS)
It's still unknown to me why it autoconnects and reacts that way; since I'm not seeing that behavior. In all cases I'd expect that the sources and sinks would have to be connected in PulseAudio, which currently should mean manual intervention by a user, and something that doesn't survive a reboot.
On your phone, you may be able to go into the "advanced" settings for the bluetooth connection (long press, usually), and disconnect the multimedia part?
I'm opening a task for PulseAudio, in case one of the audio developers have an idea about what could be causing this?