I can't sign up yet :( vm are sending me a new hub for Tommorow l

re: R36 Firmware Beta Test (was R35)
 

After participating in one trial where they put a firmware on general release even though there were bugs reported in the testers private forum and later just no response at all from VM to a series of reports from people I rather think the trials are just eye-candy. They'll probably just rely on the same internal testing which resulted in the release of the thing in the first place with a shedload of bugs. Investigating customer reported bugs (which may not be bugs at all half the time) costs money.

re: R36 Firmware Beta Test (was R35)
 

i am using my Draytek 2580n so did not sign up

ANY ONE WILL TEST THE BETA let us know is still handle better jitter and packet flow in the 450??
is close to the stability of 300 now?
thanks

re: R36 Firmware Beta Test (was R35)
 

dont think thats going to be included in this update

re: R36 Firmware Beta Test (was R35)
 

^^ we can only hope that it is and there are other fixes hidden within the update that they are not specifically saying about because they want the main issues to be tested.

I just signed up, hoping to get accepted.

re: R36 Firmware Beta Test (was R35)
 

Signed up, initially I was getting amazing speeds over the shubs wireless, that didn't last and the connections still dropping so anything I can do to help.

re: R36 Firmware Beta Test (was R35)
 

When they say Blizzard I assume they mean the games company because I had a right pain trying to download and get that game working

re: R36 Firmware Beta Test (was R35)
 

There must be quite a lot of fixes, mostly undocumented it would seem publically anyway.

Because it has been quite a number of months since the last update, and they seem to of taken a big jump from R30 to R35

re: R36 Firmware Beta Test (was R35)
 

Well I would say the increased jitter a lot of people seem to get on the shub is just as urgent to get fixed as the wifi issues. In fact thats all I really care about, as its the only thing I hate about it. Mines rock solid in modem mode with my buffalo router, so its staying that way.

re: R36 Firmware Beta Test (was R35)
 

R31: Came to work
R32: Couldn't be arsed
R33: Went for lunch
R34: Needed the loo
R35: Thinking about fixing wirless 2 years late

re: R36 Firmware Beta Test (was R35)
 

Of course if there was a changelog issued alongside the firmware as is done with most professional software there'd be no need to guess. I personally doubt that there's anything more in it than they've actually announced - it took an awfully long time to do very little indeed during the last phase of firmware updates.

re: R36 Firmware Beta Test (was R35)
 

The HTC One X (Android smartphone for those not familiar) has had two firmware updates since it came out.

That phone had similar wireless bugs on its release (intermittent slow speeds, and drops outs for some people) and HTC fixed it in less than a month.

Less than one month to fix and replace the wireless driver, on a device where the wireless isn't even its core function.

re: R36 Firmware Beta Test (was R35)
 

Someone mentioned, although I can't remember where, that the Superhub has had 11 firmware revisions to date :(

re: R36 Firmware Beta Test (was R35)
 

It should be remembered that the vast majority of VM's Superhub users don't have problems. If the Ssuperhub were universally faulty VM wouldn't be able to use it.

So there are some things that a minority of customers find don't behave as they want. I suspect that those users who have problems are generally amongst the heaviest rather than average users and are somehow pushing some aspect of the system to a limit.

There seems to be an unjustified complaint that VM are trying to fix these problems with new firmware. Weird. Ever since Windows was first release, Microsoft have been patching it. The Battlefield 3 game released only last October is already on PC server version 22. Unfortunately it seems that in the world of tech, things are tested behind closed doors, and then in a limited form via betas but it's only if they get released publicly, and new ways are found to use it but a small number of those public users not envisaged during the testing that a new issue comes to light.

So the current Superhub firmware is R30 and this beta is R35. That does to me indicate there is a continued effort behind the scenes to both make improvements, but equally important, not to introduce new problems by rushing out something that isn't ready.

re: R36 Firmware Beta Test (was R35)
 

I think if you ask there are more people here complaining that the many shortcomings of the Superhub haven't been fixed.