Posts by chewitt

Lesson #1 for all remotely supported tvbox devices is .. make them use Ethernet. Yes the cable is inconvenient. Yes it will save you many hours of remote support effort. In situations where I've been forced to use wireless I prefer to recycle an old Apple A1rport express device so the less-than-reliable TVBox OS is still connected via Ethernet, because ancient vendor wireless drivers in ancient vendor kernel have limits on what they will support reliably - I prefer to remove them from the equation.

Not impossible, but as they observe, there is no apt-get so you need to build dependencies into the image. Easiest would be a custom image that adds pigpiod and other bits to the image and IIRC WiringPi is one of the Pi add-ons in our repo. Once you've gotten to that stage it's not a huge leap to then repackage things as a binary add-on that can be submitted-to and then installed-from our add-on repo. The demand is likely not that high though, so I'd build it for yourself and push the sources to a GitHub account so that anyone else seeking the same can repeat the process.

Options=username=<username>,password=<password>,rw

What happens if you remove the version forcing and let things negotiate normally?

At launch there were 1GB RPi4 boards, but 2GB is now the minimum configuration and this is fine for Kodi use; the 4GB or 8GB boards are also good. These days most users have media on a NAS accessed over the network or an external USB drive so a kit with a less expensive 8GB or 16GB SD card would be fine, there's nothing in LE that would ever really need/benefit from a 128GB card.

At some point we will dump Xorg and switch Generic to GBM/V4L2, but we're aware of a number of HDR related use-cases that still need work (in drivers and in Kodi). However the devs who've been working on this are limited in number and right now real-life is rather busy for them, and K20 is super-early in the dev cycle so we're not in a rush.

I'm not sure what the cause/problem is but I've seen this at some point recently too. You can SSH into the box and use "bluetoothctl" to perform the pairing as a workaround. Same basic process (as the settings add-on drives the same API) but no GUI to go wrong.

Nothing has been done to explicitly alter or change 3D support. That said, nobody on staff uses 3D so it wasn't tested either.

Kodi saves settings on exit and it’s possible for save actions to be incomplete.. and on restart of a partial file is detected you can lose settings.

Thanks. I googled the name and only found pirate addons at first. I found the addon psd earlier so I’ll share a couple of icons later.

celedhrim Can you explain what the prometheus add-on does please?

I can share the original photoshop PSD file used for other icons when I get back from vacation. For now just send the PR with any icon.

NB: remind me in a week or so .. I will forget about this

I did a little vacation fiddling for Radxa Zero support the other day so there are some 10.0 images on my share again. Kernel is 5.14rc5 and uboot is 2021.07.. but nothing apart from the Zero image is tested and there are no real-world changes to video/audio support although HEVC is enabled and may work on GX devices with 8-bit output (it will prob crash on newer devices or 10-bit media). Usual rules apply; I’m not “supporting” the images so if it works that’s nice. If not, there’s no need to comment unless you also found a fix for something.

CE has never supported the Amlogic 32-bit SoCs so that’s not an option. Meson8 (S805/S802/S812) is slowly gaining mainline kernel support and we may release for them again in the future but there is no activity on Meson6 (8726MX) so LE 9.0 is the last and final release for WeTek Play 1 boxes.

Not that I’m aware of, but I have zero interest in torrent things (smells like piracy to me) so I’m not looking for anything.

Quote from balbes150

I don't have any working devices with AML left, so I don't test or release them anymore.

Closing this thread. Please use Official LE Test Images for Amlogic (Kodi-19)

The video drivers in LE 9.2 are not functionally complete. Please retest with current LE10 images.

For HDMI devices the audio output properties in Kodi are determined from EDID data read (once) at boot time. Modern AVRs pass-through the EDID from the downstream HDMI device, e.g. projector or TV, so I'm wondering if the HTPC is reading EDID data from the AVR itself (as the projector is not on) and then after turning it on the HDMI properties change and cause some issue.

Have a look at the EDID output from "modetest" after boot with the project off, then reboot with it on. If it's changing .. follow the instructions in the wiki to capture and use a static EDID file so the HTPC always sees the projector as on (with the right EDID data).

No guarantees that's the issue, but we do see odd things when people turn things on after the HTPC sometimes. It's just a hunch.

The one that is being used.