Develop Bugs

[GUIDE] GS2 Custom Wi-Fi (Eduroam, PEAP/MSCHAPV2) - GB/ICS

The below guide is targeted mainly for E4GT owners but has been found to help other Samsung devices as well.
In ICS the file has been changed to the standard wpa_supplicant.conf in /data/misc/wifi. However, you cannot just copy the old bcm_supp.conf data in here as the device id has also changed.
For all cases where you see something in < > you need to replace it with your information in quotes. Example "MySSID", etc.
ICS Sample
Here's what's working as of now on FD26 (11:40 CDT - Restored P2P parameters):
Note: As of FE14 please remove the eapol_flags=2 as it caused a bootloop issue.
Code:
ctrl_interface=wlan0
driver_param=use_p2p_group_interface=1
update_config=1
device_name=Wireless Client
manufacturer=Samsung Electronics
device_type=1-0050F204-1
p2p_listen_reg_class=81
p2p_listen_channel=1
p2p_oper_reg_class=81
p2p_oper_channel=11
[B]ap_scan=2
country=US[/B]
network={
ssid=[B][I]<SSID>[/I][/B]
scan_ssid=1
key_mgmt=IEEE8021X
group=WEP104 WEP40
auth_alg=OPEN SHARED
eap=PEAP
phase1="peapver=0"
identity=[B][I]<ID>[/I][/B]
password=[B][I]<PW>[/I][/B]
phase2="auth=MSCHAPV2"
[B]eapol_flags=2[/B]
}
GB Sample - bcm_supp.conf
Working Sample for GB/EL29:
Code:
ctrl_interface=eth0
update_config=1
device_name=Wireless Client
manufacturer=Samsung Electronics
device_type=1-0050F204-1
network={
ssid=[B][I]<SSID>[/I][/B]
group=WEP104 WEP40
auth_alg=OPEN SHARED
scan_ssid=1
key_mgmt=IEEE8021X
eap=PEAP
phase1="peapver=0"
identity=[B][I]<ID>[/I][/B]
password=[B][I]<PW>[/I][/B]
phase2="auth=MSCHAPV2"
priority=2
}
Eduroam Users:
Please try adding these two lines first to your configuration file before trying anything:
Code:
ap_scan=2
country=<ISO Country Code - US,GB,DE,FR,etc. - [B]No Quotes[/B]>
Please refer to above for placement. If this does not work then please proceed with modifying network settings as mentioned above.
Thanks to fellow posters, such as kobridge, sfhub and others for continuing to suggest ways to keep poking at this!

Did you have a chance to check /system/etc/wifi/wpa_supplicant.conf?

/system/etc/wifi/wpa_supplicant.conf
I'm guessing this is the template version that builds when not found:
Code:
[email protected]:/system/etc/wifi # cat wpa_supplicant.conf
cat wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
p2p_listen_reg_class=81
p2p_listen_channel=1
p2p_oper_reg_class=81
p2p_oper_channel=11

GB bcm_supp.conf
And for comparison here's my bcm_supp.conf before I went to ICS:
Please ignore the name bcm_good.conf as I always keep a good copy in /sdcard.
Code:
[email protected]:/system/etc/wifi # cat /sdcard/bcm_good.conf
cat /sdcard/bcm_good.conf
ctrl_interface=eth0
update_config=1
device_name=Wireless Client
manufacturer=Samsung Electronics
device_type=1-0050F204-1
network={
ssid="yyyyyyyyyy"
psk="yyyyyyyyyyyy"
key_mgmt=WPA-PSK
priority=1
}
network={
ssid="xxxxxxxxx"
group=WEP104 WEP40
auth_alg=OPEN SHARED
scan_ssid=1
key_mgmt=IEEE8021X
eap=PEAP
phase1="peapver=0"
identity="[email protected]"
password="xxxxxxxxxxxxxxx"
phase2="auth=MSCHAPV2"
priority=2
}
Just for kicks I tried renaming and dropping this one in as wpa_supplicant.conf - no change.

Not sure if you checked this thread - http://forum.xda-developers.com/showthread.php?t=1369856
I think it's the same issue.

A driver change would explain why the path changed as well - but I'm hoping this is a result of the leaks and will be resolved prior to OTA. If not then a big reason that I got this will be out.
Will probably pull the TAR for EL29 and see if I can find any differences... will pass on my findings here.
*Edit* OK, can't pull the ODIN .tar files where I'm at so I'll see if I can find it in Calk's EL29 build for now.
*Update 2* Driver dhd.ko is in the modem. Now I asked this before and supposedly modems are interchangeable. Will check again on using a GB modem with ICS but if good will try flashing EL29 modem and see if it fixes. Also changed /system/etc/wifi to EL29 contents.

