 QuaffAPintA Big Thanks To The Troops
join:2001-01-10
Downingtown, PA
 ·Verizon FiOS
| reply to MacAlert
Re: [DVR] 7232 Slow, Unrepsonsive Until Warms Up or a Reboot said by MacAlert:Is it just me or has it gotten worse in the last couple of days. It seems every channel change is lagging now.
Yea, lag and I've had the dvr lock up hard more than once. I have to unplug and replug it in to get it responsive again.
--
{Send Secure Notes Free and Easily} :: whisperBot.com |
|
|
|
1 edit | reply to djoropallo
Is it just me or has it gotten worse in the last couple of days. It seems every channel change is lagging now. |
|
 amarryatVerizon FiOS
join:2005-05-02
Marshfield, MA
·Verizon FiOS
| reply to billhere
That's crazy. That is beyond patience. It took one day to break, and will end up taking months to fix. It's extremely annoying. What they need to do is undo what they did so that we don't have to suffer, and get their updates working properly in a test environment before re-deploying. |
|
1 edit | reply to PJL
said by PJL:We will be deploying a software fix on all your set top boxes between November 26 to January 7 across all FIOS markets which should resolve this issue fully. Thanks for your patience.
Travis S.
Verizon Telecom Social Media Team .....
November 26 to start fixing this issue and January 7 to finish?  I'm not sure I have that much patience!
The problem is indeed intermittent although I've noticed it three times (edited from twice) in the last couple of days. |
|
| reply to PJL
said by PJL:Verizon knows what the problem is and are field testing the fix. Thanks for the update! |
|
| reply to PJL
The debate only starts when you give "information" which doesn't address actual occurrences of the problem.
I've been through numerous instances managing complex system design and implementation where someone stated he/she knew what the problem was only to find out they had not a clue as to the true underlying cause.
In your case I am skeptical since the stated problem doesn't square with some of the observed problem occurrences. Given the numerous Verizon software malfunctions over the years it's difficult for me and a lot of others to believe anything they say particularly when no deployment schedule is presented.
Sorry if this well founded skepticism offends you. |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| reply to ronsc1985
said by ronsc1985 
It matters since if you really don't know what the problem is it is impossible to fix it completely. Currently there apparently is no fix as I still get the same results.
...
[/BQUOTE : Verizon knows what the problem is and are field testing the fix. You get the same results because it has not been deployed to you.
The debate ends for me (again). It's tough when you give information that might give people the hope that this problem will actually get fixed (which is all I was trying to do) and a debate begins on what you said. |
|
| reply to PJL
said by PJL:said by ronsc1985:Actually is wasn't. The previous channels were also premium channels in several occurrences.
The second tuner may have still been on a non-premium which can occur when you flip channels. That said, it really does not matter what the cause is. All that matters is that it is fixed. It matters since if you really don't know what the problem is it is impossible to fix it completely. Currently there apparently is no fix as I still get the same results.
BTW in at least two instances I was recording another premium channel. |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| reply to ronsc1985
said by ronsc1985:Actually is wasn't. The previous channels were also premium channels in several occurrences.
The second tuner may have still been on a non-premium which can occur when you flip channels. That said, it really does not matter what the cause is. All that matters is that it is fixed. |
|
| reply to PJL
Actually is wasn't. The previous channels were also premium channels in several occurrences. |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| reply to ronsc1985
said by ronsc1985:Has anyone seen any improvement lately? In my case I still get the channel change freezes. The previous post about the cause is highly suspect since:
A. what makes the bit rate of HD ads any higher then HD normal programing broadcasts.
B. I have experienced this on channels with no advertising i.e. Showtime, Starz and Max plus several non HD channels.
It is related to buffering. Reecall that when you are watching a premium channel the second tuner may still be tuned to a non-premium channel. |
|
| reply to djoropallo
Has anyone seen any improvement lately? In my case I still get the channel change freezes. The previous post about the cause is highly suspect since:
A. what makes the bit rate of HD ads any higher then HD normal programing broadcasts.
B. I have experienced this on channels with no advertising i.e. Showtime, Starz and Max plus several non HD channels. |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| reply to ronsc1985
said by ronsc1985:...
I would remind everyone the correlation doesn't imply causality. Just because problems coincide with some event doesn't in and of itself show the event is the cause.
Well I thought I had posted my last on this topic, but I just received some important information. I've been told that it is indeed a problem with the recent implementation of the HD locally-inserted advertisements in channel feeds and the resulting impact of the larger data and bitrates on functions in the STB firmware itself, not IMG 1.9.1. A fix is being field tested for deployment. |
|
| reply to ronsc1985
said by ronsc1985:Yes except there have been no other hypothesis that I am aware of that caused the current problem. Occam's razor requires multiple explanations from which to choose.
Some have blamed version 1.9.1 of the DVR firmware. The bad assumption you have to make for this theory is that 1.9.1 worked fine for 4 - 6 weeks before this issue arose. |
|
| reply to djoropallo
Glad they are working on something. No better here. happens more often than even although maybe slightly less long between pauses. |
|
| reply to ronsc1985
said by ronsc1985:I also doubt they know what the problem is. If they did they could fix it pronto.
Um, this is Verizon...there is no such thing as "pronto" |
|
| reply to PJL
Yes except there have been no other hypothesis that I am aware of that caused the current problem. Occam's razor requires multiple explanations from which to choose. |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| reply to ronsc1985
said by ronsc1985:My assumption is spot on. You assume I meant the STB exclusively. They changed something and the system took a dump.
It's simple go back to where you were and fix the problem software/firmware wherever it is located before redeploying.
This isn't complicated you take care of your customers first. No customers no ad revenue no matter what "ad deployment system" you are using.
I also doubt they know what the problem is. If they did they could fix it pronto.
I've heard similar stories for many years when problems cropped up. Someone always has a reason but when asked to fix it they stall because the reality is they don't really understand the problem in the first instance.
I would remind everyone the correlation doesn't imply causality. Just because problems coincide with some event doesn't in and of itself show the event is the cause.
I now understand you -- you're speaking of the big "System" meaning the STB, the backend servers, etc., so you're correct, they changed something and (I would add) the STB funtionality took a dump (to use your words). And I fully agree with your words that going back is a simple fix. But a big company always trades many factors -- like add revenue and ticking off the advertisers versus customer subscription revenue and "temporarily" ticking off the end-user customer.
I also agree with you that "I would remind everyone the correlation doesn't imply causality. Just because problems coincide with some event doesn't in and of itself show the event is the cause." But in this case I would apply Occam's Razor: that among competing hypotheses, the one which makes the fewest assumptions should be selected.
This is my last reply on this topic.  |
|
| reply to PJL
My assumption is spot on. You assume I meant the STB exclusively. They changed something and the system took a dump.
It's simple go back to where you were and fix the problem software/firmware wherever it is located before redeploying.
This isn't complicated you take care of your customers first. No customers no ad revenue no matter what "ad deployment system" you are using.
I also doubt they know what the problem is. If they did they could fix it pronto.
I've heard similar stories for many years when problems cropped up. Someone always has a reason but when asked to fix it they stall because the reality is they don't really understand the problem in the first instance.
I would remind everyone the correlation doesn't imply causality. Just because problems coincide with some event doesn't in and of itself show the event is the cause. |
|
PJL
join:2008-07-24
Long Beach, CA
kudos:2 Reviews:
·Verizon FiOS
| reply to justin9876
justin9876 They do know what is wrong. And they are working on fixing it. And for me at least, as I posted yesterday, my DVR is now working much better than it has been for several months. So it should get somewhat better in the next week or two, and be fully fixed for everybody by around the end of the year (Verizon never updates their entire network at once, for good or bad, they always do a portion of their network at a time).
Justin, see my above post to ronsc1985. I agree that "they do know what is wrong. And they are working on fixing it." But they could fix it IMMEDIATELY by turning off the "new add deployement system" that broke things. But they won't because it would cost them ad revenue. |
|
