Samsung Galaxy S (Vibrant/Captivate): Infrastructure Mode

[GoogleCodeExporter]

Which device (manufacturer, type)?
Samsung vibrant

Which firmware is installed?
Stock 2.1

What version of wireless tether are you using?
All

What steps will reproduce the problem?
1. feature doesnt exist.
2.
3.

What is the expected output? What do you see instead?
XXXX

Please provide any additional information below.

I was hoping you guys can add infostruc to this app. It would help alot of us 
out there. who have devices that cant tether to ad-hoc networks. THANKS

Original issue reported on code.google.com by john.b.h...@gmail.com on 20 Jul 2010 at 7:52

[GoogleCodeExporter]

similar experience, samsung epic 4g,  (Android 2.2 DK28).  

I used 3.0 pre4 and that seemed to work for 24 hours. The next day it would say 
starting up and then running.. but the 2nd sprint hotspot icon no longer 
appeared. the log showed everything "done" except activating WiFi interface 
"failed".

I tried to clear the application data, but that didnt help. then I upgraded to 
pre5 and my phone reboots itself just after the 2nd sprint hotspot icon appears.

Original comment by chip.warner@gmail.com on 16 Feb 2011 at 5:51

[GoogleCodeExporter]

i uninstalled, re-installed, deleted the conf, re-installed binaries, and pre5 
will now start in ad-hoc. 

switching it to samsung_softap, i get the following (and no Sprint Hotspot 
icon).

#./tether start 1
KEY ==> 'none' length(4), SSID ==> '.' length(1), PSK ==> 
'6dd394556a0cbfd1dece967ff7de282586dffe96af3de03c67341465b0057868'
Softap set - failed: -1Softap start - failed: -1
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/ifconfig eth0 
192.168.2.254 netmask 255.255.255.0]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/ifconfig eth0 up]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -N 
wireless-tether]
iptables: Chain already exists
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -F 
wireless-tether]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -t nat 
-F PREROUTING]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -t nat 
-F POSTROUTING]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -t nat 
-F]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -t 
mangle -F FORWARD]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -t 
mangle -F]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -A 
wireless-tether -m state --state ESTABLISHED,RELATED -j ACCEPT]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -A 
wireless-tether -s 192.168.2.0/24 -j ACCEPT]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -A 
wireless-tether -p 47 -j ACCEPT]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -A 
wireless-tether -j DROP]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -A 
FORWARD -j wireless-tether]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/iptables -t nat 
-I POSTROUTING -s 192.168.2.0/24 -j MASQUERADE]
about to run: [/data/data/at.mysandbox.android.wifi.tether/bin/dnsmasq -i eth0 
--resolv-file=/data/data/at.mysandbox.android.wifi.tether/conf/resolv.conf 
--conf-file=/data/data/at.mysandbox.android.wifi.tether/conf/dnsmasq.conf]
script result was []
#

Original comment by chip.warner@gmail.com on 16 Feb 2011 at 7:03

[GoogleCodeExporter]

First ... I need dmesg-output ... do this after you have started tethering:

adb shell dmesg > /sdcard/dmesg.txt

This will produce a dmesg.txt-file on your sdcard. Please upload it here - make 
sure to use "softap_samsung".