Results #1
OK, here's what I did:
1) Replace /system/etc/wifi contents from FC22 with EL29 contents. (Includes 2 remounts to change to rw and back to ro)
2) Used ODIN to flash EL29 modem to replace driver.
3) Created /data/wifi directory and copied EL29 bcm_supp.conf there.
Turned back on. wpa_supplicant.conf was still the driver but was being rebuilt from bcm_supp.conf when I removed it. No change.
I just reversed #1 and flashed FC24 modem. I'm going to try rebuilding from scratch and see if it's just something in the config at this point.

Still trying...
Logcat significant events:
Code:
logcat -d
D/WifiService( 1883): setWifiEnabled: true
D/WifiService( 1883): ****************setWifiEnabled(), allowWifi***************
*true
D/WifiP2pService( 1883): P2pDisabledState{ what=131203 when=0 }
D/STATUSBAR-WifiController( 1993): Wifi state = 2
D/CommandListener( 1740): Trying to bring down wlan0
D/CommandListener( 1740): broadcast flag ignored
D/CommandListener( 1740): multicast flag ignored
D/STATUSBAR-WifiController( 1993): Wifi state = 3
D/STATUSBAR-QuickSettingButton( 1993): setActivateStatus(1) - 1:on, 2:off, 3:dim
E/WifiConfigStore( 1883): configuration found for missing network, ignored
D/WifiStatusReceiver( 3959): WIFI_STATE_ENABLED
E/wpa_supplicant( 4690): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/WifiStateMachine( 1883): Failed to set country code US
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-NO-C
I/wpa_supplicant( 4690): wlan0: Associated with
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): EAP-MSCHAPV2: Authentication succeeded
I/wpa_supplicant( 4690): EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Complete
d
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
W/wpa_supplicant( 4690): EAPOL: Failed to set WEP key to the driver.
More digging appears to indicate that this happening a lot with the 3.0 kernel - some fixes are out there for other Sammy devices. Again, hope that this is just a leak issue and that they will address this before OTA.
I'll post any more relevant updates as I get them.

Morning Update
Since it looks like this thread got quite a bit of reading I figure it wouldn't hurt to post an update.
First off, Wi-fi itself on FC24 radio and updated wpa_supplicant.conf is working fine for WPA-PSK. I've also ruled out the p2p comments in the configuration as these are part of the expanded support in the 3.0 kernel.
So I'm back to something with the driver and still trying to figure it out. Guess since Android never properly supported this PEAP/MSCHAPV2 configuration without editing (at least in my experience) it can't be affecting too many people. If anyone has a contact in Samsung you may want to pass this on to them and ask them to look at it.

I have not seen a problem with my WPA2 with caukens ICS 1.2

Is that simple WPA2 with password? If so I think I haven't had problems there either - it really seems to be with this WEP layered tunneling.
A little side note - a Cisco guy was in our office a few weeks ago and didn't know about this problem until his tablet couldn't connect to our Wi-Fi. Guess that most people are going away from the multi-layered authentication - at least using this combination.

garwynn said:
Guess since Android never properly supported this PEAP/MSCHAPV2 configuration without editing (at least in my experience) it can't be affecting too many people.
Click to expand...
Click to collapse
Can you direct me to instructions on how to edit this to work with PEAP/MSCHAPV2 in detail on EL29? My work uses this for our secure network and Android phones/tablets have never connected to it very consistently (it will if you sit still, but moving in and out of coverage or AP to AP is a nightmare). I haven't found anyone with much help. I'd love some detailed instructions. WebOS and iOS have figured out how to connect with ease.....just not Android.

mmark27 said:
Can you direct me to instructions on how to edit this to work with PEAP/MSCHAPV2 in detail on EL29? My work uses this for our secure network and Android phones/tablets have never connected to it very consistently (it will if you sit still, but moving in and out of coverage or AP to AP is a nightmare). I haven't found anyone with much help. I'd love some detailed instructions. WebOS and iOS have figured out how to connect with ease.....just not Android.
Click to expand...
Click to collapse
Here's what I did for EL29. You'll need to be rooted to do this:
1) Start ADB debug and type in SU to get superuser access.
2) cd /data/wifi
3) cat bcm_supp.conf > /sdcard/bcm_backup.conf
(Change from this command prompt window back to Windows)
4) Now use a hex editor to modify that file and add the following:
Code:
network={
ssid="[B]<Add SSID Here>[/B]"
group=WEP104 WEP40
auth_alg=OPEN SHARED
scan_ssid=1
key_mgmt=IEEE8021X
eap=PEAP
phase1="peapver=0"
identity="[B]ID here, usually network ID[/B]"
password="[B]Enter password here,normally network password[/B]"
phase2="auth=MSCHAPV2"
priority=[B]Use last number not assigned in other networks.[/B]
}
Save this as a file bcm_good.conf on the USB storage. (11GB partition)
Note: I have had it work sometimes by editing in Notepad, but I notice the hex editor always works. Line breaks appear to be the difference - you'll see a hex value 090A I believe between each line.
5) (On Phone) Turn off Wi-Fi now to replace the config file.
If you mounted the USB mass storage please also end this.
Now back to ADB Shell window:
6) rm bcm_supp.conf
7) cat /sdcard/bcm_good.conf > bcm_supp.conf
8) chmod 660 bcm_supp.conf (reset permissions)
9) chown system.wifi bcm_supp.conf (reset ownership)
Restart Wi-Fi and confirm connection. If it doesn't connect here you may need to tweak the settings slightly.
And for reference if anyone wants to know what options are in wpa_supplicant you can find them HERE. This does not include the p2p additions made available in the new 3.0 kernel.
Hope this helps! Good luck!

