Posts by rabaraf

Quote from chewitt

I don't see anything abnormal logged; using an AMLGX image on an N2 board, with the timezone configured for Asia/Dubai or with the timezone changed to Europe/Warsaw:

Code

N2:~ # connmanctl clock
  Time = 1771724187
  TimeUpdates = auto
  Timezone = Asia/Dubai
  TimezoneUpdates = auto
  Timeservers = [  ]
  TimeserverSynced = True

Code

N2:~ # grep -i bias /storage/.kodi/temp/kodi.log
2026-02-22 05:35:27.952 T:808      info <general>: Time zone bias changed from 0 mins to -240 mins (due to time zone or DST change).

If there was a general issue with timezone configuration and ntp updates (ConnMan) there'd be a ton of forum posts on the topic; and there are a decent number of people using LE13/K22 nightlies and this is the only report. This normally points towards an issue being network/environmental related and not something in the LE image.

Have you tried rebooting your internet router?

Hi,

First of all thank for your response.

The issue is now resolved. I commented it here: https://discourse.coreelec.org/t/coreelec-22-…e-bias/58212/11

Kodi 22 Nightly – "Unable to obtain time zone bias!" on LibreELEC (musl platform)

Summary
=======
Kodi 22 nightly on LibreELEC repeatedly logs:
Unable to obtain time zone bias!
This does not occur on Kodi 22 nightly under Windows using the same addons and configuration.
The message appears when addons perform timezone conversions using Arrow (e.g., utc.to('local')).

Environment
===========
- LibreELEC-AMLGX.aarch64-13.0-nightly-20260208-1a819bf-odroid-n2.img
- Kodi 22 (Alpha nightly)
- Hardware: Odroid N2
- Timezone: Europe/Warsaw
- tzdata installed (zoneinfo present)
Comparison system:
-----------------
- Windows 10
- Kodi 22 nightly
- Same addons
- No timezone bias errors
Additional Comparison:
---------------------
Kodi 21 (Nexus) on LibreELEC -> No timezone bias errors
Kodi 21 on CoreELEC -> No timezone bias errors
Kodi 22 nightly on LibreELEC -> Error appears
Kodi 22 nightly on CoreELEC -> Error appears
Kodi 22 nightly on Windows -> No error
This suggests the issue may be a Kodi 22 regression affecting musl-based platforms.

Log Example
===========
2026-02-20 17:08:43.526 T:973 error <general>: Unable to obtain time zone bias!
The message repeats whenever timezone conversion to local time is performed.

Timezone Configuration Verification
===================================
Timezone configuration on LibreELEC appears correct:
- /etc/localtime -> /var/run/localtime
- /var/run/localtime -> /usr/share/zoneinfo/Europe/Warsaw
- /usr/share/zoneinfo/Europe/Warsaw exists and is valid
There is no /etc/timezone file (which is normal on many minimal systems).
Therefore, tzdata and localtime symlinks appear properly configured.

Observations
============
- The issue is reproducible on LibreELEC nightly.
- The same Kodi nightly build on Windows does not produce the error.
- CoreELEC (also musl-based) exhibits the same behavior.
- This suggests the issue may be platform-related rather than addon-related.
- LibreELEC uses musl libc, whereas Windows and typical Linux desktop systems use different time APIs (or glibc).

Hypothesis
==========
The issue may be related to how Kodi 22 nightly retrieves timezone bias information on musl-based systems.
Timezone files are correctly configured, so the problem may be in:
- Kodi’s timezone bias retrieval logic on musl
- Interaction between Kodi and musl time functions
- A regression introduced in Kodi 22 nightly
This does not appear to be caused by addon logic, as the same code works correctly on Windows.

Expected Behavior
=================
Kodi should obtain timezone bias information correctly on LibreELEC and not log "Unable to obtain time zone bias!" during normal timezone conversions.

If further debugging information is required (strace, additional logs, testing specific builds), I’m happy to provide it.

Quote from Fabrice95

but have same stuttering with subtitles. If anyone have a solution plzase help me.

Use MKVToolNix and mux your subtitle file into the mkv container.

Quote from knfevg

Whats the latest build available for u9h? On mine is says Libreelec (wrxtasy-kszaq) 8.2.5-chroma.42w.10bit

You are correct. This is the latest version available for download from mega link provided few posts above. I'm running it on my Minix U9-H without any problems with "standard" 1080p and 2160p HDR content as well.

Quote from Mr.Brown

THanks again for the build, I was about to sell the Minix U9 and get something else for it, because I find Android OS based software media players usually garbage. They usually have plently of issues and some stuff doesnt work like support for all HD audio streams, correct color space etc.

