Develop Bugs

[Q] Wireless tethering via bluetooth

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?

[Q] Can't tether on MIUI

Hello all
I seem to be having some problems with tether on MIUI. I've tried barnacle, open garden wifi, Wifi Tether for Root, and the built in MIUI tethering.
When I connect using wifi tether and the built in MIUI and try to go to a website on my laptop it says that the DNS lookup failed.
Any idea how to fix this?
Also, does MIUI tethering show up under tethering for my carrier?
Thanks!

I use wireless tether v 2.0.8 on miui just fine. Whether your carrier knows is open to much debate about custom kernels, deep packet inspection, traffic type, etc, but just try to use tethering responsibly.
http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_7.apk

[Q] Wifi tether won't work, rooted Evo 4G and Kindle Fire

I've searched several threads, and tried asking the KF forum, but had no luck figuring out what's wrong.
Both devices definitely 100% rooted with superuser working fine, permissions granted for all apps.
I installed wifi_tether_v3_1-beta14.apk on the phone. Here are the settings:
Device Profile: Evo 4G
Setup-Method: Initially I tried Softap (master).
That's the same as infrastructure mode, correct?
Default SSID (AndroidTether)
MSS Clamping checked
Routing Fix checked​
If I try to run it with these settings, I get a popup informing me the wifi hotspot started, but with errors. No devices (PC, kindle, etc.) can see it.
If I switch Setup-Method to Ad-hoc, it runs fine, no errors, PC can see it and connect to it. But KF can't connect to Ad-hoc... so lame.
So, I got ZT-180 Adhoc Switcher.apk for the kindle fire, to switch it to ad-hoc mode. Went to settings, told it to connect to AndroidTether. Switched to Ad-Hoc mode. It says "attempting to connect" ... after a minute it gives up and keeps retrying. The hotspot shows in the list of wifi networks, but it's hanging at "Obtaining IP address".
So, what's the issue? Infrastructure mode not working? Need to flash a custom rom? I read something about maybe needing a non-stock kernel? Upgrade or downgrade my radio?

I finally found a method that works, barely.
Wifi Tether (app listed above) failed.
Adhoc Switcher failed.
Wifi Hotspot Widget failed.
Elixir2's hotspot widget failed (connected but no surf).
The one that worked is free and doesn't even need root apparently: Foxfi.
I say it "barely" worked because even this has issues.
When I tried to create a password, it wouldn't connect.
But if I leave the password blank (no password) it does work.
http://foxfi.com/bin/
I just told it to start running, and left the SSID at the default (FoxFi98 I believe).

CreeDo said:
I finally found a method that works, barely.
Wifi Tether (app listed above) failed.
Adhoc Switcher failed.
Wifi Hotspot Widget failed.
Elixir2's hotspot widget failed (connected but no surf).
The one that worked is free and doesn't even need root apparently: Foxfi.
I say it "barely" worked because even this has issues.
When I tried to create a password, it wouldn't connect.
But if I leave the password blank (no password) it does work.
http://foxfi.com/bin/
I just told it to start running, and left the SSID at the default (FoxFi98 I believe).
Click to expand...
Click to collapse
Most f those other apps are using adhoc s which the kindle fire so t notice. What worked for me was to use the built in features of a custom ROM cm9 worked well for me using WiFi tethering and Bluetooth. In fact when I was using CM9 the data speeds were pretty much the same on the tablet and phone. It was real easy too just pulled down the notification tray and presses the toggle for WiFi AP every time after the initial setup.
Sent from my Nexus 7 using xda app-developers app

FoxFI won't work on HTC phones
CreeDo said:
I finally found a method that works, barely.
Wifi Tether (app listed above) failed.
Adhoc Switcher failed.
Wifi Hotspot Widget failed.
Elixir2's hotspot widget failed (connected but no surf).
The one that worked is free and doesn't even need root apparently: Foxfi.
I say it "barely" worked because even this has issues.
When I tried to create a password, it wouldn't connect.
But if I leave the password blank (no password) it does work.
I just told it to start running, and left the SSID at the default (FoxFi98 I believe).
Click to expand...
Click to collapse
Installed FoxFi from their website on my HTC EVO 3d. When I ran it, it told me that it was unable to run on HTC phones due to a Hotspot lock and advised me to use bluetooth instead. There is no bluetooth option on my Kindle Fire. I have tried several WIFI tethering apps all with no luck.:crying:

Absolutely can't get tethering to work. Tried everything.

Jellybean 4.1.1
T-Mobile SIM
Kernel 3.0.31 -g6fb96c9
Build JR003C
Rooted using Wug's Root Toolkit v1.5.2
Permanent CWM installation
Running Root Check Basic shows my device does have root access.
1. The network doesn't even show up on any devices with the following programs:
Wireless Tether for Root Users: 3.1 BETA14
Wireless Tether for Root Users: whatever is on the Market right now
OpenGarden
Barnacle
When I click to see the log it says it can't be found.
2. Using the built-in hotspot function means I'm able to see and find the tethering network, but after connecting to it there is never internet access. I ran the built-in hotspot with the other tether programs both installed and uninstalled.
Encryption and Passwords are all set to off for both methods.
EDIT:
I erased everything. The following is on a brand new install of rooted Jellybean. NOTHING else has been installed on it yet other than unlocking and rooting it via Wug's.
Built-in hotspot works. Will this incur tethering charges on T-Mobile?
Barnacle - WIFI: Failed to connect to supplicant: No such file or directory. Stopped unexpectedly! Can't see the
Wireless Tether for Root Users: 3.1 BETA14 - can't see the tether's wifi
Open Garden - right after granting SU permission it crashes. On re-open it says "unable in install... (couldn't catch it before it disappeared). When I go to view the log I get unable to open log file. File doesn't exist!

Have you tried foxfi? Worked when I had T-Mobile. Just moved to verizon and it still works.

jeffreystrazz said:
Have you tried foxfi? Worked when I had T-Mobile. Just moved to verizon and it still works.
Click to expand...
Click to collapse
FoxFi does not work. Error starting WiFi tether. Please use Bluetooth DUN. This happens both when I have the WiFi already turned on or off.
After uninstalling a host of somewhat recommended VOIP products I got at least the built-in Hotspot and USB Tether features to work: uninstalled AutoAir (always ensures at least one of either 3G or WiFi is on to intercept VOIP calls), Plane Mode Tweaker (allows WiFi to still work in airplane mode), Y5 Battery Saver (automatically connects to known WiFi access points. Turns off WiFi automatically otherwise.
I'm not sure which one of the 3 apps above is the culprit.
But basically: none of the 3rd party tethering apps work.
Only the built-in apps work, and now I'm very concerned that I will be charged for tethering on my T-Mobile prepaid $30/month plan.
EDIT: The built-in WiFi tether works but grinds to a halt when you turn the screen of the phone off. When the screen is on it works better. USB tethering doesn't seem to be affected. I can't get Bluetooth DUN to work because my Win7 computer can't find the necessary drivers for the Nexus.

Don't worry about T-Mo charging you for tethering. If they detect tethering your web browser will display a message linking you to their website. Just don't stream any video or download any obscenely large (300 mb+) files and you should be fine.

I'm in the same boat sort. I can. Get blue tooth tethering to work but not WiFi. Keeps deselecting the enable WiFi in settings automatically. Is this not possible thru verizon even when rooted?
Sent from my Galaxy Nexus using xda premium

[Q] Tethering on EE

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...