4.2 GNEX OTA breaks Wifi Tether's ability to Configure and Start AP

[GoogleCodeExporter]

Which device (manufacturer, type)?
Samsung Galaxy Nexus (from Google Play; no carrier)

Which firmware is installed?
4.2

What version of wireless tether are you using?
3.2-beta2

What steps will reproduce the problem?
1. Install 4.2 OTA on unbranded GNEX
2. Click the tethering activation icon
3. Tethering starts "with errors" - specifically, log shows failures at the 
"Configuring AP" and "Starting AP" stages. All other launch stages succeed.

What is the expected output? What do you see instead?
I expect tethering to start without errors. I see errors that prevent any 
device from seeing or connecting to the wifi broadcast.

Please provide any additional information below.
Worked fine on 4.1.2

Original issue reported on code.google.com by adej...@gmail.com on 15 Nov 2012 at 9:58

Attachments:

• Screenshot_2012-11-15-16-57-25.png

[GoogleCodeExporter]

Same problem for me.
Here is the logcat output, hope this helps.

Original comment by adrien.m...@gmail.com on 16 Nov 2012 at 6:18

Attachments:

• logcat.log

[GoogleCodeExporter]

Still not working on v3.3-pre1

Original comment by parrothe...@gmail.com on 20 Nov 2012 at 8:36

[GoogleCodeExporter]

With 3.3 update I'm now also getting a failure on "Enabling MSS Clamping" in 
addition to the failures I had before.

Original comment by adej...@gmail.com on 20 Nov 2012 at 8:44

[GoogleCodeExporter]

Well with v3.3-pre1, if you select the Setup-Method as "Netd (master)" then all 
the previous errors of "Configuring AP" and "Starting AP" are gone, the only 
error is "Enabling MSS Clamping" which is a new error as mentioned in the last 
comment.  Even so, you still cannot see/connect to the AP

Original comment by parrothe...@gmail.com on 20 Nov 2012 at 9:59

[GoogleCodeExporter]

Getting same error on Verizon GNEX 4.2

Original comment by scottbau...@edinarealty.com on 24 Nov 2012 at 12:34

[GoogleCodeExporter]

tested right now v3.3-pre2 on GNEX 4.2 (custom AOSP rom) and still doesn't 
work; I setted device profile to Samsung Galaxy Nexus GSM and I tried different 
setup method. I usually get 3 errors: 
- starting AP
- configuring AP
- enabling MSS clamping

with method "netd" AP errors desappear but I'm not able to see/connect any 
device
As reported before, it was working on Android 4.1.2

Original comment by orlandel...@gmail.com on 27 Nov 2012 at 3:23

[GoogleCodeExporter]

Please try ...
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_3-pre2.apk

And you might need to activate the option "WiFi-driver reload 2" from 
app-settings.
Not sure if that works but maybe not worth to try ...

Please note: Superuser.apk (to grant superuser-permission) is known (got 
reports) to not properly work with this option/and or android 4.2 in general. 
Use SuperSU instead:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu

Original comment by harald....@gmail.com on 27 Nov 2012 at 8:35

[GoogleCodeExporter]

re: harald

No dice.

Still getting the exact same errors:
- starting AP
- configuring AP
- enabling MSS clamping

Original comment by adej...@gmail.com on 27 Nov 2012 at 8:42

[GoogleCodeExporter]

Galaxy Nexus 4.2

Errors on:
- Starting AP
- Configuring AP
- Enabling MSS Clamping

Tried changing the following after the errors above:

Device-Profile = Samsung Galaxy Nexus (GSM)
Setup-Method = Netd(master)
WiFi-driver reload = Enabled
Routing Fix = Enabled

Result = NO ERRORS, However the tether isn't visible at all or detected by any 
laptops/tablets/etc... 

Original comment by zamudio0...@gmail.com on 28 Nov 2012 at 2:20

[GoogleCodeExporter]

Updated to JellyBean 4.2.1 cleared app data on Wireless Tether for Root users, 
installed v3_3-pre2  Still not working. (yes I'm using SuperSU)

Original comment by parrothe...@gmail.com on 28 Nov 2012 at 4:21

[GoogleCodeExporter]

Wi-Fi tethering issues on 4.2 make me headache deeply...

My PS Vita couldn't catch the stock tethering and wifi tether (whatever new or 
old version) couldn't work anyway...

