2018-05-06, 23:45
(2018-05-06, 20:16)mikeb8591 Wrote: http://www.awen.com/~mburgett/kodi/ir-de...-test-1.gzHmmm, these logs look like you had bad IR reception, none of the IR signals could be decoded properly. The previous dmesg showed proper IR receptionand decoded signals.
http://www.awen.com/~mburgett/kodi/ir-de...-test-2.gz
Could you test a bit more with the second variant (the one that has fixed_timeout=1 in ir-debugging.conf) on build 0423? That should behave exactly like build 0417, i.e. without the mceusb patches.
Just test this with kodi, watch if the button presses are as you expect, make sure the battery is fully charged and you point the remote straight to the IR receiver.
If you change ir-debugging.conf it's also a good idea to fully power off your RPi so that the receiver is in "cold state" - USB commands to change the IR timeout behaviour might persist across reboots.
Once you got proper button presses in Kodi please redo the tests (this time powering off instead of just rebooting).
The ir-keytable -t output from your very first log is a bit odd, this can also happen if the a button is bouncing / worn out. Would be good if we could rule that out with proper, full logs.
so long,
Hias