You can enable "adjust refresh" in Kodi player settings, but the system will need to have a native 23.976 mode or you'll need to use an edid.bin file to fake a connected TV with more modes. The old method you found is not possible in the modern kernel used now.
Please run "pastekodi" and "modetest | paste" and share the URLs so we can see what modes and timings exist.
I’ve done a search and found out that this is a thing with LE, but I’ve never experienced this with Kodi before. Is this a known issue?
I've never seen issues (or similar reports) with H264, so 
Is the box connected via Ethernet or WiFi? .. some wireless routers isolate devices on the wireless network so e.g. WLAN connected iPad will not be able to reach WLAN connected LE device. Connecting the box to Ethernet would fix that. Or it might be the app having an issue with the SSH certificate algorithm being used (although unlikely I think).
Pls create an SD from https://chewitt.libreelec.tv/testing/LibreE….0.2-box.img.gz and set meson-gxl-s905x-nexbox-a95x.dtb in uEnv.ini. I doubt it will help the SSH issue but hopefully HDMI audio and the IR remote should work out-of-box now? If you're able to access the box via SSH please run "pastekodi" and share the log file URL. The dtb could use some other cleanup/changes but one step at a time.
Apr 06 06:12:00.956410 LibreELEC xorg-launch[615]: ================ WARNING WARNING WARNING WARNING ================
Apr 06 06:12:00.956410 LibreELEC xorg-launch[615]: This server has a video driver ABI version of 25.2 that this
Apr 06 06:12:00.956410 LibreELEC xorg-launch[615]: driver does not officially support. Please check
Apr 06 06:12:00.956410 LibreELEC xorg-launch[615]: http://www.nvidia.com/ for driver updates or downgrade to an X
Apr 06 06:12:00.956410 LibreELEC xorg-launch[615]: server with a supported driver ABI.
Apr 06 06:12:00.956410 LibreELEC xorg-launch[615]: =================================================================
Apr 06 06:12:00.956410 LibreELEC xorg-launch[615]: (WW) NVIDIA: The driver will continue to load, but may behave strangely.
Apr 06 06:12:00.956410 LibreELEC xorg-launch[615]: (WW) NVIDIA: This driver was compiled against the X.Org server SDK from commit e6ef2b12404dfec7f23592a3524d2a63d9d25802 and may not be compatible with the final version of this SDK.^ this reads like we bumped Xorg in LE11 to a version higher than the nVidia legacy driver supports. As a result there is no OpenGL and Kodi cannot start. And if I re-read the LE10 log now it appears to be running but also prints an swrast error (not sure why it would be trying to uset that though). GeForce 8200 is an ancient card now (2008) so I'm wondering if the current legacy drivers go back far enough?
I'm not sure what the issue is here, but ping heitbaum CvH for awareness
The normal instruction would be to install the autoexec service add-on. You also need to ensure that the autoexec.py script works. If it doesn't perhaps the wrong commands are used? .. which should be visible in a Kodi debug log.
I'm looking in the LE(11) repo on my daily-driver RPi4 box and I can see pvr.filmon client listed and published.
Should I always use nexbox a95x as hardware now ?
Yes please. It's useful to have a known reference that the dtb works. If you see any issues, we can track them and (hopefully) fix them.
NB: Does the box have an IR remote? If yes, do you have a working keymap for it?
It's something to ask Kodi devs via their forums. Their feeds are nothing to do with LE.
Please update to LE11 and redo. I explicitly want to see the output from kmsprint which is included in the pastekodi output in LE11.
One more change: https://chewitt.libreelec.tv/testing/LibreE….arm-11.0.2.tar .. the vendor kernel runs the SDIO module at 50MHz but let's see if it's happy to run at 100MHz? .. If it's still connecting please try scp'ing some large files to/from the box to prove the mmc is stable at the higher speed. If it's not I can down-clock back to 50MHz again.
On the negative: Realtek maintains a driver fork for each chipset variant they shipped despite the differences between variants in the same family often being very minor, and they breed new variants like rabbits so there are probably 30+ drivers in circulation. Realtek only releases their drivers to their paying-for-support customers (end-users are not their customers) so end-users have to rely on board/device vendors sharing them; over time things generally leak to GitHub but it results in 500+ repos with slightly different versions of the same "posted once and never updated again" driver being available to confuse people. There is a large amount of common boilerplate/duplicated code in each vendor driver, and while the vendor drivers generally work okay the overall code quality is low as the drivers have never been subjected to any serious peer review during development. Frequent minor changes to upstream kernel frameworks frequently result in all the drivers breaking and needing to be patched so the drivers are a pain in the arse to maintain over time. The fact the drivers are released with a GPL license is good, but that's about the only good thing to report. Distro maintainers loathe these drivers.
On the positive: Realtek have finally embraced upstreaming their drivers and are now contributing-to and maintaining a single driver per chip family. However their primary interest is in PCI/USB drivers and the SDIO ones are often forgotten, and this is a relatively recent development so they are only investing time/effort into the latest chipsets that nobody is really using yet, not the older chipsets that are endemic. They do comment on patches for older chipsets/drivers when asked, but community developers are the primary source of development for the older chipsets. So future support looks better, but support for everything shipped in the last decade is still a bit sucky.
I'm not sure why the Realtek driver is flagged as staging in Debian (something for Debian maintainers to explain) but I am 100% confident this is the legacy Realtek vendor driver and not the upstream kernel staging driver.
Please do "pastekodi" over SSH and share the URL so we can see what's detected/connected.
Have you enabled "disable password auth" in SSH options? - this will not stop the box for prompting for a password if you connect, but it will stop passwords from ever being accepted.
Are you using the original remote for the box? .. If yes, can you share the files? - I can see the issue with audio; the required sound-card nodes are missing from meson-gxl-s905-nexbox-a95x.dts. This is simple to fix and I would like to add audio/remote and have you test.
I added the driver in the rtl8189fs branch of this repo: https://github.com/jwrdegoede/rtl8189ES_linux/branches
The rtl8189es driver that was already in the image is from the master branch of the same repo (and searches for the 'fs' driver point to that repo). It's common for an RTL driver to support multiple differently-named chips (hence it claims to be RTL8188F in dmesg) .. all part of the garbage and support debt that comes with not-upstream old vendor drivers.
These drivers are not (and will not be) submitted to the main LE repo. I'm going to leave them in my private image for a while; I don't make any guarantee they will remain in my image so at some future point you might need to discover self-building LE images. Historically the RTL vendor drivers break with every kernel major-version bump and we bump kernels frequently so playing "hunt the patch" gets tiresome.
You'll need to share UART output from the board.
In short, no. You can install another Kodi client configured with the same add-ons/sources of media on the other TV. You cannot stream from one LE instance to another Kodi client; Kodi is not a 'server' application that streams media.
cd /storage/.update
wget https://chewitt.libreelec.tv/t…ELEC-AMLGX.arm-11.0.2.tar
rebootPlease update again. That's ^ all you need to do. I think it should probe the right driver now; if yes it will probably fail to load firmware but that will show an error and we can see what's missing.
Any ideas why odroid-c2 can't boot with 11.x versions?
The "odroid-c2" board image has the largest number of active AMLGX installs so I'd guess PEBKAC
Have you read the wiki instructions? https://wiki.libreelec.tv/hardware/amlogic
