As I said above, a 3:30 reboot could really effect people in the Pacfic time zone. If they wanted to watch any program that started at 6:30 in the eastern time zone, that's when the rboot would occur.
I am in Connecticut and the daily update is the same time, 1:30AM. If the update time is 1:30 for all time zones, I think that 3:30 would be a better time for most. (However, as I said previously, it still would be a problem for some; I really can't understand why the engineers can not make the simple change to to allow us to choose the update time).
Since it's 1:30 am no matter where you live, it's programmed into the Hopper itself. So, most probably, it's the receiver phoning home to see what's new. The receiver initiates the process, not Dish. In order for Dish to call the receivers instead and only start a reboot if there is new software, it would take a major rewrite of software and most probably a huge expense to up grad Dish's computer system. I'd rather Dish spend it's resources on other things to make the system better. Like being able to decide when we want the receiver to phone home. These are only my thoughts.
I'm honored that Peggy mentioned me on here. As far as the "fix" goes. It requires something that isn't scheduled by design to be "fixed". This is not a big, but it is something that is done intentionally. With the former recievers, people were not letting it update. Then mad because the guide was not up to date. Dish took this ability away with the hopper. My point is, if not satisfied with the product, do not use the product. But this is how dish has designed this specific peice of equipment. It may change in the future. I have heard through the grapevine that it is likely to change in the near future, however, as it stands currently, the 2-5 minute update isn't enough for me to hate the equipment. And yes, 130 is a primary time I'm watching tv. I get the frustration, but that just makes it time to do something else. My viewing experience does not hinge on this feature, and it only updates once per day. I am not someone that gets mad when something goes against dish, I just think there are better things to really discuss, such as the dish anywhere user experience. The codec is just fine with the hopper.
Based on your reply, I would guess that you have spent no time managing systems or networks. I have about 25+ years of relevant experience to the topic.
Your points may be valid, but they won't accomplish anything.
This is the way Dish wants to do their updates and we can love it or leave it (of course, they'll be quick to point out if you have an ETF.)
And the blunt truth is they really don't care how much any of us may be an expert concerning a particular subject.
I'm not trashing you, because believe me, they're are other things they do that make me say WTF.
That's exactly right. It's stupid to ask to update since it's not going to update until the recording is finished anyway. I'm not saying that I wish it would reset, and break my recording either -- I don't want that. The problem is that they should go back to where it won't pop up the update message until recordings are finished. I have no official confirmation on this but I suspect this is an attempt to try to make sure everyone gets the nightly updates and is mainly a method to counteract those who purposely have been setting recording timers specifically from 1-6 a.m. so that no updates could get through. If people want to do that, then that's on them. If Dish wants to try to intervene they need to find a better way so that those of us who do watch and record TV for awhile in the early a.m. hours don't have to suffer.What I don't understand is that for the past year I've been able to avoid the 1:30 update message by setting a timer, & the update would happen afterwards - the last software update changed that & it pops up the message no matter what, but still doesn't update/reboot till the recording is completed. Why have the message, it's not doing anything if there's a recording. The system should be smart enough to know it has a recording in progress & not show a message till it's finished, which is the way it was working before 342.