Cannot connect to PEAP Wireless Network

[Guest Matchstick]

Hi,

I've encountered what appears to be a bit of a problem with this phone.

Whenever I try connecting to a PEAP secured wireless nertwork the Secure Credentials password box appears then after entering that I get a Force Close in com.android.settings. (I can connect to open and PSK secured Wifi without problem.)

I first noticed this in MCR but I've also tried rolling back the ROM and Recovery/Bootloader to stock with the same problem.

Is anyone else seeing this issue as it's a bit of a problem here ?

[Guest tronads]

i don't know if this is related, but on stock and custom roms, I have found that I cannot even see the wireless network that I can run on my old Nokia using Joikuspot. Its not a range thing as its right next to it. My Ipod, and laptops etc can see it without issue, but it just picks up nothing on the Blade. Its fine with my regular home wifi though.

[Guest Simon O]

That issues happens with most Android 2.1 devices.

[Guest Matchstick]

That issues happens with most Android 2.1 devices.

Hmmm I've connected to the same networks with an HTC Hero (1.5 & 2.1), HTC Desire and Samsung Galaxy S without any kind of problem so I would argue that it's not that widespread :lol:

[Guest Matchstick]

Hmmm I've connected to the same networks with an HTC Hero (1.5 & 2.1), HTC Desire and Samsung Galaxy S without any kind of problem so I would argue that it's not that widespread :lol:

Well problem is sidestepped anyway by copying the network sections of my Desire's /data/misc/wifi/wpa_supplicant.conf into the the Blade one.

Cheers

(If anyone wants details on how to set up their Blade to work with the Birmingham University Eduroam and UOBWifi APs drop me a PM)

Edited October 1, 2010 by Matchstick

[Guest ritterkeks]

I want to bring up the thread again to state,

that this is still an actual problem.

like it was mentioned SOMEWHERE in the MCR thread and didnt get resonance:

when you try to connect to a 802.11x network (like the worldwide eduroam networks)

the wireless settings app crashes -> force close

however, the post in the MCR thread contains a useful hint: just create the connection manually.

that worked for me and since adb also does not work for my device,

editing wpa_supplicant.conf would be quite laboriously with the terminal emulator

[Guest puj]

I am having the same problem, forced closes when trying to connect to a network that worked fine with my old nokia. Normal wpa networks are fine though.

Edited October 22, 2010 by puj

[Guest Simon O]

I am having the same problem, forced closes when trying to connect to a network that worked fine with my old nokia. Normal wpa networks are fine though.

Same problem on the Pulse also which makes me think it's an Android 2.1 issue. I believe you have to manually edit the wpa_supplicant.conf file to fix this.

[Guest lpinho]

Hi all,

i can only find the "wpa_supplicant.conf" file in the /etc/wifi/ directory, but I cannot even edit it, although I can see it (using Astro File Manager) if I try to open it I get an error (file not found), the checking the permissions, is doesn't even have the read permissions (maybe that's why an error occurs)

Any help? How can I change the permission level in android? Is there a terminal application for this?

Thanks,

Luis Pinho

Edited October 27, 2010 by lpinho

[Guest lpinho]

@Matchstick:

Even using a terminal inside Blade, I tried to change the permission of the file (wpa...) bu I always get an error "read-only file system".

So, I cannot overwrite it or even read it to check its content...

How did you copied the file into the correct directory?

Thanks

[Guest The Ice Cream Man]

This isn't a MoDaco style fix I know, but I had this issue with my ZTE Blade/Orange San Fransico with Eduroam and installing Wifi Fixer from the Android Market has sorted it out.

[Guest Adrian Smith]

Thanks, manually adding the network fixed it for me (ZTE Blade r4)!

I didn't have this problem on froyo.

[Guest The Ice Cream Man]

Update - Wifi fixer improved things some of the time, but largely it's still shockingly bad and driving me nuts. Does Froyo have the same issue on San Fran/Blade?

Its not hardware as it connects to other networks (pubs, shops, home etc) okay.

Edited December 2, 2010 by The Ice Cream Man

[Guest The Ice Cream Man]

Is there a manual fix I can perform as alluded to above that is detailed somewhere? Can't find one....help appreciated before I smash the phone up.