Re: Bluetooth headphones mistaken for a keyboard!?!
Mark Fletcher wrote:
> I took delivery of a very nice pair of Bang & Olufsen BeoPlay H8
> bluetooth headphones yesterday. I've verified they work properly by
> connecting them to my iPhone.
>
> When I try to connect them to my PC, I am not having so much luck. PC is
> a 7-year-old self-built desktop box running Jessie with Gnome as the DE,
> with Intel Core i7-920 CPU and 24GB RAM. Bluetooth capability comes from
> a rather younger (bought about 6 months ago) bluetooth USB dongle which
> I routinely use to connect my iPhone and Android tablets to the computer
> to play audio from them through the computer's speakers. So I know it
> works fine too.
>
> Turning on bluetooth from the gnome applet, and putting the headphones
> into pairing mode, the computer quickly finds the headphones. When I ask
> the computer to connect it quickly does so, apparently successfully, and
> I hear the tones in the headphones indicating they too know they are
> connected. But, pulseaudio doesn't recognise a new audio sink has been
> installed -- and I don't blame it, because of the below.
>
> Looking in the Gnome Log Viewer in messages, at the moment of connecting
> the headphones, I see this:
>
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) config/udev: Adding input
> device 00:09:A7:09:BE:22 (/dev/input/event17)
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) 00:09:A7:09:BE:22:
> Applying InputClass "evdev keyboard catchall"
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) Using input driver
> 'evdev' for '00:09:A7:09:BE:22'
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) 00:09:A7:09:BE:22: always
> reports core events
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) evdev: 00:09:A7:09:BE:22:
> Device: "/dev/input/event17"
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (--) evdev: 00:09:A7:09:BE:22:
> Vendor 0 Product 0
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (--) evdev: 00:09:A7:09:BE:22:
> Found keys
> Mar 4 08:07:17 kazuki kernel: [382097.651490] input: 00:09:A7:09:BE:22
> as /devices/virtual/input/input30
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) evdev: 00:09:A7:09:BE:22:
> Configuring as keyboard
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "config_info"
> "udev:/sys/devices/virtual/input/input30/event17"
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) XINPUT: Adding extended
> input device "00:09:A7:09:BE:22" (type: KEYBOARD, id 13)
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_rules"
> "evdev"
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_model"
> "pc105"
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_layout"
> "jp,us"
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_variant" ","
> Mar 4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_options"
> "grp:alt_shift_toggle,grp_led:scroll"
>
>
> That doesn't look healthy. First of all it is detecting an INPUT device,
> presumably the headphone controls for volume and so on, and no OUTPUT
> device. Second, it seems to think that what it has found is a keyboard.
> Pulseaudio can, it seems to me, be excused for thinking a keyboard has
> been added and not being accustomed to playing sound through a
> keyboard... :-)
>
> I'm thinking this could be a udev problem of some kind -- perhaps I am
> missing appropriate udev rules? I am not sure how to diagnose the
> problem from here, far less fix it, so any advice would be appreciated.
> Google has, unusually, turned up zilch.
>
> Thanks in advance
>
> Mark
Which version of debian are you on and which kernel?
You may need to tell udev what kind of device it is, but we don't know if
your system is configured properly
check following articles - the second one is more practical, where you can
test pulse against the headset - I couldn't find any information on that
head set and linux except that head set is pretty expensive
https://lwn.net/Articles/531133/
http://jfcarter.net/~jimc/documents/blue-music-1504.html
I hope this helps
regards
Reply to: