Posts by dtech

Quote from suppenkasper

Do you see any chance to get this to work or can someone else help to find a working solution?

In the leading post of this topic, I also indicated under the description of the device:

Quote from dtech

5. Amlogic Meson6 (AML8726-MX) SoC on Linux kernel v3.10.108 (LTS):

• WeTek_Play | WeTek Play (a.k.a. WP1) with AML8726-MX SoC (1 GB RAM, 4 GB NAND) and a modular removable tuner:
  Working services: Power status LED, CPU temperature sensor, Analog+S/PDIF+HDMI audio output, 10/100 Mbps Ethernet, Wireless (2.4 GHz), Bluetooth, RF+IR combo remote control (HID+amremote), HDMI-CEC*, NAND boot**.

...

* On some TVs, this can cause instability, but in this case it is worth turning it off:

Settings -> System -> Input -> Peripherals -> CEC Adapter

Unfortunately, many features of the WeTek Play (and Meson6-based boxes in general) are far more unstable/unusable than even an S805/S8X2, even though they are based on the same kernel. These include the CEC service, but has also some audio and network based issues, including Bluetooth-related that are either unstable or can cause the box to freeze for no reason, which can only be helped by unplugging/replugging the power adapter.

Therefore, it can only be recommended for basic tasks. For example, WP1 may still be suitable for a headless tvheadend server.

Sorry for the late reply, but I was busy over the weekend.

Quote from thadrumr

My lockup is definitely related to the Ethernet port. It must not like either the multicast traffic it's receiving or possibly the LLDP it's receiving. It was connected to a Mikrotik CRS125 switch that is broadcasting LLDP on all ports and there is some multicast traffic on there as well.

I've experienced similar network anomalies before, as I have multiple MikroTik devices on my network, including the main router. Although I've only had issues with some IP cameras and DVRs, it wasn't easy to track down the source.

Quote from thadrumr

This MXQ has a SPDIF output to my Yamaha receiver to maintain digital connection. I just use one of those standard 1/8" to dual RCA cables and use the left (White) RCA cable for the SPDIF connection to my receiver.

I created a media converter for it so that I could use it with Toslink. (S/PDIF 3.5 mm Jack -> RCA -> Toslink)

Quote from xixi22

I mean locate issue in ISA default konfig. My issue is in TV PVR switching channels and this use plugin managed streams over Input stream adaptive, seems default config have issue. Change to manual 1080 and now no crash.

Unfortunately, I can't really comment on that, since it's an add-on, and the last version released for Leia is already outdated.

I also suspect that this bug isn't specifically Amlogic specific, but has existed on all platforms. IDK.

Edit: I found a fairly similar bug on GitHub: https://github.com/xbmc/inputstream.adaptive/issues/1362

Quote from thadrumr

Question I have a MXQ HD18q box running the latest 9.2.18 patch. I am having issues with it randomly locking up. I have tried a factory reset and it's still locking up. I am wanting to use it as a Airplay 1 receiver for Apple Music to get full lossless audio. I have it connected up with HDMI and Ethernet only. It will boot up and run fine. The CPU will hover around 60-65 degrees C which doesn't seem to hot. I have also tried to stream a movie and it will do that fine. If I leave it alone will will eventually lock up. This was with it sitting idle with only an SSH connection into it. One time I was streaming music to it using airplay and it locked up mid song. Can you think of anything that would cause this or is it time to retire this old thing?

Unfortunately, I don't have any Apple stuff, so I've never personally used the Airplay feature. It's a good question whether this could be the cause of the instability issues, or if there's something else going on. (E.g. an unstable addon, a weak power supply, an overheating issue, a dying SD card, etc.)

A pastekodi output would be nice, maybe it will reveal something...

Quote from xixi22

Hello, im new here , then sorry when exist simmilar Q . Longtime i use kszaq Krypton as perfect working on my Tanix S905X. Now i some time testing more variants of newer, but all have issues . I hope this Leia is better, but my test with latest .18 release isnt success. Box boot works ok , but as other on some playing manipulaions totaly hangs and cant reboot any way (ssh too) when in lockup state. Only power off hard.

Is this known issue , hope have some solution? Pls help.

My plan is upgrade from 17 to 18 with same stability. 17 works still perfect , but PVR sclient is old ...

The situation is similar to that of the previous colleague, because I have no idea what could be causing it, and based on your description, the circumstances of the error's occurrence are unfortunately not entirely clear.

"some playing manipulaions" -> What does this mean in this context?

I would be happy to see a pastekodi output, although if the box really just freezes, I'm not sure the log will reveal anything.

Quote from Yorker

