yes, as i understand all keys of the remote need to be assigned new
they won't be imported i guess?
In my case, with MCE IR remote, almost all remote buttons working with LE13, especially the common buttons. Were few "special" buttons, but that can be resolved in "keyboard.xml". Example the button with a DVD simbol, had named "menu" in LE12 and remote.xml, in LE13 and keyboard.xml is "dvd". True, the MCE remote is the default supported, with other remotes could be more difficult.
did you have to input your remote commands over again?
LE13 seems to change the way remote commands are processed.
I'm really looking forward to a beta
Hi, You should read this: Important change in LE13 remote handling
I don't have the option to "Uninstall". I only have option to "Disable". Hence my frustration.
If you could tell which addon is the "problematic" for you, maybe somebody have the information why you can't uninstall it.
I have made a bunch of changes to make it work like keeping my wifi open (without a password) for months, and it still had issues that required a reboot to fix. I switching over to another linux disto because someone was on my network for hours on sunday and monday morning.
If with "wifi open" you had the same issues, why you kept without encryption??? 
If your RPi-LE have unstable wifi signal, looks like sometimes unable to (re)connect to router. If you have a spare USB-Wifi stick (with a "real" antenna), worth a try. Or for a try, can the RPi move closer to router?
I'm using 3 RPi with LE, two connected through LAN (cable is always faster and stable), just at one I need to use wifi. I modded my RPi3B to be able to use a proper external antenna (the tiny antenna on the RPi is the weak piece - at all RPi versions).
Now it keeps prompting for a password..I have rebooted so many times i am considering switching back to RPiOS
LibreElec is a great project, don't give up so easy. A lot of people using RPi and LE with wifi, usually without issues (me too).
Indeed is "something" with the wifi connection in the LE, but I think is influenced by the router wifi settings too.
Try this: in the router use WPA2 encryption only (not mixed mode), in the RPi-LE set a manual IP. That should help to a stable wifi.
The weak or unstable wifi signal isn't help in this situation, all RPi versions is notorious about the tiny wifi antenna and bad wifi signal.
Recently was an update to enable the WPA3 wifi encryption for RPi, the command suggested by chewitt disable that. Worth a try too. Or you can try an older LE13 version (before 20260919).
So update. Came home, booted the Pi, and no internet again. The wireless "state" says ready again instead of online. Tried to refresh, but nothing. Even did a disconnect and then reconnect under its settings, and nothing.
You provide a description of the problem, but with little useful data. Could be useful to know how your RPi connecting to the wifi: IP is DHCP or manual set; Wifi router encryption does WPA2, WPA3 or mixed mode?
For stable connection for now you should set the RPi to fixed IP, in the router encryption only WPA2 (use strong password), don't use in the router any MAC based IP assignment.
I trieed this. but i do not understand this application. especialy the text entries.
Hi, in the wiki page all is explained: https://kodi.wiki/view/Add-on:Audio_Profiles
I'm using this addon for the same reason, auto-changing the audio output based on the media type (HDMI for movies, I2S audio for music). Basically is enough in the addon settings to activate the first two (or more, if you need) "Profiles", set the media types to switch automatically. After that set manually the output and "run" the addon to connect to a profile. Repeat for each profile. With a bit experience, can be set to work without any issue. Not mandatory, but can be useful to have set a keyboard/remote button, to be able to change the output manually ("Switching Profiles Using Keymaps" in Kodi wiki).
In the past I spent a lot of time to have simultaneous audio output, searched any options, finally this addon I found that do the job well.
Hi, In the LibreElec addon you can enable the SSH service.
To access the file system without LE, the simplest way is to boot a live linux from USB.
Hint: install the Ventoy boot manager to your USB stick then "drop" one (or more) live-linux ISO file to stick.
WPA3-SAE should now work fine on RPi5 and RPi4 with the latest LE13 nightly build
Hi, thank you, that's good news, any information if that will be implemented on RPi3 too?
On a RPi5 my wireless "airmouse" dongle is being recognised until I physically unplug and re-plug the dongle after each reboot. I found updating to the latest 12.2.1 did not help.
Hi, far as I know, the LE12x development is stopped, developers working on the LE13. You should try the latest LE13 nightly, for an RPi5 no need to upgrade, use a spare SD card and test it.
If you don't mind, could you link the "4K/HDR instructions in the wiki and run the GUI at 1080p"?
Hi, The LibreElec official wiki page about the "4K / HDR" setup.
VLouis thanks, thats a workaround that might probably work.
"Probably"? Why you didn't tried? It would take only few minutes, easy to do, and needs to be done only once. Easy and done. Why this "cruciade" for GUI modification to be included special settings? Especially when could be exist an easy workaround.
... or not to use libreelec at all. i got it. i give up.
That's only up to you...
Hi, see here, maybe it's the same issue what I had: Important change in LE13 remote handling
When i use DHCP and then try to change the DNS it says its forbidden, which is a bit odd. Unfortunately, in my country we are sometimes forced to use a different DNS server than the one that is sent by the proprietary router (where nothing like dns is configurable).
Hi, Do you strictly need to use DHCP at that device? I'm thinking about, you could to start to configure the network with DHCP. After it's connected, change to "manual". The values obtained by DHCP will remain, and you change only the parameters that you want (DNS server). Maybe worth a try...
Note: Primary copies of movies, videos, etc reside on my media center. That is, rather easily retrieved if necessary. So, I'm not completely opposed to formatting the disk (e.g., ext4) and rebuilding the library. But, if there is a better way to resolve this, I'm all ears
HI, Changing to ext4 would take some time, but I think it worth it. No more issue with NTFS under Linux...
Is there a way to check that the created EDID file is actually working?
You can try to start the RPi with nothing connected to RPi's HDMI ports. Wait soime time and onnect the HDMI cable directly to the TV. If working, the saved EDID is correct. Or you can save it again: run the "getedid delete" command, power off the RPi, connect the TV directly to RPi's HDMI port, start the TV, wait few seconds and start the RPi. Only if you see the correct image on the display run the "getedid create" command.
Another workaround could be to add to the "cmdline.txt" the "video=HDMI-A-1:1920x1080@60D". That should force at the startup the standard FHD resolution. This I never tried, I'm using the "EDID save" method.
EDID is the display's capability information stored in a dedicated memory in display. The OS (linux - LibreElec) try to obtain it from display at the startup to know what picture resolution and FPS to use. Without EDID data usually the OS doesn't provide image. By saving the EDID data (getedid create command), the OS will use the saved one, regardless the display is connected or not.
Hmm, I connected the TV directly to the Pi and indeed I now get EDID=ok!
After "getedid create" I still get "weak or no HDMI signal" with the switch involved though, directly through the splitter works as it always has. In Debug I still see EDID=none..
The "getedid create" save the connected display EDID data (if is display connected and working correctly). That means, next time, at startup the RPi will use the saved EDID data to set the picture parameters, instead waiting to get it through the HDMI connection, and send image to HDMI regardless "see" a display or not.
So, up until a while ago everything worked great.
Hi, many years ago I worked on a TV repair shop and that I heard many times... Usually everything's working till... stopping working.
Raspberry Pi 4b (4GB RAM) outputting to HDMI0 (the port next to the USB-C) into a HDMI 2.1 Switch that Feeds a HDMI 2.1 Splitter from which one output goes to the TV (Hisense 55E7NQ, 2024) and the other one into an HDMI grabber that goes into HyperHDR (also running on the Pi).
That's a really "unusual" way to connect a display to an RPi. My hint is, somewhere the display (TV) EDID data is cut to reach the RPi. And because the RPi (and LE) didn't "see" the display, didn't provide picture. So, you should try at first to connect the TV directly to the RPi's HDMI0 and check it. And if in that way working, you have picture from RPi, you could try to save the TV's EDID to RPI: SSH to RPi and run the "getedid create" command (no more need for the RPi to "see" the display's properties). If you ran that command before, better to delete the previous data and run the "getedid delete" first. After that you could connect back your "strange" HDMI chain and try it. If isn't working maybe something defective, play "lego" by removing elements from chain (switch, splitter, cables) till you found what's the cause. I almost forget, start the TV first, and the RPi few seconds later to be sure it get the EDID (the "getedid create" fix that too).
