Posts by chewitt

The terminal add-on in our repo allows you to access an SSH console from a browser. Or you can do things the normal way and use any SSH client from any OS. There is no terminal within the Kodi GUI at all, and no plan to ever add one. ChatGP is not infallable.

LibreELEC.tv/linux.aarch64.conf at master · LibreELEC/LibreELEC.tv

Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.

github.com

^ The driver is enabled in LE11 nightly images:

https://test.libreelec.tv/11.0/RPi/RPi4/LibreELEC-RPi4.arm-11.0-nightly-20230111-6d10ebf.img.gz

NB: LE does not support direct update from LE9.x to LE11. If you attempt it the update process should automatically fail but it's possible for users to override those checks. If you do that, the update *will* 100% break booting because the vendor and upstream boot processes are completely different.

If eMMC is wiped this image will boot from SD/USB: https://chewitt.libreelec.tv/testing/LibreE…etek-hub.img.gz and once LE is running and you have SSH access you can download the same image to /storage and write it to eMMC using emmctool.

If eMMC is not wiped and vendor u-boot is still trying to do some form of recovery the following are the factory update/restore images that can be loaded from SD/USB to recover the Android OS. These are not Amlogic burning tool images (which I don't have).

dtb.img

Shared with Dropbox

www.dropbox.com

recovery.img

Shared with Dropbox

www.dropbox.com

factory_update_param.aml

Shared with Dropbox

www.dropbox.com

If eMMC is not wiped but vendor u-boot cannot recover things (is broken some way) the worst case scenario is to open up the box (screws are behind the foot pads) and short pins on the emmc chip to disable it. This prevents vendor u-boot (or whatever remains of it) from interfering in boot and effectively forces SD or USB boot; so you can use the AMLGX image I linked above. It works but most users feel uncomfortable about sticking screwdrivers on memory chips to short pins and it's best done with UART access so you can see what's happening.

In all cases, having the UART cable that WeTek shipped in the box connected so you can see what's actually happening and/or where things are failing is always a good move.

Quote from gulliversreise

Hi! Is there a step by step guide on how to install LE 11 test image on wetek play 2 to boot from sdcard?

Write the "box" image to SD card, edit the dtb name in uEnv.ini to use the WeTek Play 2 dtb (do not rename the dtb) then force recovery mode boot via toothpick method. There's a longer version here: https://wiki.libreelec.tv/hardware/amlogic

I moved the post from my Amlogic support thread since you are clearly not running Amlogic hardware.

Quote from Reddirt

I think this addon is kinda like an orphan child and as long as it works (mostly) I doubt the devs have the time nor inclination to dedicate their time and energy to a limited audience of users as it will only work on the x86 builds.

That's a reasonable assessment of the situation. We *would* like it to always work, but it's never the highest priority.

Quote from Masutin

It appears I need builds marked as 'box'. Is my only source http://test.libreelec.tv/11.0/Amlogic/box?

Builds for 10 are not for Amlogic (http://test.libreelec.tv/10.0/Generic), so unsuitable?

Experimental LE11 test images are here: https://test.libreelec.tv/11.0/Amlogic or https://chewitt.libreelec.tv/testing/ nothing else will run on Amlogic hardware. If there is no specific device-tree for your box you will need to experiement (lots of devices are similar.. we have no idea what specs/hardware your box has). Note that the boot process is different to legacy images. There are no LE10 images (or nothing worth using). There is zero support for piracy images like AE in this forum.

The V4L2/GBM video pipeline changes don't make software grabbing as simple as it was before, so I wouldn't expect to see much movement on the add-on being updated anytime soon. If Hyperion is a must-have for you, an external/hardware grabber is the way forwards.

I've blind copied the udiskctl command from your original script. On closer inspection we don't bundle this utility in the OS; hence the failure message that you see. You'll need to sub some other method for turning disks off (or at least parking heads) - perhaps hdparm?

#!/bin/bash
for mount in $(awk '/\/dev\/sd/{print $1}' /proc/mounts); do
  umount -f $mount
  sleep 2
done
for disk in $(ls /dev/sd* | sed 's/[p0-9]*//g'); do
  udiskctl power-off --block-device $disk
  sleep 2
done

^ Split into two steps

Quote from jim_p

Moreover, please tell me if your le 10 AMLMX image can boot straight from usb/sdcard (all black mxq running le 9.2.8.x from emmc). I have a 30-45 minute break tomorrow and I want to test it as much as possible.

It's highly experimental and I have no time to coach users on what it might be like .. so I'd rather you ignored it.

Quote from jim_p

Can you please show me the AMLGX thread?

libreelec AMLGX - Google Suche

Kodi and its scrapers are designed to work with relatively standardised naming formats and the single best way to avoid naming issues is to use the right formats when you rip original media. You can start by sharing Kodi debug logs showing a library update/scrape so we can see what might be happening.

2023-01-07 11:55:21.524 T:852     debug <general>: OnPlayBackStarted: CApplication::OnPlayBackStarted
2023-01-07 11:55:21.525 T:1231    debug <general>: Thread BackgroundLoader start, auto delete: false
2023-01-07 11:55:21.531 T:1186    debug <general>: Loading settings for /media/ExternData/HDD/Filme/0-Test/4K/Dolby Vision FEL Test Samples/FEL_test_for_AVS.mkv

There is no support for Dolby Vision at this time, and that file doesn't appear to have other (normal HDR) tracks to fall back onto.

I'm not familiar with OpenATV .. so how does it save/record media and what format/location are subs being save to (or embedded in)? - And how are you playing back the recordings? (from a shared, IPTV list, etc.)?

#!/bin/bash
for i in `ls /dev/sd*`; do
  umount -f $i
  sleep 2
  udiskctl power-off --block-device $i
  sleep 2
done

^ That should unmount disks before powering down the drive. Also, you probably want to block the shutdown process while this is done so background the commands like autostart.sh