Related
My wife's just got a tablet so wants to get it connected via her Wildfire.
We tried turning it on last night but it's not working properly - the hotspot functionality itself seems be enabled properly, but in Wireless and Networks, the text under the 'Mobile network' option keeps cycling between 'Connected' and 'Use phone for data connection...'.
The text 'Wi-Fi hotspot active' keeps appearing and disappearing from the notification area.
We appear to be able to successfully connect the tablet via wifi to the Wildfire but there's no internet access.
The handset is completely stock and unbranded (Froyo, build 2.22.405.1). Internet access in general is fine and my wife's data plan specifically allows tethering (GiffGaff UK, using a Gigabag).
Has anyone else encountered this issue and found a way around this? Am willing to start rooting and flashing other ROMs if it will solve the problem.
for tethering try the Barnacle wifi tethter app from market - works for me
I'll give that a try when I get home and report back here.
Have you ever tried it using the in-built functionality and either found it to work or not? Considering I've not had problems with my own handsets (previously a Desire, now a Sensation) it seems odd that I can't get it to work on my wife's Wildfire.
I used the built in one on stock rom with no problems at all on 2 wildfires, I used to use all mine then leech from the girlfriends. Could it be a problem with her apn setting? Maybe call customer service and check its set correctly for tethering.
Personally I'd tell her its broke though and flash it like I did the girlfriends purely because I'm a flashaholic!!
Sent from my HTC Wildfire using xda premium
Just in case anyone was wondering (or for the benefit of future searchers)... I finally got the Hotspot working after I installed a custom ROM (DK Custom Froyo v4.7 - I didn't want anything too different to Stock).
Custom kernels etc. didn't work (in fact, the one I tried destabilised the handset), neither did other options such as Barnacle on the stock ROM.
Thanks everyone for trying.
Hi guys,
I've searched the whole forum but I couldn't find any other thread about my problem.
When I connect my HOX to WiIF (Sitecom WL-370 - 300N Gigabit Dualband Router) everything works fine at first, but after a few minutes (5, or sometimes 15 minutes) I've got no Internet anymore but I'm still connected. Also WiFI Analyzer still detects the network. I've this problem both on 2.4 GHz as on 5 GHz. I've also tried switching channels.
The strange thing is, I can still receive a WhatsApp message but I can't send any, also I can't browse on the Internet or things like that.
After turning my WiFi off and on it works fine again for the few minutes..
Best Wi-Fi performance is turned on and the other devices at home haven't got this problem.
Anyone having the same problem or knows a solution?
I've got the same problem and it seems to be totally random. What i noticed is that my Google Play Store always stops working (no connection) shortly after i turned on the phone (~10 minutes). Switching Wifi off and on again doesn't seem to change it, i need to restart my HOX to get it working again while other apps connect just fine after turning Wifi off and on again.
Edit: Stock Vodafone ROM (1.28.161.9)
I have the exact same issue and i went through every setting in my router trying to fix this.
I would turn on my WIFI, connect to my home network, and start downloading. After a few minutes it'll either stop (the dl percentage not change) and then if i reload the market/youtube/browser or any app that users the net, it'll say no connection.
The weird thing about this is that it LOOKS like i am connected to wifi (in the notification bar).
This may be a separate issue, but i tried to turn it off and then on again to get around the issue. This time around i would try to connect to my home wifi and it'll just say 'Saved' and then the network would go out of range.
I am running Leedroids rom.
I might have found a solution:
Under Settings -> Wifi -> Menu -> Extended there is an option for Wifi Power Saving. After unchecking it all my connectivity problems are gone.
May be worth trying a static IP configuration, if you know enough about ip4 to do it. I've seen problems with android Wi-Fi since version 2.2 - if your router issues an indefinite dhcp lease, it can show exactly the symptoms you describe. Only a possibility but worth a try.
Sent from my HTC One X using XDA
I have the exact same issue - the wireless shows connected yet you cannot browse the Internet etc. I have also tried every setting on the Wireless AP without any success. Even tried static IP and that does not fix it either. Whilst other devices in the house are ok...
The weirdest thing is though it does not happen everywhere i.e. at other places like work (where at least the same type of AP is in use) or at my brothers' house (where he has a Linksys). This is pretty much the only thing that bugs me with the HTC - the only workaround I have found is to make sure that WiFi is kept on only at times when plugged in - this doesn't actually fix the issue but it does mean that the phone will disconnect the WiFi and get a new connection next time it wakes up - this way I find I get the problem much less than when I have it set to Always.
I might have found a solution:
Under Settings -> Wifi -> Menu -> Extended there is an option for Wifi Power Saving. After unchecking it all my connectivity problems are gone.
Click to expand...
Click to collapse
I already unchecked it but it didn't solved my problem
May be worth trying a static IP configuration, if you know enough about ip4 to do it. I've seen problems with android Wi-Fi since version 2.2 - if your router issues an indefinite dhcp lease, it can show exactly the symptoms you describe. Only a possibility but worth a try.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Also no success
I have the exact same issue - the wireless shows connected yet you cannot browse the Internet etc. I have also tried every setting on the Wireless AP without any success. Even tried static IP and that does not fix it either. Whilst other devices in the house are ok...
The weirdest thing is though it does not happen everywhere i.e. at other places like work (where at least the same type of AP is in use) or at my brothers' house (where he has a Linksys). This is pretty much the only thing that bugs me with the HTC - the only workaround I have found is to make sure that WiFi is kept on only at times when plugged in - this doesn't actually fix the issue but it does mean that the phone will disconnect the WiFi and get a new connection next time it wakes up - this way I find I get the problem much less than when I have it set to Always.
Click to expand...
Click to collapse
Yeah, exactly, I've got the same problem. At school I've got no problems with the WiFi. I already send a message to HTC and I'm waiting on there answer.
I have kinda the same issue.
Using a HOX and at work I'm connected to Wifi and I can browse. At my house I can connect to the wifi, my IP is right that I'm getting from DHCP (I even tried putting in a static IP) but I can't browse
I also have a HTC Sensation, same setup and it works. The sensation can browse at work and at my house.
Why would this be?
Tried all sorts of solutions, but the only one that works is disabling the N-band and only leave B and G. This means that your laptop won't connect with the faster N, but at least the HOX works (what's more important )
Well I tried broadcasting a separate SSID on the b/g interface only for the exclusive use for the hox but that hasn't made any difference...my workaround is to have tunein radio in the background streaming whilst surfing...if I get bored of that solution my next workaround will be to trade the hox for an s3 as much as I despise TW...
Sent from my HTC One X using xda premium
I tried all the bands "B, G, N" and nothing works. So tired of this crap. Think I might just get a S3
RenVilo said:
I tried all the bands "B, G, N" and nothing works. So tired of this crap. Think I might just get a S3
Click to expand...
Click to collapse
I was thinking to do the same but there is no chance in hell of me doing that after I compared my HOX with a display model at the phone shop. Pentile screen vs LCD on the HOX? HOX = Sharper and better whites - the white on the S3 is bluish and so obvious. Another thing also I noticed is that the aggressive auto brightness on the S3 is too much - you won't tolerate it and you will likely be forced to manually adjust all the time. That plus reading that the S3 goes through the battery like no mans business when on standby unless you turn off all the features and put it in power save mode (might as well buy a Nokia then) at least the HOX uses the Ninja core and actually does save your battery in standby mode.
Anyway - the reason I replied is that I found a workaround (note, workaround does not mean a fix) - I put in a wifi extender in an area where I tend to spent most of my time with the HOX - this has not fixed the problem per se but rather seems to have elevated it somewhat. Basically now if the HOX drops from the main offending AP it automatically gets hooked up on to the extender and carries on working! I say this because (and I saw this only twice so far) I realised that when the phones Internet connection stops and you load a new page it timed out and get page cannot be found but when I hit refresh it works again you do notice a 3-4 second lag (this never happened before the extender came into play). Not sure if anyone else has tried this but I got a Linksys/Cisco extender for £69 and so far at least it has given me a workaround. Of course your mileage may vary...so don't splash out on an extender and come and blame me if it doesn't work for anyone here...
I am also having this issue with my HOX has anyone found a fix for this?
i have tried everything listed and nothing works.
its weird though because i have NO issues on my home network, but my network in my apartment here and at work network i get this issue
!!
bbbbbbbbbbbbbbbbuuuuuummp any fixes??? this sucks !!!!
What versions of android you guys have? Stock, sense, vanilla android, ics, jelly bean? Because I didn't encounter this problem when running stock or ics custom roms. After I updated hboot to 1.31 and tried different jelly bean sense roms it appeared. I also tried some stock android roms (ice cold jelly and liquid smooth) and wifi seemed to work fine. So is this sense problem only?
Ot1s said:
What versions of android you guys have? Stock, sense, vanilla android, ics, jelly bean? Because I didn't encounter this problem when running stock or ics custom roms. After I updated hboot to 1.31 and tried different jelly bean sense roms it appeared. I also tried some stock android roms (ice cold jelly and liquid smooth) and wifi seemed to work fine. So is this sense problem only?
Click to expand...
Click to collapse
The only change for me is update to HBOOT 1.31 and then things started happening. Otherwise runnin 4.0.4.
No workaround so far, at least i have not founf a way.
I've seen a few similar threads to the one I'm about to make. I've tried different suggestions which I will post here. Yet, none of them seems to work and I'm curious to see if anyone of you has a fix for my problem. My phone is an unbranded international HOX using the 9.7.2 ARHD rom by Mike1986. Here we go:
Problem
While being on WIFI my push notifications aren't coming through in time. There's a delay from anywhere between a few minutes up to as much as 40+ minutes. The phone doesn't have this issue being on the mobile data network. I'm also not 100% sure if the delay is still there when I'm on an different router. Even when I turn on the screen again, the messages seem to come in randomly.
Settings
WIFI best performance enabled
Static IP by router
WIFI sleep policy: Wifi always on
Tried suggestions
Wakelock: One thread described using an app called REGPON keep-alive, which installs a wakelock onto the phone to keep the data connection alive. This app did not do the trick. It only drained my battery and the messages still didn't come through.
Wifi performance: Set the phone to maximum wifi performance. This seemed to work for a while but ended up not working proper either
Kernel: Try a different kernel was one suggestion. I've switched from Stock to Faux123 010 kernel. This didn't change anything about the WIFI problem.
Static IP + Portforwarding + Disabling router Firewall: I've tried both port forwarding on port 5228 and even the range 5224-5228. I've also tried setting up triggered ranges. Maybe I'm doing something wrong on this part though. The router firewall is disabled and it should no longer block anonymous WAN packages.
Disable SmartSync: With the Suite Tools that are included in Mike1986's rom I've disabled Smartsync. No results as far as the wifi problem goes.
Probing app: I've tried an app that supposedly probes my router at least every minute in order to keep the connection alive.
Switching between b/g/n network: Didn't make a difference. The signal quality of the router is also good.
The only thing that did work for extended periods of time was using this remote control app that allows me to type through my PC keyboard, where the text ended up on the phone. I've also got an app installed to test push notifications. It's capable of making a log. Maybe that'll give you guys more information.
Right now I'm not sure if it's an issue with the HOX or if my router somehow stops the traffic. I don't recall having this problem on my HTC Desire. Does anyone have anymore tips?
Thanks,
Zendio
No problem with Gmail push notification on Stock 2.17.401.2.
Yesterday I still was on ARHD 9.7.2, also there I never noticed any delay.
Edit: this complies to various wifi networks (@home, @office, @parents etc.)
Zendio said:
I've seen a few similar threads to the one I'm about to make. I've tried different suggestions which I will post here. Yet, none of them seems to work and I'm curious to see if anyone of you has a fix for my problem. My phone is an unbranded international HOX using the 9.7.2 ARHD rom by Mike1986. Here we go:
Problem
While being on WIFI my push notifications aren't coming through in time. There's a delay from anywhere between a few minutes up to as much as 40+ minutes. The phone doesn't have this issue being on the mobile data network. I'm also not 100% sure if the delay is still there when I'm on an different router. Even when I turn on the screen again, the messages seem to come in randomly.
Settings
WIFI best performance enabled
Static IP by router
WIFI sleep policy: Wifi always on
Tried suggestions
Wakelock: One thread described using an app called REGPON keep-alive, which installs a wakelock onto the phone to keep the data connection alive. This app did not do the trick. It only drained my battery and the messages still didn't come through.
Wifi performance: Set the phone to maximum wifi performance. This seemed to work for a while but ended up not working proper either
Kernel: Try a different kernel was one suggestion. I've switched from Stock to Faux123 010 kernel. This didn't change anything about the WIFI problem.
Static IP + Portforwarding + Disabling router Firewall: I've tried both port forwarding on port 5228 and even the range 5224-5228. I've also tried setting up triggered ranges. Maybe I'm doing something wrong on this part though. The router firewall is disabled and it should no longer block anonymous WAN packages.
Disable SmartSync: With the Suite Tools that are included in Mike1986's rom I've disabled Smartsync. No results as far as the wifi problem goes.
Probing app: I've tried an app that supposedly probes my router at least every minute in order to keep the connection alive.
Switching between b/g/n network: Didn't make a difference. The signal quality of the router is also good.
The only thing that did work for extended periods of time was using this remote control app that allows me to type through my PC keyboard, where the text ended up on the phone. I've also got an app installed to test push notifications. It's capable of making a log. Maybe that'll give you guys more information.
Right now I'm not sure if it's an issue with the HOX or if my router somehow stops the traffic. I don't recall having this problem on my HTC Desire. Does anyone have anymore tips?
Thanks,
Zendio
Click to expand...
Click to collapse
I am so sorry to hear you are affected by this problem, but also happy someone else is experiencing the exact same thing as I am !!!
I have tried different solutions to no avail.
Would love to hear something on this topic !!
Also I should note, I don't have any kind of task killer installed.
In general use WIFI feels really fluid and responsive. I really have no idea what could cause these problems.
Zendio said:
Also I should note, I don't have any kind of task killer installed.
In general use WIFI feels really fluid and responsive. I really have no idea what could cause these problems.
Click to expand...
Click to collapse
Did we get any update on this, I have the issues on 3 phones..desire HD, sensation and a brand new Galaxy S3
modd1uk said:
Did we get any update on this, I have the issues on 3 phones..desire HD, sensation and a brand new Galaxy S3
Click to expand...
Click to collapse
I hope so. My One S is experiencing the same thing. I've tried everything above. No luck. Some stuff is fairly critical that I get it as soon as it comes in. I might try getting ahold of a Nexus 4 and do some testing with its wifi, just to make sure it isn't a general Android problem.
What router do you have? My issue was any android device in the house. Turned out it was my router, I put a custom firmware on it and all my trouble have gone away. My friend has the WiFi issue on a virgin media superhub.
Sent from my HTC Sensation Z710e using Tapatalk
I have an Asus RT-N66U. Funny you should suggest that. I'd planned to throw Tomato on it tonight and see how that works out. I did some tests at my folks' and their router had the same results. It's some cheap Netgear thing. Not sure of the model at the mo. I'll post back with results. If not tonight, tomorrow some time.
No go
Well that was unsuccessful. Actually it slowed things down. With the default firmware I get notifications from the instant I press power to wake up my phone. With Tomato there was a second or so before I got them.
Time to try DD-WRT tonight to see if that does the same thing.
I have an rt-n56u so the older version of yours and I'm running the Asus wrt that is being made, its fixed all my problems and is awesome tbh.
Sent from my HTC Sensation Z710e using Tapatalk
Set Beacon mode power safe (BMPS) to 0 in WiFi ???.ini config file should resolve this problem.
Such ???.ini config file usually placed under /system/etc/wifi or /system/etc/firmware/wlan/prima/
Hello all. I have been playing with the new 4.1.2 JB ROMs on my 7100 Note2 and have been having one major and repeatable issue, that I have seen mentioned a few times by others, with no obvious resolution.
I have tried the various leaks of the 4.1.2 that were floating around (the stock one, Wannam and Android Revolution HD 5) and now I have just tried the final Polish PLAY version of 4.1.2 as well as the latest Wannam as well. All do/did the same thing:
They can see my wifi SSID and they can BEGIN to connect and "obtaining IP address" comes up. EITHER they then fail and tell me connection is poor and to try again, or they will connect and then drop within a minute. Just today I made some kind of movement on this by trying different kernels. Perseus25 gives up and tells me signal is poor. Perseus27 WILL actually connect and stay connected but can never actually surf anywhere. Note2Core will either connect or tell me my authentication is wrong (which it isn't) and when connected, it too refuses to surf. RedPill is same as Note2Core. BTW, even when they DO connect, they do so at a measly 5Mbps (and cant find internet)
Now, you are all probably thinking "his wifi is rubbish!" but I REALLY cant see how that can be! Firstly, there are other users out there who have mentioned this in a few threads but I have never seen any useful replies as to a solution (or a cause!). But also, if I restore back to my usual ROM which is Android Revolution 4.1 HD (=JB 4.1.1) with a perseus25 kernel, then I connect immediately and stable at 54Mbps and works great. (all it takes is a CWM restore back and it is working 100%. same location in my office, same router, wifi etc!) Plus same wifi serves two laptops, wife's Galaxy S2, and has seen many iphones, ipads, and other laptops all fine.
Back in the days of the leaked 4.1.2 I DID try jumping wifi channels on the router just to prove a point. Every single one did same thing.
Flashing procedures have been the 'standard' method: boot into CWM, wipe data/cache/dalvik/battery, then flash new ROM, boot OK.
I had assumed that the early leaked version of the ROM had some bug but very disappointed to find same behavior in the Polish PLAY version which is final release AFAIK. It makes all these subsequent ROMs based on it totally useless to me.
I even extracted and flashed the modem.bin from my working ARHD4.1 ROM but nothing changed. So modem and kernel same as working systems but something clearly broken somewhere.
If you are one of the other folks out there who also has this issue, might be helpful if you give some info about your setup, so somebody clever out there can help us join the 4.1.2 club?!
Any thoughts?
(setup: UK VirginMedia 120Mbps down/10Mbps up. Cisco Linksys E4200 router. about 10 feet from router with one 'paper wall' between! ARHD4.1 finds full signal and surfs fast. 4.1.2 totally unusable)
Help me Obi-Wan Kenobi(s), you are my only hope!
I have noticed similar problems on my SGH-i317 using CleanROM 3 (4.1.2). The wireless connection randomly drops while browsing. This happens even in areas with excellent signal quality.
-Sn1PeR- said:
I have noticed similar problems on my SGH-i317 using CleanROM 3 (4.1.2). The wireless connection randomly drops while browsing. This happens even in areas with excellent signal quality.
Click to expand...
Click to collapse
Thanks for contributing. Helps prove the point that it is something in the new ROM as our wifis are fully functional otherwise. I have matched the modem and kernel from my working 4.1.1 system and still failing....
I hope we get some help.
I also got this problem from latest WanamLite & Omega ROM. Both are using 4.1.2 JB.
Wifi detected and connected but always obtaining ip address..
Sometimes it tooks so long and can get ip, but still cannot access internet or can't even ping different ip address from the same network.
hendry said:
I also got this problem from latest WanamLite & Omega ROM. Both are using 4.1.2 JB.
Wifi detected and connected but always obtaining ip address..
Sometimes it tooks so long and can get ip, but still cannot access internet or can't even ping different ip address from the same network.
Click to expand...
Click to collapse
strange, i've been running omega 7 to 7.4 but dont have any problems with wifi.
i've connected to home wifi (TP-Link), workplace (Cisco/Linksys) and some coffe-shops without any problem.
most of them using WPA2 or WEP. sometimes obtaining ip address with WEP could take a lil longer about (10-15sec) but always a success.
but never used wanamlite for my note2 so cant comment any, srry
I'm not saying the issue is in the wifi itself, but it can probably be fixed by disabling n mode and only using b and g. Also try to make sure the phone gets assigned a static ip.
Issue seems to be 4.1.2 related.
Sent from my GT-N7100 using Tapatalk 2
yes.. i'm also facing the same problem.. whenever i flashed custom rom based on 4.12, like wanam 2.0, 2.1 n crash rom, i cant connect to the wifi.. it always shows optaining ip address and it never connected.. now i m using stock rom 4.11 n there is no problem to connect to the wifi..
i juz wonder why it happens to several devices only?
I having the same wifi problem with 4.1.2 firmware...revert back to 4.1.1 wifi connection run flawlessly..strange !
I have tried switching OFF the 5GHz signal from my modem and sticking to 2.4GHz.
Have also tried turned off N and locked it down to just B & G.
Have tried turning off the WMM in the QoS section.
All of these have been mentioned around the place as possible solutions, and I am afraid none of them changed anything at all for me. Also read that one person had his wifi issues resolved when he dropped WPA2 security and went back down to WEP. This is an unacceptable solution to me as I don't want to make my WiFi so insecure, and also, what happens when I go to my friends and family who all (rightly) use WPA2?! So wont even be trying that.
I am actually getting a new Virgin Media Superhub in about 2 weeks so will revisit the issue then to see if 4.1.2 just doesn't like my Cisco router.
Just weird. And frustrating as wanted to move on to 4.1.2!
have you tried changing the channel on your n router?
Ok. I here is my evo 4G lte story. I flashed cm10 as soon as I got this phone a month and bit ago. I totally had wifi connectivity problems at work and at my house. One worked better and one had to be spammed to connect 20 times to connect and would still occasionally drop. I went to sense is from there and found it to be reliable. Though I just moved to the ota, I find this sense to be just as reliable.
In all. The new ota let me move to jb with reliability.
Sent from my EVO using xda app-developers app
I dun think it is about router.. because with 4.11, I found no problem to connect.. when I use 4.12, I cant connect to any other wifi network..
Sent from my GT-N7100 using xda app-developers app
Why not all people getting this wifi problem using 4.1.2 ROM? Does the device something problem? But why going back to 4.1.1, wifi problem dissapeared and can connect directly?
Really2 weird....
Sent from my GT-N7100 using xda premium
hendry said:
Why not all people getting this wifi problem using 4.1.2 ROM? Does the device something problem? But why going back to 4.1.1, wifi problem dissapeared and can connect directly?
Really2 weird....
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
yes.. i also wonder why this happen..
I also have exactly the same problem. I have tried every single 4.1.2 ROM but I can't keep my wifi working. I have had to go back to 4.1.1 as well. My wifi is perfect on 4.1.1. I use Cisco e4200 with ddwrt flashed. Very frustrating!
kobykoby said:
I also have exactly the same problem. I have tried every single 4.1.2 ROM but I can't keep my wifi working. I have had to go back to 4.1.1 as well. My wifi is perfect on 4.1.1. I use Cisco e4200 with ddwrt flashed. Very frustrating!
Click to expand...
Click to collapse
have u tried 4.12 stock rom before u flash 4.12 custom rom?
All 4.1 2 rom having same wifi problem for me..i guess the problem from firmware itself ...
Sent from my GT-N7100 using xda premium
Try changing channels to below 11 if you're in Europe and the router uses channels above.
Sent from my GT-N7100 using Tapatalk 2
I`am on ARHD 6.0 currently and i never had problems with wifi on all the previous ARHD rom`s. Try doing a full wipe or at least also do a system wipe (and wipe cache/dalvik cache, data/factory reset and format preload) before flashing a rom. I`am sure that will help guys.
i have same problem no ip adressing and when i set statique ip no internet
i test Omega wanam mondx... same issue
omega 6.1 works great but at 7 version no internet by wifi, but ok in data
i have a logcat if help (catlog app)
i test rest router, change wpa2 to wpa, change channel, wps, super wipe (allll format) every omega rom, set mac adress in router with static ip
i become crazy why not on all device its n7100 XEF french buy on amazon
Sorry for my poor english
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