streamzap remote gives double key presses in kodi

[graysky]

I am using a streamzap remote on a raspberry pi running 'kodi-standalone -l /run/lirc/lircd'. I have lircd setup and running with my /etc/lirc/lircd.conf.d/streamzap.conf and the remote gives a double key press in Kodi (I hit right arrow and it responds with two right arrows for example). To fix this on x86_64, I simply added the following to /etc/X11/xorg.conf.d/90-streamzap.conf which causes Xorg to ignore the remote as a keyboard device, but since kodi-standalone on the Raspberry Pi does not use Xorg (it uses xinit), I don't think this file is sources as it is on my x86_64 box. Any thoughts to fix the doubling of key presses on the Pi?

$this->bbcode_second_pass_code('', 'Section "InputClass"
Identifier "Ignore Streamzap IR"
MatchProduct "Streamzap"
MatchIsKeyboard "true"
Option "Ignore" "true"
EndSection
')

[WarheadsSE]

xinit still should be using xorg.

[graysky]

I placed the file in the same location but it doesn't seem to be honored.

[graysky]

I am not seeing a /var/log/Xorg.*.log when kodi starts nor do I see anything in journalctl relating to ignoring the IR receiver (though I do see the lines as the kernel and lircd see and initialize it). Love to fix this

[moonman]

Is there a usb receiver module or you are using gpio homemade receiver. If homemade, i had to play with repeat filter in lirc to get rid of double presses.

[graysky]

Nothing homemade here. In my first post I linked the product from amazon. It is a basic USB IR receiver. It works fine with that 90-streamzap.conf I pasted on the x86_64 box using full blown Xorg so I'm thinking it must be something about how our service is calling the executable.

Arch ARM:
$this->bbcode_second_pass_code('', '/usr/bin/kodi-standalone -l /run/lirc/lircd')

Arch
$this->bbcode_second_pass_code('', '/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7')

[moonman]

I only saw the remote on the picture at amazon without scrolling thrpugh the. It shouldn't be that. Upstream they use xinit because it doesn't work without it. It does on rpi. I didn't dig into that to find out why.
When you are in terminal (or anything where you can type) when you press a key on the remote does it show up on the screen? If not then lirc is not emulating uinput. Launch lirc with different repeat filter args, it might help.

[graysky]

Another user with this problem and no practical solution: https://lkml.org/lkml/2013/11/13/315

Any thoughts based on his experience are welcomed.

EDIT: The solution was to blacklist the modules jacking up the input:
$this->bbcode_second_pass_code('', '% cat /etc/modprobe.d/streamzap.conf
install ir_sharp_decoder /bin/false
install ir_xmp_decoder /bin/false
install ir_rc5_decoder /bin/false
install ir_nec_decoder /bin/false
install ir_sony_decoder /bin/false
install ir_mce_kbd_decoder /bin/false
install ir_jvc_decoder /bin/false
install ir_rc6_decoder /bin/false
install ir_sanyo_decoder /bin/false')