I cannot get wifi tethering to work on my Droid 1 when running MIUI, stock froyo, or Cyanogen. I have tried Wireless Tether on all three ROMS, I can connect to the phone, but no Internet data is transferred. I'm currently using MIUI 12.3 and found that it has a built in wifi tether that also fails. Barnacle didn't work either.
From what I can figure out this may be either a kernel issue (I never changed it from stock, but MIUI may have its own?) or a problem with how I achieved root (superoneclick). I appreciate any and all advice! Thanks!
I run both a rooted 2.1 stock and NookieFroyo. One thing I noticed about Nookie is that the adhoc performance when tethering to my Droid1 is HORRIBLE. This has been consistent between versions 056 to 068. I decided to replace the wpa_supplicant with this one and VIOLA! Rock solid adhoc performance with my Droid1.
This is tested on NookieFroyo 0.6.8 and a Droid1 running 2.2.1 using both Barnacle and WifiTetherForRootUsers.
Hi How do I enable the adhoc on my nook to work to connect to WIFI through my phone. I have been reading through a lot and I'm so stuck. I just left it alone for a few days. It was getting on my nerves. I want to be able to connect to wifi on my phone. Oh and just to add, I do not know how to use ADB. The driver issue and the sdk is rocket science to me. Any help that you can provide will be a great help.
from what i understand, the wireless tether in the market is an older version. Use one of the more updated wifi tether versions found on their site at....
code.google.com/p/android-wifi-tether/downloads/list
i believe any wifi tether after .05 will have infrastruce tethering available as well. I was frustrated with not being able to tether too, but this fixed my problems.
Thanks, your attached wpa supplicant has my tethering working quite fast, whereas before it hardly worked at all
I have an AutoNooter'd Nook Color. My cousin did it for me so Im not sure on the details of what version is running.
Thing is, I can tether the NC to my EVO but not my moms Epic. Why not? Wifi tether on both are version 2.0.6. I can tether both to my laptop with no issues.
Both work to tether my laptop. Both on same channels (6).
Only the EVO works to tether the NC. But the Epic does not. The NC color doesn't even see it in the wireless settings.
Oh, earlier I did the 1 click root for the Epic in order to put Wifi tether on there.
Like I said, tethering works fine to my laptop, its just the NC doesn't see it, but sees the EVO.
Weird,
Any help?
Not knowing the Epic personally, my first guess would be the Epic is providing tethering adhoc vs. access point mode. There's some discussion in other development threads that include scripts to allow you to change modes on a rooted NC, that'll likely be your best bet.
Some brief Googling tells me I may be right - saw references to adhoc mode in relation to Epic tethering. So that's what I would pursue (had to do this on my iPhone's tethering as well)
Devices running froyo typically broadcast infrastructure networks as opposed to adhoc. Stock android devices have trouble connecting to adhoc networks.
http://forum.xda-developers.com/showthread.php?t=868354
here is your solution
one of your devices is probably adhoc while the other is infrastructure.
the NC will connect to infrastructure devices and not to adhoc without the fix.
the fix still has some bugs though (wifi stops when screen is off)
in that thread is a script for switching between both using ADB..
have fun!
nice to know,
I did some searches on Adhoc with the Epic. Seems this thing only broadcasts in ADHOC, and most android devices won't pick it up. So my EVO works because it can broadcast infrustructure mode (is that because its 2.2 Froyo?).
So from what I read, MobileAp for the I9000 can be put onto the Epic but seems like there's alot of work that goes into it. And supposebly works better than Wifi Tether.
http://forum.xda-developers.com/showthread.php?t=756804
I just wanted it to be simple....will the Froyo Epic update fix this by any chance?
I swear at one point in time I had a version of Android Wifi Tether that allowed me to use WPA2. Can I still find the apk for this or am I just thinking crazy thoughts?
i have such in CM6 on Desire. would like to get in on TAB...
i've installed WiFi Tether for Root Users 3.0-pre11 which is experimental and includes WPA2, but it doesn't have TAB on the list of devices profiles.
so tethering starts with errors and it doesn't show up in the networks list, i think something's wrong or missing for TAB
the link for the tool is
http://code.google.com/p/android-wifi-tether/
I was wondering if anyone had tested the new update (1.2) with Wifi in the Ad Hoc Mode as is commonly used with WiFi Tethering apps? Version 1.1 could not see a ad hoc WiFi network without some file modifications.
answer from a newb
No it still does not see adhoc networks, what modifications do you speak of, for that is what i would like my nook to do, see and connect to adhoc networks. i assume i will have to root it, and if so is there a clear easy way to root the 1.2 update? or even better have the stock system and rooted system side by side (i think i read that you can use the sd card to hold the root info on. i a newb to all this rooting stuff, but want to expand and learn.
Cpt420 said:
No it still does not see adhoc networks, what modifications do you speak of, for that is what i would like my nook to do, see and connect to adhoc networks. i assume i will have to root it, and if so is there a clear easy way to root the 1.2 update? or even better have the stock system and rooted system side by side (i think i read that you can use the sd card to hold the root info on. i a newb to all this rooting stuff, but want to expand and learn.
Click to expand...
Click to collapse
I am rooted on the stock 1.1. I use the ad hoc switcher (search these forums) when I need ad hoc to connect to my rooted Moto Droid with WiFi teather. If ad hoc is still not working with 1.2 then I will probably continue to use the switcher for the few times when I need it.
Still waiting on an auto-neuter for 1.2. When it is available, I will flash back to stock, upgrade to 1.2 and then auto-neuter 1.2. I used it for 1.1 and it was flawless.
If you are on stock, unrooted 1.2 then you might want to wait for the auto-neuter as well.
Ad Hoc is still broken. I had trouble also trying to use connectify (win 7 wi-fi sharing app)...my NC couldn't pick up the WPA2-PSK network. So no luck there either.
Ad-Hoc works for me without any modifications under 1.2 and sleep works without having to turn on and off the nook to get wifi to work again. I am in love!
Ad hoc now works fine with 1.2 -- just tried with with Wireless Tether and my Droid X.
Has anyone tried with the myWi from any iphone version?
Yes that's how I tether...it's working wonderfully with 1.2 no hack needed
botossi said:
Has anyone tried with the myWi from any iphone version?
Click to expand...
Click to collapse
You getting adhoc on MN or just stock 1.2?
jtxmobile said:
Ad-Hoc works for me without any modifications under 1.2 and sleep works without having to turn on and off the nook to get wifi to work again. I am in love!
Click to expand...
Click to collapse
Are you sure it is stock 1.2 and you are on a ad hoc network? It is still an android system that will not see ad hoc. I tested it today with windows wifi router on ad hoc and the nook would not see it.
My personal experience ... the ad hoc patched wpa_supplicant file on nookdevs.com and some xda forums works on all versions of nook color, stock mods or even honeycomb preview. But does not work on stock or rooted update 1.2. Apparently this is because the working os versions are using version 5 of wpa_supplicant and the patched verson is also version 5 ... nook color update1.2 however uses supplicant version 6 and no one has recompiled an ad hoc patched version 6 wpa_supplicant yet for the nook color as has been done for other phones and tablets on xda forums. While some people think they are connecting with phones via ad hoc, using version 1.2 of the nook, there phones are most likely generating aps in infrastructure modes and not ad hoc mode.
New, rooted 1.2 needs WPA supplicant fix for adhoc
At least in my experience. I bought my nc with the 1.2 already pre-installed. It would only recognize the infrastructure wifi. I have the droid 1. It does not have the option to become a WiFi hotspot as newer phones do (30$ through Verizon). With wireless tether/barnacle I've been able to connect through the droid as an adhoc network, but only after the wpa_supplicant fix. I use it every day this way, as there's no WiFi at my office.
BTW, it does go between my home wifi and my droid adhoc without having to make any additional hacks beyond the most basic one. It seems to recognize both easily, back & forth every day.
Rsptexas, just wanted to (respectfully!) be clear that the droid 1 is definitely adhoc, no question whatsoever. Though I'm aware people are getting confused about what their phone puts out. I can't recall which version of the supplicant fix finally worked, as I tried several. Don't give up on it folks, you can really get adhoc to work on 1.2
Final thing then I'll shut up: 'toolbelt' says the wpa supplicant fix in post 872521 on this forum has the version of the fix that works for the rooted 1.2 ( junior member, can't do links yet, sorry).
Just type the number of the post in the search box at the top of the page
I can verify that http://forum.xda-developers.com/showthread.php?t=872521 does work for Manual nootered 1.2. I did not even need to apply the change back to infrastructure.
There is a lot of false info. out there. Many people think their phones are running AdHoc when in fact they are running infrastructure. Many modern modern phones can do infrastructure, and some roots provide it for free.
My lil old Eris, definitely does not support it.
Now my Nook can connect through AdHoc.
~Leko