Sorry this might be a dumb question but i recently got a Wetek Core (S812) device and was looking into what i can i do with it apart from Kodi

The question is a bit strange because this box is primarily suitable for media playback, but boxes equipped with this SoC are also popularly used for game emulator purposes. In addition, background services can also be run on it, for example using Docker even under LE.

However, due to difficulties running the mainline kernel on n200C devices, only the legacy 3.10 kernel is functional at the moment.

pets

Pulseaudio package has been updated because too many patches were needed to fix this bug, but the next version (v13.0) includes all of them.

The snapshot image is available here: https://libreelec.dtech.hu/snapshots/20250520_master_803f533/

Please try it and report back if the problem is really solved. Thanks.

Quote from Ionman

Is there a download for the VNC server which will run on my Wetek Core? I don't seem to be able to browse https://libreelec.dtech.hu/packages/

The packages directory and its browsing are hidden on the server for security reasons, but you can find it in the LibreELEC Add-ons repository, among the services, under the name Amlogic VNC Server.

Quote from pets

pulseaudio[2118]: E: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse/module-alsa-card.so: /usr/lib/pulse/libalsa-util.so: undefined symbol: pa_alsa_ucm_device_update_available .
Seems related to e.g. https://bugs.gentoo.org/700870 . (see also #937).

Any chance of getting that corrected?

I will check, thanks for letting me know.

Quote from Lirk

It seems that manual updates doesn't work from LE interface. Also need to test addons autoupdating (20250405_master_b9e7a60/LibreELEC-Generic_S905.arm-9.2.8.18).

I haven't experienced any anomalies when updating addons. For manual system updates, I only list the latest stable version. So, if you already have that installed, you will see an empty list. You can only manually update to snapshot versions via the update folder.

Edit: Something is really wrong with the manual updates listing because the output is empty. I will investigate this after the Easter holidays, so please be patient.

Edit #2: I found the source of the problem, which can be traced back to the fact that I grouped the devices (S805, S8X2, etc.) in the JSON file generated for the USB downloader, and the manual update method also uses this file, but it did not find the specific device.

Fortunately, I managed to solve it on the server side, so in theory it should now work flawlessly on older versions as well.

If you have the opportunity, please check it yourself, if you haven't updated manually with the tar file yet.

Edit #3: Since then, I have also changed the list of images shown by the USB-SD creator.

Quote from Ionman

Any advice on what tools I'd need to build for my Wetek Core using Windows? Specifically, I'd like to tweak visualization.shadertoy to implement a better timer (on the Core, iGlobalTime overflows/wraps every 8.192 seconds). From; https://github.com/xbmc/visualization.shadertoy/tree/Leia

I have never used Windows tools for cross-compile, so I don't know if it is even possible to compile binary code for armv7. Moreover, the NTFS file system does not handle the unix-like file system level permission management, so I would not recommend cross-compile Kodi and its addons under Windows.

Quote from tecc

Now I want to install LE instead to finally settle on the best distribution for me. Unfortunately unzipping the generic box image to the SD card and booting from it did not work.

You don't need to unpack it, just write the image to an SD card, but there are additional steps required to boot. The description in the link sent by chewitt includes everything for the new versions.

Quote from tecc

Thanks, but what older LE version should I use with my box should I still like to have 'HDR to SDR tonemapping'?

This definitely works under the community release I maintain (LE-AML 9.2 LTS).

Quote from Lirk

Why it cannot be fixed by comparison Kodi 17.6 changes in the sources? Maybe it can be fixed by replacing some old files from Kodi 17.6?

It would make more sense to backport the bug fix, but I don't know if the bug is actually in Kodi or FFMPEG.

Quote from Lirk

So. I have an old question about software deinterlacing support.

I tested old kszaq's image version 8.2.3 and software deinterlacing works properly with the same CPU load in debug info for both versions - 8.2.3 and 9.2.8.18, it shows about 170% of CPU-KODI load and 30%-40% for each of cores, but in 9.2.8.18 version it works with frame dropping.

I used this video sample for testing with disabled AMCODEC support. May be there is a way to repair this functionality?

Unfortunately, there was never a real solution for this, because the hardware deinterlacer works incorrectly for some formats. But AFAIK on Kodi Leia the software method causes the same frame drops you are experiencing, and this issue is not exclusive to Amlogic devices.

Workaround #1:
Please try this with MPEG2 hardware decoding enabled:
echo 1 > /sys/module/di/parameters/bypass_all

In fact, this solution also only works in some cases, but it worked for me for PAL (576i50) format DVDs.

If this method has led to positive results, it is worth applying it at startup, for example:
echo "echo 1 > /sys/module/di/parameters/bypass_all" >> /storage/.config/autostart.sh

