Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Is Multi-Channel audio and Multi-Soundcard the same option?
Are multiple sound cards required for running multiple Slim Device players? (linuxmce + squeeze[anything] pulls search hits for softsqueeze, squeezeslave, logitech media server, slim-devices, and about 30 others I cant recall offhand. I just want to use use Slim Device Squeezebox Players/emulators).
Okay, this sounds probably stupid on my part, but you're used to that from me, I suppose.
I'm using a Gigaset 610 IP together with LMCE and thats all working nicely so far. Today, when I came home I noticed a missed phonecall. Upon checking it on my Gigaset, I was astounded to see the full name of the caller in the display. It was somebody I knew, but didn't have the number for, so clearly this info came from somwhere else.
Right now I'm a bit confused, where this nice feature comes from...is Asterisk now automatically doing a reverselookup or is this something my Gigaset does on its own?
I'd appreciate your input.
I really want to beat whomever did the udev rules for these devices to a fucking pulp...
Sure, here it is on the accelerometer machine (hp6710b):
Thanks for having a look at this. I will try to apply and test your patches on my false positives (hp6710b notebooks accelerometer) and let you know. Will be great if this is addressed.
udevadm info --query property --name /dev/input/js0for your accelerometer device. (Accelerometer in my laptop doesn't present at /dev/input/js?) I know it will not mis-detect a mouse device now but I'm not sure what the accelerometer presents as.
awesome. patch it
# udevadm info --query property --name /dev/input/js0
DEVLINKS=/dev/char/13:0 /dev/input/by-id/usb-VirtualBox_USB_Tablet-mouse /dev/input/by-path/pci-0000:00:06.0-usb-0:1:1.0-mouse
OK, so the package is installed if required, but I can't see why the GamepadCmd variable is set because I can't figure out where/if it's ever used?
snag is... that "GamepadCmd" bit... what is that used for and where does it come in. Is it a necessary step I'm missing out?