Posts by tecc

chewitt
Yeah, I expected this coding stuff to go right over my head. So what version can I downgrade to to get working subtitles until mesa issues 12702 is fixed? Thx.

Da Flex
Issuing the reboot command via SSH makes no difference to rebooting from the GUI: the screen stays black, I cannot connect via SSH any longer and I have to power cycle the Odroid to get back into Kodi.

Thanks for the tip with CEC, I've changed the settings and now it's working fine. Apart from the reboot that's still not working. Is there a way to determine my Odroid's harware revision? Can it be fixed by software?

chewitt

So where should I check regularly to see whether the subtitle bug is fixed?

Unfortunately not. Here's what happens:

When I reboot the Odroid, I only get a black screen on my TV and can't connect to it via SSH. Only when I power cycle it, LibreELEC boots and I can watch my media. What's even weirder though: when I'm connected via SSH and turn off the TV via the remote (setting it to standby), I can no longer browse the directories, WinSCP reads 'Network error: Software cause connection abort'. When I turn the TV back on, the screen stays black. Only when I power cycle the Odroid, I get back into Kodi.

Thanks for clearing that up, chewitt. Unfortunately, there's a new and weird issue now that I've upgraded to this version:
My TV, Odroid and dumb switch are all plugged into a power strip with switch so it's disconnected from power when I don't use it. When I turn it on, LibreELEC only boots up to a black screen showing LibreELEC (chewitt): 12.80.0 in the top left corner and that's it. Pressing the source button on the TV's remote shows a resolution of 3840*2160P 30 Hz despite having been set to 1920*1080P 60 Hz before shutting it down the day before.

Now, if I unplug the network or HDMI, nothing happens: still a black screen with LibreELEC (chewitt): 12.80.0 in the top left corner. However, if I unplug the Odroid's power and plug it back in, the system boots up normally to its 1920*1080P 60 Hz resolution. I can switch between TV and Odroid or other sources (like my RPI5) without any issue.