Even updated to 4.21 are could help anymore...

Original comment by TCSdisa...@gmail.com on 28 Nov 2012 at 9:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok, well I manage to get tether work and visible for Laptop, Tablet & PS Vita. 

(According to the "About" menu in Wi-Fi Tether)
Version of Wi-Fi Tether = 3.2-beta2-modv5 ***Synergized*** 

Settings:

Device-Profile = Samsung Galaxy Nexus (GSM)
Setup-Method = Native Framework Tether
Encryption = Works both ON & OFF
Don't disable Bluetooth = Unchecked
Enable Access-Control = Checked (but seems it isn't working)
Keep Alive = Checked
Routing Fix = Enable

The only error on log is "Disabling NAT rules" but it still works! You may want 
to Re-Install binaries/configs by hitting the option button on top right corner 
in the settings menu. Also try to reboot phone, seems if you play around you 
can leave your phone in a weird state.

:) Glad I got this going on, played some COD Black Ops 2 on Vita with Tether & 
I gotta say no lag at all. 

Galaxy Nexus 4.2
Build = JOP40C

Original comment by zamudio0...@gmail.com on 28 Nov 2012 at 3:23

[GoogleCodeExporter]

sorry zamudio, where is "3.2-beta2-modv5 ***Synergized***" version?? in 
download page there is only 3.2-beta2 ... I tried with that and used your 
settings but no dice ...
on setup-method I can't fine the "native framework tether" option ... 
(I'm running paranoidandroid 2.99 beta5, Android 4.2.1)
thanks

Original comment by orlandel...@gmail.com on 28 Nov 2012 at 3:40

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

@ orlandel

Here is the direct link for the download:
http://www.androidfilehost.com/?fid=9390195663897100312

I found the apk from surfing the forums @ Xda-Developers
http://forum.xda-developers.com/showthread.php?s=5155cbb3ec245e33d92c746af1d5b62
9&p=34601944

Post #32 has the link to the APK as well, same as the direct link for download.

Original comment by zamudio0...@gmail.com on 28 Nov 2012 at 3:54

[GoogleCodeExporter]

Ok a little update from my comment #13.

I hadn't reboot my phone since yesterday when I was playing on the Vita with 
Tether from my phone. It wasn't working properly. I just tried connecting to 
the tether from my Ipod Touch and it detected it and connected, but internet 
failed! So, I turned off Tether & reboot the phone and started tether again. 
Now the ipod touch reconnect and I tried the web browser I am able to surf the 
internet and such.

If anyone has questions let me know. I would like to help the community out.

Running Stock Rooted/CW Recovery
Galaxy Nexus

Original comment by zamudio0...@gmail.com on 28 Nov 2012 at 3:55

[GoogleCodeExporter]

All that 3.2-beta2-modv5 ***Synergized***  does is enable WiFi tether under 
Settings - Wireless & Networks - More... - Tethering & Portable Hotspot - 
Portable WiFi hotspot.  That doesn't help me since I can already do that on my 
own..  It works when I use the built in tethering option on most devices, yet 
some devices like my chromebook are unable to connect... It seems the WiFi 
tethering in 4.2 & 4.2.1 has bugs.  I'm not the only one having issues with it

Original comment by parrothe...@gmail.com on 28 Nov 2012 at 4:23

[GoogleCodeExporter]

@ parrothe - In my scenerio: If I use the internal WiFi tether (built-in) it 
doesn't get picked up by the PS Vita, my laptop, tablet or Ipod Touch. I have 
to use Wi-Fi Tether to get it working properly and get picked up by all 
devices. 

I don't have a chromebook so I have no way to troubleshoot. The only way would 
be to go to my local bestbuy store and tried/test it there. 

Original comment by zamudio0...@gmail.com on 28 Nov 2012 at 4:27

[GoogleCodeExporter]

@zamudio
with APK you linked, I don't solve my problem:
ok, it uses Native Framework Tether and I can see both notification icons: the 
one related to wifi tether app  and one related to the native tether (built 
in), so my laptop connects to the phone using native tether ... but my problem 
is that with native tether I'm not able to access the internet, and that's the 
reason why I was searching  to use wifi tether instead ...

the problem comes from my carrier (Vodafone Italy) that in some way 
automatically changes the APN when I start built in wifi tether ... this new 
APN charges my bill with additional costs so I asked to the carrier to disable 
it ... so I started using wifi tether app that allowed me to tether using my 
default APN and avoid additional costs ... 

Original comment by orlandel...@gmail.com on 28 Nov 2012 at 4:29

[GoogleCodeExporter]

@orlandel - Let me see what else I can dig up for Vodafone...

I'm in U.S. and have T-Mobile. They don't like Tethering from my phone & have 
manage to block my internet if I tether, however using the wi-fi tether + 
fallback enables me to use tether, even though Wi-Fi Tether shows on the 
download/upload 0 all the time, but I am actually able to navigate through the 
internet/etc..

Original comment by zamudio0...@gmail.com on 28 Nov 2012 at 4:41

[GoogleCodeExporter]

@zamudio0 see when I use the built-in tethering, it works great for my laptop, 
my brothers laptop,my Logitech Revue, and a couple other computers I've tested 
it on... just not my ChromeBook (not since 4.1.1) I've seen others complain it 
doesn't work for them on select devices too.  I have Verizon but I'm running a 
AOSP 4.2.1 ROM where the dev has enabled free tethering, which works on all my 
devices... yet my ChromeBook won't even connect to it at all, its not an issue 
of the internet not working. I've tried the native framework on 3.2-beta2-modv5 
***Synergized***  and the fallback tethering on 3_3-pre2... they don't help

On another note... When I select "Fallback Tether" on v3_3-pre2 it requests SU 
for some reason...  even though it says its available for non-root users.  
Either way, it doesn't even work, I get the same errors with or without 
Fallback Tether enabled, even when I disable WiFi Driver reload and change to 
Samsung Galaxy Nexus CDMA/LTE

Original comment by parrothe...@gmail.com on 28 Nov 2012 at 5:31

[GoogleCodeExporter]

I'm having the same issue with 4.2 and 4.2.1. I had to revert to 4.1.2 to get 
it to work again. 

Original comment by danielsh...@gmail.com on 6 Dec 2012 at 8:44

[GoogleCodeExporter]

im experiencing the same issues with 4.2.1 (tethering not working at all 
regardless of what settings i attempt - and with the same three 
- starting AP
- configuring AP
- enabling MSS clamping
 issues on the latest beta) however i don't think  danielshs solution is a viable one since any new revisions of android will likely continue to perpetuate whatever changes caused this issue to start with

Original comment by Methos...@gmail.com on 8 Dec 2012 at 4:41

[GoogleCodeExporter]

The application will attempt to mount the file system /system write (rw) to 
copy the binary file but with Android 4.2 does not work anymore the command 
"mount -o remount, rw / system"

Original comment by fabio.gr...@gmail.com on 13 Dec 2012 at 3:11

[GoogleCodeExporter]

I enabled "Full Content Logging" for WifiTether v3_3-pre2 using SuperSU; below 
is the log (may be one or two typos, though I checked it twice):

/data/data/com.googlecode.android.wifi.tether/bin/tether start
about to run: [/system/bin/ndc softap stopap]
200 0 Softap operation succeeded
500 0 Softap Unknown cmd
about to run: [/system/bin/ndc softap stop wlan0]
about to run: [/system/bin/ndc softap fwreload wlan0 AP]
200 0 Softap operation succeeded
about to run: [/system/bin/ndc softap start wlan0]
500 0 Softap Unknown cmd
about to run: [/system/bin/ndc softap set wlan0 wlan0 AndroidTether open none 1 
0 8]
Lost connection to Netd - did it crash?
about to run: [/system/bin/ndc softap startap]
Error connecting (Connection refused)
about to run: [/system/bin/ndc interface setcfg wlan0 192.168.2.254 
255.255.255.0 up]
400 0 Failed to set prefixLength (Success)
about to run: [/system/bin/ip rule add to 192.168.2.0/24 lookup main priority 
50]
about to run: [/system/bin/ip route flush cache]
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -N 
wireless-tether]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run [/data/data/com.googlecode.android.wifi.tether/bin/iptables -F 
wireless-tether]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -F 
FORWARD]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -t 
nat -F POSTROUTING]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -t 
nat -F]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A 
wireless-tether -m state --state ESTABLISHED,RELATED -j ACCEPT]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A 
wireless-tether -s 192.168.2.0/24 -j ACCEPT]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A 
wireless-tether -p 47 -j ACCEPT]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A 
wireless-tether -j DROP]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A 
FORWARD -m state --state INVALID -j DROP]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -A 
FORWARD -j wireless-tether]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -t 
nat -I POSTROUTING -s 192.168.2.0/24 -j MASQUERADE]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/iptables -I 
FORWARD -s 192.168.2.0/24 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS 
--clamp-mss-to-pmtu]
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: no such file or directory
protoent* get protobyname(char const*)(3) is not implemented on Android
iptables: No chain/target/match by taht name
about to run: [/data/data/com.googlecode.android.wifi.tether/bin/dnsmasq -i 
wlan0 --dhcp-authoritative --no-negcache --user=root --no-resolv --no-hosts 
--server=8.8.8.8 --server=8.8.4.4 --dhcp-range=192.168.2.100,192.168.2.108,12h 
--dhcp-leasefile=/data/data/com.googlecode.android.wifi.tether/var/dnsmasq.lease
s --pid-file=/data/data/com.googlecode.android.wifi.tether/var/dnsmasq.pid]
about to run: [/system/bin/chmod 666 
/data/data/com.googlecode.wifi.tether/var/tether.log]
script result was [t]

