Posts by dtech

Quote from chewitt

dtech I think the idea was to get the box booting any non-Android OS first, and work forwards from there.

There's nothing wrong with that, but at the moment I see that my legacy images are currently being tested, and the upstream autoscript is not really compatible with them, that's why I indicated that.

By the way, my legacy autoscript does not have statically defined memory addresses that are present in the upstream version. Since there are some differences between S805 (m8b) and S8X2 (m8 and m8m2) in this area, it is not surprising why the 's805_' prefix is included in the name of s805_autoscript.

I see there is a bit of confusion here, so I think it would be worth fixing some things.

This topic is for the upstream AMLMX images, which works with the mainline kernel (6.x).
But these are not compatible with legacy versions and requires completely different bootscripts.

Thefinaldoom

If you are trying to use the upstream version, you would be talking in the right place, but in the case of the legacy images I made, you are not doing this in the right topic. So if you were to try my legacy community builds, with kernel v3.10, then I would rather recommend this aml_autoscript.src boot script, and this topic for support-related communication:

Thread

Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

Latest version: LibreELEC 9.2.8.18 (Release date: 2025-05-20)

IMPORTANT NOTICE!

Due to the switch to GLIBC v2.34, all binary addons have been rebuilt. The main version of the add-ons has been changed from v9.2.0 to v9.2.1, so after the system update, the binary add-ons will also be updated. In addition, the default transfer protocol in the repository has also changed from HTTP to HTTPS.

NOTICE: If the auto update is enabled, but the installed version is not the latest, then the supported devices…

dtech

February 7, 2021 at 2:33 PM

This forum is quite big, so if possible, we try to communicate related things in their own place and not pollute other topics.

Thanks and cheers.

Quote from O'Brother

... the supplied IR remote 'OK' key is flakey (it's like its not polled 100% of the time - needs multiple clicks, there's no issue with it normally).

The remote control configuration of my build only differs from the last official one in terms of the functions of a couple of buttons, but the timings are the same. I still think that there will be something wrong with the OK button or with the batteries. I still think that there is something wrong with the 'OK' button or the batteries are partially dead. (But the first one is more suspicious.)

Quote from O'Brother

Bluetooth is on, shows my bluetooth remote, but it can't connect
...
I use a a custom .hwdb for my bluetooth remote, installed the Aeon MQ skin, but otherwise no other changes.

Unfortunately, in the case of the Bluetooth connection, I cannot provide more specific help, because it is not really my area of expertise. However, since I managed to pair and connect 3 devices at the same time based on the screenshot above (a keyboard, a mouse and an audio device), I think the issue is not on the side of the box.

Quote from O'Brother

Hi, I tried your latest build (9.2.8.12) on my Wetek Hub and there seems to be issues with the supplied IR remote - sometimes the select button doesn't work or seems to be double pressed etc.

So far, no one has sent a report about the remote control error, and I haven't experienced a similar problem either. Unfortunately, the Hub has a pretty crappy remote control. Could it be that there is a physical problem with that button on your remote?

Quote from O'Brother

I also couldn't pair an alternative bluetooth remote as I couldn't get it detected under the bluetooth. Neither of these are issues on the original 9.2.8. I didn't test anything else given the difficulty in control.

Even with a Bluetooth connection, your description does not really cover what the problem is. I just tried it and connected several bluetooth devices to my Hub and they all paired and worked without any issue:

I know, it's a pretty basic question, but I have to ask: is 'Enable Bluetooth' turned in LE Setting addon under 'Services'?
Also, is visibility/search function enabled on the pairing device you want to connect? (e.g. pressing a 'Connect' button)

Quote from pets

I got the box with WebOS 1.7 ...

It's not an LG television, so I think you meant to write WeOS.

Try this:

Index of /misc/wetek-unbrick-resources/

Quote from pets

After fresh install to NAND I just can get black screen - so far made it work including IR-remote (black Terratec NEC remote) as update to v8 after no success via disp_cap/guisettings.xml. Any other proposal?

If it worked from an SD card before, that's a little weird to me.
Did you use the zip package for the installation, or did you upgrade from an earlier version?
(Sorry, I just missed the point again: "After fresh install ...")

Quote from pets

Loading alsa-device via module-udev-detect (want to try to utilize networked audio from Linux Laptops) leads to:
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
maybe related to https://bugs.gentoo.org/700870 .

I have to look into this, but I ask for your patience because I may not be available for a few days.

Quote from Shonk

is there an s905 build for my MXQ-PRO 4k

The build is in progress, when it's ready I'll copy it to the same directory I linked earlier. (~1.5h)

Quote from Shonk

is there an easy way for me to upgrade the copy on internal nand apart from installtointernal then restore a backup?

