I am unable to get a UMA connection on 4.5.0.37.
How many other 8320 users are having the same issue?

I do know that you are not alone.

Dude, you gotta use the search button.... We just had a heart felt discussion about it over the last 2 days.

Someone said that the UMA function still works, it just wont show on the ribbon...

Give the BBmessenger a try with UMA, and maybe that will tell you...

No, UMA does not work on 4.5.0.37 on the T-Mobile 8320.
It gives an error W006.8 - it has nothing to do with "it just wont show on the ribbon".

It doesn't work.

well mine works just fine .... it actually picks up UMA faster than .18......the only thing is it doesnt say UMA on the bar .....

So if you go into the WiFi diagnostics, there is no error message?

nope no error message ...shows me which router im connected to which i think how its suppose to be ..
i dont really understand how the same software works for me but not for the other guy with same specs?????
t-mo 8320???
[we even live in the same state ..lol...] NJ

Actually, you are the first one I can find who it works for.

UMA works for me as well

edit no it doesnt

Fascinating. On my T-Mobile 8320, using 4.5.0.37, UMA will not start. WiFi is fine. In WiFi Diagnostics, it shows an error W006.8, status T-Mobile Network error.

I wonder if you are using a different serving UNC and Security Gateway Address.

It plain doesn't work.

UMA doesn't start for me either. I've heard that it works for a few but not for others.

i apologize for the wrong statement UMA doesnt work what works is only wi-fi...
(is there any improvements at all on .37??)

Yeah, EDGE works better. It's a trade-off right now. Which do you want? UMA or EDGE?

I need UMA...so I downgraded my OS to .18

Wirelessly posted

No UMA on mine either with .37. I have a feeling this software is the same build for the 8310.

.18 had wifi/uma issues for me so I actually use .18 with the rim8320g.sfi file (in the GPRS folder) from .10. Pretty good combination.

lol...looks more stable compare to .18 not dropping calls and all
think ill hang onto .37 for now..

If you don't need/want UMA then it's fine. I recommend going to Options >Mobile Network and setting your mobile connection to Mobile network only. That way it quits searching for the UMA. I'm guessing that will eat up the battery.

That's exactly what I did.

My battery was torched last week at WES...with both WIFI and Cell ON. Something about the TMO network and all the peeps trying to hit it.

There was so much WiFi and BT there I am surprised we all didn't glow.

Good thing I dont use UMA , I'm installing in this very moment this new OS

Is there a way to take the UMA features from the .18 build software, and insert then in them in the .37 software and reload the software onto the 8320to get UMA working

Anyone has a problem viewing youtube videos??? When I click on a link, media player opens but nothing happens :( ...any suggestions?

yepp I"m getting the same error as everyone else on my 8320, oh well, haven't played with this update much yet though, will check back later

i have my youtube working (even though i never use it) )
one question : has anyone checked their media card space with .37 looks like it doesnt support more than 2 gigs (i have a 6 gb card but it only shows 1.96gb)

Some people got their UMA working but uninstalling the certificate and reinstalling them, some just waited overnight and UMA showed up. Some deleted the two Wifi service book and just resend them.

I might be, but which file do we grab from .18 to .37?

rim8320g.sfi is the file responsible for the radio, it's in the GPRS folder where the loader OS files are located. (Program Files\Common Files\Research in Motion\Shared\Loader Files\8320 etc etc)

Anyway, don't was the time screwing up your BB, I tried both .10 and .18 radio files on the .37 and had bad issues when using either. Any time I opened my browser the os would throw a few errors and lock, and I didn't get UMA either. Instead of a W006.8 error, I got an "Unknown error". So yeah, it doesn't seem to play nice.

I'm using the same config as John listed above with .10 radio with .18 os and it works quite well. .18 had issues with UMA, at home if I dropped off UMA for any reason, it would take a restart of the phone to get it to re connect. Funny that at the office I never had that trouble, it always worked there.. Very odd, but .10 radio works great!

This is from Nastyboy2: It's worth a try, I haven't tried it myself but I will give it a run tomorrow.

finally got uma back with os .37 after trying all day. here are the steps i took.
go into options, then security options then certificates.
delete the 2 t-mobile usa inc listings.
it will ask you to enter a password before removing keystores.
go into options, then advanced options, then service books.
delete the 2 wifi tcp/ip entries.
reboot the curve.
the 2 wifi tcp/ip entries in service book will reappear after the reboot.
go to mobile.blackberry.com with the bb browser and click on help.
click the hotspot@home(uma) is not working link and follow the instructions to install the root certificate and the trust certificate.
reboot again and see if you have uma.

if it doesnt work, an extra step to try would be to go into advanced options then host routing table and hit menu then register now to resend service books to your device.

Hope springs eternal.

Deleted the Service Books.
Deleted the Certificates.

Rebooted.
Reloaded Certificates from Mobile.Blackberry.com
Reregistered

No UMA

UMA error code W006.8 - T-Mobile Network Error

It keeps trying to authenticate and fails.

But WiFi works great...

@NJBlackBerry: same here. no uma love.

I guess my question is why is it working for a handful of users, but not everyone

the answer is market dependent.

Source? What is a market defined as? Cell tower? State? US region?

Here's how I'd define the problem....

I dislike craps tables with blue (or red) felt. Green or nothing.

And I agree with you.

Yup, seems to be a roll of the dice..

I tried doing the steps above before when I had it, I had deleted everything wifi related on my phone and nothing would change the W006.8 error I was getting so I rolled back.

I even tried wiping my trusted key and certificate databases using destktop manager and reload them, made no difference.

no UMA love here on my device in Phoenix, AZ

I had some time to play with this os version yesterday. I was unable to get UMA to work at all. I even went and removed and re-added the t-mobile certs from the mobile.blackberry.com.

I recently changed jobs and decided to do a few wipe with -resettofactory switch. Once the phone finally came up I had UMA for about 20 seconds. I made a phone call and it worked. After 20 seconds it was gone! I had it on the rest of the day to see if it would come back and it did not.

I then reverted back to .18.

I thought maybe it was my it policy that might have stopped it, but after 20 seconds it was error 6.7.8. and it kept pinging and pinging the uma servers....