I should clarify here quickly.... maybe I had "nightly" reboots, or maybe it just seemed that way at the time. Since I've started keeping a closer watch on this, I think that what I am experiencing is probably in line with the so-called "72 hour rule". I still consider that a "glitch" though, even if it's "only" every 3 days. No warning, just BOOM! Screen goes dark for several minutes with no indication of what is going on. But I typically am watching TV every night from late evening until 3 or so in the morning. And so many series-recordings are happening in the background, the hours of which I am not totally aware of. So for whatever reason, DISH has decided that "people like me" just have to grin-and-bear-it. Unfortunately, I don't think this is really a bug, but just the way the system operates. I've been keeping a written log since Sunday, so I'll see what happens this week. Thanks tho
The real question is why does dish want to reboot the system every night. .. I only reboot my phone or pc when it starts acting up.I should clarify here quickly.... maybe I had "nightly" reboots, or maybe it just seemed that way at the time. Since I've started keeping a closer watch on this, I think that what I am experiencing is probably in line with the so-called "72 hour rule". I still consider that a "glitch" though, even if it's "only" every 3 days. No warning, just BOOM! Screen goes dark for several minutes with no indication of what is going on. But I typically am watching TV every night from late evening until 3 or so in the morning. And so many series-recordings are happening in the background, the hours of which I am not totally aware of. So for whatever reason, DISH has decided that "people like me" just have to grin-and-bear-it. Unfortunately, I don't think this is really a bug, but just the way the system operates. I've been keeping a written log since Sunday, so I'll see what happens this week. Thanks tho
It all started with the 921, they had so many bugs with that system that they decided to do a nightly reboot to start each day out fresh. It did actually help that POS work better so DISH just decided to keep the practice of a daily reboot on every system since rather than write better code.
Seems like making that reboot time a configurable option could solve so many problems. Can it be that difficult? Or do you think there is a reason that they don't want to do so?
I have recently noticed my HWSs are missing recordings the next morning that the timers were set to fire in the 1 to 2 AM time. These 1 AM timers were due to conflicts during the normal program time. I have started moving some timers around to other Hoppers so this won't happen anymore. I will be so glad to go to Hopper 3 someday to get around the conflicts.
In all of these discussions about the reboots, there is something that I don't think I've seen addressed yet: why exactly is a nightly reboot needed in the first place? I can understand rebooting for new software. Guide updates are done "on the fly". But why a nightly reboot?
I'm guessing that is something specific to the HWS? I've never seen any kind of "counters" on the H3 - unless they are there and I'm just not seeing them?
there is a "history" page now, that shows "notifications" and "resets" for all receivers ... maybe that took the place of counters. Otherwise they are very well hidden. I think you are probably right though.. Anyway, hopefully someone else with a HWS can answer your question.
