If the routers are doing Auto channel selection then it is possible that the prevailing wifi reception conditions have caused them to swap to a different channel that can then cause TP connection problems. Normally the TP seems to work best on a low channel number (e.g. 1)
Our work networks seem to run three channels - 1, 6 and 11. 11 seems to be the strongest at my end of the building.
Edit:
I noticed something odd this morning. I came in to work this morning and the tablet connected to wifi just fine. I installed something that required a reboot, and after the reboot wifi crapped out. One of the interesting things I noticed was that after the reboot in Wifi Analyzer, I was no longer seeing any of the 5ghz channels, NOR was I seeing the wifi networks on channel 6. Just 1 and 11.
After tinkering around, a reboot into WebOS then back to CM9, some checking with Wifi Analyzer, and turning the radio off and on a few times, I finally managed to get wifi back. In doing so, Wifi Analyzer once again is showing the APs on 1, 6 and 11, as well as the 5ghz bands.
Our work networks seem to run three channels - 1, 6 and 11. 11 seems to be the strongest at my end of the building.
Router manufacturers design the routers to use those three channels to keep the best channel separation. The problem is Android running on the TouchPad does not play well with channel 11. Since you don't have any control over that routers at work, there is nothing you can do to your TouchPad to improve the situation except wait for a wifi driver in ICS that works properly or use WebOS at work.
Our work networks seem to run three channels - 1, 6 and 11. 11 seems to be the strongest at my end of the building.
Edit:
After tinkering around, a reboot into WebOS then back to CM9, some checking with Wifi Analyzer, and turning the radio off and on a few times, I finally managed to get wifi back. In doing so, Wifi Analyzer once again is showing the APs on 1, 6 and 11, as well as the 5ghz bands.
Just for grins you might want to try FXR Wifi Fix and Rescue. If I understand the way it works, it copies your AP login settings, then it deletes your wifi profile and maybe some other housekeeping like turning the radio off and back on and then sets your AP logins again. There is also a program Wifi Fixer that appears to monitor your connection and when it sees a problem, tries to work it's magic to get it back. FXR has to be run each time you need it, Wifi Fixer run in the background.
Wifi Fixer got a cheap Android tablet going on wifi when nothing else worked.
am on cm9 march 29 th build of tenderloin with mod 1.5 with consistent download speed of 15000 kbps and upload speed of 6000kbps,no problems with wifi at all.initially had lot of problems so clean installed cm9 alpha 2 ,fixed the time to the local time and then clean updated to march 29th cm9 build with mod 1.5 its working damn good so am not going to change unless there is a new beta build .
I have not... yet. I'm sort of waiting until if/when they get integrated with the main source. In the meantime I'm just trying to see if I can figure out what is going on (maybe to help a dev along?).
Quote:
Originally Posted by nevertells2
Just for grins you might want to try FXR Wifi Fix and Rescue. If I understand the way it works, it copies your AP login settings, then it deletes your wifi profile and maybe some other housekeeping like turning the radio off and back on and then sets your AP logins again. There is also a program Wifi Fixer that appears to monitor your connection and when it sees a problem, tries to work it's magic to get it back. FXR has to be run each time you need it, Wifi Fixer run in the background.
Wifi Fixer got a cheap Android tablet going on wifi when nothing else worked.
I'll try that... I have it installed now.
It's really strange though, each time you turn off and on the Wifi, it seems to be a crapshoot as to what channels it sees. I have a feeling that the driver isn't quite getting initialized properly with the correct channel data.
I have not... yet. I'm sort of waiting until if/when they get integrated with the main source. In the meantime I'm just trying to see if I can figure out what is going on (maybe to help a dev along?).
I'll try that... I have it installed now.
It's really strange though, each time you turn off and on the Wifi, it seems to be a crapshoot as to what channels it sees. I have a feeling that the driver isn't quite getting initialized properly with the correct channel data.
Not quite sure what you mean by it being a crap shoot about what channel it sees. Whatever channel you have your router locked to is what channel the TP will see. Have you tried looking at the wifi spectrum in your area using Wifi Analyzer to see how much traffic is using which channel? I would lock your router to the channel with the least traffic.
Not quite sure what you mean by it being a crap shoot about what channel it sees. Whatever channel you have your router locked to is what channel the TP will see. Have you tried looking at the wifi spectrum in your area using Wifi Analyzer to see how much traffic is using which channel? I would lock your router to the channel with the least traffic.
I don't blame you for possibly not following along the last couple days. This is a corporate wireless network. They run AP's on channels 1, 6 and 11 throughout the building. I can see the APs on 1, 6 and 11 simultaneously (as well as a pair of 5ghz channels used).
When the touchpad's wifi is working PROPERLY, it can see the APs on ALL of the channels. If I wifi off and back on, it "randomly" sees only a subset of channels at any given time. Sometimes it will only see 1 and 11, sometimes only 6 and 11, sometimes only 11. Occasionally if I cycle enough times, it will eventually see ALL of the channels, and it is only during this time that it is capable of connecting to the network properly.
Short answer: It's NOT my network nor my router, I have no control over the network itself. What I am finding is what appears to be an initialization issue with the wifi chipset in the touchpad (which we all know there's SOMETHING wrong in the drivers already - the question is WHAT).
I don't blame you for possibly not following along the last couple days. This is a corporate wireless network. They run AP's on channels 1, 6 and 11 throughout the building. I can see the APs on 1, 6 and 11 simultaneously (as well as a pair of 5ghz channels used).
When the touchpad's wifi is working PROPERLY, it can see the APs on ALL of the channels. If I wifi off and back on, it "randomly" sees only a subset of channels at any given time. Sometimes it will only see 1 and 11, sometimes only 6 and 11, sometimes only 11. Occasionally if I cycle enough times, it will eventually see ALL of the channels, and it is only during this time that it is capable of connecting to the network properly.
Short answer: It's NOT my network nor my router, I have no control over the network itself. What I am finding is what appears to be an initialization issue with the wifi chipset in the touchpad (which we all know there's SOMETHING wrong in the drivers already - the question is WHAT).
You're right, I did loose track of the fact that you are talking about your companies network. Are the different AP's fixed on the different channels? Is there only one SSID for all those AP's? You should be able to tell using Wifi Analyzer which AP is set to which channel. If each AP has a unique SSID, then you could "Forget" all the AP's and only try to connect to those on either channel 1 or 6.
What are you trying to do with your TouchPad at work? If it is just checking email or browsing, try using WebOS. I have only run into one person that had problems using WebOS with his router.
I have not... yet. I'm sort of waiting until if/when they get integrated with the main source. In the meantime I'm just trying to see if I can figure out what is going on (maybe to help a dev along?).
The ath6kl drivers (2.9) are available as a simple update zip and do seem to have helped quite a few people where the networking is environment is outside their control. It looks like they are the main candidate as the basis for new integrating new drivers in and it is also helpful to get feedback that they have helped or resolved network connection issues.
Always a good idea to have a Nandroid backup if you want an easy way back.
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?