Hey everyone,

Hoping you can help/provide feedback on your experiences. I have an 8900 with active UMA service. UMA on 4.6.1.250 and 5.0.0.238 worked flawlessly, not so with the latest 5.0.0.314.

I was able to connect via UMA initially after the upgrade, but for the past three days no luck. I have confirmed I am on WiFi and have an active connection for BIS/BES over the WiFi. Manually setting mobile options to WiFi only yields no results.

I've tried battery pulls, soft resets, re-registering with the network, etc...

Any thoughts/suggestions?

Cheers!

Whenever I have issues like this at home, I reset the router and it has fixed the problem 100% of the time.

That said, I realize that not everyone can stroll around the building at work resetting wireless routers and rebooting servers, etc., so I don't have a practical suggestion.

Klotar, thanks for the response. In fact I did reset our routers/access points. I'm unable to connect both at home with the Rogers TalkSpot router as well as at our office. I forgot to mention it during the original post. I am a seasoned IT Pro but don't have the time to delve into the inner workings of the config on the handheld running beta code nor watch the network for traffic to see what's going on. I'll just downgrade if that's what's needed. I didn't know if anyone else was running into these problems.

I wouldn't assume it's the OS. It could be your carrier.

I have 5.0.0.314 on the 8900 with T-Mobile and UMA is no problem.

So just to add more to the conversation...

After several attempts to get 5.0.0.314 to work I tried the following:

- Full wipe of the device via BBSAK 1.7
- Reloaded 5.0.0.314 via BBSAK 1.7 (AppLoader)

Still no UMA, re-setup WiFi network, verified BIS/BES via WiFi, waited a good 15 minutes, still no voice connectivity via UMA

- Full wipe of the device via BBSAK 1.7
- Loaded 5.0.0.238 via BBSAK 1.7 (AppLoader)

Still no UMA, re-setup WiFi network, verified BIS/BES via WiFi, waited a good 15 minutes, still no voice connectivity via UMA

- Full wipe of the device via BBSAK 1.7
- Loaded 4.6.1.310 via BBSAK 1.7 (AppLoader)

UMA hooked up within seconds of adding the WiFi network...so I definitely think this is software related.

Anyone have any suggestions...I'd like to get back to 5.0.0.x BUT not at the expense of losing my unlimited calling when on WiFi...

works on the g/f's t-mobile 8900 running .314

I noticed mine was not working either. Turned off mobile network and turned on wi-fi and I could not get UMA to work. I tried to re-register and it said it would queue the request up until the next time I had data service. Turned mobile network back on and UMA popped up (assume something to do with registering on the network again?). Mobile network is off again now and UMA seems fine.

It not working for me either!!

+1, rogers, with unlocked tmobile 8900. no uma icon what so ever... was fine with previous 4.6....cant remember the pre 5.0 version.

I have had no problems with UMA working for me using 5.0.0.314 either ar home or work. I have even use UMA at a local cafe. I did a clean wipe with BBSAK and uploaded OS using apploader from C: drive

I had some issues with UMA in the past, but have found that if I keep my router on channel 3 that I do not have any issues with it ever. I do have a T-Mo@Home router that I use exclusively for UMA use on the blackberries in the house, but previously they were on the other wireless network in the house and I had that set to channel 3 as well.

I've left all the other settings at their defaults on the T-Mo router and have never had any UMA issues along the upgrade and beta OS paths.

Changing to channel 3 might be worth a shot to see what happens..

from all the posts above, seems like only Rogers/Fido customers are having issues with UMA. all the "yes it working for me" are on T-MO.
just an observation. note, that I am able to get wifi to work (white wifi logo) and can see it work on data, but the UMA logo doesnt ever come on. I have tried wifi only, but no calls go through.

Hasn't worked for me in about 2 weeks. Cancelled the service.

For the record, I downgraded back to 4.6.1.310 and UMA is working again on Rogers. I've noticed it takes a while to hook up to UMA though, as much as 5-10 minutes once getting on WiFi.

Also noticed that the 9700 makes no mention of supporting UMA on Rogers' site.

Yea... any 3G phone does not work on Rogers UMA service. Currently it must be an EDGE only device.

