"Currently Unavailable " and No Audio on various channels
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Verizon FIOS
I am absolutely amazed that literally 1000's of customers are experiencing the same ongoing issues.
I have the (3) 6416-2 DVR's with the1.6.1 release but I still get to reboot every couple of days.
Call CS which I have done a few times since Sept 2008 and they do a system reboot which doesn't provide any longer fix than if I reboot from home
I am asked to disconnect this and jiggle that.When I have a problem I get to become a Verizon Diagnostic Tech. I am told or it is inferred that the lack of reliable service or the failures are somehow related to my non Verizon
cable connections
All this and Oh Yeah I get to write you a check every month.
Thanks Verizon .........thanks for doing business with me
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have also been getting Currently Unavailable lately very randomly. It's very annoying, sometimes 4 or 5 channels in a row. Sometimes comes up after watching a channel for 10 or 20 seconds. Is it something I did?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My CUrrently Available" problem is on the PBS channels (23,24,523, adn two otehrs I do nto have with me now, and also on 513.
My response fromtechincal non-support as been similar to reset everything. Thten works for ten minutes ot a day then returns. Of cousrse the big problem is when you programmed to record something you really want, and then come back and find two recording of 7 or 8 seconds each becasue the siganl was Currently Available.
Very tempted to call Cmcast and then Verixon will lose more than FiosTV cusotmer as my internet will go too.
Anyone get any real service?
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@DMZ wrote:
If there's the old R9 coax in your home that cable companies used back in the old days, it MUST be replaced with R6 coax that has the thicker middle insulator.
Although this might be true, I can assure you that wiring or a defecttive coax-box CAN'T be the reason for this problem. All was working fine a week ago and guess what - I'm still using the same wiring. I do not understand howsomebody can even suggest that wiring could be the cause for this issue when the problem pops up virtually everywhere..
I'm having this problem as well and if a nationwide problem occurs over the last few weeks AND I didn't change ANY of my hardware and everything was working fine before, why MUST I suddenly replace my coax?? Makes no sense to me..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you have RG59 COAX, it is not supported plain and simple. Even if it was not a problem last week and something did change. RG59 will not handle the higher frequencies of FIOS. MOCA running at 1050mhz for the IP portion of FIOS should not be run over older RG59 COAX. If you do not have the older COAX then I would say it's not the issue.
@FloridaFiOS wrote:
@DMZ wrote:
If there's the old R9 coax in your home that cable companies used back in the old days, it MUST be replaced with R6 coax that has the thicker middle insulator.Although this might be true, I can assure you that wiring or a defecttive coax-box CAN'T be the reason for this problem. All was working fine a week ago and guess what - I'm still using the same wiring. I do not understand howsomebody can even suggest that wiring could be the cause for this issue when the problem pops up virtually everywhere..
I'm having this problem as well and if a nationwide problem occurs over the last few weeks AND I didn't change ANY of my hardware and everything was working fine before, why MUST I suddenly replace my coax?? Makes no sense to me..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@prisaz wrote:If you have RG59 COAX, it is not supported plain and simple. Even if it was not a problem last week and something did change. RG59 will not handle the higher frequencies of FIOS. MOCA running at 1050mhz for the IP portion of FIOS should not be run over older RG59 COAX. If you do not have the older COAX then I would say it's not the issue.
@FloridaFiOS wrote:
@DMZ wrote:
If there's the old R9 coax in your home that cable companies used back in the old days, it MUST be replaced with R6 coax that has the thicker middle insulator.Although this might be true, I can assure you that wiring or a defecttive coax-box CAN'T be the reason for this problem. All was working fine a week ago and guess what - I'm still using the same wiring. I do not understand howsomebody can even suggest that wiring could be the cause for this issue when the problem pops up virtually everywhere..
I'm having this problem as well and if a nationwide problem occurs over the last few weeks AND I didn't change ANY of my hardware and everything was working fine before, why MUST I suddenly replace my coax?? Makes no sense to me..
Again, look at all the various complaints. I highly doubt all these members suddenly moved or switched to older Coax. BTW, I already used FIOS last week..(;. In addition, my system is NOT set to MOCA.
While your information is highly appreciated, it's obvious that this is a software-issue caused by 1.6.1 and will probably fixed with 1.6.2.
It just doesn't make sense to advise other members to have their wires changed to solve the problem although the software from VZ is messed up. Also, "plain and simple"..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@golfdude wrote:
So, what is the fix? Unplug the STB, drink a cup of coffee, plug the STB back in, and this new software will be installed?
No, the new software is rolled out by VZ based on your region. I, in the Florida area, probably have to wait for several weeks to have that fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@FloridaFiOS wrote:While your information is highly appreciated, it's obvious that this is a software-issue caused by 1.6.1 and will probably fixed with 1.6.2.
That comment is scary as I have the problem on 1.6.0 and was hoping that 1.6.1 would help. Now does this mean i will haveto wait another decade?
As to the cable issue, my house is new one year, with all new cables (RG6 and Cat-5e). - SO NO CABLE PROBLEM
Problem occurs on HD/DVR box, not SD box.
I have tried changing from HDMI cables between my "cable box" and the AV receiver. Still have HDMI cable between AV receiver and TV. Did not fix problem. To change the receiver to TV cable woudl mean removing the TV form the wall. Tell me this is not necessary. I won;t do it unless I have high probabliity of fixingthe problem.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@SteveK wrote:
@FloridaFiOS wrote:While your information is highly appreciated, it's obvious that this is a software-issue caused by 1.6.1 and will probably fixed with 1.6.2.That comment is scary as I have the problem on 1.6.0 and was hoping that 1.6.1 would help. Now does this mean i will haveto wait another decade?
As to the cable issue, my house is new one year, with all new cables (RG6 and Cat-5e). - SO NO CABLE PROBLEM
Problem occurs on HD/DVR box, not SD box.
I have tried changing from HDMI cables between my "cable box" and the AV receiver. Still have HDMI cable between AV receiver and TV. Did not fix problem. To change the receiver to TV cable woudl mean removing the TV form the wall. Tell me this is not necessary. I won;t do it unless I have high probabliity of fixingthe problem.
Steve
You're obviously understanding what I'm trying to say. There is NO NEED to fix any hardware like wires, receivers etc. if the KNOWN ISSUE is the software! Changing hardware or other settings might even make things worse!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content