Re: [Rhythmbox-devel] Bluetooth, AVRCP and Rhythmbox

[John Frankish <j-frankish slb com>]

> -----Original Message-----
> From: Bastien Nocera [mailto:hadess hadess net]
> Sent: Tuesday, 18 May, 2010 14:26
> To: John Frankish
> Cc: rhythmbox-devel gnome org
> Subject: Re: [Rhythmbox-devel] Bluetooth, AVRCP and Rhythmbox
> > >
> > > On Tue, 2010-05-18 at 06:35 +0200, John Frankish wrote:
> > > <snip>
> > >
> > > Could you test "evtest" on the device created? There should be a device
> > > created in /dev/input/* for the fake input, check whether events are
> > > sent there.
> > I don't see a new /dev/input/* being created, but there is:
> >
> > /sys/devices/virtual/input/input11/event11
> >
> > $ cat /proc/bus/input/devices
> > ...
> > I: Bus=0005 Vendor=0000 Product=0000 Version=0000
> > N: Name="00:1B:66:00:31:88"
> > P: Phys=
> > S: Sysfs=/devices/virtual/input/input11
> > U: Uniq=
> > H: Handlers=kbd event11
> > B: EV=100007
> > B: KEY=10300 168 0 0 0 0 0
> > B: REL=0
> 
> Looks like it could be the one.
>
I managed to find evtest to compile

$ sudo evtest /dev/input/event11
Input driver version is 1.0.0
Input device ID: bus 0x5 vendor 0x0 product 0x0 version 0x0
Input device name: "00:1B:66:00:31:88"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 163 (NextSong)
    Event code 165 (PreviousSong)
    Event code 166 (StopCD)
    Event code 168 (Rewind)
    Event code 200 (PlayCD)
    Event code 201 (PauseCD)
    Event code 208 (Fast Forward)
  Event type 2 (Relative)
  Event type 20 (Repeat)
Testing ... (interrupt to exit)
 [touch track skip]
Event: time 1274200254.037702, type 1 (Key), code 163 (NextSong), value 1
Event: time 1274200254.037709, -------------- Report Sync ------------
Event: time 1274200254.092604, type 1 (Key), code 163 (NextSong), value 0
Event: time 1274200254.092608, -------------- Report Sync

So indeed, that looks OK

> > > > Is gnome-settings-daemon the only way to do this or is there another
> > > > way?
> > >
> > > It's not the only way to do it, but it's the supported way for GNOME
> > > applications, and Rhythmbox in particular.
> > >
> > > > The AVRCP signal is getting as far as uinput, but using "dbus monitor --session", I cannot see any dbus
> > > > AVRCP events in X and gnome-settings-daemon seems to have a problem (debug output below)
> > > >
> > > > How does the AVRCP signal get from uinput to X?
> > > >
> > > > John
> > > > ----------------
> > > > DEBUG:         Property: 'bluez.name' = 'Sennheiser PXC310BT'
> > > > DEBUG:         Property: 'device.icon_name' = 'audio-headphones- bluetooth'
> > > > DEBUG: Starting keyboard manager
> > > > [1274118894,000,xklavier.c:xkl_engine_start_listen/]    The backend does not require manual layout
> > > > management - but it is provided by the application
> > > > DEBUG: Starting a11y_keyboard manager
> > > > DEBUG: Starting media_keys manager
> > > > DEBUG: Unable to parse: 'XF86AudioMute'
> > > > DEBUG: Unable to parse: 'XF86AudioLowerVolume'
> > > > DEBUG: Unable to parse: 'XF86AudioRaiseVolume'
> > > > <snip>
> > >
> > > Huh. Did you compile gnome-settings-daemon yourself? That does look
> > > like a problem indeed...
> > >
> > > Cheers
> >
> > Yes, I compiled it myself, but the dependencies appeared to have all
> > been met and there were no error messages. What would be needed to
> > enable 'XF86AudioMute', etc to be parsed?
> 
> You're missing /usr/include/X11/XF86keysym.h from somewhere.
> 
> So the problem has nothing to do with Rhythmbox, just your setup.
> 
> Cheers

Well,  /usr/local/include/X11/XF86keysym.h is definitely there, but I haven't found where the gnome-settings-daemon source looks for it yet.

..but yes, it does not look to be a rhythmbox problem.

Thanks for the help

John