when I try to config remote, it report following error:
LibreELEC:~ # ir-keytable
/sys/class/rc/: No such file or directory
No devices foundhow to fix it ?
In my images meson-ir is not supported, only amremote, so all you need is the appropriate remote.conf file.
If you could identify what box you have, I could help you find the correct remote control config.
Well no voltage error in your case but are you using LibreELEC-WeTek_Play_2.arm-9.2.8.18.img.gz or LibreELEC-Generic_S905.arm-9.2.8.18.img.gz with gxbb_p200_2G_wetek_play_2.dtb is it same thing ?
Since it is not DVB-S, there is no LNB to be powered (13-18V DC), so there is obviously no such problem with this tuner. Regardless, there is a 5V DC output for possible antenna signal amplifiers, but for terrestrial signal reception (DVB-T/T2) a passive antenna is basically sufficient, and for cable TV (DVB-C) this is not even necessary.
For WP2, I strongly recommend using the WP2 image, because it is optimized for it (different boot method, remote control codes, kernel drivers, etc.), and between the base modules, only this one contains the wetekdvb driver.
The abdroid box os uses kernel 3.14.29 so drivers should be compatible but I have no idea how to proceed.
I extracted your stock ROM image with AMLogicTools and unfortunately the driver is not included as a module, so it is impossible to extract and use it from its original environment.
If you have access to the wetek play 2 it has a built in DVB-S2 tuner you don't need LNB to be connected to the tuner ...
No, WeTek Play 2 has a removable tuner, mine has DVB-T2/C and I don't have a DVB-S/S2 modular tuner for it at all.
WP2:~ # dvb-fe-tool -a 0 --verbose
Found dvb demux device: dvb0.demux0
path: /dev/dvb/adapter0/demux0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.demux0
bus addr: platform:dvb.50
Found dvb demux device: dvb0.demux1
path: /dev/dvb/adapter0/demux1
sysfs path: /sys/devices/dvb.50/dvb/dvb0.demux1
bus addr: platform:dvb.50
Found dvb demux device: dvb0.demux2
path: /dev/dvb/adapter0/demux2
sysfs path: /sys/devices/dvb.50/dvb/dvb0.demux2
bus addr: platform:dvb.50
Found dvb dvr device: dvb0.dvr0
path: /dev/dvb/adapter0/dvr0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.dvr0
bus addr: platform:dvb.50
Found dvb dvr device: dvb0.dvr1
path: /dev/dvb/adapter0/dvr1
sysfs path: /sys/devices/dvb.50/dvb/dvb0.dvr1
bus addr: platform:dvb.50
Found dvb dvr device: dvb0.dvr2
path: /dev/dvb/adapter0/dvr2
sysfs path: /sys/devices/dvb.50/dvb/dvb0.dvr2
bus addr: platform:dvb.50
Found dvb frontend device: dvb0.frontend0
path: /dev/dvb/adapter0/frontend0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.frontend0
bus addr: platform:dvb.50
Found dvb net device: dvb0.net0
path: /dev/dvb/adapter0/net0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.net0
bus addr: platform:dvb.50
Found dvb net device: dvb0.net1
path: /dev/dvb/adapter0/net1
sysfs path: /sys/devices/dvb.50/dvb/dvb0.net1
bus addr: platform:dvb.50
Found dvb net device: dvb0.net2
path: /dev/dvb/adapter0/net2
sysfs path: /sys/devices/dvb.50/dvb/dvb0.net2
bus addr: platform:dvb.50
Selected dvb frontend device: dvb0.frontend0
path: /dev/dvb/adapter0/frontend0
sysfs path: /sys/devices/dvb.50/dvb/dvb0.frontend0
bus addr: platform:dvb.50
Device Sony CXD2837ER DVB-T/T2/C demodulator (/dev/dvb/adapter0/frontend0) capabilities:
CAN_2G_MODULATION
CAN_FEC_1_2
CAN_FEC_2_3
CAN_FEC_3_4
CAN_FEC_5_6
CAN_FEC_7_8
CAN_FEC_AUTO
CAN_GUARD_INTERVAL_AUTO
CAN_HIERARCHY_AUTO
CAN_INVERSION_AUTO
CAN_MUTE_TS
CAN_QAM_16
CAN_QAM_32
CAN_QAM_64
CAN_QAM_128
CAN_QAM_256
CAN_QAM_AUTO
CAN_QPSK
CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.11, Current v5 delivery system: DVBT
Supported delivery systems:
[DVBT]
DVBT2
DVBC/ANNEX_A1. If it was built with kernel 3.14, it might work. But generally, its stability is questionable due to the different build environment.
2. What do you mean on "generic build"? The Availink drivers are tightly built into the Amlogic BSP kernels, so it's unlikely that they could be easily ported to the mainline kernel.
I was hoping that the driver would be able to start the demod chip like the WP2, but it seems that the WP2 dtb doesn't have a dvbfe entry because all the necessary parameters are fixed in the driver. (This is just a suspicion, not confirmed.)
However, if the above is true, then the driver is not truly universal, but only works with the WeTek factory wiring solution, and not with a different configuration. This is too deep water for me, unfortunately I am not that knowledgeable, I am mostly just experimenting. Unfortunately, I do not have any DVB-S capable accessories, neither LNB nor dish.
I think I will give up at this point, I'm just guessing blindly due to the lack of devices. 
Really sorry about the confusion — here is the exact S905D DTB pulled directly from the OS :
I compared it and the modified parts are the same, only the order of the lines was different. I'm afraid that the dvbfe section contains a misleading configuration, so I modified the dtb again based on a different approach. If this doesn't get us any closer to the solution, then I have no more ideas for now.
I modified it a bit based on the original Android device tree, please try the attached file.
The dvb-latest and crazycat_aml only load the AVL6211 demodulator driver if ...
I don't see any of them active:
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: setup base modules
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/base/lib/modules/3.14.29
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: added firmware from /usr/lib/kernel-overlays/base/lib/firmware
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: adding overlays from /storage/.cache/kernel-overlays
Apr 11 16:28:37 LibreELEC kernel-overlays-setup: done
Apr 11 16:28:37 LibreELEC systemd[1]: kernel-overlays.service: Succeeded.Please enable one of them, because only avl6862 is present among the base modules in the Generic_S905 image.
CyberPhoenix There is no need to try different images, the affected driver is present, just inactive. The dvb-latest and crazycat_aml only load the AVL6211 demodulator driver if dev_name = "wetek-dvb"; is present in the dvb section.
I have modified the gxl_p231_2g_dvb.dtb file (attached), try with the Generic_S905 image, and please send me a pastekodi as well.
Installed LibreELEC-Generic_S905.arm-9.2.8.18.img.gz from https://libreelec.dtech.hu/images/S905/ dunno if this is the correct version to go for since I think S905D can handle newer version like in CE 21.3 kernel 4.9.
I have been working with kernel 3.14 only, so this is the latest version. But, my dvb-latest package is newer than the one in CE 9.2, so I trusted it more, but you could also try the CrazyCat driver.
However, I think that dtb should also be modified, because the I2C bus lines are also wired differently. Unfortunately, I probably won't be able to help you get the tuner working, because it's outside my area of expertise, especially DVB-S/S2.
Well, bad news, box is fried... or at least in the process of frying
I'm sorry this happened, I would have been happy if it had been found out what was causing the sound output problem.
So tired legacy 9.2.8.18 generic with kernel 3.14.29, so far my experience has been the same with CoreELEC, any suggestions would be greatly appreciated. Thanks in advance for your help!
Unfortunately, I'm not really experienced with tuner/demod drivers. However, please proceed in a similar way as with CE, so install the dvb-latest package and send me a pastekodi output. Thanks.
You have a lot of ruined devices, I admire that
Unfortunately, I have no luck with the WeTek boxes, but I can assure you that they did not break down by me, unfortunately I received them in bad condition. The WP2 above was probably dropped earlier, but apart from the sound, its other functions work. The KI Plus got a power surge, and I received it defective as well. I tried to repair it, replacing a bunch of SMD components on it, but unfortunately it broke down again a year after the repair.
It seems I have the same DAC, maybe dtb is the issue?
There is an SGM8905 operational amplifier after the DAC and this is probably the cause of the problem, because it is probably controlled and either does not receive power or is in mute mode.
I found a reference that is only present in the dts of the p201, and may refer to this:
audio_suspend_pins:audio_suspend_pin{
amlogic,clrmask=<AO 0x78000000>;
amlogic,pins = "GPIOAO_8","GPIOAO_9","GPIOAO_10","GPIOAO_11";
amlogic,pullupen = <1>;
amlogic,pullup = <0>;
};Oddly the default when HDMI is connected is "P201 analog" but I still get sound thru HDMI.
"P201 analog"? I think you checked it under the current version based on the mainline kernel, because under LE 9.2 its name is AML-M8AUDIO Analog.
I'm trying to watch via analog composite on SDTV, but I get no audio (video is perfect, subtitles work).
Unfortunately, the GXBB SoC (S905) does not have an internal stereo audio DAC, so it needs an external I2S DAC chip for analog audio output. I admit that I did not test it much because my WeTek Hub and Odroid C2 do not have analog audio output, my WP2 has a faulty audio part, and my KI Plus is also broken.
The last chance is my Videostrong KII Pro, which is equipped with an S905. I will try to check this weekend to see if it has analog sound output.
If you have disassembled your box before, do you have a good quality photo of the PCB in the box? It would be good to know what DAC chip is in it. (But, if the box has not been opened yet, do not disassemble it just for that reason.)
Edit: I tested the analog audio output on my KII Pro and it works perfectly. The DAC chip in this box is ES7134LV.
(I think I have never had so many things connected to this box at once.)
However, the fact that I haven't experienced the issue you describe makes it a bit more difficult... 
Question #1:
Is it just the videos that have no sound, or are the system sounds missing as well?
Question #2:
Are you sure everything is set to default?
I mean, the selected output is analog, audio passthrough is disabled and the number of channels is limited to 2?
Is installtointernal still heavily discouraged on random boards?
New LE even dropped the command.
This script was never present in the official LE images based on kernel 3.14, so according to the official statement it is not recommended. I do not see this situation as critical, but regardless, it cannot be guaranteed that there will be no problems.
It is a known issue that some boxes may have problems overwriting the dtb partition when booting from external storage, so the operation may need to be repeated one more time to successfully boot from internal eMMC/NAND Flash.
Hey, is it possible to install your LE to eMMC on s905?
Sure, you can easily do this with the installtointernal script.
If yes, would making a backup of eMMC with Armbian's ddbr or Khadas Rescue preserve the firmware and bootloader/config?
Unfortunately, I haven't used these yet, so I can't comment.
The uboot bootloader parameters can be checked with fw_printenv under my images. However, the installtointernal script does not modify the uboot bootloader or its parameters, it only modifies these partitions:
dvamg Thank you for the logs, although I don't see any significant difference, it's a good thing in this case.
NOTE: for some reason, LibreELEC-Generic_S905.arm-9.2.8.18.img + gxbb_p200_1G_100M_RealtekWiFi.dtb now has operational wifi and eth - I have no explanation for this as it did not work before.
Either it was a hardware bug, or the fact that I rebooted to NAND and back before doing these batch of tests, or because I didn't have to trigger the boot recovery button push at all since it was already set up, possibly combo of all three and cheap hardware being goofy, or maybe something (drivers/hardware state) persisted between Android and all of these tests.
There could actually be several things causing it, but luckily it seems to have been resolved.
I am using LE 9.X dtbs for LE of course! Those two dtbs are from LE and they work on my device (+wifi +eth).
There can be a difference in the dtb between two successive subversions. "LE 9.x" is not much information in itself, because there have been many community builds of 9.0, but I don't know of anyone else who has made 9.2 for AML. Moveover, I use the kernel modified by kszaq instead of the official legacy LE's amlogic kernel.
That's why I asked you that if you use v9.2.8.18, please use the dtb included with it. I wanted you to see this clearly, it's no coincidence that the dtb was also updated during the update process.
I was only reporting to you that the box indeed has eth and wifi hardware that works when tested with another OS, because you talked about the device not reporting wifi hardware being present.
I didn't say that I don't see a wifi adapter at all, I just said that I don't see a Realtek SDIO wifi chip because the mt7601u is a chip manufactured by MediaTek, and it also connects via USB instead of SDIO, so the RealtekWifi dtb makes no sense.
However, since I now have two dtbs to pick, do you want me to provide some logs of both to see if one works better than the other, or some other kind of test?
Meanwhile, I compared the p201 and gxbb_p200_1G_100M device tree sources, and their Ethernet parameters are exactly the same, so there can be no significant difference between them. Therefore, I don't understand why your Ethernet didn't work with the gxbb_p200_1G_100M_RealtekWiFi.dtb, unless it's because it comes from a different build (e.g. a different LE build or CE).
I mentioned gxbb_p200_1G_100M_RealtekWiFi as this was working with old CE 9.X (both wifi and eth) so the hardware is in this device and it's operational.
I've went thru every generic LE 9.X dtb and found that these two work, both wifi and eth:
gxbb_p200_1G_100M.dtb
gxbb_p201.dtb
If you use external dtbs, I cannot provide any support for their operation.
Please use only the dtbs packaged with the image, which are located in the device_trees directory.
In fact, only use those included with the current version, because there may be differences even between previous versions.
I would have been happy if you had at least told me what device you have, because I'm not sure that you are using the right DTB for your device.
Unfortunately I didn't get an answer to this, although a device model name would be helpful. Unfortunately, I'm still not convinced that you are using the good DTB, especially because I don't see any Realtek SDIO wifi chip in the kernel log.
Regarding Ethernet, in the logs you sent, this doesn't look good:
[ 7.417077@3] stmmac_hw_setup: DMA engine initialization failed
[ 7.417091@3] stmmac_open: Hw setup failedI think you should try a 1Gbit DTB first and ignore RealtekWifi, because it doesn't seem to be present.