Related
so with my minimal knowledge of phone stuffs ive kinda learned that when i run the wireless tether for root app on my phone it uses ad hoc to supply other computers with internet... basically im asking, will my evo be able to supply my xoom with internet?
Not at the moment, no support for Ad-Hoc networks in HC, not sure if there ever will be - very annoying.
I'm not sure but I believe there is a new version of Wireless Tether that will allow such a connection. When I first tried the Kindle connecting to my DX, it wouldn't connect. With the new version, it does.
Sent from my DROIDX using XDA App
My Xoom connects to my DX with no problems.
Go download Wireless Tether from the website. The experimental one is called Wifi Tether now. Works like a charm for infrastructure mode so that the Xoom can tether with your phone. Also Bluetooth seems to work fine as well.
Sent from my DROIDX using Tapatalk
Is the Wireless tether for the phone or the Xoom (or both)? I need an option for the iPhone in case the steps posted here won't work!
is this an app that enables ad-hoc detection on the Xoom,
or
does it just provide a full wifi hotspot tethering feature for Android devices?
I also use an iPhone which supplies an ad-hoc hotspot connection that I need my Xoom to recognize and connect to.
So does that mean you got it to work that way? Is the app available through the Market?
No its not available in the market. Google wireless tether and look for wifi tether. The new app sends the signal via infrastructure mode. I think it applies to certain phone like Droid X and EVO.
Sent from my DROIDX using Tapatalk
The Wireless Tether app is ran on the host phone wanting to be turned into a wifi hotspot. There are certain phones that run in Ad-Hoc mode in default (aka Droid 1) and the only option to tether the Xoom to them is via bluetooth. As others have said, the new version "WiFi Tether" is apparently enabling infrastructure mode rather than Ad-hoc mode, something that the Xoom can actually connect to.
There is no app that you install on the Xoom. When the WiFi Tether is ran on the host device, the Xoom just connects to it as a WiFi router and works just fine (or bluetooth if thats what you're doing).
So OP, if you can't get the new version of WiFi tether to work for you and your Xoom, try the Bluetooth tethering option, it's been shown in detail in a thread here how to do it, and it should work just fine.
funnycreature said:
Is the Wireless tether for the phone or the Xoom (or both)? I need an option for the iPhone in case the steps posted here won't work!
Click to expand...
Click to collapse
The app is for android, and for the host device not the Xoom, so you'll need to Bluetooth tether your iPhone.
wpa_supplicant
I understand exactly what the OP is talking about, as i'm trying to do the same thing. What makes matters worse, is that ad-hoc connections ARE possible in android. Meaning android can connect to ad-hoc networks, but it requires swapping out the wpa_suppplicant file in system/bin with a modified one that doesn't filter out ad-hoc networks.
i've even tested this on my EVO, and it connects to other android phones incapable of broadcasting in infrastructure mode, it even connects to my ubuntu netbook broadcasting in ad-hoc...
(if you want to see what i'm talking, just search the forums for wpa_supplicant, something will turn up )
I've tried doing the same "fix" with my xoom, but it doesn't take. Using ADB or root explorer, i've replaced the orignal (making sure to save a copy just in case) and fixed permissions to 775, but it doesn't take. The wifi antenna will turn on, but it doesn't find anything once being replaced, not even saved networks or access points. I can get wifi back by restoring my backup, but i'm at a loss as to why it doesn't work on the xoom (3.0) but does with my evo (2.3).
as a side note, i'm using the right replacement for the wpa version returned by entering
"wpa_supplicant -v" in a terminal emulator or adb. It returns version v0.6.10 and there is a working, modified, v0.6.10 that should make things work, but doesn't....
anyway, if anyone has any input, i would love to hear it!
I am in the same boat. Regardless of whatever permission settings I have tried (mentioned in the dev forums that I can't yet post in), I still get a dead wifi with the new supplicant file.
Ah, I feel better now. It must have been the supplicant file, as I found this other one and it worked without permission modifications first time out.
You will have to google "xoom supplicant" and use the file found on the first response (android.net)-I can't post the link- the downside to attitude having, overlord type forums is inability for new users to provide any help, or at least with any convenience.
i try connecting my xoom to my computer, and it wouldn't work. i have the "Intel My Wifi Technology" but each time i set up a connection, the xoom finds it, but will take like a minute trying to connect and all i see on the xoom is "Obtaining IP address". it shows on my computer that a new device is connected. maybe this only works computer to computer. cuz i have had success with another laptop connecting to my computer with no problem.
I am using the Launchpad kernel and the WPASupplicant file and am connected to my phone's ad-Hoc network now. I used the beta Wi-Fi Tether and it worked great, but crashed my Samsung Galaxy S at least twice a day. So I installed the WPA file without setting any special permissions, just used Root Explorer to copy it an it worked fine.
Is there a way to connect on a ad-hoc hostet by a laptop (win7) yet?
That would be interesting, cause if it work this way, it will work for every phone or something else!
Hey Guys,
i am having a little problem. i am using the Intel My Wifi Technology. and i don't know if i am doiing something wrong or this is just not possible. but i try connecting my xoom to my laptop, and it is not working or connecting. i get a message on the xoom that say's Obtaining IP address", but nothing happen on the xoom. is this not yet possible on the xoom. i don't know if this is consider ad-hoc network or not, cuz i am new to all this.
but here is the link to intel website for the program i am using as a wifi hotspot.
http://www.intel.com/products/wireless/mywifi.htm
and here is a video of what the program does.
http://www.youtube.com/watch?v=AuAQjR76A68
anyone with knowlwdge on this please help me understand what i am doing wrong or not doing. or even if this is a possibility.
If you're not opposed to rooting your Xoom, here's another option. I just unlocked and rooted my WiFi-only Xoom yesterday, and inserted the supplicant file in this thread: http://forum.xda-developers.com/showthread.php?t=1033314
It works like a charm! I'm running a WinMo Touch Pro 2 with WMWiFiRouter, and the Xoom now sees and properly connects to Ad Hoc networks. And, it still works with all other networks.
I don't know which way you prefer to attack the problem (from the Xoom or the phone), but I've been thrilled ever since I got all this done yesterday. Everything else on the Xoom is great, and now I've got the working SD card as well.
supremecream06 said:
Hey Guys,
i am having a little problem. i am using the Intel My Wifi Technology. and i don't know if i am doiing something wrong or this is just not possible. but i try connecting my xoom to my laptop, and it is not working or connecting. i get a message on the xoom that say's Obtaining IP address", but nothing happen on the xoom. is this not yet possible on the xoom. i don't know if this is consider ad-hoc network or not, cuz i am new to all this.
but here is the link to intel website for the program i am using as a wifi hotspot.
http://www.intel.com/products/wireless/mywifi.htm
and here is a video of what the program does.
http://www.youtube.com/watch?v=AuAQjR76A68
anyone with knowlwdge on this please help me understand what i am doing wrong or not doing. or even if this is a possibility.
Click to expand...
Click to collapse
Is it right that you host a Wifi on your computer and tether internet to you tablet? I think its the usual problem android and ad-hoch, witch not work!
ok, I'm a total noob. I chose to buy the iconia because it had ports which the ipad doesnt have. I would like to teher with my iphone 3gs running pdanet. I read your forums. I rooted the iconia(thank you very much btw) n installed the new wpa supplicant. I also installed root explorer as per the instructions. I couldnt get the iconia to see the wifi hotspot eventhough I could see it on my laptop. I noticed that in the system/bin I had 2 wpa supplicant I removed the original one and after that the wifi woulndt work all I would get was an error. Even after I put it back it wouldn't work. Anyway to make a long story short I fiddle with the permissions on the original n got my wifi working again. Howeverr I still can't get the iconia to see the iphone hotspot. If you have any solutions I would greatly appreciate it. Also if u have a solution please consider that I'm a noob n would appreciate some sort of tutorial. Thank you very much.
domnoob said:
ok, I'm a total noob. I chose to buy the iconia because it had ports which the ipad doesnt have. I would like to teher with my iphone 3gs running pdanet. I read your forums. I rooted the iconia(thank you very much btw) n installed the newIt is not possible to have two files in the same place with the same name wpa supplicant. I also installed root explorer as per the instructions. I couldnt get the iconia to see the wifi hotspot eventhough I could see it on my laptop. I noticed that in the system/bin I had 2 wpa supplicant I removed the original one and after that the wifi woulndt work all I would get was an error. Even after I put it back it wouldn't work. Anyway to make a long story short I fiddle with the permissions on the original n got my wifi working again. Howeverr I still can't get the iconia to see the iphone hotspot. If you have any solutions I would greatly appreciate it. Also if u have a solution please consider that I'm a noob n would appreciate some sort of tutorial. Thank you very much.
Click to expand...
Click to collapse
It is not possible to have two files in the same place with the same name. Remember to put the tablet into airplane mode first. Then just rename the original to wpa_supplicant.bak, copy in the new one (make sure name is wpa_supplicant), and edit permissions on the new file to have execute for all. Turn off airplane. Copy the .bak to somewhere safe. That should be all you have to do.
Thank you for your answer. I moved the original file n put it on my sd card. Left the new wpa_supplicant_a500_wifi_adhoc in the system/ bin n changed the permissions but still got wifi error. Maybe I have the permissions wrong is it all check on read, first two check on write n 3 checks on execute?? N the special no checks ??
Moved as not development, please read the rules and post in the correct section ONLY.
I would like to do this as well. Right now, I have PDAnet on my iphone 3gs (jailbroken) and set it up as a wifi hotspot, but this is tedious and drains the battery. Bluetooth or hard tether would be preferable, but I think I'm just going to get an android phone and be done with this iOS crap.
I think android phones have the same issue. Read the forums if the wifi connection is an adhoc such as pdanet android os stick isn't designed to see it, which to me seems like a huge oversight.
I agree, it seems stupid that there is no native support for adhoc stuff. One should not have to root their phone for that functionality.
It like these manufacturers want you to buy their product, but are hell bent on preventing you from using it as anything but a expensive web browser. Just look at the list of all the stuff you can't do without "bending the rules" and rooting/hacking something.
There is no good reason for it!
Has anyone tried tethering via MyWi off Cydia? I just installed it to try out the trial but will not be able to test it out until later today. I'll give you guys and update, but I believe it also creates an adhoc network.
MyWi works, but has anyone been able to establish an L2TP over IPSEC connection over this kind of adhoc network tethering?
I took a look at the logs on the VPN server and looks like it never gets a response after the initial contact and just closes the connection because it declares the peer dead.
ipigi said:
Has anyone tried tethering via MyWi off Cydia? I just installed it to try out the trial but will not be able to test it out until later today. I'll give you guys and update, but I believe it also creates an adhoc network.
Click to expand...
Click to collapse
I tried to get MyWi to work, and it just doesn't. The wifi tethering hotspot seems to work (with the correct wpa_supplicant file), but PDAnet already does this for free. I was interested in either the hard wired or bluetooth functionality.
Simply put, bluetooth and USB tethering does not currently work on Honeycomb 3.1. I wish someone would prove me wrong, but everything I've read indicates that the support isn't there. I've seen a few people claim that they've gotten it to work, but they've never been able to back it up by explaining how.
Bluetooth tethering needs a specific profile, which does not appear in the settings window under the device when your iphone is paired. This should show up under "profiles" when you click the little wrench icon, but it doesn't appear to be there. Looks like you can pair with the iphone, but you cannot connect, which is the required step to get the profiles to show up. If you try to "connect" from the iphone side, it says A500 is not supported.
Furthermore, Honeycomb seems to have no embedded support for USB tethering. Hopefully someone can create an app which will allow an android tablet to be a USB tethering client.
Cheers,
-PW
Hello I have in my rom Iconia A500 THOR V14.2 ANDROID ROM 3.2.1 works fine, I used wifi tethering with my tel. rom htc hd2 and HD2_NDT_GINGER_2.3.7_CM7.2_BASED_V35.0_MAGLDR and earlier and this too well, but with great battery consumption at tel. So PdaNet tablet discovered by BT to connect both perfect and very good speed and low power consumption.
The problem is that I tried to do the same with other rom in the Tel and nofunciona with any other, in some Wifi if I managed to connect but bt nowhere.
I can not access this configuration to the proxy and the true sense of megustan the HTC rom and now I can not use them for this.
I have read also in San Google and forums and I think it has something to do DHCP choking in Iconium.
Would greatly appreciate help in resolving this problem.
I'm not completely sure I understood you correctly, but here's what I think might help you:
Bluetooth is somewhat broken on this tab. I don't know if BT tethering works on any ROM... I never actually searched for it and it's not in the settings.
WiFi Tethering works just fine with most ROMs; Acer removed the menu entry, but not the necessary software, i. e. any "WiFi tethering widget" will work if you've got root. I'm not sure about non-rooted devices, though, as I rooted mine like 10 minutes after I got it... Also, most custom ROMs (even almost-stock ones) restore the menu entry, so you don't even need that.
EDIT: After re-reading your post I think the problem might just as well be with the kernel you use... Its source is (in violation of the GPL) not available, so I can't be sure of that.
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.
I really tried to find this answer before posting!
My Simple Touch was working fine with my home wifi until I rooted it. Now it can't connect. The signal is fine; the nook is right beside this computer which is connected fine. It says the signal is good. It just never connects.
I tried forgetting it and adding that network again.
Suggestions?
ravenrose said:
I really tried to find this answer before posting!
My Simple Touch was working fine with my home wifi until I rooted it. Now it can't connect. The signal is fine; the nook is right beside this computer which is connected fine. It says the signal is good. It just never connects.
I tried forgetting it and adding that network again.
Suggestions?
Click to expand...
Click to collapse
What firmware version are you running? B&N made a number of improvements to wifi in later versions. You might upgrade to a later version and see if that work better. If you want to completely reset to factory, there are instructions for doing so.
Also, sometimes it depends on your router. Mine had trouble connecting because it didn't send it's SSID. (this problem persisted with all versions.) Check your router settings (or get your parents to) and see how it's configured, and be sure it is compatible with the nook.
some router is better, my nook2 wifi is OK in my home but does not work in office