I don't know for sure about that. I do know that channel has perfect time, and now that the Mio is not using NTP, it's not changing all over the place anymore.
Osmio 4K Clock Problem
- Thread starter Alan Rovner
- Start date
- Latest activity Latest activity:
- Replies 117
- Views 14K
Well, I moved my dish to H&I channel on 101w. I then went into the menu and did a Restart. After the Restart, it automatically MOVED the dish to 99w, and brought up the Bars & Tone channel and synced time.
I then tried the same thing with it just in Standby. When I brought it out of Standby, it once again automatically MOVED the dish from 101w to 99w, and the Bars & Tone channel.
So, seems like this might work. Guess we'll have to leave it like this for now, and see what happens in the future. As long as it doesn't try to sync to NTP time, it shouldn't mess up for whatever reason that it was. Though I'm now wondering if setting a delay of 30 seconds or so to sync time with NTP, that would also work? I never tried that, because supposedly that's supposed to be for Wifi connected receivers, and mine is wired ethernet. Might be something else we could test, as maybe keeping the receiver in Standby is somehow a factor with it going crazy on NTP time sync?
I don't remember any FTA satellite receiver that I have ever owned that could keep correct time.
I do have an OSMio but cannot criticize its time accuracy because it's powered off 99.9% of the time and I never connect it to the internet. I seem to have lost interest in FTA.
I do have an OSMio but cannot criticize its time accuracy because it's powered off 99.9% of the time and I never connect it to the internet. I seem to have lost interest in FTA.
Also turn OFF "NTP Cold Start", and make sure you hit the Green button for SAVE
I did that right after posting and seems to have fixed that issue. I still have some kind of problem with adding additional timers though.
I've lost interest in television altogether. I find myself watching reruns because todays programming turns me off.
I've had time issues in past, but now my Mio+ is working perfectly. I am using TNAP 4.0 Build 2021-05-08, Enigma version 2021-06-02 Kernel 5.12.0 [T2MI]. The software update screen shows no further updates are available. I never turn off my receiver since turning it off in past had introduced time issues occasionally. I have my system time setup as shown below:
I believe it's placing the Mio into STANDBY that causes the clock issue. IF you leave it on all the time, that's probably why you don't have time issues.
I like my stuff to go to standby or turn completely off. It may not be a significant energy saving but if you left all of your electronics on all the time then it does become significant. Just my opinion. I even have my central air conditioner set to 80 during the daytime.
I dunno if this post is useful, but I have an original dm900 and am locked into using the dreamOS images, which is not nearly as customizable as the images you guys get to use, so i had to do things all via my own customization's.
I created a script that runs at boot up via the systemd :
www.howtogeek.com
My script is simple.
#! /bin/sh
rdate -s utcnist2.colorado.edu
rdate -s utcnist.colorado.edu
echo $(date) - NTP Update >> /media/hdd/ntp.log
exit 0
As long as you have an internet connection, then the clock sets at bootup. Also, make SURE you disable the time being set via Transponder. - I believe your images allow you to set that via the menu system. On my image, i had to manually edit the settings file within /etc/enigma2 folder. You can only modify the settings file when enigma2 isn't running. To turn off enigma2, telnet in and issue a Init 4 command. Then you can ftp into the box and modify the settings file and modify the transponder time setting. Then telnet into the box, and issue a reboot command.
Date/Time is VERY important for me. I also wrote customization's that gives me full EPG information for all my channels. If the date/time doesn't set correctly, then the EPG is all screwed up. I have really enjoyed being able to utilize the EPG to setup record timers.
I created a script that runs at boot up via the systemd :
How to Run a Linux Program at Startup with systemd
Launching a Linux program at startup isn't a black art, it's just a series of steps. We'll show you how to do it with systemd.
www.howtogeek.com
My script is simple.
#! /bin/sh
rdate -s utcnist2.colorado.edu
rdate -s utcnist.colorado.edu
echo $(date) - NTP Update >> /media/hdd/ntp.log
exit 0
As long as you have an internet connection, then the clock sets at bootup. Also, make SURE you disable the time being set via Transponder. - I believe your images allow you to set that via the menu system. On my image, i had to manually edit the settings file within /etc/enigma2 folder. You can only modify the settings file when enigma2 isn't running. To turn off enigma2, telnet in and issue a Init 4 command. Then you can ftp into the box and modify the settings file and modify the transponder time setting. Then telnet into the box, and issue a reboot command.
Date/Time is VERY important for me. I also wrote customization's that gives me full EPG information for all my channels. If the date/time doesn't set correctly, then the EPG is all screwed up. I have really enjoyed being able to utilize the EPG to setup record timers.
Where did you get that one? Mine is 06/02/21 (develop) even after doing on online update. I don't see a 06/17/21 version, even at Legit?
Ok, I see it available there, but there's no info about it, and EB hasn't posted anything. So, I don't know. I'm not going to be the first...
I've had this issue since I purchased my mio. It has done this to me on different flavors of enigma - tnap ,openvix, and the current image I use, openpli. It's done it on numerous releases of those flavors. It seems to me to have something to do with recordings. It will be on the right time and you may set up a timer and find it back to 1970. It may happen when you play a recording. I haven't done any systematic or structured troubleshooting, because it seemed to be more trouble than it was worth. I went as far as setting up an openpli build environment and building and installing that build in one of the "slots" on the mio; thinking I could debug it from there. It was a learning experience, for sure; but with other problems taking precedence I never carried it through. I just set it up to sync on ntp time once an hour and keep an eye on it when I set up or play a recording.
ebo
Far better than NTP time. It might be off around 5 seconds, but it beats it suddenly going to something random, at a year or months earlier.
EB over at Legit says it's an on-going issue with the NTP time software originally built into Enigma images. He claims that it'll be fixed for once and all in TNAP 4.1, which is a few weeks off.
