I used to be able to connect to my 5ghz wifi network without a problem. It stopped working recently when I flashed one of the CM9 ROMs. I thought it had something to do with the ROM but it was working on earlier CM9 builds. I flashed back to Task650's v14.1 ROM where it used to work fine but I still can't connect. It sees the network but when I click connect it doesn't do anything. I haven't made any changes on my router and I can connect to my 2.4ghz network fine. I have a Linksys E3200 router with the 5ghz network setup on channel 36, 40mhz channel width and WPA2 personal security. I've tried changing all the settings on the router but i still can't connect. I did Odin back to stock last week because I was getting a lot of reboots on the CM9 ROM I was running. After that I flashed CWM and then flashed the latest CM9 ROM. It seems like the trouble connecting to my 5ghz network started around that same time.
Does anyone have any idea what problem could be? I have a 7510 32gb Tab.
Thanks.
Does anyone have this issue? I Odin'd back to stock 3.1 and I still couldn't connect to my 5ghz network. When I click on the network it doesn't do anything. I found this issue with the galaxy nexus connecting to 5ghz wifi - http://code.google.com/p/android/issues/detail?id=22474. A lot of the posts on there describe the exact same problem I am having. I used to be able to connect fine then it stopped working. It was working fine on the stock ROM, all of Task650's ROMs and all the CM9 KAMGs. I was flashing a lot of the CM9 ROMs during the time it stopped working. It could be a hardware issue, but the fact that it sees the network fine makes me think it's not. I recently upgraded the firmware on my router and did a factory reset on it but that didn't help.
I have this same problem on my Galaxy Nexus. Put your phone really close to your router (a few inches) and I bet it will connect on the 5GHz band.
If it connects at really close range then you know the hardware is damaged... my guess is samsung has some kind of serious design flaw in their phones for this to be happening to so many people on different models of their phones.
5GHz bug?
I recently discovered that my Tab 10.1 works with low channels (eg 36) but not high channels (eg 149). I was surprised to find quite a number of postings about the same issue. Is there a firmware issue or is it a bad RF chip? It seems Samsung has a problem...
If anyone is still having this problem I found something that worked for me. The info below is copied from this issue http://code.google.com/p/android/issues/detail?id=40999#c4
"...only channels 36, 40, 44 and 48 work for 5GHz on the Galaxy Nexus. (My AP was on auto and blasting on # 149).
I manually set it to 48 and presto I was connected."
There's an error in the configuration file- /system/etc/wifi/nvram_net.txt
Take a look at the thread here http://forum.xda-developers.com/showthread.php?t=1866908
Related
Got a 32GB version.
All my other devices, windows laptops, android tablet connect up to my wifi fine. I am using WPA with AES (static IP). The HP Touchpad connects, but there is huge packet loss and it barely can keep a connection. It doesn't drop out per se, just cant get any data. Tried changing router settings, being 30cm from it etc. Still same problem. Any apps/tweaks i can try on the Touchpad?
Maybe it has something to do with Wi-Fi 802.11b/g/n with WPA, WPA2, WEP, 802.1X authentication;
maybe your router doesnt support it.
Just curious, are you running any of the Preware patches?
I am having a similar problem with my 16gb wifi model. Wifi works for a short while, then drops the signal. If I go in and turn off wifi on the device and turn it back on again - then it will work fine for another few minutes until it eventually drops the connection again.
I had this problem before I loaded any preware tweaks - and after as well. I am running the Govnah app to overclock to 1.5ghz and a few other logging tweaks.
I did some digging and it seems the most likely issue is a problem with the firmware of my router (D-link DIR-655), specifically the wireless n protocol. I am going to try updating my router firmware and see if that helps out.
By the way - no issues with my two laptops, dell streak 7, or my wii - so its definately isolated to be an issue specific to my touchpad/router combination...
I too am having problem. I don't drop the wireless connection, just a internet connection. All of a sudden nothing on my touchpad can connect to the internet, until I turn the wireless off and then back on again. Very weird. Everything else working off of my Dlink DGL-4500 works fine, except the touchpad.
I notice a few of you have Drinks, maybe thats the cause?
I'm running on FIOS and using Verizon's provided router. Works flawlessly. I've had one issue w/ WiFi, but a reboot solved that and has never come back.
I had problems with my dlink 615. TP would lose connection after 20 minutes or so. My wife's would do the same. My evo 4g had the same problem. I changed the router to the G only setting. I haven't had any problems with either TP since that change. The 615 uses draft N and was one of the early routers with this. I think it causes problems with some devices. I haven't really lost any speed either as the 615 will only connect at the speed of the "slowest" wireless card on the network, and I have some devices at g speed that are always on. I do plan to get a new router at some point.
jdexheimer said:
I had problems with my dlink 615. TP would lose connection after 20 minutes or so. My wife's would do the same. My evo 4g had the same problem. I changed the router to the G only setting. I haven't had any problems with either TP since that change. The 615 uses draft N and was one of the early routers with this. I think it causes problems with some devices. I haven't really lost any speed either as the 615 will only connect at the speed of the "slowest" wireless card on the network, and I have some devices at g speed that are always on. I do plan to get a new router at some point.
Click to expand...
Click to collapse
See my Touchpad is the ONLY device having problems, that's the part I don't get. All of my devices are wireless N as well.
TouchPad WiFi issues
Okay, I've tried every custom kernel available with almost the same results. I'm beginning to think my unit is defective, but I am hoping it is the custom kernels and not my unit. I haven't tried restoring the stock kernel but I suppose I should have before writing this. Anyway..onto the issue!
Does anyone have this problem where WiFi will randomly stop transmitting data? It happens most when I am browsing the web with the stock browser and almost all the time it is after the unit awakes from sleep. Sometimes it happens while browsing but the majority of the time it happens when coming out of sleep. WiFi is still on and connected to my network, but network activity is not there. The only way to fix it is by doing one of the following:
-Turn off and on WiFi
-Launch the HP software catalog.
The second method one seems to give the network a jump start and WiFi will begin working again and data will transmit.
Freeza I think that's a common slug, I read some other posts about it. Heck mine was doing it a lot, but not so much lately. I don't think you have defective device.
Sent from my HP Touchpad using xda premium
I have this issue too, on two Touchpads on the same wifi network (mine and my wife's). The issue vanishes on my portable wifi 4G hotspot and my much better office wifi network, so it's probably my router. I've ordered a MUCH better router, and if that kills the problem, I'll know for sure within a week.
I hear this is a common, but situation-specific issue.
phew.... Was getting worried for a bit there. Thanks guys. Hopefully the next webOS update can fix it
yoseth said:
Got a 32GB version.
All my other devices, windows laptops, android tablet connect up to my wifi fine. I am using WPA with AES (static IP). The HP Touchpad connects, but there is huge packet loss and it barely can keep a connection. It doesn't drop out per se, just cant get any data. Tried changing router settings, being 30cm from it etc. Still same problem. Any apps/tweaks i can try on the Touchpad?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1257357
I also have this problem. The wireless on the TP will stop working, even though it says it is connected. Disabling and re-enabling the wireless fixes it temporarily.
I also have an 802.11N wireless router. It is a Trendnet TEW-633GR. No other wireless device has ever had an issue with it, so I think the touchpad doesn't handle something properly...
So since updating my atrix 4g to av 2.3.6 b 4.5.141 update my home wifi connectionto the device has been turning on and off. I have narrowed it down to the router belkin g+ mimo just wanted to make others aware. Had no issue before this update.
Any info on why this has happened?
All other devices stay connected as usual.
The Radio that comes with 4.5.141 is 1.77.37P, which I am also running and has given me the same problem. My former radio (1.77.30P) that shipped with 4.5.91 did not have this issue for me.
I fixed it by doing the following:
Settings > Wireless & Network Settings > Wifi Settings
From there, hit the menu button and choose advanced.
Click the "WiFi Sleep Policy" and set it to Never
This will stop the wireless from shutting off when the screen is off. Hope it helps!
Did you power off/on both the router and phone? Always worth a try before spending too much time do other possible fixes .
If the sleep policy is already set to never and you're still experiencing the problem you could:
1) flash the older radio
2) debug the problem. Install the sendlog app in marketplace. Recreate the behavior a few times. Open sendLog and email it to yourself. Look at the sendlog output to see why your phone is dropping the connection (wifi auth errors, signal issues, etc).
My home wifi is an old WRT54GS with WPA2 PSK and I've had no problems. Work is a 802.1x EAP. The other day I was at a coffee shop that had WPA2 and my Atrix was having some issues authenticating with the wifi router. After a few tries the phone finally connected. Not sure if that's the same problem you're experiencing.
Thanks I tried that.
What is happening is the connection just drops ff while on web or youtube ect.
It disconnects for a sec then reconnects. does this randomly. Even with the setting to never still randomly disconnects and reconnects.
Like I said no other wireless device does this and the atrix just started after the update.
may have to change routers hope not.
Will try the log app and post the results later.
Why change your router when it's the phone that has the problem? You need to address the root cause, not try and bandaid it.
Any possibility you can flash the 36P radio and try that? (Need to unlock your bootloader though).
Could also try a hard reset (30/30/30) of your router. This will load back all defaults, and sometimes clears up connection issues if you have them, but since this started with the update, it shouldn't be that.
I dug out my old netgear. atrix hasnt dropped connection once.
Something here conflicting with the belkin making the atrix drop it.
Tried the log file. Lol 1.2 mb of confusion.
Thanks everyone.
Maybe get belkin to send me a new router.
Just for testing purposes can you try connecting to the belkin with no WEP/WPA/WPA2/whatever enabled?
btw don't post sendlog output. log could contain sensitive information .
Its a known issue on Belkin routers and the 2.3.6 gingerbread update. Something to do with DHCP Lease renewal. Try this
Go in to router settings
Select LAN Settings
Change Lease time from forever to 2 days
Reboot router and phone
This fixed the problem for me
Sent from my MB860 using Tapatalk
I resolved the problem. Belkin rep explained to me that I need the N band.
I was using G the new update for the atrix updated the radio. My router was old and the firmware is outdated. Sounds like bs to me. Anyway bought a linksys today. Problem solved.
I was impatient. Will try changing the date just for giggles. For now Im surfing xda.
Edit: changing the lease time did not resolve the issue for me. The new router is working perfectly.
we have a Belkin 750DB, and a Netgear WNDR3300 and are experiencing the same issues on the belkin, but not the netgear. I haven't had a chance to try the difference between N and G on the belkin. We haven't found a resolution yet, the router is only a few months old, and costs way too much to change out... any else solved this really yet? besides falling back to the 36P radio?
I run a Netgear on G and another Netgear on N at home, and have no problems with either router with any radio. My network printer runs off the G network, so I switch the Atrix to that if I need to print, otherwise my Atrix connects to the N router.
(Split the G and N so I can run N devices only on one and maintain highest transfer speeds).
I think the sales guy was talking BS. Atrix works fine on either band.
..
Just a update on this...
I have tested Netgear, and Linksys routers
Both have performed flawless
It is only on the Belkin router that the issue occurs at least for me.
So it must be some conflict with the new radio and Belkin.
If anyone has had luck with Belkin please let me know your settings.
I think it's somewhere in the router settings, but my wrt54g at home with dd-wrt can connect just fine with my Epic 4G Touch running Cyanogen 9 (or any other ICS rom for that matter). The one we have at work (also wrt54g running dd-wrt) won't. I'll reference this thread here: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=667631
I've changed the "no acknowledgement" setting, changed security modes, disabled the SPI firewall, and even tried factory defaults. But it just doesn't want to connect for some reason, however when I use a gingerbread rom it will connect just fine.
So my question is, if anyone has found a solution as to why ICS phones don't like connecting to DD-WRT routers.
Widespread issue
I don't know if it's any consulation but this issue seems to be affecting a lot of people. << link to thread on sprint's site but I'm new to this forum so can't post it >>. No one on that site mentions dd-wrt but that doesn't mean it isn't a dd-wrt specific issue.
I am also expericing what I think is the same problem. I am using the Sprint Nexus S 4G connecting to my linksys wrt320n router with dd-wrt build 18946M (I upgraded from 14700(ish) to see if that resolved my issue but it didn't).
The issue seems slightly more complicated than a simple inability to connect. Before upgrading to ICS (in stock ginger bread), a few days ago, I would occasionally see my phone attempting to connect to my router and failing. Now with ICS, my device connects, gets an IP address and the router wifi status page shows the device as connected with good signal strength, but alas, there seems to be no network connectivity.
I decided to try CryogenMod 9 and see if the issue was resolved in their build. So I flashed the lastet (update-cm-9-20120411-NIGHTLY-crespo4g-signed.zip) cm9 mod and still experience the same issue.
Any help anyone could provide on this issue would be swell.
Confirmed it is DD-WRT
I came across this thread immediately after upgrading my router from stock to DD-WRT. Immediately the wifi on my phone stopped working. My phone, Nexus S 4g will not even see the network. Conveniently my neighbor has the same router as I do, a Cisco e3000 with a factory rom. I can connect to his network without any problem. Ugh. I love DD-WRT. Maybe I'll try a Tomato firmware... Well at least all my other phones/tablets work. It is specific to the Nexus S 4g.
UPDATE: I believe it is tied to the mixed network mode on my 802.11n router. I tried my old 54G in G only mode and it is working fine with my phone
scicarb said:
UPDATE: I believe it is tied to the mixed network mode on my 802.11n router. I tried my old 54G in G only mode and it is working fine with my phone
Click to expand...
Click to collapse
Confirmed. I changed the wireless mode to 2.4Ghz N only and everything works. Mixed Network mode was giving the Nexus S fits.
I just *successfully* got my MotoE/Android5.1 working on DD-WRT after 2 days down (problem started w/new version of DD-WRT on a repeater)
MY WORKING SOLUTION: Turned of "auto" on the channel selection of my 2.4Ghz channel on both primary and repeater routers, turned control channel to 20 on the primary (where the DDWRT offerred a choice) then restarted phone. It was probably something with auto channel on one or both of disparate routers.
Phew. Nasty glitch.
I have searched all over and I don't find an answer, if I'm missing a thread please just point me in the right direction.
My home wifi has been working with my Note just fine since I got the phone (cue ominous music) up until yesterday. Last night, it started asking me for a password (which was weird, because it hadn't since I first got the phone and set the connection up), and I put the password in, but it kept saying "authorization error." I am really frustrated, I rebooted the phone, the router, removed the home wifi connection (the "forget" button) and reinput it -- I even booted into "safe" mode to make sure it wasn't some app -- no joy. It's a very simple linksys router, WPA/WPA2 security, all the other tablets/computers/phones in the house work just fine (tablets/other phone Android, laptops Windows.) And my Note was working just fine until last night -- no recent software install or update, it was seemingly just random. It's a stock Verizon Note, I haven't even bothered to root since it does everything I want.
Here's the kicker: I connect to OTHER public networks just fine. I connected to my work and McDonald's wifi this morning, no problems.
What could be wrong? I really need to be able to use my wifi at home, I don't see anything in Google or on the boards about this. I am hoping my search-fu is weak and someone knows what is up with this.
restore defaults on your router, then setup a new password.
Hope this Helps....
MaureenMun said:
I have searched all over and I don't find an answer, if I'm missing a thread please just point me in the right direction.
My home wifi has been working with my Note just fine since I got the phone (cue ominous music) up until yesterday. Last night, it started asking me for a password (which was weird, because it hadn't since I first got the phone and set the connection up), and I put the password in, but it kept saying "authorization error." I am really frustrated, I rebooted the phone, the router, removed the home wifi connection (the "forget" button) and reinput it -- I even booted into "safe" mode to make sure it wasn't some app -- no joy. It's a very simple linksys router, WPA/WPA2 security, all the other tablets/computers/phones in the house work just fine (tablets/other phone Android, laptops Windows.) And my Note was working just fine until last night -- no recent software install or update, it was seemingly just random. It's a stock Verizon Note, I haven't even bothered to root since it does everything I want.
Here's the kicker: I connect to OTHER public networks just fine. I connected to my work and McDonald's wifi this morning, no problems.
What could be wrong? I really need to be able to use my wifi at home, I don't see anything in Google or on the boards about this. I am hoping my search-fu is weak and someone knows what is up with this.
Click to expand...
Click to collapse
I have been experiencing this problem for the past 4 days. I have owned my Note II since December 25, 2012 and it has been working on any WIFI AP ive tried. 4 days ago in the middle of the day, my phone started giving out "authorization error" and would not let me log in to my home WIFI. I have 4 computers, 3 smartphones and other devices all working perfectly in my home WIFI. My problem even occurred when connecting to open, unsecured WIFI AP also. Nothing seemed to work. I called Verizon and did all the steps leading up to factory reset. With no luck on any tricks or tips from them I called Samsung. They walked me through the same processes and everything, so I decided to do a factory reset. This did not fix anything. I still get "authorization error" and "wrong password" on any WIFI i try to connect to.
I found out yesterday if I stand within 5 feet of my WIFI router I can connect and browse the internet for a few minutes until it kicks me off and does the same old "authorization error". If I sign in to my WIFI within the 5 feet and walk away, it disconnects and again, gives me the error messages.
I called Verizon back and they are sending me a replacement phone.
TL;DR:
Try accessing your WIFI when you are right next to it.
If problems still persist, call your carrier.
I hope your phone isnt as busted as mine.
Argh, that's bad. At least my phone connected to open networks so I knew the hardware was ok -- I wiped the router and set it up again (per the suggestion in this thread) and I'm good for now. (Embarrassed I didn't think of that myself) Hope you have better luck with your replacement phone!
soaptylerdurden said:
I have been experiencing this problem for the past 4 days. I have owned my Note II since December 25, 2012 and it has been working on any WIFI AP ive tried. 4 days ago in the middle of the day, my phone started giving out "authorization error" and would not let me log in to my home WIFI. I have 4 computers, 3 smartphones and other devices all working perfectly in my home WIFI. My problem even occurred when connecting to open, unsecured WIFI AP also. Nothing seemed to work. I called Verizon and did all the steps leading up to factory reset. With no luck on any tricks or tips from them I called Samsung. They walked me through the same processes and everything, so I decided to do a factory reset. This did not fix anything. I still get "authorization error" and "wrong password" on any WIFI i try to connect to.
I found out yesterday if I stand within 5 feet of my WIFI router I can connect and browse the internet for a few minutes until it kicks me off and does the same old "authorization error". If I sign in to my WIFI within the 5 feet and walk away, it disconnects and again, gives me the error messages.
I called Verizon back and they are sending me a replacement phone.
TL;DR:
Try accessing your WIFI when you are right next to it.
If problems still persist, call your carrier.
I hope your phone isnt as busted as mine.
Click to expand...
Click to collapse
Ok............ wow you have me 100% nervous now. I've been experiencing this issue ever since I unlocked, rooted and ROM'd my Note 2 back in the middle of December, and I experience the problem with only my Wireless-N SSID on my router. I can connect to the Wireless-G band just fine but the N one gives me this error no matter whether it's open or not. I seriously hope this isn't an issue of broken hardware..............
I figured this was worth mentioning. I have 3 Note 2's in my household, 2 of them are running Beans Build 5 and Perseus kernel overclocked and the other phone is totally stock.
All 3 phones have the exact same issue of connecting to the 802.11 N band on my router. They connect to the G band just fine. I think this rules out any worries about it being a lemon issue. Most definitely is a Samsung software issue that's been happening to multiple models going back a few years. Here's a google search of this issue using non-phone specific parameters. Notice how ALL phone specific forums point to a Samsung device.
I have a bad feeling that this is not something that will be getting resolved any time soon.
Edit:
The plot thickens. I have performed some tests on my router to see if I could get my phone to connect. Well here's my results:
5Ghz band = Wireless-N Only = Authentication error occurred
5Ghz band = Wireless-A/N Mixed = Connects instantly
2.4Ghz band = Wireless-N Only = Authentication error occurred
2.4Ghz band = Wireless-G Only = Connects instantly
The problem is clear. It's Wireless-N. I can connect just fine at Wireless-A speeds (54mbps max signal) and everything up to Wireless-G, independent of frequency, but as soon as I try to force Wireless-N onto my phone, it craps out and fails to authenticate. This happens regardless of whether I have the network encrypted or not.
And based upon my google search I have linked to in this post, I doubt this is something we can expect to be fixed anytime soon. Oh yeah and for the record, when I have my router set to Wireless-N only mode, I was able to connect instantly without error on my crappy old HTC Thunderbolt running a hacked together AOSP 4.0.3 ROM.
Yep............... GG Samsung
wireless n has been a unreliable joke since it was released...my favorite routers are the linksys wrt-54gl running linux dd-wrt firmware. one of the most affordable rock solid routers built. its only g band but most people do not need anything faster for home use. heck most of us cant afford the t1 type connection speed to utilize n band anyway.
Exact same problem as well...I'll have to try the Wireless N-only vs. Auto to see if that fixes it...
EDIT: Both wireless mode settings of 'N-only' and 'Auto' caused the problem. I had to set it to 'Legacy' in order to get the connection to stick without authentification errors. Have an ASUS RT-N66U router...
EDIT 2: Did the same thing on my Cisco E3000 and it worked as well.
Really looks like a Sansung wifi bug on the Note 2....
vortmax said:
Really looks like a Sansung wifi bug on the Note 2....
Click to expand...
Click to collapse
It's not Samsung. There have been issues with myriad devices and wireless N pretty much the whole time it's been around. Android OS or the the N standard-- I personally know people with other manufacturers hardware and the exact same issues. If it's an OS problem, you would think it would be fixed by now, but who knows, like was mentioned above, very few people need the bandwidth that wireless n can theoreticly provide.
Good Luck,
Jason
jacampb2 said:
It's not Samsung. There have been issues with myriad devices and wireless N pretty much the whole time it's been around. Android OS or the the N standard-- I personally know people with other manufacturers hardware and the exact same issues. If it's an OS problem, you would think it would be fixed by now, but who knows, like was mentioned above, very few people need the bandwidth that wireless n can theoreticly provide.
Good Luck,
Jason
Click to expand...
Click to collapse
It's definitely something specific with Samsung and the N2 since my cousin's G3 connects to the same router on 5GHz WirelessN/Auto with no issues at all. I think they have a bug to fix...
Can someone else perform a check with their Note 2 on a Wireless N only setting? It seems this is a bug that really need to be fixed.
vortmax said:
Can someone else perform a check with their Note 2 on a Wireless N only setting? It seems this is a bug that really need to be fixed.
Click to expand...
Click to collapse
Mines been working on N only since I got it. Rooted and running about 6 different ROMs.
Sent from my SCH-I605 using xda premium
I just had this issue come up when moving to an AOSP ROM this morning. I even nandroided to a previous ROM that had working WiFi and still not working. I restore defaults on my router and reset all my security settings. Still getting the same authentication error.
Sent from my SCH-I605 using xda app-developers app
For the people experiencing this issue, are you on 4.1.1 or 4.1.2?
vortmax said:
For the people experiencing this issue, are you on 4.1.1 or 4.1.2?
Click to expand...
Click to collapse
I have tried roms that were 4.1.1 and 4.1.2 with no luck.
Sent from my SCH-I605 using xda app-developers app
I am pretty much to the point of using Odin to go back to stock and see if that fixes it. I went back to stock rooted rom that was my first backup and the problem still carries over.
Sent from my SCH-I605 using xda app-developers app
Hello guys, I have 2 smartphones which are ''Samsung Galaxy Grand 2'' and ''Nokia 5''. Both of them supports 5Ghz Wi-Fi band. My router is ''Tp-Link Archer c50''.
The problem is both of my phone doesn't detect the 5Ghz band at all. There is no problem in the router. Laptops works well with it. I took the router back to the shop from where i bought it, they found out it's working with there smartphones (don't know the model though).
It's Good to say that my router only supports channel 36, 40, 44 and 48 of 5Ghz band.
I tested my mobiles channels by connecting each other via Hotspot and found out that they are always using channel 153. So i thought it was the problem. I also asked for support from Tp-link and Nokia's online care but they failed to help me out.
Now few days ago for some reason i installed cm 14.1 rom in my Grand 2 and there i found out that it's detecting 5GHz band but whenever i tried to connect the rom kept crashing. Anyway for whatever the reason i installed that rom didn't worked out for me so i got back to stock rom.
There i found out my Grand 2 is detecting the 5Ghz band in stock rom which never happened before. It was working well but after few hours it disappeared. From then after few hours mobiles battery got empty and it shut down. After charging i switched on the mobile and found out that its detecting again but after few hours it disappeared again. I restarted the mobile but this time and from then i didn't seeing the 5Ghz band anymore.
So, can anyone tell what's the problem!!!!???