2010-06-07, 19:11
@Zerogoki
Are you using bluez from my PPA? From your steps, it looks like you're using the ones shipped by Ubuntu. That version does NOT have my patch, and so has a hardcoded key mapping that is pretty annoying to get working with XBMC. Since you paired okay, that should be good. (I would re-check by running "list-devices" after a reboot.)
As for your questions, here's some filler to get you started...
The "uinput" kernel module (which you loaded manually via modprobe, and set up to autoload on boot via /etc/modules) is used by the bluez code to inject input (in this case, keyboard keycodes) into the kernel stack. (It's pretty useful, but X11 screws things up later, which is why we need the mapping configuration...)
The new input.conf that my patch allows for, lets you configure a remote timeout, as well as a key mapping. This allows a user to more easily configure both XMBC's keymap and the remote together.
Are you using bluez from my PPA? From your steps, it looks like you're using the ones shipped by Ubuntu. That version does NOT have my patch, and so has a hardcoded key mapping that is pretty annoying to get working with XBMC. Since you paired okay, that should be good. (I would re-check by running "list-devices" after a reboot.)
As for your questions, here's some filler to get you started...
The "uinput" kernel module (which you loaded manually via modprobe, and set up to autoload on boot via /etc/modules) is used by the bluez code to inject input (in this case, keyboard keycodes) into the kernel stack. (It's pretty useful, but X11 screws things up later, which is why we need the mapping configuration...)
The new input.conf that my patch allows for, lets you configure a remote timeout, as well as a key mapping. This allows a user to more easily configure both XMBC's keymap and the remote together.