Re: [pulseaudio-discuss] Media Keys on Bluetooth headsets?
On Tue, 29.12.09 07:24, Ng Oon-Ee (ngoo...@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 (ngoo...@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 -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Media Keys on Bluetooth headsets?
On Thu, 2009-12-31 at 17:02 +0100, Lennart Poettering wrote: On Tue, 29.12.09 07:24, Ng Oon-Ee (ngoo...@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 (ngoo...@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. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Media Keys on Bluetooth headsets?
On Mon, 2009-12-28 at 01:28 +, Matthew W. S. Bell wrote: On Mon, 2009-12-28 at 08:08 +0800, Ng Oon-Ee 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.) The Linux kernel input layer is responsible for handling Bluetooth AVRCP. Whenever, an AVRCP device is connected an appropriate input event device should appear; one can use 'lsinput' to list input devices. I believe that hald-addon-input then processes these events and emits DBUS 'ButtonPressed' events. In the case of GNOME, I believe these are then picked up by gnome-settings-daemon, and emitted as X key-presses. One can use 'dbus-monitor --session' to see the events. Matthew Thanks for your response, Matthew. First off, I don't have lsinput anywhere on my system, I suppose you mean 'lshal' instead? Any idea what I should be looking for there? And I do have hald-addon-input and gnome-settings-daemon running, but dbus-monitor --session doesn't show anything (not even when I connect the BT headset, which is weird and perhaps indicates something wrong with my system?) Ideas are appreciated. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Media Keys on Bluetooth headsets?
On Mon, 28.12.09 08:08, Ng Oon-Ee (ngoo...@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. Note however that there is currently no way in X to map keypresses to the devices they originate from. That means that volume change keypresses do not necesarily change the volume of the device they were triggered from. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Media Keys on Bluetooth headsets?
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.) So, is there any specific setup I need to do to get them working? The only reference I could find when trawling the web is http://noraisin.net/~jan/diary/index.php?s=pulseaudiosubmit=Search who says it 'just worked'... ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Media Keys on Bluetooth headsets?
On Mon, 2009-12-28 at 08:08 +0800, Ng Oon-Ee 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.) The Linux kernel input layer is responsible for handling Bluetooth AVRCP. Whenever, an AVRCP device is connected an appropriate input event device should appear; one can use 'lsinput' to list input devices. I believe that hald-addon-input then processes these events and emits DBUS 'ButtonPressed' events. In the case of GNOME, I believe these are then picked up by gnome-settings-daemon, and emitted as X key-presses. One can use 'dbus-monitor --session' to see the events. Matthew signature.asc Description: This is a digitally signed message part ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
