Database Develop

[Q] Wifi Tethering help please

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!

Wireless tether with EVO but not Epic. Why?

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?

CM7 Wi-Fi Encryption issues

I was having problem connecting to my Wi-Fi using CM7 RC1 & nightly's 1-3. I have a D-Link 655 using WPA/WPA2 PSK encryption. It would get stuck in a loop: scanning... connecting... disconnecting.... However, it would tether to my HTC Hero using WEP encryption and to open networks.
I googled and saw that others had similar issues with CM7 and tried some of their solutions (reboot router, set Nook Color Wi-Fi to never sleep) but it didn't work for me.
I went back to Cicada's Nookie Froyo 0.6.8 after each CM7 install because Wi-Fi was working great for me. I did some digging into 0.6.8 zip file and noticed that it has a "scripts" folder in "/system/etc/wifi/softap/" that is not in CM7 also there is an extra file called "tiwlan_drv.ko" in "/system/etc/wifi/" that is not in CM7.
I pushed the entire "wifi" folder from 0.6.8 to CM7 Nightly 3, did a chmod 644 on the individual files rebooted and I was able to connect to my wireless network. I am not really sure what worked specifically but I thought that I would share in case someone was having similar issues or could possibly explain what is going on.
I am really enjoying CM7 and I am grateful to everyone on XDA and to the CM guys for their hard work.
Wi-Fi Folder from Nookie Froyo 0.6.8 attached
MD5: 9A47EFD6C96DBA1074C341D98CC30D12

ringbolo said:
I was having problem connecting to my Wi-Fi using CM7 RC1 & nightly's 1-3. I have a D-Link 655 using WPA/WPA2 PSK encryption. It would get stuck in a loop: scanning... connecting... disconnecting.... However, it would tether to my HTC Hero using WEP encryption and to open networks.
I googled and saw that others had similar issues with CM7 and tried some of their solutions (reboot router, set Nook Color Wi-Fi to never sleep) but it didn't work for me.
I went back to Cicada's Nookie Froyo 0.6.8 after each CM7 install because Wi-Fi was working great for me. I did some digging into 0.6.8 zip file and noticed that it has a "scripts" folder in "/system/etc/wifi/softap/" that is not in CM7 also there is an extra file called "tiwlan_drv.ko" in "/system/etc/wifi/" that is not in CM7.
I pushed the entire "wifi" folder from 0.6.8 to CM7 Nightly 3, did a chmod 644 on the individual files rebooted and I was able to connect to my wireless network. I am not really sure what worked specifically but I thought that I would share in case someone was having similar issues or could possibly explain what is going on.
I am really enjoying CM7 and I am grateful to everyone on XDA and to the CM guys for their hard work.
Click to expand...
Click to collapse
Can you post a copy of that folder here so others can try it with out having to find rom to pull it from.

Same, please - would like to give it a try. Had only two fields to fill in on a EAP/MSCHAPv2 university network on stock rooted (username and pass), but lots more options and not working on CM7.

Well I've had no problem at all on multipel networks configurations, with CM7, and actually find it to be much more reliable than other installs. I have literally tried every possible config and they all work.
It doesn't make much sense for encryption to be responsible for the behavior your report (making and dropping connections).
1. Have you checked the network itself - e.g. use wifi analyzer, and look at the signal strength. You may be using a network that is in a crowded band, and adjacent devices may be trying to shout over each other (though the NC seems to generally be able to shout over my celphone). For instance, in my neighborhood almost everybody is on the default channels 1 and 6, which really cuts the range and signal strength of my wifi. Honestly you won't believe the improvement by switching to an empty channel.
2. Is you work network broadcasting over multiple channels? This is typical but it does mean that as you move around the building you will drop briefly as you switch from one router to another with the same SSID on different channels.
3. Have you installed any additional software that might be fighting with the system. For instance set CPU is now redundant - as the same functionality is built into CM7 and it will fight with the system if you install it. So you haven't installed any unecessary wpa_supplicant fixes, right? Or a profile manager? And you are not using a task killer, right?

