Hi Johan,

2007/11/22, Johan Hedberg <johan.hedberg@gmail.com>:
> I don't think there is any proper documentation yet. bluez-utils-3.22
> has some preliminary AVRCP support but by default it's disabled. You
> need to add a line "Enable=Control" to the General section in
> /etc/bluetooth/audio.conf to enable it. Currently no D-Bus signals or
> or methods are supported. Instead, the audio service uses the kernel
> uinput interface (you need to have the uinput module loaded) to inject
> keypress events to the kernel input subsystem. You can see what kind
> of AVRCP->keycode mappings are used by looking in the audio/control.c
> file from bluez-utils.

Thanks, now it works great!

One more question: what was the reason to use

KEY_NEXT and KEY_PREVIOUS, instead of
KEY_NEXTSONG and KEY_PREVIOUSSONG?

The latter are below-256 keycodes (like KEY_PLAYPAUSE,
which is used by BlueZ for pause) handled nicely by
all applications (like keytouch), where the former, which
are currently used, are extended codes, mostly unsupported
in user-space.

As far as I am interested, I changed the codes in my local
BlueZ installation so that I do not have to change keytouch.

Now it works nice with keytouch and hence audacious.

Thank you:

    Kristóf

ps. Here is a patch, if anybody is interested.