7216 settop box ISSUE confirmed by Verizon!
Jeff1512
Enthusiast - Level 3

I have a QIP 7216 settop box connected to the TV via component cables (not HDMI).  Sometimes when I turn the settop on, i get audio, but the video is all black.... If i power the box off, then on again, it's fixed.  If I change channels, it's fixed.... Anyone else experience this?

UPDATE:  Verizon has confirmed this to be a known issue w/ the 7000 series and 1.6.2.   I'm curious how many others have seen this issue as it does not happen all the time.

0 Likes
Re: 7216 settop box ISSUE confirmed by Verizon!
psumatt1
Contributor - Level 2

Jeff-

I've never experienced this. (and have the same setup) Sounds odd..

0 Likes
Re: 7216 settop box ISSUE confirmed by Verizon!
retiredme
Specialist - Level 1
Last night I experienced an odd glitch. The 7216 DVR was recording a recurring program and I was watching live a different channel. At 9:45 PM EDT, the live channel lost lock and I received a different "Currently Unavailable" message than previously seen. I could not change channels up or down to re-establish channel connection, but kept getting the "Channel Unavailable" message. About this time, I noticed that the red "recording in progress" light had extinguished and I was losing my desired recording.  I powered off the 7216 and repowered. It seemed to work OK, so I manually re-established the recorder to capture the remaining minutes of my scheduled recording (I now have two segments, one large and one small, for the show with a gap of a few minutes). This is the first glitch since upgrading to 1.6.2 that I have noticed. I do not recall that my hand was near the remote, so I do not think I triggered the event accidentally. Besides, what would cause simultaneous loss of signal and recorder stoppage? I will chalk this up to random electrons/bad karma and monitor the situation for any reocurrance. Thank you.
0 Likes
Re: 7216 settop box ISSUE confirmed by Verizon!
Joe01880
Contributor - Level 1
"Currently Unavailable" on channels is a known issue with the 7216 HD DVR. Upgrade 1.6.2 has been reported to fix this issue. An alternative would be to exchange the 7216 for a 6416 HD DVR which has not had that problem in the past.
0 Likes