View Single Post
Old 10-17-2004, 03:17 PM   #8 (permalink)
Thumbs Must Hurt
Join Date: Oct 2004
Location: North Carolina
Model: 8300
Carrier: AT&T
Posts: 119
Post Thanks: 0
Thanked 0 Times in 0 Posts

Originally Posted by ScOObydoo
The 7100 shoud not have these problems, and yes; I've had 100's of version 1 products.

These bugs are too reproduceable to be acceptable.

It's not like we found some wacky roundabout way to makde the device hang, all you do is turn off a bluetooth device in the middle of accepting it's connection, and it crashes. Things like this should never make it past their product testing.

The 5810 is the only device i know of that was as bad as the 7100, RIM has an excellent reputation when it comes to the quality of their products.

In the case of the 7100 there are simply too many serious issues to be able to call it a "great" product. Between the having to reboot to get messages come through, and the bluetooth issues I'd still claim that RIM screwed up, they should have delayed the introduction of the device.
Well I would have to say I completely disagree. I have never had this BT issue and have been using it since day one, I am running custom applications written by my company that work great, and it is faster and more reliable than my 7280 with better battery life. I expected some bugs in the 7100t and I have not even encountered the IM issues everyone has been talking about.

As far as the reported problems I have seen on these boards, none of them point to a hardware issue at first glance so I have faith that they will all be resolved. Perhaps expectations were too high that this device would be _exactly_ like a cell phone and less like a business tool? I dunno...

IMHO when you buy a product that is new to the market, any bug you find should as always be properly reported and documented, and a fix is sure to come. It is just one of those things that techies have to deal with.

The BT issue I tried to reproduce on my unit and was unable to, so it does not affect all builds and all BT headsets - I am not saying this is an isolated issue, but it is not a global one. I am using build 112 of the BB SW and the Plant. M1000 headset.