I found an LE-8.2.5 firmware that supports the CVBS output:
If possible, try it on an SD card, and if it works, the patches will need to be integrated into version 9.0.2.
However, the analog audio output will probably not work with this either.
I found an LE-8.2.5 firmware that supports the CVBS output:
If possible, try it on an SD card, and if it works, the patches will need to be integrated into version 9.0.2.
However, the analog audio output will probably not work with this either.
Unfortunately, none of the devices I use have official support, so I personally didn't encounter this update bug.
I don't know how the update check procedure works, but I changed the version number in the patch to "9.0.2-DVB" instead of the original "9.0.2" and the update check may not like extra strings.
"9.0.2" > "9.0.2-DVB" ?
Unfortunately, the problem is twofold. The first problem is that the CVBS output was disabled 5 years ago, because it causes problems with HDMI: projects/WeTek_Play: Remove support for CVBS output, because it cause… · OpenELEC/OpenELEC.tv@ffe3936 · GitHub
The second problem is that the analog audio output is also not working.
So, in the first approach, the simplest solution might be to get an HDMI-Composite or an HDMI-SCART converter if you would not use the HDMI output for anything else. Fortunately, these adapters are available cheaply from China, but due to different TV standards (PAL/NTSC/SECAM), you need to find carefully a compatible converter for your analog TV.
I also use one of my boxes with an adapter on a Full HD monitor, although it’s an HDMI-VGA, that also has a D/A for audio with a 3.5mm stereo jack connector.
I tried to compile the official 9.0.2 sources with my patches and it worked on the first try.
It is downloadable from here: Index of /3rdParty/WeTek_Core-9.0.2-DVB-semi-official/
But if you want to compile it yourself, I made a patch to the original source. You need to do the following:
git clone https://github.com/LibreELEC/LibreELEC.tv.git -b 9.0.2
cd LibreELEC.tv/
wget http://libreelec.dtech.hu/3rdParty/WeTek_Core-9.0.2-DVB-semi-official/Source/LibreELEC.tv-9.0.2-WeTek_Core-DVB-source.patch
patch -p1 -i LibreELEC.tv-9.0.2-WeTek_Core-DVB-source.patch
DISTRO=LibreELEC PROJECT=WeTek_Core ARCH=arm make image -j8
But I couldn’t try the image because I don’t have a WeTeK_Core device.
Since then, I have updated the crazycat package and added support for the dvb-latest package, because I had a lot of stream quality problems with the Astrometa DVB-T2/C tuner under the crazycat addon. It took about a week to put the packages and their configuration together to make them work.
I also got an Xbox One tuner and tested it. Works perfectly with both crazycat and dvb-latest packages.
This screenshot was taken from TVH-4.2 running on my M8S device (LE-9.0.2/amlogic-3.10, selected kernel addon: dvb-latest):
You need to clone my github repo, or just download the sources directly from here: e00c4a39e6c9c042ccc4896f8d3fbbc99fe8a940.zip
The simplest solution is to replace the entire contents of "packages/linux-driver-addons/dvb" in your source directory with the contents of my source.
And you will then need to make the following changes to the "projects/WeTek_Core/options" file:
# build and install driver addons (yes / no)
DRIVER_ADDONS_SUPPORT="yes"
# driver addons to install:
# for a list of additinoal drivers see packages/linux-driver-addons
# Space separated list is supported,
DRIVER_ADDONS="crazycat dvb-latest"
After that, you need to start building. In short, that's it.
Hi guybrush,
I have built some versions of the crazycat drivers for the S812 SoC, with amlogic-3.10 kernel support for my device (M8S+), and maybe it will work on Wetek Core as well.
But you need to install driverselect package first:
script.program.driverselect-0.1.6.100.zip
... and then the driver, one of them:
Index of /dvb-packages/crazycat/
You will need to restart your box after installing and selecting the driver.
OK and installing libreelec directly to box so I dont have to use dual boot?
Since the Android part doesn't work well then how to install directly to MXQ the libreelec so I don't have to use the external SD Card....................
Hi AZlink,
I also have a piece of box with this PCB. Do you have the stock ROM for this S805 Rev 2.0 (20150806) board?
I tried several ROMs, because the original ownership of the box crossflashed it to a different firmware.
The kszaq's LE 8.2.3, and my LE 9.0.2 test builds are working properly on the box (m201d), but I want to use the factory original IR remote (0x40400001) instead of the remote of my M8S (0xfe010001), and I have an issue with the front red/blue LED control too.
All this functions hardcoded to the original uboot, but I couldn't find it.
If you (or someone) have the correct ROM, or a download link, or just the filename / build date / something usable information, please share with me.
Hi dtech,
I used Demetris version 18.6 and the remote.conf is working fine. I can turn the box OFF no problem, but turn it back ON did not work. So far
the only Demetris Libreelec version Kodi 18.0 is working perfect on my box. Other version my box had a problem to turn it back on after turn it OFF. I had OTT M8S box with Eny M8S ROM installed. I did rename the copied dtb to dtb.img and put it to the root of the SD card.
I don't know the Eny's uboot which power options used. If it supports power off correctly, you can try my M8S+ bulid on your box instead of M8S build.
My M8S supports suspend mode only, but my box isn't an Eny version.
Which device do you have? An Eny M8S 2G? And what was the name of image file that worked by Demetris?
Did you rename the dtb file to dtb.img and copied it to the root of sdcard first partition? If you just copyed the file into device_tree it is not enough.
And one more thing: my M8S (n200C) and Eny M8S (n200) have different IR remote.
I found some picture from Eny's remote, and it uses same remote like MXQ (S805) device.
If you have this remote, you need the correct remote.conf: remote_mxq.zip.
My builds are tested with two variant of M8S+ box, and it perfectly works with ap6330 and bcm4335b0 as well.
The two boxes have same PCB, the only difference is just the wifi/bt module, but both are working.
My M8S (n200C_2G, PCB: CS_812M8_V1.3) build is based on same source, and it also have ap6330 on the PCB, ad it works too.
Maybe if you have a correct dtb (n200_2G?), it will work, but I cannot test it, because I don't have any n200-based S812 device.
I found a solution that can be used for my problem as well: How to deactivate screensaver after resume from suspend?
If the box resumes from suspend, it can send a "BACK" command with "kodi-send", and it closes the Power menu before the HDMI signal shows on the TV screen. This solution works perfectly: add kodi-resume service to ignore power menu when wake up · dtechsrv/LibreELEC.tv@41e66bc · GitHub.
Okay, but how? I compile LE from source, so I will try to find a permanent fix for this sutation, a source code patch would be the best.
The autostart.sh is just a temporary modification for one device only, but it is not enough.
I tried to figure out what process handles this, because systemd have a "kodi-lirc-suspend.service" script.
If I send the box to suspend mode, dmesg shows the last pressed button was ENTER (Power menu -> Suspend item selected).
The box is now in sleep state. I press the power button again. The box wakes up, LED changes from red to blue.
But there is no pressed button listed in dmesg. Kodi somehow still detects this button event, and it shows the power menu again.
I tried to override power button event: instant sleep instead of power menu.
But it causes an evil endless loop: wake up and back to suspend again...
Thanks, but this is not a real solution. If I need to completly ignore power menu, I can comment out the line of power button in the remote.conf.
But I need the power menu if the power button pressed in normal mode.
I don't know what process can handle power button event if the box is in suspend mode.
If the button is pressed, the box wakes up, but Kodi also handles this button event. I have the problem with the last thing only.
Hi all,
I have a problem with the power button of my IR remote control. The uboot of my box (M8S, Amlogic S812 2G/8G) doesn't support power off correctly, therefore I applied a suspend patch in Kodi (LE 9.0, Kodi 18.2).
The suspend and resume works fine with my box. When I press power button, the box woke up, but the power menu always shows up after resume.
If somebody have a solution, how can I ignore power button event in Kodi after I sent to sleep the box, please share with me.
Thanks,
dtech.
I also made a custom version for M8S+ devices, which based on the Demetris' source:
GitHub - dtechsrv/LibreELEC.tv: 'Just enough OS' for Kodi for OTT M8S+ TV boxes
(Compiled LE image for M8S+: Releases · dtechsrv/LibreELEC.tv · GitHub)
Maybe my source repo is usable for Eny M8S (n200) devices too, because I also replaced the kernel version to another one.
The original kernel was unbootable on my M8S+ device, because it encountered a problem with NAND flash pins.
This is a legacy LE v9.0.2 build with Kodi 18.2, because later versions from Kodi (18.3+) have a very strange issue with Simple IPTV client (very slow channel change, about 8-10 seconds), and I cannot find the correct patches for this issue. Maybe it exists, because on AlexELEC doesn't have this issue with newer Kodis, but sadly Alex cannot update his sources on GitHub.
I also have an M8S device (n200C_2G, PCB: CS_812M8_V1.3), and it works with same meson8m2_KII.dtb.
The only thing I had to replace was the remote.conf, but I also patched the LE's remote-config script, so it loads remote.conf from /flash too.
I tried to solve the power issue, because my M8S's uboot cannot turn on via IR remote control. So now it goes to suspend instead of power off state.