It's like we're all in alternate universes. We are using BB Storms, right? I didn't land a Motorola forum by accident or anything?
This has been the issue since day one. One group of phones works good with an OS and another group can't live with it. I couldn't use .99 because it was constantly rebooting itself. 122 killed my battery. But 90, 103, 109, 113, 132 all worked fine, but others had nothing but problems. Still think there is a chip set difference depending on where they were built.
Thanks man. In DM it said something about not upgrading the software at this time but I think its because I still have .122 on my computer so I just used the loader. In the process of updating now. Hope I dont jack this up.
well, here's hoping that doesn't happen! but if it does, this should help:
Well after 9 battery pulls .132 is finally working right but personally .122 is better .132 is laggy froze up once never should have switched nothing is better memory the same I feel like .132 is actually a small step below .122
Posted from my CrackBerry at wapforums.crackberry.com
Loader wouldn't read my device config so I ran it with the /nojvm option which forced the install but wiped out all my 3rd party apps....That said - this is the fastest and most stable OS I've run yet and I'm on probably my tenth...
No surprise it's running faster with your device memory cleared of apps.
Posted from my CrackBerry at wapforums.crackberry.com
Well after 9 battery pulls .132 is finally working right but personally .122 is better .132 is laggy froze up once never should have switched nothing is better memory the same I feel like .132 is actually a small step below .122
Posted from my CrackBerry at wapforums.crackberry.com
Thanks for the excuse to finally skip an update.
Posted from my CrackBerry at wapforums.crackberry.com
I am really enjoying this OS. Been running it since last night and only had one problem so far. My screen had a few running lines through it while i was trying to do SMS/MMS about 10 minutes ago. It was real spotty and the letters were almost transparent. The battery pull fixed it. First real issue I have had in awhile. Was running .113 and really enjoyed that one with no issues at all.
Well after 9 battery pulls .132 is finally working right but personally .122 is better .132 is laggy froze up once never should have switched nothing is better memory the same I feel like .132 is actually a small step below .122
Posted from my CrackBerry at wapforums.crackberry.com
The boot seems fast, the applications seem to load faster
I can't tell how stable the radio is. .122 had a stable radio even though it was not a Verizon OS. Right now the radio is acting normal. In my house it was bouncing around, went outside and it continued to bounce. Now I am on the same couch and it is stable.
how can some phones work well with the update and some dont? i dont get that. everyone is getting the same update so why are some people saying its super fast and some people saying its terrible?
how can some phones work well with the update and some dont? i dont get that. everyone is getting the same update so why are some people saying its super fast and some people saying its terrible?
I suggested quality control, but it could be the apps. Though the radio signal should be stable regardless.
The again I completely wiped the device and then installed .132 and had issues with the radio. RIM really needs Six Sigma, I am certified I will go work for them...
Forget it, the radio is now playing games again. Most reliable, haha!
I noticed that sometimes you gotta give a new OS a few days to settle. I had .122 do that to me. The first day my memory drained and battery severely...On the second day, both of them did much better, and same was for speed and overall performance and on third day the phone was awesome. Now I am getting same thing with .132, memory is not doing well today, battery: I already charged the phone twice today, some lag, and keep loosing data (1XEV to 1X to 1xev to 1x). Will see what happens tomorrow. I know that it needs time.
Edge? You are using AT&T? Try to Register your host routing tables.
Done brother! I try re-register, i have the service book reloaded, then try the swap-a-radio app(never got it to work on vista64) and still fighting to get it working. I think im going to go back to the previous version, This one is kicking my a$$.