Before I go into the depths of RasPlex trying to fix all the broken mappings in 0.7.1 for my PS3 BD Remote, does anyone have any mapping files that are working?
Ok… this is driving me batty…
It took me forever to find the branch/tags that had 0.7.1 and twice as long to find the files involved… (Side note - perhaps some docs on how to check out / build / find things in the repos would be cool)
So the PS3 BD remote is neutered by this commit:
I don’t know why, the commit message is near-pointless, but a ton of key mappings are removed in the ps3remote.evmap file (and many others).
I’ve been unable to edit the file on the RasPlex because the root filesystem is SquashFS and I can’t remount it rw.
So… how do I put the entries back in this file – or is there some easy way to make the edit and rebuild the SquashFS filesystem?
The eventlircd commit is taken from upstream OpenELEC, and mostly removes unnecessary mapping of key to same key.
The real issue is possibly due to https://github.com/RasPlex/OpenELEC.tv/commit/7f9f8118cee8544be81f038f4faeaa22d94d4506 where we switched bluetooth to use UHID since reconnecting a keyboard could take up to 10 seconds before it got recognized by RasPlex.
I plan to revert that change once I have finished switching to libudev for hot-plugged input support since the use of UHID prevents gamepads from working correctly.
It’s not clear how that flag could break the mapping on the BD Remote in such a way that exactly mirrors the keys removed from the .evmap file. Either way, testing is the key here.
Any suggestions on how to go about reverting that file (or the bluez config, I believe both are on the / FS)?
When bluez uses UHID all events are seen by PHT as if they where coming from a keyboard device.
Comment UserspaceHID in /storage/.config/bluetooth/input.conf and reboot, I have not tested but my PS3 remote worked before I added the UserspaceHID setting and did not test the remote after.
You will also want to modify IdleTimeout since it can take up to 10s for input events to be recognized after a reconnect.
Good news / bad news… Good news is the wife isn’t really pissed off at me for screwing up the remote control. Bad news is that I’m not sure all the buttons are quite mapped right. (The major ones are, but she was complaining about the subtitle button and the color buttons but I haven’t had a chance to test myself yet.)
So it looks like most of the mapping is ok, one of the color buttons doesn’t jump to an undefined page anymore (donno why wife used that to shortcut to the movie list, but whatever…) not a major deal.
However, after making that change (and leaving IdleTimeout) the same, the BD remote will stop controlling playback after a while (nothing on the remote will work). I have to stop playback with a Plex client remote and then the BD remote works instantly (like it was connected the whole time, but being ignored).
