Related
Is anyone else having issues with the WiFi stalling and having to reset it, even though signal strength shows as excellent?
It's not a channel interference issue as I know what channels are in use, plus its doing the same on 3 different networks where other devices work fine, I'm using WiFi fixer to reconnect but its still problematic.
What have others found to be the best solution?
Samme issue here. Wifi keeps on disconnecting/loosing the connection and is most of the time unable to reconnect. Have to either turn wifi off/on or choose "forget" and reconfigure the AP my Hero in order to get it to work again.
It´s a Linksys WRT54GX running WPA/WPA2 + TKIP.
Have used an iPhone 3G on the same router for a year now without ´any´ problems.
I'm using WiFi quite often but I don't have this problem with my Hero.
Are you absolutely sure that there isn't any interference? It might be that the Hero is just a bit more sensitive than your iphone.
Today I found G-mon at Market which scans around for WiFi-networks. Perhaps you'll find out that there is a network that's interfering constantly. I've had that a few years ago and then found out that the bus-company uses WiFi on their busses which uses the same channel as I did with my WiFi-network.
Thx for the tip. Checked and no interference.
Also having this problem with a Linksys WRT54G. No WPA though.
I don't trust this router at all; using WPA and connecting a Dell Axim X51v to it in the past used to knock out WLAN on router, needing a hard reset.
same problem here. Wifi is disconnecting randomly within a few meters from the Airport extreme. It also reconnects again...most of the time....without me doing anything.
i'm also having problems with wifi - using a linksys befw11s4 with wep. i've got everythign else turned off - have followed all the instructions i can find here in the forums, and not had any success :/
If you press the Menu button in the Wifi settings you can select Advanced. There's an option there that defines when Wifi is disconnected. If you set this to Never than the Wifi connection will be stable. (At least in my case it is).
Again, thx for the tip but this is not really considered a "solution" but rather a workaround.
I don't like the idea of having it on "allways on". A real battery drainer and it shouldn't be necessary.
I had similar issues with my wifi (Linksys WRT160NL) until I installed "Wifi Fixer" from the market on my hero. Since then wifi runs without problems!
I had similar problem, Linksys WRT54G v1.0 running fairly old (but latest available) Linksys firmware, with WPA/PSK.
Yesterday, re-flashed router to Tomato (based on HyperWRT), setup for WPA2/PSK(AES) and now all is working perfectly, no problems at all.
So looks like some incompatibility between the Hero and the Linksys firmware, for WPA.
Well, I'm running the latest firmware for my router but have now done some other configuration changes and it seem somewhat consistent with your findings.
Previously it was running in a "WPA, WPA2 + TKIP" mode but it has now been working flawlessly since I change it to "WPA2 + AES". Hence:
- WPA2
- AES
=
- WPA, WPA2
- TKIP
=
Info, update on the router: I'm having a WRT54GX, not WRT54G.
interesting; I had no choice but to upgrade, as the newest firmware for the v1.0 WRT54G doesn't - I believe - support WPA2.
Since I had many other wireless clients working fine with WPA (not WPA2), but not the Hero, one wonders if there are some WPA bugs on the Hero that get tickled by older routers, or just that the Hero is being less lenient than other clients.
glad yours is better too, anyway
I found that wifi performance and stability on the hero improved a lot when I changed my AP from dynamic 802.11 b/g/n operation to 802.11g only. I've seen other boxes with linux having similar issues with this AP (D-Link DIR-655), which points towards a driver issue. Wifi works better on Linux kernel 2.6.30 and later on notebooks so things should improve once HTC produce a build that include a more recent kernel. Wifi was quite a headache on notebooks too with the drivers in kernel 2.6.27.x that is included in the current hero firmware.
I have same problem - frequent line drops whne full strenght signal shows
I also have a Linksys WRT54G - never had any problems before.
tried wep and wpa -no difference.
Also tried some "always On" utility from the market place, it only helped reset it quicker.
As stated above, mine got more stable when fixing router to WPA2+AES but I now realize that I still do experience connectivity issues, although less frequently then before...
i don't think this has anyting to do with the router. I got a router from HUAWEI,forgot its brand, but not linksys for sure. I've tried the university wifi as well. they all have the same issue.
Mine is working great with a Belkin.
Looks like a problem with the Linksys firmware.
Anyone tried a firmware upgrade on the router?
Uqbar said:
Mine is working great with a Belkin.
Looks like a problem with the Linksys firmware.
Anyone tried a firmware upgrade on the router?
Click to expand...
Click to collapse
Indeed, if you read up just a few posts, you'll find that question answered
that said, although things seemed initially to get better, I'm still seeing regular drop-outs with the upgraded router, and now still with the Hero upgraded to the HTC 2.0 ROM.
I do note that it seems to drop most when I'm sitting quite close to a different strong wireless client, e.g. a laptop. Perhaps the Hero just isn't a strong enough signal, and gets swamped?
Anyone else notice a correlation between dropouts, and proximity to other clients?
I've tried several builds:
Darkstone Froyo
DarkStone FroyoStone
mattc Froyo with Sense
mattc Froyo without Sense
shubcraft
Xcelsior
mccm v1.7
WiFi just does not work at home. It'll connect, but I can't actually browse anything. It comes back immediately as a "page not found" error. Today I took my phone around town specifically to test WiFi on other networks. It worked perfectly on two open networks. There were no issues at all. It works at my office as well.
My network at home is wired as:
Internet --> DLink Gamer Lounge (wired router with special features) --> Linksys WRT54G wireless router
The DLink has DNS and DHCP services. The Linksys has none and is assigned a static IP.
My network at work is wired as:
Internet --> DLink Gamer Lounge --> everything else including a Linksys WRT54G setup just like at home
There is a Windows Server setup to take care of DNS and DHCP. The Linksys has same setup as at home.
At home, I disconnected the DLink, enabled DHCP on the Linksys, then my Android phone worked on wifi just fine.
I reconnected wired router and reset all settings. Android wifi doesn't work anymore.
I don't think my wired router is incompatible. I'm wondering if the wireless router not being the DHCP agent has anything to do it. Other wireless devices connect fine like this. My phone in WinMo connects fine. My friends' iPhones connect fine. My friends' native Android phones connect fine. Every wireless device (except HD2 Android) connects to the network and works just fine.
Anyone have any suggestions?
Is there a route tracing program for Android? Or something that will show me all the IP information (including DNS)?
Update:
DarkStone1337 said:
Because you have no DHCP on your wireless router, your IP address and DNS server and default gateway settings aren't being set by Android. No idea why. You'll need to do this manually in Android by pressing the windows button in the wifi network settings and setting the right values from there.
Click to expand...
Click to collapse
I just used an app to check IP settings. IP address, subnet mask, gateway, DNS, and everything are being set properly (there is a DHCP server on network, just not on WiFi router). I tried to setup a static IP address and other settings. Whenever I try to connect that way, it gets to "Obtaining IP address" and then fails, cycling through the whole process. Is it possible the code for IP stack (or IP Tables) in these builds of Android are not complete?
Update 2:
DarkStone1337 said:
Not an app, but using ADB logcat is sufficient enough.
If you have adb set up then follow this: https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file
Click to expand...
Click to collapse
Just read about ADB (Android Debug Bridge) briefly. I think this will be a bit out of my league. I'm not that familiar with Android / linux. I'll post in the other thread asking if someone else more skilled can grab one. If not, I'll see about trying to figure it all out this weekend.
Same issue
FreakyFerret said:
I've tried several builds:
Darkstone Froyo
DarkStone FroyoStone
mattc Froyo with Sense
mattc Froyo without Sense
shubcraft
Xcelsior
On all of them, WiFi just does not work. It'll connect, but I can't actually browse anything. It comes back immediately as a "page not found" error. Today I took Matt's Froyo with Sense around town specifically to test WiFi on other networks. It worked perfectly on two open networks (Quizno's and McDonald's). There were no issues at all.
My network was wired as
Internet -- Wired router (with special features) -- wireless router
The WiFi router was basically treated like a switch with its DHCP turned off. I disconnected the wired, enabled DHCP on the wireless, then my Android phone worked on wifi just fine.
I reconnected wired router and reset all settings. Android wifi doesn't work anymore.
I don't think my wired router is incompatible. I'm wondering if the wireless router not being the DHCP agent has anything to do it. Other wireless devices connect fine like this. My phone in WinMo connects fine.
Anyone have any suggestions?
Is there a route tracing program for Android? Or something that will show me all the IP information (including DNS)?
Edit: It should be noted other Android phones (that came with Android) do work fine. Just these HD2 builds is the problem.
Click to expand...
Click to collapse
I just want you to know I'm in the same situation as you. My router is a Belkin Wireless N router (WPA2 encryption). I get a valid IP address and I can ping the router but no DNS or access past the router. There was an earlier version of an Android build (I think a MattcFroyo) that worked with my wifi set-up. But I need BT headset support and the Darkstone build seems to be the only one that reliably works with my BT devices. (BlueAnt T1 & Motorola EQ7)
Please let me know if you find a solution that works!
Thanks.
Sept 4 Update. The only version that I have found that provides both Wi-fi connectivity and BT head set is the Shubcraft version 1.4 for my router configuration. Version 1.5 doesn't and neither do the latest Mattc and Darkstone builds.
Hell, I can't even get my Wifi working at all. Darkstones V1... Wifi just says "Error". Have the latest zImage, and everything. :/
Shushunmire said:
Hell, I can't even get my Wifi working at all. Darkstones V1... Wifi just says "Error". Have the latest zImage, and everything. :/
Click to expand...
Click to collapse
jinhenry, I'll let you know.
Shushunmire, are you using HD2Froyo or FroyoStone (clean or Sense)? Also be sure to post in Darkstone's thread that relates to the build. I know HD2Froyo v2 was giving error for wifi, but his latest update fixes that.
I tried various market apps to do network diags on the phone. All they offered was basic ping. When trying to ping anything on the wifi, it just fails right away. It's like it's not even seeing the network and just saying no network around. I even tried to ping the phone's own local IP and it failed. I tried looking for a traceroute type app, but there was none.
I installed Cirtex app. On cell connection, it pulls up the IP info of the wifi (but cell data works):
Device IP Address:{cell IP}
Interface name:/usb0(usb0)InetAddress:/{Ip of wired router, DHCP server, DNS server}
Interface name:rmnet0(rmnet0)Inetaddress:/25.1.238.x (don't know)
Interface name:lo(lo)InetAddress:/127.0.0.1
On wifi connection, it gives error:
Can not get te IP Address for the device. (errors their's)
Interface name:eth0(eth0)InetAddress:/{correct wifi ip}
Interface name:usb0(usb0)InetAddress:/{correct wifi ip}
Interface name:lo(lo)InetAddress:/127.0.0.1
If I use a static IP, and set the gateway to the actual network gateway (wired router, DHCP server, DNS server), phone tries to connect until it gets to the "Obtaining IP" stage, then it fails and cycles over. If I set the gateway to the wifi router (which is no more than a wifi access point) it will connect.
To repeat cause I know you have a lot going on: other wifi devices work on this network fine (using static or dynamic ips) including windows laptops, mac laptops, xbox, Wii, iphones, winmo phones (this one even), and even other android phones.
If I set the wifi router as the gateway (plug internet directly into it and turn on DHCP on wifi router), everything works fine. I don't even change its static IP.
Hopefully some of this will help. :/ The more I play around with it, I get the feeling the IP stack is the cause.
I AM HAVING THE SAME PROBLEM!!!! my lil bro got an htc hd2 as well n we got them the same day n when i flashed android on his and mine... his wifi was working while mine was not and i have tryed so many different builds but nothing solves the problem...it searches but at the end it says unable to scan networks....anyone plz help i really need wifi
p.s we both are on....
rom: core cell series
build: hd2 froyo v2.1
his hd2 works perfect while my wifi is not
jinharry said:
I just want you to know I'm in the same situation as you. My router is a Belkin Wireless N router (WPA2 encryption). I get a valid IP address and I can ping the router but no DNS or access past the router. There was an earlier version of an Android build (I think a MattcFroyo) that worked with my wifi set-up. But I need BT headset support and the Darkstone build seems to be the only one that reliably works with my BT devices. (BlueAnt T1 & Motorola EQ7)
Please let me know if you find a solution that works!
Thanks.
Click to expand...
Click to collapse
have you tried setting the router to use G only? i had an issue with the newer builds on a d-link 635 that was the same, it woudl work then suddenly woudnt work at all, rebooting the phone didnt help, changing the router to use G only instead of mixed seemed to fix the issue
Here's my issue. On my phone I could connect to wireless fine, my two sons liked Android on the hd2 so much that we picked up 2 more hd2's, that's where the problem started. Any one of the phones can work on wireless just fine... but try and connect any of the others and while they do connect, they don't work. Any of them.
It's almost as if they are seen as the same device or something. Some kind of unique id is missing or something.
Ducter said:
Here's my issue. On my phone I could connect to wireless fine, my two sons liked Android on the hd2 so much that we picked up 2 more hd2's, that's where the problem started. Any one of the phones can work on wireless just fine... but try and connect any of the others and while they do connect, they don't work. Any of them.
It's almost as if they are seen as the same device or something. Some kind of unique id is missing or something.
Click to expand...
Click to collapse
are they using the same builds? its possible that the mac address being used is the same and the router sees it as the same device
Richy99 said:
have you tried setting the router to use G only? i had an issue with the newer builds on a d-link 635 that was the same, it woudl work then suddenly woudnt work at all, rebooting the phone didnt help, changing the router to use G only instead of mixed seemed to fix the issue
Click to expand...
Click to collapse
Didn't help Thanks for suggestion though.
unless it has changed recently, all HD2-android builds are using the same MAC-address. So this could very well be your problem.
Ducter said:
Here's my issue. On my phone I could connect to wireless fine, my two sons liked Android on the hd2 so much that we picked up 2 more hd2's, that's where the problem started. Any one of the phones can work on wireless just fine... but try and connect any of the others and while they do connect, they don't work. Any of them.
It's almost as if they are seen as the same device or something. Some kind of unique id is missing or something.
Click to expand...
Click to collapse
FreakyFerret said:
jinhenry, I'll let you know.
Shushunmire, are you using HD2Froyo or FroyoStone (clean or Sense)? Also be sure to post in Darkstone's thread that relates to the build. I know HD2Froyo v2 was giving error for wifi, but his latest update fixes that.
Click to expand...
Click to collapse
I'm using FroyoStone (w/Sense).
And yeah, will do that. I just figured it wasn't working at all until I saw your post.
I use currently mattc 1.5b w/sense and had (have) the same problem with
DHCP is on. I allways got the status "Obtaining IP address" and nothing happen.
I played a little bit with the static IP settings...I set DNS 1 equal the the gateway entry and then wifi works....but only static.
I think this is a router issue...I use Speedport W 502V.
I doubt it's a router problem since all other devices work perfectly.
same issue, please give your attention, developers, thanks.
I've had the exact same problem with my Wi-Fi using several Android builds. Tried static IP and every possible setting I could find and solved it by add the Mac-adress in my router setting. (192.168.1.1) and now it works perfectly. I'm now using shubCRAFTv1.3
Hope you can fix your problem this way. Cheers.
Sent from my HTC HD2 using XDA App
I'm having issues with Wifi too. I'm also currently using mattc Leo + Froyo w/Sense 1.5b. My problem isn't that the phone doesn't connect via wifi... it does. The problem is that after it connects the connection seems to go dead/times out after about a minute or two.
For example, after installing the build and running through the setup, i connect to wifi, then sign in with my gmail account. This all works as it should. Then by the time I want to sign in to my facebook/twitter accounts during that same setup sequence, it no longer can connect to the internet. My suspicions of the connection having a "timing out"-like occurrence was then confirmed when I turned off wifi, and switched it back on. Everything would work and sync for about a minute, then it would cut out again (but it would still show a full strength connection via wifi). It's a bit of a strange one.
I used Energy's build before trying this one, and WiFi worked flawlessly. So I'm assuming its not my router, but something up with my device and/or its settings.
Thanks in advance for any tips/help.
snozze said:
I've had the exact same problem with my Wi-Fi using several Android builds. Tried static IP and every possible setting I could find and solved it by add the Mac-adress in my router setting. (192.168.1.1) and now it works perfectly. I'm now using shubCRAFTv1.3
Hope you can fix your problem this way. Cheers.
Click to expand...
Click to collapse
What do you mean by you added your phone's MAC address to the router? Where exactly in the router? Guessing you mean you set your phone to use a static IP, then set your router's DHCP client to always assign that IP to the phone?
wibblewobbles said:
I'm having issues with Wifi too. I'm also currently using mattc Leo + Froyo w/Sense 1.5b. My problem isn't that the phone doesn't connect via wifi... it does. The problem is that after it connects the connection seems to go dead/times out after about a minute or two.
For example, after installing the build and running through the setup, i connect to wifi, then sign in with my gmail account. This all works as it should. Then by the time I want to sign in to my facebook/twitter accounts during that same setup sequence, it no longer can connect to the internet. My suspicions of the connection having a "timing out"-like occurrence was then confirmed when I turned off wifi, and switched it back on. Everything would work and sync for about a minute, then it would cut out again (but it would still show a full strength connection via wifi). It's a bit of a strange one.
I used Energy's build before trying this one, and WiFi worked flawlessly. So I'm assuming its not my router, but something up with my device and/or its settings.
Thanks in advance for any tips/help.
Click to expand...
Click to collapse
sounds like the same issue i had, i had to set my router to use G only rather then mixed g/n to fix the issue
FreakyFerret said:
I've tried several builds:
I don't think my wired router is incompatible. I'm wondering if the wireless router not being the DHCP agent has anything to do it. Other wireless devices connect fine like this. My phone in WinMo connects fine.
Anyone have any suggestions?
Edit: It should be noted other Android phones (that came with Android) do work fine. Just these HD2 builds is the problem.
Update:
I just used an app to check IP settings. IP address, subnet mask, gateway, DNS, and everything are being set properly (there is a DHCP server on network, just not on WiFi router). I tried to setup a static IP address and other settings. Whenever I try to connect that way, it gets to "Obtaining IP address" and then fails, cycling through the whole process. Is it possible the code for IP in these builds of Android are not complete?
Click to expand...
Click to collapse
I had problems before with a similar setup, and I can tell you that NOT having the DHCP on the router (gateway out) is the issue. You have to remember that "these HD builds" are still in development with WIFI issues still being ironed out.
My advice, try using fixed IP assigning (on wireless router) using the phone's wifi adapter mac address.
Right now your phone is going to the wifi router who will be sending packets to the DHCP server and back to wifi router so that it goes out. Also usually, there tends to be a conflicts because some DHCP clients just assume that the server for DHCP is the gateway too.
or... Check that your DHCP server (if another machine) is doing internet sharing, in case devices try to use its address as a gateway, which will then go out anyway through the wifi router.
The fact you report may be in my oppinion, useful for the devs (eventually), but dont get high hopes for this to be on the immediate to-do list
I just picked up my wifi only Xoom today, and discovered that it appears to have an issue that's virtually identical to one that the Thunderbolt shipped with as well: I simply cannot make L2TP over IPSec connections. In fact, judging by the logs on the server, the VPN client in Honeycomb does not even try to connect. Checking the server side logs shows no entries whatsoever. However, if I go back to my Thunderbolt (which now, being rooted and on a different ROM, will work) I can connect to the same VPN, with the same settings, with no issues. But when I try from the Xoom, all I get is "Unable to connect to the network. Do you want to try again?"
However, I can establish a PPTP connection from the Xoom without any problem (which is, again, exactly the behavior that my Thunderbolt exhibited until I was able to go to a new ROM), BUT, once the connection is established, the Xoom behaves as though it has NO internet connection whatsoever.
I would REALLY appreciate help with this. Thanks
Thats odd. I have had no issues with L2TP and IPSec. Works slow for sure but was working fine. I was on wifi at home. When I tried via 3g it was ungodly slow, took like 5 attempts to connect. Any info would be nice
PPTP more info;
http://code.google.com/p/android/issues/detail?id=4706
My wifi is spotty, at best. I've tried every ROM but every ROM has the same issues: wifi will work for awhile, then it won't, then I power the phone off, then it doesn't work after I power it back on, then I disable it and re-enable it, and it may/may not work. Basically, it's totally unreliable.
I AM running a 2.4 mouse/keyboard combo, but I've tried different channels on my router: 1,6,11 ... they all have issues. My router is a D-LINK 615 and supports 801.11b-n.
I have an iPhone and it is rock solid on the wifi; plays nicely with the keyboard and mouse and doesn't miss a beat. But I REALLY want my HD2 to work: it's more baddass!
Can anyone help me out?
by not working, could you be more detailed? coz if the problem is about wifi went to sleep state after you lock the phone, then there's a settings for that.
danxtian said:
by not working, could you be more detailed? coz if the problem is about wifi went to sleep state after you lock the phone, then there's a settings for that.
Click to expand...
Click to collapse
Where's the setting?... I must have missed it! I can restart the phone and get the wifi symbol, but the reception bars aren't fully lit... only the very lowest (I'm on a sense build now).
I go into wifi settings and it says 'connected' ... but I try to load the browser, or marketplace, or Amazon AppStore ... and I'm not connected. I disable wifi then I renable it and my wifi bar is full! And the wifi works for, maybe, 30-45 seconds before it doesn't work again.
Really, really odd. And this is how it behaves on all ROMs I've tried.
*EDIT* I just saw that my wifi sleep policy is set to 'never' go to sleep.
I just turned on "best wi-fi performance" but I have my doubts that it will work... and my battery is going to suffer, big time.
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Thanks! Help installing a new kernel...
linj said:
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Click to expand...
Click to collapse
Hrmm.... I've been searching high and low for a good kernel and was thinking it might be the issue. I found g.lewarne's kernel http://forum.xda-developers.com/showthread.php?t=917590 ... but I have no idea how to apply it to my current build: http://forum.xda-developers.com/showthread.php?t=1027768
Is it possible to apply the g.lewarne kernel to CME Desire HD2?
linj said:
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Click to expand...
Click to collapse
I just flashed g.lewarne's GL_CORE_V5 from here:
http://forum.xda-developers.com/showthread.php?t=917590&highlight=reboot
... I flashed the whole ROM and I'm getting zero wifi. Even with the other kernels I was able to get some wifi, but none with this one. I like the ROM look a lot, but nothing doing on the wifi front.
Anyone else have suggestions??
WPA vs WPA2
Make sure you set ONLY WPA and TKIP in your router settings... I have much more reliable wifi because of this.
Also, choose specific wifi channel ... channel 6 works for me, and I've seen channels 1 and 11 as recommended channels as well.
Mixed WPA/WPA2 and TKIP/AES modes were horrible for wifi
FYI!
My ROMs are working relatively well now... much better than mixed modes (no wifi working)
diznanl said:
Make sure you set ONLY WPA and TKIP in your router settings... I have much more reliable wifi because of this.
Also, choose specific wifi channel ... channel 6 works for me, and I've seen channels 1 and 11 as recommended channels as well.
Mixed WPA/WPA2 and TKIP/AES modes were horrible for wifi
FYI!
My ROMs are working relatively well now... much better than mixed modes (no wifi working)
Click to expand...
Click to collapse
Ah. Unfortunately I have little control over the wifi infrastructure on campus (I'm in a college environment). That said, I'm not connected to the WPA2 Enterprise ssid but the unencrypted one.
Good to hear you found a resolution!
I have found that WiFi works just as good as my laptop when I'm running Windows Phone 7. Much faster at connecting and can connect further to the edges of signal then Android. I wonder why this is.
Hi
I've had a search in the forums but haven't seen any other posts re. this but wondered if anyone had any ideas?!
Basically I'm having problems connecting to some networks with my Tab 10.1 (stock, updated OTA to the latest TouchWiz UX last week).
I first had a problem last week when I took the device into work - there's an 802.1x EAP network there but it wouldn't even show up in the network list. My SGS2 connects to it without an issue.
Then when I got home tonight (after happily using it at my parents' house during the day) I found it wouldn't connect to my home WiFi (hidden SSID, WPA2). It had connected to this network fine in the past, but now was just sitting showing it as 'not in range' network. At first I thought it might be a router issue (it used to be a little flaky), but then I saw that my iPod and SGS2 were both connecting and working on it without a hitch.
I couldn't see the network at all in WiFi Analyzer (similarly to at work), although it was showing my neighbours' WiFi networks fine. I tried deleting the saved entry and telling the router to broadcast the SSID but it still wouldn't work.
I then put on my WiFi hotspot on my SGS2 (also a previously remembered connection) and it worked absolutely fine!
Does anyone have any ideas where to go next apart from doing a full reset? (which although not the end of the world would be quite a pain).
Thanks for any suggestions/tips!
OK, bit the bullet and restore my device to factory settings - it STILL can't see my home WiFi, despite my SGS2, laptop and iPod all connecting to it fine. It is however showing up two networks belonging to neighbours and also my SGS2 if I put it in WiFi hotspot mode!
Any suggestions folks??
Sounds like a route issue, did you reboot the router? Is the router on a channel below 12?
Hi thanks for the reply!
I actually just spotted a post at http://www.thegalaxytabforum.com/index.php?/topic/5511-my-wifi-no-longer-works/ with the same issue.
It looks like Samsung have mucked something up when they made the Touchwiz UX update - it now blocks WiFi channels 12 upwards, when the old stock Honeycomb firmware didn't do this. I'd moved my router onto 13 to reduce congestion and I guess the work one must be on 12/13 too.
I can see from the table at http://en.wikipedia.org/wiki/List_of_WLAN_channels that 12/13 are only allowed under low-power conditions in the USA, but this isn't the case elsewhere so they shouldn't have locked it down outside of the USA.
This also happend to me
pwhooftman said:
Sounds like a route issue, did you reboot the router? Is the router on a channel below 12?
Click to expand...
Click to collapse
As I had setup an additional router in my house (with assigned a high numbered -or so i thought- fixed IP address) for some reason my main router tryied unseccesfully to assign the same IP to my SGT as the router. This had obviously conflicts and could not log in.
Went into the router eliminated the fixed IP address and voilá! it got working again, all IP a dinamic!!
Regards