HI,
My phone can't connect to WEP networks.
there is no problem with open or WPA networks.
I tried to delete the config file in the system/wifi folder.
I tried to replace the DHCPCD file as Guardian Bob suggested here:
http://forum.xda-developers.com/showthread.php?t=907772
with no luck!
Any ideas?
Thanks.
btw, it's android 2.2.1.
Kinda thin on the info. Whose ROM are you on? Do you get an error message or does it just not connect? Can you see the WEP network or does it not show up? Might be better off posting to the correct ROM-related sticky in Q&A as this is not a Captivate problem. Mine running A3 connects to WEP networks just fine.
Well, it goes from "Obtaining IP address from..." to "not in range" or " remembered" and then back to "Obtaining IP address from..." in a loop.
I tried two routers, I can see the networks but both of them are giving me the same problem.
My ROM is PILOTX, the problem is that I don't think they have an official forum for this.
I asked several people with the same ROM and they have no problems. I think maybe I installed some app. that screw my WIFI config or something....
If you know a better place to ask this question I will appreciate it.
Thanks.
poqw said:
Well, it goes from "Obtaining IP address from..." to "not in range" or " remembered" and then back to "Obtaining IP address from..." in a loop.
I tried two routers, I can see the networks but both of them are giving me the same problem.
My ROM is PILOTX, the problem is that I don't think they have an official forum for this.
I asked several people with the same ROM and they have no problems. I think maybe I installed some app. that screw my WIFI config or something....
If you know a better place to ask this question I will appreciate it.
Thanks.
Click to expand...
Click to collapse
Never heard of that ROM. Is there a thread on the Captivate forums for that one?
Anyhow... here are a couple of places... http://www.facebook.com/pilotxrom
or here... http://iandroid.co.il/forum/topic12091.html
Seems to be some chatter about that devs roms those places. Honestly have never seen that one before. Good Luck.
Thanks lownox. I know of this places, I post my question there before I came here.
I got no answer there.
You don't know this ROM because its a very small group from Israel
but it's a good and solid ROM.
Did you find a fix for this issue? I have the same problem with the stock 2.2 ROM. My wife has the same phone, same stock 2.2 ROM - but DOES NOT have this issue. So, 2 (same) phones, same ROM, but mine has this issue
The one difference is that my wife's phone does not have a data connection i.e, just work on wife (when available).
Regards
Nick
poqw said:
Well, it goes from "Obtaining IP address from..." to "not in range" or " remembered" and then back to "Obtaining IP address from..." in a loop.
I tried two routers, I can see the networks but both of them are giving me the same problem.
My ROM is PILOTX, the problem is that I don't think they have an official forum for this.
I asked several people with the same ROM and they have no problems. I think maybe I installed some app. that screw my WIFI config or something....
If you know a better place to ask this question I will appreciate it.
Thanks.
Click to expand...
Click to collapse
I've never heard of that ROM, either, which will make it very hard for anyone in here to help you if it is indeed a ROM problem. Like I said, I have never had issues with connecting to various networks and security protocols and I rarely see any posted problems like yours that aren't related to the modem being used on the phone. You might try the modem thread in Dev and see if there's a better one for your area that others can recommend, but be sure it will work with your ROM. Mixing modems with the wrong ROM base can be catastrophic.
Miami_Son said:
I've never heard of that ROM, either, which will make it very hard for anyone in here to help you if it is indeed a ROM problem. Like I said, I have never had issues with connecting to various networks and security protocols and I rarely see any posted problems like yours that aren't related to the modem being used on the phone. You might try the modem thread in Dev and see if there's a better one for your area that others can recommend, but be sure it will work with your ROM. Mixing modems with the wrong ROM base can be catastrophic.
Click to expand...
Click to collapse
It's an i9000 ported ROM with added hebrew locale.
poqw said:
Thanks lownox. I know of this places, I post my question there before I came here.
I got no answer there.
You don't know this ROM because its a very small group from Israel
but it's a good and solid ROM.
Click to expand...
Click to collapse
I cannot agree with you on that, it's not as solid as you think. Mainly because when the developer modded it he had the i9000 in mind. And only minor changes were made to make it work on the captivate.
Don't interpret my words as disrespect for the developer. Any contribution to the android community is BLESSED. It's just that he has a lot more israeli i9000 users than captivate ones.
You right, there are lots of I9000 in israel, its the #1 hit after the Iphone. We dont have too many Captivate here. I guess you are from israel...?
Anyway, as much as hate replacing Roms, I think I have no choice to go for the CM...
Related
Hi,
I've been having a problem where my phone is restarting itself intermittently while I use the wireless network at my school (Purdue). I've tried both WPA and WPA2 (the school provides networks for both) and seen problems with both. The networks are the "enterprise 802.1x" version which requests a username and password to connect. I sometimes have to try a few times to get it to connect to WiFi (it sometimes takes a minute or two after I first turn on "Wi-Fi". Then, every few hours, the phone reboots itself: I'm in the middle of doing something (can be anything) or the phone is idle in my pocket and then the AT&T boot screen appears. I assume that there is some sort of kernel panic or something else that causes the hardware to reset itself.
I'm fairly sure that this issue only happens in a specific building on campus, so perhaps there is a misconfigured access point here. Even so, this is still a bad problem and could have security implications (perhaps a malformed packet is causing some buffer to overflow).
My phone is a non-rooted, stock AT&T Captivate with the JH7 firmware
I've tried talking to Samsung, but they want me to send the phone to them so that they can "repair it". I've swapped out the phone at the store where I got it for a new unit and the new unit (with new battery) also has this same problem.
The 802.11g at my house works flawlessly.
Ideas?
Assuming that this is a kernel-panic issue, how would I extract a stacktrace or other debug information? Do kernel panics cause the phone to restart itself? Have the 802.11 drivers been updated in newer kernels (what's the chance that a custom firmware based Froyo would solve this issue?)
(disclosure: This question was posted on samsungcaptivateforum last month without any
productive responses. I'm a new user here, so I cannot link to that post yet....)
pigrew said:
Hi,
I've been having a problem...
Click to expand...
Click to collapse
Thats weird because my phone has no problems like that and I have connected to many WPA networks. I don't know the source of the problem but my suggestion would be try a custom rom before sending to samsung because it can't hurt. If it doesn't work for you then just restore to stock and send it to them. (kernel suggestion: latest speedmod kernel. works flawlessly.)
Do you use "enterprise"/RADIUS/802.1x authentication? (This (roughly) means that you need to enter a username and password in order to connect to your network).
I was trying to wait until AT&T releases 2.2, but I'm getting impatient on that front. I'll try to look for the speedmod kernel, perhaps. My office is in an electronics lab, so I wonder if something is spewing out RF interference in here.
-Nathan
joeshmoe08 said:
Thats weird because my phone has no problems like that and I have connected to many WPA networks. I don't know the source of the problem but my suggestion would be try a custom rom before sending to samsung because it can't hurt. If it doesn't work for you then just restore to stock and send it to them. (kernel suggestion: latest speedmod kernel. works flawlessly.)
Click to expand...
Click to collapse
I just flashed my with the Cognition 3.02 firmware and the issue is still present. My hunch is that it is a wifi firmware or driver bug. I doubt that these things are changed in the various kernel builds.... Maybe the official Froyo release will fix it, but at this point I doubt that it will.
Someone in my building suggested that the issues may be caused by us having two separate networks on different sides of the building that have the same ESSID.
Ive tried with stock 2.3.6, CM7 and CM6 and although the CM roms improved wifi reception by leaps and bounds, my N1 will still not recognize some very necessary wifi SSIDs, namely the one at work. On my laptop, my old phone (Optimus T), and everyone elses smartphones there is no problem connecting at work. The access point is provided by a Fortiwifi 60c server. fortinet.com/products/fortiwifi/60C.html
Has anyone else had this problem or know the right direction for a solution? Wifi at work is a must!
it's not an adhoc network is it?
try moving closer to the source and see if other android phones can see it too
No, the network in question is not an ad-hoc. Yes, as I said in my original post, other smartphones and wireless devices have no problem making this connection.
I flashed and upgraded my phone's baseband radio to the most up-to-date version and my phone still doesn't see the network in question. I'm just about out of ideas.
Radio has nothing to do with WiFi.
Try different kernels.
Make sure that the visible access point isn't Wifi N.
Thanks for the experienced suggestion, thats just what I needed. Is there much risk involved in flashing kernels like there is with radios? Is the process the same, boot into recovery then install zip? Ill do the research myself here in a few hours when Ill have the free time but I'd like your input as well, Jack_R1, since it sounds to me like you know what you're talking about here. I'm hoping that you'll reply before I give this a try.
There is no risk when flashing kernels - in the worst case, if the flash went wrong, you can always boot to recovery and flash again.
The process is the same.
Kernel should be compatible with your type of ROM (AOSP GB/AOSP ICS/CM7/CM9/MIUI/etc).
Hi Everyone,
As title says, a few weeks ago I noticed that my wifi keeps dropping no matter what I do.. this being as i surf and not in sleep mode or anything like that.
How did it start?
when it happened this is what i did, went to GB rooted rom, flashed up to JB room paranoid android, all worked fine except i noticed wifi kept dropping, tried another jb rom ,same thing, tried ics kingdroid rom, same thing. So then I decided to go back to original official stuff GB, same thing.. wifi dropping, went to official ICS, still wifi keep dropping.
What I have done to try to fix it:
Tried different roms, networks, all settings in Wifi settings. Googled like 3 days straight, mostly this seems to be a galaxy s3 problem not a galaxy note problem. A few people said they solved it by giving it a static ip which wouldnt work for me as im on like 3 different networks, and by changing sleep settings to make sure it doesnt shut off during sleep mode, which i honeslty have no problem with. Someone solved it by switching rom, nothing i find applies to me..
So what do I do??
I would honestly appriciate any suggestion, this is a great community so I got high hopes Sorry if my question has been answered before but I dont belive so, i posted in noob thread any noone had suggestion so I hope I dont do anything wrong with this post.. cheers :victory:
spiralpen said:
Hi Everyone,
As title says, a few weeks ago I noticed that my wifi keeps dropping no matter what I do.. this being as i surf and not in sleep mode or anything like that.
How did it start?
when it happened this is what i did, went to GB rooted rom, flashed up to JB room paranoid android, all worked fine except i noticed wifi kept dropping, tried another jb rom ,same thing, tried ics kingdroid rom, same thing. So then I decided to go back to original official stuff GB, same thing.. wifi dropping, went to official ICS, still wifi keep dropping.
What I have done to try to fix it:
Tried different roms, networks, all settings in Wifi settings. Googled like 3 days straight, mostly this seems to be a galaxy s3 problem not a galaxy note problem. A few people said they solved it by giving it a static ip which wouldnt work for me as im on like 3 different networks, and by changing sleep settings to make sure it doesnt shut off during sleep mode, which i honeslty have no problem with. Someone solved it by switching rom, nothing i find applies to me..
So what do I do??
I would honestly appriciate any suggestion, this is a great community so I got high hopes Sorry if my question has been answered before but I dont belive so, i posted in noob thread any noone had suggestion so I hope I dont do anything wrong with this post.. cheers :victory:
Click to expand...
Click to collapse
What's your modem? Go to settings > about> baseband
thanks for the reply it's n7000xxlrk , it's it suppose to be that?
Sent from my GT-N7000 using xda app-developers app
The operation of Wi-Fi is a core responsibility. Try changing the kernel. Modem is responsible for the connection to GSM. If you change the kernel does not help, you probably have a broken phone.
Gregs5 said:
The operation of Wi-Fi is a core responsibility. Try changing the kernel. Modem is responsible for the connection to GSM. If you change the kernel does not help, you probably have a broken phone.
Click to expand...
Click to collapse
well i have weak wi fi signal.. Most of the modems don't work for me.. Ddlp4 is the one i use..and no the kernel has nothing to do with wifi signal strength
Check your router and see if WPA Wireless network encryption is set to AES, if it is, change it to TKIP., see if you can connect after.
Usually it's nothing to do with the ROM, modem, kernel, android or even the phone itself, it might be your router setting that needs a change.
Know it was long since I made this thread but I wanted to report result, it was as above poster said. Rouer settings, finally found compatible ones after sooo manny roms, modems and other fixes were attempted.
Sent from my GT-N7000 using xda app-developers app
This same this also happend with me several tymss..just goo to dialer and dial *#*#526*#*# I m not sure that this will work on ur phone!!
Sent from my GT-S5830 using xda premium
Hey,
I have a X8 e15a, stock kernel (can't change or it would be hard bricked) and... I can't make the wifi work...
I've tried stock roms, froyo, MC V3, and gingerdx...
I get the same problem, It can detect wifi connections, but when i try to connect...
"scanning... connecting... disconnecting" and loops like that :crying:
Any clue why?
Thanks
Try connecting with a different network.
You might be trying to connect to the same network. Try somewhere else and see if you can connect. Maybe that router isn't properly configured. I had a similar problem a few months ago.
Also , please don't make two different threads about the same issue in two different sections. All questions are to be posted in the Q&A section only. Not in the "General Section"
Mayank77 said:
Try connecting with a different network.
You might be trying to connect to the same network. Try somewhere else and see if you can connect. Maybe that router isn't properly configured. I had a similar problem a few months ago.
Also , please don't make two different threads about the same issue in two different sections. All questions are to be posted in the Q&A section only. Not in the "General Section"
Click to expand...
Click to collapse
Sorry, I wasn't really sure where to post it
I've tried that too, it's a general prob, I've tried to connect to OPEN, WEP and WPA, and it's the same...
I wonder if the wifi it's broken, but... then why it can detect the nets?
Updating from CM9, I notice that the phone now loses it's authentication with the router multiple times in one day. That is, the icon changes from blue to white, and no data can pass through. It is necessary to turn wi-fi off and then back on to restore the connection.
On the premises, we also have a Motorola G, Nexus 7, Samsung Galaxy Nexus and a Nexus One. All but the GNex have no problems with this router. The GNex is still stock, so it would appear to have something to do with these older Samsung phones running 4.3. Searching Google, someone suggested forcing the phone to use the 2.4 band, and doing so with the GNex doesn't completely fix it, but it does happen less often. However, I can't find a "wi - fi frequency band" setting in CM.
So, does anyone have any idea what's going on? And is there a way to force the Captivate to use the 2.4 band?
Thanks much
gibosi said:
Updating from CM9, I notice that the phone now loses it's authentication with the router multiple times in one day. That is, the icon changes from blue to white, and no data can pass through. It is necessary to turn wi-fi off and then back on to restore the connection.
On the premises, we also have a Motorola G, Nexus 7, Samsung Galaxy Nexus and a Nexus One. All but the GNex have no problems with this router. The GNex is still stock, so it would appear to have something to do with these older Samsung phones running 4.3. Searching Google, someone suggested forcing the phone to use the 2.4 band, and doing so with the GNex doesn't completely fix it, but it does happen less often. However, I can't find a "wi - fi frequency band" setting in CM.
So, does anyone have any idea what's going on? And is there a way to force the Captivate to use the 2.4 band?
Thanks much
Click to expand...
Click to collapse
CM9 is quite old, chances are that the kernel modules don't support it.
BWolf56 said:
CM9 is quite old, chances are that the kernel modules don't support it.
Click to expand...
Click to collapse
Thanks for your reply.
Before, while running CM9, the phone would remain properly connected to the router indefinitely. This problem of losing authentication did not occur until after upgrading the Captivate to CM10.2.1
gibosi said:
Thanks for your reply.
Before, while running CM9, the phone would remain properly connected to the router indefinitely. This problem of losing authentication did not occur until after upgrading the Captivate to CM10.2.1
Click to expand...
Click to collapse
Oh misread your post.
If forgetting and re-entering the network doesn't work, try another kernel (make sure it's compatible).
BWolf56 said:
Oh misread your post.
If forgetting and re-entering the network doesn't work, try another kernel (make sure it's compatible).
Click to expand...
Click to collapse
I am willing to give this a try, but I am still pretty new at this sort of thing. While I have rooted and put Cyanogen Mod on two phones, I have never tried different kernals. Would you be able to give me a short list of 3 or 4 compatible kernals that I could try?
Thanks much!
gibosi said:
I am willing to give this a try, but I am still pretty new at this sort of thing. While I have rooted and put Cyanogen Mod on two phones, I have never tried different kernals. Would you be able to give me a short list of 3 or 4 compatible kernals that I could try?
Thanks much!
Click to expand...
Click to collapse
Just look in the Dev section and use one that matches your version (4.1, 4.2, etc).
NeatKernel seems to be popular around here.
Installed NeatKernal today so will see how it goes.
Thanks much for your help!
Installing NeatKernal didn't solve the problem, so decided to try the most recent CM 11 nightly....
After installing CM 11, the router and the phone still do not play nicely together. I contacted Linksys about this issue quite some time ago, but never received a response, so it is beginning to appear that the best solution is to simply replace the router. However, the Captivate is just a spare phone to play with, so it's not worth the extra expense and time, so will probably leave things as they are...
Cheers