Fix for Play/Pause key on some MCE remotes

Such a fix is just not possible in latest lirc 0.9.4 since it does not contain any remotes definitions. Although it's possible to patch current version, from zesty+ the remote definitions lives in http://sf.net/p/lirc-remotes; this is also whar other distros use. So, the best solution here would be to close this ticket and open a new at the upstream remotes project.

I'm suggesting a fix for e.g. Xenial, as otherwise many users will have non working play/pause, a basic function, for a few years. The simple fix I suggest is safe, as it only affects MCE remotes, where the problem is.

I'm just the upstream maintainer, so I'm not involved in if/how current stable releases are patched. That said, since new users will use the new database I'd suggest you file a bug there for the benefit of those; this is not to say anything about whether xenial should be patched or not

Thanks for the suggestion (and for your work upstream!).

I had a look at lirc-remotes, and it already has what I consider the correct fix, namely, to change the key code to KEY_PLAYPAUSE.

If when I get this version of lirc on my machine I still have my MCE remote, and it still doesn't work in Kodi, I suspect it will be time to chase the bug there instead.

You can test using the ppa at https://launchpad.net/~leamas-alec/+archive/ubuntu/lirc-0.9.4. Don't forget the message if you upgrade, the update requires configuration changes.

Thanks! I probably won't have time to do that, but I'll try to remember if I do.

Setting this to confirmed since the remote definition differs from the sort-of-upstream lirc-remotes.

Basically this is a Kodi bug since Kodi (as the only major client) does not respect the mappings done by lircrc but instead reads the raw codes from lircd. One of the purposes of lircrc is to handle problems like this, and so it does - when used.

Since re-mapping this key according to the patch would break configurations for other users which have handled this using .lircrc I'd recommend closing this bug as wontfix.

Someone should file a bug against Kodi for bad behaviour. It's too late to skip the raw reads from lircd, but adding an option to use lircrc is IMHO the right path. Kodi does some mapping, but lircrc is more than mappings: modes, repeat suppression, long keypresses and so on.