NTP is incredibly flaky

KyleS · December 8, 2017 at 5:11 AM

I've seen this issue on and off since starting to use Libreelec. I thought it was a couple bad servers in the pool, and just bad luck... However, even tonight I added 1.ca.pool.ntp.org and 2.ca.pool.ntp.org, rebooted... still no clock set.

Obviously adding `ntpd -p 0.ca.pool.ntp.org 1.ca.pool.ntp.org 2.ca.pool.ntp.org` to my autostart.sh resolves the issue instantly, but this is crap for less knowledgeable people. Please consider using ntpd or similar instead of the current mechanism.

**chewitt** · December 8, 2017 at 8:52 AM Official Post

On what hardware? .. we need a volunteer to test a connman change that should resolve these issues. As none of the staff experience the problem we've not been able to test it.

KyleS · December 9, 2017 at 12:51 AM

amlogic s905 clone box, using Wireless. I've set the network to block on boot so it's not a race in that regard.

**chewitt** · December 9, 2017 at 7:48 PM Official Post

Which 'community' release are you running? .. we can bug the creator to add the patch we need testing and spin you a build.

KyleS · December 13, 2017 at 8:10 AM

Quote from chewitt

Which 'community' release are you running? .. we can bug the creator to add the patch we need testing and spin you a build.

kszaq currently.