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

    After installing dvb-latest rebooted then :

    Same error in CE : ERROR    FE_SET_VOLTAGE: Operation not permitted

    pastekodi 

    Tried the custom gxl_p231_2g_dvb_custom but :

    pastekodi

    After that, I decided to boot into the original OS and extract the DTB just to be sure. It turns out that it's not the same DTB that was included with the update ZIP file.
    Really sorry about the confusion — here is the exact S905D DTB pulled directly from the OS :

    Quote from CyberPhoenix

    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.

    Sadly it's not working. What I think is that we can't just edit mapping addresses on dtb since LE uses it's own mapping maybe 0x73 on OS doesn't map the same on LE :

    Code
    LibreELEC (dtech): 9.2.8.18 (Generic_S905.arm)
LibreELEC:~ # ls /dev/dvb/
ls: /dev/dvb/: No such file or directory
LibreELEC:~ # dmesg | grep -i dvb
[    7.640221@0] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.dvb-latest.conf
[    7.691911@0] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.dvb-latest/lib/modules/3.14.29
LibreELEC:~ # dvb-fe-tool -a 0 --verbose
WARNING  device dvb0.frontend0 not found

    pastekodi

    The voltage controller seems not working properly! I suspect AV2011 when tuner is detected previously using the default gxl_p231_2g_dvb.dtb when doing :

    If you can run the same command on a DVB-S2 working device, it should help clarify things.

    That's the latest update file from vendor, the unlocked bootloader image and the box hw layout maybe this will help get some useful stuff.

    For the second box S905H here is the updated dts file, turns out dtb files from the update images are not the same as the one directly loaded into the OS.

    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. :(

    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, you can try the command :

    dvb-fe-tool -a 0 --verbose

    If at the end it doesn't output : ERROR    FE_SET_VOLTAGE: Operation not permitted then there are two possible scenarios :

    1. Driver compatibility, if so is there a way to extract drivers from the box image and put them into LE?
    2. Kernel has been tweeked for this exact device this is more plausible since images made for these devices are different from generic builds; but generic builds also include dvb support with the correct dtb like gxl_p231_2g_dvb.dtb so it makes less sense.

    At this point, the behavior suggests that either the WeTek-specific kernel patches are required for proper tuner initialization, or LE’s generic DVB support isn't fully compatible with the built-in tuner despite the correct DTB being present. Further testing or comparing kernel configs/modules between the stock image and LE may help pinpoint the exact cause.

    Quote from CyberPhoenix

    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.

    1. 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.

    Quote from CyberPhoenix

    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.

    Quote from CyberPhoenix

    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.

    hello,

    I download 9.2.8.19, it boot success

    but when I try to config remote, it report following error:

    LibreELEC:~ # ir-keytable
    /sys/class/rc/: No such file or directory
    No devices found

    how to fix it ?

    thank you

    Quote from flydt

    when I try to config remote, it report following error:

    LibreELEC:~ # ir-keytable
    /sys/class/rc/: No such file or directory
    No devices found

    how 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.

    Quote from dtech

    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.

    thank you, I will investigate how to use amremote

    ref doc:

    Thread

    Create remote.conf from scratch

    I have a new TX3-Pro (S905X- Android 6) box. I run it with kszaq 7.0.2.009 version (thanks to kszaq, great job!). The only problem I had was that the remote control didn’t work at all. Also copying remote.conf from the Android /etc folder to libreelec /storage/.config didn’t help. I thought a while, that may be the device tree (dtb) was wrong for my box but this wasn’t. It was the remote.conf. It seems to me, that Android 6 uses a remote configuration different from the /system/etc/remote.conf.…
    ippon
    January 6, 2017 at 8:08 PM

    copy https://github.com/CoreELEC/remot…ent/remote.conf to /storage/.config

    comment content of:

    between key_begin and key_end

    between repeat_key_begin and repeat_key_end

    run remotecfg .config/remote.conf

    press OK button in remote

    LibreELEC:~ # dmesg
    [ 538.296106@0] remote: Wrong custom code is 0xfd029f00
    [ 543.716170@0] remote: Wrong custom code is 0xfd029f00
    LibreELEC:~ #

    vi remote.conf，set factory_code

    factory_code = 0xfd029f00

    run command:

    LibreELEC:~ # remotecfg .config/remote.conf
    curpara:factory_code fd029f00
    curpara:work_mode 00000000
    curpara:repeat_enable 00000001
    curpara:repeat_delay 00000082
    curpara:repeat_peroid 00000078
    curpara:release_delay 00000014
    curpara:debug_enable 00000001
    repeat_delay = 130
    repeat_peroid = 120
    work_mode = 0
    repeat_enable = 0x1
    factory_code = 64770
    release_delay = 0x14
    debug_enable = 0x1
    LibreELEC:~ #

    press POWER button in remote and get log message:

    LibreELEC:~ # dmesg
    [ 2138.422743@2] remote: cur_mode = 0
    [ 2138.422761@2] remote: set_remote_mode[78]
    [ 2164.000795@0] remote: Wrong custom code is 0xa8579f00
    [ 2165.311417@0] remote: Wrong custom code is 0xa8579f00
    [ 2165.836795@0] remote: Wrong custom code is 0xa8579f00
    [ 2166.101722@0] remote: Wrong custom code is 0xa8579f00
    LibreELEC:~ #

    try to edit remote.conf with
    # 0x57 116 ;POWER

    LibreELEC:~ # remotecfg .config/remote.conf
    curpara:factory_code fd029f00
    curpara:work_mode 00000000
    curpara:repeat_enable 00000001
    curpara:repeat_delay 00000082
    curpara:repeat_peroid 00000078
    curpara:release_delay 00000014
    curpara:debug_enable 00000001
    KEYMAP_LEVEL: ircode = 0x57, keycode = 116
    repeat_delay = 130
    repeat_peroid = 120
    work_mode = 0
    repeat_enable = 0x1
    factory_code = 64770
    release_delay = 0x14
    debug_enable = 0x1
    LibreELEC:~ #

    also tried:

    # 0xa8 116 ;POWER

    but, none of can poweroff box

    and never got following:

    remote: scancode is 0x0043,invalid key is 0x0000.

    only get message as:

    remote: Wrong custom code is 0xa8579f00

    don't know, how to do

    my box's Skyworth Q+ remote dammaged, so I use third party remote, it can be used in LE12 with meson-ir format config file

    have no idea

    here I post meson-ir format remote config file which can work in LE12 and coreelec

    # table minix, type: NEC
    0x9f57 KEY_POWER

    0x9f43 KEY_UP
    0x9f06 KEY_LEFT
    0x9f0e KEY_RIGHT
    0x9f0a KEY_DOWN

    0x9f47 KEY_HOME
    0x9f16 KEY_CONTEXT_MENU
    0x9f02 KEY_ENTER
    0x9f4f KEY_ESC

    0x9f5d KEY_VOLUMEDOWN
    0x9fff KEY_VOLUMEUP

    0x9f8a KEY_MUTE

    You didn't interpret the description correctly, so the factory_code is not correct either.

    I made a new one based on the remote code above, please try it:

    This file should be copied to /storage/.config/remote.conf.