This is brilliant idea to have on "Video process, Audio process, System Information" screen (when OPTION button on TV remote is pressed) more information such as Color space, Chroma subsampling, Colour depth...

I would confirm that micro-stuttering is noticeable on my Odroid-C2 running LibreELEC (Leia) v8.95.2 BETA. This is almost not visible but when I'm looking with my eyes very close to the screen it is perceptible, especially with the scenes where camera is moving along the landscape very slow but for 5 or more seconds - then for sure I see motion is freezing for one or more frames.

So for that reason I'm going back to LibreELEC (community): 8.2.3.1-C2 (Kernel: Linux 3.14.29) build made by kszaq where micro-stuttering is not happening at all.

Another problems I noticed with Leia Beta 2:

- CPU temperature is huge in idle mode. This is around 68-73 ºC when screensaver is active while on kszaq build it is 48-52 ºC

- Create System and Kodi Backup action is starting and window is disappearing after one or two seconds but the backup file is taking as I see in WinSCP how the file's size is growing. Until backup is completed screen in LibreELEC is frozen.

Running LibreELEC (Leia) v8.95.2 BETA and first discovery is that the CPU temperature is EXTREMELY high. While on LibreELEC (community): 8.2.3.1-C2 (Kernel: Linux 3.14.29) build made by kszaq I had around 48-52 ºC now it is 68-73 ºC in idle mode (screensaver active)

Hi all,

I have been running around 2 years LibreELEC (community): 8.2.3.1-C2 (Kernel: Linux 3.14.29) build made by kszaq which is by the way excellent.

I have specific settings and a lot of customization made in Kodi, add-ons, boot.ini, advancedsettings.xml, key mappings, etc...

Today I tried to do an upgrade to official build LibreELEC (Leia) v8.95.2 BETA

Steps performed:

1. LibreELEC backup done in "old" kszaq's build

2. Installed LibreELEC (Leia) v8.95.2 BETA

3. Restored LibreELEC backup

Everything went good and my Odroid-C2 booted, add-ons updated themselves, startup screen showing Kodi Leia, etc...

Only one thing is "wrong" - In System Information I see that I have Kernel Linux downgraded from 4.19.12 to 3.14.29

Is there a way to upgrade just only Linux Kerne? Or there is no way and I need to install LibreELEC (Leia) v8.95.2 BETA again, restore only Kodi backup and do remaining customization manually?

Sorry for noob question but would like to have that one missing part sorted out with your support of course guys...

EDIT: I run LibreELEC downgrade to v8.95.1 directly from LibreELEC menu selecting LibreELEC-9.0 Update Channel hoping it will replace kernel to 4.19.12... at booting process I saw KERNEL and SYSTEM were extracted and installed... but when Kodi started I still see Linux Kernel 3.14.29. So I decided to install LibreELEC (Leia) v8.95.2 BETA from scratch and... surprise: in fresh installation there is LibreELEC (official): 8.95.002.9.0 (Kernel: Linux 3.14.29) So maybe all official LibreELEC (Leia) BETA builds are running with Linux Kernel 3.14.29 although LibreELEC web page says in one of the updates bullets: * Updated to Linux Kernel 4.19.12 ???

Quote from Kodianer

[...] but play, stop, forward and so on show no response at all. [...]

I was able to find the solution for non-working Pause, Stop, Start, Forward, Backward buttons on my Panasonic TV's remote. First I discovered those buttons are starting to be non-responsive when I did a restart of my Odroid-C2 and the solution is: if you watch something in Kodi just switch off TV and then switch it on again and.... those buttons are working again. Don't know why it happen....

Quote from chewitt

