I'm using exactly the same XML to get "ContextMenu" on my RPi 3B+, and it works fine. Maybe you additionally have a keymap editor installed, which "overwrites the XML overwrite".
You can mark this thread as solved by editing your initial post.
I'm using exactly the same XML to get "ContextMenu" on my RPi 3B+, and it works fine. Maybe you additionally have a keymap editor installed, which "overwrites the XML overwrite".
You can mark this thread as solved by editing your initial post.
Seems there is no chances to get this device to work except waiting for the mainline kernel driver?
Already tried the latest milhouse build?
It seems like the context of autoexec.py is outside Kodi runtime, so the XBMC lib isn't usable from there.
To start the script right, do this:
Does that add to or replace the default settings?
Both. It adds a non-exiting definition or replaces an existing one.
What would be the accepted Remote key for a mouse Right-Click?
Wrong question
. The question is, which Kodi action is linked to the right-click.
If "ContextMenu" doesn't performs the right action for your needs, selects yours here.
An example if I have the "side" menu open and need to go back.
Is that correct?
Using the "Back" action is correct. You probably need different Kodi actions. Define different actions on your remotes color keys.
I found this instruction how to setup a 32 / 64 bit hybrid system on RPi: raspberrypi.org forums.
Hmm, Google must have that DRM algorithm from somewhere. Why do they get it, but we don't? We are good and legal, too. Maybe we just have to ask them.
Try the brand new LE 9.2.3. ![]()
Greengrass Full kodi.log please. Tell us how you play audio files (network share, USB stick).
Creating a 5GHz frequency needs more energy than 2.4GHz. So switching to 5GHz could break a weak hardware part.
I think we did all we can to fix it. Replace your RPi or use a WiFi adapter.
The guys are currently building LE 9.2.3, which is based on Kodi 18.7.1.
PS: Ready to download now. ![]()
Now I can not even connect to the 2.4Ghz as before.
...
Wiped the card and installed offical Raspbian, same thing no wifi anymore.
If you still can't connect to 2.4GHz with the latest firmware, then I bet your internal WiFi is broken, and you should replace the device.
They seem to be dealing with the Pi3 and circa 2018. Still relevant?
Yes, it's a risk to select the right files. Probably too much risk.
My advice is to use a second microSD containing Raspbian.
On Raspbian use the rpi-update command to update the firmware. That's the safest way to do it.
After that, insert your LE card, and it hopefully runs better with the new firmware.