Not tryin to argue but how could it be the router settings if it worked like a champ before I installed cm9?
My roomate is out of town on business. So when he gets back what should we change on the settings?
With WiFi, each device and operating system handle security on the router differently. CM7 & CM9 while similar in that they're basic builds of android, are still very different.
The command lines for when and how a security key is sent to the router are handled in a different manner. They're also recognized by the router differently when they respond.
In this example, this is CM9 base code, wifi set for enterprise security:
public class EnterpriseField {
private String varName;
private String value;
private EnterpriseField(String varName) {
this.varName = varName;
this.value = null;
}
public void setValue(String value) {
this.value = value;
}
public String varName() {
return varName;
}
public String value() {
return value;
}
}
/** {@hide} */
public EnterpriseField eap = new EnterpriseField("eap");
/** {@hide} */
public EnterpriseField phase2 = new EnterpriseField("phase2");
/** {@hide} */
public EnterpriseField identity = new EnterpriseField("identity");
/** {@hide} */
public EnterpriseField anonymous_identity = new EnterpriseField("anonymous_identity");
/** {@hide} */
public EnterpriseField password = new EnterpriseField("password");
/** {@hide} */
public EnterpriseField client_cert = new EnterpriseField("client_cert");
/** {@hide} */
public EnterpriseField private_key = new EnterpriseField("private_key");
/** {@hide} */
public EnterpriseField ca_cert = new EnterpriseField("ca_cert");
/** {@hide} */
public EnterpriseField[] enterpriseFields = {
eap, phase2, identity, anonymous_identity, password, client_cert,
private_key, ca_cert };
As you can see there are a bunch of commands that need to happen on the OS side before a sync can happen with your wifi router. Any variation here, can cause the enterprise security to boot the command back that there's a verification issue, like you're seeing.
The CM7 build, actually uses a completely different set of command structures than CM9, as in the way it processes each separate type of security (WEP, WPA, WPA2...etc).
So CM7 is going to act different than CM9, and vice versa.
Same with your router, in that with CM7, it could have been identifying your device as a standard wifi device, like another computer. When CM9 comes in, if the router is not updated with the best firmware, it may not recognize the new OS that your phone has. It also may be looking for a different log sequence from the phone in WEP or WPA or WPA2 securities. Hence the suggestion of messing with the router to see if a different security setting might work better than the other.
It also could be that because the first failed attempt by CM9 didn't verify correctly, the router could be blocking access entirely, because it thinks it's an intruder trying to take command of the router, and has blocked your phones IP or MAC address from connecting. I've seen this on some high end enterprise type routers in the past. They're security measures, that allow the router to automatically protect against bandwidth pirates, just looking to use your internet.
In order to truly figure out what's going on with all of this, you need to have admin privileges on the router, to access the logs of what is occurring when you're trying to connect to the router. Once you have the logs, you can then identify if the security type is the issue, or the MAC filter is the issue, or some other setting that may be causing your problem.
Or if the phone in general is just not catching at the correct time.
Without having those logs, there's not much anyone can tell you here on getting it fixed, unless there's a new update where the WiFi commands are changed, but those haven't been touched in 21 days according to Github. So I don't think you're going to get an update on wifi connectivity through the nightlies at this point, because it's not a main issue.
More pressing is solving the data switching from 4G to 3G & on reboot, and then the video codecs & bluetooth audio issues.
Those are more relevant to making this a truly daily driver for most users.
I hope this helps.
