PDA

View Full Version : Channel Change issue


TriggerDeems
07-11-07, 11:44 PM
I have a new HR20-700 in the TV room. About 10% of the time, it won't change channels when I type in a new channel number on the remote (again 90% of the time it works fine). The receiver will recognize the inputs, and it will display on the TV set, but it won't physically change to the new channel 10% of the time. Try it again, and it will typically work. Pressing the "enter" button doesn't make any difference. The channel up/down buttons work every time. I've tried 2 other remotes, no help--same story. All three remotes work flawlessly on another HR20(so don't expect any remote/battery issues). The "good" HR20 worked fine when it was swapped to the TV room (so don't expect any line issues to that room). The other HR20 and two H20s all work fine in their normal rooms (so don't expect any satellite dish issues). I've reset the "problem" HR20 with a menu-reset, a RBR, and a plug pull reset--no change. Any other ideas?
Thanks

TriggerDeems
07-12-07, 10:16 PM
Anyone have any ideas or suggestions or seen this issue? Thanks

veryoldschool
07-12-07, 10:53 PM
Anyone have any ideas or suggestions or seen this issue? Thanks
Just one [well two]: wait for the new national software release [or come to the CE forum and test the new software].

TriggerDeems
07-12-07, 10:58 PM
Just one [well two]: wait for the new national software release [or come to the CE forum and test the new software].

Thanks VOS. Since the other HR20-700 works fine, even on these two cable runs, do you think a firmware could really fix it? I'd think they were basically the same hardware, but who knows.

cygnusloop
07-12-07, 11:04 PM
Thanks VOS. Since the other HR20-700 works fine, even on these two cable runs, do you think a firmware could really fix it? I'd think they were basically the same hardware, but who knows.

It's one of those strange and inexplicable things. Some folks see it, and some never have. All with the "same" hardware, and the same software revision. For those that were experiencing it, the revs have had a positive effect. Go figure.:confused:

veryoldschool
07-12-07, 11:16 PM
Somebody is steeling my post count. :lol:

cygnusloop
07-12-07, 11:18 PM
Somebody is steeling my post count. :lol:

Since you have me by more that 10:1, I don't feel all that bad about it! :lol:

All :gott: :gott: :gott: :gott: :gott: to VOS!

TriggerDeems
07-12-07, 11:20 PM
Since you have me by more that 10:1, I don't feel all that bad about it! :lol:

All :gott: :gott: :gott: :gott: :gott: to VOS!

Thanks guys. I've been around for sometime and snooping for even longer, and hadn't ran across this one before.

veryoldschool
07-12-07, 11:20 PM
Since you have me by more that 10:1, I don't feel all that bad about it! :lol:

All :gott: :gott: :gott: :gott: :gott: to VOS!
I'm runnig about five days late this month to hit my next 1,000 mark.

mcbeevee
07-13-07, 08:19 AM
Anyone have any ideas or suggestions or seen this issue? Thanks
Is the remote/receiver set to RF? If not, it might help to switch from IR to RF. :)

radamo
07-13-07, 08:49 AM
I posted the same issue about a week or two ago. Sometimes you enter a channel in and nothing happens. Other times the unit changes to that channel. The only way to make it listen every time is to type in the channel number and then depress the ENTER key. Really very strange...
RA

houskamp
07-13-07, 08:52 AM
Check the "banner time" setting.. having it set to 2 secs tends to do this.. On the bright side they seem to have it fixed in the latest test releases..

mcbeevee
07-13-07, 09:06 AM
I posted the same issue about a week or two ago. Sometimes you enter a channel in and nothing happens. Other times the unit changes to that channel. The only way to make it listen every time is to type in the channel number and then depress the ENTER key. Really very strange...
RA
My original thought was the enter key or using leading 0's, but the OP said: "Pressing the "enter" button doesn't make any difference".
:confused:

radamo
07-13-07, 09:58 AM
Check the "banner time" setting.. having it set to 2 secs tends to do this.. On the bright side they seem to have it fixed in the latest test releases..

Mine is definitely set to "2 Sec"... so that may be the cause. Glad to hear that the new test releases clear this up. It can be annoying.
Thanks for the update.
RA

bobnielsen
07-13-07, 10:04 AM
With the national software version, setting the banner time to 4 seconds should take care of it. OTOH, there is a new CE release coming tonight.

davring
07-13-07, 10:16 AM
In the nine months that my HR20 has been alive it has always been hit or miss, from day one. It hasn't gotten any better or any worse with any updates and hitting enter, and number entry, just makes it sound angry, and I do have the banner time set for 2 seconds, I'll switch to 4 and see if that helps.

veryoldschool
07-13-07, 10:45 AM
In the nine months that my HR20 has been alive it has always been hit or miss, from day one. It hasn't gotten any better or any worse with any updates and hitting enter, and number entry, just makes it sound angry, and I do have the banner time set for 2 seconds, I'll switch to 4 and see if that helps.
I had it, but not since the last test update. FWIW

Steve Robertson
07-13-07, 11:54 AM
Thanks for the tip on the banner as I have mine set at 2 seconds will make the change tonight

TriggerDeems
07-13-07, 06:17 PM
Based on the initial suggestions to wait for a new firmware, or go with CE, I decided to try downloading the same software all over again. So, I did a "reset everything" and download the same firmware on reboot (0,2,4,6,8, enter), and it works 100% now. Granted, that reset my banner time to 4 secs, instead of 2 secs where it was when I was having the problem, so who knows. I just reset the banner to 2 secs just now, and it still seems to work. Quirky. Thanks for the help, all.

PS, I was always using IR mode.