Please remove the seller link, you agreed to the forum rules!
Use Libreelec 8 from here: thread-2156.html
Write the img.gz file to a micro sd card with rufus (Rufus - Create bootable USB drives the easy way) or a similar image writer software.
Replace dtb.img on the sd card with this file: gxl_p212_2g.dtb (rename to dtb.img)
Place card in box, power on while pushing the reset switch and release switch when Libreelec logo appears.
Please provide a sample file that exhibits this problem.
I checked with a terminal apk in Android: my version of the box loads the 9082xs module. I use only wired ethernet, so I do not mind. Also, plugging in an usb wlan adapter worked fine in libreelec, so I can use one of these if I really need wlan.
HaselnuesseTo: If you want to check yourself, install Terminal Emulator 1.0.70 by Jack Palevich and type "su" (accept root privilege) and "lsmod" when connected to wlan in Android. It is possible that multiple versions of this golden box exist.
kszaq: Thank you for clarifying the driver issue, and as always thanks for your continued support of these builds.
That is the Akaso M8S with S912. I made a mistake, the label of my box is "HM8", with S905X.
Hello,
I received a really cheap S905X box "Akaso MH8 HM8". Libreelec 8 boots fine with standard reset switch procedure, if gxl_p212_1g.dtb is used. Sadly, wlan does not work.
sdio devices:
LibreELEC (community) Version: 8.0.0c
LibreELEC git: e5a2b4eb5166ae2eae3e071bab75d3b7f06bdce1
akaso:~ # udevadm info /sys/bus/sdio/devices/sdio*
P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: MODALIAS=sdio:c07v02E7d9082
E: SDIO_CLASS=07
E: SDIO_ID=02E7:9082
E: SUBSYSTEM=sdioAndroid kernel modules:
akaso:~ # mkdir -p /tmp/system
akaso:~ # mount /dev/system /tmp/system
akaso:~ # find /tmp/system -name *.ko
/tmp/system/lib/8189es.ko
/tmp/system/lib/9082xs.ko
/tmp/system/lib/audio_data.ko
/tmp/system/lib/dhd.ko
/tmp/system/lib/dwc3.ko
/tmp/system/lib/dwc_otg.ko
/tmp/system/lib/mali.koI have not found any information on this "9082xs" but I saw that you contacted someone on github who seems to have access to some kind of driver source.
My wired x360 clone controller worked out of the box. The mii blutooth controller I ordered weeks ago is stuck in postal limbo between China and here; but I will test as soon as it arrives.
Yes, see thread-1129.html
Put
echo 1 > /sys/class/amhdmitx/amhdmitx0/output_rgbin autostart.sh in config folder.
DTS-HD MA works with my setup with S905 (see signature). The S905X box will arrive on Friday, but I am sure it will work, too.
What avr are you using? What are your test files?
Please note that there might be some incompatibilities between some avrs and the way kodi signals dts-hd formats. With my receiver, DTS-HD HRA 7.1 is not correctly recognized by my avr. This is a kodi/avr problem and happens with an x86/Windows 10 box as well. See DTS-High Resolution. What's the score?
dhd is a module used by broadcom wifi drivers.
Is the 8192eu not your usb wlan stick? You should blacklist the module used for the internal wlan.
You can check the loaded modules with "lsmod" using ssh. But you'll need to comment your lines in autostart.sh and blacklist.conf and reboot, so we can see both modules and interfaces.
What is your device and what device tree did you put on the SD card (the dtb.img file)? This error is an indication that the wrong device tree is used.
Maybe the devices get enumerated differently in the new version. Could you check with ssh what the output of "ifconfig" is?
Same for me, need to run the above command after every power up or reboot though.
I added the command to my autostart.sh.
On my wetek hub, the ir remote stopped working after I upgraded beta6 to 8.0.0a. Manually doing a
remotecfg /flash/remote.conffixed it.
The problem is that "MXQ pro 4k" is not a specific box, but more of a generic label that is used by multiple manufacturers and sellers. The box I own (see my signature) works fine with the generic gxbb_p200_1G_100M device tree, but yours is most likely newer and uses a completely different board and wlan chipset. Did you try one of the "realtek" device trees?
You can open the box and take a picture of the PCB. Then we might be able to help you further.
Not being able to switch a powered off box with the remote is an issue many boxes have. Current understanding is that in order for this to work, the manufacturer needs to make sure that the u-boot bootloader correctly recognizes the remote signal. This takes extra work, so with the cheap boxes, it often is neglected. My MXQ Pro 4k simply switches the hdmi output in its android firmware when I push the button.
Depending on the type of subtitle, it has to be rendered as a graphic to be displayed. As I wrote before, especially with subtitles in ASS format (which allows for a lot of effects, colors and other fluff) this will lead to CPU usage spikes that interfere with the video rendering. It is very easy to notice with software decoded videos, but can also be seen with hardware decoding. You can try downloading subtitles in other formats for your files and check if it gets better.
In my opinion, the root cause for this is that kodi apparently uses just-in-time rendering for the subtitles. This is no problem on PCs with lots of CPU power, but the arm SoCs do not have much power to spare. Pre-rendering subtitles in advance could help with the spikes, but would delay the start of video playback and is most likely a significant change in the kodi player code.
That SATA is most likely some usb2sata bridge, as the SoC has no native interface, as far as I know. Could you boot Libreelec, connect with ssh and type "lsusb" with a sata disc connected?
Edit: Found it, apparently it's a JMicron JM20329 USB 2.0 to SATA bridge. See Tronsmart Vega S95 Telos TV Box Unboxing and Teardown
I think you got your RAM (dynamic memory) and ROM (flash memory) mixed up. But anyway, a printout of "mount" and "df" from android root would show what partitions are mounted in android and how much space they have.