I used a task killer last night and for the first time had problems with file explert connecting. After reinstall it started to work again. This was the only time I have had any problems with wifi.

bonobomidwest said:
Well I've had no problem at all on multipel networks configurations, with CM7, and actually find it to be much more reliable than other installs. I have literally tried every possible config and they all work.
It doesn't make much sense for encryption to be responsible for the behavior your report (making and dropping connections).
1. Have you checked the network itself - e.g. use wifi analyzer, and look at the signal strength. You may be using a network that is in a crowded band, and adjacent devices may be trying to shout over each other (though the NC seems to generally be able to shout over my celphone). For instance, in my neighborhood almost everybody is on the default channels 1 and 6, which really cuts the range and signal strength of my wifi. Honestly you won't believe the improvement by switching to an empty channel.
2. Is you work network broadcasting over multiple channels? This is typical but it does mean that as you move around the building you will drop briefly as you switch from one router to another with the same SSID on different channels.
3. Have you installed any additional software that might be fighting with the system. For instance set CPU is now redundant - as the same functionality is built into CM7 and it will fight with the system if you install it. So you haven't installed any unecessary wpa_supplicant fixes, right? Or a profile manager? And you are not using a task killer, right?
Click to expand...
Click to collapse
I've tried several different builds of Nook Froyo (SD/EMMC), Stock Nook Color 1.01/1.1.0 & deeper-blue's Honeycomb v01 and they all worked with my wireless connection. Laptop also works.
I will do a fresh install of a CM7 build (wiping system, cache, data), reboot and the first thing I try to do is connect to Wi-Fi and It would get stuck in at: scanning... connecting... disconnecting.... I've tried to login numerous times making sure the password is correct and nothing.
After giving up I would do a fresh install of Nookie Froyo 0.6.8 and try to access my Wi-Fi and it connects on the first try. As I said, I am not sure why coping the wifi folder works but it works.

Disregard my post, moving to another area of campus made it connect smooth as butter.

I have installed phiremod nook V3 to my nc, everything is ok,
except for the wifi connection.
My nc can't connect to any hotspot even my iphone 4
but it can connect to my router (linksys 54-TM the setting is G not mix mode).
I want to try it but I don't know how to copy the wifi folder you provided to my nook.
Is it the script like that:
adb push ??? /system/etc/
How about the script for chmod 644?
thx a lot!

I have neither Wi-Fi, not USB working now
I have exactly the same issue with the nightly build 8 (2011-02-27) when connecting to my D-Link DIR-655 with WPA2 encryption. My Nook with CM7 would not connect in a meter from a router. I have other wireless devices, like PSP, Cruz Reader, Acer netbook, etc. and all of them work just fine, likewise the same Nook with the original firmware. On the top of that now Nook does not connect via USB to neither XP nor Window 7, which was also working fine with the stock firmware. I followed the instructions from the wiki.

Add one more nook to the wifi problem list. I've tried every encryption method and can't get my nook to connect. The only way I could connect was in "Open" and thats not an option.

Add me to the list as well. I just installed CM7 nightly 12 and I can not connect to my network. It worked prior to installing CM7, ie. rooted stock on the Nook.
I am also running the Dlink DIR-655 and WPA2 encryption as my main router. I also have an Asus working as a repeater using the same SSID but with all other settings the same.
I rebooted the router and repeater and the nook and I wiped and reinstalled CM7. Nothing worked and that didn't work. I get the scanning, connecting, disconnected loop. Without a connection, I really can't do much so I'm going to have to find another rom.

Thanks for this thread. I was trying to figure out why Nookie Froyo and HCv4 worked for me, but not Phiremod...then I realized that Phiremod is CM7 based. I really liked the look of it, but I never REALLY got to try it out because of the stupid wi-fi issue.
The odd part is at my school, the network is "open." I'll have to try this out and post my results...At first I thought it was the WPA_supplicant file that was all messed up and I was gonna push a different one from Nookie but I got too frustrated.

Switching to tkip-only encryption worked. There seems to be an issue with aes encryption and cm7 (on build 13 now).
-via Nook Color.