BUT when I turn off the TV (so it's in standby) and turn in back on, and select the Odroid as the source, again I only get a black screen despite it having successfully booted before. I must unplug it from power to get it to boot again. I have not seen this behaviour on 9.2.8. Any idea what's causing this?

Thanks chewitt, I've just tested it and it works, here are my observations:

• local playback from USB flash drive works fine - great!
  
• rebooting the system via Power > Reboot does not work, the screen stays black, I don't even see the LibreELEC logo; I have to unplug the Odroid to do a fresh boot
  
• subtitles are not being displayed (known issue in K22 as you've mentioned above)
  
• forced subtitle flag is ignored, the regular German sub is selected instead, most likely cause I've set my Kodi to German;
  (this issue may be related to the one listed above)
  
• how come neither Settings > System Info nor Settings > LibreELEC mentions what version of Kodi is actually running?
  I see LibreELEC 12.80.0 but not that it's Kodi 21.2 - I find that strange
  
• NTP time server selected on first boot does NOT show up under Settings > LibreELEC > Network > Time server
  I have to manually add it there again
  
• during initial setup I switch the system to German, however, Settings > LibreELEC > System > Keyboard still shows 'us' instead of 'de', and Settings > User Interface > Regional > virtual keyboard is still set to QWERTY instead of QWERTZ. Even after having done so the English layout is still active, I get Y when I press Z and so on. Weird.
  
• despite all devices on my network being members of the same 'workgroup', I cannot access my desktop's share by its name but I have to add the source via IP instead
  

BTW, would an update via putting a tar file to /storage/update have worked as well? Also, is there a way to mount the contents of an IMG file (on Windows)? I've tried mounting your image in Virtual Clone Drive but it did not work. 7zip shows

0.fat 536.870.912
1.img 33.554.432
2 1.048.576

but I don't know how to access the files in 0.fat.

Right, so I've found the tar file here and did the downgrade which worked fine, now the subtitles are shown again when playing back files from my network share. However, when I plug in a flash drive into any of the 4 USB ports of the Odroid, it's not being recognized and I can't play back files locally. How come?

Sorry, but where do I get this tar file? Is it also a known problem that the USB ports do not work? When I plug in an USB flash drive nothing happens. When I boot from my Coreelec SD card on the same hardware, the flash drive is recognized and I can play back the files on it. Thx!

Thanks, chewitt, that did the trick. However, what version of Kodi is this, 22.0? I'm getting no internal SRT subtitles when playing back the exact same MKV from my SMB share that are shown just fine in Kodi 21.2 on my CoreELEC player. I really like the stream selection button that in the lower bar but when I select the sub stream, it still won't get shown.

EDIT: Played back the same file locally, still no subtitle shown.

Hi guys,

I'm not sure I understand the section on board images correctly but apparently writing

LibreELEC-AMLGX.aarch64-12.0.2-odroid-c2.img

or even

LibreELEC-AMLGX.aarch64-13.0-nightly-20240504-1a2bcb3-odroid-c2.img

on the SD card and turning on my Odroid C2 is not enough, it does not boot. What am I missing?

Quote from dtech

In short: it is necessary to execute the "toothpick method" again, because aml_autoscript is executed only in this case.

Thanks again but I seem to be confused about the terminology. It's been a while so I can't be sure but I don't remember having used the toothpick method for anything to make 9.2.8.8 - Kodi 18.9 run on my box, especially since I kept booting LibreELEC from the SD-card. Now, I would like to upgrade to the latest version that can run on my box. Can any of you point me to the correct img to download and what dtb to use and boot process to use? Thx!

Quote from dtech

For versions based on the mainline kernel (LE10+), the dtb setting is different compared to legacy versions. Please check if you have done the settings correctly as described in the description: https://wiki.libreelec.tv/hardware/amlogic#box-images

Thanks for this info. The legacy version booted straight to LibreELEC without the need for pressing the reset button on my device and I'm perfectly fine with not having it boot from the internal eMMC storage. So, I've added this uEnv.ini to the root of the SD-card:

dtb_name=/dtb/imagename.dtb
bootargs=boot=UUID=2306-0801 disk=UUID=8268da37-3a8d-4f6d-aba0-08918faded56 quiet systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0

referencing all dtbs found in the 'LibreELEC-AMLGX.arm-11.0.3-box.img' (which hopefully is the correct one) contaning 'meson-gxl-s905x', starting with 'meson-gxl-s905x-p212.dtb'. To no avail, the system is stuck at the boot screen showing the S905X logo. Am I using the wrong image/dtb?

Quote from dtech

Without a built-in tuner, the S905D doesn't make much sense. Based on the photos and the description above, it has an S905X SoC (this X is not a wildcard character, it is a real X.), so I recommend the MXQ-4K-Pro_2G image for testing, without any dtb replacement.

Thanks for replying with this to my question from some time ago. I've been running LibreELEC (dtech) 9.2.8.8 - Kodi 18.9 Leia ever since but for the life of me can't remember exactly what dtb.img I actually did use (here's the MD5: 4c723801b797f26828caed55ebec8b32 in case that helps) . Since CEC sudddenly does no longer work on a friend's TV of mine (who owns the same box), I was planning to use the original remote, so I've downloaded LibreELEC-AMLGX.arm-11.0.3-box.img.gz and tried renaming each of these

meson-gxl-s905x-hwacom-amazetv.dtb

meson-gxl-s905x-khadas-vim.dtb

meson-gxl-s905x-libretech-cc.dtb

meson-gxl-s905x-libretech-cc-v2.dtb

meson-gxl-s905x-mecool-m8s-pro-plus.dtb

meson-gxl-s905x-nexbox-a95x.dtb

meson-gxl-s905x-p212.dtb

meson-gxl-s905x-tbee.dtb

meson-gxl-s905x-vero4k.dtb

to dtb.img but none of those worked on my Xoro HST 260 S. What am I doing wrong?

Hi guys,

CEC suddenly stopped working with my Xoro HST 260 on my ex's Samsung TV so I thought why not update from LibreELEC 8.2.3.1/Kodi 17.6 Krypton to the latest version to see if it'll work again there? The player comes with 2 GB RAM and an AMLogic S905X, so what version should I use?

LibreELEC-AMLGX.arm-11.0.1-lepotato.img.gz or LibreELEC-LePotato.arm-9.0.2.img.gz

Also, how do I create a bootdisk for my SD Card under Windows? When I simply write any image to the SD, the player does boot from internal memory to Android which I wanna avoid. Unfortunately, I really can't remember how I made it work the last time and I seem to be unable to come up with the proper search times to find a step-by-step guide to set this up. TIA!

Hi guys,

can you please tell me what image to use to update my Xoro HST 260 S to the latest LibreELEC that can be run on it? According to the OEM's webpage I save back in the day, specs are

CPU: 4x 2.00 GHz S905D QuadCore Prozessor

RAM: 2 GB (DDR3)

Video: Mali 450 QuadCore GPU

Internal RAM: 8GB

OS: Android 6.0 Marshmallow

but I'm not sure about the S905D cause the bootscreen says S905X (don't know if X is simple a wildcard).

Since I'm also having issues with my Odroid box and I've got 2 more Xoros hooked up to various TVs in the house, I would like to use a tool to generate an edid.dat file to make sure the proper video settings are used on boot. How do I do that? Thx!

I have only one cable I can use for the Raspi 4 due to the mirco connector on one side. This is the cable that actually worked that one time where Kodi automatically set the GUI size to 4K. So I doubt it's the cable. I just don't get why this setting appears to be lost on reboot or whatever the reason might be that after reboot I can't get a picture like I got before. Anything else I can try?

So, I've added hdmi_safe=1 to the config.txt and rebooted, switched HDMI ports and then configured Kodi via the GUI. When I rebooted manually, I only saw the initial boot phase on 640x480 up to the multi-coloured square but then then my TV's screen stays dark. The TV is capable of 4K on Kodi which works fine with my Odroid and CoreELEC using the same HDMI ports but I would rather use the Raspi 4 instead. What can I do to get video? Thx!

+ x$ for the screen. Well, gonna use Bodhi Linux or something. If all else fails, Win 7 + Winamp it is.

So, it IS actually the NX bit? An otherwise discarded laptop is quite good as a jukebox, though.