Posts by chewitt

  • backup kodi from ubuntu and restore to LE

    Assuming there is no media on the internal drive and you only need to move config data: IMHO it will be cleanest/easiest to back-up only the Kodi userdata folder on Ubuntu. Then make a clean LE install and "restore" the userdata folder to /storage/ubuntu. You can now stop the clean (empty) Kodi install and selectively move essential files back before restarting or rebooting to effect the changes: Library DB files, your sources.xml and passwords.xml and advancedsettings.xml files, and the contents of the addon_data folder. You can reinstall all add-ons from the respective LE or Kodi repos and they will reuse the existing (previous) config. I would let thumbs etc. download again and I would go through the GUI to set things as you like again: guisettings.xml normally contains some /paths/to/things for Ubuntu that are wrong with LE and those aren't automagically updated. Most of the time it takes 5 mins max to setup Kodi again. Take pics of the major screens on a phone if you need to "backup" things. If you are familiar with the major files Kodi uses and where things are located the entire process is a 10-minute job .. plus some time for thumbs to resync.

  • recent Pi V3D kernel patches

    The current rpi-6.6.y kernel in LE12 images contains earlier iterations of the same changes. Once upstream merges the patches that are submitted to the mailling list the pi devs typically revert earlier changes and backport the now-merged ones to keep the kernels in sync. Then LE will pick the merged changes up in a future kernel bump.

    NB: I wouldn't expect any noticeable performance increases. Rendering the 2D Kodi GUI is a simple task compared to the complex 3D game graphics used for the benchmarks.

  • Can no upgrade LE 8.2.3.1 to major version 11.0.6

    If you reuse the SD card you will permanently overwrite the current/working install so I would recommend using a different SD card for AMLGX experiments. Then set the dtb name to use in uEnv.ini .. as per the wiki instructions.

    If the device worked with the p212 dtb before (means the box is GXL/S905X) use the meson-gxl-s905x-p212.dtb file. If you use the p212 dtb file from the old LE image or gxbb/s905 dtb files from AMLGX image the box is not going to boot.

  • Looking for Ideas LibreElec - Trakt - Sonarr

    Code
    systemctl stop kodi
rm -rf /storage/*

    That ^ should give you a system free of all the containerised piracy tools. Sorry if that's not directly answering the question.

    Thread

    Forum Rules

    General Conduct

    • Be polite and respectful to forum staff and other users
    • Be polite and respectful towards this project and other projects
    • Be patient, user and staff are spread all over the world, an answer may take time

    Posting

    • One topic per thread
    • Posts should be written in English (add text in your native language if needed)
    • Be as descriptive and detailed as possible. We are not mind readers!
    • Do not cross-post or double-post
    • Do not post or promote external URL links to products, a name
    …
    newphreak
    March 15, 2016 at 1:02 AM

  • CVideoPlayerAudio::Process - stream stalled

    Code
    2024-04-07 13:05:18.389 T:1107    debug <general>: OnPlayBackStarted: CApplication::OnPlayBackStarted
...
2024-04-07 13:05:29.383 T:1473    debug <general>: CPtsTracker: pattern lost on diff 83389.000000, number of losses 1
...
2024-04-07 13:07:28.544 T:1473    debug <general>: CPtsTracker: detected pattern of length 1: 41708.24, frameduration: 41708.333333

    It might be odd timestamps in the file. I see ^ logged which matches the "couple of minutes" theory. The file plays fine here on RPi5, but that's because RPi5 doesn't hardware decode H264 media (so it's the same workaround as disabling DRMPRIME).

    popcornmix  HiassofT might be able to explain more. I don't have an RPi4 around in current location.

  • Generic S905x boards

    The "box" image has bootscripts to hook into vendor u-boot and make it run an LE image. Your box has nothing on eMMC (either it has been erased or eMMC has failed) so there is no vendor u-boot to hook into and thus no boot with that image.

    The "board" images for VIM1 and LePotato have modern u-boot compiled for those specific boards installed (to the boot media: in this case an SD card) and these use modern u-boot config files (extlinux.conf) not Amlogic vendor boot script garbage. The files used to create/sign modern u-boot are device-specific so it's unintentional and unusual that your box can also boot with them.