The easiest way is to enable debug logging in kodi and then watch the kodi log, using tail -f .kodi/temp/kodi.log and look for the HandleKey lines while you press the remote buttons.
Thank you for your help!!!
Meantime I observed the "Windows" button ("launch_media_center") on my mce remote looks like doesn't have action assigned. I added the "ActivateWindow(Home)" function.
And changed the key id="61692" to dvd... 
Hi, I had some time to try the latest LE13 nightly on a spare RPi4B (still using the latest LE12.2 nightly - without any noticeable issue).
Short story: I'm using the same HP MCE IR remote at the all my three RPi-LE devices. Some remote buttons I remapped within "remote.xml". At the LE13, I converted to the "keyboard.xml" and all previous remaps working, excepting one: The "DVD" ("KEY_DVD" in the "mce_keyboard.toml") button I remapped to launch a bash file (basically change the audio output and load an "m3u" playlist). Used the keymap editor addon I found that key have the key id="61692" (I just assigned a new function than looked at the generated "gen.xml" file), after that used the <key id="61692">System.Exec("/storage/.kodi/userdata/PlayM3U.sh")</key> - and now is working this too well.
My questiuon would be: exist any alternative (simple) way to find the "key id" for different remote buttons?
Is it possible to once shot upgrade to the latest version, with minimal issues?
Yes... but... a simple backup is always a good thing, just in the case something goes wrong...
Another "thing": even if the upgrade should be fine, if you don't have to much stuffs installed, a fresh install on another card (or better to a new one, the flash cells in the card have a limited life, maybe the old could be at the end of life) always is better...
And a final "thing": the LE12 have no more updates. So in the case of fresh install, you should try the latest LE13 nightly, it's good for the daily use and have newer software/drivers.
Dang! Took longer than I expected until someone suggests to try "fresh install" or something like that
For the moment I do not have the time to start something from scratch, but I'll keep it in mind...
"Dang", you should do that meantime or before asking help... You don't have a hour to try a basic fresh install, an easy thing with a RPi and a spare SD card, instead waiting for others to find what's wrong with your stuff.
Any other ideas are also welcome.
I think you should have two question:
What you want to do with your LE ?
Is anything "missing" in the already in use RPi4-LE?
If you doesn't expect to handle some "very exotic" HDR-4k media files, you should stick for now with your RPi4B. One of the best software supported device, stable, silent, very small power consumption. If that RPi isn't enough for you, with an old laptop you isn't make a big deal. Even could be worse than the RPi4B. In that case you should think about a new and powerful small PC... just needs some research in the matter of the situation of the linux/LE software (driver) support.
Reason ... am at a location with a Raspberry Pi ... WiFi ... Projector without HDMI CEC ... no ethernet near unmovable projector ... no keyboard
Hi, do you have any "remote device" to controll that RPi? Even with a simple IR remote can be set the wifi connection (virtual keyboard) or just use once any cheap keyboard for first setup and disconnect after that.
I'll try swapping the USB items around to see if that solves it.
Did you tried what I wrote a week ago?
I have a spare hard drive and would like to install LibreElec on it to test it out. My current setup is a Win11/Debian dual boot desktop PC. The setup is dual boot, dual drive, so each OS has its own drive.
Hi, Another question could be: what do you want to do finally with the Kodi? To install the Kodi with their own OS (like the LE), it's worth if you want to use that PC mostly as a HTPC. If you want occasionally to use the Kodi, to watch a movie, just simple install the Kodi at one of the existent OS, and use it. The LE intended to be the minimal OS for Kodi. That means, the driver support for some PC parts is limited, when at a "big" OS (Win11/Debian) that isn't a problem.
BTW, I think you can try the LE without install, just run from the USB drive.
If I know well, that jack output isn't a "real" audio output. It's one of the GPIO of the processor, used with software PWM and a bare bone RC filter to work as an audio output. And probably that is the reason why sometimes isn't synchronized perfectly with the video screen. That is working in this way for many years. If you wait for a fix for this, or switch to something else, with better sound quality, it's up to you only.
Hi, "using the built-in 3.5mm headphone output on the Raspberry Pi" for video streams isn't the best combination. Some times ago I struggled with that, till I bought an RPi compatible audio DAC module. I don't exclude the possibility, in the future a solution for that, but low chance. The fast solution could be to buy an RPi audio DAC hat or an HDMI audio extractor module. Or if you have any USB-audio dongle around, you could try it too.
Is there anything recommended that works out of the box.
Looks like a simple "out of the box" solution doesn't exist for that. I you want to put some work in, try to start from beginning. Remove all devices from USB but the remote's dongle, install the latest 13 nightly to an SD card. Make only the basic settings and try the remote for a while. If working well, try to add back, step by step the USB devices, install addons. If you could find what trigger the issue with the remote, you are a step closer to find a solution.
How could I correct the EPG
Hi, try to "Clear data" at Settings -> PVR & Live TV -> Guide. Than reboot.
Not sure what's happening, hope this is enough info for it to get fixed.
and then manually generate the required .url and .sha256 files and content
"Incorrect checksum..."
Hi, maybe isn't a "right solution" for this, but I'm using for a long time a daily reboot cron job. These OS's are developed to be used continuously... but that's true for an ideal world. For the "strange behaviors", a good prevention could be the regularly reboot. If you use a cron job like this: "15 04 * * * reboot", will reboot your device at everyday at 04:15 am.
That could rule out LibreELEC being the issue.
Just think about this a bit. It's a very large number of LE users have RPi4, if would be something with the LE, there would be a lot of complains about that. 99% it's something wrong with one of your RPi.
Will the "bad" RPi4 boot Raspberry Pi OS if you flash that onto an SD card?
How long would take to try it? If you really want to solve that, why just wait for others, instead to try few simple things? Like if booting with PiOS, or from USB, or check for LED blinking (bootloader error codes)? Did you checked the link I sent to you about the eeprom bootloader?
Any idea what's going on here?
Hi, maybe defective SD card reader. Try to boot from USB. Also can be the eeprom bootloader too, check this: RPI4 Recovery
There is a fix for this?
Hi, if you have around a USB-wifi dongle, it's worth a try. Also you can walk with your device to the lan cable and make a log (SSH and "pastekodi" command), maybe someone could help you what missing for built-in wifi.
The tvheadend43 plugin 12.80.6 could not be found in the arch64 repository.
Hi, if you want to install the TVHeadEnd server (service.tvheadend43), indeed at this moment isn't at the libreelec addons server for ARMv8/aarch64 location. Interesting, the version for ARMv7/arm is present on that server...
