Database Users

Captivate & 802.1x

I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot

I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!

Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.

I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App

Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App

can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App

This sounds more like your network not being allowing your device rather then the device having an issue.

it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App

designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.

Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.

So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.

Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.

I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network

I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.

jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.

phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:

UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.

As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.

Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App

Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.

[Q] wifi and dhcp issue with 3.1 stock

hi everyone, some days ago I installed the virtuous 1.6, than replaced with a rooted stock 3.1. Since then, when I disconnect from my wifi for a while, getting far away from my router, it happens that coming back into the wifi field the tablet tries to reconnect but after 4 or 5 times it stops trying and tells me the connection is disabled. I see the dhcp service bouncing, no ip assigned. The only solution I've found googlin' around is to rename/delete the file dhcpcd-wlan0.lease in /data/misc/dhcp. It worked. but the issue got back again and again. I wanted to find out the cause and solve the problem once and forever, if possible. It's a pain in the... you know

Here is my topic. There is also one solution to it apart from the one you've found in google (which was probably my topic anyway ).

You're right, it'was your post. I've read it againg but I can't find out which could be the alternatrive solution. Keep in mind that when I got this wrong behaviour the first time obviously I invesitgated the possible causes, and I discovered the inability to retrieve a dhcp IP address either with my wifi router, with my wifi access point 3g and with a tethered connection via Iphone (all of them I normally use when I'm not at office). None of these would work until the uplisted file deletion). Would you be so kind as to suggest me, if you can, the possible solution in more detail (apart from performing a global reset that would be as annoying than deleting the file)
In any case, many tnx for your answer

Currently the common solution is to abandon the leaked 3.1 rom or put up with the bug.
Manually setting DHCP also works but it's usefull only if you'll use the tablet on one wifi. Else it's just a big pain in the arse.

I have same issue with the stock 3.1 rom.
At the end what I did was manually assign IP address for my iPhone's MyWi connection.
It seems mine has no trouble to connect to my home wi-fi network as well as work...

I also get that problem. But now, seems to have fixed it. I have done the followings:
- delete the dhcp lease file
- change the channel of my wifi router to 9 or below
- download the ad-hoc supported wpa_supplicant
Please try if above help you

Help with fixing Wi-Fi

I have reached my wit's end trying to resolve my problems, so I'm posting here for ideas on fixing this, any input is appreciated!
When this started I was on stock, rooted, ICS 4.0.3 and had been for months. My wife has a nexus s with the same config and hers works fine.
Last week, my daughters sidekick 4G stopped having wi-fi internet connectivity. I turned her wi-fi off, then back on and it was fine and has been ever since. Later that night, my nexus did the same thing, the same procedure resolved it. Ever since then, my wi-fi will only work for 1-5 minutes after turning the wi-fi on. This is the only thing I can think of that changed that could have caused this. This was the first night we connected her sidekick to wi-fi.
The wifi symbol is up there, it'll be blue for up to half an hour, but won't have internet connectivity for long. One thing I noticed pretty quickly was that even though the grey wi-fi symbol is there, I can't access the router settings at 192.168.1.1 from the phone. I thought the grey wifi symbol still indicated I was connected to the router still, but it's not working. Each time this happens, I can turn wi-fi off, back on immediately and it'll work for 1-5 minutes. It appears that the more I constantly use it after turning it back on, it seems to maintain connectivity longer.
Last weekend, just after these issues started, I visited my sister and my phone operated on her wi-fi all weekend just fine.
When I came back home, my problems started immediately.
Here's what I've tried in pretty much the order I tried them:
I started by uninstalling avast, facebook, and autostarts
selected "Forget network" in access points screen and reconnected
Factory reset
Wipe dalvik cache & fix permissions
see if it worked without sim card in (it didn't)
flash GB broadcom driver
Switched router channel from 6 to 1
flash stock 2.3.6 (wi-fi problems still present)
flash OTA ICS (still had problems)
flash stock 2.3.6
flash OTA ICS
re-root
Flash PixelROM 1.60 LiteTouch
factory reset router (No wifi problems on using open network and default SSID for 30 minutes!)
resetup WPA Personal security and rename SSID same as before
Worked for another 15 minutes or so after this
flashed stock 2.3.6
flashed OTA ICS
re-rooted
Restored nandroid backup - quit working after this step
Factory reset router - worked for about 15 minutes, I decided I was ok so I setup security and SSID as before, then it quit working again
flashed PixelRom 1.60 LiteTouch
flashed stock 2.3.6
Flashed OTA ICS - THIS time I did not restore my google backups from the cloud, fearing that this was somehow restoring something that was causing me problems. It did not help.
Changed SSID on my router and reconnected phone
I have spent countless hours trying to fix this. I don't believe it's the hardware because the router factory reset seems to help quite a bit, works fine on unencrypted default router settings, and it worked on my sister's wi-fi.
I have nmap and wireshark and have a basic working knowledge of them. I have adb setup and usable on my computer. I also have dd-wrt installed on my router and have for years. Is there any kind of IP or hardware logging I could perform with these tools to help figure out what's going on??? ANY help is GREATLY appreciated!!

Well i'm no expert with any of this, but it sounds more like a router issue.. If both your sidekick and nexus have the same characteristics of failing wifi, it cant be the devices..
If you've already reset your router and it does the same exact thing, maybe it is something wrong with the router itself. You said it connected fine at your sisters house, so it cant be any hardware within the phone.. The only thing I could think of is maybe try a different router in your house to see if it works? If that helps get rid of the connectivity issue, then you can just get a new router and be happy with the wifis

I don't think a *hardware* problem with the router would only affect 1 device connecting to it wirelessly. I would think that kind of issue would affect all devices on the network.
Which makes me wonder if there's a setting on the router that may be causing it somehow, or some combination of packets might somehow cause the router to block my phone.
But again, I'm open to ideas here and I appreciate your input. I think getting another router will be my next step if I don't hear anything better by the time I get my next paycheck.

nevarDeath said:
I don't think a *hardware* problem with the router would only affect 1 device connecting to it wirelessly. I would think that kind of issue would affect all devices on the network.
Which makes me wonder if there's a setting on the router that may be causing it somehow, or some combination of packets might somehow cause the router to block my phone.
But again, I'm open to ideas here and I appreciate your input. I think getting another router will be my next step if I don't hear anything better by the time I get my next paycheck.
Click to expand...
Click to collapse
Ohh, I thought you had said that both the sidekick and nexus were having problems connecting. My bad.
But yeah have you changed any settings on it lately? Or messed with anything related to the router? Some setting may be kicking your device off after 5 mins, maybe some frequency setting or something dumb like that, I have no clue.
I know how it feels to have funky wifi, so I was only trying to help. good luck

Have you removed DD-WRT from your Wireless Router and back to stock OS? I had a Linksys router with DD-WRT and after about 3 years it started working so weird it became useless with any device. Had to buy a new one.
BTW, are other devices connecting fine to this router?
As swamp goblin stated, I would try with a new router.

It sounds like an issue on your router (or AP) with mixed client settings. I have had this issue with an old Netgear AP.
Try forcing "WPA2 with AES only" if all clients support it, otherwise force "WPA with TKIP only". If you have mixed B/G/N devices, force the fastest mode that all devices support. I use "G only".
Then remove and re-add the router on all your devices.
Also check for router firmware updates, and if you use DD-WRT firmware, find the Wiki page for your model and revision and use the suggested build there. The DD-WRT database they have is a mess and should not be used!

swamp goblin said:
Ohh, I thought you had said that both the sidekick and nexus were having problems connecting. My bad.
But yeah have you changed any settings on it lately? Or messed with anything related to the router? Some setting may be kicking your device off after 5 mins, maybe some frequency setting or something dumb like that, I have no clue.
I know how it feels to have funky wifi, so I was only trying to help. good luck
Click to expand...
Click to collapse
I haven't changed any settings, until this problem began, which makes this even more maddening. I appreciate your input regardless
Oogway13 said:
Have you removed DD-WRT from your Wireless Router and back to stock OS? I had a Linksys router with DD-WRT and after about 3 years it started working so weird it became useless with any device. Had to buy a new one.
BTW, are other devices connecting fine to this router?
As swamp goblin stated, I would try with a new router.
Click to expand...
Click to collapse
I haven't removed it. I thought I had a model that couldn't go back to stock, but I WILL be looking into this. The other devices connecting fine are Sidekick 4G, Wife's Nexus S, Acer Aspire one, HP tx2000 laptop, and my wife's HP laptop. I also have my satellite receiver connected via ethernet.
SpookyTunes said:
It sounds like an issue on your router (or AP) with mixed client settings. I have had this issue with an old Netgear AP.
Try forcing "WPA2 with AES only" if all clients support it, otherwise force "WPA with TKIP only". If you have mixed B/G/N devices, force the fastest mode that all devices support. I use "G only".
Then remove and re-add the router on all your devices.
Also check for router firmware updates, and if you use DD-WRT firmware, find the Wiki page for your model and revision and use the suggested build there. The DD-WRT database they have is a mess and should not be used!
Click to expand...
Click to collapse
I will certainly try these settings. Thanks for the tip on the wiki page

I had this problem too, I solved only flash again my radio...
Try if solve...
Or if don't work try to make a reset.
Sent from my Nexus S using Tapatalk 2 Beta-4

SpookyTunes said:
...Try forcing "WPA2 with AES only" if all clients support i...
Click to expand...
Click to collapse
THIS FIXED IT! I tried it first since it was the simplest solution and I've been 4 days with no loss of connectivity since I changed it to AES only, which all my clients do support! Thanks so much!

Evening Yallll - Wifi question for yas!!!

OK so device is a - LG D80210B - 16GB - UK - EE - UNLOCKED - ROOTED - StockMOD rom with update package. 4.5gb storage space left.
2nd device is a - HTC ONE 16gb - STOCK - NO ROOT
3rd device is a - SAMSUNG RV510 Laptop.
Im on EE uk network on both phones with EE ADSL Broadband at both mine and my partners house.
Now.... One would assume everything from the same company would be simple... If only that was the case! haha.:silly:
Now which ever property I visit within 15 - 20 minutes of being on the Wi-Fi the LG G2 kicks everybody out of the router, all at the same time. No one can access the network until one of 2 things happens... either I disconnect for 15mins plus or the router gets restarted nothing else will bring back the internet. Note - This does NOT happen when I am not present and surfing can be achieved all day on any device.
So ive spoken to the useless turds at EE technical support on the phone about 30 x they have absolutely no idea what the issue is but its definitely only related to my device. There suggestion is to cancel and go back to sky (which worked flawlessly previously to EE being installed). this is an option but it means another month with no internet at all and I also get an additional 10GB of 4GEE data on my phone allowance if I have there broadband so it would be beneficial to keep it.
Things ive tried;
Every different setting under the sun.
Different encryption.
Static IP addresses.
DCHP settings.
the brightbox will only broadcast internet on 2.4ghz as well if it helps anyone diagnose.
Using a known router as an access point to see if that solves the issue - again perfect until I log on.
Tech support.
Search the net and forums on here.
Spoken to a networking wizard mate of mine.
The problem seems to lie in the LG G2 and/or Jellybean firmware currently installed and installed as stock as the fault is not present when I log off the Wi-Fi...
So..... I decided to try a different rom, the Slim Kat rom
The Wi-Fi works flawlessly for me and everyone else however the rom is just too unstable at the moment to be a daily driver. It doesn't have the complete knock on knock off features and I don't really like the look I much prefer the stock rom as well as some of the games I play just will not work.
Now ive had and been flashing smartphones for about 8 yrs with the help of you lot on here leedroid especially was one of my faves so im not a novice or anything im just lost for what else to do or try????
Has anyone else experienced anything similar?! I would send it away to see if its a hardware fault but as it works perfectly on kitkat I assume its got to be some kind of bug in jellybean.
OR ive changed something that's ****** it up.
I would really appreciate any imput at all because I have a phone I cant use at my partners house or at home ...
Cheers brett

Just to add it also does it when Im on my own i.e. just the phone.

bump for today.... this is really breaking me now as no one can use the wifi for longer then 15 minutes lol

So theres not one single person that has even the faintest idea of what my issue may be?

Someone had this issue before, read about it. A router update fixed their issue. If setting device static, the router also needs to be configured to hold it, try this with all devices and lock local IP's. Next, leave a device off and see if it gets kicked. The G2 seems a bit picky with routers... On the Comcast Technicolor, it won't push past 3.5 dl, but max up. Some old drt firmware has problems as well.

Steamer86 said:
Someone had this issue before, read about it. A router update fixed their issue. If setting device static, the router also needs to be configured to hold it, try this with all devices and lock local IP's. Next, leave a device off and see if it gets kicked. The G2 seems a bit picky with routers... On the Comcast Technicolor, it won't push past 3.5 dl, but max up. Some old drt firmware has problems as well.
Click to expand...
Click to collapse
Thanks for the reply dude...
Yeah tried to update it but its telling me its on the most recent software even though its date is 2010. Called tech support they say it up to date.
I can set the IP in the DHCP section of the router but I cannot for one second find out how to do it on the phone... do you know?
I used DHCP to assign a static IP to both phones, the Nintendo wii, the sky box and the laptop, so they always pick up that IP from the router without fail. I also set the DHCP settings so that it does not conflict with any of the locked IP's just incase - so DHCP is from 192.168.1.2 - 192.168.1.99
Its not a router problem as much as id like to blame it on that because I used my old known working sky router as an access point to connect to as well and that make absolutely no difference apart from slow it down because it doesn't support "N" mode.
Its an EE brightbox router - piece of *****
I can leave the other 4 devices connected to the router 24/7 with no issue until I connect the LG G2. Then all devices are booted at the same time usually 15-20 mins sometimes less. never more. it also only occurs when just the LG is connected. Like now my phone is stuck at recovery ATM (another problem im trying to solve) and the internet hasn't dropped once my partner is on it and so is the sky box so its DEFO my phone that's doing the bad.
That's ODD that isn't it my up and downstream in the router are both above 10meg although the attenuation and line noise keep changing.
cheers for the input

In wifi menu of phone, hold on connection and select modify. Check show advanced options, chose static, input data(along with password again). Reboot phone. After you fix it of course.

Steamer86 said:
In wifi menu of phone, hold on connection and select modify. Check show advanced options, chose static, input data(along with password again). Reboot phone. After you fix it of course.
Click to expand...
Click to collapse
I ended up getting a new router that seems to be ok so far... what does that actually do? Thank you so much for it suggestions
Sent from my LG-D802 using xda app-developers app

Sets static for phone. Has to be set on both router and phone. I just found out the G2 has some issue with AES on certain routers. Try TKP only. I had to do this with my other Technicolor. Odd thing is AES works fine on the SB 6141. Lost on that one.

Had exactly the same issue with my shiny new G2. Using a Netgear modem/Router. I upgraded the firmware and that seems to have fixed it. It was killing the Router within about a minute of use. Now running 25 minutes without any drops. Fingers crossed it's permanent.
Sent from my LG-D802 using Tapatalk

[Q] i9505: WiFi not saving key, invalid IP address

My GT-i9505 has a problem with the Wifi. I bought it a month ago and the Wifi stopped switching on after 2 weeks suddenly, no idea what caused it. I formatted the phone and that fixed the problem, it's been working fine since then. Now I have 3 more small problems all related to the Wifi:
1) It takes a while for Wifi to switch on now, maybe 10-15 seconds. It seems to get worse every time I leave a place using Wifi by letting it disconnect on it's own when I go out of range.
2) I have to input my WPA key every time I connect to the same home wifi router (Dynalink RTA-1025w). How do I get it to save my key/password?
3) It almost always connects to the router without being assigned a proper IP. On DHCP it usually assigns 192.168.1.3 when it works, but sometimes it says ::1 instead. I have to change DHCP to Static and manually input 192.168.1.3 and that fixes it instantly, but I need to do this and input my WPA key almost every day.
I was planning on rooting and installing CM but I thought I should ask about my wifi problem first. I'm assuming CM will fix these problems but I thought I should double check and ask whether I should fix this before installing CM, just in case I make the problem worse. This is also my first smartphone so I'm completely new to all this (my last phone was an old Nokia E55).
Another unrelated question. What's the difference between the CM on cyanogenmod.org VS. KVT49L [AOSP] 【4.4.2】Dan&Ktoonsez 【CM Edition】on this forum? (http://forum.xda-developers.com/showthread.php?t=2763735)
I'm guessing the latter is the same thing but with further tweaks, fixes and additions, correct? I would ask in the relevant thread but I don't have permission. As a legit newbie, I'm quite overwhelmed with all the CM choices, how do I know which is the right one for me?