As Marky was saying, the runaway IR code issue can often be managed better when you create a macro for certain codes. Usually Volume up and down.
For example, to prevent runaway for volume up, you would create the following macro for both volume up and volume down:
Delay 100 ms Volume Up or Down code Delay 100 MS
This enough of a macro to sort of side-step the issue with the IR chip which is causing the problem.
Do the same for any hard button which is being repeated.
On the flip side, the run-away is caused by an incomplete button press of short duration. In this short duration, the remote senses the volume up comand but it does not see the next part of the repeating command which is to stop the repeating.
We have had very good success by telling the client to push the button a bit more deliberately. It is the short "flick" which actually causes the issue. Yes, the hardware has a fault which should prevent this.
But just spend a quarter second more and make a complete push, or a more deliberate push or some have said a "harder" push which all accomplishes the same thing.
