Saved Wifi network keeps disabling itself
I've been dual wielding my 9900 and Z10 for more than a week now, evaluating whether to make the transition completely. There are a lot of differences in experience between the two obviously, but not all positive. I'd say
six steps forward two steps back in terms of usability.
However, the biggest difference that affects me consistently is the Z10 Wifi handling. In my hospital environment, we have no cell signal so I depend on Wifi coverage wherever I go. This involves walking between several access points throughout the day. On my 9900 I could just trust that it would always latch onto the next AP and never loose connectivity. However, the Z10 seems to always timeout and fail if switching APs. What's even more annoying is that after several failures in re-establishing, the saved network would disable itself and I would have to manually re enable, sometimes several times before it would successfully reconnect. It is incredibly annoying. Sometimes I would be in just be sitting in one spot and it would disconnect itself from one AP and try to look for another, fail, and then disable the profile again. I don't have time to constantly check my connection and re enable every few minutes, and with the 9900 I could just trust it would constantly hammer away at connecting until it found one. It's quickly becoming a deal-breaker.
Checking inter access point handover makes no difference. This was unchecked with the 9900 anyways.
Anyone else run into this problem?
Posted via CB10
- 02-20-13, 09:33 AM #2
Yes welcome to the club. Our company network Wifi used to work flawlessly and now I'm running into the same problem. Saved Wifi networks show a disable connection. When you click on them it actually shows disabled.
Not sure as to why this is happening but for sure is annoying. Also if I use a hotspot and logged in and lose range it will ask me to reconnect through the hotspot website again. My bold 9780 did that automatically.
I almost wouldn't mind as much if it would simply eventually connect, even if it takes repeated attempts, and not disable the profile on failure. I don't see any logical reason for this; this should be a user-selectable option to not auto-disable.
Posted via CB10
- CrackBerry Addict
02-20-13, 10:38 AM #4
- 682 Posts
I have encountered this problem as well, sometimes even at home. My PlayBook has the same issue from time to time and it's certainly frustrating. Strangely enough, there are times when my gf is over, and her z10 keeps disconnecting from my wifi network (disabled as well) and my z10 wifi is perfect.
Posted via CB10
- 02-20-13, 12:38 PM #6
Both the 9900 and the Z10 are assigned distinct IPs. However, this is a huge hospital so I can't comment on whether or not there would be a conflict with any of the other umpteen number of devices coming and going at any particular time. I'm just a simple doctor who wants the connection always available, no questions asked :P
Examining the Z10 logs, I see various combinations of the following errors around the time I lose/re-attempt a connection: "failed to initiate AP scan", or "wlan_auth_fail:unresponsive_ap", and a lot of "skip - blacklisted (count=2 limit=1)". Of course, the 9900 stays connected throughout this
- 02-20-13, 02:24 PM #8
Ok this is royally p_ing me off. I've had to manually re-enable my work wifi profile about thirty times yesterday. Why on earth would a profile disable itself if it fails to connect? I cannot fathom what purpose that would have except to make life difficult for people. Is this a BB10 OS thing?
Sorry for the rant, but I'm going to leave my Z10 at home if this continues. Not exactly conducive to efficiency.
- CrackBerry Abuser
02-21-13, 09:50 AM #11
- 179 Posts
This is a bad design choice by BlackBerry- they did this on the PlayBook WiFi and it happens with e-mail accounts too!
Basically, what I see happen is that when the device wants to connect to a (WiFi access point, email account, possible other things), it tries to make the connection and if it fails, it retries 3 times, one after the other, and if all three attempts fail, the account or profile is disabled. I can guess that the developer rationale behind this was that if a connection was not available, rather than continually retrying and bombarding the AP or server with requests and using up battery life, it was better to just disable.. The problem is that in reality, radio signals and the internet are not 100% available all the time, and it is quite possible to see a WiFi AP, but not be able to associate (if you're on the fringes of coverage for example), or for an email server to be down temporarily for maintenance, etc, so while retrying first is a good strategy, doing it three times in a row and calling it quits is not.. If you're walking around a building or the server is down for upgrades, it's going to take longer than the 30 seconds that each retry attempt takes, so the result is that the device is always disabling accounts prematurely.. What they need to do is a "progressive backoff"- the first retry takes place right away, then you increase the delay before the next attempt, and increase it even more before the next, etc, so that you keep the number of requests manageable, and maintain battery life.. Then you pick a threshold: an hour, a day, a week, whatever, that you can't connect, and instead of automatically disabling, you notify the user that there might be a problem.
I've also noticed that some of my POP accounts show as 'disabled' once in a while, but email still is received despite this. The disabled account often spontaneously becomes active again without my intervention, which is what I hoped would happen with the wifi profiles, but to no avail.
If this is a design choice ,i agree it is a horrible decision. I'd rather have shorter battery life than have to manually reconnect to every network, otherwise what is the point of having push email.
- CrackBerry Addict
02-21-13, 12:16 PM #13
- 708 Posts
I have been Running into this a lot at work as well. I have handover enabled but it seems that the OS has a hard time with the hand shake when moving from one AP to another. My 9780 just jumps over to the next AP the Z10 seems to think its lost its token then re authenticates. The controller won't give it a new one because it is still authenticated. Boom disabled
Posted via CB10
- 02-24-13, 08:37 AM #15
Has there been a solution found for this issue?
Our office building spans several floors and there are two WPA access points per floor. Throughout the day, as you go to meetings and such, the phone is supposed to invisibly connect to the strongest access point when you get out of range of your old access point. A coworker of mine, so far the sole Z10 owner in or office, has found this wifi disabling quite frustrating as you can imagine. I feel a little bit guilty because this guy was ready to buy a SG3 in December but I told him to wait for Jan 30 before making a decision. Any help would be appreciated.
I spent a good part of my morning with our IT guys to get some real time logs as I walked around the hospital. They're "working with the vendors" to determine what the issue is (APs associating but not authenticating), because apparently they will be upgrading to BES10 afterall. If they give me any follow-up I'll post it.
Still doesn't change the fact that the profiles will disable themselves on failure. Most unhelpful.
Posted via CB10
- CrackBerry Newbie
04-07-13, 06:44 AM #19
- 4 Posts
I also have been experiencing this problem. I believe in an enterprise environment, where WiFi authentication is performed against an ldap server such as Active Directory, the 3 attempts limit is useful to prevent locking out a users AD account, and thus prevent them logging on, as most networks I have seen have their password policy to lockout at above 3. If a user were required to change their password, and then did not update on their phone, their account would soon be locked as the phone would keep trying to authenticate with the old password. A better way to handle this on the phone would be to warn the user the profile had been disabled, and only apply this to access points that use a radius server to authenticate clients. If the access point uses a plain PSK, then the phone should keep trying as its unlikely there is a danger of locking out someone's account.
- 04-07-13, 08:41 AM #20
Well, it's been said that the Playbook OS was a test bed for the Z10's OS. Looks like they brought forward the bugs too. My Playbook does this often, my Bold does not. I will not be upgrading to a BB10 phone any time soon. At this point I think I'll just keep what I have as I have no complaints with my 9300. The ball is in Blackberry's court. Hopefully these things will be ironed out in a more timely fashion than they have on the Playbook.
There are actually two issues here. The first one that initially caused the most annoyance for me was the fact that wifi profiles will automatically disable after several unsuccessful authentication attempts. Apparently by design, it sucks. However, I've noticed now that after some time, say half an hour, a profile that automatically disabled itself will reconnect by itself without requiring me to manually re-enable it. Still completely unacceptable, waiting 30 mins to reconnect instead of having the device hammer away repeatedly until a connection is made is not optimal.
However, in the process of working this out, it appears that the reason for the authentication errors (failing in step 2 of EAP) are the Aruba AP's themselves here at the hospital. We've determined that at the adjacent building (cisco network based) there is no issue with prompty latching on and handing over between APs. Blackberry and the vendors have been working at the problem (it helps that our CEO is a BB fan) and hopefully some good news will come out of this.
- CrackBerry User
04-10-13, 10:13 AM #23
- 26 Posts
Same issue here: My Z10 often disables my work Wi-Fi profile. But it doesn't stop there, I've noticed that when the profile gets disabled it's also re-ordered to 2nd position in my 3 saved profiles. Interestingly, at the same time, the AT&T Wi-Fi profile is raised to the top even if I've disabled and condemned it to the bottom.
It was so much nicer when my 9900 obeyed my simple Wi-Fi wishes! But I'll be patient with my Z10.
I work for a large state university and we use HP APs with WPA2-Enterprise. All APs use the same SSID. On the Z10, IPv6 and Inter-AP Handover are off because I haven't seen any difference when they're on.
- CrackBerry Newbie
05-02-13, 10:48 PM #25
- 1 Posts
Aaaaarrrrrggggghhhhh... It is a little comforting to know others are suffering the same frustration. My 9800 was ROCK SOLID. I know many other people had issues with that phone, but 3yrs and a TON of usage and no issues. So I upgrade, rather willingly, but this ONE issue (other minor ones) is driving me mad. Oddly, those experiencing it on their Playbook, is an issue I have NOT seen it on my Playbook, but EVERY frikin' day on my Z10.
Rant and Vent over.
- By dee.dubya in forum BlackBerry PlayBookReplies: 27Last Post: 06-29-15, 11:34 PM
- By endo4ryan in forum BlackBerry PlayBookReplies: 51Last Post: 03-18-13, 11:26 PM
- By svelt in forum BlackBerry PlayBookReplies: 14Last Post: 08-10-12, 01:09 AM
- By mitelman in forum BlackBerry PlayBookReplies: 2Last Post: 05-31-12, 10:57 PM
- By jhimmel in forum BlackBerry PlayBookReplies: 6Last Post: 06-01-11, 07:11 AM