Tether started with errors! Failed to config and start access point

[GoogleCodeExporter]

Which device (manufacturer, type)?
Sprint Galaxy Nexus (toroplus0

Which firmware is installed?
Android 4.2.1 (rooted with stock recovery)

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

What steps will reproduce the problem?
1. Press to start tethering
2. Tether started with errors! check Show Log
3. Failed to configure and start AP

Original issue reported on code.google.com by vinit.ma...@gmail.com on 29 Jan 2013 at 8:13

Attachments:

• Screenshot_2013-01-29-14-30-29.png

[GoogleCodeExporter]

I upgraded to Android 4.2.1 I am having the exact same issues you are reporting.

All things the same, I had Android v4.1.2 on a Sprint Epic 4G Touch, running 
3.2-beta2 as well, device profile Samsung Galaxy Nexus (CDMA/LTE) and that 
works. 

It appears there is some issues specific to 4.2.1. I'd be curious if anyone has 
had success with 4.2.1 and this app.

Original comment by adam.moh...@gmail.com on 30 Jan 2013 at 5:29

[GoogleCodeExporter]

Same in  Nexus S 4g with 4.2.1. 

Original comment by soller...@gmail.com on 7 Feb 2013 at 6:38

[GoogleCodeExporter]

@#2
http://code.google.com/p/android/issues/detail?id=38563

Original comment by adam.moh...@gmail.com on 7 Feb 2013 at 6:48

[GoogleCodeExporter]

I had this same issue, but I "solved" it by installing 3.1b14, then 3.2b2, and 
finally 3.3pre2. Unfortunately, while now the log shows green on all counts, it 
still doesn't work. It doesn't seem to be broadcasting the SSID and I can't 
connect.

What setup methods have you been using? The only one I can coerce to work 
(though as I said, still no SSID) is Netd. The rest of them still result in the 
same errors.

Original comment by longbot...@gmail.com on 9 Feb 2013 at 1:41

[GoogleCodeExporter]

I haven't been able to fix the problem.  Netd starts the program without 
errors, but you're right, no SSID and no wifi connection.

I might try the solution in adam's link, but it sounds like a cumbersome 
process to go through every time I want to tether.

Original comment by soller...@gmail.com on 10 Feb 2013 at 11:01

[GoogleCodeExporter]

I am currently working on that, but I haven't had much luck. As is, command did 
diddly squat, so I have to figure out which interface to tell it to use. I'm 
not even sure if a solution that works for the GSM GNex will also work for the 
LTE/CDMA version.

However, as I read that thread, it's relating to the built-in tethering 
infrastructure, which Sprint has intentionally crippled beyond hope unless you 
have a tethering plan. Getting that method working won't help me much (though 
it might for you, if you have a different carrier).

Original comment by longbot...@gmail.com on 11 Feb 2013 at 5:39

[GoogleCodeExporter]

see my comment in 

http://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c39

there are bunches and bunches of wifi-tether issues reported against 4.2.1, and 
i bet most are related to the ndc softap 'set' command argument changes.

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

[GoogleCodeExporter]

exact same problem with verizon galaxy nexus running 4.2.2

Original comment by vsu...@gmail.com on 6 Mar 2013 at 4:19

[GoogleCodeExporter]

Might it be possible to increase this from a medium to high priority, given 
that it's from 4.2.1 onward, due to internal changes in Android?

Original comment by longbot...@gmail.com on 6 Mar 2013 at 4:21

[GoogleCodeExporter]

AOKP d2vzw JB MR1 Build 5 on a VZW SG3.  That's Android 4.2.2 for those keeping 
score.  I'm nervous about using the native tether and have always been fond of 
WiFi Tether.  Native tethering in AOKP appears to work just fine.  WiFi Tether 
starts with errors.

Here's to hoping there is a fix soon.  I miss being able to tether devices.  
Nothing new to report in regards to what has already been posted.  Darren 
seemed to be on to something in the other thread.  Let's hope the dev finds a 
solution.

Original comment by craig.la...@gmail.com on 8 Mar 2013 at 1:13

[GoogleCodeExporter]

I'm not sure why this would be medium priority... since this makes the app 
unusable.

