Netflix broken in 309 on H3?

[mloebl]

Got 309 today, and Netflix hangs when it starts up on a black screen. Family not happy 1080P so no 4k here. Have to hard cycle the receiver to get it to come back. Anyone else?

 

[reynoltd]

Same was happening to me but now seems to work


Sent from my iPhone using SatelliteGuys mobile app

 

[Bobby]

Working fine for me...

 

[mloebl]

No luck here. It looks like it's a detection issue. It fires up to detect HDMI capabilities, not seeing HDCP 2.2 and it's failing. I tried disabling the surround receiver in line, but still failing on the TV too.

EDIT: Just to be clear, it looks like when the Netflix app starts, it tries to detect HDMI capabilities as resolution of screen will change. I see the Netflix logo, it does this detection, then fails. If I check my surround receiver, it's complaining that it's trying to use HDCP 2.2 on the TV that currently doesn't support it. If I shut off the receiver, it gets a bit farther, but just fails on a black screen.

 

[drwatson618]

In order to run 4K, you need to use an input that supports HDCP 2.2. If you don't have one, you'll have to change your resolution to 1080.

 

[mloebl]

Just to be clear, I don't have a 4k TV but 1080p however the Netflix app seems to be trying to force hdcp 2.2

 

[drwatson618]

Odd. Dumb question, have you tried using a different HDMI cable?

 

[mloebl]

I'll try a different cable tomorrow, its not a bad idea. Also know that my Onkyo surround receiver is HDCP 2.2 capable but my TV is not. Wonder if the app is misreading the surround receiver HDCP capabilities and not working correctly.

 

[david_jr]

Try connecting direct to TV to see if it makes a difference.

 

[lparsons21]

I'll try a different cable tomorrow, its not a bad idea. Also know that my Onkyo surround receiver is HDCP 2.2 capable but my TV is not. Wonder if the app is misreading the surround receiver HDCP capabilities and not working correctly.

Everything in the chain has to be HDCP 2.2 capable. If the TV isn't, 4K isn't going to work.

 

[DVKCal]

You should read what the OP said, he isn't trying to watch 4K.

I am having the EXACT same problem. This has nothing to do with us trying to watch 4K, we aren't even selecting any video, the Hopper demands HDCP 2.2 when we launch Netflix and crashes the box immediately when it doesn't detect HDCP 2.2.

I suspect the OP is like me and has a Netflix account with 4 streams, which also allows for viewing 4K, even though we aren't viewing it. For people on 4 stream packages, it is suppose to check for HDCP 2.2 and if it doesn't detect it, then hides 4K content, instead it crashes the box if it doesn't detect HDCP 2.2. This is a major issue for me.

 

[PinGorilla]

Just tried launching Netflix and I get a message after the Netflix splash page "This content can not be displayed because your TV does not support HDCP 2.2.". This is some bulljunk.

My H3 input goes into a brand new Denon HDCP 2.2 compliant receiver and out to my TV. My TV is an older Samsung LCD 720p/1080i 60hz.

Guess I will do my part and contact Dish to report it.

 

[spoiler1041]

Just tried launching Netflix and I get a message after the Netflix splash page "This content can not be displayed because your TV does not support HDCP 2.2.". This is some bulljunk.

My H3 input goes into a brand new Denon HDCP 2.2 compliant receiver and out to my TV. My TV is an older Samsung LCD 720p/1080i 60hz.

Guess I will do my part and contact Dish to report it.

Just out of curiosity, do you pay for the 4 stream uhd netflix service?

 

[mloebl]

Just tried launching Netflix and I get a message after the Netflix splash page "This content can not be displayed because your TV does not support HDCP 2.2.". This is some bulljunk.

My H3 input goes into a brand new Denon HDCP 2.2 compliant receiver and out to my TV. My TV is an older Samsung LCD 720p/1080i 60hz.

Guess I will do my part and contact Dish to report it.

Bingo that's exactly the deal here. It's a brand new Onyko receiver that's HDCP 2.2 compliant while my Samsung TV is a few years old so it's not. I don't have the 4 stream Netflix but their 2, so that's why I suspect it's a detection issue from the Netflix app. I'll try to log something with dish today as well. I also did try setting the hopper to 720p but didn't make a difference.

 

[PinGorilla]

I have the 9.99/month plan. 2 screens in HD. I do not have 4K content plan.

 

[drwatson618]

Bingo that's exactly the deal here. It's a brand new Onyko receiver that's HDCP 2.2 compliant while my Samsung TV is a few years old so it's not. I don't have the 4 stream Netflix but their 2, so that's why I suspect it's a detection issue from the Netflix app. I'll try to log something with dish today as well. I also did try setting the hopper to 720p but didn't make a difference.

What Onkyo do you have? I have the 646 and only the first three inputs are HDCP 2.2. You could try a different input and see if that helps.

 

[mloebl]

What Onkyo do you have? I have the 646 and only the first three inputs are HDCP 2.2. You could try a different input and see if that helps.

It's the RZ900, I'll take a look and see, that's a great idea!

 

[drwatson618]

On the RZ900 input 6 and 7 are not HDCP 2.2.

 

[mloebl]

On the RZ900 input 6 and 7 are not HDCP 2.2.

Thanks! Switched to Input 7 and Netflix (and the family) all happy again...

 

[spoiler1041]

Thanks! Switched to Input 7 and Netflix (and the family) all happy again...

So that's what they mean about 2.2 not being backwards compatibile. Can't be...