Thank you for your feedback concerning HDMI-CEC on the Hopper & Joey platform!
DISH has been listening to your feedback and I am please to report...
@ScottGreczkowski:
Hopefully Dish will fix this right and either go back to the prior way which most of us loved or drastically shorten the delay and fix the issue below. Here's another problem with their latest tweaking of the HDMI connection that they need to correct:
Common scenario, you use the remote's TV power button because you want to turn off the TV
and Hopper. But your spouse (or yourself) says "hey, I wanted to hear that story..." or whatever. So now they set that long Hopper off delay and the Hopper stays on for 5 minutes and lucky for you because you can press the TV power button again and the TV comes back on with the Hopper still in all its glory and life goes on. Buffer and all. Or does it...
If you do this, then after those 4-5 minutes
the Hopper still shuts itself off. Right in the middle of what you are watching. I tested this last night because I was playing around with the TV off option to see how it works. When I was done I wanted to watch a little more TV and shortly after I started up a recording the Hopper dozed off. I thought that maybe if you use the TV power off then back on again that if you
did not change a channel or something that of course the Hopper would think you really did want to shut it off and turned itself off. So I did the TV off/on again but changed channels on the Hopper a few times, looked at my recordings, thinking that 'logically' the Hopper would detect user activity and cancel the auto off countdown. Nope. Shuts down anyway and you lose whatever buffer you had.
So what's the point of the delayed off of the Hopper if there is no way to stop the inevitable off sequence? You wanted to not lose the current TV buffer for an accidental TV off button press with HDMI-CEC enabled so you can quickly turn the TV back on and not lose anything but Dish "testers" did not even think about different scenarios like this?
I guess I just don't get how Dish engineers and employees are managed by their leadership to let a lot of these little problems like this slip through the cracks. Do they even use their equipment and
try to break it to ensure their customers are getting as close to a rock solid release as possible?? I really think their User Acceptance Testing consists of a basic check-off only approach.
Premise: Hey, let's delay turning off the Hopper. Did users really ask for this?
Not really, but gives us something to do and put on our yearly performance reviews. Oh, OK.
Design: Delayed turn off.
UAT: Did it delay turn off?
Result: Yes. Now let it rip to users as S330.