[android] Nexus 4 / Lollipop wiFi Issue

[Cache]

Hi all

 

Just wondering if anyone else with a Nexus 4 which updated to Lollipop via OTA is having issues with wifi? At home it works fine, at work it seems to refuse to connect with an exclamation mark next to it. If I forget the wireless network and reconnect then it works fine for the rest of the day. Come back in the next day and the same issue.

 

I'm not 100% sure if it's to do with the different types of AP's which we have around school and it just refusing to connect, but it seems once it refuses to connect it won't connect to any until it's forgotten.

 

Anyone have a solution other then forgetting it and reconnecting?

[Arthur]

Sounds a bit like this bug...

 

https://code.google.com/p/android/issues/detail?id=78702

 

Does giving the phone a static IP make any difference (either via DHCP or on the Nexus 4 itself)?

Edited December 2, 2014 by Arthur

[Cache]

Will give the static IP a shot tomorrow, cheers

[Tallwood_6]

I'm seeing this on my nexus 5 and lollipop at work, very annoying but enabling and disabling the wifi will usually get it working.

[Cache]

Meant to reply back to this, Static IP has resolved the issue.

 

Not ideal, but solves the issue, cheers! Now to wait for 5.0.1 to arrive...

Edited December 8, 2014 by Cache

[caffrey]

5.0.1 Nexus 4 OTA images are out, I just sideloaded mine this morning - I'll check when I get to school if its working fine

[Arthur]

I think this must be the Wi-Fi bug that's fixed in 5.0.1...

 

https://android.googlesource.com/platform/external/wpa_supplicant_8/+/android-5.0.1_r1 (Full Changelog)

 

Work around AP misbehavior on EAPOL-Key descriptor version

 

It looks like some APs are incorrectly selecting descriptor version 3

(AES-128-CMAC) for EAPOL-Key frames when version 2 (HMAC-SHA1) was

expected to be used. This is likely triggered by an attempt to negotiate

PMF with SHA1-based AKM.

 

Since AES-128-CMAC is considered stronger than HMAC-SHA1, allow the

incorrect, but stronger, option to be used in these cases to avoid

interoperability issues with deployed APs.

 

This issue shows up with "WPA: CCMP is used, but EAPOL-Key descriptor

version (3) is not 2" in debug log. With the new workaround, this issue

is ignored and "WPA: Interoperability workaround: allow incorrect

(should have been HMAC-SHA1), but stronger (is AES-128-CMAC), descriptor

version to be used" is written to the log.

 

Bug: 18411110

[caffrey]

Well on my nexus 4 the open guest network and the wpapsk work okay but the wpaeap network isn't, then again it's mainly nexus 5s here that are having the most issues