Worked great! Very detailed instructions. You rock!
Sent from my SPH-D710 using XDA

Follow Up
Since my MIL has my phone for a few more weeks I've been researching this further. I haven't found any case of ICS yet where this was working properly. A few posts talked about the MAC address not being correct but I have ruled this out in my case as the MAC address shows just as it always has.
Further searches found reports on Google Code but no fix. I find it hard to believe as devices start switching to ICS that this will remain unsolved.
Anyone that has experience with the Linux 3.0 kernel and/or wifi (particularly PEAP/MSCHAPV2) please feel free to throw in any suggestions to try and get this working again.

*removed - frustrated post*

Weekly Update
Sorry for clogging the thread but figure it doesn't hurt to share these findings. Have received a few PMs asking about this so obviously there are some reading up on it.
I flashed the nodata FD16 yesterday and dumped /system to /sdcard/sysFD16 and then thought more about sfhub's suggestion to check the wpa_supplicant binary. Thought this was in the modem so flashed EL29 modem and then dumped /system again but to /sdcard/sysEL29. Moved both to external_sd and brought the card to work since I can't bring the phone.
Got to work today, checked both out and they seem to match file for file. Dates are different but sizes are identical, which I didn't expect. Guess that means I should try pushing the full EL29 package, dump and compare again. (Will probably back everything up using TB though to save some of the headaches.)
I got to thinking and noticed in /system/etc/wifi the NVRAM_NET.txt file. Are these values are automatically applied when flashing through ODIN? I briefly noticed some values resembling these when looking through either ##DATA# or ##DEBUG# (don't remember which one) and will look again when have time. I know the device id changed in wpa_supplicant.conf, maybe it's looking for the wrong one still?

FD26 Update
As of FD26 I've noticed a new change, may have been since FC24 but wasn't able to test it at work.
The scan completes but now it doesn't even attempt to connect to the network! It seems like I've taken a step backwards
*Edit*
Found the problem - was failing due to the WPA-EAP in the key_mgmt section. That got me back to where I was.
Played around with it a little more and finally success! I'm on my network at work!
I'll be posting updates as I reintroduce the p2p strings, so long as they play nice.

Updated first post with a note covering FE14 and later (as of FE16).

HI,
In my case, i put
network={
ssid=<SSID>
scan_ssid=1
key_mgmt=IEEE8021X
group=WEP104 WEP40
auth_alg=OPEN SHARED
eap=PEAP
phase1="peapver=0"
identity=<ID>
password=<PW>
phase2="auth=MSCHAPV2"
eapol_flags=2
}
But, if you put <, dont work, you need put "
network={
ssid="SSID"
scan_ssid=1
key_mgmt=IEEE8021X
group=WEP104 WEP40
auth_alg=OPEN SHARED
eap=PEAP
phase1="peapver=0"
identity="ID"
password="PW"
phase2="auth=MSCHAPV2"
eapol_flags=2
}
This way it work´s....
Thanks so much for your help

JB 4.1.2 ROM has bugs in WiFi

I tried both ROM which using latest 4.1.2 JellyBean, but found bugs when connecting wifi. It's always obtaining ip address..
But sometimes, it can get ip.. toggling wifi on/off cannot success connecting.
Here's the logcat, hope some experts here can give me solutions
As I'm now very dissapointed why some people not getting this problem..
Code:
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
I/wpa_supplicant(29520): wpa_supplicant v2.0-devel-4.1.2 2012-11-26/18:22:02
E/wpa_supplicant(29520): Can't open default ap file
I/wpa_supplicant(29520): rfkill: Cannot open RFKILL control device
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
I/p2p_supplicant(29523): wpa_supplicant v2.0-devel-4.1.200
I/wpa_supplicant(29520): State: DISCONNECTED -> SCANNING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00
I/wpa_supplicant(29520): Scan requested (ret=0) - scan timeout 10 seconds
I/wpa_supplicant(29520): nl80211: Received scan results (2 BSSes)
I/wpa_supplicant(29520): Trying to associate with F4.7C.2A (freq=2412 MHz rssi=-50dBm)
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): ASSOC when wpa_state = 3, do_assoc = 0, reassociate = 0
I/wpa_supplicant(29520): State: SCANNING -> ASSOCIATING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=F4.7C.2A
I/wpa_supplicant(29520): Start Assoc status = [0] !!!!!
W/wpa_supplicant(29520): wlan0: Failed to initiate AP scan
E/wpa_supplicant(29520): wlan0: Not associated - Delay processing of received EAPOL frame !!!!
I/wpa_supplicant(29520): State: ASSOCIATING -> ASSOCIATED
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=F4.7C.2A
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): Associated with F4.7C.2A
I/wpa_supplicant(29520): State: ASSOCIATED -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=8 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): WPA: Key negotiation completed with F4.7C.2A [PTK=CCMP GTK=CCMP]
I/wpa_supplicant(29520): State: GROUP_HANDSHAKE -> COMPLETED
I/wpa_supplicant(29520): CTRL-EVENT-CONNECTED - Connection to F4.7C.2A completed (auth) [id=0 id_str=]
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=9 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/dhcpcd (29551): dhcp main start
I/dhcpcd (29551): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (29551): bssid match
E/DhcpStateMachine( 2529): DHCP failed on wlan0: Timed out waiting for DHCP to finish
I/dhcpcd (30384): dhcp main start
I/dhcpcd (30384): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (30384): bssid match