Original comment by parrothe...@gmail.com on 13 Dec 2012 at 6:44

[GoogleCodeExporter]

I repeat, the problem is the file system that is mounted in writing, in Android 
4.2 "mount-o remount, rw /system" by mistake, it can be seen from the log that 
are not found some commands
with this problem, the application can not copy some files

Original comment by fabio.gr...@gmail.com on 14 Dec 2012 at 8:14

[GoogleCodeExporter]

Hi Folks, I am having the same problems in my GNex as described above.  Native 
tether connects, but fails to allow internet access.  Wifi Tether does not 
connect for the three reasons shown above depending on the connection settings. 

Is it possible that the RIL update for 4.2.1 may change how the mobile carrier 
views the data traffic on their network, or in the way both the native hotspot 
in the ROM and Wifi Tether generate the internet connection?  This might 
explain why some people can connect in one region and other with the same set 
up fail in a different region.  Just a stab in the dark, but I read somewhere 
that one needs to play with the broadband settings to optimize the phone 
connection.  I presume that this also includes the data connection.

Original comment by nexus02...@gmail.com on 18 Dec 2012 at 9:41

[GoogleCodeExporter]

Is it possible that the changes made in 4.2+ for multiple user profiles are 
what is causing the mount command to fail?

Original comment by max.awes...@gmail.com on 23 Dec 2012 at 7:03

