Database Users

WiFi randomly fails to connect after last update

I've had my Transformer for about 2 months now and my WiFi connection has always been reliable and robust, but ever since the last OTA update (8.4.4.11) it's gone flakey. I know the problem is not my wireless router since WiFi was working great before the update and I have lots of other devices that connect without any issues.
At least once or twice a day after resuming from standby, the WiFi icon stays dark and no amount of trying to reconnect will get it back. After a few tries, I can actually watch the checkbox for WiFi settings toggle on and off repeatedly by itself.
I've tried changing the WiFi disconnect policies, closing down apps, and stopping non-critical processes but the only thing that fixes the issue is to power down and restart. WiFi will then work for awhile but eventually goes out again.
Anyone else seeing this?

I have the same problem
Sent from my PC36100 using XDA Premium App

same thing here =/

same here and i'm getting piss off at the fact that new updates is screwing over my wifi connection.

FWIW - it's also discussed in these 2 threads and is worked around by giving your TF a static IP. Not ideal, I know, but at least it will get y'all working.
http://forum.xda-developers.com/showthread.php?t=1041502
http://forum.xda-developers.com/showthread.php?t=1190896

there has been issues with other tabs and OTA upgrades with WIFI. Try brouse in the A500 forums. There was a file to delete that fixed the issue. Must have root access.

41 UOTE=cvfl;16258699]FWIW - it's also discussed in these 2 threads and is worked around by giving your TF a static IP. Not ideal, I know, but at least it will get y'all working.
http://forum.xda-developers.com/showthread.php?t=1041502
http://forum.xda-developers.com/showthread.php?t=1190896[/QUOTE]
That's kewl and all but what if you connect to different AP's during the day. I access through my EVO 4G while at work and then access my home network when I get home. This may or may not work. I'll have to see when I get my TF on Thursday. Thanks for the quick links though.

You can also increase the dhcp lease time in your wireless router, it also works for me.

AcIdC0R3 said:
... but what if you connect to different AP's during the day.
Click to expand...
Click to collapse
Download WiFi Analyser, which will show you, which IP data you need for static configuration.

