A little bit harsh at the end there. I would have said, "...isn't with the software but with the hardware." Otherwise, I agree with you, though.
U504
- Thread starter stardust3
- Start date
- Latest activity Latest activity:
- Replies 94
- Views 10K
Sorry, but Dish hardware is a closed system. Other than external HDDs, users can't randomly add pieces of hardware that Dish's software has to deal with. Most of the issues that are discussed here aren't "user error" either, it's just the way the system software works. "We" have no control over it.
All software has bugs and glitches. If all of those had to be fixed before release, we'd never see any software, be it Dish set-top software, Microsoft Windows, Apple macOS or iOS, Android, etc, etc.
Omg!Not to go into too much detail, but you haven't seen some of the major bugs that didn't make it to the public.
Much of this is NOT keyboard - chair - interlink errors.
Loss of 4x, certain slow modes, recording on another HWS and messed up DVR listings/recordings CANNOT be blamed on anyone but Dish.
Sure the first three aren't "bugs" they're "features." But the last is certainly not what Dish intended. As are other problems.
Loss of 4x, certain slow modes, recording on another HWS and messed up DVR listings/recordings CANNOT be blamed on anyone but Dish.
Sure the first three aren't "bugs" they're "features." But the last is certainly not what Dish intended. As are other problems.
I take VERY great exception to this comment. How exactly can it be the user's fault when software that produces one result one day does not following an "update" and all the user has done is push the on button?
I have a feeling that U505 will further address OTA.
Last edited:
Hehe the problem could very well be with the users. Some users don't notice the bugs which tells me that those people have a very limited use case or that they are not very observant.
Kind of hard to miss obvious things such as creating a manual timer and then saving it and finding that it was created with a completely different time than you picked.
Kind of hard to miss obvious things such as deleting a timer and then while still on the timers screen trying to adjust the priority of another timer and having it move the timer below instead because it didn't internally adjust the numbering to account for the timer that was deleted.
Kind of hard to miss that the guide data on some shows does not change day to day so the show does not record "skipped, already recorded." No work around because if it thinks it has recently recorded the episode then it isn't going to re-record it regardless of the recording type.
Fix these obvious things please so that those of us who notice the defects can watch our tv shows.
I love the HWS/Hopper3. No other complaints really but when I try and fail to record a show for the same reasons that it failed six months ago, it gets frustrating.
Seems that they are more interested in adding new Alexa features than they are with operational stability.
I'm 100% with Hall on this one. Android is a good example of software that has to handle many different combinations of hardware. Dish is much more like Apple though. Everything is vertically integrated into their own little ecosystem. If something doesn't work, the hardware maker is the same as the software provider, Dish. I've done some beta testing, and for the most part I don't mind it. The beta tests I did though were ones that I signed up for knowing what was going on. I don't like being a beta tester for Dish with no "opt out" button.
If the OTA problems are only software issues, then why can John Sheridan test 2 different Hopper 3 receivers from their warehouse having the same software version and one works and one has problems? I suspect that the Hopper3 hardware may vary based on the manufacture date and the actual manufacturer.
Dish has always tweaked their hardware throughout their production life. There's a sticker on the back or bottom of the receivers and at one time, they used simple A, B, C, D, and so on revision designations. I remember an issue years back where the A, B, and C revisions were fine but D and newer revisions had a specific issue.
Absolutely. There's always a chase after Better Faster CHEAPER!
Like when CUI was released to testers and DVR recordings didn't play anymore?? Uh huh.....Not to go into too much detail, but you haven't seen some of the major bugs that didn't make it to the public.
I still do not have U504 for the Hopper 3. Is there anyone else that do not have it yet? I wonder if it got cancelled!
I don't understand signal strength meters. The lowest my tv can lock on channels is at a 10 on the tv tuner signal meter. However the H3 won't lock on to my ABC affiliate which is at 25! Pitta-full. Another strange thing is my NBC affiliate is at 73 on the tv but 81 on the H3. I guess what might help is if DISH can change the meter to lock on channels at 10 or above. 
Dish may have discovered that 504 broke more than it fixed. Maybe you should count yourself lucky.
The TV tuner meter and the Dish meter use two different methods of measurement. What is a 10 on the TV might be a 60 on the Dish tuner. You would get breakups at 60 and Dish doesn't want to let that pass because you would be calling them each time your picture went away. They opt to be on the safe side and only pass signals that are strong enough to maintain a good, steady, picture.I don't understand signal strength meters. The lowest my tv can lock on channels is at a 10 on the tv tuner signal meter. However the H3 won't lock on to my ABC affiliate which is at 25! Pitta-full. Another strange thing is my NBC affiliate is at 73 on the tv but 81 on the H3. I guess what might help is if DISH can change the meter to lock on channels at 10 or above.
I lost a few stations ota that were in yellow and around 75- 80 strength. But luckily all my main networks and most of the sub channels are locked in at 100% and green.
FWIW our Hopper 3 is still on U503 tonight. And I hope it is still on U503 tomorrow
