I have searched for this issue and there are TONNES of threads about it and a lot of proposed solutions but none of them work for me. I have been using this HTC Incredible for some three months now and have gone through various ROM's including some Sense based, CM7, a couple ICS ROM's and MIUI. But every one of them gives me this problem with the wifi at work. The phones finds the network, connects to it, authenticates and then gets stuck at Obtaining IP Address... and then repeats the cycle.
I used to have an iPhone that worked well with the same wifi spot. My friend's Nexus running ICS connects just fine. But my phone exhibits this problem with this wifi spot and a bunch other public spots it has connected to before.
From reading various threads, it happens when Android remembers the last IP address it got at this spot and tries to assign itself that but fails. It does not learn to ask for a new one. Which is verified by the fact that assigning a static IP, then going back to dynamic IP address makes it refresh the IP request and work for a little bit. Then it goes to sleep and the same agonizing cycle starts again.
Is it because of the hardware? Is it because of the Kernel? Does anyone have a clue?
I have tried Wifi Fixer app and that didn't help. Another person has listed three other apps and how those did not work for him (so I didn't even try them).
At this point, this issue is so frustrating for me. Can anyone recommend some more ideas for me to try? Different ROM's, different kernels? Anyone? ANY one?
This happens to me intermittently when I come home. Multiple ROMs and kernels, no rhyme or reason. When I notice it, I restart the phone and have to turn WiFi back on. Then it works fine for a day or longer. I wonder if it's a bug that's triggered by background processes.
I came across this possible fix while searching for something else. Wifi Won't Connect
Also, I would not be so quick to write off those other apps you mentioned, it is very possible that the person who said they did not work had something different that was causing the Wifi to not connect/obtain IP.
Thanks guys. I have installed a new Kernel and will try it as well as the above suggestions in the next couple of days and report back. Here are the suggestions made so far:
1. Turn wifi off. Restart the phone and turn wifi on.
2. wpa_supplicant renaming
3. Other wifi fixing apps.
yelloguy said:
Thanks guys. I have installed a new Kernel and will try it as well as the above suggestions in the next couple of days and report back. Here are the suggestions made so far:
1. Turn wifi off. Restart the phone and turn wifi on.
2. wpa_supplicant renaming
3. Other wifi fixing apps.
Click to expand...
Click to collapse
Have you tried forgeting the network in the wifi settings menu and then try connecting again?
Yes, I have tried forgetting and starting from scratch again. And with the new Kernel, it just doesn't connect at all. Gets stuck in the Getting IP address loop even for the very first time. I tried #1 but that didn't do anything. I cannot rename the wpa_supplicant because I don't have the USB cable with me and the ROM doesn't let me access the internal storage in ES Explorer. And since I can't get on the wifi, I can't try the other wifi fixing apps (#3).
So I have tried to trace my issue to it's roots and after a lot of investigation I decided to make this thread.
The issue:
When connecting to home wifi network I get "Authentication error occurred" even though it's the good password.
It first occurred on stock 4.1.1 ROM with stock Kernel even before rooting. What's more interesting is that I've successfully used the same wifi network for around a month. Other devices connect just fine, no settings on the router changed when this started happening. Didn't fiddle with any settings on the phone neither. I can connect to free wifi APs just fine.
What I've tried:
Dialing *#0011# and from service mode disabling wifi power saving feature.
Using all possible encryption combinations on the router (Open - no password, WEP, WPA-PSK AES and/or TKIP, WPA2-PSK AES and/or TKIP or both WPA and WPA2 at the same time), switching channels, disabling 802.11n mode.
Using some modded wpa_supplicant files from this thread.
Using a bad password just to get a different error.
Downloading some other wifi connectors from the Play Store including Wifi Connection Manager which claims to "Fix device Wi-Fi problems." by cleaning the stored wifi config files and maybe something more.
Flashed Omega v10 ROM with Perseus kernel.
All these things and basically any combinations of them worked to no avail. And the only thing that helped was being very close to the router. That way I manage to connect but moving a couple of meters away, like to a nearby room, and it starts giving the same error even though the network strength is still full at that point.
My thoughts:
I saw a similar issue at a couple of places including a similar thread last active dec 23rd, Android issues on code.google.com and androidforums, but no solutions found there worked. Also comparing how my old original Note and an even older LG P500 perform, the wifi signal is obviously weaker on the Note 2. My area is not heavy on wifi networks, so my guess is there's something wrong with wifi drivers or configuration. Sooooo.... What can I do to remedy this issue and also is there any way to beef up my wifi in the process?
OrangGeeGee said:
So I have tried to trace my issue to it's roots and after a lot of investigation I decided to make this thread.
The issue:
When connecting to home wifi network I get "Authentication error occurred" even though it's the good password.
It first occurred on stock 4.1.1 ROM with stock Kernel even before rooting. What's more interesting is that I've successfully used the same wifi network for around a month. Other devices connect just fine, no settings on the router changed when this started happening. Didn't fiddle with any settings on the phone neither. I can connect to free wifi APs just fine.
What I've tried:
Dialing *#0011# and from service mode disabling wifi power saving feature.
Using all possible encryption combinations on the router (Open - no password, WEP, WPA-PSK AES and/or TKIP, WPA2-PSK AES and/or TKIP or both WPA and WPA2 at the same time), switching channels, disabling 802.11n mode.
Using some modded wpa_supplicant files from this thread.
Using a bad password just to get a different error.
Downloading some other wifi connectors from the Play Store including Wifi Connection Manager which claims to "Fix device Wi-Fi problems." by cleaning the stored wifi config files and maybe something more.
Flashed Omega v10 ROM with Perseus kernel.
All these things and basically any combinations of them worked to no avail. And the only thing that helped was being very close to the router. That way I manage to connect but moving a couple of meters away, like to a nearby room, and it starts giving the same error even though the network strength is still full at that point.
My thoughts:
I saw a similar issue at a couple of places including a similar thread last active dec 23rd, Android issues on code.google.com and androidforums, but no solutions found there worked. Also comparing how my old original Note and an even older LG P500 perform, the wifi signal is obviously weaker on the Note 2. My area is not heavy on wifi networks, so my guess is there's something wrong with wifi drivers or configuration. Sooooo.... What can I do to remedy this issue and also is there any way to beef up my wifi in the process?
Click to expand...
Click to collapse
I had somewhat the same issue. Autentication error.Even though WIfi worked properly on my Galaxy y.
From v9, I flashed v6 Omega and then everything was working fine. So go ahead and flash Omega v6.
And after that did you go back to a Jelly Bean ROM?
Edit: at first I figured omega v6 wasn't JB, but then I checked... For the peace on my mind I'll try flashing Omega v6 later today.
OrangGeeGee said:
And after that did you go back to a Jelly Bean ROM?
Click to expand...
Click to collapse
When I went to v6, all was working well. But when v10 was released,i flashed it,hopiing that the wifi issue is not there but alas same result.
Before flashing,I made a backup of my wifi folder found in root folder /etc/wifi .
After flashing v10, and overwriting the wifi folder with the one that i had backed up, the issue was solved even on 4.1.2 for me.
Worth a try mate.
Do report back.
zeeshanonlyme said:
When I went to v6, all was working well. But when v10 was released,i flashed it,hopiing that the wifi issue is not there but alas same result.
Before flashing,I made a backup of my wifi folder found in root folder /etc/wifi .
After flashing v10, and overwriting the wifi folder with the one that i had backed up, the issue was solved even on 4.1.2 for me.
Worth a try mate.
Do report back.
Click to expand...
Click to collapse
Sounds very interesting. Will report Dunno if an upcoming exam is more important than solving this issue now
OrangGeeGee said:
Sounds very interesting. Will report Dunno if an upcoming exam is more important than solving this issue now
Click to expand...
Click to collapse
The curiosity will hamper your exam!
Is it today?
Well there's 24 hours left, but work and catch-up for half a year is no small feat
To follow up, did flashing Omega v6 work?
i'm really keen to know as I am having the problem currently.
Authentication Problem Wifi - solved for me
Hi folks - I had the same issue with my Galaxy Note I717 (it's the AT&T Note 1) that I got yesterday. I have no problem with my T959 Vibrant to connect to my router at all. But the Note always gave me the authentication problem. So I took it with me to work today and no problems at all to connect to Wifi over there - everything just worked fine.
Back at home - same issue. So I was thinking about to reset my router when I saw this button on it's side and I remembered that I had read something in the settings of my phone.
So that's what I did: When choosing the network on the phone I went to advanced settings. WPS - here I choose Push Button. After that I pushed the button on my router and voila everything worked as supposed.
After switching Wifi off and back on there was no authentication problem anymore. So to confirm the whole thing I let the phone forget the connection and I had the same authentication problem. After choosing WPS "push button" and pushing the button on the router everything worked again.
I don't know - maybe it's just basics for a lot of guys here, but I was glad to figure that out by myself and maybe it helps someone else.
In the case that it might be important - my Note runs stock ICS 4.0.4, stock kernel. is rooted and unlocked. The Vibrant runs ICS Passion V13.1 and Kernel Kiss Yum Yum Good #2. The router is a D-Link DIR 655 Wireless N
Following up the thread:
No, flashing omega v6 didn't work for me.
What I found out is actually 5 GHz band routers work just fine (for example at my university) and all the 2.4 GHz ones give the same error if I'm not close enough to them (something like 5 meters with straight visibility and 2 meters behind closed doors with my home router Comtrend WAP 5813n).
I have called Samsung's Warranty Center to ask for assistance and since we don't have official Samsung service centers in Lithuania, they told me partnered service centers might just return the phone to me as it is and so they would call me when they found out more about this issue (that was almost 2 weeks ago). Will call them again tomorrow and will post any updates if the story develops.
EDIT: After talking to them they apologized for taking so long and assured me I was not forgotten and the issue was forwarded to UK because they have no records/info about it here in Lithuania. Strange thing is I still have my phone, they didn't even wanna check it out.
Note 2 wireless issues
Lads I tried EVERYTHING to get connection working after it dropped on me after a month. Done everything I have read on every forum. EVERYTHING. All other Samsung devices work fine except this note 2! One other odd thing I discovered. It connects fine to any modem or roster fine then when try again on each it won't. You tell me guys? I had it with this issue. Help before I chuck it in Port Phillip Bay!
Hello Jumbo,
i had the same problem and read a lot threads about this error message.
For me it looks like not all who get this error have the same problem.
Some wrote that they fixed it by
- exchanging the wifi folder with the one from 4.1.1..
- flashed a different kernel
- downgraded to 4.1.2
- changed wifi energy saving stuff
- messed around with their routers
and so on..
I also did all this stuff but with no success..
In my case I figured out that
- the same problem exist on 3 different routers (so it couldn't be a router issue)
- the wifi speed (when I sometimes got connected) kept falling from 65MBit down to 5MBit
and by having a wifi connection, I couldn't reach any webpage.
- then I recognised, that I only had a working connection, when I was close
to my router, like 1 or 2 meters without anything between us. In this case
I had no problems with authentication and to surf on the web.
I decided to send my Note2 in for a repair, and guess what... They changed my
Mainboard and since then, everything is back to work..
How long did it take for the repair? I can't imagine being without my phone for an extended period....
I know, it's an addiction, but I'm ok with that..
Steve
I have an identical issue with my S3 GT-I9300
For a totally reliable wifi connection, I've had to site the cradle for the phone on top of my router!
Am out of warranty, so if anyone finds a fix for this that does not involve a mainboard change...
(My first post on this site- I just wish it had been a fix rather than a query)
fuzzer said:
How long did it take for the repair? I can't imagine being without my phone for an extended period....
I know, it's an addiction, but I'm ok with that..
Steve
Click to expand...
Click to collapse
Sorry for the late answer.
My repair took 1 week...
shipped it to w-support on Monday and got it back Saturday.
I was really happy with w-support here in Germany.
I've reset my device to stock and so far it's been sitting @ warranty center for a week, no answer about the roots of the problem yet..
May have found a solution
Hi,
I had the similar problem. With me it started happening after I changed to a Zyxel modem. After some investigation I noticed that in the Zyxel the default gateway is set at 192.168.1.254 whereas most other brands use 192.168.1.1.
Have an inkling that Android doesn't play nice with non-192.168.1.1 gateways.
So changed this in the router settings.
To be sure I also allocated fixed IP on the LAN to my devices and made sure that in the advanced settings of my WiFi network on the Android device I made sure the primary and secondary DNS addresses matched those that the router uses.
Oh.. And to top it all off I fixed the broadcast channel of the router to channel 11 (Probably best you use an app like WiFi Analyser from the Play Store to find the channel that works best for you)
This seems to have solved it for me for now. (I know, not a very scientific method, but got fed up with trying to isolate the culprit)
BTW. Am running (1) Galaxy Note on latest stock ROM (rooted though) (2) Galaxy Tab 2 7" (stock JB ROM - non rooted).
Hope this helps..
Sounds so strange that gateways and channels did it for you. I've tried to change channels on my router with no results. Also I have tried way too many routers before I decided router settings were not a problem. I guess we may have different kind of hardware/software faults resulting in same error message.
OrangGeeGee said:
Sounds so strange that gateways and channels did it for you. I've tried to change channels on my router with no results. Also I have tried way too many routers before I decided router settings were not a problem. I guess we may have different kind of hardware/software faults resulting in same error message.
Click to expand...
Click to collapse
I know. It is weird.
Mind you only a few hours have passed since my changes. I'll keep an eye on it if it reverts to it's old state.
Ok.
Had the same issue again this morning, but oddly enough, once it connects, it stays connected. Also when the phone is put to sleep.
Sent from my GT-N7000 using xda app-developers app
I have a Rogers Samsung Galaxy Note 2, stock on 4.1.2. No Root, No Nothing.
I was going to flash it back to 4.1.1 but couldn't. The computer can not see the phone. I changed, updated all drivers, but the phone is not seen. The USB options that come up on the phone don't even show up. Even tried different computers.
That was fine, a weird issue, but I also can not connect to any WiFi connection, don't have the ability to try mobile connection. It says obtaining IP for awhile, and then says Connection Disabled, Poor Quality. And keeps going in circles.
So I am thinking the phones hardware is messed up badly. Anything I can do, any ideas, suggestions? It was purchased second hand, so I am thinking the person could have scammed me, or I dunno.
Thanks.
Hello all!
I am having constant data issues all day where I go to use an app that needs it, it says that no data connection can be found or something. I turn the radio off, turn it back on and then it works. It's a good work-around but it does get very annoying. I've tried multiple 4.4.2 roms but no avail. I tried a different kernel but I couldn't even use the phone. Any ideas?
Same for me; I'm rooted now but it happened before root and after the JB ota updates. Annoying but otherwise I love this phone
I think this has been a known issue since ICS (I could be wrong though).
If anyone knows a fix that would be cool (I have GSM google play gnex)
My issues started late last night, lost data connection and it didn't come back. On my way home, it connected then lost again at home. Went to Verizon today and they couldn't figure it out, said possibly the radio is taking a crap.
On my way to work, it connects then gone. I tried flashing the radio, pulled battery, booted without sim, formatted cache and delvic. I have tried everything and think it's the end of the line for it
I've been rooted since the day I got it and had the issue once a while back but it straightened out and has been great since.
Certain CyanogenMod ROMs have trouble with the Network Modes sticking. Which carrier are you using? For my carrier, I had to have the correct APNs set to get 4G and MMS working. It might be that this is the problem in most cases, especially when the phone switches between 4G and 3G in spotty areas.
Hey all. I need some advice. This morning my G3 (D850) dropped WiFi connection for no reason. It says the signal is good but the network info says saved, secured. It will attempt to connect over and over again and if it does connect the signal is weak as can be and it drops the connection within 2 seconds. My coworker has a G3 also and is connected to the same work network I am. His connection says excellent where as mine said good. His device connects just fine with full bars. I'm baffled. I've already tried manually selecting 2.4 Ghz and 5 Ghz instead of auto select and that didn't help at all. I've tried manually turning off WiFi and turning it back on. I've tried turning airplane mode on and then off to refresh the connection and that didn't help. I've done a battery pull as someone in one of the android authority forums suggested that (apparently I am not the only one having this issue.), didn't work. I've unchecked WiFi optimization - no dice. There was another post on a different forum here on XDA that said turning off WiFi and then deleting the WiFi config folder located in data/etc/wifi and then rebooting fixed the issue for them so I tried that. After reboot when I tried to turn on WiFi my G3 rebooted itself. Does it everytime. SO, I had to restore to a nandroid backup (btw I'm on rooted stock 10f) to get the phone to stop hating my WiFi toggle attempts. Last ditch effort I did a factory reset hoping for an easy fix... Nope. I don't know what else to try. It was fine yesterday all day. This morning it was perfectly fine and then randomly started having this issue. I haven't altered any system files whatsoever. I really don't want to send my device to LG for warranty replacement so I'm hoping someone can help me out that may have had this issue and resolved it. The only difference between my device and my coworkers device is he is still on 10d and I am on 10f. That could be the issue I guess but that doesn't really explain why my device has been perfectly fine until this morning and I've been on rooted 10f for weeks. I am planning on flashing back to straight bone factory stock 10d when I get home here in a few hours from work but Idk if that will help or not. Judging from the amount of google search results of "LG G3 WiFi connection problems" this seems to be an issue for several people. I won't know if it's on the software side or hardware side until I get home but in the meantime has anyone had these issues at all? People have had success in changing to Static IP but I would have to do that for every connection I attempt to connect to and that's a pain in the a$$. Also, that does nothing to identify the root cause of the issue. Any help would be greatly appreciated. =)
BreakingVZW said:
to much words
Click to expand...
Click to collapse
try deleting /data/misc/wifi then reboot, it that doesn't work try an other kernel(rin kernel is good)
suljo94 said:
try deleting /data/misc/wifi then reboot, it that doesn't work try an other kernel(rin kernel is good)
Click to expand...
Click to collapse
Thanks for the reply. So it turned out my phone just randomly decided it doesn't like my work network anymore. Idk why lol. I got home and it hooked right into WiFi. Gf's WiFi and open networks as well. I call shenanigans. I went ahead and flashed back to 10d anyway though.
BreakingVZW said:
Thanks for the reply. So it turned out my phone just randomly decided it doesn't like my work network anymore. Idk why lol. I got home and it hooked right into WiFi. Gf's WiFi and open networks as well. I call shenanigans. I went ahead and flashed back to 10d anyway though.
Click to expand...
Click to collapse
I am having the same issue! But it is happening in other networks too...sometimes I get the phone to connect but it only works for a while and when I check the networks it only says Saved, even if I try to connect again
Having the same issue, whether at work or home, my wifi has become near useless. I've even gone as far as trying a different ROM. Didn't work.
Same thing here
I also have tried factory reset, installed a new ROM, changed settings in my router... but the problem remains I don't know what to do anymore, I use wifi a lot!! I searched through other topics but no one seem to know how to solve it. Unfortunately my warranty already expired, I took my phone to some technicians but honestly it didn't help at all...they all said it was a software bug and I should wait for an update but if it was just that a new ROM would fix it,right?
I am not very familiar with phone hardware but I assume that if it was a hardware problem I wouldn't be able to turn it on or connect to any network, right?? (any experts here???)
Any solution is welcomed.
anyone please?? :crying:
P.S : I tried a new baseband, new kernel and new ROMs. So far, nothing changed.
I can connect sometimes but get kicked out within minutes. At other times I only get the saved,secured message.
This is happening in every network