I have a Vero4k and use a RC6 remote with the built-in IR receiver. This works fine with the 2017.04-1 software. I believe that it worked with 2017.05-1 update, but I am actually not sure in that I updated then went out of town for a week. I think that it was working to update to 2017.05-2, but now it is not working properly. I have to hit the button twice within ~1 sec to be registered. A single hit with nothing for over ~1 sec will do nothing. That is, if I hit buttons once every 2 sec, nothing happens. I ran irw and the issue shows up there, so it is something early in the process.
I remember an issue a long while ago where button presses were being duplicated and there was some method of filtering that out. I never had that problem, so I don’t remember the details.
I should point out that I use a DirecTV remote and a custom lircd.conf file and custom Lirqmap.xml and custom remote.xml files. I tried plugging in a USB IR receiver and that works OK. It is just the built in receiver that is not working.
I reverted back to 2017.04-1 to make sure that it works. If does. I then updated to current version (2017.05-2) and it stopped working again. So, something is different between 04-1 and 05-2 that is causing the problem.
Well, you broke it again in 2017-06.1. The local IR input on the Vero4k only registers a command if I double press the button. Is there an easy way of going back to 2017-05.3? Or better yet, getting this fixed?
Sorry for the confusion. It is not working now. Well, actually, it is as I reverted back to 2017.04.1. The only other option in the installer is 2017.05-2 which didn’t work for me until I loaded the experimental build that you gave me. I removed that line in sources.list as soon as I rebooted. That was all old history.
So, it was working after the 2017.05-3 update, but not today’s 2017.06-1. I did reboot and it doesn’t matter. The remote will only register if I push the button twice in quick succession.
So, you think that there may be a slight timing difference between the two kernels? That’s an interesting thought. I won’t be able to check this out until the weekend. I don’t have free access to the system. This seems unlikely, as it can correctly recognize every key as long as it is pressed twice.
@sam_nazarko As per my post feedback when you release the fix post June update I also experienced the same and that’s why I said every 2 remote presses VERO4K doing ONE action. Given you told me this is the best you can do I accepted it.
As per forum feedback this used to work flawlessly until May Update and given you reverted all changes done I am not sure what else you can do…
What’s strange is @jmkinny says it only regressed in the last update; so needs more investigation. Unfortunately I think if we fix this issue it may cause problems for other users. I’ll produce some more builds and see what can be done as long as you guys are willing to test.