Original comment by aka...@gmail.com on 11 Mar 2013 at 12:54

[GoogleCodeExporter]

Ditto to #11.  This should be high priority.  Just to be clear, 4.2.2 is not 
working for Nexus S 4G.

Original comment by soller...@gmail.com on 11 Mar 2013 at 8:20

[GoogleCodeExporter]

There are actually several reports of this nature, and all of them are marked 
"medium" in priority. Some of you might find this other thread interesting: 
https://code.google.com/p/android-wifi-tether/issues/detail?id=1661

There's some more information on the root cause of this issue, as well as a new 
app alternative.

Original comment by longbot...@gmail.com on 11 Mar 2013 at 8:35

[GoogleCodeExporter]

Any new updates? I'm running AOKP build 6 on verizon galaxy nexus.. Built in 
tether starts and then stops immediately... wifi tether won't even broadcast.. 
A lot of people are claiming that they have it broadcasting and can connect and 
get an IP and everything, but no throughput. However, mine won't even 
broadcast. Just says "tethering started with errors, check show log" then I do 
and everything is "done" except for Starting AP and Configuring AP which fail.

Original comment by russellh...@gmail.com on 17 Jun 2013 at 5:37

[GoogleCodeExporter]

FIXED 

http://socal.hanhuy.com/~pfnguyen/wifi-tether-gnex-4.2.2.apk

If you guys are willing to trust me, I have my own build of wifi-tether posted 
at the link above; it is signed using my debug key, so you will need to 
uninstall any existing version of wifi tether you may have.

FYI, my patch is not a general-purpose solution, as it will break on prior 
versions of android (it is specifically tailored to 4.2); although it also 
fixes the mssclamping error at the same time.

Original comment by russellh...@gmail.com on 17 Jun 2013 at 5:52

[GoogleCodeExporter]

Do we have a fix for 4.1.2?

Original comment by newcreat...@gmail.com on 21 Jun 2013 at 2:27

[GoogleCodeExporter]

This is how I have fixed this issue.  I am running a GS3 with CyanogenMod 4.3.  
I downloaded the wifi tether 3.4 experimental and also downloaded SuperSu to 
replace Superuser.  This fixed it for me.

Original comment by Danielb...@gmail.com on 5 Aug 2013 at 1:04

[GoogleCodeExporter]

DanielB....you are awesome, my friend!  Put SlimBean 4.4.4 build 8 on a GS3 and 
was tearing my hair out on how to get this working.  All the other suggestions 
I've seen bit the dust, and nobody else I have seen mentioned SuperSu vs. 
Superuser.  That was the key!  Thank you...thank you...

Original comment by tginsb...@gmail.com on 11 Sep 2013 at 9:41

[GoogleCodeExporter]

Oops...that was SB 4.2.2.... :-)

Original comment by tginsb...@gmail.com on 11 Sep 2013 at 9:42

[GoogleCodeExporter]

#15 Thanks that link made the tether work exactly how it's supposed to 
Using Epic 4G Touch (SPH-D710), Android 4.2.2

Original comment by faizan.s...@gmail.com on 1 Oct 2013 at 3:12

[GoogleCodeExporter]

No way I  can get it to work! I'm trying with a Google Nexus S with 4.2.1. I 
tried with the link in #15 and SuperSU. Any suggestions? 

Original comment by sng...@gmail.com on 6 Oct 2013 at 11:28

[GoogleCodeExporter]

sng...@gmail.com.  Try using link #17 - wifi tether 3.4 experimental along with 
SuperSU.  That's what worked for me.

Original comment by tginsb...@gmail.com on 7 Oct 2013 at 1:23

[GoogleCodeExporter]

Just updated my Nexus S to 4.3 Hellybean. Now Wifi tether 3.3-pre2 experimental 
works flaulessly :) 

Original comment by sng...@gmail.com on 9 Oct 2013 at 12:54

[GoogleCodeExporter]

@ #15 russellh...@gmail.com

You sir are a life saver, also on a Epic 4G Touch running CM 10.1  

Original comment by lalkr...@gmail.com on 10 Oct 2013 at 2:32