Posts by chewitt

Quote from salvador

There is no details how to connect video on a specific HDMI

On LE, Kodi does not run under a desktop/windowing environment so display selection is not possible. Instead Kodi will output on the display connector that probed first, and because hardware probe order cannot normally be guaranteed it is not possible to pre-determine which connector will be used.

On a general purpose Linux distro with a desktop/windowing environment you can move the Kodi app window to a specific display and the OS will (or should) remember this, and Kodi will allow you to select a specific display for full-screen output.

In both cases you should be able to select a persistent audio output device in Kodi settings.

It will not be possible to run released versions of LE11 because the latest hardware (and CPU stepping) requires mesa changes that do not exist in the embedded version of mesa. There are also boot firmware changes required, although that's less complicated as files from newer releases can be literally drag/dropped on the older SD card. I can't comment on whether newer mesa is a simple or complicated. Changing the package in the buildsystem is simple, but whether it then compiles or fails on other dependencies is the $64,000 question. There is no HOWTO guide or writeup on doing that kind of thing, and I doubt project staff will leap to volunteer at spoon-feeding instructions.

Why LE11? .. I can't think of any good reason not to use something newer

Given the immense size of the RPi userbase and attentive support it receives from their developers; if there was a real-world issue with current practice it would have been attended to.

There was some activity last month https://github.com/raspberrypi/linux/issues/6867 but as nobody has submitted a demand for us to bump the add-ons to something that includes usable code yet, I would assume development is still work in progress.

RPiOS and LE use identical firmware, config, and kernels. If it works in one it should work in the other.

Have you tried hdmi_force_hotplug=1 ? - I'm not 100% sure this is still supported in Pi firmware but worth a shot.

Quote from Elicity

I could reproduce some I think: I use the HDMI-port closest to power-port, when I use the other one CEC does not work.

That's intentional and expected. CEC is only supported on the HDMI-A-1 connector (nearest the USB-C power port).

Have you tried a different HDMI cable?

If the device is not showing up with "lsusb" then the device is either not connected, not connected via USB, or perhaps has not been powered up (might need something toggled during boot or a dedicated regulator to be described) as the output of the command is a raw read of the devices attached to the USB bus and there is no need for anything to be "supported" with drivers etc.

NB: device-tree will only describe the connectivity for the USB hub/ports, there's no need to describe attached USB devices because once ports are probed/discovered anything attached to them will be probed and have supported drivers loaded automatically (as it's USB). Asmedia chips are normally supported by the generic "CONFIG_USB_UAS" driver which is enabled by default in LE images; and I would assume in ilmich images too.

Pastebin the dumped device-tree file, someone else might see something in it.

If the WiFi/BT module in your box is QCA9377 (as with that user) the device-tree file you are using either describes a Broadcom SDIO module and neither WiFi or BT will work, or this patch is applied: with https://patchwork.kernel.org/project/linux-…[email protected]/ and WiFi will work, but the BT module is connected via serial UART connection; and since Broadcom and QCA9377 modules run at different speeds etc. this will not work unless the device-tree file correctly describes how it is connected.

I have zero knowledge on Batocera and will not be building custom Batocera images to guess at fixes, so you need to go report the issue to Batocera developers via their forum and follow their guidance.

Quote from Emaitaly

I'm trying Batocera on an old Android Tv Box... GooBangDoo XB-III - AMLOGIC Quad-core A53

I suggest you post in the Batocera forum then, because we do not support Batocera here.

You will need to configure Tvheadend, then install the pvr.hts add-on and configure that to connect to the Tvheadend instance.

1. Raspberry Pi 5 boards are a small and well supported device for LE use.

2. I've never heard of Kodi being sideloaded on Roku things (but then I don't have any interest in Roku so..)

3. Android HDMI sticks are popular for running Kodi, if you like or can tolerate Android.

4. Android smart TV's are smart as long the the OS is maintained (sometimes yes, sometimes no).

5. You can run Kodi natively on modern WebOS (LG) TV's now, although it requires some developer mode hacking.

This forum is going to be rather limited to LE oriented ideas and opinions though. The more popular home for "best thing for Kodi" type threads is the the Kodi forum.

Quote from jim_p

Has anything changed since le 11? Because there is no dtb folder in there, just one named amlogic

The dtb folder was renamed to amlogic to align with upstream u-boot conventions. Hence when you switch from an invalid path to the dtb file (dtb) to a valid path (amlogic) the device booted. The update process knows about both locations so it doesn't matter whether you have an old style (dtb) or newer style (amlogic) filesystem layout, the update will be successful.

Quote from jim_p

it booted... after like 2-3 minutes of being "stuck" in the le and kodi splash screens!

Most likely performing a DB upgrade.

Quote from jim_p

So what do I do now?

Your conversaton has wandered all over the place so i've lost track of what you were trying to do (sounds like you forgot too)

If you want to put content in a Library view (Movies/TVshows) then you MUST scrape the content. If you don't want to scrape from an online source you can provide your own .nfo files (one per episode) and use the offline scraper. If the offline scraper is not doing what you expect; either you have invalid expectations on how it works, or it's disagreeing with content of the files and failing to use them. To triage what might be going on you'll need to share a Kodi debug log so we can see verbose output as the scan/scrape takes place and what info/error messages are generated.

NB: Each time I see people flailing around trying to get some custom filesystem structure or content to scrape I'm wondering why folks don't just use the 'Videos' non-Library view to find and play media. It's not a fancy view. It will still track watched status. It requires zero config and effort to use.

Quote from xixi22

Cant edit then add logs here

There's a time limit on editing posts to stop human new-user spam-bots posting something innocent (which gets approved) and then editing the post later to embed links to whatever thing/service they're pushing. Pretty standard config for forums.

It's bundled with the second/alternative LEIoT distro that's now part of the LE buildsystem.

polo_joe Compose is not included with the standard Docker add-on because it's a HUGE file. I will get around to submitting a separate add-on for it at some point so it that can be downloaded alongside Docker if required. Until then you'll need to wget an appropriate arch file from https://github.com/docker/compose/releases to somewhere on /storage and execute it manually.

Quote from dominion

Maybe bug came back again?

Nope.

Share a Kodi debug log that demonstrates the issue.