Hi, changed my autostart file like this:
1: nano /storage/.config/autostart.sh
2: Deleted old wrong line
3: Added this: ntpd -d -n -q -p pool.ntp.org
After reboot it looks to work so far. Thanks!
Hi, changed my autostart file like this:
1: nano /storage/.config/autostart.sh
2: Deleted old wrong line
3: Added this: ntpd -d -n -q -p pool.ntp.org
After reboot it looks to work so far. Thanks!
How can I use this? Do i have to add it somewhere in a settings file?
Hi Klojum, I tried that, even put it at 60 seconds but no effect. The strange thing is that as soon as Kodi is starting, my sync with Emby and DVBLink are working right away no matter which amount of seconds I set to wait. SO it looks like the connection is there. I will try to run a bug report later today. Maybe that helps.
Hi, I am having problems since updated to 8.0.2 with the time settings.
I already tried this:
-Check regional settings in Kodi interface settings menu.
-Added different time servers in the librelec addon.
-Enabled the option to wait for a connection before starting Kodi.
-Adding a autostart script: nano /storage/.config/autostart.sh
#!/bin/sh
(sleep 30; \
/usr/sbin/ntpdate pool.ntp.org; \
)&
When I reboot the system, the time is incorrect.
When I just open one of the time server fields in de libreelec addon and close it again, the time is corrected on the spot. Even when it was an empty field.
I have the PI on all the time and have it rebooted automatically every 24 hours.
I would think this means the time server is working but just not on the startup of LE. Is there a way to trigger the time server after startup? Or is there an other way to fix this?
Thanks for any help!
I have the same issue with LibreELEC 8.0.0 on the Wetek Core. After a while the GUI is extremely slow and mosthly a SSH reboot is the only option.
LibreELEC devs, I see several threads related to this topic, does it make sense to still share bug reports or is there enough information for you to investigate?
chears
Hi,
I am running my Wetek Core with LibreELEC 7.0.2 on the NAND and have it setup now in such a way that it will stay on and reboots every morning at 5am to make sure it's free of hick ups and PVR syncing is up to date. Now I only see one challenge, we have multi users at home with their own watched statusses for movies and TV Shows and now when the Core stays on the user can be confused and be using the wrong user account and in that way mix up the watched statusses of an other user. Therefor I was hoping for an option with my remote. I use a Flirc receiver in combination with a Logitech Harmony 650. So I have flexebility to configure buttons to specific commands. Ideally I was hoping to swop the power off command with a logout command. Is there a way to do this? Maybe with a script?
by the way, i am not an advanced user...:)
It looks like it was indeed the skin, no issues after the skin swop. I also see similar complaints in the Kodi subforum of the Xperience skin. Thanks!
Thanks for the advice. I started with going back to the default skin. So far I was not able to reproduce the freeze. I'll share conclusions after a few days.
After deleting all related addons and de Superrepo repository I rebooted the Core but again I was able to reproduce the window freeze.
This time it was after playing online music with the addon ListentoEU for a period and after stopping I tried to switch to the TV guide. There it froze.
Attached are the logs.
Thanks for looking into this, I'll start cleaning all addons linked to Superrepo and we'll see if the issue still occures.
Hi DaVu I am not that experienced with the debug logs, therefor my appologies if I provide the wrong data.
I activated detailed logging and reproduced the issue.
Attached are all logfiles in the logfolder. Just added everything....
Hi,
Just installed LibreELEC 7.0.2 on my Wetek Core's NAND last evening to test stability. So far it looks positive, it's a nice fast solution. I only have had a few freezes while navigating between windows.
Below is the logged comment behind this, what can cause this?
08:09:52 T:3036155904 NOTICE: InitWindowSystem: Using EGL Implementation: amlogic
08:09:52 T:3036155904 ERROR: EGL error in InitDisplay: 3003
08:09:52 T:3036155904 ERROR: InitWindowSystem: Could not create display
08:09:52 T:3036155904 FATAL: CApplication::Create: Unable to init windowing system
rgrds, Bert