[GoogleCodeExporter]

So, still no fix for this issue? Having the exact same problem on my Galaxy 
Nexus (VZW)  4.2.1. It would be nice to know if the developer were working on a 
fix for it...

Original comment by chriseva...@gmail.com on 25 Dec 2012 at 4:38

[GoogleCodeExporter]

2013... No fix for this or acknowledgment?

Original comment by galfords...@gmail.com on 17 Jan 2013 at 6:07

[GoogleCodeExporter]

bummer.  i'm having the same issue.  waiting on the cable guy to come and 
install new service at my apartment and i'm bored.  trying to tether my phone 
to my ps3 so i can watch some netflix.  i'm stealing wifi from a neighbor who 
doesn't have their router password protected, but the signal dies out all the 
time and is too weak for my ps3 to pick up.

either way, like i said, i'm having the same issue.  the on-board tethering 
doesn't work well, either.

by the way, i'm running cm 10.1

Original comment by mozaf...@gmail.com on 26 Jan 2013 at 8:04

[GoogleCodeExporter]

I've updated to Siyah 7.6.4 kernal and the wifitethering errors go away 
completely but the wifi still turns off.  Looks like anything AOKP (CM10 based) 
has this problem.

Original comment by Knips...@gmail.com on 1 Feb 2013 at 4:40

