The android kernel is most likely different from the linux kernel used in Libreelec. As I wrote in the second post of this thread, some android firmwares use
/sys/devices/virtual/amhdmitx/amhdmitx0/rgb_modeYou can try using that or check what files exist in that directory. Most newer Android firmwares have the "force RGB" option in the settings, you could try to find an update for your box.
Make sure that you use an editor that allows for UNIX-style line breaks (e.g. notepad++) or better use the nano editor on the ssh shell (like the wiki page told you to).
You do not need sudo, and most likely you need to include the full path to ifconfig, so try this:
/sbin/ifconfig wlan0 downYou are right, both commands render my VC-1 media unplayable. It is very smooth by default, but becomes out-of-sync and slow with the commands.
You can put the command in the file autostart.sh in the config directory. This file is executed every time libreelec starts. The old openelec wiki describes it nicely:
I was mistaken about the soc, sorry.
there are no device trees for boxes with 3gb. You will need to extract the device tree for your box so that it can be adapted for libreelec.
Currently not supported SoC Amlogic S912. Please read here: thread-1653.html
That is interesting.
It makes me wonder why so few people are moaning about this...
To be honest, while I can see the difference clearly in the pattern video, I fail to notice it with my regular media.
My eyes are not the best and my TV with which I can test is quite old, so this might contribute. My projector setup is still on Jarvis; I did not compare there.
Do you have the chroma upsampling issue with the build from Raybuntu (official LibreELEC?) on your Wetek Hub as well?
Image from krypton kszaq or krypton raybuntu (beta3) looks the same to me.
I would still like to know if this is a S905X-specific issue or if S905 is affected as well....
I only own S905 devices (see signature), so the chroma upscaling issue is present on both 905 and 905X.
This time I also had a look at the Spears&Munsil chroma upsampling pattern and the difference between Jarvis and Krypton is very obvious.
I am not really capable to take a picture of the phenomenon... I tried.However in Krypton, all the "Low Frequency Zone Plates" look much worse than even Nearest Neighbor, extremely blocky.
In Jarvis, they look like something between Nearest Neighbor and Bilinear on the upper circles, Bilinear or Bicubic on the lower circles.Patterns:
#4723768Explanations:
Choosing a Color Space, 2nd Edition | Spears & MunsilThe "High Frequency Diagonal Bursts" are also much worse in Krypton.
Thank you for providing the link to the sample files and explanation. I did some testing today and can confirm your observations: The images from Krypton and Jarvis are different, and Jarvis is the less blocky one.
As far as I followed the development, the kernel is the same for both versions. So presumably, somewhere in the code, the video decoder might be initialized slightly differently.
Regression from 5b (wetek hub): I have no longer the option to use pulseaudio (bluetooth) audio. I can only select amlogic pcm or amlogic hdmi.
Starting bluetooth service and connecting my headset still works, though.
After restarting the hub, the option appeared. Will test further.
Please report any regressions (previous and known issues are known!) vs 7.95.beta5b.
Regression from 5b (wetek hub): I have no longer the option to use pulseaudio (bluetooth) audio. I can only select amlogic pcm or amlogic hdmi.
Starting bluetooth service and connecting my headset still works, though.
Am I right in assuming, that the "premium" S905 devices (like Odroid C2, WeTek Hub, WeTek Play2) currently have the same issues with the video player / hardware decoding in Krypton, as all the others do? For instance the frame skips...If this is a hardware decoder issue, all devices behave equally, right?
There are a few differences:
The wetek devices contain the neccessary keys to allow for HDCP encryption, the odroid-c2 and all the no-name chinese boxes do not.
The wetek and odroid hardware specifications do not change, so you can always be sure what you will get when you buy the box (esp. with wlan and bluetooth chipset).
But all boxes with S905 SoC should behave in the same way regarding video processing and output.
There is currently no box from wetek or odroid using the S905X SoC, so you will be limited to no-name boxes here. While the advantage would be the hardware decoding of HDR and VP9 content, some of the feedback by S905X users makes me think that this chipset might behave differently when decoding h264/h265 video. I do not own a S905X device, so I cannot compare.
Android might not properly power off the box. To test, you can
My cheap OTT box simple switches off HDMI output when I push the "off" button...
There is no passthrough available for live TV in kodi Krypton. Multichannel audio will be decoded to pcm.
Hello,
I feel stupid - when creating the new sdcard I forgot to change the device tree. It worked fine with the first beta, but not with the second.
Everything works fine with the wetek hub device tree.
Hi,
I installed the latest Marshmallow beta for the wetek hub. Dual booting from sd-card is supported (boot screen shows message and power button on remote can be used to switch boot device from "nand" to "sdcard") but does not work with booting kszaq's builds from sdcard. I tested both Jarvis and Krypton releases, and get
"error in mount_flash: mount_common: could not mount /dev/mmcblk0p1"
The wetek hub release from raybuntu boots fine, on the other hand.
