Posts by kszaq


    Odd how someone took the time to remove an unsolicited link to the box I purchased, (which I'm 100% ok with) all I was trying to do is give complete picture of exactly what I have and what problems I'm having. But what makes no sense is that my issue was never addressed, not even a simple and short "yes, that correct device tree, not sure why it's slow." I did my best to be very through in my device & problems unlike many other posts.

    I removed your link while browsing posts on a smartphone according to a request to not post any store links. I haven't answered your post until now to provide a more complete one - I don't like typing long posts with Tapatalk. And as I am the only developer behind these builds (I mean device-wise, core OS is of course developed by the LE team) you can only get an answer from me or a user trying to help.

    The device trees that are available in download folder are based on my comparisons with generic device tree for previous kernel and porting changes to the latest kernel. I can never say for sure a device tree is correct one for your box or not. That said the differences between them are very minor and most of the time if it boots - it works. That's why for a next release I will make only a few generic device trees to fit most boxes.


    It's defiantly a build or tree issue. Expecially when an old Rpi is literally 60-90 times faster. Which means something on Rpi that takes 1sec, takes over a min on this build. Which is really odd, because Rpi uses an inferior USB.

    Not sure what else I could post to help identify the problem. And if the problem can't be fixed, just it being acknowledged so others done spend 20hrs trying fix an unfixable issue.

    An old RPi has much greater support, both SoC-maker and community-wise.

    What you might be exepriencing is a memory leak that has been corrected to some extent for the next release. You can try using the latest test build I posted a few days ago that includes some fixes. I hope your experience will improve a bit: LibreELEC-S905.aarch64-7.0-devel-20160830160706-r23311-g51fe9ae.img.gz

    xsi I have MiniMX 1/8 and it uses AP6212 for WiFi which is capable only of 20MHz channels in 2.4GHz band. I must also say that antenna in this box is really poor.

    If you can connect to WiFi, it means the driver is already there. The only change for already supported devices from the latest build will be a firmware fix for AP6335.


    1- Sometimes it freezes and I have to unplug to reboot, it is normal?

    MK808B Plus have flaky cooling, they might overheat from time to time.


    2- Using kore in a android smartphone, it lags responding to the kore commands. Is something wrong with my internet connection?

    Are you using the latest build? There is a patch that improved WiFi response time.


    3- I use a 2Gb old class 4 Kingston sdcard, it can affect the performance of LE?

    A faster SD card means faster boot and userdata operations so yes, it affects performance. That doesn't mean that you should change your card to a different one if you're OK with performance you have now.


    kszaq How is the optical pass-through audio progress going? Can we expect it for next release?



    Everything is working fine after the first attempt, exept the SPDIF-output. SPDIF isn't shown in the audio-output setting anymore, but it works with Android on NanD. With 7.0.2.005 on my other Beelink Mini MXIII SPDIF is working perfect.

    ...has anyone an idea?

    In S905 there has never been an option in Kodi menu to choose S/PDIF output. With Amlogic whenever you send something to audio ouput, it is output by both HDMI and S/PDIF when possible - i.e. stereo tracks or DD/DTS. Optical output works on my box by simply selecting HDMI for output.

    To make SPDIF output work, you need a device tree with optical output definitions. Default Amlogic device tree is for electrical S/PDIF and I admit I might have omitted that change in device tree for MiniMXIII. If your box has 2GB RAM and 1Gbit Ethernet, you should try using gxbb_p200_2G_iNepo_Q.patch device tree. Fot the next release build all device trees have defaults for optical output.


    I am about to try NAND install MiniM8s Pro S905 2g/8g and i am confused by the step 1 below's meaning ?
    This step is not needed for first install ?
    I understand the rest.

    Internal memory is divided into several partitions - one of them is recovery and another is dtb. When you use toothpick method, u-boot looks for recovery and dtb image on SD card/USB drive and if it doesn't find them, it loads them from internal memory. When you install >=.006 build to internal memory, factory device tree in internal memory is replaced and it won't work with factory recovery (not true for boxes with the latest kernel, i.e. S905X and maybe some S905).

    Why it says "This step is not needed for first install"? When you have original factory firmware on internal memory, you also have original device tree that works with recovery image. So when you install LE to internal memory for the first time, you don't need to provide recovery and device tree images.
    [hr]

    During my work on .007 I developed a script that may help installing LE to NAND for people having issues with it yet who can run LE from SD card. This should work for all releases. Here's how:

    • The script is experimental, you do it on your own risk! Download original Android firmware before installing anything to internal memory!
    • Boot LE from SD card and connect to your box over SSH.
    • Execute the following commands:
      Code
      wget http://kszaq.libreelec.tv/s905/tools/installtointernal
      . installtointernal
    • Follow on-screen instructions. The scripts says it makes a backup copy of recovery and device tree but in some cases this might not be possible. It should still be able to write LE to internal memory.


    I accidentally powered off an MXQ while upgrading from 5.0.8 to the latest release. Usually you would type 'exit' and it will reboot but doing that just reboots to this prompt. Is there any way to unbrick this? The toothpick method doesn't even register


    Sent from my iPhone using Tapatalk

    Your SYSTEM partition needs to be re-formatted. Try using a procedure for new NAND installation. With the latest build you will keep you data.


    Also noticed, related to sound, that by default in this build the audio output device is defaulted to AML-M8AUDIO:ANALOG (AML: @ in config file) and I also have available AML-M8AUDIO:HDMI (AML:HDMI in config file.) I wondered if the HDMI setting should not be the default?

    This will change for the next build.

    koenkooi Can you try if rootwait in CMDLINE with my standard options helps booting?