The problem is that no low-level USB functions seem to work at the moment.
Have you tried connecting a different type of USB device (e.g. flash drive) to the OTG cable? Because if that doesn't work either, then we have to check the problem elsewhere.
The interesting thing is that lsusb should also show the USB host chip (or the root hub).
If you unplug the OTG-cable and boot without that (empty first port), is the output still null?
my setup
Unfortunately, I don't have such a device, but are you sure this USB Y-cable with OTG-adapter is suitable for this purpose?
Maybe the middle two USB wires (DATA+/DATA-) are not shared in this Y-splitter (or I don't know, what is this), so I think this will not work.
I think the tuner only gets the power and that's it.
You should try adding a dedicated power supply to the 2nd micro USB port (I mean a real power supply, not a phone charger) and connecting the tuner to the first via OTG.
Hello good afternoon,
I would like to know what is the latest oscam compliancy compatible with K1 Pro S905D, with LibreELEC v9.2.8.7.
and the latest version of Tvheadend for LibreELEC v9.2.8.7.
I have oscam and Tvheadend installed but I can not access via web.
Everything in the repository runs without problems. Are you sure you are trying to access your box on the right IP address and port?
Tvheadend 4.2 and 4.3: http://<IP-of-your-box>:9981
OScam: http://<IP-of-your-box>:8888
Unfortunately, there are problems with the recently published image, so I do not recommend using it for now.
I have sent you a message about how to resolve these issues, please read them.
I have installed this build on mx-iii g and everything works fine. But I have tried to install some docker addons and does not work. Is there something that I have to enable to make it work?
Unfortunately, there is nothing you can do to make it work.
IMPORTANT NOTES - Please read them carefully before asking:
...
- Docker only works under 64-bit SoCs (S905/S905X/S905D), it is not available on 32-bit systems (S802/S805/S812)!
I have the default skin (i dont remember the name i think estuary) The option of power menu that is missing i think its "Reboot from eMMC/NAND"
I modified the affected menu file, please try it:
Index of /misc/shutdown-menu-mod/
So it depends on which theme I will use? But which theme to use so I can add
boot option in power menu ?
In principle, the power menu of each skin can be edited. Mine is also edited, for example:
Which skin are you using?
Hello to everyone. Could you please add a dual boot (or reboot to Android) option to power menu ? There are only power off reboot and exit options
Each Kodi skin uses its own powermenu config, so there's not much point in adding it to Estuary by default, not to mention that this menu item will appear in English on non-English languages as well, which is quite confusing for some users. I don't think you're using the Estuary skin either, because there's no Exit menu item under LE. 
It would be nice to see a dmesg under LE as well. By the way, does lsusb show your tuner?
Do you really own so many devices? :O
*Although my Play 2 is half-dead and my KI Plus is unfortunately completely dead at the moment. 
I assume that the first one is the correct dtb.
If the wifi doesn't work, you need the second one. It differs only in that.
I want to try it on an mxq pro 4k with 1g of ram, which means I have never used that image before.
Thus, is the right image the one with "k_series" in its name (from the releases page in github)?
I only upload images to GitHub that made for those devices which I have. I define all of them precisely in the first post linked above.
The other images are in the 3rdParty category, which are only available from my own server. The links are also in the first post.
In short, you need exactly the Generic_S905 image. Regarding dtb, I'm just guessing:
gxbb_p200_1G_100M.dtb or gxbb_p200_1G_100M_RealtekWiFi.dtb.
May I ask what is the new image for s905?
It is essentially the same as the previous MXQ-4K-Pro_2G image, but it contains all the GXBB/GXL dtbs in the device_trees directory. So, you no longer need to download the right dtb separately, just overwrite the dtb.img with the right one.
Also, that automatic update notice at the end. Does it mean that the user can now use libreelec's built in function to update it, i.e. from 9.2.8.6 to 9.2.8.7?
I need to quote myself from the #1 post:
NOTICE: If the auto update is enabled, but the installed version is not the latest, then the listed devices will automatically download and install it after restarting.
Sometimes it's worth looking back at the first post, because I usually write the bigger changes there.
As I see it, the problem here will be different. First, loading dhd is unnecessary if your device has Realtek wifi. The error also applies to this, the 8188eu module seems to be loaded, but cfg80211 is required for the wifi to work, but it crashes due to the incorrect dhd-config. The dhd is only required for Broadcom-based chips.
Question #1: Did you use my Wetek Play project directory as a base? Because then you have to delete this file:
LibreELEC-AML/projects/<YOURPROJECTNAME>/filesystem/usr/lib/modules-load.d/wireless.conf
This will force load dhd even if it is not needed. And that might be the problem for you.
Question #2: Which dtd file did you use in your project?
# Kernel extra targets to build
KERNEL_UBOOT_EXTRA_TARGET="<filename>.dtd"LibreELEC v9.2.8.7 (2023-01-22) has been released for S805, S8X2, S905x and WP1 devices.
Some changes are announced because support for some devices has changed:
Changes since v9.2.8.6 (2022-09-04):
For download links, please check the first post in this topic: #1
Mirror (GitHub): Release LibreELEC v9.2.8.7 for AML S805/S8X2/S905 and WP1 (2023-01-22) · dtechsrv/LibreELEC-AML
NOTICE: Automatic update will only be enabled for this version in a few days.
NOTICE UPDATE (2023-01-23): Automatic update has been enabled on all supported devices (except 3rdParty).
I've got Libreelec-AML 9.2.8.7 to build and boot on the MX box, but I'm having an issue with the Realtek 8188ETV wireless.
Libreelec doesn't allow me to enable the 'wireless active' option. I've SSH'd and lsusb, the device is present so I assume the drivers are working.
Various places have mentioned Realtek wireless support is a bit of an issue of contention for the libreelec team, so I'm expecting some pain getting this working.
Unfortunately, this is my first outing in compiling the linux kernel so I'm really a n00b when it comes to this. Is there any recommendations in tackling this issue?
I can post dmesg dump if that would be any help.
The Realtek 8188* is a general USB chip, I also have an external one (TP-Link TL-WN722 v2).
I use an external module for this in my builds, instead of the integrated module of the kernel.
First, you need to check if it is enabled in your kernel configuration, because if it is, it should be disabled:
# CONFIG_RTL8188EU is not setNext, add RTL8188EU-aml to the ADDITIONAL_DRIVERS variable in the options file in your project directory.
If that doesn't help either, then please send me a log file: journalctl | paste
Hey all, does anyone know if/where one can purchase/source one of these boxes? I have an MXQ pro+ running the latest build, and would like to add another one or two to my arsenal. The challenge is finding one.
It is quite difficult to buy a used box these days, because on the one hand it is rare, and on the other hand, if you find one, the seller sometimes gives it at a price that is usually not worth it.
Interestingly enough, I managed to get Libreelec working on my amlogic s805 based box, only With MXQ image (which more closely resembles the specs of the Freesat Angel V8 box I got) I only managed to get to the Kodi splash screen (where it got stuck), and with the lower speced M201D firmware - it booted without a hitch - although Bluetooth does not work, the network speed is a tad slow, and some things just get the box frozen. It still works MUCH better than with the Android 4.4.2 that comes with the box (and cannot be updated). So thanks.
The limiting factor and the reason for the freezes, may be the lack of memory. 512 MB is not too much.
Bluetooth and Wi-Fi are also quite a gamble. The quality of the drivers integrated into the 3.14 kernel and chips themselves are not very good.
i get an ID error 1
It is not an ID error, it is an HID error. One character is missing from the beginning of each line due to display overscan settings.
Read more about this issue:
