Hello there!
Thanks to the many useful threads on this forum, I successfully rooted my Desire HD and implemented ad-hoc Wi-Fi support (in order to control my AR-Drone).
Everything went well so far, since I can connect to "non ad-hoc" networks as well as ad-hoc ones.
But I find myself stuck with a problem which I do not know where to start to try and solve it.
See, I think this has to do with the wpa_supplicant (and not wpa_supplicant.conf) file I modified using >this one<, which is the one that allowed me to detect ad-hoc networks.
I used the recent one (the "-v2" file in the thread) and since ad-hoc works fine now, I assume it has been successfully placed into the /system/bin directory.
The problem is, before this manipulation I could SSH my DHD using the very useful SSHDroid, but now, I just can't connect to my phone using SSH anymore, and I do not get why since I can connect from my phone to the Internet using my home's Wi-Fi network, and SSHDroid does not monitor anything wrong and seems to be correctly launching.
I tried uninstalling and reinstalling SSHDroid but the result is the same.
Where should I start to investigate?
Thanks a lot!
We are attempting to connect several (rooted) developer Samsung Nexus S phones running 2.3.4 to each other using ad-hoc WiFi (with NO access-point, just the phones)
We've gone through the steps of modifying wpa_supplicant.conf to allow the phones to *connect* to ad-hoc networks. We're stuck now not being able to *create* an ad-hoc network from the phone.
Other posts on XDA show that it can be done on phones with the TI wifi chipset (modifying tiwlan.ini). Unfortunately, the SNS does not have this chipset.
These phones do support the wireless-hotspot app, which, IIRC, does create an ad-hoc wifi network, so there must be some support to create one on the phone.
Has anybody successfully *created* a wifi ad-hoc network on the SNS before?
Thanks,
Aaron
I am having difficulty getting our XOOM tablet to connect to WiFi via a mobile hotspot being provided by a Galaxy Nexus. Both the XOOm and Nexus are running ICS and are not rooted and are stock.
The XOOM sees the WiFi network being provided. However, it will not obtain an IP.
I have no issue getting other devices, including another Nexus, and Transformer Prime (both ICS) to connect to the same hotspot that the XOOM can not connect too.
Does anyone else have this issue or know how to fix it?
221 views and no replies? Surely I am not the only on experiencing this issue...
wstahlm80 said:
I am having difficulty getting our XOOM tablet to connect to WiFi via a mobile hotspot being provided by a Galaxy Nexus. Both the XOOm and Nexus are running ICS and are not rooted and are stock.
The XOOM sees the WiFi network being provided. However, it will not obtain an IP.
I have no issue getting other devices, including another Nexus, and Transformer Prime (both ICS) to connect to the same hotspot that the XOOM can not connect too.
Does anyone else have this issue or know how to fix it?
Click to expand...
Click to collapse
Stock Android doesn't support ad-hoc networks, which stock tethering is. Guessing the devices that work are running custom roms.
ZanshinG1 said:
Stock Android doesn't support ad-hoc networks, which stock tethering is. Guessing the devices that work are running custom roms.
Click to expand...
Click to collapse
The Nexus which is providing the mobile wifi hotspot (via Verizon subscription) is running a stock version of Android (4.0.2) and is not rooted. The devices which can connect to this hotspot are another Nexus of similar stock version, a Dell M4500 laptop, and an Asus Transformer Prime running the latest 4.0.3 version of Android as provided by Asus.
As mentioned, the XOOM is running the latest version of stock ICS as provided by Motorola.
The only device that cannot connect to the hotspot is the XOOM. I do not see where I can choose between an ad-hoc network or an infrastructure network within the wifi hotspot settings.
Also, like I mentioned before, the XOOM has no issue with connecting to the Nexus if it shares it's internet via Bluetooth, it only has an issue with obtaining a connection via the wifi tethering mobile hotspot.
What is really confusing to me is that the same wifi hotspot which the XOOM has trouble connecting to, the Prime connects with no problem at all.
Produce a logcat of the xoom attempting to connect.
wstahlm80 said:
The Nexus which is providing the mobile wifi hotspot (via Verizon subscription) is running a stock version of Android (4.0.2) and is not rooted. The devices which can connect to this hotspot are another Nexus of similar stock version, a Dell M4500 laptop, and an Asus Transformer Prime running the latest 4.0.3 version of Android as provided by Asus.
As mentioned, the XOOM is running the latest version of stock ICS as provided by Motorola.
The only device that cannot connect to the hotspot is the XOOM. I do not see where I can choose between an ad-hoc network or an infrastructure network within the wifi hotspot settings.
Also, like I mentioned before, the XOOM has no issue with connecting to the Nexus if it shares it's internet via Bluetooth, it only has an issue with obtaining a connection via the wifi tethering mobile hotspot.
What is really confusing to me is that the same wifi hotspot which the XOOM has trouble connecting to, the Prime connects with no problem at all.
Click to expand...
Click to collapse
Prime isn't running stock Android.
(There is no option in stock android for infrastructure or ad-hoc with tethering, nor is such a distinction relevant with Bluetooth)
ZanshinG1 said:
Prime isn't running stock Android.
(There is no option in stock android for infrastructure or ad-hoc with tethering, nor is such a distinction relevant with Bluetooth)
Click to expand...
Click to collapse
Indeed, my description of "stock" is not accurate. When I describe these devices as "stock" I am receding to them as having an unmodified ROM as it was provided by the respective device manufacturer.
So you are correct that my Prime is not running a true stock version of Android. My bad.
ZANSHING1: Is it even possible to connect a wifi XOOM to a mobile wifi hotspots (specifically, to one being provided by a Verizon Samsung Galaxy Nexus which does have the appropriate hotspots feature as part of the phone plan)?
BIGRUSHDOG: where do I need to go to obtain the "logcat" file you are requesting?
wstahlm80 said:
ZANSHING1: Is it even possible to connect a wifi XOOM to a mobile wifi hotspots (specifically, to one being provided by a Verizon Samsung Galaxy Nexus which does have the appropriate hotspots feature as part of the phone plan)?
Click to expand...
Click to collapse
I think you will have to use one of the tethering apps that provides a full infrastructure hotspot.
This is the only one I'm aware of that does. There may be more. But it has some requirements for the kernel.
http://code.google.com/p/android-wifi-tether/
I've been tethering my Xoom to my Bionic for months. And was tethering to my Droid X before that. I had to flash a ad-hoc wifi supplicant through clockworkmod recovery to get tethering to work on my Xoom. Or. If you have root explorer, I assume you'd just back up stock wifi supplicant file and replace with one that is modified, like I had to do on my galaxy tab. You'd still need to be rooted to do that though. Stock isn't going to cut it.
Sent from my Microwave using Tapatalk and super heated water molecules
So....if I am understanding these responses correctly, the XOOM will be able to access a wifi hotspot which is provided by a (Android) phone ONLY if it (the XOOM) is rooted and has certain files either added or modified in order to connect to the aforementioned wifi hotspot?
wstahlm80 said:
So....if I am understanding these responses correctly, the XOOM will be able to access a wifi hotspot which is provided by a (Android) phone ONLY if it (the XOOM) is rooted and has certain files either added or modified in order to connect to the aforementioned wifi hotspot?
Click to expand...
Click to collapse
Sorta kinda There are two flavors in which a device may be able to broadcast a wifi tether signal. Ad-hoc and Infrastructure. When the broadcasting device is in Infrastructure mode, it basically simulates a full wireless router. Any device should be able to connect as a client. Ad-hoc is a bit different. It is basically a point to point connection in which there's no real routing. Its actually complex but I'm trying to use layman's terms If your phone is broadcasting ad-hoc, the xoom currently can not connect. By default, Android can not connect to adhoc, whether stock or custom rom. For complex reasons, this is especially the case with ics. So it is necessary to determine what type of signal your phone broadcasts. Please describe in detail how you initiative your tether on the broadcasting device.
bigrushdog said:
Sorta kinda There are two flavors in which a device may be able to broadcast a wifi tether signal. Ad-hoc and Infrastructure. When the broadcasting device is in Infrastructure mode, it basically simulates a full wireless router. Any device should be able to connect as a client. Ad-hoc is a bit different. It is basically a point to point connection in which there's no real routing. Its actually complex but I'm trying to use layman's terms If your phone is broadcasting ad-hoc, the xoom currently can not connect. By default, Android can not connect to adhoc, whether stock or custom rom. For complex reasons, this is especially the case with ics. So it is necessary to determine what type of signal your phone broadcasts. Please describe in detail how you initiative your tether on the broadcasting device.
Click to expand...
Click to collapse
The broadcasting device is a Verizon Galaxy Nexus running the latest 4.0.2 version of Android as provided by Verizon. The phone is not rooted and we do pay for the tethering service offered by Verizon.
In regards to how we turn on the wifi tethering, we complete the folksingers steps:
SETTINGS> More... (under WIRELESS & NETWORKS)> Tethering & portable hotspots> Portable WiFi hotspot (turn on by activating the green check within the box)
In regards to how the WiFi is Configured, we are using the WPA2 PSK security option.
...and as I mentioned before, my Asus Transformer Prime has no issue connecting...nor does my laptop....only the XOOM has a problem.
Download this
https://market.android.com/details?id=net.solarnz.apps.lumberjack
Attempt a connection and export the Lumberjack logs. The post them on pastebin.com
Hello!
I recently moved away to a new home and I don't have a wifi router at this time and don't actually need one for just my G3. But still want to try whether any alternative is possible. I stumbled upon what a trick called "AdHoc" but according to the guide, android nativly doesn't support Adhoc (or something like that).
So I am looking for a way to make it work OR any other way to get wifi on my phone. Probably something like reverse tethering.
Thanks!!!
EDIT :: I am also tried using adhoc for myself but, the phone gets stuck on "authenticating" .
So you want to tether your phone to your computer?
I use a program for Connectify to make my own private hotspot using whatever wired connection my laptop has. Its entirely free though probably not the most lightweight or "hack-y" way of doing it.
We had a guide for tethering your PC internet for froyo in which we had to replace WPA supplicant file but it's of no use to you (cm 7)
I myself had tried adhoc of Microsoft but it is way too difficult to configure
You did not mention anything about your PC
If it is from Dell you get a program known as peer net with which you can get wifi in your home. This works with our galaxy 3
Also I think cm7 supports Adhoc as the program mentioned above works flawlessly with it
If it is true then try connectify, virtual router and other programs
If you succeed in configuring wifi be prepared to use the slowest internet speed possible
Sent from my GT-I5800 using XDA
I'm trying to modify my Asus ME172V tablet so it can access an ad-hoc wi-fi connection.
The best method appears to be replacing the wpa_supplicant file. However when I replaced the original with a file that was modified to enable ad-hoc wi-fi would not turn on.
Is there a wpa_supplicant file that will successfully enable ad-hoc wifi on the ME172V?
Or is there another way I can enable ad-hoc access?
I got a suggestion on another forum (Thanks!) and resolved the copying permission issue by turning off the wi-fi.
Partial solution found - delete this message
My questions in my modified previous post are still pertinent. I can't figure out how to delete this post...
need wpa_supplicant for ME172V w/ad-hoc
Well I've searched and found 3 different wpa-supplicant files that all apparently enable ad-hoc on other devices. Unfortunately on the ME172V wi-fi can't be turned on with any of them.
Anyone know of a wpa_supplicant that enables wi-fi and will work with the ME172V?
I want a tablet with ad-hoc wi-fi as a controller for my music server. If I can't come up with a solution soon I guess I'll just buy a Windows tablet and sell the ME172V.