Forum › Forums › Freesat HD › HDR 1000, 1010, 1100S › Remote not operating any functions
- This topic has 39 replies, 7 voices, and was last updated 11 years, 1 month ago by
Anonymous.
-
AuthorPosts
-
September 25, 2014 at 11:29 am #16089
Anonymous
Inactivenow remote not operating any functions. Batteries replaced no response
Admin edit: Thread title changed to some more appropriate.
September 25, 2014 at 11:44 am #55876Barry
ModeratorDependant on remote in use:
1. Ensure you have pressed STB button – if remote has that button
or
2. Remote may have changed code, as witnessed by a couple of us.
Try reprogramming it.
With unit powered on and display on TV…
Press OK and Zero button on remote simultaneously, a message should appear on screen re remote code, if you have not changed it before then press 1 then OK.
September 25, 2014 at 3:43 pm #55877Anonymous
InactiveThe number of users reporting this and very similar problems since the last s/w update seems significant to me. Twice since the update my almost 2 year old box has become completely unresponsive to the R/C, except for power button. When powered off/on from R/C again would not respond. I fixed it each time by completely cutting power to the box for about 1 min, reconnected and all was OK. Has that update made the box unstable?
September 25, 2014 at 5:59 pm #55878Anonymous
InactivePollensa1946 – 2 hours ago »
The number of users reporting this and very similar problems since the last s/w update seems significant to me. Twice since the update my almost 2 year old box has become completely unresponsive to the R/C, except for power button. When powered off/on from R/C again would not respond. I fixed it each time by completely cutting power to the box for about 1 min, reconnected and all was OK. Has that update made the box unstable?
If this is just after boot, I have the impression that sound and picture appear before the boot process is complete and a small wait will restore functionality.
I also suspect that for example other remote keys are functional e.g. Volume. (Perhaps these are serviced by a NMI (non-maskable interrupt).
I do hope you put your unit in standby before pulling the power.
Unlike you PC (if you have one) the unit is almost always writing to disk and you risk disk corruption (especially to the time-slip buffer).
September 25, 2014 at 8:11 pm #55879Anonymous
InactiveYes I did notice that the volume control was still effective. Still it seems strangely coincidental that this is suddenly happening after a s/w update.
As to…
REPASSAC – 2 hours ago »
I do hope you put your unit in standby before pulling the power.
Unlike you PC (if you have one) the unit is almost always writing to disk and you risk disk corruption (especially to the time-slip buffer).
Did you have a glass of Cheval Blanc at hand when typing that?
September 26, 2014 at 12:53 pm #55880Anonymous
InactivePollensa1946 – 16 hours ago »
Did you have a glass of Cheval Blanc at hand when typing that?
Not at all. Live in small farming village with lots of vines around, so tend to drink the local wines most of the time. Whites from 1.20 (en vrac) Euro’s a litre, reds a little more.
For something a bit different I like a nice shiraz (managed to get a case of this cheap) – very full bodied.
Reread my post – seems fine to me, except could do with a comma or two.
October 19, 2014 at 10:27 am #55881Anonymous
InactiveInteresting! I bought a new box that exhibited exactly the same problem. Stuck with it for about a month, then concluded the box was faulty so I returned it for a replacement. The replacement, however, exhibits exactly the same problem, i.e. refuses (occasionally) to react to remote when first powered up. Only cure I have found is to switch off at the mains for an hour and try again. I am in the process of leaving it switched on at the mains permanently to see if that resolves the problem. This is definitely a firmware/software issue and not “IR interference” as suggested by Humax.
October 19, 2014 at 12:14 pm #55882Anonymous
InactiveRobin Hood – 1 hour ago »
Interesting! I bought a new box that exhibited exactly the same problem. Stuck with it for about a month, then concluded the box was faulty so I returned it for a replacement. The replacement, however, exhibits exactly the same problem, i.e. refuses (occasionally) to react to remote when first powered up. Only cure I have found is to switch off at the mains for an hour and try again. I am in the process of leaving it switched on at the mains permanently to see if that resolves the problem. This is definitely a firmware/software issue and not “IR interference” as suggested by Humax.
I think the boot process is not complete when the home screen is displayed – I notice that it does take 10-15 seconds longer before the remote commands start to be serviced.
October 19, 2014 at 12:59 pm #55883Anonymous
InactiveSo it is bad programming! Is it not normal that as soon as the program screen is displayed, users will use the remote to select a program? I would certainly not expect the box to hang if the remote is used used too soon.
October 19, 2014 at 1:17 pm #55884Anonymous
InactiveRobin Hood – 17 minutes ago »
So it is bad programming! Is it not normal that as soon as the program screen is displayed, users will use the remote to select a program? I would certainly not expect the box to hang if the remote is used used too soon.
I guess if would be quite easy to delay showing the picture for 15 secs.
My unit does not hang – it just does not service the remote presses.
October 24, 2014 at 2:13 pm #55885Anonymous
InactiveHave left the box switched on at the mains for 5 days now in the hope that the problem would be resolved. No such luck. Just powered it on and, guess what, it is totally unresponsive to the remote – yet again. This is definitely a serious system problem that Humax needs to address asap.
October 24, 2014 at 2:27 pm #55886Anonymous
InactiveRobin Hood – 12 minutes ago »
Have left the box switched on at the mains for 5 days now in the hope that the problem would be resolved. No such luck. Just powered it on and, guess what, it is totally unresponsive to the remote – yet again. This is definitely a serious system problem that Humax needs to address asap.
Have you thought the problem might just be with your unit seeing as it’s not something that seems to be a widespread issue?
October 24, 2014 at 2:40 pm #55887Anonymous
InactiveYes. That is why I returned the first box for a replacement. This second box is no better.
October 24, 2014 at 3:03 pm #55888Anonymous
InactiveRobin Hood – 21 minutes ago »
Yes. That is why I returned the first box for a replacement. This second box is no better.
They did replace the remote as well as the box?
October 24, 2014 at 3:21 pm #55889Anonymous
InactiveYes. Replaced everything. My first action was to try using another (programmable) remote, but that was no good either. All the remotes worked the TV, but both the Humax boxes just froze (intermittently) after boot up. While it pains me to say it, my previous Sky box worked seamlessly for years.
-
AuthorPosts
- You must be logged in to reply to this topic.