If you already have my build installed on the eMMC, then boot from there, and copy the .tar file via Samba to the Update directory. Then you don't have to worry about saving/restoring, you just have to restart the box and the update will run automatically after starting.

Or, if it's easier for you via SSH, do this:

cd ~/.update/
wget https://libreelec.dtech.hu/snapshots/20231231-master-5167113/LibreELEC-Generic_S912.arm-9.2.8.13.tar
reboot

The end result will be the same.

Here it is:

Index of /snapshots/20231231-master-5167113/

Please send me a feedback after you try it. Thanks.

Quote from Shonk

When you start up kodi you get a popup in the top right

Okay, now it's clear to me what you were talking about earlier, this is originally a patch from OSMC.

So far, no one has asked it, and I haven't dealt with it in particular, because I wasn't bothered by that popup message, but I added the patch at your request.

The build is in progress, I will post the download link when it is done.

Shonk

The answer came sooner than I thought:

In newer Kodi versions, they have been replaced with the following, which no longer has a backport for Leia:
metadata.tvdb.com -> metadata.tvdb.com.python
metadata.themoviedb.org -> metadata.themoviedb.org.python
metadata.tvshows.themoviedb.org -> metadata.tvshows.themoviedb.org.python

Sorry for the late answer...

Quote from Shonk

When scanning TV Shows it scans the folder's and adds the images for the folders but never scans the files in the folders

when you go into the addons there is a typo on the TV Shows addon which is suspect is what's causing the problem

i think maybe people who have updated to this build instead of going straight to this build may not get this problem

See image atached

I have installed metadata.tvdb.com-3.3.0 and that is working fine (What i used on Kazaq 8.2.2.3)

This is not a LibreELEC specific issue, but there might be some confusion in the Kodi repo, I will try to find it and report it on GitHub to the Kodi devs.

Until then, you can access the latest version for Leia here: https://mirrors.kodi.tv/addons/leia/metadata.tvdb.com/

Quote from Shonk

I dont know if you do requests but if you do can i request that the cec popup's are suppressed unless its an error

Whilst looking how i can disable it on every boot i ran into coreelec added a patch to suppress them unless there's an error so you could most prob see what they did

I would need a little more detailed information than that, because I don't know exactly what you mean by that.

Quote from standal

I have some dvb-t2 android box, see post (unknown s905d dvb-t box), and tried your ROM, but did not work. It wrote DDR init failed...

Any kind of ROMs should not be installed on a box that is not properly identified. Moreover, this is particularly true for boxes with tuners. If you have several pieces of this box, it would be best to make a flashdump from one of the working pieces.

In PRi4, there is no hardware decoding option for AV1 codec, so I am not surprised that these videos are stuttering.

iam5

Thank you for your description. However, a small improvement was made in the last version. In the second half of November, I published v9.2.8.12, which includes a new Generic_S805 image.

Although this may cause problems for some older bootloaders, that's why I also published the classic HD18Q and m201d images.

If you are trying the Generic_S805 image and the bootloader of your box supports multi-dtb loading, you do not need to choose which box is yours, the bootloader will do it instead of you. In addition, the configuration of both remote controls can be found in this image.

So, for a new installation, I recommend that trying the Generic_S805 image as the first attempt.

Quote from Zameero

I have another question: I have a S912 box (Generic H96Pro 2GB/16GB) that has a problem with the shutdown process: Basically it doesn't work as the machine simply restarts instead of powering off. In Android there's no such problem.

As I have seen in the first round, this is a common problem with this box:

Thread

Remote power trouble

Hi, I am still trying to get my head round why the remote power on / off behaves differently in terms of Android v. LE on my H96 Pro Plus 3/32 4K, no matter what remote.conf file I use. On Android, when on the blue led is on and when off a red led is on. On LE, when on the blue led light is significantly weaker and when off there is no led light at all. Also I am unable to power the box on by the remote. Is there any hope for a fix / workaround to avoid having unplug and plug the power cable…

tyrol_gangster

January 24, 2018 at 8:54 PM

Of course, I didn't look into it enough, I didn't really have much time for anything yet...

Quote from Zameero

Is there really no hope for the newer dav1d on this legacy build?

I'm not saying it's impossible, it's just extremely time-consuming, and unfortunately I don't have enough of it right now.
In addition, there is also the pitfall that it turns out in the process that it is not feasible. (Just like the HDR with VP9 under 3.14 kernel.)

Quote from Grzesb

I want run LE without any HDMI.

But when cat /sys/class/amhdmitx/amhdmitx0/disp_cap > /storage/.kodi/userdata/disp_cap

If the HDMI is not plugged in, the source is also empty, so you will create an empty file without any contained resolution.

Instead of this method, try to add a resolution statically, like this:

echo 1080p60hz > /storage/.kodi/userdata/disp_cap

It is also more than enough for simple VNC remote connection.