cvfl said:
FWIW - it's also discussed in these 2 threads and is worked around by giving your TF a static IP. Not ideal, I know, but at least it will get y'all working.
http://forum.xda-developers.com/showthread.php?t=1041502
http://forum.xda-developers.com/showthread.php?t=1190896
Click to expand...
Click to collapse
Not exactly the same issue and I already set up static IPs for all the devices (32 of 'em!) on my wireless network long ago.
I did find that one particular app was probably the cause (PCFile Sync) and since replaced it with another having similar functionality, but I still very occasionally lose WiFi and have to reboot.

Tigrev said:
Not exactly the same issue and I already set up static IPs for all the devices (32 of 'em!) on my wireless network long ago.
I did find that one particular app was probably the cause (PCFile Sync) and since replaced it with another having similar functionality, but I still very occasionally lose WiFi and have to reboot.
Click to expand...
Click to collapse
I've been following this issue since I started having it on the 3.1 update when I unboxed the thing, so I'd really like to understand what issue you found with PCFile Sync, or at least what led you down that road.
Up to this point because of my specific goings on I've been thinking it was more a DHCP/routing issue and not in fact a WiFi/connection issue - i have strong connection before and after whatever the event that shuts things down is, just no traffic.
A little more info here as well - http://forum.xda-developers.com/showthread.php?t=1191792

cvfl said:
I've been following this issue since I started having it on the 3.1 update when I unboxed the thing, so I'd really like to understand what issue you found with PCFile Sync, or at least what led you down that road.
Up to this point because of my specific goings on I've been thinking it was more a DHCP/routing issue and not in fact a WiFi/connection issue - i have strong connection before and after whatever the event that shuts things down is, just no traffic.
A little more info here as well - http://forum.xda-developers.com/showthread.php?t=1191792
Click to expand...
Click to collapse
The behavior I described in my initial post (watching WiFi toggle on and off in settings) seemed to suggest something was blocking or interfering with the normal connection after resuming from standby (I have my WiFi disconnect policy set to turn off WiFi when the display is off).
So I just started closing down apps that had WiFi access and when I killed PCFile Sync (which I use to sync files between the TF and an NAS), the problem went away. I'm now using FolderSync Lite which doesn't seem to cause any issues, although on rare occasions WiFi will still loop for awhile before connecting.
This never happened in HC 3.1 so I think it's a vulnerability in 3.2 under certain conditions ... and those not using a static IP on their LAN are probably seeing something similar happen.

You know, after using my TF after the update, I think what this wifi bug is really just a fix gone wrong. Maybe it's some condition set to turn on wifi only when in use (to save battery life, or allow certain tablets that won't go into deep sleep to go into deep sleep or something like that) but it's set with some super sensitive conditions that make it turn off unless there is an actual request for internet?
My bar goes from blue to grey/white after a minute or something, but I can seem to always access some webpage when I click it from an app. Hmm.

Tigrev said:
... something was blocking or interfering with the normal connection after resuming from standby (I have my WiFi disconnect policy set to turn off WiFi when the display is off).
Click to expand...
Click to collapse
This happens to me with 3.1 randomly, though my policy is set to keep WiFi alive and I never used this PCSync app.
In my opinion the Android Broadcom WiFi card driver is buggy, because the SGS2 with android 2.3.3 has similar problems and also a Broadcom card.
So I guess it has nothing to do with the Android version, but is a buggy WiFi driver. I remember, that I had similar problems with an Intel card in a Toshiba notebook years ago and it was fixed with a driver update.
The question is, who develops the drivers, Google's Android team or Asus & Co? I guess the later? If it are the manufacturers, I find it strange, that Samsung has similar issues.

+ 1 on this very frustrating bug; since upgrade to 3.2 it happens every now and then ; as I did not install any new Apps I assume that this is just a very annoying 3.2 bug...
Anybody with any solution plz?

bmszabo said:
Anybody with any solution plz?
Click to expand...
Click to collapse
A german TF owner reported in a german Android forum, that he phoned Asus support about all well known 3.2 issues and they told him, that a firmware fix will be released by OTA next week.
Knock on wood that this is true.
So far ... static IP.

Aymara said:
This happens to me with 3.1 randomly, though my policy is set to keep WiFi alive and I never used this PCSync app.
Click to expand...
Click to collapse
Me too, before I static IP'd the TF.
Aymara said:
In my opinion the Android Broadcom WiFi card driver is buggy, because the SGS2 with android 2.3.3 has similar problems and also a Broadcom card.
So I guess it has nothing to do with the Android version, but is a buggy WiFi driver. I remember, that I had similar problems with an Intel card in a Toshiba notebook years ago and it was fixed with a driver update.
The question is, who develops the drivers, Google's Android team or Asus & Co? I guess the later? If it are the manufacturers, I find it strange, that Samsung has similar issues.
Click to expand...
Click to collapse
I have had several other problems with Broadcom WiFi drivers, so this doesn't shock me at all.

cvfl said:
Me too, before I static IP'd the TF.
Click to expand...
Click to collapse
I always use static IPs.
I have had several other problems with Broadcom WiFi drivers, so this doesn't shock me at all.
Click to expand...
Click to collapse
I feared, that someone would say this

[Solved] Iconia looses WiFi after upgrade to 3.2

Hi All,
I am not in the habit of creating new threads. But after searching and reading a lot of other posts I concluded I had to create one.
After upgrading to 3.2 my WiFi connection is lost after a few minutes. I have reset my router after the upgrade but that did not help.
This is what happens: I "cold- boot" my Iconia and after a few tries it finds my Router and establishes a connection. After a few minutes though, the connection gets "lost". It happens to me when I leave my Iconia on. If I leave the Iconia on it tells me after a few minutes that there is no Internet connection. It keeps searching, connecting and disconnecting untill I power of the Iconia. After restart the same occurs after a few minutes. If I shut down the Iconia and start it again, the same thing happens (after a few minutes).
I am using a TP-Link router WR1043ND with firmware 3.13.4 Build 110429 Rel.36959n
Anyone have similar issues? Is there any way to fix this apart from contacting Acer or downgrading to 3.1?
BTW My Iconia has build number Acer_A500_7.006.01_com_Gen1 and has not been rooted or otherwise altered.
Any help greatly appreciated....
Greetz,
S.J. Onnie

S.J.Onnie said:
Hi All,
I am not in the habit of creating new threads. But after searching and reading a lot of other posts I concluded I had to create one.
After upgrading to 3.2 my WiFi connection is lost after a few minutes. I have reset my router after the upgrade but that did not help.
This is what happens: I "cold- boot" my Iconia and after a few tries it finds my Router and establishes a connection. After a few minutes though, the connection gets "lost". It happens to me when I leave my Iconia on. If I leave the Iconia on it tells me after a few minutes that there is no Internet connection. It keeps searching, connecting and disconnecting untill I power of the Iconia. After restart the same occurs after a few minutes. If I shut down the Iconia and start it again, the same thing happens (after a few minutes).
I am using a TP-Link router WR1043ND with firmware 3.13.4 Build 110429 Rel.36959n
Anyone have similar issues? Is there any way to fix this apart from contacting Acer or downgrading to 3.1?
BTW My Iconia has build number Acer_A500_7.006.01_com_Gen1 and has not been rooted or otherwise altered.
Any help greatly appreciated....
Greetz,
S.J. Onnie
Click to expand...
Click to collapse
Ton's of post about this. just google wifi drop out.
Some have fixed by changing in the router the lease time from forever to maybe a week or day. And that may not be your issue but worth a shot. Some have also fixed by using static ip for the tab. Their are others.

Hi Shaun298,
Will give your suggestion a try. Will let you know! Tx!!
Greetz,
S.J. Onnie

S.J.Onnie said:
Hi Shaun298,
Will give your suggestion a try. Will let you know! Tx!!
Greetz,
S.J. Onnie
Click to expand...
Click to collapse
There's a fix if you were rooted but since your not this post doesn't help you ha sorry.
Sent from my PG86100 using Tapatalk

Neither of the tip's require root, one change is in the router, and the other on the tab, root or no root.

shaun298 said:
Neither of the tip's require root, one change is in the router, and the other on the tab, root or no root.
Click to expand...
Click to collapse
The fix im referring to is applying a smali patch which i think requires root. Changing the router isnt always possible if its not your router and you dont have the user name and password and i dont know how well switching from dhcp to static works but the couple times i tried i still experienced dropouts
Sent from my A500 using Tapatalk

Did not think about campus routers and such. I had the wifi drop out with several roms. With security on the router open, I did not get the drop outs, but who wants to run like that. My fix was back to stock 3.1.

Hi All,
Thanks for your support and your suggestions.
Found a solution that seems to work over here: http://www.transformerforums.com/fo...neycomb-3-2-update-problems-tf.html#post34828 (Thanks, Shaun298)
Not sure how long WiFi stays on but I am hoping it sticks.
Weirdest thing: I did not even know you could reboot the Iconia like that :-S
Greetz,
S.J. Onnie

still not working
After I upgraded my A500 to Taboonay 2.2 (which is GEN_1 of Android 3.2) I started experiencing this issue.
Wifi connection keeps dropping every other 5-10 minutes. After reading this thread I was unpatient to figure out if the proposed solution works for me.
Unfortunately wifi still keeps dropping after I booted with power button adn "-" volume bottom pressed and then rebooted.
I also tried deleting the existing connection manually after that and repeated the same procedure. Even after that when I added wifi network from the scratch it still keeps dropping like it was previously

[Q] Help! My acer A500 no longer accesses the Internet

Guys a week ago I bought my acer a500 Iconia yesterday I updated it to version 3.1, it was fast hands, much improved, I turned on my wifi connected it more often when I was browsing it does not access the Internet more and more strange I I can even access my router. Then I saw in that topic if you give it a reset back 2x the wifi to work properly. The more I did it and did not work, so I found the website of acer patch to fix the problem, I used more problem remained, so I downloaded another update.zip to update it to version 3.2, more el is still with the same problem does anyone know how to solve this?

First thing I'd do is try a hard reset the device..see where that takes you. Have you tried other routers, or tried connecting a different device to your router (to make sure it's not a router issue...)? If not, try restarting your router and modem first.
I take it you're running stock/not rooted?

