JamesB - 18 hours ago »
MontysEvilTwin - 2 minutes ago »
On digging through this thread further, the Tenda 311U+ has already been confirmed as working after the update: see here.Yep, so it has. Useful to know.
UPDATE: Still no issues with operation of Tenda 311U+ with update
It is looking increasing like the dongle issue is related to the vendor and product ID codes (see post #249). Some unbranded dongles and others, such as the Tenda 311U+, share the same VID and PID codes as the Humax branded model so they still work.The change required to the driver to make the Edimax dongles work again is trvial, it in just depends whether they want to fix it or not.
Is it strange that the reboots seem to have disappeared (touchwood) for the last 2 or 3 weeks? Still on 2.02.34, had numerous reboots the first week or so, then as far as I have noticed there's been nothing since?
spark001uk - 2 hours ago »
Is it strange that the reboots seem to have disappeared (touchwood) for the last 2 or 3 weeks? Still on 2.02.34, had numerous reboots the first week or so, then as far as I have noticed there's been nothing since?
Consistent with Freesat's statement that server-side changes had helped the problem.
http://www.freesat.co.uk/help/got-freesat/fix-a-problem/freetime-boxes-rebooting
Ah ok. The statement was a bit ambiguous, as they didn't mention server side I just assumed they were making improvements to the firmware and testing it. 
Yeah, communication is not their strong point.
JamesB - 9 hours ago »
spark001uk - 2 hours ago »
Is it strange that the reboots seem to have disappeared (touchwood) for the last 2 or 3 weeks? Still on 2.02.34, had numerous reboots the first week or so, then as far as I have noticed there's been nothing since?Consistent with Freesat's statement that server-side changes had helped the problem.
http://www.freesat.co.uk/help/got-freesat/fix-a-problem/freetime-boxes-rebooting
I have a different experience James - for the very first time since the update was released, my 1000s suddenly decided to reboot last night. This happened right in the middle of the programme about women who flew fighter aircraft during the war (WW2) - fascinating programme.
Fortunately the box wasn't recording nor did it spoil my enjoyment as the second it happened I switched inputs back to the TV's own Freeview tuner. I noted the reboot was quite rapid too.
Is it possible that whatever Freesat has done may have inadvertently introduced the issue to a different chipset not previously affected?
Different chipset? Why would your box have a different chipset?
We don't yet have an explanation as to the cause(s) of the rebooting - only that the server changes helped. Presumably once they feel they've cracked it completely they'll either issue a new release or re-broadcast the one that was pulled.
JamesB - 2 hours ago »
Different chipset? Why would your box have a different chipset?
We don't yet have an explanation as to the cause(s) of the rebooting - only that the server changes helped. Presumably once they feel they've cracked it completely they'll either issue a new release or re-broadcast the one that was pulled.
My understanding is the components within the devices, in line with practices throughout the electronics industry are sourced from different suppliers. Hence my comment different chipset.
My guess about why rebooting might be caused by interaction with Freesat's servers, would be that it has to do with the attempts to smooth out the rough edges of loading, accessing, and refreshing Showcase/OnDemand. Differences in behaviour from one box to the next would more likely be down to differences in usage/setup/environment than differences in components. But I'm only guessing.
You must log in to post.
