- This topic has 342 replies, 45 voices, and was last updated 6 years, 9 months ago by
.
-
Posts
-
nickcc – 6 hours ago »
Faust – 1 hour ago »
nickcc – 14 hours ago »
nickcc – 22 hours ago »
I have the same reboot problem with one of my 1100s 1TB boxes. Contacted Humax support who advised restoring to factory settings which I did just over three weeks ago. All seemed OK until yesterday when same fault occurred, tried restoring again but fault still occurring.
Have contacted Humax support again and waiting on reply.
Nothing from Humax but it seems according to Digital Spy a Freesat problem. Just another reason to change back to Sky, unfortunately. Just rebooted again, checked that the software was up to date which it was, seems Freesat is unable to compete with Sky. I remember another terrestrial supplier that went bust, wonder if Humax and Freesat will be next.
If it’s a new box and you are not satisfied then get it changed. If it’s under six months old you don’t need to prove a fault as it’s considered to be inherent. I’ve had virtually no problems with my box in over 3 years.
It would appear there is nothing wrong with the box and Freesat confirm that their software is at fault which they keep attempting to cure, that’s the reason for all the restarts/reboots. Don’t see the point in changing boxes if the box isn’t at fault. Incidentally I swapped boxes out and get the same fault with my other almost new 1100s box, we never noticed the restarts on this other box as we only use it for about 30 minutes a day whilst the other box is used for at least 8 hours per day.
Freesat confirm the software fault is more common with the 1000s and 1100s boxes so if you have another type of box maybe you’re not affected.
HDR1000S. I would take what Freesat tell you with some scepticism as they tell different people different things. Personally if the box is as bad as you claim then I would be getting it swapped out.
andyfras – 1 hour ago »
Faust – 6 hours ago » My remote control however is a different story as a number of buttons have now become problematic and this is simply down to wear and tear.
If you feel brave, open up the remote. You’ll probably find an oily substance has leached out of the silicon membrane; wipe off as much as possible, then touch a hot soldering iron onto the suspect conductive pads on the membrane (it won’t melt). This will usually restore conductivity to the pads. You can test the suspect pads with a multimeter on the 100kohm range, with the probe tips on the same pad, but not touching each other. A pad resistance of less than 10kohm should work OK.
This procedure may need repeating occasionally.
I did this with my previous remote – Panasonic. It did work but quickly deteriorated again. Thanks for your post though.
Faust – 1 hour ago »
nickcc – 6 hours ago »
Faust – 1 hour ago »
nickcc – 14 hours ago »
nickcc – 22 hours ago »
I have the same reboot problem with one of my 1100s 1TB boxes. Contacted Humax support who advised restoring to factory settings which I did just over three weeks ago. All seemed OK until yesterday when same fault occurred, tried restoring again but fault still occurring.
Have contacted Humax support again and waiting on reply.
Nothing from Humax but it seems according to Digital Spy a Freesat problem. Just another reason to change back to Sky, unfortunately. Just rebooted again, checked that the software was up to date which it was, seems Freesat is unable to compete with Sky. I remember another terrestrial supplier that went bust, wonder if Humax and Freesat will be next.
If it’s a new box and you are not satisfied then get it changed. If it’s under six months old you don’t need to prove a fault as it’s considered to be inherent. I’ve had virtually no problems with my box in over 3 years.
It would appear there is nothing wrong with the box and Freesat confirm that their software is at fault which they keep attempting to cure, that’s the reason for all the restarts/reboots. Don’t see the point in changing boxes if the box isn’t at fault. Incidentally I swapped boxes out and get the same fault with my other almost new 1100s box, we never noticed the restarts on this other box as we only use it for about 30 minutes a day whilst the other box is used for at least 8 hours per day.
Freesat confirm the software fault is more common with the 1000s and 1100s boxes so if you have another type of box maybe you’re not affected.
HDR1000S. I would take what Freesat tell you with some scepticism as they tell different people different things. Personally if the box is as bad as you claim then I would be getting it swapped out.
Unfortunately Humax have confirmed a software problem as I posted earlier so looks like I’m stuck with it, especially as I have the same fault with my other 1100s box, until the update goes through.
Has anybody asked Freesat or Humax if going back to a previous firmware would help or solve the problem until the newer firmware is out? The firmware version before the current one that came in June/July, was also rock stable as far as I could tell, in fact, I couldn’t spot anything of use in the new firmware (though perhaps the iplayer from the last firmware wouldn’t work now?).
Any ideas? It’ll be a week tomorrow with zero known reboots with the network disconnected on my box, so it’s looking pretty likely it is indeed presumably, poorly written firmware reacting badly to something going on at the Freesat server end (as in, the box firmware should never reboot due to a problem or something it doesn’t like in the network data feed! (unless Freesat are able and are, issuing an instruction for the box to reboot?))
Maybe I’ll setup a transparent proxy again and point the box at that, to log what network traffic is taking place between it and Freesat, if the new firmware doesn’t come out soon (it surely won’t, if experience is anything to go by!
).
mutant_matt – 14 hours ago »
Has anybody asked Freesat or Humax if going back to a previous firmware would help or solve the problem until the newer firmware is out? The firmware version before the current one that came in June/July, was also rock stable as far as I could tell, in fact, I couldn’t spot anything of use in the new firmware (though perhaps the iplayer from the last firmware wouldn’t work now?).
Any ideas? It’ll be a week tomorrow with zero known reboots with the network disconnected on my box, so it’s looking pretty likely it is indeed presumably, poorly written firmware reacting badly to something going on at the Freesat server end (as in, the box firmware should never reboot due to a problem or something it doesn’t like in the network data feed! (unless Freesat are able and are, issuing an instruction for the box to reboot?))
Maybe I’ll setup a transparent proxy again and point the box at that, to log what network traffic is taking place between it and Freesat, if the new firmware doesn’t come out soon (it surely won’t, if experience is anything to go by!
).I get reboots with no network/internet connection.
Are most of the reboots with the 1100s? I don’t see many if any posts from 1000s owners still experiencing this issue.
Mine is a 1000 and up until last Thursday, was rebooting all over the place!
A week of disconnection has made it seem perfect. I’ll cross my fingers and plug it back in again later today I think.
Cheers,
Matt.
My network connected HDR1010S rebooted once several weeks ago, but has been fine since.
My (not connected) 1000s rebooted last night at 19:58 while watching a recording of Strictly which was still recording and carried on recording until 20:20 ish.
I had one reboot (HDR1000S) while attempting to delete a series of recordings (may be a coincidence), this terminated a recording in progress. Not been able to repeat it since.
My HDR1000S has just rebooted at 20:22 whilst recording Planet Earth II. Recording failed.
Mine rebooted last night just befor 1900 hr and tonight about the same time.
When you think of the many Freesat/Humax customers who must be experiencing this reboot problem, especially the length of time this has been going on, it really is disgusting.
I think you will find that the number of users currently experiencing reboots is quite small. It is hard to tell from forum posts where only users with problems post, however the numbers of recent posts have reduced significantly from the time freesat were thought to have solved the problem.
It’s very strange why some reboot and others don’t. Mine for instance hasn’t done this since the initial problem was identified and a ‘fix’ applied weeks ago. Could it be that not all the Humax Freesat boxes share the same components i.e. chipsets from different suppliers etc.
- You must be logged in to reply to this topic.