I need help in configuring settings for the tether. I have it connected to the pc but it seems no one else can even see it on the list of wireless networks and also when I start it says "started tether with errors" any special frequencys or somethin?
Related
So I'm using wireless tether app and it runs great on my PC. My PC's wifi card found my phone with no problem and connected to it. I gave my PC access control in the app and I can now access internet. However, when attempting to scan for networks on my playstation 3 it does not see my phone. I have assigned an SSID from within the app. Also, something else I noticed that was weird if anyone knows, I enabled wifi encryption but the setup methods threw me off with the Auto, iwconfig, and wpa_supplicant. I chose wpa_supplicant and gave the phone a password but when I connected my PC to the tether it never prompted me for a password (weird?). So if anyone knows what all this stuff means and also how I can get my playstation 3 to see my phone please let me know! Thanks in advance!!
Read this on another forum... but i believe it holds true...
"The PS3 will only connect to an Infrastructure Access Point. The wifi tether can only create an Ad-Hoc connection."
from this forum
You can however connect your PC/Laptop through wifi tether... then connect the PS3 to the PC with an ethernet cable... and internet connection sharing (ICS) enabled on that port.
Hi I want to use the wireless tether on my Galaxy S.
It seems like Wireless tether is the only software that turns off wifi then turns back on automatically after the tether (unlike Barnacle)
so it wanted to try it out.
but It looks like I can't get it working.
it says it's running but my IPAD can't detect its signal at all.
could someone please help me on this issue?
thanks
You should make sure that in the Mobile AP setting the "Hide my device" is unchecked.
for me, my computer didn't found the proper ip settings.
Any suggestions ?
I've got an EVO running CM6 stable with android-wireless-tether (pre7). I am able to pair/connect to my home PC by setting up a bluetooth PAN in Windows 7. I right click on my device, choose "Connect > Access Point" and it says "Connection Successful". The only thing I get now is "Identifying..." until I am stuck with the good ol' 169.xx... IP address.
I checked the log for the wireless tether app, and it shows:
Enabling NAT rules... done
Enabling IP forwarding... done
Tethering now running... done
error: SIOCSIFFLAGS (Cannot assign requested address)
I've done a little research on the error and tried a few suggestions (rebuild binary/config files, changing the default LAN IP in awt settings) to no avail.
I also tried disabling WiFi and just attempting to share the 3G connection which still isn't working out (same error). Can anyone help me out with this one? I've also tried awt pre8 with the same results.
I had same setup and problem. Started the supper user app and quit app. Powered down phone restarted phone. After restart WiFi tether worked fine. Don't know why .
Sent from my PC36100 using XDA App
Just turn on wireless teather and the go to access conections fine androidap and connect to that. Why do you have to use blue tooth am I missing something? Wireless teather is in the settings with CM6 so you dont need an extra app for teather?
Thanks for the suggestions. I tried opening/closing SU app and rebooting, got the same result.
The reason why I am doing it this way is because I have a PC with only a network card (not WiFi). It's about 30/40 ft. from my router. Rather than buying a wireless card or some cable, I'm connecting via bluetooth and sharing my phones WiFi connection.
I understand if I had a WiFi adapter I could just use the built in Hotspot feature, but if I had WiFi, I would rather connect directly to the router.
I'm definitely interested in this too. At work, we have a no-wireless router policy, and I don't really feel like firing it up and have a guy holding a Fluke wireless network analyzer come and find me.
Bluetooth is alright for what I need. Seems to almost be a kernel issue or something. Worked *perfectly* with my N1, even with pre8. The EVO with CM6 stable isnt working. Just as a note, the wifi portion works correctly.
Actually let me rephrase : The bluetooth section does work, I believe there might be an issue related to the dnsmasq dhcp server not being able to serve IPs. The 'Upload' section of the information panel changes, the Green Download section stays 0.00. The client never receives an IP address, and thats about it.
Logcat didnt really show me much of anything critical error-wise, I'm really hoping that I can downgrade/upgrade a kernel in order to support whatever hardware changes there were between the N1 and the EVO.
I checked the wireless router wifi mode, and it no longer works either. 'Started with errors' is what I get now when in the wifi mode. The built-android wireless tether works fine, but I either wish I could hide the ESSID or have a bluetooth option available.
It *seems* related to the kernel, but logcat doesnt mention anything about not being able to load a module, and the wifi-tether app doesnt have a txt log, or does it?
I happily used wireless tethering on my rooted Desire, so figured it wouldn't be too different doing exactly the same with my new One X.
I originally tried to use the stock tethering option - new phone, new firmware. I wasn't surprised when it didn't work. So I waited until I had routed my phone to try the app I used on my Desire - Wireless Tether. It didn't work. So I tried WiFi Tether for Root Users (the update of Wireless Tether). And FoxFi. And ClockworkMod Tether. And WiFi HotSpot/WiFi Tether. And Barnacle Wifi Tether...
When I activate Wireless Tether (or WiFi Tether), it begins tethering "with errors, check log". I open the log and find it's failed: Setting ad-hoc mode, Setting essid, Setting channel and (if active) Activating encryption (iwconfig). The rest did not fail, but of course I can't see it in the network list due to the essid failing.
I can only assume the other apps encounter similar errors. FoxFi simply says "WiFi mode has failed on your phone. Please use Bluetooth mode instead.". When I try Bluetooth mode: "Fail to activate. Internet not detected.", although there is definite data up and down stream.
I'm connected to the 'EE' network, formerly Orange (they've changed names), though that didn't affect my Desire when I tried it last week, it still worked. I'm running Android Revolution HD 9.7.2. I've tried creating a new APN with the same settings, but that didn't change anything.
Acelister said:
I happily used wireless tethering on my rooted Desire, so figured it wouldn't be too different doing exactly the same with my new One X.
I originally tried to use the stock tethering option - new phone, new firmware. I wasn't surprised when it didn't work. So I waited until I had routed my phone to try the app I used on my Desire - Wireless Tether. It didn't work. So I tried WiFi Tether for Root Users (the update of Wireless Tether). And FoxFi. And ClockworkMod Tether. And WiFi HotSpot/WiFi Tether. And Barnacle Wifi Tether...
When I activate Wireless Tether (or WiFi Tether), it begins tethering "with errors, check log". I open the log and find it's failed: Setting ad-hoc mode, Setting essid, Setting channel and (if active) Activating encryption (iwconfig). The rest did not fail, but of course I can't see it in the network list due to the essid failing.
I can only assume the other apps encounter similar errors. FoxFi simply says "WiFi mode has failed on your phone. Please use Bluetooth mode instead.". When I try Bluetooth mode: "Fail to activate. Internet not detected.", although there is definite data up and down stream.
I'm connected to the 'EE' network, formerly Orange (they've changed names), though that didn't affect my Desire when I tried it last week, it still worked. I'm running Android Revolution HD 9.7.2. I've tried creating a new APN with the same settings, but that didn't change anything.
Click to expand...
Click to collapse
I tried the other day to wifi tether my hox and couldn't but my old legend could, which is weird. I did mange to get it working by turning auto connect off on laptop and manually inputting the key. I ended up using usb tether in the end though, but only due to phone needing charging
USB tethering doesn't connect either...
Hi i used to create my own hotspots when i still had ADSL from my windows 7 machine. All my phones tablets other PC's would connect to it with no problem whatsoever.
I have found other uses for wifi networks that do not require an internet connection. Now seeing as i do not have an internet connection on my computer and some of these that i use only work if the network is not started by the phone, the hotspot has no internet connection.
This is where I think Android says screw the wifi without an internet connection lets use cellular to do things. The error it throws up is "Avoided Poor Internet Connection".
Is there a way to fix this without connecting the hotspot to an internet connection & without rooting or modding my M8?
slugger7 said:
Hi i used to create my own hotspots when i still had ADSL from my windows 7 machine. All my phones tablets other PC's would connect to it with no problem whatsoever.
I have found other uses for wifi networks that do not require an internet connection. Now seeing as i do not have an internet connection on my computer and some of these that i use only work if the network is not started by the phone, the hotspot has no internet connection.
This is where I think Android says screw the wifi without an internet connection lets use cellular to do things. The error it throws up is "Avoided Poor Internet Connection".
Is there a way to fix this without connecting the hotspot to an internet connection & without rooting or modding my M8?
Click to expand...
Click to collapse
Settings > Wifi > advanced
turn off auto-switch to mobile network
This should help
Another one in developer settings (however not ticked by default)
Settings > developer options
turn off aggressive wi-fi to cellular handover
These should help you if not already enabled. If they aren't then I'm afraid I don't know