[GoogleCodeExporter]

@knips
... Is Siyah kernel compiled for Galaxy Nexus? Where did you find it?

Really no one developer is interested or able to solve this issue? Or nobody 
cares since everyone uses the built in tether? 

Original comment by orlandel...@gmail.com on 4 Feb 2013 at 10:30

[GoogleCodeExporter]

I'm sure I'm preaching to the choir for the most part but this app is far 
superior to the built in tethering.

Original comment by MSRen...@gmail.com on 4 Feb 2013 at 10:35

[GoogleCodeExporter]

Having the same problem here. Nobody is working on this?

Original comment by UsefulEndymion on 5 Feb 2013 at 11:46

[GoogleCodeExporter]

Based on the log snippet post (#26) I'm wondering if it might be manually 
possible to copy those files. Anyone tried that?

Original comment by longbot...@gmail.com on 10 Feb 2013 at 7:19

[GoogleCodeExporter]

I'm experiencing the same issue. This is the only thing keeping me from getting 
4.2. Is this a problem with the app or with android?

Original comment by psip...@gmail.com on 12 Feb 2013 at 3:58

[GoogleCodeExporter]

The post in #26 was very helpful.  I looked into the source code for 
/system/bin/ndc, and the interface to the 'softap set' command changed the 
number of arguments:

in 4.1.1 
(https://android.googlesource.com/platform/system/netd/+/android-4.1.1_r6.1/Soft
apController.cpp), the arguments to softap set are:

/*
 * Arguments:
 *      argv[2] - wlan interface
 *      argv[3] - softap interface
 *      argv[4] - SSID
 *      argv[5] - Security
 *      argv[6] - Key
 *      argv[7] - Channel
 *      argv[8] - Preamble
 *      argv[9] - Max SCB
 */
int SoftapController::setSoftap(int argc, char *argv[]) {

in 4.2.1 
(https://android.googlesource.com/platform/system/netd/+/android-4.2.1_r1.1/Soft
apController.cpp)

/*
 * Arguments:
 *      argv[2] - wlan interface
 *      argv[3] - SSID
 *      argv[4] - Security
 *      argv[5] - Key
 *      argv[6] - Channel
 *      argv[7] - Preamble
 *      argv[8] - Max SCB
 */

when the /system/bin/ndc is invoked from wifi-tether with the incorrect 
arguments against 4.2.1, netd actually crashes (saw it in the logcat). this 
results in the "Lost connection to Netd - did it crash?" message. since the 
softap config is never configured correctly, the AP won't start, the SSID won't 
broadcast, etc.

i was able to get tethering started from a command line with the following:

/system/bin/ndc softap stopap
/system/bin/ndc softap fwreload wlan0 AP
/system/bin/ndc softap set wlan0 KVGT open none 1 0 8
/system/bin/ndc softap startap
/system/bin/ndc interface setcfg wlan0 172.20.21.254 255.255.255.0 up

/data/data/com.googlecode.android.wifi.tether/bin/iptables -N wireless-tether
/data/data/com.googlecode.android.wifi.tether/bin/iptables -F wireless-tether
/data/data/com.googlecode.android.wifi.tether/bin/iptables -F FORWARD
/data/data/com.googlecode.android.wifi.tether/bin/iptables -t nat -F PREROUTING
/data/data/com.googlecode.android.wifi.tether/bin/iptables -t nat -F POSTROUTING
/data/data/com.googlecode.android.wifi.tether/bin/iptables -t nat -F
/data/data/com.googlecode.android.wifi.tether/bin/iptables -A wireless-tether 
-m state --state ESTABLISHED,RELATED -j ACCEPT
/data/data/com.googlecode.android.wifi.tether/bin/iptables -A wireless-tether 
-s 172.20.21.0/24 -j ACCEPT
/data/data/com.googlecode.android.wifi.tether/bin/iptables -A wireless-tether 
-p 47 -j ACCEPT
/data/data/com.googlecode.android.wifi.tether/bin/iptables -A wireless-tether 
-j DROP
/data/data/com.googlecode.android.wifi.tether/bin/iptables -A FORWARD -m state 
--state INVALID -j DROP
/data/data/com.googlecode.android.wifi.tether/bin/iptables -A FORWARD -j 
wireless-tether
/data/data/com.googlecode.android.wifi.tether/bin/iptables -t nat -I 
POSTROUTING -s 172.20.21.0/24 -j MASQUERADE
/data/data/com.googlecode.android.wifi.tether/bin/dnsmasq -i wlan0 
--dhcp-authoritative --no-negcache --user=root --no-resolv --no-hosts 
--server=8.8.8.8 --server=8.8.4.4 --dhcp-range=172.20.21.100,172.20.21.108,12h 
--dhcp-leasefile=/data/data/com.googlecode.android.wifi.tether/var/dnsmasq.lease
s --pid-file=/data/data/com.googlecode.android.wifi.tether/var/dnsmasq.pid
/system/bin/chmod 666 
/data/data/com.googlecode.android.wifi.tether/var/tether.log

echo 1 > /proc/sys/net/ipv4/ip_forward

i haven't tried with encryption yet, but it should be a matter of passing the 
correct args.

so, along those lines -- i tried editing the tether.edify script to remove the 
extra arg for my config.  but wifi-tether copies that file over every time it 
starts from the GUI. so i made the file read-only ... and, while it would then 
start w/o errors, something else was still controlling the wifi interface 
outside of tethering -- so it was busted still.  i didn't dig into that anymore.

long story short: the components are there and can be made to work, the major 
issue being the argument changes. but it still required a shell to run it.

hope that helps the devs!

Original comment by darren.o...@gmail.com on 12 Feb 2013 at 3:27

[GoogleCodeExporter]

I'm having the same problems with my Galaxy S3 on Pacman 4.2, I got it to kind 
of work with the synergized one but 4G drops once my laptop connects...

Original comment by Barnwe...@gmail.com on 14 Feb 2013 at 3:52

[GoogleCodeExporter]

any news on this?

it's the only thing that keeps me from upgrading my galaxy nexus to 4.2

Original comment by riccardo...@gmail.com on 27 Feb 2013 at 3:04

[GoogleCodeExporter]

I've got the same problem and won't update until I know it'll work.

Original comment by bubb...@gmail.com on 27 Feb 2013 at 3:05

[GoogleCodeExporter]

I'm getting the same problem on GNEX 4.2.1 stock on Sprint.  I also tried 
Barnacle, FoxFi, and SVTP; they all failed as well.  The best solution I found 
for the time being is EasyTether which works through USB and then broadcasting 
WiFi from the computer side.  It's not as convenient as WiFi Tether, but it 
works now.

Original comment by WhoSan...@gmail.com on 27 Feb 2013 at 3:23

[GoogleCodeExporter]

I solved with this: 
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter

Original comment by fabio.gr...@gmail.com on 9 Mar 2013 at 7:59

[GoogleCodeExporter]

#44 I presume you are the same Fabio Grasso who sell the app... 

Original comment by federico...@gmail.com on 9 Mar 2013 at 8:02

[GoogleCodeExporter]

yes, I developed this app to solve this problem.

is there any problem?

Original comment by fabio.gr...@gmail.com on 9 Mar 2013 at 8:05

[GoogleCodeExporter]

Probably using this codebase with the open source fix in the comments.

Original comment by derrick.simpson@gmail.com on 9 Mar 2013 at 8:05

[GoogleCodeExporter]

Hey, I'm down. If it works, I'll buy it. I was going to donate to THIS project 
if the maintainers ever decided to update it, as a thank you. But if you're 
going to actually be responsive in a reasonable timeframe, then I'll happily 
vote with my dollars in your direction.

Original comment by longbot...@gmail.com on 9 Mar 2013 at 8:08

[GoogleCodeExporter]

absolutely not, it works in another way by testing it soon becomes clear.

cmq I did not want to disturb

I apologize if I did.

Original comment by fabio.gr...@gmail.com on 9 Mar 2013 at 8:08

[GoogleCodeExporter]

@longbot if you want you can try the app
I remind you that Google from 15 minutes to cancel the purchase and seek 
reimbursement

Original comment by fabio.gr...@gmail.com on 9 Mar 2013 at 8:14