-
I don't agree with you on this. I think the people going through several replacements are fishing for that one "perfect" handset. There's no arguing that the Storm has issues, but the problem with a lot of people is that they cannot recognize a software issue vs a hardware one most of the time. A lot of replacements probably have happened which didn't need to happen, but at the same time there's several phones out there that have screen click issues, period.Yes there are probably some handsets that have QC issues and apparently the refurb dept has horrible QC but i still believe a lot of the issues that we see people complaining about is user error. I am not discounting the bugs that everyone can duplicate, I am talking about the ones that are localized to 2-10 people and they are the only ones with that specific complaint.
I will relate this back to cars since I have spent the better part of my life working for the local dealer. Everyone loves their car when they buy it and typically have a 45 day window where there are no issues what so ever. Then they have to make that first payment that they have never had to make before and are scrambling to find the money for it. Then all of a sudden they are in the service dept every other day complaining about something that either a.)doesn't exists or b.)is something that is trivial and they were dealing with for the last 45 days without a complain of it.
I see this scenario replicated throughout various industries time and time again. I have seen it in the military as well as I am reclassifying my MOS with the National Guard and watching these recruits come through talking about I didn't sign up to run 3 miles a day. Yet the contract they signed states that they will remain in good physical condition to be able to meet the APFT(Army Physical Fitness Test) standards.
Sorry to the OP for getting a little off topic here. Radio some of us do enjoy what our BB can do. Yeah I want it to do more like cook my dinner and keep my kids in line but that is just taking the value out of family time
.
That being said, the other part of this is that I don't want to put up with bugs in the most recent versions of the OS that weren't there with the release software. There is one perticular bug on my list that this EXACT thing has happened with. The HTML email menu choice bug is the one I'm talking about. It wasn't there in .7x builds, so why the f should it be there in EACH AND EVERY release up to .141? Why?... because RIM overlooked it and didn't find it. I highly doubt they saw the issue and simply said "Meh, who cares... they won't notice." To me this is a glaring problem with the GUI code in itself. It shows that RIM's having some kind of diffculty tailoring the menu GUI around the touch screen interface. There are certain conditional arguments in the GUI code that trigger what menu choices should be presented to the user based on certain conditions. This part is ultimately flawed and is causing this problem. It needs to be fixed and fixed quickly. I honestly could care less about the lock issue in .141 (that's why I didn't put it on the list... I'll give them the benefit of the doubt and state that it probably slipped by and until it ends up in release after release, I won't add it), but for the other things listed to be left unfixed is simply UNACCEPTABLE and if NO ONE on any of the testing teams (RIM or carrier) thinks they are acceptable, then they should be ashamed of themselves as it shows the type of quality of product that we've seemed to come to expect from the last few years out of RIM. Ever since they started to get fancy with the code (starting with 4.5), we've seen a lot of problamatic code... more so in 4.6 and 4.7, but the track record really started in 4.5. It's almost like they are traveling in uncharted territory or something....05-18-09 09:20 AM
