>I've got a similar device. >Bus 004 Device 002: ID 0419:0001 Samsung Info. Systems America, Inc. IrDA >Remote Controller >The wDescriptorLength for it is 171. Yet another 0419:0001 device. I already read about descriptors with 184, 203, 135, 199 bytes.
>After patching my kernel with this patch http://launchpadlibrarian.net/25472216/samsung203b-2.6.29.patch the device works fine, except of two keys: This patch only brought back the old state for all 0419:0001 devices without 184b descriptor, i.e.using the regular HID input device. Probably your device still has some minor descriptor quirk, rendering your two keys useless. >Then i applied this patch >http://launchpadlibrarian.net/22301251/hid-core.patch This fixed key stuck, >but another problem rose I do not recommend this workaround anyway. Please post your output of "lsusb -v" for the remote. If the report descriptor is shown as unavailable, you might need to unload any daemons or even the hid module. Alternatively, load the HID kernel module with the debug option enabled -- similar to the original poster above. Brand/device info of this remote would be interesting Probably /dev/hidraw output for vol keys would also be interesting (w/o the workaround patch). -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
