Are you trying to load a page that have java scripts that may make your browser overload and time out. Other than that it may be your device. I've had .171 .175 and .180 and I'd say .180 is the most stable with wifi.

Has the memory leak been fixed with this verison

myFaves came back after I had gotten the device back to the way I wanted, themes, settings, etc.

So myFaves is working and so far the OS seems fine, I haven't left the house yet today so we'll see what happens long term.

If it acts up for me, instead of going back to .180, I'll most likely roll all the way back to .175.

Anyone notice any differences yet?

Yep - I've seen the same problem as you have Rivvie. This appears to be a bit more stable (and still not perfect) but I have to wait until Monday to see how it performs at work.

So far so good. Haven't done a ton of browsing or calling over the holiday, but from what I've done, I have no problems to report.

Aww man, another one? lol I REALLY clean up the OS for myself whenever a new OS comes out. I just did this like 3days ago, dont wanna have to do this again damn it!! I think i will wai till 4.3 to ugrade myself, unless there is a huge difference. Ill wait and see what u guys have to say before i do an upgrade.

I have been using it all day yesterday and today and so far no problems yet. I'm on T-mobile in Newport Beach, CA. The hand off has been fast but have not been on a call yet during the hand off to see if it goes dead. Will keep you apprised.

Had one issue yesterday, but I'm not sure if it's related to the OS or the theme. I did a search on Google Maps and called the place from the map result. I got a "would you like to allow google maps to access the phone", said yes, but the box never went away and had to reboot. Also, I'm using Calix's Titanium Today theme and one text message will not go away. Again, this may be related to the theme though.

...but Monday is so, so far away! Can you just go to work now and then let me know in a few hours?

OK. I will go in now just to test this.

NOT

May have to go in tomorrow however...

That's where he's going with those scissors!

My initial impressions so far is that in this version of the OS, WIFI is more responsive. I connect to routers faster and get the UMA connection much quicker then in previous versions of the OS. Browsing via WIFI also sseems quicker.

My memory leak issues seem to be better (I have not used my BB like usual, so I cannot say that the memory leak issues have been solved in this OS.) While I have not taxed my BB like I usually do due to the holidays, my available memory has not diminished over the last few days of use - like it did in prior versions of the OS. (Since running into low memory warnings - in a few days, my BB went from 8M free to less then 1M free, I typically check available free memory once a day.)

On the downside, I have noticed one small potential glich. When scrolling through my messages and opening e-mails, the BB sometimes seems to be "sluggish" to "non-responsive" for a few seconds, kind of like the system is completely taxed. After a few seconds, the BB responds as usual. Anyone who spins the trackball and the cursor does not move knows how annoying this can be. This has happened a few times now, so, I do not consider it an isolated event.

Any chance you have something like Empower or BBSmart HTML mail viewers installed, or maybe even BeamBerry, which could be causing the death pauses? Can you create a test scenario for others who've upgraded to test as well, trying to mimic your behaviour?

This and JC's reboot crash don't sound good...

Does anyone have a clue or approx date of 4.3 release? I just want to wipe my blackberry for a clean install to make it a bit faster, and I just don't want to waste my time with the same version if 4.3 could be released soon.
Thanks.

The *rumors* have been end of December or early next year. There is no release date yet.

Any more reboot issues JC? I have it downloaded just waiting to install.

Nope, just that one, so far.

Good deal. I will be installing today and post anything I notice. My usage is about 85% UMA and WiFi.

Thanks. I think I will just wait, no need to fix what's not broken. My BB works, and that's good enough.

No, I do not have any HTML e-mail viewers installed. I do have BeamBerry installed, but I have had BeamBerry installed on my Curve since the day I got it. Unfortunately, I cannot devise a way to recreate the bug I experienced.

However, I will note one new issue that just happened - all my audible prompts and the phone ringers somehow became muted. For example, if someone called, the phone would not generate an audible ring. Since upgrading to this version of the OS, I have not made any changes to any of my audible prompts/ringers in any of my profiles. Switching profiles did not correct this problem. The only thing that worked was a battery pull.

After you click on the link, where do you go?

Well, unfortunately, I have to report another random reboot. This time it was while I was in BBMessenger. That's two in 5 days....I never had any with .171, .175, or .180.

Everything works to be fine after upgrading from 180 but I have noticed that sometimes my Voice Dialing hangs at "Initializing"...specially when its activated via bluetooth...not sure if this is an issue on the software or the Nokia BT headset, never tried to activate it via BT before with 180