I'm assuming the problem is because of handoffs between 3G<-->UMA. If you were to run the phone in EDGE only in theory it should work, turning on 3G when you want it, but losing the ability to roam in and out of your TalkSpot/WiFi zone.

I was also having lots of issues with UMA on Rogers, but got it working now. I upgraded to 5.0.0.314 straight with App Loader (found on XP at c:\Program Files\Common Files\Research In Motion\AppLoader\Loader.exe) without wiping out my 8900, I even didn't have the official 4.6.1.250 but 4.6.1.310 (Avea).

I read somewhere that by rebooting without Wi-Fi on and only activating Wi.Fi after the device comes up UMA would work, but this only worked for me last night. Today I had to reboot and UMA did not come up all day, not even soft (alt-shift-del) and hard reboots. I followed one of the comments, turned off GSM and Wi-Fi and only activated UMA and it came up in about 5 seconds, oddly enough.

On the 3G-UMA issue, T-Mobile offers "Wi-Fi calling" with the Bold and they do have a 3G network. When the 9000 came out for Rogers I heard that the strategy was that these 3G devices were more for "business people" and that Rogers had deactivated UMA on purpose (having said that, would it work to load the certificates and activate it through the e-screens, anybody?)

Hope this helps

For those having issues have you checked the WiFi Diagnostics?

Options->Wi-Fi->Wi-Fi Tools (Menu Option)->Wi-Fi Diagnostics

UMA wasn't working after I upgraded to .348 even after setting up UMA in the engineering screens. The UMA section in WiFi Diagnostics showed a DNS error which helped me realize I fat-fingered one of the UMA URLs.

Dave

just an FYI, if you already dont know, you cant utilize the UMA function on a unlocked bb (non provider phone). Another words, my T-Mobile unlocked 8900 will not work on Rogers UMA service, everything else works -> wifi browsing, calling, mms, sms, etc.
As dmattox mentioned, in wifi diagnostics, it shows the phone is trying to connect to tmo network even though i am on rogers. I have looked everywhere on the phone and net and have come to this conclusion... no UMA for me

Odd, I upgraded from 314 to 348 and UMA is now rock solid, you might have done something wrong on the e-screens

d33pa,
Odd as well, I have read of people that made UMA work on their unbranded berries, you need to put the t-mobile certificates and then activate them through the e-screens. Other option is to re-brand your berry

Take a look at forum called "UMA unlocking" at crackberry, uma-unlocking-201539 (sorry, can't post links just yet)

You are a godsend. Totally appreciate this info!

I have gotten to the escreen, however am stumped on how i would acquire the ca.rogers.com certificate...

Have you tried adding Rogers in the UMA engineering section?

Take a look at this thread:
forums.crackberry.com/f65/uma-device-swapping-218920/

Wirelessly posted (Bold)

Thanks all so much in assisting me in getting the uma working on my tmo phone on rogers sim!
I managed to pull the cert ca.rogers.com from a previous backup on my old Rogers 8900 phone. If anyone is stuck on finding the cert, let me know and ill send you the cert for Rogers.

So it is working now? Sorry about the confusion, at first I thought you wanted to put a Rogers phone on the T-mobile network, that's why I mentioned about the T-mobile certs, but the reverse works the same of course.

Wirelessly posted (Bold)

Yes, its working now! I have UMA with purple bars on my ph when I select wifi preferred.

I had a couple calls that came in and the call quality was crap, perhaps its the 5.0.0.314 OS, I heard the latest 5x (can't remember off hand the exact version) is better for UMA. I'm just happy I got this far.

I doubt the internet connection is the issue because I have a wrt54g with 15mbps down and 1mbps up consistently.

I would suggest you go to .348, at least for UMA on Rogers it is now rock-solid; the quality is just good, not the same as GSM, some glitches here and there, but I doubt is my internet connection, I have 50Mb/s and 1Mb/s upstream and I have configured the router for QoS, but you are dropping your packets onto the net, so who knows what happens there .

BTW, I did the upgrade directly from .314 to .348 and no issues (too lazy to go through the whole process of reloading the OS and the apps)

Wirelessly posted (Bold)

Thanks for the info, ill be upgrading to 348 in the very near future. I made a few more calls and its working great (not sure why the initial 2 calls sucked), ill upgrade any ways. Long live bbf!
&
Go Canucks Go!