TV Online Attempting To Update Today - Parsing Error

[Ryu]

I used hardwire no help

[crazed 9.6]

Just turned it on now and have same error on the avov vixo1

But after exiting that error message, IPTV does still work.

[Falcon05]

Useing a google public DNS thru your router may work.
Or if using wifi from aVoV to router, try the hard line instead.

I've had these phrasing errors also and never really found a way to fix it.
But try the above, it may help

I've always used 8.8.8.8 as primary and 8.8.8.4 as secondary DNS addresses for both IKS and IPTV.
I also always hardwire to any device used for video apps. In the old days, I'd throw a datascope
on the line and watch the datastream. But those were the days of 3270 bisync and 9.6kb circuits. LOL

[crazed 9.6]

yea that public DNS worked awhile back with the avov, when it was showing every channel as 'Temporary Not Available' message (it was every channel that showed that and not just a few, and that DNS worked to fix that)
But doesn't work for this phrasing error. Didn't work last time if I remember
But last time I could not use the IPTV TVOnline app till that error was fixed.
This time I can and am... But one thing that I did this time with this avov, was last used it was not exited outta the TVOnline APP and left in stand by with the RCU.
So it never was exited outta that APP, and even thou I can't update the new update now, the IPTV TVOnline still works.


I did see that the new Update said it was for to fix channel connection issues.

[4wheelin]

i just got update message again and downloaded it

[BIO]

I was just told that they are working on some TVonline updates for TVonline stb and VIXO 1. Guess the parsing errors and such are related.

[theuduk]

Avov just updated tvonline to 1.47, some get it some do not at this time.

[Dazed_Again]

I was just told that they are working on some TVonline updates for TVonline stb and VIXO 1. Guess the parsing errors and such are related.

Confirmed, Its now working fine

[BIO]

Confirmed, Its now working fine

I was just told the same thing, looks like the update is fixed now. Don't have a minute right now to check it out but will do that tonight

[Falcon05]

Both of my Avov boxes are now running on 1.47. Thanks to the Avov team for getting the issue corrected so quickly! Channels seem to change from one to another a bit faster than under 1.45.