So I've been using a wifi tether app that's convenitely named "WiFi Tether" for over a year now. Recently my phone started bugging out, so I wiped it (backed up my SDcard) and installed a new ROM and reinstalled WiFi Tether. Now I start up the app and it says it started with errors, please check log. I checked, it had like 6 errors, tweaked the settings, now I'm down to one error. That's the AdHoc setup failed.
I changed it to Softap and started it again and had 5 or 6 errors, went back to AdHoc, still get the same error and I'm frustrated. I've changed channel frequency's, enabled/disabled security, tweaked NAT settings, and still get that ONE error that's preventing me from tethering.
Download wifi tether for root users from its Google code page, version 2.0.7
Related
I have flash the rom I9000XWJM7. and using the OCLF from the appbrain.
i have tried to use Samsung Apps when running on Wifi or data. But both failed.
before the flash, i can access samsung apps.
Error msg i get is "Network unavailable"
authmn said:
I have flash the rom I9000XWJM7. and using the OCLF from the appbrain.
i have tried to use Samsung Apps when running on Wifi or data. But both failed.
before the flash, i can access samsung apps.
Error msg i get is "Network unavailable"
Click to expand...
Click to collapse
Try to setup APN for your provider.
APN setup is done - i think?
i am able to download from appbrain, market.
able to surf the net.
I had a similar problem.
It was the APN settings. Looked like my mobile provider has blocked certain Samsung ports. When I changed APN settings (proxy and port) I was able to connect to the Samsung applications.
i tried port 8080 and 8081. but its still not working.
Btw it doesnt even work on Wifi. wifi dont need to configure any ports right?
I've searched several threads, but can't figure out what I'm doing 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.
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 attempt to run it with these settings, I get a popup informing me the wifi hotspot started, but with errors. The log just says most of the wifi steps failed, I can post details if needed. I don't think it's really running - no upload/download indicator showing at the bottom of the app. My PC can't see the hotspot.
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).
Error code: ERR_PROXY_CONNECTION_FAILED
Running Nexus 7 2013 (2nd Gen) WiFi, kitkat, unlocked,
Wifi shows strong connection, detailed error message,
Unable to connect to the proxy server, A proxy server is a server that acts as an intermediary between your device and other servers.
Your system is configured to use a proxy, but Google Chrome cannot connect to it. All my other wifi devices, phones and laptop connect OK.
If you use a proxy server...
Check your proxy settings or contact your network administrator to make sure the proxy server is working. (end of error mssg)
This is beyond me, I was using wugfresh to root, got it unlocked but never got it to root, while doing so, there are two kitkat os options, and when I finally tried the second one, this happened. All else works fine, just this wifi connection error, I reset wugfresh to the first kitkat os version and tried rooting again but no change in proxy error. Not blaming wugfresh, just explaining what I was doing. Googled for a solution but they all refer to Chrome on a PC, I cannot find proxy setting info on the Nexus 7 2013 wifi.
I've tried all the obvious, shut off and restart, plus, wiped and factory restore to original.
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
atombombzero said:
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Click to expand...
Click to collapse
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
I am running a rooted stock with a stock recovery. In installing the hotspot hack zip, does this require TWRP or CWM recovery??
Aronmorg said:
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
Click to expand...
Click to collapse
I am just a UNIX admin so I know enough to be dangerous. I am no dev.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
Also, I can't find the hack of which you speak. I scoured the forums today and found nothing.
I'm running synergy 4.3 rom and native hotspot works no problem. .
I just got my wife's s4 to use the native hotspot by downloading the service.odex and .jar with stock rom. I don't know if something like that is available with the note 2. I see that someone using the synergy 4.3 rom got native hotspot to work, but is that possible with stock rom.
I have a Samsung Galaxy Tab 3 GT-P5210 and have installed TWRP and cm-12.1-20150505-UNOFFICIAL-p5210.zip together with open_gapps-arm-5.1-stock-2016-02013, and all was ok. Now about 2 weeks ago although there was a wifi signal, there was an exclamation mark against it and no internet connection.
I tried to sort that out with no luck and then decided to start over again. Using TWRP, I wiped the relevant folders, then re installed cm-12.1-20150505-UNOFFICIAL-p5210.zip again. When I rebooted into the sytem, there were minimal icons, but no play store and a browser that was locked to a particular website which it couldn't load.
WiFi was working ok now, so I then installed the open_gapps-arm-5.1-mini-20160203. I then rebooted into system and google maps wasn't working, and I had the exclamation mark back again on my wifi connection. I did try the stock version of open_gapps, but there were no google keyboard, no maps and no text to speach.
I had an idea of installing the firefox apk file but it wouldn't work giving and error: 'firefox won't run on this device (x86, 22)'
There is also no internet wifi connection when just install the bare bones OS. It's there at the first boot, but on a subseqent boot there is no internet
Update: I was checking some settings in my router and found that my GT-P5210 tablet was blocked in the MAC filter list. I removed it from the list and now it can connect to the net.
I installed this : cm-12.1-20150505-UNOFFICIAL-p5210.zip
then this: open_gapps-x86-5.1-micro-20160528.zip from here: http://opengapps.org/
The tablet runs fairly well except sometimes it is unresponsive, but that is something else to look at.