This is a known issue in amcodec (which is why it's not seen on pi) and probably won't be fixed until the next major wave of VideoPlayer changes land in Kodi Leia (v18). You can use skip steps rather than rewind to move back in a video and things are okay.

Thanks for information
Yes, of course skip backward can be used but you have to remember to don't press skip button too fast one by one as it sometimes also causing a freeze.
Will be waiting for next Kodi 18 release...

Would like to report a bug in latest (LibreELEC-Odroid_C2.aarch64-7.95.3) build for Odroid-C2.
Steps to reproduce:
watch a movie (doesn't matter if h.264 or h.265) and then press Rewind button (can be any speed, for example x2) to back for example 1 minute and then press Play button ---> video freeze.

This issue doesn't happen on Raspberry Pi 7.95.3

Primary mistake is to use samba protocol in Linux world. NFS should be used instead of SMB. So if you have RPI, Odroid, Wetek, etc. running Libreelec which is Linux and have your content repository on NAS (Synology, QNAP, Netgear, etc) which is also running on Linux system then its obvious that you should share your files using NFS as this is native file sharing protocol for Linux. SMB in this configuration is simple big mistake. Of course it will work but: slower and utilizing CPU heavily and... as we can read above configuration to get it work require a lot of effort and time.

Quote from reddevilmeuk

[...]it can traverse the file structure but not download play any content[...]

permissions? Mine are: 0664

Quote from reddevilmeuk

hi i'm having the exact same issue the Pi cannot connect to a sharedDB. If I remove the advancedsettings.xml and add the path manually it works..... if I add the advancedsettings.xml file back and try to browse the share it hangs the Pi

has anyone anymore on this?

the wait for network has been tested with no avail....

No, that problem doesn't occur for me.
My configuration: SQL DB running on D-Link NAS, Odroid C2 configured by advancedsettings.xml to connect to that SQL DB provided by IP address (not by name), media content on NAS shared using NFS (no Samba), LE configured to wait for Kodi fo 10 seconds at startup.
Part of my advancedsettings.xml:

<videodatabase>
<name>MyVideos</name>
<host>192.168.1.111</host>
<user>kodi</user>
<pass>kodi</pass>
<type>mysql</type>
<port>3306</port>
</videodatabase>
<musicdatabase>
<name>MyMusic</name>
<host>192.168.1.111</host>
<user>kodi</user>
<pass>kodi</pass>
<type>mysql</type>
<port>3306</port>
</musicdatabase>

Quote from outcave

I have same your config:
Odroid-C2 ----(HDMI)----> Onkyo Receiver ----(HDMI with ARC)----> Panasonic Plasma TV

I'm still using my workaround: setenv hdmi_cec "0" in /flash/boot.ini

Try this:
power off Odroid
power off TV

then

power on TV (select HDMI as input)
power on Odroid

when all it's powered on and you are able to see Kodi, on TV change the input from HDMI to TV.
Now select again HDMI so Kodi is again on TV
Reboot Odroid.

Now it should be working.

CEC support on Raspberry Pi is better then Odroid C2.

Display More

"when all it's powered on and you are able to see Kodi" - at this stage I see a black screen only so I did few switches from HDMI to TV and finally I saw Kodi on TV but still Stop/Pause/Rewind buttons were not active so I repeated procedure and got additional unexpected result: no sound on TV, so unplugged HDMI cable from Odroid-C2 and made sound back on TV through Denon, then repeated your procedure again and got Stop/Pause/Rewind buttons on TV remote somehow working.
Unfortunately I'm fully agree that CEC support on Odroid-C2 is much worse than it is on RPi2.
Need to consider if Odroid-C2 should be my HTC device or should I stay with RPi2 and wait longer until Odroid-C2/LibreElec/Kodi will be improved in CEC area.
Anyhow thanks for your procedure - it just showing how unexpected results we have in CEC on Odroid-C2.

Quote from outcave

Hi.
Yes, if I power off the TV and then power On the TV (leaving LibreELEC powered on) these "extra" key works... strange behavior
But, anyway, after a LibreELEC reboot these key will not works again. And, as you can imagine, I don't like to power off the TV and then power On the TV to have these keys working...

SOLUTION:
I made some troubleshooting and I was able to get these buttons working always by disabling the CEC in the boot of Odroid C-2.
So I edited the file "boot.ini" in "/flash" and changed the row from setenv hdmi_cec "1" to setenv hdmi_cec "0".

Disabling HDMI-CEC at boot solved the issue. CEC will anyhow works because it will be stared later from LibreELEC.

I have just migrated from (RPi 2 + LE 7.02) to (Odroid-C2 + LE Alpha 10) and experience exactly the same problem: Stop/Pause/Rewind buttons on TV Remote doesn't work. Configuration is: Odroid-C2 ----(HDMI)----> Denon Receiver ----(HDMI)----> Panasonic Plasma TV.
Those buttons were working properly with (RPi 2 + LE 7.09)
Unfortunately your solution: setenv hdmi_cec "0" in /flash/boot.ini doesn't work for me.

Does it work on previous LE Alpha builds?

Hi all,
OE is a dead project so I decided to upgrade OE to LE on my RPi2. Upgrade went without problems so I'm happy user of LE.
Configuration is as follow:
RPi2 --- HDMI ---> AVR Denon --- HDMI ---> TV Panasonic.
Problem:
When switching off TV (using TVs remote) and then switching off AVR (using AVR's remote) Denon is automatically switching on, so I have to press Power off button again in order to switch it off.
That was not happen when running OE on RPi2 but is so annoying when using LE.
I was trying to find out a threads related to this issue but no one reported exact the same behavior.
Hoping this will solve the issue I have upgraded to LE 7.90.005 but it remain and unfortunately settings for CEC are not appearing - just an empty box so I can't experiment with changing settings.
Any suggestions?
Is anyone experience the same result with CEC?