I use the stock 3.2 ROM, I think the problem is the router, I used a program to use my laptop as a router and it worked, but not yet tested on a real router, but I think it's IP.

had this to
I had this when I bought my tablet (back when it had 3.1).
as fast as I got home and tried it the first time all networks around me could be found except for the one in our house.
I did a factory-reset on the tablet but it didn't work.
then i did a factory-reset on my router (since I lost the admin password). this seemed to work and after reïnstalling the ISP's things it functioned completely again.
I would suggest you change the channel of your wifi, the protection and retype the SSID.
also clear the logs and the firewall blocks.
If you retried connecting with these instructions leave a message here with your results

i try make what you says, but dont workink , my probleme is my router...
thanks!

[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.

[Q] wifi issues - will not hold connection

after the latest updates from asus my transformer will not hold a wifi connection for more than 2 seconds - it keeps trying to obtain an ip address but will never stay connected. i just tried a hard reset and the problem still persists. i can't believe i'm the only one having these issues, but i don't see a specific thread here that talks about it.
is there any way to load a new ICS update or a different rom, given that i cannot connect to wifi?
any help would be greatly appreciated - thank you!

harryzwd said:
after the latest updates from asus my transformer will not hold a wifi connection for more than 2 seconds - it keeps trying to obtain an ip address but will never stay connected. i just tried a hard reset and the problem still persists. i can't believe i'm the only one having these issues, but i don't see a specific thread here that talks about it.
is there any way to load a new ICS update or a different rom, given that i cannot connect to wifi?
any help would be greatly appreciated - thank you!
Click to expand...
Click to collapse
this happens suddenly for me ... this wasn't happen 1 or 2 days ago ... maybe an updated app .... :|

for the hell out of it i was going to reboot my home wireless router and noticed that there was an updated firmware out for it - so i installed the new firmware, rebooted, and my transformer hopped right on. anyone having issues might try sinply rebooting their router. that (and maybe the new firmware?) worked for me...

I was suddenly having connection issues myself. Turned out my neighbor moved the channels of his router onto the channels I use. This is of course after I checked what other routers near me were using and selecting free channels when I did my initial router setup. Perhaps you also have an inconsiderate or stupid neighbor. The free app Wifi Analyzer will show this sort of situation.
Sent from my PG41200 using Xparent Purple Tapatalk