Sander, >> Control is enabled by default in 4.60, is there anything I can check >> to see why I don't see any log messages about avrcp, no input device >> appear, nothing logged, etc? > > Currently there is support in bluez to act as a AVRCP target, and it will deliver these > events through the input layer. No new input device will appear, it will go through > /dev/uinput (which I think you can open for reading then) Thanks for the tip. I didn't have /dev/uinput or /dev/input/uinput so I mknod'd it temporarily (mknod /dev/input/uinput c 10 233). Trying to get anything out of it while streaming gives me "No such device". Is there somewhere else I can look to debug what bluez is doing to see if it's trying to handle avrcp events? Is there any d-bus api for examining them? hcidump shows avrcp messages going across, I just don't know what bluetoothd is doing with them. thanks all -- Brad Midgley -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
