Join now - be part of our community!

Wifi authentication problem after upgrading to Android 6.0

charlescheng
Visitor

Wifi authentication problem after upgrading to Android 6.0

I have just upgrade to Android 6.0 last night for both of my Xperia Z5 Compact and Z5 Premium, and it looks nice.

However, when I back to work and try to connect to company Wifi network today, it keeps showing "Connecting..." under the SSID for very long time, and ultimately showing "Authentication problem".  The SSID I connect to using PEAP-MSCHAPV2 authentication, I am sure that my username and password is correct as I was using this the day before, as well as using other mobile devices.  When I try to some SSID using common WPA2-PSK authentication, it works properly.  Therefore, it shouldn't be the problem on the hardware side.

Since I'm not able to do a factory reset currently due to many data instead, does anyone have similar problem or suggest a work around for this problem?

Thank you very much.

Charles

9 REPLIES 9
profile.country.DK.title
jchristensen
New

Hi,

have you tried a simple restart?

charlescheng
Visitor

A simple restart?

Yes, I did.  By the way, I have exactly the same problem in both of my Z5 Comapct and Z5 Premium after upgrading to Android 6.0 Marshmallow.

Having said that, I have to give credit to Sony that this is the only problem I am experiencing after 2 days, and the battery life is amazing after the upgrade.  It's now very close to the performance of my previous Z3 compact with nearly 2 days battery life, and the phone is now much more responsive.

Anyway, it would be very great to have a solution to this Wifi authentication problem, thanks guys!

Charles

thesiner
Visitor

Hi!

I have the same problem, with 802.1x-peap-mschapv2(phase 2) auth.

With adb shell following i see next messages:

18.03.2016	11:02:06.880	31144	31144	I		wpa_supplicant	 p2p-dev-wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
18.03.2016	11:02:06.912	1813	2902	D		WifiStateMachine	 shouldSwitchNetwork  txSuccessRate=0,00 rxSuccessRate=0,00 delta 1000 -> 1000
18.03.2016	11:02:06.918	1813	2902	D		WifiStateMachine	 CMD_AUTO_CONNECT sup state ScanState my state DisconnectedState nid=29 roam=3
18.03.2016	11:02:06.918	1813	2902	E		WifiConfigStore	 saveWifiConfigBSSID Setting BSSID for "mydomain-a"-WPA_EAP to any
18.03.2016	11:02:06.918	1813	2902	E		wifi_gbk2utf	 g_pItemList is NULL
18.03.2016	11:02:06.946	31144	31144	I		wpa_supplicant	 wlan0: Trying to associate with SSID 'mydomain-a'
18.03.2016	11:02:06.946	1813	2902	E		WifiConfigStore	  rewrite network history for "mydomain-a"-WPA_EAP
18.03.2016	11:02:07.094	31144	31144	I		wpa_supplicant	 wlan0: Associated with 00:1f:45:94:36:e0
18.03.2016	11:02:07.094	31144	31144	I		wpa_supplicant	 wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
18.03.2016	11:02:07.101	31144	31144	I		wpa_supplicant	 wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
18.03.2016	11:02:07.102	31144	31144	I		wpa_supplicant	 wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
18.03.2016	11:02:07.111	31144	31144	I		wpa_supplicant	 wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=ise2.mydomain' hash=0b06228c7436ecfb956923c54f44fd5309841da8285fcc3de9869dba4964e6d7
18.03.2016	11:02:07.116	31144	31144	I		wpa_supplicant	 wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=ise2.mydomain' hash=0b06228c7436ecfb956923c54f44fd5309841da8285fcc3de9869dba4964e6d7
18.03.2016	11:02:07.153	31144	31144	I		wpa_supplicant	 EAP-MSCHAPV2: Authentication succeeded
18.03.2016	11:02:07.579	31144	31144	I		wpa_supplicant	 wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
18.03.2016	11:02:09.304	31144	31144	I		wpa_supplicant	 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1f:45:94:36:e0 reason=2
18.03.2016	11:02:10.384	1813	2903	D		WifiService	 Client connection lost with reason: 4
18.03.2016	11:02:11.136	1813	3578	D		WifiService	 acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 binder=android.os.BinderProxy@fed44e7}
18.03.2016	11:02:11.212	1813	3578	D		WifiService	 releaseWifiLockLocked: WifiLock{NlpWifiLock type=2 binder=android.os.BinderProxy@fed44e7}

wpa_supplicant CTRL-EVENT-DISCONNECTED reason=2 is WLAN_REASON_PREV_AUTH_NOT_VALID

Is SONY support read this forum?

thesiner
Visitor

New log with debug enabled

http://pastebin.com/W4UNxxUj

charlescheng
Visitor

Thanks thesiner for the contribution.  Not sure if Sony is aware of the problem reporting right now?

It's always good to have a response or at least an acknowledgement no matter what status it is; otherwise, I guess they are not interested in this topic, or don't think that it's a problem at all.

When I have time, I will try to backup Z5 Premium and perform a factory reset to see if it's solved, will let you know.

Charles

thesiner
Visitor

On Xperia z2 I have the same problem after update to Android 6 beta release. On z2 and z5 with Android 5.1 all worked. After updating to 6.0 I have a problem with wpa supplicant on both devices.
Rickard
Master

I'm sorry to hear this Slightly_frowning_Face

Would it be possible for you to take a log from your phone with Wi-Fi verbose logging enabled and send it to me?

To do this:
Settings > About phone > Build number, tap 7 times on the build number
Go back and select Developer

Turn on "USB debugging"

Turn on "Enable Wi-Fi Verbose Logging"
Try to connect to the network
Settings > Developer options, select "Take bug report". When the report is ready share (may take a minute or so) you get a notification that you can tap and share to Google Drive. Please send me a link to this file in a private message.

charlescheng
Visitor

Rickard, please check your Private Message inbox, thank you.

philieee
Visitor

Hey,

I have exactly the same problem with my Z5 compact (android 6.0). I did the update last weekend and in several private wifi networks everything works fine, but in my company's wifi network I get no connection (same thing as mentioned above, long time "connecting..." and then "Authentication problem". The SSID also uses PEAP authentication.

I already tried to enable the old DHCP client in the developer options, which was suggested in another thread, but it didn't help and I did a reset of my network connections with no result....

I'm going to get the log tomorrow and then upload it, if it's of any help....

Thanks a lot

Philipp