Closed Bug 850172 Opened 13 years ago Closed 13 years ago

Unable to connect to bluetooth speaker (Bose Soundlink II + Logitech Wireless Speaker Adapter)

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::Settings
Platform:
Other
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 807758

People

(Reporter: djst, Assigned: shawnjohnjr)

Details

The Unagi phone was able to discover my bluetooth speaker and pair it (see screenshot: http://farm9.staticflickr.com/8106/8539482276_59273448f0.jpg), but when trying to connect to it, it showed an error message saying "Check that the device you're trying to connect to is still in range and has Bluetooth turned on". See screenshot: http://farm9.staticflickr.com/8367/8538373037_ea90e44890.jpg I tried a number of times but it never worked. Maybe we aren't supporting speakers/headsets yet? If so, the error message should probably be more precise here since it's not an issue of range. Tested on B2G 1.1.0.0-prerelease, 03/08/2013 10:55PM
Component: Gaia::Bluetooth File Transfer → Gaia::Settings
Assignee: nobody → shuang
Bose Soundlink II only supports Bluetooth A2DP profile. B2G currently does not support it. There is hack version you can try to support for temporary purpose. https://github.com/shawnjohnjr/releases-mozilla-central/tree/AVRCP1_3-Test
Regarding error message incorrect, it is because current Setting only checks "class of device" value, which only provide information "audio" device, but it lacks of Bluetooth SDP information which really tells what profiles that remote device supports. It made an assumption that every "audio" category device supports HFP profile. For FFOS v1, it only blindly connects to HFP profile. However, bluetooth speaker only supports A2DP profile, so HFP profile fails to connect. If we want to fix it, we need to do SDP query and properly indicate A2DP profile was not been supported.
(In reply to Shawn Huang from comment #2) > For FFOS v1, it only blindly connects to HFP profile. However, bluetooth > speaker only supports A2DP profile, so HFP profile fails to connect. > If we want to fix it, we need to do SDP query and properly indicate A2DP > profile was not been supported. Ah, so I assume that we plan to support the A2DP profile at some point in the future, but we don't now. Thanks for the explanation! Feel free to dupe this bug if there's already an existing bug about adding A2DP profile support.
Mark it as duplicated
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.