Database Info

WPA2-Enterprise problems on Android 2.2

Hello
You see, I have been a time I've tried connecting to WPA2-Enterprise network, but since I tried Android 2.2 has been impossible, because you never get to connect when the connection requires a certificate.
An example is the connection to the university network "eduroam"
Reading information, I found that the problem is given in the version of WPA-supplicant Android 2.2 (And Android 2.2.1).
My question is how one could put another version of WPA-supplicant, or directly replacing the version of Android 2.1 Eclair?
Thank you very much and best regards

snaky90 said:
Hello
You see, I have been a time I've tried connecting to WPA2-Enterprise network, but since I tried Android 2.2 has been impossible, because you never get to connect when the connection requires a certificate.
An example is the connection to the university network "eduroam"
Reading information, I found that the problem is given in the version of WPA-supplicant Android 2.2 (And Android 2.2.1).
My question is how one could put another version of WPA-supplicant, or directly replacing the version of Android 2.1 Eclair?
Thank you very much and best regards
Click to expand...
Click to collapse
If you're rooted, it's in the etc/wifi system folder I believe but yeah I've messed around with my WPA supplicant file when I was running a 1.5 ROM since wince it had bad WPA2 Enterprise support.

Ok, but what I do with that file? File overwrites the file from Android version 2.1?

Quick question for you - is the router broadcasting the SSID?
My Nexus has this issue (as well as others), where if you are NOT broadcasting your SSID, then it won't connect. Try just broadcasting and see what happens.

I try to connect to eduroam, if it shows the SSID.
The problem is when the connection requires certificates.
In Eclair was not present this error.

Help !! please? I can't connect to Eduroam....

[Q] Connecting my Sensation to WPA2-Enterprise wireless network

Hey I am trying to connect my Android device to a WPA2-Enterprise network.
I have exported my CA certificate and changed the extension to *.p12 so that android can import it.
I connected my work laptop and check on the wireless properties it shows the following:
Security Type: WPA2-Enterprise
Encryption type: AES
Authentication Method: Certificate
After I imported my certificate and click on the wireless connection it only provides me with a EAP method, which my laptop does not use because when I switch from certificate to "Microsoft: Protected EAP (PEAP)". Since I don't have password to connect to the WPA2-Enterprise 802.1x wireless, I would imagine it would be the same on my Android device "I tried my phone and tablet"..only using my windows credentials to connect for example domain\username and pw.
Any ideas?
Maybe I need to convert the certificate instead of changing the extension to *.p12?
I tried using Wifi Advanced Editor from the Market but no luck....has anyone run into this type of situation where you use certificates and no EAP?

Anybody???

Sensation - MIUI, various from 1.11.25 to 2.1.13 - EAP Wifi problem
I too have suffered from this problem and dispite looking at various bulletin boards have found no solution. I have tried different kernels, advanced wifi configurator and have the same problem.
Frustratingly it is not always present as an issue, sometimes it will connect and others it will not. If I find any more info, I will update this post

Any update on this, also wanting to connect my Razr to my work network

Any updates on this?

[q] pptp vpn

Tiamat 2.2.2 and Stock 3.2.1 for Xoom WIFI only, the PPTP connection lasts only two (2) minutes. Is this a problem with android? I used tiamat 2.2.1 and earlier versions of android and there was no problem. L2TP works, but significantly slower.. I use vpn to access videos from other countries. Anybody else with same issues or have solution, I don't like to go downgrade firmware.

no PPTP connectivity

When running Gummycharged FE 2.0, I can connect to my PPTP VPN via the Settings or from 3rd party apps, like 5 VPN or 1 VPN.
I have tried to get Humble 5.0 RC2 with Imoseyon 4.0 kernel to connect to PPTP with no success.
I downloaded a tun.ko module I found, and copied it into /system/lib/modules and well as /system/modules (not sure which would work) and rebooted and still cannot connect the the VPN.
Does anybody have any advice? Interestingly, one of the features in the new OTA update is that IPsec VPN functionality was added, so I'm guessing that it should work fine if I'm on stock.
Also, I'm guessing that stock and future builds based on EP4D should have working PPTP.
Any thoughts, i would love to enable PPTP on EP4P, if possible. If, not I guess thats the way it goes. Interestingly, my Gummcharged FE 2.0 setup just prompted me for the OTA.

[Q] Support for ad-hoc

I have a 3G Xoom (umts_everest) without a SIM card (yeah, it's dumb. It's a long story).
I'm currently on Codename Android 1.5.5 (ICS 4.0.3), but I accept suggestions if it can solve my problem.
Has anyone successfully connected to an ad-hoc connection? I'm trying to tether my Samsung Galaxy Spica (old warrior!) via any tethering app available but my Xoom won't see the network. I used to do that using Froyo's regular Hotspot feature, but this is not available on my current ROM on the Spica (the only usable ROM I've found), so I have to use one of these tethering apps.
Doing some research I found that ICS does not support ad-hoc natively, so has anyone released a ROM/patch to work this out? I found some topics for the Adam (none for the Xoom), even tried one of the wpa_supplicant from one, but no luck.

No need to modify wpa_supplicant binary
I changed data/misc/wifi/wpa_supplicant.conf instead of wpa_supplicant. I added ap_scan=2, then set the adhoc network to
priority=1
mode=1
then pushed back the modified file. chown ownership back to system.wifi.
I had root access through adb. So root wasn't necessary for me.
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other know networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.