hendry said:
I tried both ROM which using latest 4.1.2 JellyBean, but found bugs when connecting wifi. It's always obtaining ip address..
But sometimes, it can get ip.. toggling wifi on/off cannot success connecting.
Here's the logcat, hope some experts here can give me solutions
As I'm now very dissapointed why some people not getting this problem..
Code:
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
I/wpa_supplicant(29520): wpa_supplicant v2.0-devel-4.1.2 2012-11-26/18:22:02
E/wpa_supplicant(29520): Can't open default ap file
I/wpa_supplicant(29520): rfkill: Cannot open RFKILL control device
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
I/p2p_supplicant(29523): wpa_supplicant v2.0-devel-4.1.200
I/wpa_supplicant(29520): State: DISCONNECTED -> SCANNING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00
I/wpa_supplicant(29520): Scan requested (ret=0) - scan timeout 10 seconds
I/wpa_supplicant(29520): nl80211: Received scan results (2 BSSes)
I/wpa_supplicant(29520): Trying to associate with F4.7C.2A (freq=2412 MHz rssi=-50dBm)
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): ASSOC when wpa_state = 3, do_assoc = 0, reassociate = 0
I/wpa_supplicant(29520): State: SCANNING -> ASSOCIATING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=F4.7C.2A
I/wpa_supplicant(29520): Start Assoc status = [0] !!!!!
W/wpa_supplicant(29520): wlan0: Failed to initiate AP scan
E/wpa_supplicant(29520): wlan0: Not associated - Delay processing of received EAPOL frame !!!!
I/wpa_supplicant(29520): State: ASSOCIATING -> ASSOCIATED
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=F4.7C.2A
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): Associated with F4.7C.2A
I/wpa_supplicant(29520): State: ASSOCIATED -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=8 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): WPA: Key negotiation completed with F4.7C.2A [PTK=CCMP GTK=CCMP]
I/wpa_supplicant(29520): State: GROUP_HANDSHAKE -> COMPLETED
I/wpa_supplicant(29520): CTRL-EVENT-CONNECTED - Connection to F4.7C.2A completed (auth) [id=0 id_str=]
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=9 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/dhcpcd (29551): dhcp main start
I/dhcpcd (29551): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (29551): bssid match
E/DhcpStateMachine( 2529): DHCP failed on wlan0: Timed out waiting for DHCP to finish
I/dhcpcd (30384): dhcp main start
I/dhcpcd (30384): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (30384): bssid match
Click to expand...
Click to collapse
Why are you posting this here when you've already posted it in the Omega 8 thread? This is not the place to be posting it. I'm not seeing any wifi problems.

