My first impressions of LE 13 on RPi 4 after upgrading:
Well what can I say upgrading to LE 13 solved the issue for me. The timezone option is gone from Kodi settings and migrated to LE addon. So far no issues, yay!
Sounds like a lot has changed in this regard I could certainly give it a shot. I'm just a little worried about running nightlies on production (family lol) system especially since new Kodi is still in alpha. I guess I can try cloning the SD card or at least backup the LE partition beforehand. Anyhow I'll let you know how it goes.
I also noticed that connman itself has idea about timezones (connmanctl clock)
Hi! I get this rather strange behavior that EPG is late by one hour after reboot. Here's what I gathered so far trying to troubleshoot:
#!/bin/sh
name=$1
sqlite3 ~/.kodi/userdata/Database/Epg16.db << EOF
.parameter set @name "$name"
SELECT
sTitle 'Title',
datetime(iStartTime, 'unixepoch', 'localtime') 'Start',
datetime(iEndTime, 'unixepoch', 'localtime') 'End'
FROM epgtags
JOIN epg USING (idEpg)
WHERE sName = @name AND date(iStartTime, 'unixepoch', 'localtime') = date('now', 'localtime')
ORDER BY iStartTime;
EOFI'm using 12.2.1 with RPi 4. Has anyone else experienced something like this before or has any clue what's going on?
Whatever the problem was it seems to be fixed in 12.0.2 
I'm not able to launch games stored in zip files when browsing Games source. Opening zip doesn't seem to do anything. Surprisingly everything works when done from File manager: I can browse zip contents and select rom file and Kodi presents a list of compatible emulators.
I tested this feature in Ubuntu with Kodi 20.2 from PPA and it worked. I'm able to browse zip and launch rom from inside:
LE version: 11.0.6
Device: RPi4
Very cool but what will happen after version in /usr gets updated? My guess is you'll be stuck with the one you copied over to /storage until you update it manually.
Thank you for your detailed explanation and pointers. Now I need to experiment with build system commands a little. From what I've learned I can see two possible ways of adding something reliably to LE: one is producing a static binary with distro toolchain; the other is maintaining a package with dependencies within LE build system. The first one is more suited for quick testing (just build, scp to LE, run) the other for better long term integration and rebuilding.
That's strange because I can't find any trace of qt in hyperion addon. The binaries are not linked against it and there are no libraries maybe it's compiled in statically?
If you add "qtbase" to https://github.com/LibreELEC/Libr…EC/options#L259 the files should be available?
Haven't tried this. Is it possible to build just a single package? I was actually using system cross compile toolchain not LE one to compile the app.
Hi there I recently tried to cross compile a command line app that uses Qt toolkit to use with LE. Unfortunately, I couldn't link qt5 libraries statically because distros don't ship static versions of them. I didn't want to recompile entire toolkit so I started to search for any traces of qt inside LE and found qtbase package. I can see it's used as dependency of hyperion addon but do any of its files end up in LE filesystem?
Here's what I'm missing btw:
# ldd Skyscraper
/usr/lib/libarmmem-v7l.so => /usr/lib/libarmmem-v7l.so (0xf78e0000)
libQt5Gui.so.5 => not found
libQt5Network.so.5 => not found
libQt5Xml.so.5 => not found
libQt5Core.so.5 => not found
libGL.so.1 => not found
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf7710000)
libm.so.6 => /usr/lib/libm.so.6 (0xf76a0000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xf7660000)
libc.so.6 => /usr/lib/libc.so.6 (0xf74f0000)
/lib/ld-linux-armhf.so.3 => /usr/lib/ld-linux-armhf.so.3 (0xf79ef000)So there's some inconvenience to get to the DVD title but it works and it proves that DVDs can also be played by a DVD drive connected to a hub.
I have DVD drive (in USB3 enclosure) connected through a powered hub as well Play Disc entry appears in the main menu of Estuary although I've noticed that it sometimes there is a delay. The problem with my powered hub is that drive keeps being spun up periodically even after powering off RPi causing inconvenience of having to disconnect the drive after usage.
/storage/.kodi/userdata/advancedsettings.xml .. create it if required, it doesn't exist (as it's not needed) by default.
This is only required when one wants to change the default port number (9090).
In Kodi 10.0.4 only EventServer port (9777) is opened after restart despite the option "Allow remote control from applications on this system" being enabled.
# netstat -tulp | grep kodi
tcp 0 0 0.0.0.0:36666 0.0.0.0:* LISTEN 1047/kodi.bin
tcp 0 0 0.0.0.0:50152 0.0.0.0:* LISTEN 1047/kodi.bin
tcp 0 0 :::36666 :::* LISTEN 1047/kodi.bin
udp 0 0 localhost:9777 0.0.0.0:* 1047/kodi.binAfter toggling the option JSON-RPC is initialized and the port 9090 is opened and allows connections.
There is a warning in the log during boot regarding JSON-RPC not sure if it's relevant to the issue
2023-02-13 03:55:47.383 T:1047 WARNING <general>: JSONRPC: Could not parse type "Setting.Details.SettingList"
2023-02-13 03:55:47.383 T:1047 INFO <general>: JSONRPC: Adding type "Setting.Details.SettingList" to list of incomplete definitions (waiting for "Setting.Details.Setting")
2023-02-13 03:55:47.384 T:1047 INFO <general>: JSONRPC: Resolving incomplete types/methods referencing Setting.Details.Setting
2023-02-13 03:55:47.412 T:1047 INFO <general>: JSONRPC v12.4.0: Successfully initializedDoes netcat work for anyone? I tried connecting to Kodi JSON-RPC port but it results with error:
# nc localhost 9090; echo $?
1Edit:
Seems there is a bug with JSON-RPC port not being opened after reboot which requires toggling menu option "Services/Control/Allow remote control from applications on this system" each time
Oh nevermind the above procedure is outdated. Anyway getedid create correctly dumped EDID and setup files in /flash for booting with it. No manual steps needed and everything works now. But I still don't understand why kernel needs such assistance: is this RPi limitation or faulty TV?
I'm facing a similar problem with an old TV as described by thread author. Additional symptom is that unplugging and reattaching the HDMI cable during Kodi operation results in black screen until Kodi is restarted. I will try above procedure tomorrow and see if it helps.
I'm a bit curious why EDID needs to be stored in two places:
- /flash/edid.dat
- /storage/.config/firmware/edid/edid.bin
The first one will be used by firmware during boot and the second one is for kernel?
2023-01-28 02:22:08.697 T:1434 INFO <general>: Starting Kodi (19.5 (19.5.0) Git:19.5-Matrix). Platform: Linux ARM 32-bit
2023-01-28 02:22:08.697 T:1434 INFO <general>: Using Release Kodi x32
2023-01-28 02:22:08.697 T:1434 INFO <general>: Kodi compiled 2023-01-07 by GCC 10.2.0 for Linux ARM 32-bit version 5.10.110 (330350)
2023-01-28 02:22:08.697 T:1434 INFO <general>: Running on BCM2835 with LibreELEC (official): 10.0.4, kernel: Linux ARM 64-bit version 5.10.110
Why is Kodi is compiled for 32-bit ARM in RPi4 build? It might have been the case before in earlier releases but it's the first time I noticed this.
Yes but the effect is that the audio is then downmixed to a stereo signal.
What kind of audio interface you're using? You should be able to send multichannel PCM over HDMI as long as the receiver supports it:
For digital audio, if an HDMI device has audio, it is required to implement the baseline format: stereo (uncompressed) PCM. Other formats are optional, with HDMI allowing up to 8 channels of uncompressed audio at sample sizes of 16 bits, 20 bits, or 24 bits, with sample rates of 32 kHz, 44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz, 176.4 kHz, or 192 kHz
AFAIK current latest LE & Kodi releases does NOT have a special support for DVB-T2 USB sticks. So you have to check whether the DVB-T USB stick you wish to use is supported by Linux kernel (release that current LE is running on) or not.
I'd have to investigate this since I'm not sure whether they need any device-specific driver in kernel. They are USB devices after all so also part of some standard USB "class"?
