BlackBerry Forums Support Community

df662 · 10-22-2007, 04:02 PM

Wirelessly posted (BlackBerry8320/4.2.2 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Bbweather does not work on my 8320 after installing this os. I tried uninstalling and installing bbweather again but still a no go. I'm getting an open tunnel failure and yes I did input my APN again after upgradin os. Anyone have any ideas what's up

PCgirl · 10-22-2007, 04:10 PM

Quote:

Originally Posted by HaTaX

Hehe, sorry about that. Been watching the forums while I test out .180 and get my berry back to the way that it was.

A few observations with .180:

Seems very similar to .175 as far as speed goes, nothing I can see as a huge change other then it seems to start up from cold very quickly.

As far as bluetooth with wifi goes, I'm actually having MORE trouble with the .180 version. Bluetooth was off and a UMA connection was made, I turned bluetooth on and fired up my bluetooth headphones / headset. (They actually work quite well as a headset in a quieter environment) The result was the headset connected quickly to the device but when I went to make a call to 611, the call never went through, was dropped, and then it reverted back to EDGE.

Here's where things get strange and I hadn't seen this with .175.... After the dropped call, I tried it again on EDGE and the call went right though. I then waited for the device to reacquire it's wifi connection and then UMA, this took about 2-3 minutes for it to do it on it's own. After words I tried again to make a call and it again dropped the call, and reverted to EDGE with no call being completed at all. When I let it sit this time, it did reconnect to the wifi network, but did not establish UMA. So I went into wifi diagnostics to see what the error was with UMA and it said ISP error, as I was in this menu the UI started becoming very unresponsive, and then the phone rebooted itself.

After it had come back up I again tried the bluetooth + UMA dialing and was still unable to even get it to connect when dialing out, if even for a few seconds, all I ever heard was the call lost tone (3 pitch climbing tones). Also odd was that after it dropped it this time, I simply shut off the headset and the bluetooth on the device and attempted to make a call. It STILL gave me the call lost tone and refused to make an outgoing call, the only resolve I had to this was to shut off wifi, and after it had hooked back up on the EDGE network I could make outgoing calls again. After I had made a successful call to 611 on EDGE I turned wifi back on and it is working as expected again.

This is no good and I may revert back to .175 if .180 fixes nothing else and makes the bluetooth with wifi worse then it was.

Hi HaTax,

I scrolled upwards and read your post above and I think since my only issue was with WiFi anyway I will just keep the .171 for now.

Thanks!

TimW · 10-22-2007, 04:41 PM

Wow that took a long time. I fell asleep in my chair, to wake up 20 minutes later and it still working... :D

Pinman · 10-22-2007, 04:45 PM

I do not have a data plan...but I installed the update and it took all of about 5-10minutes. Connected to UMA right off the bat. Have not tried Bluetooth yet...but will soon!

fourthaye · 10-22-2007, 04:50 PM

So is there no way to do this on a mac??

churchill · 10-22-2007, 04:53 PM

Contrary to the above, my wifi and UMA is GREATLY improved and much faster.....Thats the news so far.

BB4Life · 10-22-2007, 05:07 PM

quick question:

i unlocked my 8320 to use on ATT, and now I lost my medianet browser..any way i can get that back??? thanks

bryanparke · 10-22-2007, 05:22 PM

uh oh...

never had this happen before - i just started the upgraded to .180 walked away and came back and the 'enter device password' screen was up, i entered the password and pressed 'next' - the phone shut off and never turned back on (waited a long time). the device password screen never continued, just sat there with the back/next buttons greyed out. i eventually pulled the connection to the phone and pulled the battery. Now, right when i put the battery back in i just get a red flashing light - no hourglass, nothing.

anyone have advice?

rivviepop · 10-22-2007, 05:25 PM

Quote:

Originally Posted by BB4Life

i unlocked my 8320 to use on ATT, and now I lost my medianet browser..any way i can get that back???

...how could you have lost the medianet browser if the device was locked before, it couldn't have been used on AT&T where that service book exists? In any case, did you re-send your books to the 8320 from your BIS login?

bryanparke · 10-22-2007, 05:33 PM

i went ahead and started down the path of apploader /nojvm - just bummed that i lost all my data, will attempt the restore of the backup when the os finishes reloading. have upgraded many bb's and never had this happen before.

oh well - i bet somehow i did something wrong.. although, there really isn't anything one can do wrong with a bb upgrade - they have made it so easy.

can't win 'em all.

ndub33 · 10-22-2007, 06:57 PM

I searched for this no luck-if there is a thread relevant to it, I will gladly kick my own butt...

I did the upgrade to .180 today. I work in a T-Mobile Hot Spot, and where I was getting a UMA connection (slowly) with the .171 OS, I now get no wifi connection at all, W010 and W002 errors,and my IP address shows 0.0.0.0 in Options>Status.

Anyone have any insight?

rtst31975 · 10-22-2007, 08:02 PM

Well I tried installing twice and both times I got an "App Error 523" reset message and it wouldn't finish restoring curve. Anyone know what causes this? Oh well, I am happy with the .175 os.

GLOCKshooter · 10-22-2007, 08:12 PM

I am upgrading right now. Don't know why, .175 was working just fine, but why not? It's there.

bdraco · 10-22-2007, 08:32 PM

Quote:

Originally Posted by GLOCKshooter

I am upgrading right now. Don't know why, .175 was working just fine, but why not? It's there.

The uma .180 seems more stable, it was able to hold a call to at&t customer service to cancel a line (the 8320 is on tmo).

monkeypaw · 10-22-2007, 08:34 PM

Upgraded from .175 to .180 and so far seems slightly better on wifi. With WPA2 before it would instantly disconnect if I tried to call voicemail. Now I had about a 20 second call so tried the Motorola H700 headset and it kept for about 5 seconds more. Then my phone did a reset or something like that. On WPA the call was again ok for about 20 seconds with the BT headset then the router rebooted. Still not working obviously, but it is better than before.

Back on WEP now and no problems.

Helmdawg · 10-22-2007, 08:48 PM

Although I wasn't having any problems with .171, I upgraded to .180 and its still working great (thankfully)

vinniet · 10-22-2007, 09:25 PM

On the upgrade to 180 it is hanging on "Waiting on Device Init" and on the bottom it says Connection to Device. Its been on this for 20 minutes. The only thing on the screen is the wait logo for BPhone theme. Was I suppose to switch themes before the upgrade? Any ideas?

UPDATE:

I waited it out and the wait cursor changed to a hour glass. Then it started to restore everything. It all worked but took a while so make sure you have time to wait....

Helmdawg · 10-22-2007, 10:55 PM

Quote:

Originally Posted by vinniet

On the upgrade to 180 it is hanging on "Waiting on Device Init" and on the bottom it says Connection to Device. Its been on this for 20 minutes. The only thing on the screen is the wait logo for BPhone theme. Was I suppose to switch themes before the upgrade? Any ideas?

UPDATE:

I waited it out and the wait cursor changed to a hour glass. Then it started to restore everything. It all worked but took a while so make sure you have time to wait....

Any update will take some time while in the initialization stage, anywhere up to an hour in some instances. Be patient...

Ramsy · 10-22-2007, 11:12 PM

Quote:

Originally Posted by rtst31975

Well I tried installing twice and both times I got an "App Error 523" reset message and it wouldn't finish restoring curve. Anyone know what causes this? Oh well, I am happy with the .175 os.

I got this same error message. I had to hit the "reset" option on the Curve. However, .180 OS loaded successfully. It just did not restore my old apps. But, when the Curve rebooted, it auto started a wireless enterprise activation - so a lot of the data was loaded back via that process and then I just used desktop manager to reload the other data from the loaderbackup file that was made as part of the install process (if you selected backup data as part of the install process).

HaTaX · 10-22-2007, 11:23 PM

Quote:

Originally Posted by monkeypaw

Upgraded from .175 to .180 and so far seems slightly better on wifi. With WPA2 before it would instantly disconnect if I tried to call voicemail. Now I had about a 20 second call so tried the Motorola H700 headset and it kept for about 5 seconds more. Then my phone did a reset or something like that. On WPA the call was again ok for about 20 seconds with the BT headset then the router rebooted. Still not working obviously, but it is better than before.

Back on WEP now and no problems.

So you've found that the combination of WPA2 encryption and your bluetooth stability? I think I'll give it a shot turning encrptyion off and using MAC filtering. The only thing I really use this AP for us my t-mobile phone. I have another for general wifi access, it just doesn't do WMM.

BlackBerry Forums Support Community

OS: BB 8320 4.2.2.180 TMo