Comment 48 for bug 1181106
Revision history for this message
| Sergio Costas (rastersoft-gmail) wrote Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) | #48 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi all:
I have exactly the same problem as everyone, and tried everything commented here without success. But I found a way of doing it work, which maybe helps to fix the error:
* Paired my headset, but didn't set it as trusted. Restarted the bluetooth service (did this only once, not every time I want to connect your headset; is just to set it in a know state).
* Now, every time I want to use the headset, I turn it on. Bluetooth icon in gnome will briefly show as connected, but returns to disconnected (because it detected the paired device, but, as it is not a trusted one, will no connect automatically to it).
* Wait about ten seconds until I hear a little "pop" in my headset (I suspect it is when, after waiting a connection, it puts in some kind of sleep mode to save battery)
* Now I can go to the bluetooth icon and set A2DP mode, and everything works fine.
If I try to connect it before that status change, the headset will stuck in HSP/HFP mode and will refuse to change to A2DP mode.
But there is a case when this fails: sometimes, when turning on the headset, Gnome shell shows a popup and asks me if I want to accept the connection. In that case, no matter if I accept or deny it, waiting to hear the "pop" doesn't work: it will also remain stuck in HSP/HFP mode.