One of my receivers is sometimes off by 2 minutes. Rebooting corrects it. But I have noticed that both receivers have minor differences in time between them most of the time. I'll be glad when they get the NTP time issue resolved.
Osmio 4K Clock Problem
- Thread starter Alan Rovner
- Start date
- Latest activity Latest activity:
- Replies 117
- Views 14K
......osmio 4k. openatv 6.3 & 6.4 in 2 slots.
tp or ntp time....perfect always.
el bandido is a great dude. but if tnap were so good i'd be using it right now.
just saying.
tp or ntp time....perfect always.
el bandido is a great dude. but if tnap were so good i'd be using it right now.
just saying.
The bad thing about using AFN for time sync is that when I stop watching a program the dish moves over to 99W. I suppose that doesn't happen if the receiver is on all the time. But I don't want my receiver on all the time. Any news of a NTP time sync fix yet?
No, though he has posted some TNAP 4.1 test images if you want to try them.
That's far better than it randomly going back to some years in the past, so timers don't fire at all.
It would cost a lot more to replace the actuator than to reset the time or to have the time set via NTP. I'm going back to NTP and hope for the best.
I installed the TNAP 4.1 test image today. I have switched my Mio+ to standby to see if it keeps accurate time. So far it's good.
Sent from my SM-G950W using Tapatalk
IF it starts going random time again while using Standby mode, then try a test of leaving the receiver ON all the time, and see if it holds NTP time then. Let us know.
The time quickly went wrong when I switched off the receiver. So I reconfigured the receiver to only use Internet for a reference instead of Internet/transponder. The receiver is keeping good time while switched on. But I'll turn it off overnight and see how it does.
Sent from my SM-G950W using Tapatalk
I installed 4.1 on one of my mios but there isn't an option for "System time" anymore. In other words, there's no way to sync the time. There was a plugin for systemtime but the box wouldn't let me install it - error message was that there was already a systemtime plugin installed. I couldn't find that systemtime plugin so I wasn't able to remove it.
cyberham If that's true, then how is Cyberham using it, because he also installed it, and said he changed his clock settings...
Also, you DID read that I said those TNAP 4.1 were test images, correct?
There is no longer a System Time menu. In Setup>System>Customize, there is a Time synchronization method parameter where you can choose Auto, Transponder Time or Internet (NTP). You can also set the NTP hostname. So if the time goes wrong, you must restart the receiver to get a time update.
Latest here is the clock went wrong again. When I turned on the receiver, the date was December 31, 1969. So for now, I am going to leave the receiver turned on continuously.
Latest here is the clock went wrong again. When I turned on the receiver, the date was December 31, 1969. So for now, I am going to leave the receiver turned on continuously.
Yes I know it's a test image. I'm just reporting what I found.
There's no SYNC button, or sync at a time interval? That sucks, because that means you'd have to reboot to grab time, or wait for it to sync itself whenever.
Let's clarify something. I read some are turning the receiver off cold. Not on standby. I don't use TNAP. But....
El Bandido over on Legit has stated the real time clock (RTC) has no battery backup. Or super capacitor if that be the case.
So. If you divorce the receiver from power, it has to lose set time/date. On standby it shouldn't.
It's not an image thing. It is the design of the electronics in the receiver. No provision for or a not installed RTC power source. The image I use will lose time and date if left off over night. On standby it doesn't. And fyi I always use ntp and not tp as the time source.
Looking into problems of using ntp you may want to delve into your router setting too. That would be up to your particular router or firmware. Some have issues with allowing udp port 123 (ntp) traffic. Might be worth looking into.
El Bandido over on Legit has stated the real time clock (RTC) has no battery backup. Or super capacitor if that be the case.
So. If you divorce the receiver from power, it has to lose set time/date. On standby it shouldn't.
It's not an image thing. It is the design of the electronics in the receiver. No provision for or a not installed RTC power source. The image I use will lose time and date if left off over night. On standby it doesn't. And fyi I always use ntp and not tp as the time source.
Looking into problems of using ntp you may want to delve into your router setting too. That would be up to your particular router or firmware. Some have issues with allowing udp port 123 (ntp) traffic. Might be worth looking into.
I went with PurE2 6.5, because I liked the clean, responsive default skin and the built-in options to set up many different types of network shares. So far the time hasn't bugged out and the wifi has stayed up. (I can't prove that my wifi issue isn't a hardware issue, but it seems terribly suspicious that it's only gone out with one software family yet.) The only thing I miss from TNAP is the mapping of the blind scan to the blue button and the channel selection to the green button, but I'm assuming they can be changed, I just haven't had time to look into it yet.
El Bandido has explained you must edit your Settings file to remove any old references to SystemTime. See his comment on legitfta. One user has tried and it has solved the time accuracy issue. I have these old references in my Settings file so I will edit and try the clock again.
Too busy right now with the Olympics closing ceremony about to begin.
Too busy right now with the Olympics closing ceremony about to begin.
Last edited:
I keep my Mio in Standby when not in use. NEVER shut it off, and when set to NTP time, it does NOT keep time anymore. The front screen is in my full view while sitting on my living room chair, and I can SEE the clock suddenly wander off to some random time, whenever it pleases. I finally gave up on NTP time, and changed to transponder time and use Bar's & Tone on 99w as a Startup service. That's slow by about 4 seconds, but NEVER varies to random times and dates like NTP does.
My router is fine. The Mio USE to work perfect for well over a year +, at least with the original TNAP. Then came the updates, and it started going bad.
Similar threads
Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)
Who Read This Thread (Total Members: 4)
Latest posts
-
-
Scripps News shutting down OTA 'after' November 15th- Latest: comfortably_numb
-
-