Separate names with a comma.
Discussion in 'Hopper System Support Forum' started by 3HaloODST, Jul 20, 2012.
Didn't for me .
S217/S268 7/21/2012 2:54AM.
Kitchen Joey is active, linked to the Den Hopper with a show about 10 minutes behind (on the kitchen Joey). Screen freezes, audio continues. Pause clears the condition but goes to live TV. Not good.
Cold reboot is the cure.
Isn't it always :hurah: .
Based on my experience with the last release before this one, I've been cold booting everything in the AM after I notice the upgrade. So... the freeze up occurred after the cold reboot. Either way--pause then pay or cold reboot--you lose what you're watching. Unacceptable repair. Also my friendly little rectangles that I photographed and posted in another thread are back. This time there are two of them.
Your DVR is something. Perhaps unique in some chip's parameters.
Twice now I was watching a show on the 2nd hopper and I hit search. I cancel out of the search and the show remained in a little box in the left hand top corner with the rest of the screen black. The unit became completely unresponsive and needed resetting.
Do you have S2.17 software version for your Hopper? If this continues, please PM me your receiver number with further details so I can submit a trouble report to our engineers to find a resolution to the issue. Please let me know. Thanks.
I am on S2.17, I haven't tried it again this morning because I have too much sport going on.
I will try it again soon.
My Joey no longer sees my Home Network since this update. I use Tversity and my Hopper sees my videos/music/pictures just fine. My Joey also did see it before this update. When I run the network setup on the Joey, if fails, even though there are packets incrementing (RX/TX). I did a red button reset on the Hopper and unplugged the Joey, but it still doesn't connect. Also, I'm not sure if this is related, but I downloaded a program "On Demand" on the Hopper, but when I try to play it back, it's just a black screen. Am I missing something or is this a bug in S2.17?
I'll agree with that. The Den Hopper is really something else unique and likely failing is some way that is intermittent, yet doesn't cause the unit to crap out. Too early to call Dish on it though, as the situation is hard if not impossible to reproduce in a timely fashion. One of my rectangular friends is back.
217 has had a good affect on my setup!
213 totally screwed things up. Weeks of Joey freezing and searching for the Hopper.
This update has actually solved that problem completely! I'm glad they're on top of their equipment!...at least in my case (after countless hours with Hopper support after the 213 debacle...) I'm loving 217! Obviously everyone's box and setup responds differently to different updates. For the first time in a LONG time, things are back to normal here!
It's S2.16 or S2.17 or S2.22. Isn't hard to recognize ?
What? Is there a S222 rolling out?
Someone elsewhere mentioned supposedly there will be a S218.
My head is starting to swim.
Well, if you want to be technical like that, right now my Hopper is showing me S217 on the System Info screen -- no "."'s.
Sounds like you may need to re-enable bridging on the hopper:
Yellow Hot Key
Select MoCA from drop down
Blue Hot Key twice.
It's always been in that format for System Info, but official naming (if yo remember that SW page on E* and dish's sites) still the same L2.11 or S2.14 or M1.05, etc.
So, your bickering missed a target and return back as a boomerang.
Thank you, that did it
New problem that came up after this update: My HD space went from 3% used to 17% used from Friday night to Saturday morning. I watched or deleted everything by Sunday afternoon, but it only dropped down to 16% used with ZERO recordings. Today, after recording about 5 hours last night, it's at 17% used again. Right now it shows Total Space Avail: 1231 GB, Free Space: 1035 GB and I have 3.5 hours stored on it. I have tried both a red button reset and unplugging for 30 seconds, no change. That doesn't seem right, does it? I called tech support and was told that it "sometimes" takes 24 to 48 hours to update. I find that extremely hard to believe, but it will be 48 hours tomorrow, so will see. I hesitate to do a factory reset, but would that fix the problem?
Hardly. My point was that you keep trying to correct people on an extremely minor point while most people who even look at the version number are going to be going by what their display is telling them.