I'm sure they will get the bugs out soon.
That's the overly optimistic viewpoint of someone who doesn't know what kind of bugs they're dealing with.
They're dealing with hardware and software issues on several levels, trying to get motherboards and chips to perform tasks they weren't designed to do and thus cannot handle the data, they are trying to link together several different types of hardware, all of which speak different languages, and at the same time are tying to implement all kinds of really neat, keen, supercool and groovy updates and features from Research In Motion (Blackberry), and are trying to get it all to work within the current hardware and software platform of Qualcomm.
This is not merely something that broke and now it needs to be fixed. It's the classic case of fixing something that wasn't broken. Whoops. It's a classic bad implementation of a good idea, ill-timed, ill-conceived, and utterly unprepared.
Oh, they're working on it, but they're treating symptoms instead of curing the cause. They get one thing to work, and the fix causes several things down the line to quit working. Like, let's get these two pieces of hardware talking to each other, great, that works, whoops, now the software that talks to the hardware doesn't talk to it anymore, let's fix that, great, whoops, now that piece of hardware over there won't talk to this one 'cause the DHCP server can't talk to anything, oh, man, now what do we do...
Shouldda had a parallel system, hardware and software, up and running, and then roll it right over. But that would have cost more than doing it piecemeal. Whoops, again.
When they get it all done it'll be really kewl, tho.