U502 has blown up OTA...again.
- Thread starter Jon J
- Start date
- Latest activity Latest activity:
- Replies 202
- Views 18K
So you are saying we should all finagle for a replacement? This is pretty wide spread.
That's what you thought a while back. You suggested only receivers with receiver IDs starting with a specific set of digits were affected. My receiver had a different number and was affected.
Are you suggesting that if I call Dish and tell them I'm having issues with OTA channels (live, delayed, recorded), they look at my receiver ID and if it's a certain number (within a set of known numbers), they'll offer to replace it ?
I haven't checked thoroughly with the single tuner as far as drop outs on Joeys but I did check and it dropped the OTA channels from the guide with both single and dual tuners. I only know what I know and I don't know what I don't know, so...
I did ask if others with the same problem also had receivers with RID 's that began with R191 like the 2 problem receivers I had, I was just trying to gather facts. I know when I replaced my receivers that were dropping the OTA channels every day the problems went away.
I've never had the break up problems that apparently you, KAB and others are having so I have no suggestions in regard to that.
It could also do with what factory they were produced and/or refurbished in. They don’t necessarily have to be the same batch. It could be a undiscovered manufacturing issue. Wether anyone will ever know for sure is another thing as there’s so many variables.
These things each seem to have their own individual personalities. For instance right now I have one H3 that turns itself on right after the nightly updates every night and then I have 2 that don't. And they're all on U504.
I would really hate to be a software engineer working on the firmware for these bad boys.
Does this receiver also turn itself back on after the four-hour (or whatever length of time you set) inactivity shutdown? Just curious. I have observed this behavior on several models of receivers, so it is not just a H3 thing, nor is it anything new.These things each seem to have their own individual personalities. For instance right now I have one H3 that turns itself on right after the nightly updates every night and then I have 2 that don't. And they're all on U504.
I would really hate to be a software engineer working on the firmware for these bad boys.
Mine are set for the four-hour default, but since the receiver immediately turns itself back on again, it is almost like they are set to "Off."I have the inactivity timers set to 'Off'.
This morning recordings I saved that previously broke up on playback are playing back perfectly. 'Splain that. Obviously the problem was introduced at playback not when revorded.
Sorry to get your hopes up. As mentioned above, it's still breaking up on mine.
Hey, here's an idea: Someone with a Hopper 3 and the OTA module in one of the DMAs where Dish and the Network Affiliate are having a pissing match should record the breakups occurring while watching the Affiliate in dispute with the OTA module. Then, send it in to the station and point out that Dish's tactic of sending free OTA antennas to their customers won't let them watch the Affiliate in "perfect digital quality". That should put a fire under Dish's programming team!
So did anyone ever figure anything out here? It's been months and my OTA recording still suck, which is a problem because I grab quite a bit of shows off the digital subchannels.
H3 on U508, ID starts with R194xxxx..
H3 on U508, ID starts with R194xxxx..
