OK, I managed to gather all the logs you suggested (or at least I think so).
The first is the dmesg output upon plugging in the device. See the dmesg attachment, it describes all the steps I took.
The second is the lsusb -v output. This output was got with hid, usbhid and hid_samsung modules _unloaded_
And the last is cat /dev/hidraw1 upon pressing the volume keys (hidraw attachment). The problem here is that every other key on the remote, when pressed, except the volume ones, results in two lines of code in console on cat /dev/hidraw1 (from what I understand, the first line is key press code, the second is key release code). The volume keys result only one line of code (the press code only), that is why they stuck. So, the hidraw attachment shows two codes: the first is vol down key press, the second is vol up key press. The freaky symbols '^@' are produced because the keys are actually stuck.
Please let me know if anything else is needed.
OK, I managed to gather all the logs you suggested (or at least I think so).
The first is the dmesg output upon plugging in the device. See the dmesg attachment, it describes all the steps I took.
The second is the lsusb -v output. This output was got with hid, usbhid and hid_samsung modules _unloaded_
And the last is cat /dev/hidraw1 upon pressing the volume keys (hidraw attachment). The problem here is that every other key on the remote, when pressed, except the volume ones, results in two lines of code in console on cat /dev/hidraw1 (from what I understand, the first line is key press code, the second is key release code). The volume keys result only one line of code (the press code only), that is why they stuck. So, the hidraw attachment shows two codes: the first is vol down key press, the second is vol up key press. The freaky symbols '^@' are produced because the keys are actually stuck.
Please let me know if anything else is needed.