I want some experts here can give me solutions on what's wrong with my device.. so everybody can see
My friend also never got problem using 4.1.2 based ROM. I think maybe the structure android files on my devices has invalid permission access or something else i dont know.. That's why i want to get any explanation on this..
Here i added more logcat debug data
Code:
I/WifiManager( 2820): setWifiEnabled : true
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): setWifiEnabled: true pid=2820, uid=10092
I/WifiHW ( 2529): module is semco
E/WifiHW ( 2529): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2529): Start Check B2 #######
I/WifiHW ( 2529): wifi_trigger_poke : Found 4334B3
I/WifiHW ( 2529): ==========[WIFI] SEMCO MODULE ===========
D/WfdService( 2529): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-WifiQuickSettingButton( 2820): Wifi onReceive(2)
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
D/WifiP2pService( 2529): P2pDisabledState{ what=131203 }
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
E/WifiHW ( 2529): supplicant_name : p2p_supplicant
D/WifiP2pService( 2529): Supplicant start successful
D/WifiP2pService( 2529): P2pEnablingState
E/WifiHW ( 2529): Unable to open connection to supplicant on "/data/misc/wifi/sockets/p2p0": Connection refused
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-WifiQuickSettingButton( 2820): Wifi onReceive(3)
D/WfdService( 2529): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/WifiP2pService( 2529): P2pEnablingState{ what=143378 }
D/WifiP2pService( 2529): DefaultState{ what=143378 }
E/WifiP2pService( 2529): Unhandled message { what=143378 }
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): startScan: false pid=31094, uid=10027
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): startScan: false pid=3240, uid=10031
D/WifiNative( 2529): callSECApiBoolean - ID [13]
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
D/WifiNative( 2529): callSECApiVoid - ID [50]
D/WfdService( 2529): intent recieved android.net.wifi.STATE_CHANGE
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
E/WifiP2pStateTracker( 2529): getNetworkInfo : NetworkInfo: type: WIFI_P2P[], state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.STATE_CHANGE
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiP2pService( 2529): P2pEnablingState{ what=147457 }
D/WifiP2pService( 2529): P2p socket connection successful
D/WifiP2pService( 2529): P2pEnabledState
D/WifiP2pService( 2529): sending p2p connection changed broadcast
I/STATUSBAR-QuickSettingButton( 2820): action: android.net.wifi.p2p.STATE_CHANGED
E/WifiStateMachine( 2529): BroadcastReceiver : WIFI_P2P_STATE_CHANGED_ACTION is : android.net.wifi.p2p.STATE_CHANGED
D/WfdService( 2529): intent recieved android.net.wifi.p2p.STATE_CHANGED
D/WfdService( 2529): intent recieved android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WfdService( 2529): onReceive << WIFI_P2P_CONNECTION_CHANGED_ACTION
D/WfdService( 2529): WIFI_P2P_CONNECTION_CHANGED_ACTION >> isConnected() false
W/WifiP2pStateTracker( 2529): WifiP2pStateReceiver : android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WifiP2pService( 2529): DeviceAddress: 3a:76:f1
D/WifiP2pService( 2529): InactiveState
D/WifiP2pService( 2529): InactiveState{ what=147462 }
D/WifiP2pService( 2529): P2pEnabledState{ what=147462 }
D/WfdService( 2529): intent recieved android.net.wifi.p2p.THIS_DEVICE_CHANGED
D/WfdService( 2529): WIFI_P2P_THIS_DEVICE_CHANGED_ACTION arrived
D/WifiP2pService( 2529): DefaultState{ what=147462 }
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.STATE_CHANGED
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive(), Action : WifiP2pManager.WIFI_P2P_CONNECTION_CHANGED_ACTION, isConnected() == false
D/WifiDirectBR( 5039): stopServiceTest : false

try installing this modem LJ2 http://www.mediafire.com/?9wfmm51c87b2bwn

