Related
since updateing to FRF83, wifi tether seems to have been slowed down.
has this been done to keep american networks happy?
Can anyone else verify this? I'll check when I get home... but that would suck.
I just tested it. I can not confirm this issue. My tether speeds are as fast as they always are.
No issues at all here, worked great!
Same here, my WiFi tether speeds are right in line with my N1's 3G speed tests.
well my tether is working but my hotspot is not... >: l
Everything is happy happy joy joy on my end
WiFi Tethering not Changed
No changes have been made to the WiFi tether however your speeds can be hindered by network traffic and a number of other issues. Even a microwave oven near by will interfere with speeds or something as simple as an application checking for updates in the background on your computer.
Best thing, try again at another time or location. It helps to test often to get an idea of the fastest speeds you may see, when and where you got the best results.
I had this problem as well. Here's what I did that fixed it:
Change the security to Open. After that, try to connect to your phone. If you're able to connect, change back to WPA and it should work.
I noticed that the password I set before the update had quotes around it, so I wonder if that was the problem...
I've got an AT&T n1 and I am using it with Vodacom in Tanzania. I'm now running frf83 and internet on my phone works but I am unable to tether. The computer can see the hotspot and connect, but there are DNS problems. My tech friend helped me but he was unable to make it work and concluded that he could ping the internet fine but DNS wouldn't work, not even open DNS. I dunno, anyone have this problem or know a fix? I would be grateful.
crazedwowo said:
I had this problem as well. Here's what I did that fixed it:
Change the security to Open. After that, try to connect to your phone. If you're able to connect, change back to WPA and it should work.
I noticed that the password I set before the update had quotes around it, so I wonder if that was the problem...
Click to expand...
Click to collapse
I'm using open and it still doesn't work but thanks for your help.
Im stock and on tmobile and its working great for me, hooked my buddy's iphone just now to test it
It does not work with me . i tried on FRF50 work fine but on FRF83 no wifi at all
Does not work for me ether
I even factory reset my phone but wifi tether doesn't work, something to do with DNS.
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 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
Sooooo i just happened to find a wifi tether that works for the revo and heres the link http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-beta1.apk
i dont know who developed it or anything i just found it.....
use at your own risk...
click thanks if it saved u LOADS of time haha
rodney323 said:
Sooooo i just happened to find a wifi tether that works for the revo and heres the link http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-beta1.apk
i dont know who developed it or anything i just found it.....
use at your own risk...
click thanks if it saved u LOADS of time haha
Click to expand...
Click to collapse
Does this circumvent the pay-to-tether method?
Yep dont need to pay for tether
Sent from my VS910 4G using XDA App
Got to test it out with my nook today - it worked great!
its not working for me. My buddy doesn't see it on his Evo 4G wifi.
Just tested it out and it worked great. No 4G in my area until October so I was running You Tube, which blocked here at work, over the tether and it it was really smooth. The app was painless to use, no configuration at all just started it and gave it SU access and off I went. My laptop connected right up.
Nice app/find.
rmendez19 said:
its not working for me. My buddy doesn't see it on his Evo 4G wifi.
Click to expand...
Click to collapse
im sorry to hear that but as i mentioned i didnt create it soooo ionno lol
I know most phones can't see the tether network for some reason or another
Sent from my VS910 4G using XDA App
FYI-> I went to tether today and the 4G built-in app expired so i tried my restored wifi tether from my dInc.
it worked.
4g and 3g tested, both working.
not sure why this app didnt work before...
decrapped rom
I believe the reason most phones can't see it is because it creates a Wifi hotspot in Ad-hoc mode and not Infrastructure mode like most Wifi routers do. Android phones cannot connect to an Ad-hoc network, at least I haven't found one that does.
If you connect to this network from a computer you'll usually also see it listed with Ad-hoc mentioned or a different icon of some sort.
I have noticed that Apple's products can connect to an Ad-hoc network. I'm not sure why this limitation exists on Android handsets, it's quite annoying.
Most of the "official" carrier Wifi hotspot's do support Infrastructure mode, so that's why you can connect when using one of those hotspot app's.
HereOnTheHill said:
I believe the reason most phones can't see it is because it creates a Wifi hotspot in Ad-hoc mode and not Infrastructure mode like most Wifi routers do. Android phones cannot connect to an Ad-hoc network, at least I haven't found one that does.
If you connect to this network from a computer you'll usually also see it listed with Ad-hoc mentioned or a different icon of some sort.
I have noticed that Apple's products can connect to an Ad-hoc network. I'm not sure why this limitation exists on Android handsets, it's quite annoying.
Most of the "official" carrier Wifi hotspot's do support Infrastructure mode, so that's why you can connect when using one of those hotspot app's.
Click to expand...
Click to collapse
It is because in Ad-Hoc mode there is no server assigning it an IP Address like you get with the infrastructure mode found in routers and other devices. You have to make sure that all the devices are configure with matching IP addresses (addresses in the same subnet and class), gateways, and subnets. Ad-hoc is generally a manually configured network where you configure each device. It is what we used to call peer to peer in the old days.
The app listed in this thread works great. Just to check ppl are turning on the wireless radio first? I know its a simple thing but you would be surprised how many times ppl forget that step.
I've been fighting with this app since I got it. I know the problem is with my laptop, but when I had the Inc. i could connect with no problems at all. I see the signal from the phone in my wireless list, just as an adhoc connection. I just can't get my computer to ever connect to it.
I know the error lies somewhere between the keyboard and chair, but if anyone has any ideas on what I should try, plz let me know.
Running. Win7 Ultimate 64bit
Thanks all!
it works!
The first WiFi device I tried to connect was my wife's phone (Samsung Captivate) but her phone would not find WiFi Tether signal.
But my rooted Nook Color did and it works fine.
HereOnTheHill said:
I believe the reason most phones can't see it is because it creates a Wifi hotspot in Ad-hoc mode and not Infrastructure mode like most Wifi routers do. Android phones cannot connect to an Ad-hoc network, at least I haven't found one that does.
If you connect to this network from a computer you'll usually also see it listed with Ad-hoc mentioned or a different icon of some sort.
I have noticed that Apple's products can connect to an Ad-hoc network. I'm not sure why this limitation exists on Android handsets, it's quite annoying.
Most of the "official" carrier Wifi hotspot's do support Infrastructure mode, so that's why you can connect when using one of those hotspot app's.
Click to expand...
Click to collapse
Interestingly enough, I was able to use this quite well on my Nook Color running CM7 when they had 4g turned on in my area (for one day). After they switched it back off, I have been able to connect, but the data doesn't seem to go.
I don't get the correlation, because I was even able to tether it at work where I only had 3g, but the second they turned 4g off, it wouldn't tether from 3g. Frustrating.
I just want to note I am using it on a 3G connection. They have not activated 4G in my area.
I figured out what was wrong. The problem was that I was authorizing my nook exclusively, and while this works, it doesn't appear to be a permanent solution. You have to redo it occasionally when you reconnect.
Sent from my NookColor using Tapatalk
having issues with this app, laptop connects and some sites work, speak easy speed test reports very nice speeds, but for whatever reason several sites will only partial load and then timeout. Forum based websites work fine and it seems youtube works also. Not sure why others won't.
I am trying to connect my laptop running Windows Vista Home to my LG revo. I can see the AndroidTether ssid and it is ad hoc. But when trying to connect it just sits there trying then has a message that "connection is taking longer than usual" then it gives a timeout. I can get a connection with my desktop running Vista Ultimate. Anybody know what setting in my Windows laptop that may have to be changed? I setup my wireless adhoc device props to match the LG revo settings. I found a new driver for the wireless network card and it connected just fine...DOH!
Just to mention for some people
If you still can't connect try checking if u made a static ip for your network adapter....just putting this out there
Sent from my VS910 4G using XDA App
OK. So we need a static IP address? And for the other poster.. how did you match the settings to the Revolution? I have been fighting this wireless tether since I rooted. All help and comment are awesome! Thanks guys.
Sent from my VS910 4G using XDA Premium App
I'm tring to run WiFi tethering software so I can get internet access on my Toshiba Thrive Tablet. I have an original Motorola Droid phone. I rooted the phone and when I run any WiFi tethering software it's broadcasting in Ad-Hoc mode. For some reason my Tablet can't see any Ad-Hoc networks. So, this is a big problem for me.
My friend has a Droid Incredible and he has a custom ROM installed on his phone and his phone doesn't broadcast in Ad-Hoc mode, his phone broadcasts with a regular WiFi connection. Why does his work that way and mine only works in Ad-Hoc? Do I have to install a custom ROM to get mine to work in regular WiFi mode? If so, which ROM is recommended?
Another solution is to get my Tablet to recognize Ad-Hoc networks. Is there some way to do that also?
Thanks so much for all your help and time!
Which tethering app are you using?
Both Wireless Tether and the 2.2 default 3G Hotspot app are broadcasting in infrastructure mode.
I remember my Wii not being able to connect to a hotspot created via Wireless Tether - did'nt try 3G Hotspot yet...
Well, I've tried different Hot Spot Apps and they are all the same. I used the same app on both my Droid phone and my friends Incredible phone. His phone worked in Infrustructure and mine worked as Ad-Hoc. I don't know what default 3G Hostspot app you are talking about. My phone didn't come with any. From what I was reading it has to do with the hardware of the phone. Since my phone is so old it only supports Ad-Hoc and the newer phones support Infrustructure. I think that's what people are saying.
I've been reading there is a way to make Tablets see Ad-Hoc but I can't find any information on how to do it with the Toshiba Thrive Tablet. I guess there are different patches and you need to find the right version that's compatible with your Tablet.
So, the only solutions I can see is get a newer phone that supports Infrustructure or to find the patch that works with my Tablet and lets it see Ad-Hoc.
Thanks!
Eiertschik said:
Which tethering app are you using?
Both Wireless Tether and the 2.2 default 3G Hotspot app are broadcasting in infrastructure mode.
I remember my Wii not being able to connect to a hotspot created via Wireless Tether - did'nt try 3G Hotspot yet...
Click to expand...
Click to collapse