Posts by chewitt

  • Bricked MXQ Pro 4K

    Moving to a separate thread as your problem has nothing to do with the (entirely different) WeTek Hub issue.

    Amlogic boards always boot from eMMC if signed Amlogic boot code is present in the right sector on eMMC, and you have flashed a ROM image with incompatible (has the wrong RAM chip timing details) u-boot to eMMC so the board is stuck in a boot loop.

    The best option is (re)flashing the original Android ROM to eMMC using Amlogic Burning Tool to restore the correct u-boot. The less simple option is manually shorting pins on the eMMC flash chip to temporarily disable the chip so it is not seen and the board will then attempt to boot from SD/USB media. It's not difficult to short the pins, but the problem will be finding a signed u-boot version that supports the board (as they need to support the right RAM timing data) and supports booting from SD card (as the compatible u-boot in an Android ROM will be for eMMC boot and on GXBB/S905 that means the AML signature in the wrong location).

    I do not have a collection of old Android boot ROMs (aside from WeTek Play2/Hub) and the only GXBB boards LE provides bootable SD card images for are WeTek Play2 (and Hub, but that has issues), Odroid C2 (which will not boot on anything else due to internal hardware checks), and the NanoPi-K2. So our options are limited and I have low time/interest in changing that.

    Searching for old S905 MXQ Android ROMs is the right direction. Flash them and see if they at least boot to a kernel. If they do you can force recovery boot to run Linux again. If they don't, you didn't make anything worse than it already is.

  • HDR on x86 Hardware

    Kodi supports upgrading. It does not (and never has) supported downgrading. In LE the OS packaging (everything in the read-only SYSTEM file) means the core OS and Kodi itself will downgrade fine, and newer Kodi DB versions created during upgrade will be ignored. However settings, add-ons, and add-on settings in the persistent /storage area were updated from LE10 to LE12 and those do not downgrade and will not be compatible with LE10. If you manually delete /strorage/.kodi/addons/* it will probably work again. If not, you might need to trash /storage/.kodi/userdata/guisettings.xml as well. And no guarantees on /storage/.kodi/userdata/add_data/* settings being compatible either. You may end up needing to clean reinstall.

  • LE 12.0 - Pi 4B 2GB - Unable to update library: Compressing DB 0%

    Code
    2024-06-16 13:46:58.137 T:936     error <general>: CCurlFile::Exists - <dav://USERNAME:[email protected]:5000/Films/> Failed: Weird server reply(8)
2024-06-16 13:46:58.137 T:936   warning <general>: Process directory 'dav://192.168.16.102:5000/Films/' does not exist - skipping scan.

    Do you see the same issue if you use SMB instead of WebDAV?

    I suggest this because "Yes, Kodi supports WebDAV" but I don't recall any of my Team Kodi colleagues ever admitting in public that they used WebDAV to access media, so it's almost never being tested among wider changes. SMB in comparison; is being used all over the place by everyone and will probably just work.

  • FFMPEG cannot stream and decode with MPEG-DASH.

    I guess it did't work because the tidal2 add-on depends upon inputstream.ffmpegdirect and not the native ffmpeg version used by Kodi that we patched in the image; so the patch is still effectively missing.

    mglae submitted changes to make changes to ffmpeg and ffmpegdirect earlier, which are now merged, so if you wait patiently for 24-48 hours those changes will have arrived in the latest LE13 nightly and updated add-ons in the LE13 add-on repo.

  • Bqeel M9C Max (S905X) - Wipe data interrupted / doesn't boot anymore / no remote

    Android boxes either power-on when you apply power or they have a power button on the case to turn on. If yours has no button, the box is powering on but failing to boot. This could either be a hardware failure (eMMC device gone bad) or a software problem (flashing the wrong ROM to eMMC and breaking boot) or a combination of both (eMMC is bad so the ROM flash fails). UART boot logs from the device are the only way to see what is happening during early boot to understand device state. If you cannot share UART logs there is nothing more we can do. NB: Even if you can, our help is going to be limited: this is a forum for supporting our distro so there is no magic ROM archive to help with reflashing Android and we have little interest in fixing broken boxes.

  • Path to Files on internal storage

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. Generate a log URL (do not post/upload logs to the forum)

    use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

  • Request - Partial Library Update (newer files only)

    Code
    It could log the timestamp of the last scan, then process all folders newer than said timestamp.

    The incorrect assumption ^ is that clock time inside an OS is a reliable concept, and in reality it's not, it's a little fluid. These days most devices have no local RTC chip and rely upon internet time; so time is only accurate for 'most' users 'most' of the time.

    The better approach is to have change detection similar to Plex and some other mediacentre apps. Then once an initial long-format scan has been completed you only need to scan content being added or changed, which is inherently faster.

    The challenge is always that ideas are easier than implementation :)