Hi guys, just wanted to preface that I checked out multiple threads on 'weak wifi' issues and could not find a solution.
Here is my issue:
- I have a rooted (S-OFF/ENG-OFF) HTC Desire HD from Telus.
- I was running Android Revolution but decided to try a different ROM. At this point I had no trouble with wifi.
- Anyway, I tried an ICS ROM (IceColdSandwich-8.0.AOKP) but started noticing that the wifi connection was very weak. It would connect, open a couple of sites, but within 2 minutes, the signal would weaken to zero bars and it couldn't connect. The same thing happened with Google Play, Gmail sync etc.
- I know it is not a router issue as I have a HTC Desire Z right next to me and it has no problem connecting.
Here is what I've tried, software/hardware wise:
- Took off the battery cover and cleaned the contacts.
- For Sense ROMs, I went to advanced wifi setttings, and selected "Best Wifi Performance" and/or DLNA auto-IP.
- Turned wifi on/off.
- Tried a bunch of ROMs (Virtuous_Quattro_RC3, BlackICE v 1.50, DHD_WWE_3.12.405.1, AOSPX-1.0, etc.)
- All ROMS have been flashed after a full wipe using Android Revolution ROM's Full wipe (which works for all roms in CWM)
- Flashed new radios (26.14.04.28 and a couple of others)
What more can I do?
Thanks.
Hey I am currently running the same rom on a Telus DHD rooted.
I had the same issue and it apparently has something to do with whether your network is b or g based. If you play around with your routers settings and check to see which band you're currently using on it, change it and check it out. 5ghz is what mine is running and its working great.
Also as a note if you ever have problems with joining a ad hoc network make sure that you have it set as a open network with no passwords otherwise it won't even let you get a IP address for some reason. Its a limitation of all the ICS roms currently.
fallenkirmit said:
Hey I am currently running the same rom on a Telus DHD rooted.
I had the same issue and it apparently has something to do with whether your network is b or g based. If you play around with your routers settings and check to see which band you're currently using on it, change it and check it out. 5ghz is what mine is running and its working great.
Also as a note if you ever have problems with joining a ad hoc network make sure that you have it set as a open network with no passwords otherwise it won't even let you get a IP address for some reason. Its a limitation of all the ICS roms currently.
Click to expand...
Click to collapse
Thanks for replying. I'll try it out. If this information was already covered in another thread, I'd appreciate it if you could link me to it.
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
When I'm running an AOSP Rom, my Wifi only scans for networks after a fresh boot. Once it has connected to a network, no more scanning happens, no matter how often I tell it to. It's quite an annoyance when I have to reboot my phone every time I leave home and want to connect to a coffeeshop Wifi outside.
Once it is connected, there are not further issues - signal is good, no random disconnects or anything. Just no scanning.
Everything works fine on stock, and I've successfully tried ViperX with Sense 5, but all AOSP Roms I've been trying recently had this behavior - I have no idea what's causing it. Maybe it's an issue with the CM kernel (most Roms use some form or other of it)?
I really have no idea. Thought I'll post a question here while I go do some more troubleshooting of my own.
I also just grabbed a snippet of what I hope is the relevant part of the logs: https://paste.xinu.at/WO9zZ/
On second thought, maybe it's not AOSP based, but rather 4.3. I haven't spent much time on 4.2 with this phone, so I don't remember if the problem existed back then. If I don't find a solution, I will downgrade later to make sure.
Solved Somewhat... Not really. Worked-around maybe.
I rolled back to CM 10.1.2, and the problem went away. Seems like it wasn't AOSP causing the problem, but the new always-on feature in 4.3, which allows scanning for networks even though Wifi is switched off. I've done some searching, and other people on all kinds of devices have had problems with Wifi since this change was implemented.
Once I disabled this feature and toggled Wifi off/on once, the problem seems to be gone on CM 10.2. Not quite a proper solution, but I guess I can live with that for now, I don't really have the time, energy or experience to look into this further. Maybe somebody more enlightened than I has a proper solution.
Very frustrating issue seems to have developed for me over the past month or two in which MMS cannot be sent or received while I'm connected to WiFi. If I disconnect and switch over to LTE, MMS messages are received almost immediately and I can send them with no problem.
This is on AT&T using CM11 nightly 20140913. I used many nightlies prior to that over the summer and cannot recall when the issue developed, or if it began after a certain nightly.
I've seen this very issue (MMS problems while WiFi is connected) discussed sporadically for many other devices. Some blame it on Hangouts, but I have tried AOSP Messaging, chompSMS, and others, and it doesn't change anything. I'm *positive* that my APN is set properly (mmsc.mobile.att.net, proxy.mobile.att.net, port 80); it's also set both in the main system menu and manually in each SMS app I've tried. I can only conclude it's either an issue with CM11 or a carrier problem that has recently developed.
It's worth noting that chompSMS has a menu option that specifically forces a switchover from WiFi to mobile data when MMS is being sent/received. Even checking that option doesn't solve my problem. This makes me wonder if, perhaps, it's a ROM issue wherein the WiFi cannot be disconnected properly for this purpose? Has anyone else noticed this behavior on recent CM11 nightlies?
So I just did a nandroid backup and then flashed nightly 20141016. Sure enough, the newer nightly solves the MMS issue. However, WiFi hotspot is broken, as it has been for me on nightlies for several weeks now (thus, why I'm still running a month-old one). Too bad I don't have any backups from before the MMS bug appeared.
EDIT: Apparently this was a CM11 bug fixed on or around the 20140917 nightly. Where might I be able to find that nightly to give it a shot? At some point after 20140913, WiFi hotspot was broken, but hopefully there's a sweet spot in there somewhere. I've verified that hotspot is kaput on the M11 release. Really hoping to avoid a factory reset/clean flash if possible right now.
Hey folks, I've been having problems with my M9 for over a week and hope someone more knowledgeable can resolve this with me!
History
Firstly, I purchased this phone from Wind Mobile in Canada. Almost instantly I S-Off and migrated to Venom 1.9~ (updating along the way) where things worked flawlessly up until last week (the Venom 3.0.0 update). Along the way I've updated my firmware frequently as they have come out following Sneakyghost's Thread and the associated Google Spreadsheet. For all of the tests I am about 10ft away from my router and am always on the 2.4GHz frequency. Also worth noting that I have tested it on 5GHz and 3 other separate routers, without success. Since encountering this issue I have verified all MD5 sums of all downloads. I have a Venom 2.3.1 nandroid where this issue does not occur and rely entirely on that whenever I'm not flashing and trying to resolve this (so it is not a physical issue!).
The Issue
After updating to any ROM running Android 5.1 (with a strange exception of upgrading from venom 2.3.0 to 2.3.1 where it occurred): The Wifi on the device will not maintain a connection. At most, it may last 5 seconds. At that point, the statusbar wifi icon will hide and the data icon will take over. Some times the wifi drops so quickly, that the data icon will never disappear before the wifi drops along with its icon. If I bring the main Wifi settings menu up, I will see the entire list of saved wifi networks appear and disappear at the same time wifi is lost (almost as if it were scanning for available networks and drops whenever it does. Just a guess). If the Wifi Status window is opened (displaying specific signal strength, frequency, IP, etc), I will see the strength maintain "Excellent" while the IP address disappears whenever the connection drops. It has been suggested that wifi networks with a "space" in the SSID can cause issues with Android and other devices. Below I will post logcats of various tests, both with and without spaces in the SSID and indicate as such (doesn't seem to affect the issue).
Current Information
I have tried various firmwares that have seemed to have no affect on the results: (associated DownloadMode screenshots: one and two)
1.40.401.8
2.7.401.1 (current, what all logcats were run on)
2.8.617.4
The Logcats
http://pastebin.com/AAG0smLS - Running Venom 3.0.0 along with all of my apps - SSID: "Rose 3"
https://drive.google.com/file/d/0B00EvrpIDE-MdmNseXp4RXJ0UkU/view?usp=sharing - ARHD10 full wipe - SSID: "Rose_3"
https://drive.google.com/file/d/0B00EvrpIDE-MTHVPVTVFT195QWs/view?usp=sharing - Venom3.0.0 full wipe - SSID: "Rose_3"
more to come...
I would like to thank you all for taking the time to read this and hope that your contributions will help me come to some resolution! If there is anything you would like me to include or try, please let me know as I am open to anything.
I would also like to take the time to thank Nandroids for being awesome and for being the only thing that allows me to continue to use my phone. :angel:
Edit 1
Moments after posting, ARHD 8.1 (Android 5.0.1) finished optimizing and the issue does not occur! Since it also works on Venom 2.3.1 (Android 5.0.1) I can come to the conclusion that it is because of Android 5.1. Now if only I could figure out why....
I had wifi issues too when moving to 5.1. Connection was fine but couldn't connect to internet. What ended up fixing it was setting the wifi channel setting in the build.prop to 11 vs blank.
I doubt that's your issue but I figured it wouldn't hurt to pass along the info.
Sent from my HTC One M9 using Tapatalk
I've never had an issue with SSIDs with spaces... I've always have space in my SSID since I have wireless. I have a question: do you have router/ap which is capable of running open source firmware(DD-WRT, OpenWRT...)
hello,
what version is your M9, originally ?
I would like to thank you all for your suggestions. I have resolved the issues I've had by restoring my earliest stock nandroid from when I first rooted my phone. After, I was able to flash 5.1 based roms without any Wifi issues. For those who encounter the same issue, returning stock is likely your best bet.
Thanks again!
Easy fix for me.
So I've seen many different answers to what seemed to be the problem with the WiFi on my new M9. After connecting, data would throttle down to near nothing and occasionally come back, if only for a moment.
The fix was ridiculously simple, navigate to "Wifi Direct" under WiFi settings and rename the device in the submenu. After spending many hours tinkering with settings, reflashing, and almost returning the phone It was difficult to believe this was the difference that made the difference. I hope this helps someone and many, many thanks to the YouTube poster Rocky Xyzz to whom I cannot link yet due to my lurker status.