With ng my IR worked fine with amremote. For testing I removed the eMMC and installed Piers alpha2 with no on an sd-card. I recognized immidiately that the remote was less responsive with unwanted repeats, although still using meson-remote (amremote) with the same remote.conf.
Back to eMMC and ng the remote is now unusuable. I need to press a key several times with pauses of 1-2 seconds until it is recognized. Keeping the key pressed does not help. Tried other remotes, other configs, switched to memson-ir, but always the same behaviour. I tested older images , changed power supply and even replaced the TSOP on my Odroid N2 - nothing changes.
With meson-ir and ir-keytable- u I see several times the same code, although I already changed the pressed key. It takes the some time until a press generates the right key and not the previous one. Very strange!
Could it be that during installation of the new amlogic-no image my N2 was “re-programmed” in any way, with changing any registers that survive a power-off? Any kind of firmware update?
When I initially changed from NG to NO my remote lagged really bad. (Tox3 s905x4). I have only ever used SD cards for CE.
That much so I only ever ran NO nighty’s to see what improvements had been made. About 6 months or so ago it seemed to change and the lag mainly went away. I now use NO on 2 Tox3 boxes. One box still hesitates a second or so sometimes but the other is fine. I did have to remake some keys in the Kodi keymapper app to get them to respond properly.
You could also try a very earlier version of NO and then update it as a trial?
This might explain the different behaviour under NO. But switching back to an older NG version it should have worked as before.
If it is not an issue of persistent re-programming of internal settings inside the hardware, it must be a hardware problem with the electronic on the N2 which is responsible for processing the IR signals. Even the wakeup key does not work properly. I have to press the power button multiple times in different intervalls until the N2 begins to boot.
Could it be that a too high repeat rate in remote.conf caused a damage of the electronic components onboard of the N2, when this was effective for the first time in NO?
In the meantime I ordered a new N2+ - there is an offer on ebay for refurbished boxes for less than 70,- Euro.