4.3 is nice...read about some of the features, video recording on it's own is enough for me to upgrade besides other things

is there a stable OS that shows Chinese text?

edit

well I have had 184 on my t-mo 8320 since 11/24/07 and finally went back to 175 today. It was fadding in and out while on a call and I was sitting 3 feet from my router. Also the UMA did not seem very stable and would switch to EDGE in the middle of a call. Also while on UMA the phone would fail while trying to get voice mail several times until I finally shut down UMA and used EDGE to get the voice mail.

It seems that 175 is the most stable for me.

i keep getting you are attempting to open a secure connection, but the server's certificate has exspired. everytime i go around a new wifi connection this happens since i switched to 184. anybody else having this problem? i tried reseting my router and reseting my blackberry but still getting same message. if someone has a solution please let me know.

Why did you decide to go to .175 instead of .180, if I may ask? Just curious, not a loaded question.

I tried 180 also and while on a long conference call using UMA 3 feet from my router, the phone would go dead even though the call was still connected. While at the office, I would walk away from the router and the hand off took at least 15 to 30 second, which during the mean time the phone at my end was dead, until it switched over. This did not see not seem to happen with the 175 firmware.

I tried 180 also and while on a long conference call using UMA 3 feet from my router, the phone would go dead even though the call was still connected. While at the office, I would walk away from the router and the hand off took at least 15 to 30 second, which in the mean time the phone at my end was dead, until it switched over. This did not seem to happen with the 175 firmware.

Thanks for the update. I have had no issues with .180 and may stick there until the next release. Am I correct in saying .184 can actually be an earlier build than .180 due to delays in release by the carrier?

Is there a way to find out if 184 has an earlier kernel than 180 or what ever they use. Sorry, I just know certain things about the 8320, I don't know anything about firmware compiling or any of the programing nuances.

There are no facts as of yet to my earlier comment, was just throwing that out there based on my knowledge of carriers holding onto releases for a while.

A bit off topic here, but why are there always so many upgrades for the Blackberry? Is this normal? This is my first BB and I am wary about upgrading it because I've done it before and experienced a lot of issues with the upgrading process. Also why are the vast majority of these "upgrades" not actually from a US carrier?

12 hours in and so far my phone is operating just fine. It was a warranty exchange that arrived yesterday with .180 installed. With that OS it would sometimes not connect to the wifi network without coaxing. I'd have to turn wifi off then on again.

So I upgraded to .184 and now it'll connect to wifi without coaxing. Seems to do this faster than my old phone did but not sure if that's due to the phone being more stable or the OS.

It didn't work well with my Verizon Fios supplied Actiontec router with WPA security, so I'm running it on WEP now. That's a nice change from my old phone which I had to run off my Linksys WRT54GS running DD-WRT. Now I can leave that unplugged without having any disconnect or reboot problems with the phone so far.

This is my problem as well with .180, and it's completely random as to when it'll be a pain about connecting to Wifi and/or stay connected even if it's the same location and access point; it's a pain in the tuckus. Followup later if you can after some time and let us know if .184 has made it better all the time (and not sometimes like it is now, ugh).

Because there are bugs that need fixing. It is normal - what is *abnormal* are phone manufacturers who never release upgrades and make you live with the bugs (hello, Motorola and Samsung) or ones who release upgrades that break more than they fix (hello, Nokia S60). RIM follows the open source philosophy - release early and release often.

*groan* Welcome to Planet Earth, the USA is not the center of the universe. Did we mention that RIM is a Canadian company?

I had to coax it to connect today after waking from auto off. However, I think that Yahoo Go was causing problems. Basically, when I tried to open it I got an error e33 and it would not connect to Yahoo at all. So I reset Go and then got the message "Sorry, Yahoo! Go encountered a problem during start up. Please restart Yahoo! Go." Never got it to work.

But after that the phone got stuck on uma for about an hour. The wifi error was "UTC channel activation failed." Switched routers and the connection cleared but still was uma. Deleted Yahoo! Go and back to UMA on restart of the phone. I tried to install Go again and it wouldn't connect, so it's gone for good.

I set it to auto off and on to test and this time connected just fine. All the way to UMA very quickly.

This happens because you forgot to update the date/time on your blackberry, most of the issues that people are experienceing when certificate expired etc is because the time/date on the handset is not connect, its probably showing time/date before TMO started UMA Service.

Or you might want to install desktop manager with custom option and install Certificate Sync so that you can see all the root certificates...there should be one called T-Mobile something...make sure there is a green checkmark in front of it.