In my case, event3 will be fired when pressing normal keys and event4 will be fired when pressing the multimedia keys. So here's my input-event for device4 when pressing a volume key. After this the mouse pointer jumped to the upper left corner.
----------------------------------------------------------------------------------- felix@pc:~$ sudo input-events 4 /dev/input/event4 bustype : BUS_USB vendor : 0x45e product : 0x750 version : 273 name : "Microsoft Wired Keyboard 600" phys : "usb-0000:00:12.1-2/input1" uniq : "" bits ev : EV_SYN EV_KEY EV_REL EV_ABS EV_MSC EV_REP
waiting for events 10:24:33.894621: EV_MSC code=4 value=786665 10:24:33.894638: EV_KEY KEY_VOLUMEUP (0x73) pressed 10:24:33.894660: EV_SYN code=0 value=0 10:24:34.038652: EV_MSC code=4 value=786665 10:24:34.038669: EV_KEY KEY_VOLUMEUP (0x73) released 10:24:34.038693: EV_SYN code=0 value=0 -----------------------------------------------------------------------------------
In my case, event3 will be fired when pressing normal keys and event4 will be fired when pressing the multimedia keys. So here's my input-event for device4 when pressing a volume key. After this the mouse pointer jumped to the upper left corner.
------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------ 00:12.1- 2/input1"
felix@pc:~$ sudo input-events 4
/dev/input/event4
bustype : BUS_USB
vendor : 0x45e
product : 0x750
version : 273
name : "Microsoft Wired Keyboard 600"
phys : "usb-0000:
uniq : ""
bits ev : EV_SYN EV_KEY EV_REL EV_ABS EV_MSC EV_REP
waiting for events ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------
10:24:33.894621: EV_MSC code=4 value=786665
10:24:33.894638: EV_KEY KEY_VOLUMEUP (0x73) pressed
10:24:33.894660: EV_SYN code=0 value=0
10:24:34.038652: EV_MSC code=4 value=786665
10:24:34.038669: EV_KEY KEY_VOLUMEUP (0x73) released
10:24:34.038693: EV_SYN code=0 value=0
-------