Posts by kszaq


    When looking for a tree close to a box like the one i uploaded (MxMax 2G/16G) what suggestion would you advise if this devices tree wont be uploaded.
    Cheers

    I haven't taken a loot at this device tree as this is a tedious process: unpack transfer to my compile server, decompile to dts, compare pre-compiled dts... takes a lot of time and honestly I prefer spending my time on development and not comparing device trees. Take 3 factors into account: SoC (S905/S905X), RAM size and Ethernet speed. Then look for a device with similar specs.

    During my analysis of device tree I have noticed that many of them are very similar. I decided to not ask you for more device trees and instead I will compile the most common ones and include them in next build's download folder.


    Boot to recovery:

    • Android - there's no official option to do that but it's possible through some app. So I did boot into menu but all I've got was message that there's a corrupted file system or something like that. Check attachement to get the idea.

    I think this is the method you should use. Have you tried using a different SD card, made from scratch using e.g. Rufus? Do not replace dtb.img on LE SD card at this point, your box should boot with device tree that is supplied in image. Does it also tell about filesystem corruption on new SD card?


    Did you try enabling CONFIG_RFKILL_GPIO in kernel config, and adding OBDA8723 to the rfkill-gpio acpi list, as specified here ?

    Amlogic platform uses a different RFKILL driver and there's no need to enable this.

    Can you try this with both dev versions (first one and second one if possible):

    Code
    echo 0 > /sys/class/rfkill/rfkill0/state && sleep 2 && echo 1 > /sys/class/rfkill/rfkill0/state && /usr/bin/rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5


    2 possible solutions then:
    a) Set a timeserver inside LE configuration screen. Boot up as usual, wait inside kodi for about 30 secs. Reboot (warm).
    b) put autostart.sh into configfiles dir with "sleep 30;" in it. Now on every boot it waits 30 seconds before kodi starts, network is already connected and has enough time to get a response from time server.

    Have you tried enabling "Wait on network" in LibreELEC Settings?


    libreelec 006 k1 plus combo dvb work? I do not detect DVB.

    There is no support for built-in DVB tuners, this has been mentioned many times.


    Can't get this to work on my Sumvision Cyclone X4+, which has been running V5 ok from SD. I followed the instructions, putting the img.gz file into the udate directory and rebooting. I could then see the usual updated messages, and it said it was rebooting - and never came back. I have "no signal" on the monitor it's connected to. Tried powering off/on but still the same. So I carried on and extracted the dtb.img from the latest android firmware and put it on the SD. I held the toothpick in and powered on - but the same. Absolutely nothing on the monitor (no signal).

    I then tried a new install of V6 on a different SD card (and also tried on a USB stick) with the extracted dtb.img copied on - but still the same when trying a toothpick recovery boot - no signal on the monitor.

    Not sure what else to try next.

    Please read the instructions carefully. dtb.img from Android firmware on SD card won't work as it is different from what is needed to run the latest kernel. You have to download the device tree from my site, as linked in first post. If a device tree from you device is not listed, you can try using the closest-specced-box tree and submit a PR to my devices tree repo. Alternatively if you don't know how to modify a device tree, you can post Android device tree in a proper thread and wait for me to parse it - this has to be done by hand and takes some time.


    And, if I physically
    connect via spdif out to UE Boom 2 speaker jack 3.5 in (using a spdif
    to jack 3.5 converter) then there is no sound.

    This is why you need to change device tree: to make S/PDIF audio work. I think for the next release I will modify generic device tree to be more compatible with optical output that is present on most devices.


    I used to read temperature from /sys/devices/virtual/thermal/thermal_zone0/temp but it gives:
    LibreELEC:~ # cat /sys/devices/virtual/thermal/thermal_zone0/temp
    cat: read error: Invalid argument

    This is a known issue as the latest thermal module from Amlogic doesn't work well with latest kernel. LibreELEC


    Thank you.
    The quarter screen problem solved but unfortunately the 4k playback has some glitches in every 3-5 seconds especially when the GUI overlay is on.

    Edit:
    I've repeated the test with the next version (http://kszaq.libreelec.tv/s905/test/2016...0127b4.tar) too and got the same result. Maybe they differs in wifi stuff only.

    Yes, second test version only has some updates to Bluetooth drivers with no changes to 4K support.

    The 3-5 seconds lag appear as it seems that S905 is not capable of 4K playback + 4K GUI rendering at the same time. I will assemble a 2nd build for you today with different approach to GUI scaling to test.
    [hr]


    Will you recommend to use one of these versions or stick to the official 006 build?

    The test versions also have improvements in RAM management, I would recommend sticking to them.

    RAM is there to use. ;)

    I think that with 1GB RAM the pressure to free up memory when scrolling would be higher.

    Usage dropped for you to 30%. This would be an issue if it didn't drop or was rising constantly to the point where the box would freeze.