> > -----Original Message----- > > From: Bastien Nocera [mailto:[email protected]] > > Sent: Tuesday, 18 May, 2010 14:26 > > To: John Frankish > > Cc: [email protected] > > Subject: Re: [Rhythmbox-devel] Bluetooth, AVRCP and Rhythmbox > > > > > > > > On Tue, 2010-05-18 at 06:35 +0200, John Frankish wrote: > > > > <snip> > $ 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
But: $ xev | sed -n 's/^.*keycode *\([0-9]\+\).*$/keycode \1 = /p' | uniq ... keycode 144 = So, using xev to make up an .Xmodmap that looks like this: keycode 144 = XF86AudioPrev keycode 153 = XF86AudioNext keycode 164 = XF86AudioStop keycode 168 = XF86AudioPlay i.e. completely different to that reported by evtest... and using xset to stop the AVRCP key press repeating at warp speed: xset -r 144 -r 153 -r 164 -r 168 then the sequence is: AVRCP signal -> bluetoothd -> uinput -> X -> Xmodmap -> rhythmbox ..and rhythmbox responds correctly to play, stop, next track and previous track :) _______________________________________________ rhythmbox-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/rhythmbox-devel