Workaround #2:
An alternative solution may be if your display is a television that natively supports interlaced input format, because in this case you can also set the output to an interlaced resolution (e.g. 1080i), and then you can turn off deinterlacing with software decoding.

In this case, your television is responsible for performing the deinterlace in real time, so this will definitely provide better results than any software solution. Of course, this is not a working solution for a standard PC monitor.

In both solutions, it is important that the frame rate of the source media and the display refresh rate are in sync, so the Players Settings -> Adjust display refresh rate setting option should never be turned off.

Quote from Lirk

Yes. Generic_S905.

Please update to the latest snapshot image from here:

Index of /snapshots/20250401_master_045f4c8/

After testing, I would like a feedback. Thanks.

Quote from Lirk

DVD playback support was dropped in version 9.2.8.17, but it works in 9.2.8.16.

I can assure you that no DVD playback support has been removed, so if it really isn't working, there must be another reason.

In version 9.2.8.17, the GLIBC component had a major version update, so it's possible that what you're experiencing is related to that. I'll check tomorrow...

Edit: The problem is more complex than I initially thought. Playing DVDs from a local USB ODD also didn't work, but I fixed that this morning. However, if you try to play via an SMB share, the error you reported still occurs.

Please tell me which image you are using (e.g.: Generic_S905), because if I manage to fix it, I will create a snapshot image for it first.

Quote from vissy

Sorry for the mixup. Now up and running from NAND

Unfortunately, USB drives cannot be used for this purpose. But I'm glad it was finally resolved.

Quote from vissy

dtech I have a Wetek Core that has been gathering dust for a few years. I wanted to see if I could get it up and running with this LibreElec image.

Device is on WeOs 3.0.1 so not able to use remote to force sdcard boot. I tried using android 5.1.1. recovery to install sd-card update img. I get an error unable to mount via android recovery.

What could I do to install/boot into LibreElec? Any help is appreciated.

A quick question before we delve into deeper diagnostics:
Did you try to install according to the description in the leading post on this topic?

Quote from dtech

NAND install image for SD card: Download the NAND install image (*-sdcard.zip), extract it, and copy the contents of the file to the root folder of an FAT32-formatted SD card. Disconnect the power cord from the device, insert the prepared SD card, and plug in the power jack while pressing the reset button*. You need to hold the button about 8-10 seconds until the LibreELEC installation begins.
* The reset button on M8S+ is located behind the A/V connector, but on the Mecool and WeTek devices, the reset button is located behind the hole on the bottom of the device.

Quote from Pollostrio

Hello, sorry if this is simple to do but I’m very new to this and I need help.

I have successfully installed LibreELEC-M8S-Plus.arm-9.2.8.17-update on my Pandora with the S812 chip, and when I start it, it stays on the logo and doesn't move beyond that.

There is no SD card inserted, so I assume that’s normal.

What do I need to put on the SD card for it to move beyond that? What files are needed? Any step-by-step guide?

The NAND install images in the scdard ZIP files are made exclusively for that specific device (M8S+ and KII only), so if you install it on a different device, you risk potential bricking. In this case, the only solution is to restore the original ROM image from the device manufacturer.

It's funny when a patch looks like this:

+    // uncomment next block  enable SPDIF output to GPIO HEADERS
+    /*
+    pinctrl-0 = <&spdif_out_h_pins>;
+    */
+    // uncomment next block  enable I2S output to GPIO HEADERS
+    /*
+    pinctrl-0 = <&i2s_out_ch01_pins>, <&i2s_out_lr_clk_pins>, <&i2s_out_ao_clk_pins>;
+    */
+    // uncomment next block  enable SPDIF + I2S output to GPIO HEADERS
+    /*
+    pinctrl-0 = <&spdif_out_h_pins>, <&i2s_out_ch01_pins>, <&i2s_out_lr_clk_pins>, <&i2s_out_ao_clk_pins>;
+    */
+    pinctrl-names = "default";

In other words, these are not compiled into dtb by default, because you have to manually uncomment the option you want.
So this patch needs another patch, or this patch needs to be modified.

Quote from drollo

Hi, I own a T95z plus aswell and I had some issues whith LE12 like bad network connection, not working remote hardware, etc. And I would like ti try this dtb you have uploaded. Can it be applied on an already deployed box with LE12 or must by applied on a new installation from scratch?

Sure, it will work, you can apply the above procedure to an existing system as well. It will help with Ethernet, but it doesn't include the VFD display pins, and unfortunately we haven't been able to figure out the mystery of the remote control yet, even though I measured it before.