Database Users

Wifi sucks :(

Hi all,
I just got my device, and still thinking whether to send it back in 7 days. My main complain is the wifi. I have never seen more than 2 bars (out of 4) signal strength, even when sitting 2 meters from the router. Moreover it always drops the connection. I realized it when I tried to use IE for browsing, since that doesn't tolerate it and I keep getting the connection lost messages. Seems that Opera can live with it, but I see when the connection dropped during the page load. Youtube watcher also cannot manage to download videos when the signal is dropped.
The Tx/Rx rate also changes chaotically from 1Mb/1Mb to 54Mb/36Mb.
Before you ask: the Power Mode of wifi is set to "Best Performance", since this is the only way it is usable.
Anybody else with similar experiences?
Any solution?
I really appreciate any help, I would like to keep it!

I have no problems what-so-ever with the wifi on my D2...
It runs very well, in all applications that can use it.
- and I have full signal when I am within 5 meters of the router.
I haven't changed any settings on the device, and the router is running on WPA2-PSK at a channel not used by any of my neighbours.
Maybe you have many wireless networks in your area?

Hi,
I have more or less your problems (I opened a thead about it the day I unpacked my D2 but wasn't really condiderated). Here's my condition: I have 3 HTC devices...Artemis-->regular functioning (balanced power), TytnII-->Power Performance MUST be set to high performance, Topaz..well I could connect with balanced power but since I upgraded radio I have to keep it set to best performance, otherwise I would get "fake" connections (connection established but no data taffic). I don't really bother to have to set it like that because the connection is dam fast, which compensates the higher power consumpion.But beside this, I must say that my router is not very friendly with my D2,e.g. when I don't get a connection,I restart it and it works (this must have to do with DCHP service). I have much less trouble connecting alsewhere. So ,what to say? Try to change radio...Do you have other wireless devices working regularly in the same area?Do you have an original rom?You could also try to change wifi channel..would be happy to help

Hi,
Thank you for the answer. I have original ROM, just checked the radio, it is: 3.43.25.19. I didn't experience "fake connections" when it is connected, it is so .
I cannot change the wifi channel, the same router is used by others. However it cannot be the cause of my issues since my notebook's network works fine on the same router.
Changing the radio... seems a good idea. It is my very first smart device, I even thought that this version number was for the hardware, not the software . I will find out how to do it, maybe give it a try. Hope it is an officially supported action .

Hi Lamsebamsen,
The TD2 sees 4 wifi networks, my notebook sees 8. Is it many or not? I think the 4 which the TD doesn't see is many .

foldip said:
Hope it is an officially supported action .
Click to expand...
Click to collapse
I'm afraid not, as you would have to HardSPL your device first. There would still a way to get back to your original configuration but I don't know if you are prone to do so, that depends on how much responsability you can take on your device (is it from work or..). Another thing to try is to manually configurate your connection (e.g. assign D2 always the same IP, but watchout for network collisions!router should be set aswell)

[UPDATE]Official Nexus one Wifi issue thread(every N1 owner should read)

Sorry I know this problem probably has been brought up many times. But here I just want to make a total one and collect all the feedbacks from N1 users regarding to the wifi sleep issue with N1.
Let's just make it simple: Every N1 owner PLEASE DO test out the wifi connection when your phone goes to sleep as there are MANY people suffering from this problem all over the world. Especially the later buyers since February this year, almost every phone is potential to this problem.
######################################################
Diagnosis:
1. Set the wifi sleep setting to "never" in the wifi advanced setting menu.
2. Turn on Last.fm app(or Pandora, but Last.fm is most effective and responsive one to test it out), leave the phone on wifi and turn off the phone screen or let it goes to sleep.
3. The symptom is the app will stop streaming shortly afterwards(with Pandora stops maybe after one song, for which I suggest everyone test it for at least 15 minutes). Also most likely you will stop getting any email notification or anything requires data connection. And you might not be able to ping your phone or the ping responses VERY slow as well.
######################################################
######################################################
Background:
This problem was recorded from earliest almost 6,7 months ago and has affected both AT&T and T-Mobile versions(with reports of the same issue on other versions sold outside US). So far, it's suspected that the problem mostly likely lies in the lower level architecture of the phone(either software or hardware) because the problem still exists even after people has replaced the stock ROM with the custom ROM. Another proof is that people get problem with brand new phone and also the replacement phone. Another note is the problem has been found both before FROYO update and after. At this moment, there's no official fix(some Google employee blatantly brushed the issue away and asked N1 users to get over it, check out the link below for original conversation) for this issue except a work around thanks to wifi fixer app developer.
######################################################
This issue is often times neglected by N1 users because usually people don't use the phone on wifi all the time or they simply switch between 3g and wifi. But for people who use wifi a lot or use VOIP, it could be a real deal breaker.
So here I just hope everybody could test your phone out and see if you have this issue or not. Please report how your result turns out in this thread. Also, for further and more detailed discussion and cases, please check this out:
http://www.google.com/support/forum...52&hl=en&fid=01a47ff5b0a92d5200048be07b6cb5c1
You are more than welcome to add your experience to the discussion above so hopefully it can wake google up.
####################################################
UPDATE:
So Broadcom just released a wifi driver fix several days ago which may solve this issue. According to the record, phones with non-zero MAC address suffer from problem.
The driver has been incorporated into the latest Cyanogenmod(either RC or nightly build). People are reporting it fixes the problem while in some other cases, the problem still exists even after the fix, even for people who's MAC address starts with 00.

Last.fm works fine with the screen off here, always has done. I even turned off mobile data to be sure it's not switching over to that.
This is with the wifi set to sleep with the screen off (ie. the default setting).

i've been using wifi fixer and since i installed it, i haven't had a single wifi disconnect on my home network(it seems to be a network dependent issue as i never have issues on other networks)

Jep4444 said:
i've been using wifi fixer and since i installed it, i haven't had a single wifi disconnect on my home network(it seems to be a network dependent issue as i never have issues on other networks)
Click to expand...
Click to collapse
But you did have the problem before you installed wifi fixer, right?

Rusty! said:
Last.fm works fine with the screen off here, always has done. I even turned off mobile data to be sure it's not switching over to that.
This is with the wifi set to sleep with the screen off (ie. the default setting).
Click to expand...
Click to collapse
yeah, the point here is that many phones have the wifi sleep policy issue(doesn't work).

Indeed, however mine does, so this thread will need both sides of the argument

No problems on my Nexus One, running latest CM 6 nightly build.
I bought it couple months ago from eBay, so I'm not sure which shipment it is from.

Only issue I'm having after upgrading to Froyo is that my phone won't connect to my home network by itself when in range.
I have to go into Wifi Buddy and manually connect. This never happened on 2.1, but magically started after the FRF50 update, and never fixed itself in the next couple of builds.

Forge94 said:
Only issue I'm having after upgrading to Froyo is that my phone won't connect to my home network by itself when in range.
I have to go into Wifi Buddy and manually connect. This never happened on 2.1, but magically started after the FRF50 update, and never fixed itself in the next couple of builds.
Click to expand...
Click to collapse
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.

I have kind of the same issue at home, I recently replaced my wireless router, I never had problems connecting to the old one it would just stop broadcasting constantly but my N1 would always connect automatically. With the new router my N1 keeps saying the connection is disabled and I have to connect manually. This never happens at work, it always connect automatically so it seems to have something to do with the router settings but I have no idea what.

No problems here. Last.FM works fine for me on WiFi when screen is off. I also get notifications. Running FroYo rooted with locked bootloader
Sent from my Nexus One using XDA App

Divster said:
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.
Click to expand...
Click to collapse
i am having the same problem, when i go out of range from my wireless and then back in range, the n1 just says scanning and never re-connects.
that said, using a channel lower than 11 on my router did seem to help with the sleep issue.

hbkmog said:
But you did have the problem before you installed wifi fixer, right?
Click to expand...
Click to collapse
sorta, i never had the issue on any network besides my home one

I've also been having the disconnect problem with my N1. Maybe it would help if people whose sleep policy is actually working could post what wifi router/AP/whatever they are using. Also, if possible the first for identifiers of their MAC address. I read on one of the Google posts someone with a MAC address starting with 38:E7 having problems. The MAC for my phone is the same. For what it's worth I'm using a D-Link DIR-655 router and a Speedtouch 716 v5 WL and am experiencing the disconnect on both.

I've had the issue with 2 N1 tested on 3 different routers. I've read that it is related to the low power mode the N1 uses while sleeping not playing nice with routers. Not all N1 show the problem, apparently only the most recent ones. I've called google support and was told google knows about the issue and is working on it, but I am a bit cynical and I'll believe it when I see a fix.
Wifi-fixer fixed my problem only after I disabled Sipdroid which was interfering with it.
Mac adress: 38:E7: D8
I'll post my router model later when I get home.

Divster said:
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.
Click to expand...
Click to collapse
williec30 said:
i am having the same problem, when i go out of range from my wireless and then back in range, the n1 just says scanning and never re-connects.
that said, using a channel lower than 11 on my router did seem to help with the sleep issue.
Click to expand...
Click to collapse
as a quick update... i installed wifi-fixer and things have been much better. will report back if things start to derail again.

cabreca said:
I've also been having the disconnect problem with my N1. Maybe it would help if people whose sleep policy is actually working could post what wifi router/AP/whatever they are using. Also, if possible the first for identifiers of their MAC address. I read on one of the Google posts someone with a MAC address starting with 38:E7 having problems. The MAC for my phone is the same. For what it's worth I'm using a D-Link DIR-655 router and a Speedtouch 716 v5 WL and am experiencing the disconnect on both.
Click to expand...
Click to collapse
D-Link DIR-615 with DD-WRT v14684, phone's MAC starts 00:23

It's weird because most of the time I don't have this problem. My WiFi stays connected all night long to WiFi. But once in a while it does disconnect and switch to 3g. I think its certain routers, because I didn't have this problem for first 3 months on my old router, now it happens with my new router.
My phone never has trouble reconnecting back to WiFi. Everyday when I come home from work, as I walk up my driveway the phone has already automatically connected to WiFi. I've made sure about this one since I read this problem all over.

I bought my Nexus One directly from Google when it came out for AT&T. It certainly has the wifi issue and it is very annoying. My expectation is that the phone jump on my wifi network when in range as all of my other phones have done. Instead I have to manually engage the phone to get on wifi. SUCKS!

this is the biggest problem for me with my n1.
although the wifi does stay awake, it slows right down..
if i ping my phone, the response time increases when the phone is asleep, but doesnt time out.
if i ftp a file from my laptop to my phone, the speed drops from 1mb/sec to 100kbps/sec when the phone is asleep.
i have found the app "fix my wifi" solves the problem of waking the phone after a few hours of sleep and finding the wifi has failed. if only there was a way of getting the speed to stay the same.

[Q] How to allow incoming TCP connections (WebDroid, SSHDroid, etc.)?

Hi all,
Wondering if anyone knows how to make Android open the ports necessary for incoming connections for server apps to work without having to ping the client first under su?
Or failing that, is there a way to run a script that will ping the client IP instead of having to run the command by hand in terminal?
Thanks!

New, clearer, catchier title

This is the dev section not Q&A.

TheATHEiST said:
This is the dev section not Q&A.
Click to expand...
Click to collapse
Sorry, my bad. Mods, could someone please move my question to the appropriate venue?
LOVE your nick and avatar, dude!
Greetings from a fellow damned heathen!

i would really love to see a solution there too!
RemoteSMS over wlan would be awesome

Yom said:
Sorry, my bad. Mods, could someone please move my question to the appropriate venue?
LOVE your nick and avatar, dude!
Greetings from a fellow damned heathen!
Click to expand...
Click to collapse
.............

Any takers?
Posted from My Hacked HD2

Second that! Something's off in 99/100 ROMS, TCP doesn't seem to do anything. Only one Sense ROM by cotulla seems to work.
I disabled the adblocking hosts file to test if it had anything to do with it (e.g. SSHDroid doesn't work with it) but that didn't help anything either

Agreed, does not seem to work on any rom I've tried, only Cotulla's 'Stock Desire' Sense build seems to work (this one: http://forum.xda-developers.com/showthread.php?t=893620).
Too bad Sense's so completely dire, otherwise I'd use that. I want CyanogenMOD.

Having the same question. I am sure here must be someone who knows how to enable inbound connections....

Little update:
I noticed it is possible for me to ping and use all services when using the gateway to access everything, in my case the access point/wifi router.
So it looks like this is some kind of routing/firewall issue but I can't find anything about default blocking or firewalling on android...

Good news. I found out what is causing this on almost every build.
It has something to do with the stock wifi tethering. If you try and enable it in almost every rom it will fail, but now turn on your wifi again and everything works as it would normally do!
The build it does work on also has working stock wifi tethering, so that explains that...
For now it's good to have this workaround and I hop to have a proper fix in the future

im using RAFDROID 3.0 and i dont think i have this problem at all. I tried SwiFTP and it connected without any issues.
Try to update the busybox version mine is 1.15.2

SantanaNL said:
Good news. I found out what is causing this on almost every build.
It has something to do with the stock wifi tethering. If you try and enable it in almost every rom it will fail, but now turn on your wifi again and everything works as it would normally do!
The build it does work on also has working stock wifi tethering, so that explains that...
For now it's good to have this workaround and I hop to have a proper fix in the future
Click to expand...
Click to collapse
I tried this on Frankinstine's awesome ROM, but no cigar. There has to be a firewall rule or setting we can tweak to allow this kind of traffic...

Yom said:
I tried this on Frankinstine's awesome ROM, but no cigar. There has to be a firewall rule or setting we can tweak to allow this kind of traffic...
Click to expand...
Click to collapse
It works for me, but it's not 100% foolproof. It seems to work for a while, but not permanently. However, it's still better than the ping method. The ping method would never work for me, since I use Wifi at least 4 different places a week. Even when done automatically, how would I know what to ping on what Wifi network?! Random DHCP on workstations notwithstanding...
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
At that point it "works" for me, at least for a while.
At the very least this seems to indicate that the broken Wifi hotspot and this problem are related -- on Cotulla's build (where stock Wifi hotspot WORKS), this problem is non-existent.

Unfortunatly your steps do not work for me :-(
strikernl said:
It works for me, but it's not 100% foolproof. It seems to work for a while, but not permanently. However, it's still better than the ping method. The ping method would never work for me, since I use Wifi at least 4 different places a week. Even when done automatically, how would I know what to ping on what Wifi network?! Random DHCP on workstations notwithstanding...
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
At that point it "works" for me, at least for a while.
At the very least this seems to indicate that the broken Wifi hotspot and this problem are related -- on Cotulla's build (where stock Wifi hotspot WORKS), this problem is non-existent.
Click to expand...
Click to collapse

engst03 said:
Unfortunatly your steps do not work for me :-(
Click to expand...
Click to collapse
That's unlucky. Those steps seem to "work" for me on CleanDroid 1.30. Maybe we can just hope it works again when the stock wifi hotspot is fixed.
Alternate "solution":
Get Cotulla's "Stock Desire" ROM: http://forum.xda-developers.com/showthread.php?t=893620
It definitely works on that. Too bad sense is dog****, and your battery will last for a day max.

strikernl said:
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
Click to expand...
Click to collapse
Just tried this and it worked. As soon as I started the wifi the second time my computer started pinging HD2.
My usual procedure for fixing this was to start wifi, see assigned IP address and then ping my computer from 'Net Ping' app. This can be faster sometimes.
Is there a way to port hotspot from Cotulla's build to a nonSense build? No way for me to come back to sense again

clyder said:
Just tried this and it worked. As soon as I started the wifi the second time my computer started pinging HD2.
My usual procedure for fixing this was to start wifi, see assigned IP address and then ping my computer from 'Net Ping' app. This can be faster sometimes.
Is there a way to port hotspot from Cotulla's build to a nonSense build? No way for me to come back to sense again
Click to expand...
Click to collapse
Don't know, it's probably in the kernel, so shouldn't be too difficult, but then again, I haven't really got a clue about building ROMs.

agarp said:
im using RAFDROID 3.0 and i dont think i have this problem at all. I tried SwiFTP and it connected without any issues.
Try to update the busybox version mine is 1.15.2
Click to expand...
Click to collapse
RAFDROID is also a sense build, we want it to work on all builds, stock and CM

[ISSUE] TouchPad Android Wifi Issue Thread

This thread is intended to be a gathering point for all wifi issues on Android Touchpad ROMs.
Having a separate specific issue thread for this will serve several purposes.
Avoid wifi issues getting lost in the more general Touchpad ROM threads.
Allow issues common to wifi operation on all the different ROMs to be concentrated in one thread.
Reduce annoyance to those who are currently enjoying good wifi operation and who see repetition in the issues being aired.
Make it easier to report tests and experience on different set ups and as new drivers / ROM integrations appear.
Make it easier for users with questions to see if it has been asked before.
Background
Wifi operation on Android Touchpads currently is a hit and miss affair. Some users report flawless operation regardless of access point. Others can get stable operation with careful set up and / or choice of access point but problematic operation on access points over which they have no control. Others still fail to get conditions right for any form of stable operation.
This is in comparison with WebOS based operation where the problems seem to be much fewer. Probably most of the explanation for this difference is the current lack of suitable drivers integrated into the ROM environment. Hopefully this will be fixed at some point and there are some encouraging signs already that improvements are possible.
Factors affecting operation
There are several factors which could potentially affect the wifi performance with Android Touchpads including the type of Access point, the set up of the Access point, the local signal strength and interference conditions, variations in Touchpad hardware build, and how the ROM software has been installed and set up. A key factor on top of all these is the wifi drivers used and how they are integrated.
General advice
Until the fundamental performance is improved the end user of the Touchpad can do some things to help get better performance particularly if they have control over the Access point. Typically this will be in the home situation. Possibilities for adjusting setting for work or public access points tend to be small or non-existent.
Note that not all suggestions work for everybody affected so you have to be prepared to experiment a little to see what may work for you.
The primary suggestions I offer that worked for me in my home situation is to lower the channel setting on the router to Channel 1 even though for me that was worse from a local interference point of view. Other suggestions include avoiding dual band operation and experimenting with security settings (like using WPA instead of WPA2).
Posting
Please post to this thread if
You want to ask Android Touchpad wifi specific questions including problems you are encountering
You can answer Android Touchpad wifi specific questions posted here
You have reports on specific problems that may help resolve wifi issues
You have suggestions on how to improve operation in the short term with existing drivers
You have reports on new driver operation either better or worse.
Please also include the ROM and version used in any specific reports. Although wifi issues have been present on 2.3( e.g CM7) and 4.0 (ICS) the focus for development is now firmly on ICS and that is where improvements are likely to be made.
It is unhelpful at this stage just to post here that you do not have any wifi problems unless you have some specific advice on how that can be generally applied. We already know there are many who enjoy good wifi performance.
Currently I am using CherryKANG 0.2a which does have some experimental new drivers in and for me gives much better performance.

I'm on cm9 alpha 0.6 with stock kernel @1.5 installed with clockworkmod 5.x with a webOS 3.0.5 dual boot. My home router is open (but I use MAC Address blocking to keep the creeps out). My wifi is about 80% on point but will go out about every 24 hours and I have to forget the network, wifi off, power down. Power back up, wifi back on re connect and good for another 24 hours. I noticed if my device "reboots" instead of turning all the way off my wifi WILL NOT connect. How are people doing on cherrykang? Any better?

rochford77 said:
I'm on cm9 alpha 0.6 with stock kernel @1.5 installed with clockworkmod 5.x with a webOS 3.0.5 dual boot. My home router is open (but I use MAC Address blocking to keep the creeps out). My wifi is about 80% on point but will go out about every 24 hours and I have to forget the network, wifi off, power down. Power back up, wifi back on re connect and good for another 24 hours. I noticed if my device "reboots" instead of turning all the way off my wifi WILL NOT connect. How are people doing on cherrykang? Any better?
Click to expand...
Click to collapse
My experience so far with 0.2a of Cherry has been 60 hours of operation without a wifi issue. This includes about 6 hours on a work network where before the wifi fix in Cherry about the only way I could gt a connection was by moving very close to the access point and it would drop out within 5 minutes of moving away. During that 6 hours with Cherry it found the connection straight away, maintained it all the time and even reconnected automatically when I tried a reboot. I'll report further on this when I have had more time on the work network this week.

lafester said:
Nice post but wrong forum
(@ op)
Click to expand...
Click to collapse
Which forum are you suggesting this should be in?
I know this is development but this thread was an attempt to pull out all the wifi related questions which are already being posted in the various development threads here. I thought that development was more appropriate as the main intention is to help and encourage the development of wifi to the point where the need for wifi support becomes much less.

Clearing /data/misc/wifi and rebooting makes my touchpad connect to the router without any hesitation, I guess it is similar to forgetting and rebooting(but haven't tried that)
ROM: 0.2a Kang

ClassicNerd 0.0.4
My home network is a Netgear N600 dual band router with WPA2 security as well as a guest SSID. i connect to the 5G band with no issues with the exception of when I have to reboot. On rebooting if I connect to an access point I have to keep the screen alive for around 10 minutes. After that everything is fine, otherwise the system reboots when the screen goes off.
My work network is an overlapping pervasive network using PEAP authentication. On reboot if I do not shut down with WiFi off my settings get into a state where it refuses to connect, or even try. Forgetting the network and then entering the information again fixes the issue. I also get the sleep reboot if I don't leave the tablet on for a bit of time problem here.
I never have any disconnects that are tablet related on ether network.

Kang 0.4.8a truly rocks and addresses wifi as I can now connect even when channel is 11!
Sent from my cm_tenderloin using xda premium

guho said:
Kang 0.4.8a truly rocks and addresses wifi as I can now connect even when channel is 11!
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for that. I had been holding off switching to 0.4 based on the kernel issue comments but it looks like 0.4.8a is good to go so I'll try that.
I note with sympathy the response you got from your comment in the other thread. Some guys can get very territorial even though all these ROMS are largely based on same open source and rely heavily on the work of some central devs .

Here is my feedback from 1st full day using CherryKang 0.4.8a in my work environment.
Bottom line is that the wifi fix is giving me a big improvement over previous builds but I don't think is totally problem free.
At the start of the day it found and connected automatically.
Over a 10 hour period it dropped the connection twice after staying connected about 4 hours each time. It didn't reconnect automatically after a drop but required the wifi control to be turned off and then on again to perform the reconnect which it did very rapidly.
This is still a dramatic improvement over before where I struggled to get a connection at all and it would always drop in less than 5 minutes.
To get a better handle on comparative performance I plan to run it under WebOS tomorrow just to get a baseline on how the native tablet performs under the local conditions. I had previously tried out WebOS here and it was stable over the hour or two I had it on but I've never tried it for a full day.
Having said that I also have an ICS Nook Color here which is absolutely rock solid on this access point and has never dropped the connection over several weeks of use so I know its not a fundamental access point issue.

bobtidey said:
I'm fairly neutral about whether this is better in general or development. My original thinking that it was Android based discussion rather than general chit chat, that the end goal was the 'development' of improved wifi operation, and that it might be better local to much of the ROM discussions where wifi can be a trigger issue..
Click to expand...
Click to collapse
I was always told that the dev section is for software that you create - ROMs, kernels, tweaks, etc. It's usually something that you need to flash on your device that affects performance or functionality in some way (themes and visual mods are not included however).
Any sort of "Discussion" or any troubleshooting is usually in General or Q&A, since it can usually span across different roms, and/or software settings. No offence to you, as it is sometimes confusing to people exactly what belongs in the dev section. Usually, if it's not something you are flashing on the device, it goes in another section.
That said, I'm running ClassicNerd Butta v1, and have no issues connecting to my 2.4ghz channel on my router, but it won't connect to the 5ghz channel for some reason.
I have a netgear wndr3700 N600 router with dd-wrt firmware flashed on it.
Edit: changed "wireless networking mode" on the 5g channel from "N only" to "Mixed", and I'm now able to connect.

Since I just had some pretty bad Wi-Fi issues, I guess I should share what I found and how I fixed it.
I've been using my TouchPad very reliably on my home and work networks. I don't know what channel either are on, but at home I'm pretty sure I've been on an 802.11n access point (5 GHz channel). The router at home is a Netgear WNDR3700 v.1, but after problems with the firmware dropping countless other devices, I installed the dd-wrt firmware and configured it to only be an access point, and I'm relying on another router upstream to provide my DHCP and private network. This configuration has been rock solid for a couple months now, and I've never had to reset the access point since! After I installed CM9 alpha 0.6, I've had maybe 3 or 4 times where I've lost network connectivity on my TouchPad, but other devices continued to work; clearly a problem with the TouchPad in those cases since simply rebooting the TouchPad restores connectivity. I do not stop Wi-Fi before rebooting. This is a reliability I can live with since outages have been quite infrequent and easily fixed.
Currently I'm traveling, and I needed to setup a temporary wireless network. To do so, I used Connectify on an older Windows 7 laptop, and I'm using the Wi-Fi board built into the laptop to share the wired connection I've plugged into it. The wireless board is a Broadcom 802.11g with a BCM43XX chip set. When using Connectify, the wireless board runs on channel 11, with no way to configure it that I can find.
After ~48 hours uptime, I tried to use my TouchPad today and found Wi-Fi was not working. Using "Wifi Analyzer" from the market, I observed the TouchPad could "see" a few different access points, but it was unable to connect to any of them, while I was still able to measure things such as signal strength. Forgetting the network connection and reentering the WPA2 key did not work. Connectify showed that my Nexus S running Android 4.0.3 was still connected, but my TouchPad was "Disconnected." Rebooting the device did not restore Wi-Fi. Shuting down my laptop and rebooting did not restore Wi-Fi, although I observed my Nexus S reconnecting. I then rebooted the TouchPad into WebOS, where I could connect again, but booting back into CM9, I could not reconnect. I then turned Wi-Fi off, and rebooted. After turning Wi-Fi back on, I could see the access points again, but still couldn't connect.
What seemed to finally unstick things was turning Wi-Fi off, setting Airplane Mode on, turning Wi-Fi back on, and when I observed that turning Wi-Fi on was not automatically turning Airplane Mode off, I manually toggled it myself. Almost immediately, Wi-Fi connected.
I believe in my case, toggling Airplane Mode in the future may be a simple fix, but I only have the one data point to go by so far.
Sent from my cm_tenderloin using XDA App

For the most part my wifi works pretty good, but I have problems with my touchpad wifi at work. The wifi connects for a few moments then simply loses connectivity. The setup at work is a system of enterprise access points all using the same ssid, and for whatever reason it throws the touchpad (and some other android devices) for a loop. My android phone used to have issues too, but it was fixed with a custom rom, and webos connects fine also.
I have tried almost every rom with mixed results. The "Bricked"rom v4 gave the best experience. CM9 A6 was ok.. Next I tried classic nerd buttah 0.1.0 v1 and v2. I found it wasn't really any better than other roms out there, and had some pretty annoying glitches. I read though all of the classic nerd posts looking for answers, I found their thread to be hostile, so I didn't bother posting any questions. I promptly uninstalled, and moved on to CherryKang with the hopes that the wifi driver fix would work out. It didn't seem to do anything, but I have to say that CherryKang runs pretty good, hasn't given me any problems, and I like the 132 dpi. Every install was preceded with full wipe.
So I started tinkering with the build.prop and wpa_supplicant.conf
My hope is that something in there can be tweaked and solve my issue.
After doing some research I found a few settings that have helped other people:
-Changing hostname to a shorter hostname. The default touchpad hostname = android-78abb09201c4bca8. Edited the build.prop and added net.hostname=touchpad
found here: http://ergh.org/cmtp/-
*didn't work for me but may work for you
-Setting scan_ssid=1 in wpa_supplicant.conf
Oddly made the disconnects less frequent. Still testing
-Disabling WMM support. WMM causes havoc with some routers and devices, shutting it off sometimes clears things up.
*haven't tried it yet but I will post something when I try it tomorrow.
Other than that, I'm not sure what to try next. Any ideas?

Cubicsilver said:
For the most part my wifi works pretty good, but I have problems with my touchpad wifi at work. The wifi connects for a few moments then simply loses connectivity. The setup at work is a system of enterprise access points all using the same ssid, and for whatever reason it throws the touchpad (and some other android devices) for a loop. My android phone used to have issues too, but it was fixed with a custom rom, and webos connects fine also.
I have tried almost every rom with mixed results. The "Bricked"rom v4 gave the best experience. CM9 A6 was ok.. Next I tried classic nerd buttah 0.1.0 v1 and v2. I found it wasn't really any better than other roms out there, and had some pretty annoying glitches. I read though all of the classic nerd posts looking for answers, I found their thread to be hostile, so I didn't bother posting any questions. I promptly uninstalled, and moved on to CherryKang with the hopes that the wifi driver fix would work out. It didn't seem to do anything, but I have to say that CherryKang runs pretty good, hasn't given me any problems, and I like the 132 dpi. Every install was preceded with full wipe.
So I started tinkering with the build.prop and wpa_supplicant.conf
My hope is that something in there can be tweaked and solve my issue.
After doing some research I found a few settings that have helped other people:
-Changing hostname to a shorter hostname. The default touchpad hostname = android-78abb09201c4bca8. Edited the build.prop and added net.hostname=touchpad
found here: http://ergh.org/cmtp/-
*didn't work for me but may work for you
-Setting scan_ssid=1 in wpa_supplicant.conf
Oddly made the disconnects less frequent. Still testing
-Disabling WMM support. WMM causes havoc with some routers and devices, shutting it off sometimes clears things up.
*haven't tried it yet but I will post something when I try it tomorrow.
Other than that, I'm not sure what to try next. Any ideas?
Click to expand...
Click to collapse
Your experience I think is very similar to mine. I could get home wifi access OK by adjusting router, but work access was a complete nightmare with none of the ROMs being perfect. Most were very difficult to connect and would disconnect after a few minutes making them unusable.
I find CherryKang is much better and typically lasts about 3 hours for me. I did also try all the wpa_supplicant tricks like you say, short hostnames etc but I can't get it perfect at the moment. What is interesting is that if I turn wifi off and on to get it to reconnect then it either obtains ip straightaway or there is a delay of about 30 secs and then just says saved and isn't connected and won't recover from that. It is about 50/50 which happens and I suspect something similar is happening with a rescan to cause the drop out after it has been functioning. The work SSID is also not published and I wonder whether that can have an effect.
I tried out WebOS at work again to get a benchmark, and got 8 hours with no drop outs so the hardware and access point can function OK.
I am a little puzzled by the nature of the wifi fix in Cherry Kang so plan to post a message in there and I notice some other wifi drivers for a similar device seem to be surfacing. So I'm optimistic that this issue will be finally sorted out soon.

Bobtidey,
I also have done some in depth research regarding the wifi issues and the patches some are compiling into their kernel or as the other post in the CherryKang thread suggested manually inserting and removing the new/old modules. I definitely am noticing an increase in performance when I tried the rom, wifi was stable but for me I just got lucky and have not really had problems besides the random disconnects and what I thought was hanging turning it on. Anyway let me quote from the commit of which both these fixes originate from "Patch Set 1: I would prefer that you didn't submit this This needs stress test before it can be committed (dalingrin)." "Patch Set 1: I'm wondering if you get any firmware crashes using the new ath6kl module (check dmesg - it was the main reason why activating Wi-Fi sometimes takes very long). That's the main reason that I withheld this patch for now." So that prompted me to be a little skeptical on using this as obviously I would consider dalingrin's advice over all. There's some more to it than this as there is also a timing issue that causes crashing :
"This is not quite ready. It is the most promising driver for us going forward. However, none of the android specific functions are implemented yet. There also a crash related to timing issues though I think I can fix that. I will upload another patch set when I get a chance."
Anyway just thought I'd chime in on the subject especially after the last comment which in my opinion is rather unsettling
Links/sources from quotes and for a nice look at the material.
Expand al if you want to view the comment exchange,
http://review.cyanogenmod.com/#change,12342
http://review.cyanogenmod.com/#change,12341
Thanks,
Sent from my cm_tenderloin using Tapatalk

Classicnerd Butta v2 vs v2.1
Add'l infoI have been running the succession of Classicnerd team builds including the predecessor Xron series. I had no problem in either WebOS or in any build until Classicnerd-Butta-0.1.0-v2. Then I had several instances of connection failure after waking.
I also noticed that the signal strength was shown as dismal even right next to the router. I'm thinking that some of the problem may be the radio not waking up when the tablet does. I was able to connect by tapping the SSID listing on the TP. Then the signal strength returned to normal.
I updated to v2.1-Odex yesterday and haven't experienced any more connection failures.
All of my flashes have been done with factory reset and wiping everything on clockworkmod, reinstalling Gapps and reinstalling apps. I have not restored any backups or backup data.
Update: I have now experienced a couple of instances where the wi-fi is not connected and doesn't automatically reconnect after the TP has been sleeping. Simply turning off and turning on the wi-fi has fixed it.

Just an update on the issue I was having with my 5g network. I changed the "wireless networking mode" on my router from "N only" to "mixed" and am now able to connect.

Nizda1 said:
Bobtidey,
Links/sources from quotes and for a nice look at the material.
Expand al if you want to view the comment exchange,
http://review.cyanogenmod.com/#change,12342
http://review.cyanogenmod.com/#change,12341
Thanks,
Sent from my cm_tenderloin using Tapatalk
Click to expand...
Click to collapse
I had looked at those before, but I think they may have changed a little now and clarified things. If my current understanding is correct then Cherry Kang has the new board file referenced in the 12342 and gets some wifi benefits but this is a temporary measure. 12341 then refers to fundamentally replacing the drivers when more work has been done on them, hopefully leading to even better long term wifi support.

bobtidey said:
Which forum are you suggesting this should be in?
I know this is development but this thread was an attempt to pull out all the wifi related questions which are already being posted in the various development threads here. I thought that development was more appropriate as the main intention is to help and encourage the development of wifi to the point where the need for wifi support becomes much less.
Click to expand...
Click to collapse
WiFi has been beat to death in almost every thread in the development section, I encourage this thread and hope it can decrease the the clutter in the ROM threads.
mike-y said:
I was always told that the dev section is for software that you create - ROMs, kernels, tweaks, etc...
Click to expand...
Click to collapse
I have said this many times, and this is very true in most instances...however in this case I feel differently.
krook6023 (mod team)
Sent from my HTC_Amaze_4G using xda premium

This morning at work my wifi was dropping out more frequently than recently even using Cherry Kang build; it was lasting about 15-30 minutes.
It seems to be correlated with the probability of it connecting properly when wifi is toggled off and on. When it works it immediately says getting IP address. When it fails it delays and then just says saved. This morning this was happening 50% of the time and I had to toggle it off and on again a few times to get it to connect.
I suspect it is also something to do with re-activating the device from screen off even though I have wifi set to the default of never sleep.
So in the afternoon I left it on WiFi Analyser app with the setting to prevent the screen turning off. It stayed connected for 5 straight hours leading more credence to a theory that is somehow a re-connection on screen waking up that could be part of the issue.

Has there Ben any fix for the wifi issue? I'm almost ready to ditch Android on the tp and get a real tablet.

WiFi disconnects often?

I'm really happy with the phone so far, but my wifi disconnects fairly regularly and I keep getting a force close on the SMCC Process (whatever that is). Anyone else having problems?

I just read the thread below this and that issue seems similar.
EDIT: I tried turning off the smart wifi, but it still loses connection. The phone still shows that it's connected to whatever wifi signal, but stops downloading. This happens both at home and at work, so I don't believe it's related to the router itself.

I'm seeing the same issue on mine as well. Noticed it last night playing Pandora via wifi. Would play like 3 songs then nothing. I would have to toggle wifi on/off to get Pandora playing again.

jfugate15 said:
I'm seeing the same issue on mine as well. Noticed it last night playing Pandora via wifi. Would play like 3 songs then nothing. I would have to toggle wifi on/off to get Pandora playing again.
Click to expand...
Click to collapse
Sounds like basically the same thing. If I wait long enough, it comes back on its own, but it's faster to just cycle wifi or airplane mode once. It's fairly frustrating, and I even found myself just using 3G to do things last night instead of Wifi.

seems to be a known issue in other S4 forums:
http://forum.xda-developers.com/showthread.php?t=2254568&page=2

Mixed Mode WIFI
I had this exact same problem with my EVO 4G LTE, the problem was the mixed mode WIFI. (B,G,N). On the EVO it turned out to be an easy fix because there was a setting in the WIFI menu to force either B or G. As soon as I selected one mode I had a solid internet connection. The problem here is there does not seem to be an option in the S4 settings to allow this. I have been trying to force single mode on my router to see if that will fix it but my router will not allow me to turn it off either. Pretty serious bug I would say.

WIFI worthless on brand new S4
If you are having issues with this you might want to check this thread out!!
http://forum.xda-developers.com/showthread.php?t=2253471&page=3

it doesn't do it as often as it did with the SGS3 though

I really wish I could find a resolution to this. I'm thinking of wiping my phone and starting over to make sure it isn't an app issue, but man that's a lot of work.

Im having the same issue as well.. Im almost positive its common issue and i would expect it to be addressed in the next OTA

The common link seems to be DLink router. We have a Cisco Linksys router and it stays hooked up solid on that.

I have an Asus router. Don't know if there are usually problems with those or not, but I haven't had any prior issues.

I have a Cisco e4200 stock and a Asus running ddwrt operating as a wireless bridge to extend my network. I had to turn off mixed mode on both devices to resolve the issue. Hope that helps.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

I have the same problem but I have Netgear routers. The one at my house works fine, but at my other location. The wifi drops.

Same problem on dlink

Adding my 2 cents because I have 2 S4's that I've been testing with and I'm getting mixed results... my first post here so I hope I'm doing this right!
I have 2 wireless routers at home:
- DLink DIR-655
- One provided by my ISP (Bell Canada; not sure of the model at the moment)
The DIR-655 is troublesome for BOTH S4 devices; they stay connected for a few minutes (or longer in some cases) but will always end up not transferring data even though they show as having a very strong signal. Turning wifi on/off always fixes the issue for a short period of time.
Knowing that there seem to be compatibility issues with the S4 and DLink router, I switched them both over to the Bell router. Now only one of the devices has the wifi issue described above.
I found it odd that changing the router being used fixed the issue for one of the devices but not the other. I'm now questioning whether one device has a hardware issue or not (doubtful on this, but worth questioning).
Both S4's have the most up-to-date firmware as do all of the routers in the house. No other devices (iPhones, laptops, apple tv, etc...) have any issues with the wifi.
I've tried resetting the routers, forgetting the wifi connection and setting it back up, rebooting the phone, smashing my head against the wall; nothing seems to have worked permanently.
Is it possible that this is a hardware issue and not a software issue? Has anyone else had similar results with multiple devices?

fix....?
this wifi drops are due to the router WIFI signal setting. it will drop it you are using a B/G Mixed signal/ B/G/N Mixed signal. i recommend setting it on 802.11 g. or, if all your Devices in the house have N use N since it has more bandwidth. i use G because of the PS3
Hope this helps resolve the issue for you guys, it sure did for me.

Yurijoejoe said:
this wifi drops are due to the router WIFI signal setting. it will drop it you are using a B/G Mixed signal/ B/G/N Mixed signal. i recommend setting it on 802.11 g. or, if all your Devices in the house have N use N since it has more bandwidth. i use G because of the PS3
Hope this helps resolve the issue for you guys, it sure did for me.
Click to expand...
Click to collapse
Thanks for the suggestion, I can attest that this wasn't a permanent solution for me. After switching to N mode only, the amount of times the issue occurred was reduced, but still happens at least once per day.
It's also a pain when I'm connected to networks where I have no control over the wireless settings (work, public networks, friends networks).

I have a linksys modem and router. Haven't had a single connection issue with this phone as I had with my EVO. As my wifi disconnects and reconnects right away. Lol. First time that has happened. Knocked on wood.
Sent from my SPH-L720 using xda app-developers app

I find it disconnects much less often than the sgs3, but still occasionally disconnects
Sent from my SPH-L720 using xda app-developers app