The major reason I found to upgrade to this version *for my needs* is UMA/WiFi calling, so I'll restrict my comments to that. I found personally no other major issues except for GPS in this version compared to 188.8.131.520. I don't use "Mobile Hotspot" feature.
GPS was still problematic for me. GPS did not work after upgrade until I went into Device Analyzer GPS test.
UMA/WiFi calling problems (On T-Mobile service). I'll call it "WiFi Calling" for short since that's what Blackberry calls it, but they still refer to UMA in the menus of the phone:
- Similar functional issues as in 184.108.40.206 and 220.127.116.11 (I reported in .190 thread)
- WiFi calling range is limited to only about 10-13 meters from WiFi access point at full strength. I think this causes problems below.
- I find phone "hangs on" to the WiFi calling mode and doesn't drop back quickly enough to use 3G. Especially apparent at the limits of distance 10-13m. (WiFi calling "Preferred")
- Sometimes the phone has the UMA symbol on (meaning it "thinks" it's using WiFi calling), but: I'm unable to make outgoing calls, or the outgoing call connects but I cannot hear the far end (and far end can't hear me), or incoming calls don't ring. I find myself frequently needing to check that I can still dial calls. Phone continues to "hang onto" UMA mode and won't release it in this case until reboot or turn off WiFi calling.
- If I were to diagnose the problem it is that WiFi calling with this phone has a limited distance/signal strength range from the access point, and the UMA software logic is "hanging onto" the UMA mode too long even at distance limits...but calls can't come in/out. Similarly when returning to an area of strong WiFi, the phone doesn't switch back to WiFi quickly enough. Ultimately it seems as if the phone gets confused about whether WiFi calling is connected or not. This needs more debugging by RIM since I'm missing calls with UMA/WiFi enabled.
For anyone looking to debug this issue, here are some particulars:
- Cisco WAP610N access point, and WNDR3700 AP/router. I've tried them in "N-only" mode and "G-only" mode with similar results with respect to above problems.
Also tried them with "WMM" disabled as well as enabled with similar results.
- Blackberry set to "WiFi preferred." When set to "Mobile Network" preferred, it never switches to WiFi calling
- My 3G coverage is poor in my area, so there could be some software logic problem with switching between the WiFi and network calling in that condition.
- WiFi diagnostics show no UMA-cell handover or rove-in failures, even when in the above mode where calls don't work.
Last edited by NokiaFanToo; 01-23-2012 at 01:16 PM..
It's going to get worse, as FileSonic and those types of sites only allow those who have uploaded the files to retrieve them. All the links are effectively dead. When I get home tonight I'll load up a copy on DB and post a link.
fere libenter homines id quod volunt credunt
I had to let this leak go I was getting an operation failed message when I was on the phone and would send a text. It would cause my phone to lose all signal and I would have to refresh to get service back. I'm just going to stick with the .440. It was the best overall for me had no issues with it.
Edit* I also figured out what the bug was while playing music and making a phone call to cause it to mute. For some reason when you're listening to music and make a call after the call you have to press the "S" button twice and it'll play again. Posted via BlackBerryForums.com Mobile
Last edited by yahjoogooleh; 01-23-2012 at 09:49 PM..