Posts by chewitt

It won't be unless you install the "flirc_util" add-on from the LE repo and then logout/login over SSH.

There's been recent activity here: https://github.com/LibreELEC/LibreELEC.tv/pull/10592 .. but it reads like some further work and testing is required before things are mergeable.

I'm using a BT remote with an RPi5 on LE13 nightlies for years so I don't think there's a general issue with Bluez. The only issue I have is a few unmapped keys, but that's laziness on my part. I keep telling myself it's a "rainy day" task to update the hwdb file, but as it only rains twice a year (briefly) here it never happens

Connect the RPi directly to the projector and I'll take an educated guess that the 1/4 screen issues go away. Then if you add spliters and adapters etc. inline the issues reappear and you'll know the self-inflicted cause.

I'm not expert on config.txt options but I doubt the HDMI tweaks you added there do anything. Almost all the old firmware tweaks were obsoleted when RPi switched over to the upstream kernel display pipeline (some time ago). Many of the old tweaks have kernel DRM equivalents though.

Quote from dvamg

these should be different boards/dtbs for different boards?

LE is not CE so in some scenarios CE 'fixes' result in something that works better on some piece of hardware. In other scenarios the absence of those 'fixes' results in LE working better. Roll dice

If you run "flirc_util" does it see hardware attached? - are you able to record key-presses, e.g. flirc_util record enter

flirc ^

kernel: mt7601u 1-1.3:1.0: ASIC revision: 76010001 MAC revision: 76010500
kernel: mt7601u 1-1.3:1.0: Direct firmware load for mt7601u.bin failed with error -2
kernel: mt7601u 1-1.3:1.0: probe with driver mt7601u failed with error -2

There is no Realtek WiFi hardware visible in any of the logs shared. There IS a Mediatek USB WiFi device visible in all logs shared and this is missing firmware (as above). The Linux 6.18-rc7 kernel images posted to my test share a few days ago (mentioned in post #4) have the missing firmware added. The latest logs you shared show a Linux 6.17.4 kernel image that does not contain the firmware (although you can always add it manually using the commands in post #2). If you believe there to be Realtek WiFi hardware inside the box you need to pastebin the old vendor kernel dmesg log somewhere so I can maybe see what chip is present.

NB: LE has its own paste server so in the AMLGX images all you need to do is run "pastekodi" and share the URL generated.

Deoptim No further support for you in this forum: https://kodi.wiki/view/Official:Forum_rules/Banned_add-ons

NB: I've removed the download links to the private image as these aren't guaranteed to be free of similar crapware.

Random thoughts:

a) Always use the HDMI port nearest the PSU connector

b) Are you using any kind of micro-HDMI to HDMI adapter? .. or a proper micro-HDMI to HDMI cable? - If you are using an adapter, this is probably the source of the problem.

c) If using a proper micro-HDMI to HDMI cable (no adapter) put Kodi in debug mode, reboot, then SSH in and run "pastekodi" and share the URL .. perhaps we can see something.

video=HDMI-A-1:1920x1080M@60D

Add that ^ to boot params in cmdline.txt and the initial DRM state is forced to 1080p and that should stop the image being in 1/4 of the screen?

The colour change is probably the projector switching itself to a different RGB output mode. It’s nothing that LE/Kodi can control.

LE will update from .tar file (can be found in the same dir on the webserver) or from the .img.gz file.

No. Docker virtualises the app not the environment it runs in. So the container provides ann app which still requires a windowing environment to run under, and this still does not exist.

There is a browser called Ozone which can in theory run under GBM, but this needs to be built from sources and has a ton of dependencies so nobody has ever volunteered for the huge effort of trying to implement it for LE.

Just force-refresh the repo.

Please update to this image https://chewitt.libreelec.tv/testing/LibreE…-12.90.1.img.gz and the adapter should work now? If yes I will send the required kernel patch upstream.

NB: the image is LE13 but this should be stable for normal use.

It looks like the device ID's are not recognised by the kernel and a patch is required.

Please run cat /sys/kernel/debug/usb/devices | paste and share the URL

Quote from thedogg

I was pretty sure pi5 allows for multiscreens.

RPiOS can create a single 'desktop' over mutiple displays but then Kodi runs in a window on the desktop and you have to choose which desktop you want full-screen output on (as Kodi does not handle multiple screens) and you cannot 'adjust-refresh' display mode to suit the media being played (as Wayland does not allow this).

The closest you can get is stopping Kodi, editing config files with scripts to change outputs, then restarting Kodi. There is no way arouond the stop and restart because Kodi does not support dynamic change of video output.

I would describe the scripting approach as fragile. Feel free to experiment, but don't be surprised when it isn't reliable.

Kodi supports outputting at 1080p and switching to 4K only when required, but it cannot handle dynamic changes of HDMI output and it has no concept of fallback logic for HDMI connections. IMHO the best solution will be to send everything to the AVR and use the video/audio source mapping functions there to deliver the output routing you want.

In short, LE will not do what you require, and as the Kodi featureset is pretty consistent on all platforms I don't think any other distro or OS platform will do it either.