Pushing all the files worked for me. Don't push softap...you don't need to...
Just push the tiwlan_drv.ko, tiwlan.ini, and wpa_supplicant.conf files. You should be golden.

hongkongdisney said:
I have installed phiremod nook V3 to my nc, everything is ok,
except for the wifi connection.
My nc can't connect to any hotspot even my iphone 4
but it can connect to my router (linksys 54-TM the setting is G not mix mode).
I want to try it but I don't know how to copy the wifi folder you provided to my nook.
Is it the script like that:
adb push ??? /system/etc/
How about the script for chmod 644?
thx a lot!
Click to expand...
Click to collapse
Are you still having trouble connecting to your iPhone? I am using mywi on it and trying to tether using mywi kills my NC 's wifi completely for all wifi networks.

I am not sure what it was on my DIR-655 but i set it to B & G only and it solved the connection issues for me. I am not sure if it is the encryption our CM7 NC's are having issue with or the Wireless N.

Was on CM7 12 and now on CM7 13. Been having problems with wifi all along. Thanks for this post. Will try when I get back today

Having same issue with Wireless N
I too was having issues with CM7 and not connecting to my D-Link DIR-615 Wireless N network (WP2 with AES).
I have already gone back to stock then autonooter 3.0... but that left me with very low usb transfer speeds (0.5 or less kb).
I will have to try this fix out.
Thanks for the post!

ringbolo said:
I was having problem connecting to my Wi-Fi using CM7 RC1 & nightly's 1-3. I have a D-Link 655 using WPA/WPA2 PSK encryption. It would get stuck in a loop: scanning... connecting... disconnecting.... However, it would tether to my HTC Hero using WEP encryption and to open networks.
I googled and saw that others had similar issues with CM7 and tried some of their solutions (reboot router, set Nook Color Wi-Fi to never sleep) but it didn't work for me.
I went back to Cicada's Nookie Froyo 0.6.8 after each CM7 install because Wi-Fi was working great for me. I did some digging into 0.6.8 zip file and noticed that it has a "scripts" folder in "/system/etc/wifi/softap/" that is not in CM7 also there is an extra file called "tiwlan_drv.ko" in "/system/etc/wifi/" that is not in CM7.
I pushed the entire "wifi" folder from 0.6.8 to CM7 Nightly 3, did a chmod 644 on the individual files rebooted and I was able to connect to my wireless network. I am not really sure what worked specifically but I thought that I would share in case someone was having similar issues or could possibly explain what is going on.
I am really enjoying CM7 and I am grateful to everyone on XDA and to the CM guys for their hard work.
Wi-Fi Folder from Nookie Froyo 0.6.8 attached
MD5: 9A47EFD6C96DBA1074C341D98CC30D12
Click to expand...
Click to collapse
How did you push the file to your nook? Cwr and install zip? If not, how would you install it? The change from aes encryption to tkip encryption worked for now but I would love to be able to get on aes Encryption if possible. Thanks
Sent from my NookColor using Tapatalk

Another one with the DIR-655/WPA2 issue running with CM7. Anytime I enable N then I loose the wireless connection. Setting the DIR-655 to G makes everything connect.
On another network I run WPA2 on a Cisco e2000 and that connects without issue on N. The combination of DIR-655-WPA2-Wireless N seems to be the issue
Tolax

Tethering iPhone MiWi to CM7 NC

Just wondering if anyone here is able to tether their iPhone to the NC using MyWi and an NC on CM7?? Everytime I try, it kills my wireless on my NC to the point that it won't connect to any network or even scan for available networks for that matter.
If you're able to make it work, let me know how you did it.

I use MyWi to tether with NC with Eclair, so obviously it's possible, not sure why CM7 freaks. Is it because it's ad hoc?

I had the problem. Try the solution in this post.
It worked for me.

Thanks. I'll have to give it a go. I turned off the WEP security and it worked, so it's something with the WEP security. Also, the new version of mywi doesn't broadcast as adhoc. It is infrastructure.

[Q] Does WiFi Ad Hoc Mode work with 1.2?

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