[Verizon Samsung Galaxy S III] TrevE:
FAQ

AP Starts but unable to connect - Make sure Send Netd max client mode option is on if your on JellyBean. read p1 for required settings

Tether does not start / Adapter does not work after tether- Try to turn off Wifi-Driver Reload #1 and turn on Wifi-Driver Reload #2

Tether cuts off on on charger connect/disconnect- Try to turn off connection optimizer. More here from eyecon82 http://xdaforums.com/showpost.php?p=34467459&postcount=148

mystery_tx_man suggests removing connection manager apk - http://xdaforums.com/showpost.php?p=34838831&postcount=218

Phone takes back control of wifi- Youll notice a "What the hell" toast message. Somehow the phone moved wifi state, either you toggled an app that turns on wifi or some system process was thinking for you. Disable whatever is doing it.

cyrnel suggests disabling wireless network location services - http://xdaforums.com/showpost.php?p=34721619&postcount=200

If you get it on screen shut off try changing "Wifi During Sleep" - on htc its menu -> settings - wifi -> menu -> Advanced -> Keep Wifi on during sleep -> Always

You get a Tmobile Hotspot page-

Changing APNs is reported to work by Gandoff without changing useragent- http://xdaforums.com/showpost.php?p=34629321&postcount=191

Changing user agents works as described by mad_unix http://xdaforums.com/showthread.php?p=34388089#post34388089 and free_man http://xdaforums.com/showthread.php?p=34500399#post34500399

open1your1eyes0 has some vpn setup links which should also work - http://xdaforums.com/showpost.php?p=34798223&postcount=211

XXXX still doesnt work - First try SuperSU. This will avoid a lot of headaches. Then make sure you are on latest version and that you have uninstalled/cleared app data when you went to a newer version. Read over the last few pages of thread at least too to make sure its not a known issue then go for it and post away. Make sure you include Carrier / Device / Rom / SU application.

Debugging Issues

For those people having issues on other gs3 like devices / roms / whatever I do not even have a gs3 so this is all blind. To try to help debugging I created a script to hopefully grab information needed. This should help from both working/nonworking devices to help eliminate the stupid symlink code and fix up other devices.

The scripts point is to try to get a working AP. If you can post how you did it and we can get source changed. By default it does no driver reloads and starts an Open AP with SSID TrevScript.

First grab the latest script from svn (ill update it with more info after I get some logs so make sure you have latest)

http://svn.ziggy471.com/treve-tether/ grab tetherdebug.sh

adb push tetherdebug.sh /system/xbin/
adb shell chmod 755 /system/xbin/tetherdebug.sh
adb shell busybox dos2unix /system/xbin/tetherdebug.sh

Make sure wifi is on but do not start witfitethering. All you want to do is run "Set Binaries to WifiTether" option in the menu of app then follow below code

adb shell su -c tetherdebug.sh
adb pull /data/local/tmp/tether.log

rename the file to tether_wifibinaries.log. Check to see if any AP is available.

now run "Set Binaries to Native" option in app and reboot device

adb reboot

When the device comes back up, rerun the script.

adb shell su -c tetherdebug.sh
adb pull /data/local/tmp/tether.log

rename the file to tether_nativebinaries.log. Check to see if any AP is available.

reboot after you get the file.

adb reboot

ADVANCED

If you know what you are doing you can try to find a working combo. I added in the following command line args

ARG1 = ENCRYPTION. NONE/WPA2

ARG2 = DRIVERRELOAD. NONE/insmod/mfgloader

ARG3 = DRIVERTOLOAD. /system/lib/modules/dhd.ko (or whatever module is, required if ARG2 is set)

Examples:

Make sure wifi is on but do not start witfitethering. All you want to do is run "Set Binaries to WifiTether" option in the menu of app to start with a known working base then follow below code

try no encryption with insmod where your wifi module is /system/lib/modules/dhd.ko

adb shell su -c tetherdebug.sh NONE insmod /system/lib/modules/dhd.ko

try no encryption with mfgloader where your wifi module is /system/lib/modules/dhd.ko

adb shell su -c tetherdebug.sh NONE mfgloader /system/lib/modules/dhd.ko

try wpa2 (password is Trev) with insmod where your wifi module is /system/lib/modules/dhd.ko

adb shell su -c tetherdebug.sh WPA2 insmod /system/lib/modules/dhd.ko

There shouldn't be personal information in the debug logs, the most I can think of that would be displayed is if you have an encryption passphrase set in wifitether. Sending the 2 files named with what mode you were in will help get it going elsewhere and hopefully kill the symlink code