I think the problem lies in the modem/router software, it only is a problem on specific routers. I haven`t had a issue yet so far.

Flash the official stock 4.1.2 polish release that must came out. Check it out, may solve your problem!

I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?

If this is the bugs on 4.1.2 ROM, we should report it to samsung, so they can fix this bugs on the next build of the ROM..
Also custom rom developer should patch their ROM to avoid this bugs..

I have same problem with 4.1.1 it is perfect, but with 4.1.2 it has same problems as yours.
---------- Post added at 02:33 PM ---------- Previous post was at 02:16 PM ----------
hendry said:
I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?
Click to expand...
Click to collapse
Can you please attach the /etc/wifi folder from 4.1.1 stock??? I want to fix my wifi problem.
Thanks

hendry said:
I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?
Click to expand...
Click to collapse
Yes your right . i am also facing wifi problem disconcerting in 4.1.2 .. in previous version 4.1.1 working fine

Well i dont have this problem as yours....have a stranger one lol
I have 50 mbits internet speed at home with speed of 5.2 MB/S while just on 4.1.2 speed dont cross 2 or 3 mbits out of 50 mbits while download speed is only 200 to 270 KB/S.....
Sent from my GT-N7100 using XDA Premium HD app

I've some problem with wifi on galaxy tab 3 7.0 (JB 4.1.2)
When connect using hotspot laptop or tethering via other device, my wifi always scanning every 7s. make my battery run out.
I was trying use advance setting (static IP) but still same.
How to solved this problem?

[Q] Wi-Fi network 802.1X EAP 'Password not configured'

Hello there,
I have a strange issue with my 4.2.2 (rooted; unlocked) Galaxy Nexus (GSM)
On my university we use Eduroam, a wi-fi network which uses PEAP authentication with MCHAPV2 Phase 2 auth.
What's going wrong?
When I connect to this network everything works fine until a certain point were Android somehow loses the password.
Code:
D/CommandListener( 124): Setting iface cfg
D/CommandListener( 124): Trying to bring up p2p0
I/wpa_supplicant(14426): wlan0: Trying to associate with 00:1a:1e:15:8d:20 (SSID='eduroam' freq=2412 MHz)
I/wpa_supplicant(14426): wlan0: Associated with 00:1a:1e:15:8d:20
I/wpa_supplicant(14426): wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
I/wpa_supplicant(14426): wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
I/wpa_supplicant(14426): wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
I/wpa_supplicant(14426): wlan0: CTRL-EVENT-EAP-PEER-CERT depth=3 subject='/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root'
I/wpa_supplicant(14426): wlan0: CTRL-EVENT-EAP-PEER-CERT depth=3 subject='/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root'
I/wpa_supplicant(14426): wlan0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=/CN=UTN-USERFirst-Hardware'
I/wpa_supplicant(14426): wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=NL/O=TERENA/CN=TERENA SSL CA'
I/wpa_supplicant(14426): wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=NL/O=Universiteit Utrecht/OU=ICT Service Centrum/CN='
I/ActivityManager( 385): START u0 {act=android.settings.WIFI_SETTINGS flg=0x14000000 cmp=com.android.settings/.Settings$WifiSettingsActivity} from pid 530
D/BluetoothAdapter( 8904): 1110622808: getState() : mService = null. Returning STATE_OFF
I/Choreographer( 8904): Skipped 31 frames! The application may be doing too much work on its main thread.
D/WifiService( 385): setWifiEnabled: true pid=8904, uid=1000
D/BluetoothAdapter( 8904): 1110622808: getState() : mService = null. Returning STATE_OFF
I/ActivityManager( 385): Process org.yoki.android.buienalarm (pid 14014) has died.
I/ActivityManager( 385): Process com.google.android.calendar (pid 14258) has died.
I/ActivityManager( 385): Displayed com.android.settings/.Settings$WifiSettingsActivity: +940ms
I/wpa_supplicant(14426): EAP-MSCHAPV2: Password not configured
I/wpa_supplicant(14426): wlan0: CTRL-REQ-PASSWORD-2:Password needed for SSID eduroam
W/Settings( 670): Setting auto_time_zone has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
D/AlarmManagerService( 385): Kernel timezone updated to -120 minutes west of GMT
What I've already tried
Manually downloading and installing the certificate
Manually adding the wifi as 'hidden network'
Downloading an app, and installing it from there
Using a different kernel with updated Wifi Drivers (AK Rubik r30)
This problem occurs in stock ROM and in PA ROM. With stock kernel and the Fancy Kernel, AL Rubik
Please help me identify the solution to this problem, I've googled AND searched in XDA-forums, but to no avail as of yet.
This problem as been there for a week now, and there was a time were it just worked. (Same phone)
I know no one else on campus with this problem.

Maybe this problem is smaller.
What in essence goes wrong is that Android deletes the password from its wpa_supplicant.conf.
Is this a known issue?
I tried multiple ROM's, my password didn't change between 4.0 and 4.2.2...
Should I try downgrading wpa_supplicant itself?
Code:
network={
ssid="eduroam"
scan_ssid=1
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="<student number>@soliscom.uu.nl"
password="<a password with capitals numbers and special tokens>"
ca_cert="keystore://CACERT_eduroam"
phase2="auth=MSCHAPV2"
}

Bump

no wifi connection with cm 10.2 nightly after board replacement

Samsung replaced the board in my GT-N7100 after the SDS bug struck. eMMC check now reports: Type: V3W00M, FwRev:0x00
Has anybody the same type and managed to get wifi working with 4.3?
Installation of cm-10.2-20130910-NIGHTLY-n7100.zip works but when I set up wifi after the first reboot I'm stuck. The SSIDs are shown correctly, I just can't connect to any and see this in the log:
I/wpa_supplicant( 3111): wlan0: Trying to associate with 94:0c:6d:ee:63:47 (SSID='router' freq=2422 MHz)
I/wpa_supplicant( 3111): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=94:0c:6d:ee:23:12 status_code=1
I/wpa_supplicant( 3111): wlan0: CTRL-EVENT-DISCONNECTED bssid=94:0c:6d:ee:63:47 reason=3 locally_generated=1
I/wpa_supplicant( 3111): wlan0: Trying to associate with 94:0c:6d:ee:63:47 (SSID='router' freq=2422 MHz)
I tried the ROM on another GT-N7100, there it works fine. One difference between the phones is that the repaired one has a MAC address in Murata's range (F0:27:65:00:00:00 - F0:27:65:FF:FF:FF), the old board has a Samsung MAC.

WiFi issues (MJ5 bootloader)

Hi everyone,
My Note 2 suffers from strange wifi issues.
I am running the MJ5 bootloader and tested KitKat ResurrectionRemix and DN3 ROMS;
Oddly, I can't connect to WiFi networks most of the time.
I can activate the WiFi toggle and I can see surrounding WiFi networks but when I try to connect to one of them (protected or not), the device displays "authenticating" and then immediately "Saved, secure".
However, I saw my device once connecting to one of these saved networks from itself but therefore I hadn't any Internet connection.
Any one has faced a similar issue ?
.ant1

ant1fr said:
Hi everyone,
My Note 2 suffers from strange wifi issues.
I am running the MJ5 bootloader and tested KitKat ResurrectionRemix and DN3 ROMS;
Oddly, I can't connect to WiFi networks most of the time.
I can activate the WiFi toggle and I can see surrounding WiFi networks but when I try to connect to one of them (protected or not), the device displays "authenticating" and then immediately "Saved, secure".
However, I saw my device once connecting to one of these saved networks from itself but therefore I hadn't any Internet connection.
Any one has faced a similar issue ?
.ant1
Click to expand...
Click to collapse
Try hurricane.modem changer tool.see if.it will help

tonylee000 said:
Try hurricane.modem changer tool.see if.it will help
Click to expand...
Click to collapse
I tried 4 different modem firmwares without any effect. And I don't see any log entry that could explain the problem on DDMS.
This issue is turning me nuts !
.ant1

Something I noticed : when I try to connect to a Wifi network, the signal strength seems to drop to zero. Maybe the device bellieves the network is not strong enought to be connected to.
But still no answer why I have this problem...

I finally managed to get some interesting logs and it seems my device fails authenticating on my WiFi network. It seems that is fails only on 2.4Ghz networks, not 5Ghz ones. Also I noticed BSSID turns to 00.00.00. Normal ? :
Code:
04-02 22:29:38.713: I/wpa_supplicant(2814): CTRL-EVENT-SSID-REENABLED id=0 ssid="4641425966726565"
04-02 22:29:42.159: I/wpa_supplicant(2814): Trying to associate with 9A.91.34 (SSID='4641425966726565' freq=2462 MHz)
04-02 22:29:42.159: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=00.00.00 SSID=
04-02 22:29:42.784: I/wpa_supplicant(2814): CTRL-EVENT-ASSOC-REJECT bssid=9A.91.34 status_code=1
04-02 22:29:46.994: I/wpa_supplicant(2814): CTRL-EVENT-DISCONNECTED bssid=9A.91.34 reason=3 locally_generated=1
04-02 22:29:46.994: I/wpa_supplicant(2814): CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="4641425966726565" auth_failures=1 duration=10
04-02 22:29:46.994: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00.00.00 SSID=4641425966726565
04-02 22:29:47.004: I/wpa_supplicant(2814): CTRL-EVENT-SSID-REENABLED id=2 ssid="746957696669"
04-02 22:29:47.004: I/wpa_supplicant(2814): Trying to associate with 00.FD.6C (SSID='746957696669' freq=2412 MHz)
04-02 22:29:47.004: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=2 state=5 BSSID=00.00.00 SSID=746957696669
04-02 22:29:47.584: I/wpa_supplicant(2814): CTRL-EVENT-ASSOC-REJECT bssid=00.FD.6C status_code=1
04-02 22:29:57.039: I/wpa_supplicant(2814): CTRL-EVENT-DISCONNECTED bssid=00.FD.6C reason=3 locally_generated=1
04-02 22:29:57.039: I/wpa_supplicant(2814): CTRL-EVENT-SSID-TEMP-DISABLED id=2 ssid="746957696669" auth_failures=1 duration=10
04-02 22:29:57.039: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=2 state=0 BSSID=00.00.00 SSID=746957696669
04-02 22:29:58.054: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00 SSID=

There have been a few reports of.odd behaviour after downgrading from.kitkat. it works ok with kitkat installed yes?
I dont know of a fix but you could try my guide: http://forum.xda-developers.com/showthread.php?t=2700479
originally for people having issue going to 4.3 but the theory would be the same. Cant hurt to.try
ant1fr said:
I finally managed to get some interesting logs and it seems my device fails authenticating on my WiFi network. It seems that is fails only on 2.4Ghz networks, not 5Ghz ones. Also I noticed BSSID turns to 00.00.00. Normal ? :
Code:
04-02 22:29:38.713: I/wpa_supplicant(2814): CTRL-EVENT-SSID-REENABLED id=0 ssid="4641425966726565"
04-02 22:29:42.159: I/wpa_supplicant(2814): Trying to associate with 9A.91.34 (SSID='4641425966726565' freq=2462 MHz)
04-02 22:29:42.159: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=00.00.00 SSID=
04-02 22:29:42.784: I/wpa_supplicant(2814): CTRL-EVENT-ASSOC-REJECT bssid=9A.91.34 status_code=1
04-02 22:29:46.994: I/wpa_supplicant(2814): CTRL-EVENT-DISCONNECTED bssid=9A.91.34 reason=3 locally_generated=1
04-02 22:29:46.994: I/wpa_supplicant(2814): CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="4641425966726565" auth_failures=1 duration=10
04-02 22:29:46.994: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00.00.00 SSID=4641425966726565
04-02 22:29:47.004: I/wpa_supplicant(2814): CTRL-EVENT-SSID-REENABLED id=2 ssid="746957696669"
04-02 22:29:47.004: I/wpa_supplicant(2814): Trying to associate with 00.FD.6C (SSID='746957696669' freq=2412 MHz)
04-02 22:29:47.004: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=2 state=5 BSSID=00.00.00 SSID=746957696669
04-02 22:29:47.584: I/wpa_supplicant(2814): CTRL-EVENT-ASSOC-REJECT bssid=00.FD.6C status_code=1
04-02 22:29:57.039: I/wpa_supplicant(2814): CTRL-EVENT-DISCONNECTED bssid=00.FD.6C reason=3 locally_generated=1
04-02 22:29:57.039: I/wpa_supplicant(2814): CTRL-EVENT-SSID-TEMP-DISABLED id=2 ssid="746957696669" auth_failures=1 duration=10
04-02 22:29:57.039: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=2 state=0 BSSID=00.00.00 SSID=746957696669
04-02 22:29:58.054: I/wpa_supplicant(2814): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00 SSID=
Click to expand...
Click to collapse

tonylee000 said:
There have been a few reports of.odd behaviour after downgrading from.kitkat. it works ok with kitkat installed yes?
I dont know of a fix but you could try my guide: http://forum.xda-developers.com/showthread.php?t=2700479
originally for people having issue going to 4.3 but the theory would be the same. Cant hurt to.try
Click to expand...
Click to collapse
Gonna try that. But FYI both the ROMs with with I have the issue are KK-based (4.4.2)
PS : What's the purpose of the BLPatch ?

tonylee000 said:
There have been a few reports of.odd behaviour after downgrading from.kitkat. it works ok with kitkat installed yes?
I dont know of a fix but you could try my guide: http://forum.xda-developers.com/showthread.php?t=2700479
originally for people having issue going to 4.3 but the theory would be the same. Cant hurt to.try
Click to expand...
Click to collapse
Didn't help
I followed all the steps and reflash but I still can't connect to WiFi networks !

Might not help either but did you try dr ketans Wifi Fix? Http://goo.gl/6NLgkt
the blpatch flashes the dmg1 bootloader over the mj5 bl enabling the dmg1 to be flashed. Cant flash the dmg1 rom over the mj5 bl
ant1fr said:
Didn't help
I followed all the steps and reflash but I still can't connect to WiFi networks !
Click to expand...
Click to collapse

OK. So I followed Dr.Ketan guide to downgrade from MJ5 with the BLPatch and the WiFi Patch.
Now I have a working WiFi connexion. Also I notice that once connected, the WiFi signal strength is always very low even when being close to the antenna. If I disconnect the network, the signal strength comes back to what it should be... Also some acore FC
I think that the problem comes from a missing WiFi driver needed by the MJ5 bootloader. I may have missed one of the pre-MJ5 Samsung update that included new WiFi drivers. Unfortunately it's almost impossible to identify what's missing !
EDIT : False hope ! After few mintues, got disconnected and unable to connect again to any WiFi network
EDIT2 : And back again. Actually I think my device only connectes to 5GHz WiFi networks. Unable to authenticate with WiFi networks working on 2.4Ghz freq band...

EDIT2 : And back again. Actually I think my device only connectes to 5GHz WiFi networks. Unable to authenticate with WiFi networks working on 2.4Ghz freq band...[/QUOTE]
Sorry for this post months after yours, but...Yes, I've had this exact problem for at least a year or so and I have also tried everything. I finally gave up and only use the phone when I just don't need wi-fi. And now I've switched modems in my home and can no longer broadcast in 5ghz, so now I can't even get wi-fi through that.
One other peculiarity I've found is that if you have unsecured wi-fi it will also work. Even on 2.4Ghz. Very strange. So, no help here- just understanding your issue.

beefgalore said:
EDIT2 : And back again. Actually I think my device only connectes to 5GHz WiFi networks. Unable to authenticate with WiFi networks working on 2.4Ghz freq band...
Sorry for this post months after yours, but...Yes, I've had this exact problem for at least a year or so and I have also tried everything. I finally gave up and only use the phone when I just don't need wi-fi. And now I've switched modems in my home and can no longer broadcast in 5ghz, so now I can't even get wi-fi through that.
One other peculiarity I've found is that if you have unsecured wi-fi it will also work. Even on 2.4Ghz. Very strange. So, no help here- just understanding your issue.
Click to expand...
Click to collapse
The problem is the authentication with wpa2 if you change your router at wpa or wep is connecting. I had the same problem with a fritzbox and the solution was this.
Sent from my GT-N7100 using Tapatalk 2

vagsvag said:
The problem is the authentication with wpa2 if you change your router at wpa or wep is connecting. I had the same problem with a fritzbox and the solution was this.
I believe that is one of the many things I've tried in the past, but certainly worth trying again. Of course, it doesn't help when you use other wi-fi spots, but oh well- better than nothing.
Click to expand...
Click to collapse