Posts by kszaq

    I decided to release a 7.0.1-based build before fixing the "not being able to power on by remote" issue for V3_1 board. This bug is related to broken u-boot and not easy to fix without breaking features for other boxes, like CEC wakeup. The bug is also present after upgrading to cyx_MXQ_8189etv_8g1g_kodi_16.0_160419.

    7.0.1.1 7.0.1.1

    Commits from 7.0.0.2 to 7.0.1.1: Comparing 7.0.0.2...7.0.1.1 · kszaq/LibreELEC.tv · GitHub
    Kernel commits from 7.0.0.2 to 7.0.1.1: Comparing bd872fa628...9bf155dcbb · kszaq/linux · GitHub

    Changelog:

    • LibreELEC 7.0.1
    • fixed m201 "costdown" board LED on resume
    • minor new CEC driver initialization fixes
    • reverted Amlogic changes in kernel wireless stack for better WiFi performance
    • added overlayfs support in kernel
    • included PLL fix for 4K TVs (thanks Sam Nazarko)
    • fixed a rare issue with repeated power button keypresses
    • using 4K block for SquashFS for minor system partition read performance bump

    Known issues:

    • V3_1 board cannot wake up from suspend/power off by pressing remote power button (u-boot bug)
    • 29.97 progressive videos may stutter
    • sometimes CEC may not work
    • power LED on not officially supported boxes may not work as intended (too many boards to support them with a single build)
    • no HD-Audio passthrough and multichannel audio output
    • DVB support is experimental, some USB DVB tuners don't work at all


    I have connected from my windows 10 via Natwork Browser and dropped it on the configfiles folder but remote still not working .

    What am I doning wrong ?

    Have you rebooted after copying the file?


    Hi, i am using the Beelink MXQ with 7.0.0.2 and i just wanted to ask if the known issue "sometimes CEC may not work" means that CEC randomly turns on and off again. Which is currently my problem.

    Yes.

    If "factory" firmware uses standard Amlogic remote driver, it should also use remote.conf to setup. If you still have factory firmware on internal memory, you can extract any file from system partition in LE. Boot into LE, connect over SSH and run:

    Code
    mkdir -p /tmp/system
    mount /dev/system /tmp/system


    system partition content will be available in /tmp/system.

    To copy remote.conf to LE run:

    Code
    cp /tmp/system/etc/remote.conf /storage/.config/remote.conf

    To test the new remote.conf without rebooting run:

    Code
    /usr/lib/libreelec/remote-config


    libcec-daemon stops by itself.

    cec-client works when loaded by itself. It listens to my remote presses. No action is shown on-screen...but the terminal hears every remote press when I run cec-client in the manner you describe above. Here is a dmesg after booting and running cec-client.

    bPhC

    This means that CEC driver works well and there is a bug in libcec-daemon... not really my field of expertise. Unless there's some updated version of libcec-daemon available, I won't be able to make it work with your TV.
    [hr]

    Thank you!

    OpenElecCrazy: I need to get ssv6051-sw.bin and ssv6051-wifi.cfg from your Android firmware.

    You can extract them to Downloads samba share by booting to LE and executing the following commands:

    Code
    mkdir -p ~/downloads
    mkdir -p ~/downloads/ssv
    mkdir /tmp/system
    mount /dev/system /tmp/system
    find /tmp/system -name ssv\* -exec cp {} ~/downloads/ssv/
    umount /tmp/system

    Did you stop libcec-daemon or it stopped by itself? If the second, this seems like a bug in libcec-daemon. Can you test if cec-client works, of course with no libcec-daemon running in background and CEC off in Kodi?

    Yes, you can use the same skin.

    Yes, already installed addons should work the same (unless they do some OE-specific magic).

    There is no "unofficial addons" repo, other repos should work the same.

    No visible changes except there are no OE logos.

    Yes, on hardware side nothing changed: kernel and drivers are exactly the same.

    If you're running from SD card, you can create SD card backup of your SD card in Win32Imager to be on the safest side possible. For NAND, you can use TWRP for full backup.


    I am also seeing the device show up in my TV list but when I select it I am unable to get any navigational control. I tried to edit the keymaps using the keymap editor but it did not pick up the daemon.

    I am using this explicit command :

    libcec-daemon -d -p 0 --usb /dev/AmlogicCEC

    I can tell that it is somewhat working because if I do not run that command in my autostart.sh I will not even see the device in my TV list. Thank you so much for pursuing this !!! We are very close!

    You can simply use libcec-daemon -d. Can you grab me a full kernel log (dmesg | paste) a few seconds after a reboot? I suspect CEC driver may be misbehaving and that's why you can't control your TV over CEC. I'm still trying to improve the new driver as I've seen it misbehaving, I'd like to see if the reason is the same on your side.


    Ok here are some photos. Ill get the other files next...

    Thank You!


    Very nice photos! I have bad news and good news: bad news is that this is a very new WiFi chip with no official drivers from Amlogic. Good news is that I was able to find a driver on GitHub and I might be able to compile it. You need to give me a few days.


    Is there any chance that one of these builds can install on Odroid C1+?

    Or can you add C1+ to your support devices?

    ps. I'm now using wrxtasy's OpenELEC build from here but seem not updating for a while.

    I'm afraid my builds won't work with Odroid C1(+). While on Kodi side things should work - it's also S805 - I think Odroid may need a different kernel image and different u-boot. I don't have Odroid C1 and I won't be able to build for it. You can ask Wrxtasy to share his sources and it should be quite easy for you to port them for LE build.


    I don't have access to the original firmware. I must have tried dozens of different firmwares but none of them show my blue LED. This is the closest I've been to working correctly, the LED is red when it should be red and off when it should be blue.

    The only thing I can say is that I found a bug that doesn't turn the LED back on for "costdown" boards. I'm not able to help any further. To support all the LEDs, I'd need to make a separate build for every board there is.


    Ok cool I think I have what you need, I have added all the logs that were in the folder. I have "Blue" MXQ_S805_V3_1_20151230 and the box is currently running M201D SD 7.0.0.2 IMG. I do not see any wireless connection in the connections tab under LibreElec. Looking at my board my WiFi chip is labeled SV60510_TUB5T_4S41, eMMC chip SKhynix_H27UCG8T2ETR_BC_612A. Please let me know if you need anyhting else.

    Thank you for the logs. You seem to have an unknown SDIO WiFi chip that doesn't even show in the logs. Can you tell me what is the Realtek chip you have on your board? And can you also give me a result for cat /sys/bus/sdio/devices/*/device && cat /sys/bus/sdio/devices/*/vendor? I think you may have 8189FTV chip and there's no driver for it in my builds (yet).


    My question is which LE ROM should I use to update my box from OE to LE based on the above? The HD18q or the MXQ build?

    Thanks!

    The same that worked for you with OE releases. There are 2 differences between all the builds: device tree and remote.conf. Everything else is the same.

    When libcec-daemon is already running or CEC adapter is active in Kodi, running libcec-daemon will fail as there can only be one connection with CEC kernel driver at the time. With libcec-daemon running in background, I am getting the same results as you do, yet there is a "LibreELEC" device available on the list from my TV and I'm able to control Kodi when I select it. Keys are mapped a bit differently, that needs some adjustment...


    Edit : I was able to shut down the cec in setting\system and I was able to load the libcec-daemon successfully (No cec controll in Kodi though). When retroarch is running it does not see the new udev CEC device as an input. Have you been able to get CEC recognized in retroarch with this?

    If there's no control in Kodi, it means that libcec-daemon was not able to connect over CEC. Turning off CEC adapter in Kodi does not always work for me without a reboot, can you try doing that?