Posts by chewitt

WP2:~ # find / -name brightness
/sys/devices/platform/leds/leds/wetek-play:wifi-status/brightness
/sys/devices/platform/leds/leds/wetek-play:ethernet-status/brightness
/sys/devices/platform/leds/leds/blue:power/brightness

Let's say the blue:power LED is the annoying one:

echo 0 > /sys/devices/platform/leds/leds/blue:power/brightness

Should make it turn off.. and we can script this to run after startup:

echo "(sleep 10 && echo 0 > /sys/devices/platform/leds/leds/blue:power/brightness)&" > /storage/.config/autostart.sh

Should result in the LED being turned off 10 seconds after boot starts. You will obviously need to modify the /path/to/brightness for whatever LEDs are on the board. NB: this only works if the LEDs are GPIO controllable; some LEDs are hardwired.

No debug log = No problem to investigate.

You can power the board off from flirc, but not power on as the USB device is not awake/listening once off. It may be possible to configure a power on event from the IR sensor, but that normally depends on the low-level boot firmware and the device being suspended rather than powered off (so the sensor can receive the power-on code). jernej would need to comment on that possibility.

It makes no difference because we will overwrite the partition table on the card. As long as the OS can see the card, all is good.

The Cubox keymap is probably for an older Linux kernel and will need to be transcribed into the 'toml' format used now. There is a section in the wiki on creating custom keymaps. It needs to be updated to reference the toml format but the files you need to create and their locations are still correctly described. There are lots of existing keymaps in /usr/lib/udev/rc_keymaps/ to crib the toml format from.

Or the whole point of flirc is that you can program it to respond to any remote. If you install the config app on a PC it should take no more than 2 mins to map all the core Kodi functions to remote buttons.

The Generic x86_64 image switched to GBM/V4L2 graphics which means we use OpenGLES rendering not OpenGL required for ProjectM. The Generic-Legacy image still uses older X11 and OpenGL approach, and ProjectM should be available there, but then you lose HDR support. The Goom visualiser is OpenGLES compatible and similar to Project M.

Delete the second half of the file. If it works, the issue is in the second half of the file. If it doesn't, the issue is in the first half. Keep following the same add/remove methodology until you find the problem entry in the list.

There is a prometheus agent add-on for LE users that want to monitor stats on their HTPC (everyone else prefers to just watch movies). If you are trying to develop an application; LE is the wrong codebase to work from as our distro packaging will be rather restrictive.

Kodi filemanager cannot see hidden folders (with a . prefix) unless you enable "hidden files and folders" in Kodi options. Even if you do enable them there isn't much you'll be able to do from filemanager itself so best to learn how to SSH into the box and edit that way.

Re-reading the original screenshot: You ran emmctool without actually having the AMLGX file to write on the /storage partition so it's errored and written no data to the device. Hence boot has still worked. If the box boots; that's where advice stops because I have no interest in wading into the shitfest of atetmpting support for internal installs on hardware I don't have. I've deleted the GT1 image from my test share.

In LE11 Kodi settings can set defaults for subtitle preferences (language choice etc.). Now bring up video settings during playback and enable subtitles and 'set as default' for media.

Quote from WarpLover

CEC?

Probably. You can turn it off in Kodi settings.

I deleted the other random post that bumped a thread from 2019. Install the System-Tools add-on and you have 7-zip as an alternative to normal zip.

And you have a low-spec ARM board with an older Mali 450 GPU. It uses exactly the same mesa/lima graphics as LE10 so I would not expect any significant change to GUI behaviour. IMHO scrolling and navigation performance is more dependent on the remote device being used than anything else.

VNC is VNC .. and works with the legacy Pi codebase in LE 9.2.8. However VNC stopped working on RPi and all platforms using V4L2/GBM from LE10 onwards. It's an inherent problem with how zero-copy graphics pipelines work and a "fix" will be non-trivial to engineer; and we're not aware of anyone working on something.

Users waste an inordinate amount of time fretting about this or that tool for creating the SD card; and in 99.999999% of cases it's irrelevant to LE use because unlike other distros where it might have influence; we aren't converting a bootable ISO into a bootable USB, we are using an image explicitly designed for SD card boot.

The one thing that can sometimes influence boot and/or help with triaging boot issues is using a really old SD card; one that doesn't support fancy high-speed modes that might not always be supported well or require higher stability on the mmc bus.

ffmpeg[0x2a3c318]:   Stream #0:0: Video: h264 (High 10), yuv420p10le(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc

There is no broadcast standard for 10-bit H264 (yuv420p10le) media so almost nothing supports hardware decoding of that format, including RPi4. The file will be software decoded by ffmpeg and that might be a challenge. Traditionally Animé fans have used higher spec Intel kit for their collections; there is still zero hardware decode support on the GPU but the CPU has more grunt for the task. I'd suggest experimenting with transcoding 10-bit H264 files to HEVC. The transcode will be slow, but it's a one-time task and can be scripted easily.

boot=LABEL=LIBREELEC disk=LABEL=STORAGE

^ see if changing from UUID to LABEL works in extlinux.conf

As a general rule whitelist all 3840 4K modes that are visible (ignore 4096 4K) and 1080p @ 60/59.94/50/24/23.98 (23.976). Enable refresh-rate doubling (so 25 runs at 50) and enable adjust refresh. Kodi switches the TV to the native resolution and refresh rate for the media playing and does not adapt playback to 1080p @ 60 which will work for most (but not all) media .. and when it doesn't quite work and you notice; you can't stop noticing.