Hi all! My work uses a network setup with LEAP. I don't know a ton about this, but I did previously have my old phone (optimus s) setup with "WIFI advanced config editor" and it connected no problem. I upgraded to the Optimus G (world of difference!) and I am now having trouble getting connected. My phone see's the network, but won't connect.
I have read online a bit about wifiACE not working with ICS... and that 4.2 broke LEAP networks, but it looked like 4.1.2 (I took the OTA and am on 4.1.2) should still work. wifiACE does act funky... the setting appear unsaved in wifiACE until after I turn WIF off and back on... then they look correct... I have even checked the wpa_supplicant.conf to see that the settings had been saved (I am rooted).
Anyway long story short... does anyone have experience with this on this phone? I can see the network, just can't connect. I am not sure if it is something with the Optimus G, with 4.1.2 software, or if my configuration is not correct (I have set it up exactly like my optimus s was... I don't see why it would need to be different).
As always any and all help is appreciated!
Thanks!
Just checking back... no one has any input on this? I've done a bit of reading at different sites all over. Seems like a lot of people are having issues, but there are not a lot of answers.
I understand that this effects a very small number of people, so no one on here (or at least no one looking at this) may have experience with this. I am trying to work my way through it, but just don't have a good idea where to start.
I did read that some galaxy s3 users were able to replace wpa_supplicant with one from before the Jelly Bean update, and that fixed it for them... I have already done the OTA, but I wonder if I was able to extract it from a stock ICS ROM, if that might fix the problem...
Not that this will be much help to you. I'm able to connect to my work leap with nothing special at all. Just put in my username and password. It uses peap, then all I need is my identity and password.
Sent from my LG-LS970 using xda premium
Related
Hello,
I've searched around the Epic 4G Touch forums as best I could, but sadly I couldn't find anything that was exactly this problem (although I found some interesting articles about wifi sleep time but they don't seem to apply). I'm experiencing an annoying issue where I can connect Wifi just fine, but if the phone is left for a small period of time (~10 minutes), wifi appears as if it's still connected, however it cannot send/receive data. When this happens, the wifi status says it's "connected", but there is no data connection. The only way to to get the data back is to turn off wifi, wait for 3/4G connection to initialize, then turn Wifi back on to refresh it...then it's fine again until I set the phone down again.
I had this problem on stock EL29, so I rooted and flashed Phantom Blazer ROM (very cool ROM, but I'm still experiencing the same issue). After reading the threads on here about wifi sleep times (apparently they're backwards with ICS roms), I've experimented with every setting, yet I still have the same issue--Wifi is fine as long as I'm using the phone, I set it down, after about 10 minutes pick it back up, says it's still connected, but no data connection.
has anybody experienced this problem with this phone? I'm about to unroot my phone/go back to factory so I can take it in to a Sprint store, the problem is they (trying not to be offensive) don't seem to know very much about this device. I thought I'd ask the pros before I return it, get an iPhone, and have to eat my words about how cool Android is vs. iPhone in front of all my friends. I'm hoping there's a reliable ROM or app that can resolve this vs. having to just replace the device!
Thanks for your help!
I'm not the only one
I'm not the only one with this problem:
edit: I can't post links to androidforums.com or anywhere else, but this same problem is all over the interwebs and nobody has a solution.
I'm sure it's not my router as my ASUS tablet/laptops/girlfriend's iPhone experiences no connectivity problems. I'm thinking this is a hardware problem with some of these devices. I will unroot/reset to factory tonight and let you know what happens.
What channel is your router on? And what type is it A/B/G/N?
This is s known TW ICS bug, most likely kernel related. Almost everyone is having this issue and there is no fix until Samsung decides to repair it. There are quite a few posts similar to this one. If you're using XDA's search function, it's not very good. Try using Google next time and search XDA that way.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Hey guys, thanks for the response. Just before I unrooted/reset to factory I tried one last solution--download an app called "Wifi Fixer". It has resolved a lot of these problems. It's not 100%, but after testing it for a day so far, I've only had to manually refresh the connection once or twice. It's a lot better, even liveable, and I won't be resetting to factory afterall, at least not until Samsung provides an update. So if anyone is having the same problem, try Wifi Fixer, hopefully it gives you a similar level of success...I'm not super happy about having to run another background process all the time, but it doesn't seem to affect battery, and the fix it provides is worth it to me.
Cheers!
Huh - a couple of things. Noticed this problem crept back in FF18 and didn't know why until I went back and checked the wpa_supplicant.conf that I'm using. The line ap_scan=2 was missing; after adding it back in the signal strength is back to full and stable.
I'll bump the thread but it appears the config changes here still hold after all:
http://forum.xda-developers.com/showthread.php?t=1569348
This should also avoid having the WiFi fixer there as you can specify the country in wpa_supplicant.conf manually.
Thanks for looking in to this! A couple questions from a noob like me though:
When you say the problem crept back in FF18 ... what does that mean? Is that something that exists in the "stock" version of the Epic 4G touch from Sprint?
The manual config file tweaks you're describing ... is that something I can perform myself?
Basically I'm wondering if it's "safe" to revert to stock in order to get consistent wifi signal, or if it's something I'm experiencing because of the ROM I'm using.
Thanks!
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
Hey guys, new here to the forum. I've been using the forum a bit lately and have updated a load of things, including CM10.1, hboot 1.07, incredikernel latest jb 4.2, baseband, etc. I noticed people saying you can change your protocol from EVRC to EVRC-B. I tried following the various methods like ##778, ##program, so on and nothing seems to work. Is there a different code I'm supposed to use? Is this even a possibility with the ROM/Kernel setup that I have? It's the last thing that I wanted to do and it's bugging me.
POLSKA9000 said:
Hey guys, new here to the forum. I've been using the forum a bit lately and have updated a load of things, including CM10.1, hboot 1.07, incredikernel latest jb 4.2, baseband, etc. I noticed people saying you can change your protocol from EVRC to EVRC-B. I tried following the various methods like ##778, ##program, so on and nothing seems to work. Is there a different code I'm supposed to use? Is this even a possibility with the ROM/Kernel setup that I have? It's the last thing that I wanted to do and it's bugging me.
Click to expand...
Click to collapse
I think there is. Google search EPST AOSP and there may be an answer for you there.
Sent from my Galaxy Nexus using Tapatalk 2
I dont think there is. Every thread i find says there isnt, and to just backup your current setup, flash a stock sense rom, change the settings, and then restore your backup. The settings persist thru rom flashes. There is a pc program QPST, but im not sure if it would work or not without the epst.apk being present on the phone.
Its true you can change from evrc to evrc-b, which i have done before. However in my opinion it makes call quality no better, and can make you roam or loose connection if you go to an are that dosent support evrc-b.
Yeah, I searched what tiny suggested and that was the only solution really. Not really a problem I just thought I could streamline it. Isn't the EVRC-B a preferred setting not a forced setting? That what I thought people were setting it as for those 3 locations "home" "roaming" and whatever the third was. Maybe it just states preferred but it's really forced causing you to roam more often. I think I'll give it a try and see how it goes for me.
Hi!
I know there are plenty of threads about the wifi on this phone, I've read every one of them, posted in many places and have had no good outcome.
Here is my (lengthy) story.
Had annoying wifi bugs on stock 4.1.2, seemingly general lack of interest from the phone in connecting to wifi, but would generally connect after a reboot of both modem+phone+ disabling PSM (even then, not always )
6 months on stock go by, thought flashing a custom rom would fix everything and all would be well again, so I flashed PA.
An even more annoying bug showed up,
Turn wifi on > doesn't automatically connect, so I manually go to the wifi settings page and try connecting.
Before trying to connect - Full signal.
While trying to connect - Goes down to one bar while connecting > fails > then goes back to full signal.
Does occasionally connect, but it's rare. Rebooting both phone and the modem does nothing at all, seems to have a mood of it's own.
It's not just my wifi, but wifi at college too, other devices connect to the same access point just fine.
What would fix this? Will pretty much try most things now,I tried flashing NEAK too.
I don't have a data plan either, so my phone is basically useless without wifi, I've resigned to using my laptop all the time.
Thank you for reading this so far, I'd be thankful for ANY advice.
TL;DR :- Annoying wfi bug, tried every 'solution' I've heard of, nothing worked, never buying a Samsung again :crying:
(Attached images of the phenomenon)
UPDATE:- Just like stock, it will only connect if I am a foot away from the router, irrespective of how much signal I have. Even if I have a full signal elsewhere, it won't connect
dude u r running AOSP :silly::silly:
try TW Rom and see if the problem exists
yahyoh said:
dude u r running AOSP :silly::silly: try TW Rom and see if the problem exists
Click to expand...
Click to collapse
We meet again!
Like mentioned in the post, the only reason I flashed an aosp based ROM was in the desperate hope it'd rid the phone of its WiFi problem.
Thought a custom ROM would do what Samsung refuses to do.
Hope someone has a valid solution for this.
Sent from my Galaxy Note II using Tapatalk 2
Anyone?
I forgot I already had the range issue for quite a while, even on stock.
I had tried everything, including static IP, wps, and whatever else was stated to work.
Does anyone know of a working solution to this? Is this a hardware/software issue?
Sent from my Galaxy Note II using Tapatalk 2
Look i normally dont ask for to much help ive been around a bit know more then the average bear. I also fix hardware.
My problem is my data radio will not switch on from any attempt:
Attempted solutions:
Dialed
*#*#4636#*#*
Will not switch on from that screen
Did the obvious and switched on and off airplane mode
Replaced the entire build.prop file with a very stock build.prop after flashing stock jelly bean
Repeated steps for all stock firmware
Newest attempt wiped the entire system partition through recovery forcefully bricking the phone. I have now flashed the original stock e980 stock 10p tot file still no luck
My phone is completely unlocked fully rooted.
I've replaced the data permission files.
And I know its not the SIM card because the SIM card is in the phone I'm using right now which is an LG g2 unlocked which is for sale by the way.
And if it is a hardware problem I have not found any related video or thread to help me find an exchange where the radio is on this thing
Help me please if anybody has any idea?
Cool no help, hey moderator can u move this to thread that may get more help that would be awesome
i came looking around here because my g pros radio stopped working sometime last night while i was asleep and was about to make a thread asking for help, but seeing as how you haven't got much i doubt i would either. but ill give you a little info on mine, will it help you out at all? not sure. but i know it might make me feel a little better.
I flashed Vanir 4.4.4 last week coming from Beanstalk 4.4.4 cause beanstalk was getting buggy from all the ugly mods i subjected it to. so all was well with Vanir till i woke up this morning and had no service, no calls, no network, AND even if i connected to a wifi network it seemed that i couldn't get any data from it. I tried flashing madmacks modem cause who knows, maybe thatll help, but it diddnt. So then i flashed a different kernel and changed TCP protocols cause who ****ing knows, but it did nothing. THEN i restored my older Beanstalk 4.4.4 backup sure that it would work flawlessly but guess what, same problem. Now that im back on Beanstalk i went to the "Network Operators" option under "Mobile network settings" and selected ATT, which is my service provider, i can now make calls and texts but still no data, when i did this on Vanir it did not help. So i started messing with my "preferred network type" and realized i have data on 2G, but not 3G or LTE. Im gonna take a wild guess and say that maybe if you flash your phone back to 100% stock your radio should start working again, as much as i dont want to, i might end up doing that as well.
tl:dr
similar problem, i dont really know ****, easiest option = go back to stock, hope it works.
@Fant0m3 @alb-o
Have you guys checked if your rom shows your imei?
I have had this problem twice. My IMEI disappeared and I don't know how.
Your symptoms match.
If that's the case you could take it to a repair shop and they'll fix it in a minute or two. Or, you can check around xda.
thats a good point, when i was looking around XDA earlier i saw a few mentions of it but diddnt see anything very specific and was late for class so diddnt have time to look for too long. strangely enough mine actually started working normally again after i kept switching from 2G to 3G to LTE, which is great. but if i would've known that info earlier i could have checked if my IMEI disappeared while my radio still wasn't working, i assume it probably did.
after searching around more i found this thread that talks about it and how to prevent it:
http://forum.xda-developers.com/showthread.php?t=1857054
thanks for the help g0at1, hopefully this helps out the OP if he hasn't already fixed the problem, or anyone else that comes across this.
nope
I've flashed back stock numerous times even flashed other versions such as e988 and back again if u dint know how to do that just change your build number in your build prop file...I've tried everything I am downt to antenna cable SIM reader or cell radio.. If radio I might as well just give up cause I can't find one for sell anywhere...I'm not so pressed as I'm using the LG g2 and it's so fast stable and a bit slimmer I think I'm gonna keep it but I would like to fix it and sell it though...... My symptoms are mentioned and all tried fixes are there. Imei is read carrier is not WiFi is received but there is an X above the data bars phone is fully unlocked as well
This may help also but it does not read my imei when the SIM is not in hmm maybe I will rework the imei code and get back if that works. I will keep updated when fixed and with solution