I love the ICS beta, but I can't tether. My Nook doesn't see the wireless signal put out by my phone, even though other devices do. Anyone have a cure?
Seconded. Does it have to be fixed at the kernal level?
seems like an ICS general issue - other devices are having the same problem. from what i remember before using any roms on the nook, the wpa_supplicant file had to be modified to allow ad-hoc networks.
Related
Hi!
Did anyone manage to connect to an ad hoc wifi network? Its my understanding that you have to root your phone and edit some files in order to do so. My phone is already rooted. Anyone willing to try it out and give the steps here?
Thanks!
Android 2.1 does not support this.
Yes! I know that! But i think you can edit some files after rooting in order to allow this?
Galaxy S wont find ad hoc AP, how to fix?
Hi, how to configure galaxy to connect to a ad hoc ap? It seems like wont find the ac hoc SSID at all?
Hello,
Ad Hoc Access Points support start with Froyo, if you really need it, give the latest XXJP2 a try
Any luck finding the answer?
Nope! No luck yet! And it seems no one is interested
Sent from my GT-I9000 using XDA App
have you tried modifying those files (wpa_supplicant.conf and others)?
Are you just trying to use your phone as a mobile APN? Because this is built into the galaxy S.
brunes said:
Are you just trying to use your phone as a mobile APN? Because this is built into the galaxy S.
Click to expand...
Click to collapse
I am trying to use my wired LAN connection on my phone using the Laptop's ad-hoc wifi connection.
I'm reasonably confident that it simply isn't supported in Android 2.1 and that it's totally unrelated to config files (i.e. There's nothing your average user can do about it). I don't know if ad-hoc wireless made it into Froyo but there has definitely been an official feature request filed to Google for ad-hoc functionality.
i also find it very annoying that sgs doesn't support ad-hoc.
You can try to use this software http://www.connectify.me/
sadly it uses windows 7..
Just had a look over here: http://forum.xda-developers.com/showthread.php?t=754961
Can any dev please patch the SGS version of wpa_supplicant? Pretty please?
Another thread: http://forum.xda-developers.com/showthread.php?t=755254
really??
i couldn't find it even though i have jp3
The android OS filters out all Ad-hoc networks. There was a patched wpa_supplicant that seems to be working for some. I tried it and it does display the ad-hoc networks but fails when trying to obtain an IP... I am stay playing with it but I will update if I even manage a connection.
http://www.xda-developers.com/android/android-ad-hoc-wireless-network-support/
[Q] still no ad hoc in JPC??
is it true??
i tried a couple times and i'm still wondering about this ad-hoc problem
anyone?
i really need to confirm this
[Q] ad hoc in jpc??
is there still no ad hoc compability in the new FW JPC??
is there any trick to connect wi-fi from laptop to galaxy s.
PS: i use vista, so no connectify.
thx
hello all, i got this question: is wifi tether based on kernel capabilities? because am using dk28 and is just not working for me, apk installs fine, open and run but i cant find the connection on my laptop/evo4g. I want to know if the kernel has to support it, if so does the stock dk28(rooted) has support for it or do i have to use a different kernel?
Thank you in advance!
mine works fine..your evo cant see it because android cant see adhoc ..idk about your laptop
I'm not sure what the above poster said about Evo, but this is Epic forum.
So, I had Pre 9 running on 2.1 rooted, would not work on DK28. I read somewhere that Pre 11 was working. Downloaded, turned on and everything was great, so the version makes the difference.
Hope that helps.
To reiterate what was said earlier.
Android phones are not capable of seeing adhoc connections. Which in this case of using WifiTether is what you are creating.
Your laptop should be able to see the connection just fine. I would go back and check some settings in wifirouter and your laptop to make sure you are able to get things working correctly.
Any version of wifirouter after pre11 should work. All the way up to pre15.
Dear all,
Figured out how to ad-hoc connect via wifi. I guess it is NOT the Xoom's fault. It is the smartphone's fault.
This is according to my observation:
I had both stock non-rooted XOOM and stock rooted 2.2 froyo ATT Captivate.
I was unable to wifi tether because the ATT mobile AP message kept popping up saying that I needed to purchase a tether packed (No thanks).
I preferred the stock experience but finally went back to a custom rom (firefly) for the captivate. After installing the custom rom I can CONFIRM that I can connect via ad-hoc tether wifi via my captivate and Xoom!
I however, have not been able to bluetooth tether.
Anyways, I am returning my XOOM for the Asus transformer because it has the LED backlit screen and besides the $100 less price tag, it is identical.
Stock xoom here and rooted captivate using stock ROM and eXistz KB1 kernel.
I installed wifi teather found here: http://code.google.com/p/android-wifi-tether/downloads/list
Had to play around with the settings and set Device Profile to Samsung captivate and setup-method to Softap for Samsung and now i can teather no problems.
Softap for Samsung is actually Infrastructure mode, not Ad-Hoc.
It works fine with wifi tethering on 2.3 roms. No issues on CM7
I have not been able to get this to work.
I have the Wifi Xoom 3.1 Stock ROM
Captivate Rooted with Continuum v4
firmware: 2.2.1
Kernal: 2.6.32.9
buildNumber: FROYO.XWJS8
Any Ideas? Or maybe a step by step guide? I am trying to get the BT Tethering to work.
Thanks,
-Drokare
Yeah I was doing this with my stock Xoom and CM7 Desire HD for ages. The problem was that an unrooted phone sets up an ad-hoc connection whereas in CM7 anyway it behaves as a router AP.
So does that mean I can't get my Xoom to tether to my Captivate via BT?
Kcarpenter said:
Softap for Samsung is actually Infrastructure mode, not Ad-Hoc.
Click to expand...
Click to collapse
+1
The Xoom CAN-NOT tether to Ad-hoc without being rooted and changing out the wpa_supplicant file. The Captivate has the ability to tether infrastructure mode (mobile AP isn't ad-hoc.) The wireless tether 3.x (softap) is much more buggy than the 2.x (ad-hoc) on most phones but it might work great on your captivate. If it keeps restarting or getting really hot like it did on mine, you could always root your Xoom and flash the ad-hoc fix in recovery (super easy.)
Here's the link
But that is Wifi Tethering or just setting my Captivate to be a Hot Spot.
I was more specifically asking about the Bluetooth tethering.
Has anyone been able to get this to work? I have seen numerous threads that say they got their Wifi only Xoom to BT tether to Droid X and others.
If I would need to flash my Captivate to another build I would easily. This is the only function I need to for my Xoom and I am completely content.
So I am asking if anyone has got the BT tethering to work... the Wifi Tethering or Hot Spot as you said does heat up the phone quickly, where my friend and his Droid X with BT tethering does not heat up noticeably.
Thanks in advance,
-Drokare
So if I root the Xoom and add the Ad-hoc fix, it would allow me to use the BT Tethering?
I keep seeing threads saying fixes are needed for this to work, but I never had an issue on 3.01, 3.1 or 3.2.
HTC Desire running DevNull 1.1, set up a hotspot using WPA2 and I can connect straight away without a problem. Switch to a proper wireless access point and back again still no problems.
Am I getting mixed up with something else?
I'm tethering a connection with my Xperia X10 using 'Wifi Tether for root users' app. I'm sure it work's fine cause I'm able to connect to this network via laptop or another android phone. What I'm not able to do is connect to this network from my Transformer. I click on the network and it just changes the state to Remembered but it won't connect to it no matter how many times I cick the thing.
Have any of you managed to solve this already?
I'm running an official ICS, no root or stuff. Completly clean.
What type of hotspot is it putting out? Ad hoc?
I think so
I don't know if it can help, but the issue you describe is exactly the one I had when I used my HTC Sensation (with any ICS custom ROM) as a Wifi AP : I could browse the web from any peripheral connected to the "HTC Portable Hotspot"... except from my TF101 !
I thought the problem came from the TF101 itself (and I'm still thinking it...), but curiously I solved it by flashing my HTC Sensation back to stock ROM (Android 2.3.4) !
Now my TF101 can browse the web through my Sensation like any other device...
I'm still thinking it's Transformer. I was flashing several softs before I started posting. It was always only the bloody transformer that couldn't connect... funny thing is that exactly week ago on the exactly same ICS I've managed to connect. Then it started to fail.
I thin your router needs to support Infrastructure and not adhoc networks to work wth the transformer.
Sent from my Transformer TF101 using Tapatalk
Dude - it's a phone, not a router. It supports ad-hoc only. And as I said - it worked ocassionally. Myabe it's a reason to call a guarantee services?
if your TF is already rooted, then try the free app wifiadhocenabler from the market. i used this for my galaxy s2 because samsung disabled adhoc connections.
I can connect to my x10 just fine using the native tethering (via settings). I am still on HC though...
Sent from my X10a using The Force
I'm just a user, but I had the same problem when I was running Gingerbread on my HTC Legend. Now, there aren't really any proper drivers for that on Gingerbread, so it was done ad-hoc. When I updated to ICS on the TF101 it lost the ability to connect to ad-hoc hotspots. Installing a ROM that uses Froyo fixed it.
I think Prime users faced the same issue, but managed to enable ad-hoc support. Root on the tablet was of course needed.
This is really weird. One day it's connecting and week later it's not. And I haven't been changing ROM since then (neither on the phone or transformer)
Ad-hoc wireless support was supposed to be fixed in the latest .17 ICS update; however, I am still unable to use my TF101 to connect to an ad-hoc network.
-Matt