Posts by kszaq


    Hi!

    Maybe test a experimental build with this source helps or at least check the commits to see if the backports contains something interesting.

    Is a Kodi 16 + a lot of backports + LE patches + patches from other projects like OSMC
    It contains 122 commits over the official version of Kodi 16

    Comparing xbmc:Jarvis...asavah:Jarvis-amlogic · xbmc/xbmc · GitHub

    Thanks, but these patches are actually LE patches from Wrxtasy and some from me. And as far as I can tell it will stutter on many videos (e.g. VC-1) because of a few patches that I already tested and ruled out... I think the approach in the latest test build is the best I've ever tested on my 50GB+ sample videos. ;)

    Actually what kostaman sees - skipping to next chapter - is correct behaviour.

    kostaman Can you try this devel version with "The Grand Budapest Hotel": LibreELEC-S905.aarch64-7.0-devel-20161116235711-r23437-g73c3cef.img.gz

    I also have that movie and what I noticed it that when you zap through chapters video sometimes freezes but if you wait a few seconds it starts working again. I think decoder needs to be fed with video packets to start working properly and it has to stay that way.

    Everybody else can also test this build for a/v sync of buffering issues. ;)

    I have been trying to make the kernel module for Aigaile chips load automatically but unfortunately I couldn't make it. The only thing I achieved is an easier hack:

    • first install this devel version - when updating from 7.0.2.009 you don't need a device tree: LibreELEC-S905.aarch64-7.0-devel-20161116235711-r23437-g73c3cef.img.gz
    • if you have the previous "hack" in autostart.sh, delete it - either the whole file or lines with the hack only
    • in Configuration folder (/storage/.config over SSH) enter modules-load.d directory and create file named wifi.conf and content cfg80211_qca. A SSH one-liner for this is echo cfg80211_qca > /storage/.config/modules-load.d/wifi.conf
    • reboot


    Please report if WiFi works "automatically" with this version and after following these steps.

    Is this option available now?

    Also, one bit of confusion. After nand install, is it still possible to boot from SD for testing future versions in the same manner? Does installtointernal still work the same way in this case?

    Not yet. I've modified the script but I need to test it first. If you want to take a look at it or test:

    Code
    wget http://kszaq.libreelec.tv/s905/devel/2016-11-15-script/installtointernal
    chmod +x installtointernal
    ./installtointernal

    Yes, as long as you have SD card with LE insterted your box will boot from SD, no matter which system you have on internal memory. I do this at home for testing: stable version for family on internal memory, testing from SD.


    1. I have been struggling with tweaking codes for my IR remote on my Venz V10 Pro (2GB / 16GB). Having first gone down the lirc route (as it works fine on my other media box which is x86-based and running libreelec Krypton alphas), I got very confused as irw wouldn't work for me and eventually I discovered that lirc wasn't even running and that the remote seemed to be being treated like a keyboard and was handled by the kernel directly. Can you confirm that on these AMlogic boxes lirc is no longer used and I shouldn't concern myself with it?


    LIRC is not currently used but there is a plan to switch to it. For example, devices in current LE master branch such as WeTek Hub and WeTek Play have been switched to LIRC implementation and I think my builds will eventually switch to it as well. Before doing this, I will need to gather LIRC configs from different remote controls from users. At the moment the LIRC driver for built-in IR receiver is not compiled in my builds as it would conflict with Amremote driver.


    However I noticed a couple of differences between my remote.conf and the one in /tmp. Are you "patching" some of the values, perhaps at startup? This info from your Jarvis build thread "fixed IR remote key code replacement script (e.g. remote button not working)" is leading me to believe this. Can I remove this script or override it if I wish? Is there a thread or other info you could point me to which would explain this newer way of handling remotes instead of using lirc?


    Yes, I am patching the user-provided or extracted-from-internal-partition file. Here is the source code for the script: LibreELEC.tv/remote-config at libreelec-7.0 · kszaq/LibreELEC.tv · GitHub
    If you want to override, you can load your file any time (e.g. in autostart.sh by executing /usr/bin/remotecfg [i]path_to_your_file[/i]
    There are no guides that I know except for some information in some remote.conf files: LibreELEC.tv/remote.conf at master · LibreELEC/LibreELEC.tv · GitHub


    2. I asked this question in the Jarvis thread, but it's so busy you may have missed it. I would like to know how the initial boot process on the box is patched to check the SD card / USB for the presence of a libreELEC image so that it boots in place of the Android system which is still installed on the internal flash. It's just my ignorance of Android showing!


    This is done by modyfing bottcmd in u-boot: LibreELEC.tv/aml_autoscript.src at libreelec-7.0 · kszaq/LibreELEC.tv · GitHub


    Sorry kszaq, I just realized that you are not reachable by PM. Could you please tell me if the following tree is ok ? There are no Kbuild files in the source code that I received. I just want to make sure that I have received the right stuff.

    That's what I got from them but I haven't been able to make them work, at least not with short testing with users who have the box.

    Driver for internal tuners is closed source and not available in my kernel tree. You need to obtain and add the driver to kernel source. Unfortunately I can't help on that matter.
    [hr]

    Hi andy5macht and a warm welcome.

    Unfortunately my builds don't work for Odroid-C2.

    You might be able to run LE from USB drive on C2 but you have to have eMMC/SD with bootloader every time: ODROID Forum • View topic - Can C2 Boot from USB Memory stick

    Some hints to do it (not a solution!): burn C2 image from Wrxtasy or an official image to USB drive, change second partition label to e.g. "LIBREELEC_DISK" and modify your boot.ini to boot from USB by loading kernel from USB and change cmdline to BOOT_IMAGE=kernel.img boot=LABEL=LIBREELEC disk=LABEL=LIBREELEC_DISK. You will get further help at Odroid forums for sure. ;)