I used to be able to tell OpenViX I wanted to use my local NTP server (it's in my router, I specify it by its IP address) rather than by using transponder time, and it would work perfectly.
But now I've noticed that if I do this, the time doesn't necessarily get set correctly for quite some time after booting. I haven't waited to see how long it takes, but I know a few (5 or 10) minutes doesn't seem to do it.
It took me a while to figure out what was happening, since just rebooting without going into deep standby and removing power often seems to result in OpenViX starting up with the clock approximately correct anyway, like it just remembers in RAM or in a hardware clock chip or something. Normally I don't often use deep standby and disconnect the power, which it what it seems to take to make it almost always really obvious that the clock is wrong when it starts up again.
Of course, I can use Transponder time, which I am now doing, and that works well correctly setting the time correctly within a few seconds after booting, but in the past the NTP option did seem to work well for me.
Do you think this could be a bug introduced recently?
I guess there are other possible explanations, such as a worn out battery in a backed hardware clock in the box.
But I'd kind of assumed they did bother with battery backed clocks in enigma2 boxes, since the software always has a way to get the time anyway.
Sorry this is kind of vague, and obviously it's very low priority, almost a non bug.