It took a little longer than usual, however, OS 4.7.0.132 for the BlackBerry Storm 9530 has made its way, unofficially so, onto the web. You can get the latest BlackBerry Storm OS from the link below. Just make sure that you are comfortable with installing it and understand that you will not be supported by RIM or Verizon if you do.
OS 4.7.0.132 for the BlackBerry Storm 9530
Rob,
I’ve never updgraded my OS but am comfortable in trying. Any special advise before I do so? I imagaine I just download to my desktop and sync with my BB Storm?
Yes, make sure that you back up your device first and note that it isn’t a 5 minute upgrade. It is going to take 30 or 40 minutes.
Make sure that you are comfortable with downgrading in case you get an issue.
I’ve come to learn to have your BES admin on standby too…the last upgrade I did killed my desktop/Exchange settings and had to be reactivated
i have .122 right now…minor issues. what’s new with this version? will this be the new official verizon release instead of .113?
@sparky:
Other than the usual “it’s faster” or “it’s more responsive,” there’s nothing new, really. And no one is sure what OS Verizon will release officially.
Also, installing this OS will force you to downgrade to Facebook 1.3.
“And no one is sure what OS Verizon will release officially.”
THAT is the problem, for BB users, for verizon customer THAT is the problem, for RIM THAT is the problem. RIM should be 100% in control of their hardware and the software which runs on it. With OTA and the new app store it would be so easy for RIM to handle keeping the software up to date, while giving BB users bug fixes and software upgrades. verizon has proven time and time again service providers should not be allowed to come between a manufactures hardware and the software which runs on it.
There is a good reason why Steve Jobs’ called the four big U.S. cellphone carriers the “four orifices”. RIM would be smart to do their best to make sure their customers, BB users are taken care of when it comes to BB hardware and software performance, it’s too important to allow service providers to mess it up.
And given that RIM manages BB connectivity already, this would seem like a no-brainer. My guess is that there is a financial gain for RIM by creating carrier firmware locks.
.132 has the improved memory management that .122 offered over .113, and also has .113’s great battery life. I uninstalled .122 about two hours after I “upgraded” from .113, when it completely drained a full charge in an hour and a half.
.132 has none of these issues. Frankly, as long as these leaks keep improving the phone, I don’t give a damn if Verizon “officially” releases anything.
“There is a good reason why Steve Jobs’ called the four big U.S. cellphone carriers the “four orifices”. ”
Yes. They wouldn’t let him bend them over and have his way with them the way the music industry did. AT&T wussed out and now the iPhone has the crappiest network available.
I just updated last night and so far have noticed no real improvements from .122. Although it is a huge improvement from .75. It was easy to install and I had no real problems, with my phone or my PC. The new OS does seem to freeze up a bit, and the acelorometer gets confused when switching from landscape to portrait and vise versa. Also the screen seems to overlap. Its hard to describe, so bare with me. Imagine the screen shifts to the left, and everything that has run of the screen is now on the opposite side. It only does this every so often (when texting or emialing) and the only way to fix it is with a battery pull. All the original problems from .75 have been fixed (i.e.- random reboots, laggy camera, media palyer freezes). So I say update to .122 at least. If you do update to .132, be prepared to wait. It takes a long long time to install. Or maybe it seems like a long time when you cant use your phone.
@whiteberry
I had the same problems with .122. That screen shift is the exact thing I tried to explain in the .122 release thread. Almost like you picked the wrong resolution for your desktop monitor and stuff. So it seems that problem is not fixed from .122 to this one.