Quote:
Originally Posted by John Clark
Ok, after reading through the thread I see what you are talking about. I posted that from the mobile forums and likely didn't read enough.
I actually answered the OP's question but he asked it again anyway. I post to other forums too and likely thought I was answering a different question than that of the one here. Regardless, my mistake.
The answer to the OP's question is that an unlocked FIDO device will NOT connect to UMA on Rogers or any other network other than FIDO (if they even had UMA.) I said this in post #6. Changing the OS will not do anything, either. The FIDO device will not have the proper UMA profile set up in the engineering screens. It is possible to add UMA functionality to an unlocked device from another provider but it requires techniques that are above most people's ability. That said, if you think it is within your ability I have written posts on adding TMobile UMA capability to other branded devices. For example, I have an ATT branded Torch and I have to complete this process each time I upgrade the OS on it. See the post here:
http://www.blackberryforums.com/gene...tethering.html
I'm sure there is info out there on where to get certificates for Rogers and the proper Rogers server info to enter in the Engineering Screens but I don't have that info off hand.
I hope this clears it up. |
Well, now we're talking about two separate things - two different questions the OP actually asked in the thread. He mentioned three devices:
Quote:
Originally Posted by richdocekal
My BB8900 and my wife's BB8900 are both Rogers unlocked. The 8520 is an unlocked Fido running on the rogers network.
|
Your original answer, which you expanded on now, is succinct and 110% correct:
Quote:
Originally Posted by John Clark
Only the Rogers branded devices will get UMA. The fido device will not have the proper uma profile for Rogers.
Posted via BlackBerryForums.com Mobile
|
What I'm speaking of is his other, related question - the two 8900's which are both Rogers - one of which always connects with UMA (multiple, different brand routers at different locations) and the other one which connects WiFi but not UMA (again, tried at multiple locations on different routers.) That's the issue which pretty much has to be a device issue - either hardware or software (OS) issue.