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

[Bastien Nocera <hadess hadess net>]

On Tue, 2010-05-18 at 06:35 +0200, John Frankish wrote:
<snip>
> > Thanks for the feedback.
> > 
> > Yes, the uinput module is loaded and I've tried with alsa alone and
> > with alsa+pulseaudio
> > 
> > At the first remote AVRCP key press, I see this in dmesg:
> > 
> > input: 00:1B:66:00:31:88 as /devices/virtual/input/input11
> > 
> > ..and if I run bluetoothd in the foreground, I see (for example):
> > 
> > bluetoothd[4253]: AVRCP: uinput initialized for 00:1B:66:00:31:88
> > bluetoothd[4253]: AVCTP Connected
> > ...
> > bluetoothd[4253]: AVRCP: BACKWARD pressed
> > bluetoothd[4253]: Got 8 bytes of data for AVCTP session 0xb79d86e0
> > bluetoothd[4253]: AVCTP transaction 8, packet type 0, C/R 0, IPID 0,
> > PID 0x110E
> > bluetoothd[4253]: AVRCP command 0x0, subunit_type 0x09, subunit_id 0x0,
> > opcode 0x7C, 2 operands
> > bluetoothd[4253]: AVRCP: BACKWARD released
> > bluetoothd[4253]: Got 8 bytes of data for AVCTP session 0xb79d86e0
> > bluetoothd[4253]: AVCTP transaction 9, packet type 0, C/R 0, IPID 0,
> > PID 0x110E
> > bluetoothd[4253]: AVRCP command 0x0, subunit_type 0x09, subunit_id 0x0,
> > opcode 0x7C, 2 operands
> > bluetoothd[4253]: AVRCP: REWIND pressed
> > bluetoothd[4253]: Got 8 bytes of data for AVCTP session 0xb79d86e0
> > bluetoothd[4253]: AVCTP transaction 10, packet type 0, C/R 0, IPID 0,
> > PID 0x110E
> > bluetoothd[4253]: AVRCP command 0x0, subunit_type 0x09, subunit_id 0x0,
> > opcode 0x7C, 2 operands
> > bluetoothd[4253]: AVRCP: REWIND released
> > bluetoothd[4253]: Got 8 bytes of data for AVCTP session 0xb79d86e0
> > bluetoothd[4253]: AVCTP transaction 11, packet type 0, C/R 0, IPID 0,
> > PID 0x110E
> > bluetoothd[4253]: AVRCP command 0x0, subunit_type 0x09, subunit_id 0x0,
> > opcode 0x7C, 2 operands
> > ...
> > 
> > But there is no corresponding action in rhythmbox
> > 
> > John
> ----------------
> I understand the communications chain should be:
> 
> AVRCP signal -> bluetoothd -> uinput -> X -> gnome-settings-daemon -> rhythmbox

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.

> 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'
> DEBUG: Unable to parse: 'XF86Eject'
> DEBUG: Unable to parse: 'XF86Explorer'
> DEBUG: Unable to parse: 'XF86AudioMedia'
> DEBUG: Unable to parse: 'XF86Calculator'
> DEBUG: Unable to parse: 'XF86Search'
> DEBUG: Unable to parse: 'XF86Mail'
> DEBUG: Not a valid shortcut: ''
> DEBUG: Not a valid shortcut: ''
> DEBUG: Unable to parse: 'XF86WWW'
> DEBUG: Unable to parse: 'XF86AudioPlay'
> DEBUG: Unable to parse: 'XF86AudioPause'
> DEBUG: Unable to parse: 'XF86AudioStop'
> DEBUG: Unable to parse: 'XF86AudioPrev'
> DEBUG: Unable to parse: 'XF86AudioNext'

Huh. Did you compile gnome-settings-daemon yourself? That does look like
a problem indeed...

Cheers