trying to discover the root of the "subtitle issue"
Hi, what kind of subtitle issue did you experienced with TVH4.3? I'm switched to TVH4.3 some times ago, struggled a bit with subtitle settings, resolved finally in the Kodi settings (player/language).
And WiFi automatically connected to your AP after that?
Exactly, and I tried again that (latest LE12 nightly on the card) still without wifi issue. And because last week I wanted to try the LE13 nightly, I still have it on a spare card. Using the LE13, I tried twice the same thing with power off then on, and no wifi issue. In the past, I had wifi issues: started the TV (the RPi it's always on), the LE asked for wifi password but didn't accepted or sometimes just started without wifi connected, after a reboot started without issue. Could be the same issue?
3B or 3B+? 3B uses a different WiFi chip (Broadcom BCM43438) than RPi3B+/RPi4 (both Cypress CYW43455). So that would also point to a driver-related issue.
Maybe yes, or maybe it's already fixed in the nightly builds whatever it was. If you don't have a spare card, you could make an LE backup, then update to latest LE12 nightly (because you can go back to LE12 stable if you will want it, the downgrade from LE13 not guaranteed) and try it...
Nope, definitely not the antenna, or it wouldn't be so reproducible. It's only after cold boot. Never after reboot. 100%. RPi is next to the AP.
If the RPi is next to your AP and you have any chance to use cable instead wifi, don't hesitate, change it. Far better speed, without issues. I have 3 RPi's with LE installed and at only one had wifi problems (no way to use cable in that place). The another two with cable connetion to my router, never had any network issue in the last years.
As I'm using almost same config, RPi3B, wifi (mod. for external antenna), and latest LE12 nightly. So I pulled of the power and connected back after few seconds. The LE booted without any wifi issue...
Doesn't mean it can't be driver releated.
You got till now from two people the advice to install an LE13 nightly build and try it. So if you don't have a cheap, at least 8GB SDcard and a hour for this... I let you to keep wondering what could be wrong... Also keep in your mind, you aren't the single person who use an RPi3 with LE and wifi connection. So using the search function on this forum could help too.
I think that is a result of the some "things", and one of them is the weak RPi wifi antenna on all versions.
Two thing you should try:
Install the latest LE nightly (LE12 - very stable, I'm using it too, or/and the LE13).
Try to use a better connection. If you have any chance to use cable, forget the Wifi at RPi. If you can't, try to use a USB-wifi stick, one with a "bigger" antenna.
I'm made a modification on my RPi3B to be able to connect an external wifi antenna, the wifi is far better, but for this it's need a really advanced soldering skill. With this and with the latest LE12 nightly, I didn't remember when I had a wifi issue last time.
thanks but unfortunately no - the two USB 3.0 ports of the RPi4 do not work with the SSD (although it has a USB 3.0 port itself), but I moved from one USB 2.0 to just the other USB 2.0. port. So it is a difference between the two USB 2.0 ports... I know, super weird.
That strange indeed. At the RPi's the USB ports current limit is for total current (around 1.2A), theoretically no individual port current limit. I think your SSD need power that these ports barely can provide. Looks like one of the USB2 port can handle it for now, but the question how long and how stable.
Two thing:
I think in the config.txt can be activated the high current output adding the line "max_usb_current = 1" (you should have a proper power source for RPi).
You can use an external powered USB-HUB connected whichever RPi USB port (the SSD will be powered by HUB).
More specifically, I would like to edit /usr/share/kodi/addons/skin.estuary/xml/Includes.xml, but nano tells me it's read only. I know there is no sudo on LE, so I'm unclear on how to proceed here.
I done something like this few years ago. For a beginner probably the best approach is to copy the skin folder ("/usr/share/kodi/addons/skin.estuary") to a USB stick, use a PC to modify it as you want (if Windows - use a linux compatible editor like Notepad++), don't forget to rename it (the folder - ex: "skin.estuary_mod" and in the addon.xml - if I remember correctly), copy back to "/storage/.kodi/addons/....". Reboot, change the skin, and try if is working as you expected.
Always is a good idea to have backup before try modifications like this...
So I was able to boot Libreelec on laptop, but not on this HP T620
In that case probably in the T620 bios could be something (boot settings). Did you tried to turn secure boot off, and legacy boot on?
Or I can try an external wifi antenna if that is not possible.
That you should forget unless you have a real soldering skill! For RPi3B I did the modification to use an external antenna, and it's a big improvement. For RPi4B (that part is the same as the RPi5) you can see here: external-antenna-for-raspberry-pi-4
Maybe you can try with an USB-Wifi dongle... but in that case come the question of the driver support...
First of all check your RPi5 hardware, follow the "Da Flex" advice, prepare a minimal RPiOS installation on a new SDcard, only the power and HDMI connection, and you will see if is a warranty case or not.
loop 8 short flashes of the green LED, according to PI5 documentation it means SDRAM failure
That indeed could be a RAM failure (BGA soldering maybe) or a power source issue... or something else. But a full debug log could provide more information. Just don't forget, there is many people using their RPi5 with LE without complains, so is a solid possibility to be something wrong at your setup. Another thing you can easy try, find a spare SD-card and install the latest LE13 nightly build (that's a nice thing in the RPi). Just to see if there is any difference. These nightly builds usually are stable for daily use. One last thing, all the RPi boards have only a tiny wifi antenna, so if you have any posibility, better use cable.
the toggle for wait for Network before booting in the Libreelec settings is not working.
What means for you that "not working"? Because if I remember correctly, that option have a timeout value. So if it set only a few second to wait, when expired, the LE will continue to boot even without network connection.
I'd like to separate media from Libreelec to be able to change Libreelec builds without nuking all my 128GB SD card.
Hi, if that means you want to have all your media files on a separated device, why just don't keep the media files on a large USB stick and the LE on the SD-card? My RPi setup use a "smaller" (64GB) but fast SD-card for LE and a 256GB USB-stick for media storage.
Most machines are in a home LAN behind a NAT router so unless the user explicitly port-fortwards or configures a VPN which results in the device having a secondary (external) IP address they are not exposed. Only a tiny percentage of our active userbase have devices exposed.
That's true, and in case of the LE the risk is obviously small. But those people often like to use a "simple" password where the risk isn't low. It's really need so much "effort" to use a propper password? But I think already was consumed too many time and space for this "why isn't accepted a weak password" thing.
Maybe the best compromise is just to show a warning, and allowing the weak password afterwards.
That could be a good option, as the warning already present for the default password (if I remember correctly). At the other hand... how complicated is to set a "strong" password? Just to have enough characters, including numbers, symbols. And if somebody use the same password on different machines... that's his own and private decision.
And something else about the default/weak passwords... These machines usually are connected to internet. In the case of the weak password, what's the chance to get it transformed in to a "zombi" machines? To be used it by others for something "bad"?
Now I connected RPI to ASUS MONITOR (not TV) using the same HDMI cable like before connected to TV. And the same cable then I connected fresh RPI OS to TV. The tvservice returned me EDID information.
You should think about if your issue it's LE related, why nobody else don't reported it. So as many others (me too) are able to use LE with RPi4, without EDID issue, with your hardware it's wrong something. What you should do isn't a "rocket science", just do what "popcornmix" wrote, without any SDcard, just connect the RPi to display and check if the EDID detected or not:
All tests should be done with no sdcard and using bootloader diagnostic display:
Try with other socket on pi. If hdmi1 also reports EDID=none then it's not the pi socket
Try connecting to another hdmi display. If you still get EDID=none then it's not the display but the cable.
If another display works then your display is not correctly reporting an edid.
If there's another hdmi socket, then try that. Otherwise report issue to you display manufacturer.
Different cable and display show same result. Only those three 4:3 resolutions are available on 3B+, even after fresh installation on formatted SD card.
The 4B connects at 1920x1080 automatically with the same cable. But I agree, this is probably a secondary issue.
So, with the same cable and display the RPi4B working well and the RPi3B+ not. Maybe is something wrong with your RPi3B+. Did you tried with something else, like the "Raspberry Pi OS"? Just to check if with another OS you get the same issue. I'm using now RPi3B, RPi3B+ and RPi4B (now with the latest LE12 nightly), and only once had a display detection issue (last year, cheap bad HDMI cable).
But if I switch HDMI port on TV everything works. I read there it can be problem in 12.0.2.
That is more a HDMI cable problem instead an LE. Use a good quality HDMI cable, the quality of the cable it's more important than the length, I seen laptop connected to a "big" TV through a 5 meters long HDMI cable (wasn't a cheap thin cable 
).... Another thing, some TV's isn't provide EDID (display info) data in stand-by. So, start the TV first, then the LE device. In that case the solution could be to run the "getedid create" command https://wiki.libreelec.tv/configuration/edid#getedid-create
The monitor is actually 16:9 and supports a higher resolution. The 4B also makes use of this, but the 3B+ only offers 640x480, 800x600 and the selected 1024x768. I couldn't get it to set higher one, or any in the correct format.
Hi, I didn't seen any 16:9 display with 1024x768 max resolution (the 1024x768 isn't a 16:9 resolution at all). What's the maximum display resolution detected with RPi4B and 3B+? Looks like the 3B+ using only max. 1024x768, and if the display able for something better, it's a display detection issue there (HDMI cable?). Could you try with an another HDMI cable and/or display? Probably that isn't the main issue, but should be clarified to exclude any conection with it.
