On Thu, 2009-12-31 at 17:02 +0100, Lennart Poettering wrote: > On Tue, 29.12.09 07:24, Ng Oon-Ee (ngoonee at gmail.com) wrote: > > > > > On Mon, 2009-12-28 at 16:09 +0100, Lennart Poettering wrote: > > > On Mon, 28.12.09 08:08, Ng Oon-Ee (ngoonee at gmail.com) wrote: > > > > > > > Hi, I've been using my Jabra Halo stereo (A2DP) headset with pulse and > > > > gnome-bluetooth for several months now, works great. > > > > > > > > A question though, does pulseaudio or gnome-bluetooth (not sure who'd be > > > > responsible for this) support the media keys (next track, previous > > > > track) on my headset, or on any bluetooth headset? I'd assume these keys > > > > are standard across headsets, since they all work on the same devices > > > > (bluetooth mp3 or cellphones etc.) > > > > > > bluetoothd forwards AVRCP key events to user applications by creating > > > a virtual input device (uinput) for it in the kernel. Applications > > > that handle /dev/input devices properly (such as X) should be able to > > > make use of it without any modification. > > > > I don't have any other /dev/input/by-id/* device created when connecting > > my headset. That would probably be the root of my issues. Perhaps I > > forgot a kernel compile option.... I believe this is OT for this list > > however? Who should I contact on this? > > a stock kernel should have everything that is necessary. > > you need uinput enabled in the kernel. > > the bluez folks should be able to help you. > > Lennart > Thanks for the specifics. Somehow uinput doesn't get loaded by default, so 'modprobe uinput' did the trick.