Anyway ... I've uploaded a new version:
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_0-pre6.apk
(I've just removed some checks ...)

Please upload /data/data/at.mysandbox.android.wifi.tether/conf/tether.conf here 
as well. (After you have started via gui at least once.)

You can pull it from your device like this:
adb pull /data/data/at.mysandbox.android.wifi.tether/conf/tether.conf .

This seems to work fine for me and should do the same like previous versions.

Thanks.

Original comment by harald....@gmail.com on 16 Feb 2011 at 8:51

[GoogleCodeExporter]

Updated to pre8, and switched ROMs (still 2.2), and now everything works unless 
4G is enabled when starting tether, in which case the phone reboots (so I can't 
get at dmesg).

Original comment by fish199...@gmail.com on 16 Feb 2011 at 11:01

Attachments:

• tether.conf

[GoogleCodeExporter]

So, it reboots when starting tethering with enabled 4G?

Could you please pull the file /proc/last_kmsg when the phone is up (after the 
reboot)?

adb pull /proc/last_kmsg .

Thanks.

Original comment by harald....@gmail.com on 16 Feb 2011 at 11:19

[GoogleCodeExporter]

adb pull /proc/last_kmsg . doesn't work:
remote object '/proc/last_kmsg' does not exist

Original comment by fish199...@gmail.com on 17 Feb 2011 at 12:28

[GoogleCodeExporter]

same here (uninstalled all, installed Pre9, 4G enabled, device reboots after 
the Sprint Hotspot icon appears). i've attached '/proc/kmsg' as close to after 
the reboot as possible.

Not sure this helps, but I discovered a work around: Start Wifi Tether with 4G 
turned off. Then once its running, turn 4G on. Then stop Wifi Tether. After 
that, I can start/stop Wifi Tether with 4G on.   And now I cant figure out how 
to get it to crash again.

Original comment by chip.warner@gmail.com on 17 Feb 2011 at 2:59

Attachments:

• kmsg1.txt
• dmesg-3g-enabled.txt
• dmesg-4g-enabled.txt
• tether.conf

[GoogleCodeExporter]

ok, after a few hours of use, something was out of sync between Wifi Tether and 
the Sprint Hotspot.. the Wifi Tether icon disappeared, and when I pulled down 
the status bar, it told me that Wifi Tether had requested root privileges 
(again), and then when I went to the GUI, it said that it was not running, but 
the Hotspot icon was still there. shortly after my phone reboot. Upon starting 
up again, Wifi Tether would start with the error (softap failed), and if I 
started Wifi with 3G and tried to switch to 4G after it was running, it would 
just reboot my phone.

So, I went to manage apps, and cleared application cache for Wifi Tether, then 
started it again, and then I was able to start in 3G with no softap error, get 
it running, then turn on 4G, and now I can start/stop with 4G again.  

what are the best logs I can provide you with? and at what step?

Original comment by chip.warner@gmail.com on 17 Feb 2011 at 5:05

[GoogleCodeExporter]

looks like this is reproducible, as the same thing happened again as above 
(except the phone just randomly reboot while i was surfing). after my phone 
reboot, it would reboot for both 3g and 4g start up. once I cleared wifi tether 
app cache, then I could start with 3G, and flip 4G on again. 

Original comment by chip.warner@gmail.com on 17 Feb 2011 at 6:45

[GoogleCodeExporter]

@chip: Mmmh. I don't see anything in the logs. Maybe an appkiller which kills 
the application? 

I know if you try to start the softap when it's already enabled a device 
reboots (happens on my nexusone as well) ... and when the app is killed it 
probably does not recognize that it's already running.

Original comment by harald....@gmail.com on 17 Feb 2011 at 5:29

[GoogleCodeExporter]

no app killer. (and stock as possible). it happened again tonight, and after it 
was at the point that it reboots on starting for 3g or 4g, I found that if I 
delete "tether.conf", then the GUI will start again without crashing/rebooting 
phone. however, i could not receive data from the wifi connection, even though 
my computer said it was connected. next step, I tried 're-install binaries' and 
it magically started working again. odd thing, i never had to re-setup the 
ssid/wpa2 key/etc. but, does that make any sense if i clearly deleted the 
tether.conf?

$ su
su
# cd /data/data/at.mysandbox.android.wifi.tether/conf/
cd /data/data/at.mysandbox.android.wifi.tether/conf/
# ls
ls
wpa_supplicant.conf
tether.edify
dnsmasq.conf
tether.conf
resolv.conf
# rm tether.conf
rm tether.conf
# ls
ls
wpa_supplicant.conf
tether.edify
dnsmasq.conf
resolv.conf
#

Original comment by chip.warner@gmail.com on 18 Feb 2011 at 6:35

[GoogleCodeExporter]

harald, upgraded to our official 2.2.1 release, EB13. using 3.0 pre 10, i have 
the same problems as described before, but i have some more observations that 
might help:

1) after using wifi tether for a little over an hour, the phone will vibrate 
once, then quickly 3 more times, and then the phone reboots. then it will not 
start again without clearing the "tether.conf", or app manager|clear app cache, 
OR:

2) if the phone crashes/reboots while trying to start wifi tether in infra-mode 
(even with 4G disabled), I have found a better work around: i can go to the 
config, change it "ad-hoc" mode and start it (*even with 4G enabled*), then 
stop it, then change it to "infra-mode" then start it again (*even with 4G 
turned on, optional*), and it will work perfectly.. for at least an hour.

also, is there a log I can pull immediately after my phone reboots? or a more 
detailed log I can create when I am starting wifi tether during the time when 
starting in infra-mode crashes/reboots? I am new, but would a logcat help here, 
or DDMS?

Original comment by chip.warner@gmail.com on 23 Feb 2011 at 6:05

[GoogleCodeExporter]

My root phone was discovered by my probater T-Mobile and they put a block on my 
phone how so I go by rooting my phone again? 

Original comment by Gmartine...@gmail.com on 28 Mar 2011 at 11:24

[GoogleCodeExporter]

Samsung Captivate, rooted and using froyo, stock otherwise.  Just uninstalled 
pre5 and installed pre12.  Infrastructure mode seems to be working great!  I 
can now connect my Xoom using wifi tether!!  Thanks!!

Original comment by laneridd...@gmail.com on 12 Apr 2011 at 1:37

[GoogleCodeExporter]

Anyone have tvoutserver file??pls share..mine dont have it

Original comment by mohdazno...@gmail.com on 12 Jul 2013 at 1:31