05-08-2013 02:01 PM
Hardware: Z10 STL100-3
Have noticed that when my Z10 is unable to connect to Wifi the profile is automatically disabled, and I have to manually re-enable it. This happens both at work and at home where the failure to connect is temporary (if I manually re-enable the profile and hit "Connect" it connects).
Is thre any way to prevent the OS from automatically disabling the Wifi profile, or at least let me chose whether to or not? My guess is "No" or "not yet" since there's a long-running forum thread on this exact same issue over on CrackBerry and no solution has been posted yet. Just thought I'd try over here just in case...
05-09-2013 08:04 AM
Hi colinwu and welcome to the BlackBerry Support Community Forums!
Does the Wi-Fi network appear as one of your saved networks? Does this happen with all of Wi-Fi networks?
05-09-2013 08:18 AM
Yes they are saved profiles, and it happens with any profile that the Z10 has trouble establishing a connection with either at the authentication stage or, most often, at the dhcp stage. It I cancel the connection attempt before the 3rd try times out it doesn't get disabled. Of course, the problem is when I don't notice that, for example, my home profile has been disabled and end up using the wireless network.
From the sounds of it a lot of folks would be very, very happy if this can be resolved either by not automatically disabling the profile or prompting the user whether it should be disabled or not.
05-11-2013 01:20 PM
Two of the profiles I've exerienced this with are WEP while the 3rd is WPA/WPA2 Enterprise. I have not tried deleting and re-adding but will the next time this happens; but not being able to connect is not the issue. I recognize that sometimes connection just is not possible due to poor signal strength, over-subscription, problem with the AP, etc. The real issue is that the profile is being automatically disabled without notification. The user should be given a choice whether to disable the profile or not. Sometimes the failure is only temporary and may connect at a later time.
05-12-2013 11:16 AM - edited 05-12-2013 11:16 AM
It kills it after three attempts but if you manually select and connect it will re-enable it.
Note that the problem with it not connecting may be related to the crash/reboot issue although it doesn't appear to be at first blush. I have traced the failure to connect to a network stack blocking problem on the phone; I have an AP here that I can "see" into the negotiation with the other end while it's happening and the AP thinks the node associated but the phone doesn't see it.
See if going into airplane mode and back out causes the phone to reconnect -- you should not have to delete and re-add the profile. I have never had to do that to resolve this. If going into and out of Airplane mode restores the link then you're seeing a manifestation of the network blocking problem which I believe is related to people experiencing crashes.
05-12-2013 09:31 PM - edited 05-12-2013 09:33 PM
Thanks, tickerguy. I'll try that next time, though I have to (again) stress that I may not know when it fails the next time because the OS doesn't tell me when it fails and silently disables the profile. I don't mind that the profile occasionally fails. I just think it should not be disabled without notification. Of course, if you can guarantee that connection attempts will never fail then silently disabling would not be so much of an issue.
(BTW, I said I would try deleting the profile only because Capt Sweatpants suggested.)
Yes, I can manually get it to retry but, let's see how many steps that takes:
If it were a simple one or two step process to re-enable and retry I wouldn't mind so much.
05-12-2013 09:55 PM - edited 05-12-2013 09:57 PM
All that should not be necessary.
Turn WiFi off and back on. If that does not fix it then turn Airplane Mode on and then back off.
If either of those reconnects then the odds are extremely high that you're seeing a manifestation of what I believe is going on with the deadlock condition and it is not your WiFi network that is failing to associate. Indeed, if you could see "inside" your WiFi Access Point at the software level (where you can actually see what state the unit is in with regard to your device) you would likely find that it thinks the phone IS associated with it.