paul- wrote: > Because evdev requires the device to show under /dev/input/... Which > is not done by just making a bluetooth connection alone. > > There is some other software interaction or udev rule that does > something.
Ah, fair enough. Must admit I have only tested this on raspbian. I tried, and failed, to install evdev on pCP, so never got round to testing there. Can't see anything BT specific in /etc/udev under raspbian. *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. ------------------------------------------------------------------------ cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=114424 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
