If 5.0.0.127 is out there, why cant we get past 4.7.0.141?
- VZW had .75 in testing when they released the storm, they had to launch on .65 since it was the last one to pass before their release date they were shooting for.
and yes, .75 has its issues. the sacrifice they have to make to get the phone out for the holidays.
and i have a phrase for you to consider....
"service impacting issues"....
that is what VZW takes priority over when its testing. as long as its not preventing you from using the basic functions of the phone and keeping you from using the services you pay them for, it'll be a "decent" build....
I figures they did have it in testing but thank you for verifying it.
I understand what you mean by "service impacting issues" but if you are like me and use it for business then having my girlfriends ringtone come on during a presentation with me 10 feet away it is a service impacting issue LOL.05-18-09 08:40 PMLike 0 - patches152BannedI figures they did have it in testing but thank you for verifying it.
I understand what you mean by "service impacting issues" but if you are like me and use it for business then having my girlfriends ringtone come on WHEN MY WIFE IS with me 10 feet away it is a service impacting issue LOL.
fixed it for ya bro...05-18-09 08:42 PMLike 0 -
-
-
- Look how well .75 performs. In reality, when you get rid of some of the expectations that some people have, it works just fine! And thats a testament to how much testing they did to get .75 out there. Look at how old that build is today, yet works fine.
Dont count them out so soon. Just remember, they are testing as much as they do, for your well being as a customer. If they find a reason to fail a build, theres a reason.05-18-09 08:58 PMLike 0 - patches152Bannedthe *228 thing didn't come up until the very end....so maybe that build "slated to be released" was just their anticipation of .141 passing...and nothing was ever "slated".05-18-09 09:10 PMLike 0
- I think the "certified" ready to go build was .141 but it still had to pass everyday testing and I think it was prematurely assumed that it would.
The rest is history.
Posted from my CrackBerry at wapforums.crackberry.com05-18-09 09:14 PMLike 0 - patches152Banned
YOU'RE BOTH WRONG!!!
they were calling the .141 build the "certified" before it actually passed testing, and then at the last minute VZW failed it.05-18-09 09:21 PMLike 0 -
- Lol patches. It may seem like I copied you but I didn't. It just seems that way. We just think similarly.
Posted from my CrackBerry at wapforums.crackberry.com05-18-09 09:25 PMLike 0 - patches152Bannedtx, you should be 1 tequila, 2 tequila, 3 tequila, floor!
then dial *228, send, option 17 to enable wi-fi, and your phone will be fine...05-18-09 09:52 PMLike 0 - But then don't forget to battery pull so you can surf the net for hangover remedies.
Ugh tequila
Posted from my CrackBerry at wapforums.crackberry.com05-18-09 09:56 PMLike 0 -
- Look how well .75 performs. In reality, when you get rid of some of the expectations that some people have, it works just fine! And thats a testament to how much testing they did to get .75 out there. Look at how old that build is today, yet works fine.
Dont count them out so soon. Just remember, they are testing as much as they do, for your well being as a customer. If they find a reason to fail a build, theres a reason.Last edited by Souless Poet; 05-18-09 at 10:40 PM.
05-18-09 10:31 PMLike 0 - I have had my storm since launch too. Well I went back to .75 the other day. Poet you hit the nail on the head. This build is SLOW, lags, often it locks up just trying to switch between Land & Port. Needless to say I had it on the phone for a day. I switched back to 132. I liked 141 but battery died to fast for me.05-19-09 12:45 AMLike 0
- I know I'm going OT now but by now this thread is pretty much already there... I love how .141 made it as far as it did through VZW testing when the FIRST thing they have to do is activate the phone by *228. Literally 3 minutes into the testing process they should have realized a pretty big issue with the build which changes their whole activation process at the counter. It makes me really wonder how throrough they are with their testing.05-19-09 06:59 AMLike 0
- I know I'm going OT now but by now this thread is pretty much already there... I love how .141 made it as far as it did through VZW testing when the FIRST thing they have to do is activate the phone by *228. Literally 3 minutes into the testing process they should have realized a pretty big issue with the build which changes their whole activation process at the counter. It makes me really wonder how throrough they are with their testing.
But if you knew you were OT, then dont post it in this thread.
Lets get it back on.05-19-09 07:03 AMLike 0 -
And you get back on it!05-19-09 07:16 AMLike 0 -
That's what I keep saying about the *228 bug; however; it seems like a battery pull is WAY too much work for some of the folks who frequent these forums. There are folks on here (whom I will not name as I cannot remember precisely whom) who think that the *228 thing is a more significant bug than the unlocking problem.05-19-09 07:19 AMLike 0
- Forum
- BlackBerry OS Phone Forums
- More BlackBerry Phones
- BlackBerry Storm Series
If 5.0.0.127 is out there, why cant we get past 4.7.0.141?
« storm housing!
|
Question »
LINK TO POST COPIED TO CLIPBOARD