[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bluetooth headphones mistaken for a keyboard!?!



Mark Fletcher wrote:

> On Fri, 2016-03-04 at 11:08 +0100, deloptes wrote:
> 
>> So what I would do is to check the profiles reported via the hcitool
>> It would be most probably A2DP.
> 
> When I run hcitool info on the headphones I get:
> 
> $ hcitool info XX:XX:XX:XX:XX:XX
> Requesting information ...
> BD Address:  XX:XX:XX:XX:XX:XX
> OUI Company: Bang & Olufsen A/S (00-09-A7)
> Device Name: BeoPlay H8
> LMP Version: 4.1 (0x7) LMP Subversion: 0x2812
> Manufacturer: Cambridge Silicon Radio (10)
> Features page 0: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
> <3-slot packets> <5-slot packets> <encryption> <slot offset>
> <timing accuracy> <role switch> <hold mode> <sniff mode>
> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
> <power control> <transparent SCO> <broadcast encrypt>
> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
> <interlaced iscan> <interlaced pscan> <inquiry with RSSI>
> <extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave>
> <AFH class. slave> <LE support> <3-slot EDR ACL>
> <5-slot EDR ACL> <sniff subrating> <pause encryption>
> <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps>
> <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended inquiry>
> <LE and BR/EDR> <simple pairing> <encapsulated PDU>
> <non-flush flag> <LSTO> <inquiry TX power> <EPC>
> <extended features>
> Features page 1: 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00

I can not check at the moment. I have not tried to configure headset. I did
a lot with mobile phones and recall there was a2dp. I'll try to check later
on that.

> 
> (Address elided just in case I should care about that)
> 
> "sdptool records" gives me the following profiles supported (scraped
> from the output, can post it all if it helps):
> 
>   "Handsfree" (0x111e)
>     Version: 0x0106
>   "Headset" (0x1108)
>     Version: 0x0102
>   "Advanced Audio" (0x110d)
>     Version: 0x0103
>   "AV Remote" (0x110e)
>     Version: 0x0105
> 
> I suspect that "Advanced Audio" is the one I want...

Yes it looks like 
https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles#Advanced_Audio_Distribution_Profile_.28A2DP.29

> 
>> Next is to find out how to configure udev to map the profile to an
>> output.
> 
> Uh... yeah. Unfortunately I am not sure what that means. Does that mean
> create new udev rules? Know of any good resources I can use to learn how
> to do that? I imagine I am gonna need that 0x110d code though, right?

https://wiki.archlinux.org/index.php/Bluetooth_headset

yes, perhaps check this article here (section: Legacy documentation: ALSA,
bluez5 and PulseAudio method) - seems a big discussion and article had some
critics, but there are few ideas on how to setup udev rules
example
$ bluetoothctl 
produces output with UUID

> 
>> Jessie stock is 3.16 - it could be worth trying something newer - live
>> ubuntu pre release or so. Not only because of the kernel, but because
>> udev could be smarter.
> 
> The headphones are about a year old -- I mean this product has been on
> the market for about a year, this particular pair is brand new -- does
> that make any difference? I am willing to try a newer kernel if you
> think it will really make a difference.

No difference - question is the level of support by the OS. I must admit
that before bluez5 all this BT related stuff was a nightmare.
The good thing is that BT devices are more or less standard, so the question
is how good is linux for the B&O product.

> 
>> I had to install blueman in order to easily configure bluetooth devices
>> in gnome on jessie recently. And I read that A2DP is located now in
>> gstreamer ... pulse something package (bluez5).
>> 
> 
> Now that's interesting -- you are not the first person to recommend
> Blueman since I started looking into this but I installed Blueman the
> other day and don't see it telling me anything remotely useful that the
> gnome bluetooth applet doesn't, except for signal strengths etc which
> seem to be strong / optimal but aren't actually helping. Am I being
> stupid?
> 
> I don't see A2DP in the list of profiles -- unless that is "Advanced
> Audio"?

I think blueman helped me somehow get the proper profile loaded for the
phones I tested with

> 
> And gstreamer is installed. I see a lot of packages for gstreamer and
> they aren't all installed, but the ones that look important to me are.
> Specifically gstreamer-1.0-pulse is installed.

what about pulse-bluetooth ?

> 
>> I think you misinterpret the messages - it is normal that you get
>> keyboard as input, because there are buttons you press to control the
>> device. The problem is you are missing the audio link. So there is a
>> missing part - not wrongly configured one. I would say this part is
>> correctly configured, but the audio link is not configured at all.
>> 
> 
> Ah, I see, that makes sense I guess.
> 
>> However it could be also that the expensive brand "Bang & Olufsen"
>> provided you with a CD with windows drivers for something not supported
>> in linux - this would be your worst case.
>> 
> 
> It came with a small USB cable for charging, a regular audio cable for
> situations where Bluetooth is not allowed, a manual in about 10
> languages, and that's it. No Windows drivers. It's a pair of headphones
> primarily designed for use generically with bluetooth enabled devices,
> not primarily designed for use with a computer specifically. And I've
> been using them connected to my iPhone while writing this, and I have to
> say they are sweeeeet. So I am glad I bought 'em even if it takes me a
> few days to get them working with my PC.

Thats good - you could use a windows pc to see how the headset is recognized
and configured. You know windows provides a driver database online - who
knows if they do not relay on that db.

> 
> (Obviously I was not expecting them to work with my PC while they were
> being used by my iPhone, I am not _that_ stupid :-) )
> 

yes sure

>> 
> 
> Thanks for your ongoing help, I appreciate you taking the time.
> 

nothing special I just spent half a day few months ago setting up mobile(s)
for sync project ... and it was an interesting journey from BT perspective.
I thought I could help a bit - of course the best would be to have someone
who has done this with same or similar product.
This article was enlightening:
http://www.lightofdawn.org/blog/?viewDetailed=00031

I think you could fix this with proper udev setup though, but still it
depends and I can not make promises - it could be you need some extra
software

regards


Reply to: