Posts by chewitt

    EDID data from the TV over HDMI advertises 1080p @ 60/59.94/50/30/29.97/25/24/23.976 (all the normal HD modes) so I would be trying to use 1080@60 not an odd resolution like 1360x768 (the kernel sees 1360x768 not 1366x768).

    If you have video output which goes a little beyond the screen (and the TV auto-scan mode doesn't fix that) you can calibrate the TV output using Kodi (the wiki article was linked in an earlier post). Note that you need to calibrate each mode used, e.g. if using adjust-refresh to change from 1080@60 to [email protected] for better playback you will need to calibrate the [email protected] mode in addition to the default desktop mode.

    I'd suggest updating to https://releases.libreelec.tv/LibreELEC-AMLG…h64-11.95.2.tar or https://chewitt.libreelec.tv/testing/LibreE…ch64-12.0.0.tar as there are some minor improvements for AMLGX in LE12/K21.

    Now you have a working image we need to rebuild/test with different BlueZ versions. To guide the process we will download sources for BlueZ and start a "bisect" process in the BlueZ source directory by marking known-good (v5.72) and known-bad (v5.73) release commits (using the commit githashes):

    Code
    cd ~/
    git clone https://github.com/bluez/bluez
    cd bluez
    git bisect good 770ad5614e7e8074133e6f563495ce4822f63fe4
    git bisect bad 19f8fcdc2084048bebe5bd9ea4fb97f7ece16df0
    git bisect start

    Bisect will now suggest a githash to test. Change to the LE buildsystem (open another tab in Terminal to make copy/pasting easier) and edit packages/network/bluez/package.mk and make changes:

    ^ We change PKG_VERSION to use whatever githash bisect is asking to test (change this each time). We also null PKG_SHA256 so it is ignored (to make testing easier). We also change PKG_URL to download from the BlueZ mirror on GitHub instead of the normal repo as this supports downloading at any githash in the repo (the kernel repo only has release versions).

    Once package.mk is modified, run the "PROJECT=xxx ARCH=xxx" image build command again and the buildsystem will detect the BlueZ package changed and it will rebuild that package and create a new image. You can then transfer (e.g. scp) the built image (.img.gz or .tar file) to /storage/.update/ on your test device and reboot to see if the image works?

    If the image is good run "git bisect good" in the BlueZ source dir, and if bad run "git bisect bad" and bisect will suggest another githash to test. Keep repeating this process (edit githash, rebuild, test, mark good/bad) until bisect tells you the first bad (breaking) commit. Then report back here with that info.

    Good luck :)

    how do I create an image of the SD card that can be useful for later use with multitool on the TV box?

    Sorry.. no idea and subzero interest in investigating the topic further. As a rule backup/restore of /storage contents is always easier and faster than trying to "full-image" devices so I'd recommend learning some basic tar/untar commands.

    I really hope there's a way to get the wifi working

    Not happening. The SSV6501P chip has no driver that works on Amlogic hardware and upstream kernels. Some Armbian devs have wrangled the rather horrific vendor code to use on Rockchip boards, but in the process of simplifying the code for their Rockchip needs they removed support for the Amlogic chip implementation. You'll need to use an external USB dongle for WiFi.

    Would you mind adding a ffmpeg plugin with the 4.4.x ffmpeg version as a alternative?

    There's no info on your hardware/codecs/configuaration or Tvheadend configuration, and no debug logs .. /shrug

    So assuming there is a real problem (not related to client-side drivers) the issue should be reported to Tvheadend devs so it can be investigated. If the problem is in Tvheadend (as you suggest) that's where a fix is required; we have no interest in packaging retro ffmpeg versions for workarounds.

    Code
    connmanctl
    agent on
    scan wifi
    services
    connect <service>

    Use connmanctl to join a WiFi network ^

    Code
    <advancedsettings version="1.0">
      <!-- enable debug logging -->
      <loglevel hide="false">1</loglevel>
    </advancedsettings>

    Then create /storage/.kodi/userdata/advancedsettings.xml with ^ that content and reboot so Kodi is in debug mode. Then run "pastekodi" and share the URL generated so I can see the system log and Kodi log.