Reasons for declaring it ShowStopper: 1) EndUser vs Experts
I am very sorry, but I am just an avarage end user loving its RaspberryPi 1+2.
But I am without linux knowledge. While my Raspi is in use as MediaCenter its vital functions are playing Video and Music to my Beamer and SoundStation controling all by Remote Keyboard and App (Logitech K400 and Android/iPhone App).
So Volume up/down are main vital functions… using my Pi as MediaCenter. 2) Complaint on Incident and Release Management
If an fix is available since 3 monhs - I would expect to get this implemented asap regarding impact and severety.
That means, is it really more important to release “Redesigned the OSMC skin to provide better colours” - instead of “Volume up/down” functions? Dont agree. 3) Customizing OSMC
I dont want to focus on customizing the OS.
I would need to concern about “Backup the System”, maybe using Test and Production Environment. Testing what happens when updating the OSMC… isn’t it?
But back to topic - I want to give it a try as recommended.
OSMC running on Raspi2 sending AV to Beamer, SoundStation while using
Keyboard Logitech K400 / iOS app / AndroidApp
Now, go forth and use your WinSCP to put the file into the mentioned directory. Or put it on one of your external drives or shares or whatever and copy it from there. The file will be eventually delivered, until then use the manual workaround.
Great. 1000 Thanks for great and very quick help. I didn’t want to invest more than one hour, but this makes fun, too.
Result: OSMC on Raspi2 while using Keyboard Logitech K400 is working fine now (also the Volume up/down keys)!
Tested both ways that brought Quick Workaround:
A) Used the Filemanager (Settings > File manager) and copy xml-file from USB device to /home/osmc/userdata/keymaps (thanks for that easiest idea @srmo)
(action requires Master User access to enter Root pathes)
Navigate to the power icon in OSMC
Press ESC on your keyboard
Login to your device (default is username: ocmc and pw: osmc)
My apologies! I neglected to state that it was a disappointing failure that keyboard.xml transplant did not resolve the problem:
FAIL: Using keyboard.xml from RaspBMC device (K400 keyboard volume long-press works), does not work in the OSMC device.
Not sure if put the file in the right location based on previous comment.
OK, so it’s back to square one with the RaspBMC device and pose the question: what file needs to be configured? If anyone can suggest a list of files to publish from the good RaspBMC device, please state them and I will make them available for analysis.
I am wondering if it is possible to infer the syntax (of keyboard.xml) that would allow one to specify that ‘long press’ of the volume keys (F11, F12). If this is the case then the issue can be resolved by changing keyboard.xml. That being said, the more I think about it: it would seem that the long-press( to invoke sending multiple instances) of a keystroke does not work. If this is the case, then the root cause must be addressed before making changes to keyboard.xml. In this case, I am interested in suggestions for determining a test to diagnose where in the scheme of things the process fails. Long-keypresses of the enter key work fine on OSMC so, hopefully this lengthy comment will help arrive at a diagnosis.
@sam_nazarko: I am also arriving at a similar conclusion. If there is any test that I can perform that would help to confirm / refute this hypothesis, let me know. I am will consider testing from all concerned / participating.