Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[ViX_Misc] Timer issue sending me round the bend!!

Piranha

Member
Joined
Mar 18, 2014
Messages
161
Reaction score
0
Points
16
Age
72
Location
West Midlands
Apologies for starting a new thread on this - but having replied to my own initial thread, not sure if anyone would see that I have added a debug log showing the point at which the time settings go to rats¥$t!!
It appears that the receiver time and the transponder time difference occasionally calculates as just over TEN YEARS, which then makes all my timer recordings jump forward in time by the same amount! My wife's favourite soaps might not be running still in 2025!

I have flashed, re-flashed time and again, installed latest TMTWIN bootloader, re-flashed, never restoring settings. Re-enetered the beloved soaps timers and Lo! this little gremlin comes along and sets all of my timers to the year 2025 - an increase of exactly the same amount per timer of course - about 10.18 years!!!

This happens on BOTH my TMTWIN boxes, which were running sweetly until a couple of weeks ago (quite frankly, don't remember which was the last image that worked OK, as I tend to keep up to date with new builds. That said, I am getting the feeling that this is not a Vix or config issue (I have nothing to prove that BTW!). However, as nobody else seems to reporting a similar issue on here and having spoken to Technomate (they think it's an image or Config issue - surprise! Surprise!) I am now going crazy trying to resolve this issue so that my wife can watch her beloved recorded soaps without having to wait until 2025 (or perhaps never, as it seems likely that the timers will continue to jump ahead by ten years and a bit everything the system time is updated by the GREMLIN!!!

I will worship any OpenVix genius who helps me figure out WTF is happening with my boxes!!!!

This is the link to my posts (admins please accept my apologies if this is a poor way of doing this!)

http://www.world-of-satellite.com/showthread.php?41502-Timer-corruption
 
Thank you Sicilian!

I can only hope that Technomate will take notice of your notification, as they just informed me that it was definitely an image issue! To have the identical issue on two boxes does point towards me having done something to corrupt the system timer, but then everyone else flashes new images regularly and installs plugins too!

Many thanks for taking the time to look into this for me - as you can imagine, it is very frustrating!
 
Typical technomate response to blame the image instead of looking into their own failings.

Sent from my SM-G900F using Tapatalk
 
Typical technomate response to blame the image instead of looking into their own failings.

Sent from my SM-G900F using Tapatalk

Things is, being speaking direct with the koreans and they're looking into fixing this. So strange report, really want to know where it come from.
 
Things is, being speaking direct with the koreans and they're looking into fixing this. So strange report, really want to know where it come from.

One word springs to mind, starts with rich ends in turd.


Sent from my iPad Air using Tapatalk
 
More logged visits by the EventTimerHandler gremlin!!

Np problems for a couple of days, then all timer recordings on one box jumped forward to the year 2025 - again! Doubt it will help, but have had a look through the logs and found the same issue - a Linux time update which finds a 10 year plus difference between RTC and receiver time and updates the timers accordingly!!!
Can't understand why this issue isnt happening on other TMTwins too! Hope the Korean guys can figure it out and suggest some method of me re-installing drivers that will flush this little sod out once and for all.
 

Attachments

No sign of this particular gremlin since updating to Apollo 077 - updated to 080 today so fingers crossed!
If it's now gone, don't care what it was!
 

OpenViX Feeds Status

Back
Top