Open GoogleCodeExporter opened 9 years ago
Basically it looks like that the vibrant comes with a bcm4329-broadcom
wifi-chip. This is good because it's the same chip like the evo and nexusone
has (and you probably know that we have master/infrastructure-mode working on
these devices).
Please extract the kernel-config from your device and upload it here:
adb pull /proc/config.gz .
What kernel-modules are located in /lib/modules and/or /system/lib/modules?
adb shell
cd /lib/modules
ls
<need the output of the last command>
cd /system/lib/modules
ls
<need the output of the last command>
Original comment by harald....@gmail.com
on 20 Jul 2010 at 9:19
Hello,
Thanks for the quick answer.
As for part one:
# busybox find ./ -name config.gz
#
Part 2:
# cd /lib/modules
ls
# fsr_stl.ko
multipdp.ko
fsr.ko
j4fs.ko
dhd.ko
param.ko
vibrator.ko
rfs_glue.ko
scsi_wait_scan.ko
s3c_bc.ko
rfs_fat.ko
stgloc
Si4709_driver.ko
pvrsrvkm.ko
dpram.ko
drop_caches.ko
s3c_lcd.ko
There is no system/lib/modules. But i pasted a LS of /system/lib
# pwd
/system/lib
# ls
libwtlcore.so
libandroid_servers.so
libsavsff.so
libaudio.so
libsmp4veomxoc.so
libImmVibeJ.so
libopencore_author.so
lib_Samsung_Sound_Booster.so
libwifitest.so
libexif.so
libIMGegl.so
libsrec_jni.so
libvorbisidec.so
libPVRScopeServices.so
libnetutils.so
libskia.so
libplayready_jni.so
libEGL.so
libflashliteplugin.so
libImmVbs.so
libopencore_rtspreg.so
libGLESv2.so
libpvdivxdrm.so
lib_R2VS_ARM_GA_Library_for_Aries.so
libflashlite_jni.so
libthread_db.so
libbinder.so
libopencore_net_support.so
libarccamera.so
libsmkvdreg.so
libtvoutservice.so
libsflacdomxoc.so
lib_tvoutengine.so
libseccamera.so
libopencore_rtsp.so
libsvc1domxoc.so
Aries
libRS.so
libs264domxoc.so
libms3c_yamaha.so
libctest.so
libglslcompiler.so
libswmv8domxoc.so
libwmlscriptcore.so
libopencore_download.so
libdrm1.so
libsavidreg.so
libbluetooth.so
libtvout_jni.so
libtiffanyjni.so
libswmadomxoc.so
libquramvdecoder.so
libgtalk_jni.so
libsavidocn.so
libQEffectJNI.so
libsoundpool.so
libmtp.so
libtvout.so
libxml2wbxml.so
libsrv_um.so
bluez-plugin
libvolcustomjni.so
libvtmanager.so
libwmdrm_jni.so
libvt.so
libclientgps.so
libseccameraadaptor.so
libsaacdomxoc.so
libsmp4vdomxoc.so
libandroid_runtime.so
libaudioflinger.so
libplayready.so
libril.so
libvideieditor.so
libsysutils.so
libsecril-client.so
libdiscjni.so
libsamreomxoc.so
libicuuc.so
libs263eomxoc.so
liba2dp.so
libswmfdocn.so
libwmdrm.so
libvtstack.so
libsamsungSoundbooster.so
egl
libActionShot.so
libQmageDecoder.so
libs3cjpeg.so
libspeech.so
libaes.so
libswmfdreg.so
libjni_latinime.so
libwebcore.so
libcaps.so
libsavsvc.so
libsmkvdocn.so
libGLESv1_CM.so
libcamera.so
libsflacfdreg.so
libIcs.so
libcameraservice.so
libPanoraMax1.so
libmediaplayerservice.so
liblwfa-0.A.0-mng.so
libdrm1_jni.so
libopencore_2way.so
liblwfa-0.A.0.so
libsAMRWB.so
libhardware.so
libsensor_yamaha_test.so
libsvgplayer.so
libsavscmn.so
libs263domxoc.so
libttssynthproxy.so
libdbus.so
libsmp4fmocn.so
libomx_sharedlibrary.so
libsaaceomxoc.so
libquramimagecodec.so
libui.so
libsAMRNB.so
libslideshowjni.so
libPlusMe.so
libdrm2_jni.so
libImmVibe.so
libsavehacsetting.so
liblog.so
libflashlitepackage.so
libsflacfdocn.so
libXt9core.so
libsonivox.so
libmnglw-0.9.4.so
libsaveaudiencesetting.so
libttspico.so
libutils.so
libsthmb.so
libsflvdocn.so
libsecgps.so
libssl.so
libdprw.so
libsamsung_http_file.so
libopencore_mp4localreg.so
libFFTEm.so
libnativehelper.so
libCaMotion.so
libwbxml_jni.so
libmedia.so
libDHWR.so
libpvrANDROID_WSEGL.so
libsensor_yamaha.so
libm.so
libacc.so
libpvr2d.so
libve_jni.so
libexpat.so
libsdiv3domxoc.so
libsavsac.so
libsrv_init.so
libicui18n.so
libcrypto.so
libsamsungAcousticeq.so
libSwypeCore.so
libsystem_server.so
libsamsung_http.so
libsec-ril.so
librs_jni.so
libsflvdreg.so
libdvm.so
libtvouthdmi.so
libc.so
libskiagl.so
libpvwmdrm.so
libicudata.so
libsamsungr2vs.so
libemoji.so
libaudiopolicygeneric.so
libstdc++.so
libsqlite.so
libcutils.so
libswmv7domxoc.so
libfmradio_jni.so
libbluetoothd.so
libsmp3domxoc.so
libopencore_common.so
libsurfaceflinger.so
libhardware_legacy.so
libsac3domxoc.so
libopencore_player.so
libopencore_mp4local.so
libaudiopolicy.so
libloadaudience.so
libwlservice.so
libdivxdrm.so
libwpa_client.so
libbluedroid.so
libz.so
libmtp_jni.so
hw
libpixelflinger.so
lib_Samsung_Acoustic_Module_Llite.so
lib_Down_Sampler_ARM_GA_Library.so
libsisodrm.so
libdl.so
libreference-cdma-sms.so
libsubmictest.so
libomadrm.so
libcamerafirmwarejni.so
libs264eomxoc.so
libdivx_jni.so
libreference-ril.so
libmedia_jni.so
libopencore_downloadreg.so
libtvoutfimc.so
libsamsung_psi.so
libsamrdomxoc.so
#
Thanks
Original comment by john.b.h...@gmail.com
on 21 Jul 2010 at 4:58
Do you know if samsung has already published the kernel-sources?
I will throw something together which might work (low chance) by the end of
this week.
Original comment by harald....@gmail.com
on 21 Jul 2010 at 2:19
Hello,
As far as i know the only source available is the i9000 source and it can be
found at http://opensource.samsung.com/
I am not sure if this helps with the vibrant.
Original comment by john.b.h...@gmail.com
on 21 Jul 2010 at 5:12
Hello,
There is also a thread here that talks about the kernel + the eclair sources
http://forum.samdroid.net/f49/samsung-i9000-linux-kernel-eclair-source-1149/
Thanks
Original comment by john.b.h...@gmail.com
on 21 Jul 2010 at 5:15
Btw, Just wanted to mention No version of wireless-tether works on my vibrant
atm.
I am not sure if you are putting the non-adhoc fix + making it work at the same
time :)
Thought id chime that in.
Thanks!
Original comment by john.b.h...@gmail.com
on 21 Jul 2010 at 6:59
Ok. Here is a first version which includes some vibrant-related changes:
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_5-pre3.apk
What to test:
1) Install and try to start from gui.
2) Check for errors by selecting "Show log".
3) Pull the config-file which was created:
adb pull /data/data/android.tether/conf/tether.conf
4) Try to start from cmd-line and check for additional error-msgs:
adb shell
su
cd /data/data/android.tether/bin
./tether start 1
Please desribe your findings as good ad possible. I don't own such a device and
I'm not able to do any tests.
Original comment by harald....@gmail.com
on 21 Jul 2010 at 10:42
Ok.. I tried the tether app and here is what I get :
Starting access-point... failed
Activating WiFi interface... failed
Enabling NAT rules... done
Enabling IP forwarding... done
Tethering now running... done
tether.conf :
ip.gateway=192.168.2.254
system.rp_filter=0
wifi.encryption=open
tether.mode=wifi
ip.netmask=255.255.255.0
wifi.txpower=disabled
wifi.interface=eth0
wifi.setup=wpa_supplicant
wifi.channel=6
wifi.encryption.key=none
ip.network=192.168.2.0
wifi.driver=softap_gog
wifi.essid=AndroidTether
device.type=vibrant
Status of start :
about to run: [/data/data/android.tether/bin/ultra_bcm_config eth0 softap_gog
AndroidTether open none 6]
SET failed on device eth0 ; No such device.
about to run: [/data/data/android.tether/bin/ifconfig eth0 down]
error: SIOCGIFFLAGS (No such device)
about to run: [/data/data/android.tether/bin/ifconfig eth0 192.168.2.254
netmask 255.255.255.0]
error: SIOCSIFADDR (No such device)
about to run: [/data/data/android.tether/bin/iptables -N wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -m
state --state ESTABLISHED,RELATED -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -s
192.168.2.0/24 -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -j
DROP]
about to run: [/data/data/android.tether/bin/iptables -A FORWARD -j
wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -I POSTROUTING -s
192.168.2.0/24 -j MASQUERADE]
about to run: [/data/data/android.tether/bin/dnsmasq -i eth0
--resolv-file=/data/data/android.tether/conf/resolv.conf
--conf-file=/data/data/android.tether/conf/dnsmasq.conf]
script result was
Original comment by elee...@gmail.com
on 22 Jul 2010 at 4:28
I manually turned the wifi on and tried the manual start and got the following :
about to run: [/data/data/android.tether/bin/ultra_bcm_config eth0 softap_gog
AndroidTether open none 6]
SET failed on device eth0 ; Invalid argument.
about to run: [/data/data/android.tether/bin/ifconfig eth0 down]
about to run: [/data/data/android.tether/bin/ifconfig eth0 192.168.2.254
netmask 255.255.255.0]
about to run: [/data/data/android.tether/bin/ifconfig eth0 up]
about to run: [/data/data/android.tether/bin/iptables -N wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -m
state --state ESTABLISHED,RELATED -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -s
192.168.2.0/24 -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -j
DROP]
about to run: [/data/data/android.tether/bin/iptables -A FORWARD -j
wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -I POSTROUTING -s
192.168.2.0/24 -j MASQUERADE]
about to run: [/data/data/android.tether/bin/dnsmasq -i eth0
--resolv-file=/data/data/android.tether/conf/resolv.conf
--conf-file=/data/data/android.tether/conf/dnsmasq.conf]
Original comment by elee...@gmail.com
on 22 Jul 2010 at 5:47
# cat wifi.conf
FIRMWARE_LOADER=wlan_loader
DRIVER_PROP_NAME=wlan.driver.status
SUPPLICANT_NAME=wpa_supplicant
SUPP_PROP_NAME=init.svc.wpa_supplicant
MODULE_FILE=/proc/modules
IFACE_DIR=/data/misc/wifi
DRIVER_MODULE_NAME=dhd
DRIVER_MODULE_TAG=dhd
FIRMWARE_LOADER=
SUPP_CONFIG_TEMPLATE=/system/etc/wifi/wpa_supplicant.conf
SUPP_CONFIG_FILE=/data/wifi/bcm_supp.conf
DRIVER_MODULE_PATH=/lib/modules/dhd.ko
MFGDRV_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_mfg.bin
nvram_path=/system/etc/wifi/nvram_mfg.txt
DRV_AP_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_aps.bin
nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=200 dhd_poll=1
DRIVER_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_sta.bin
nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1
DRIVER_APS_FIRMWARE_NAME=bcm4329_aps.bin
DRIVER_STA_FIRMWARE_NAME=bcm4329_sta.bin
INTERFACENAME=eth0
WAPI_SUPPORT=false
SUPP_CONF_FILEPATH=/data/misc/wifi/
SUPP_WAPI_AS_CERT_FILE_PATH=/data/misc/wifi/cert/as/
SUPP_WAPI_USER_CERT_FILE_PATH=/data/misc/wifi/cert/user/
SUPPLICANT_STATUS=wlan.supplicant.status
Original comment by john.b.h...@gmail.com
on 23 Jul 2010 at 5:19
Issue 453 has been merged into this issue.
Original comment by harald....@gmail.com
on 23 Jul 2010 at 8:02
Ok, this does not work. It was just a quick try (shot into the dark).
Basically ... what we know from other device (HTC Evo, Google NexusOne) there
are two different ways to setup master-mode (broadcom bcm4329-chipset). I've
configured the "google-method" for it so far - which doesn't work obiously.
I have to check the source-code of the wifi-driver (which should be a part of
kernel-srouces) first. This takes some time ...
Original comment by harald....@gmail.com
on 23 Jul 2010 at 8:15
Koush and I worked on getting the stock kernel from the vibrant dumped.
Here is the link: http://forum.xda-developers.com/showthread.php?t=733792
Let me know if this helps you guys.
Original comment by john.b.h...@gmail.com
on 23 Jul 2010 at 9:41
Any progress with this? I posted a few items.
Thanks
Original comment by john.b.h...@gmail.com
on 25 Jul 2010 at 4:20
Oh. Could you guys test the following:
1) I assume you have "wireless tether" installed - so the "iwconfig"-binary
which we need later is present.
2) Make sure wifi is disabled.
3) Connect to your phone via adb and become root:
adb shell
su
4) Load the wifi-kernel module and wifi-firmware (we take the one with the
_ap.bin suffix).
insmod /lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcm4329_aps.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=200 dhd_poll=1
5) Lets see if a interface with a "wireless extension" was created:
/data/data/android.tether/bin/iwconfig
(Please report the output here)
Thanks.
Original comment by harald....@gmail.com
on 25 Jul 2010 at 4:43
4) insmod: init_module '/lib/modules/dhd.ko' failed (no such device)
Original comment by drdr...@gmail.com
on 25 Jul 2010 at 5:02
> 4) insmod: init_module '/lib/modules/dhd.ko' failed (no such device)
Oh. Please enable wifi via gui and check which modules were loaded:
adb shell
su
lsmod
Original comment by harald....@gmail.com
on 25 Jul 2010 at 7:54
With WiFi turned on (and connected as a conventional client):
# lsmod
dhd 181460 0 - Live 0xbf195000
vibrator 6744 2 - Live 0xbf191000
s3c_bc 2880 0 - Live 0xbf18b000
s3c_lcd 5060 0 - Live 0xbf184000
pvrsrvkm 205996 44 s3c_bc,s3c_lcd, Live 0xbf14c000
multipdp 30968 1 - Live 0xbf13f000
dpram 194152 10 multipdp, Live 0xbf10a000
param 10132 0 - Live 0xbf105000 (P)
j4fs 65548 1 - Live 0xbf0ef000 (P)
rfs_fat 235456 6 - Live 0xbf0b0000 (P)
rfs_glue 74328 1 rfs_fat, Live 0xbf098000 (P)
fsr_stl 248012 6 j4fs, Live 0xbf056000 (P)
fsr 328428 3 dpram,fsr_stl, Live 0xbf000000 (P)
#
Original comment by bruce.ad...@gmail.com
on 25 Jul 2010 at 8:20
a "lsmod" with disabled wifi please?
Original comment by harald....@gmail.com
on 25 Jul 2010 at 8:42
With WiFi disabled (with a data connection through T-Mobile):
# lsmod
vibrator 6744 2 - Live 0xbf191000
s3c_bc 2880 0 - Live 0xbf18b000
s3c_lcd 5060 0 - Live 0xbf184000
pvrsrvkm 205996 44 s3c_bc,s3c_lcd, Live 0xbf14c000
multipdp 30968 1 - Live 0xbf13f000
dpram 194152 10 multipdp, Live 0xbf10a000
param 10132 0 - Live 0xbf105000 (P)
j4fs 65548 1 - Live 0xbf0ef000 (P)
rfs_fat 235456 6 - Live 0xbf0b0000 (P)
rfs_glue 74328 1 rfs_fat, Live 0xbf098000 (P)
fsr_stl 248012 6 j4fs, Live 0xbf056000 (P)
fsr 328428 3 dpram,fsr_stl, Live 0xbf000000 (P)
#
Original comment by bruce.ad...@gmail.com
on 25 Jul 2010 at 8:45
Just to confim data :
wifi turned OFF
vibrator 6744 2 - Live 0xbf191000
s3c_bc 2880 0 - Live 0xbf18b000
s3c_lcd 5060 0 - Live 0xbf184000
pvrsrvkm 205996 32 s3c_bc,s3c_lcd, Live 0xbf14c000
multipdp 30968 1 - Live 0xbf13f000
dpram 194152 10 multipdp, Live 0xbf10a000
param 10132 0 - Live 0xbf105000 (P)
j4fs 65548 1 - Live 0xbf0ef000 (P)
rfs_fat 235456 6 - Live 0xbf0b0000 (P)
rfs_glue 74328 1 rfs_fat, Live 0xbf098000 (P)
fsr_stl 248012 6 j4fs, Live 0xbf056000 (P)
fsr 328428 3 dpram,fsr_stl, Live 0xbf000000 (P)
with wifi turned ON
dhd 181460 0 - Live 0xbf22b000
vibrator 6744 2 - Live 0xbf191000
s3c_bc 2880 0 - Live 0xbf18b000
s3c_lcd 5060 0 - Live 0xbf184000
pvrsrvkm 205996 32 s3c_bc,s3c_lcd, Live 0xbf14c000
multipdp 30968 1 - Live 0xbf13f000
dpram 194152 10 multipdp, Live 0xbf10a000
param 10132 0 - Live 0xbf105000 (P)
j4fs 65548 1 - Live 0xbf0ef000 (P)
rfs_fat 235456 6 - Live 0xbf0b0000 (P)
rfs_glue 74328 1 rfs_fat, Live 0xbf098000 (P)
fsr_stl 248012 6 j4fs, Live 0xbf056000 (P)
fsr 328428 3 dpram,fsr_stl, Live 0xbf000000 (P)
if I try to use insmod after wifi turned ON
insmod: init_module '/lib/modules/dhd.ko' failed (File exists)
Original comment by elee...@gmail.com
on 26 Jul 2010 at 1:23
Ok. Could you guys please try 2.0.5-pre4:
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_5-pre4.apk
This probably supports now the galaxy s ... adhoc-mode only at the moment.
Original comment by harald....@gmail.com
on 27 Jul 2010 at 10:42
Confirmed working on vibrant. I have not tested infertructure mode yet though.
Original comment by john.b.h...@gmail.com
on 27 Jul 2010 at 10:46
No infrastructure-mode at the moment. I didn't had much time to investigate the
samsung galaxy s sources.
To be honest ... I don't know why ...
insmod /lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcm4329_aps.bin
nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=200 dhd_poll=1
is NOT working.
Does ...
insmod /lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcm4329_sta.bin
nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1
and/or ...
insmod /lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcm4329_mfg.bin
nvram_path=/system/etc/wifi/nvram_mfg.txt
work?
Please provide the output of "dmesg" too.
Original comment by harald....@gmail.com
on 27 Jul 2010 at 11:08
It works on the Captivate in adhoc-mode.
Original comment by DannyFritz
on 27 Jul 2010 at 11:13
That's 2 for the Captivate in adhoc!
I love you guys and donations are well deserved!!!!
Thanks for all the hard work.
Original comment by jcab...@gmail.com
on 27 Jul 2010 at 11:28
Great work. :)
now lets ses infatructure please? :) with a cherry on top?
Original comment by john.b.h...@gmail.com
on 27 Jul 2010 at 11:38
I've seen in the vibrant forum @xda that stopping makes troubles?
http://forum.xda-developers.com/showthread.php?t=737344
Could somebody please verify if a "unknown state"-message appears after
pressing the stop-button?
If this is really an issue.
Please check:
adb shell
su
cat /proc/sys/net/ipv4/ip_forward
(report the output - should be 0)
ps
(report the output)
Original comment by harald....@gmail.com
on 27 Jul 2010 at 11:40
I sometimes see unknown state when I press stop. And both wifi images show up.
But it didn't seem to matter when I clicked the on button again.
Original comment by DannyFritz
on 27 Jul 2010 at 11:43
That's bad :-(
Could somebody please check what I've asked in #28 AFTER you hit the
stop-button (when getting the "unknown state" message)?
Original comment by harald....@gmail.com
on 27 Jul 2010 at 11:46
Does NOT work for me on the Vibrant. I had it working on my G1 so I don't
think I have any issues with the wifi tether app config or the client wifi
config.
It seems to work on the phone and the log seems okay, and the SSID is
broadcast. But the client never connects. When turning off wifi tether I get
the "unknown state" message. cat /proc/sys/net/ipv4/ip_forward results in "1"
while in the unknown state.
Bluetooth doesn't work for me either; when turning Bluetooth on it goes into
unknown state and there's no way to get out of it.
I don't have adb working right now, only a terminal emulator, so I can't easily
report the output of ps. Let me know if there is something in ps I should be
looking for; otherwise I'll work on getting adb set up on my computer.
Original comment by marginof...@gmail.com
on 27 Jul 2010 at 11:49
D/TETHER -> CoreTask( 2958): Root-Command ==> su -c
"/data/data/android.tether/bin/tether stop 1"
I/AudioHardwareALSA( 2207): Initialized ALSA PLAYBACK device
AndroidPlayback_Speaker_normal
D/AudioHardwareALSA( 2207): Set PLAYBACK PCM format to S16_LE (Signed 16 bit
Little Endian)
D/AudioHardwareALSA( 2207): Using 2 channels for PLAYBACK.
D/AudioHardwareALSA( 2207): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 2207): Buffer size: 4096
D/AudioHardwareALSA( 2207): Latency: 92879
W/Parcel ( 2255): Attempt to read object from Parcel 0x4ea1dde0 at offset 716
that is not in the object list
I/ActivityManager( 2255): Starting activity: Intent {
act=android.intent.action.MAIN flg=0x58000000 pkg=com.noshufou.android.su
cmp=com.noshufou.android.su/.SuRequest (has extras) }
D/SuRequest( 2703): Sending result: ALLOW
D/su ( 3040): 10144 /system/bin/sh executing 0
/data/data/android.tether/bin/tether stop 1
D/TETHER -> MainActivity( 2958): Calling onResume()
I/WifiHW ( 3041): wifi_unload_driver: enter
D/WifiHW ( 3041): Unable to unload driver module "": No such file or directory
E/WifiHW ( 3041): wifi_unload_driver: error exit
D/TETHER -> CoreTask( 2958): Root-Command error, return code: 1792
I/NotificationService( 2255): enqueueToast pkg=android.tether
callback=android.app.ITransientNotification$Stub$Proxy@47b2c500 duration=1
D/dalvikvm( 2958): GC freed 11175 objects / 572448 bytes in 30ms
W/InputManagerService( 2255): Window already focused, ignoring focus gain of:
com.android.internal.view.IInputMethodClient$Stub$Proxy@47b1d4d0
W/PowerManagerService( 2255): Timer 0x7->0x3|0x3
I/PowerManagerService( 2255): ULight 7->3 f0
I/AudioHardwareALSA( 2207): Output standby called!!. Turn off PCM device.
I/PowerManagerService( 2255): ULight 3->7 f0
I/StatusBarPolicy( 2255): BAT. status:2 health:2
W/PowerManagerService( 2255): Timer 0x7->0x3|0x0
I/PowerManagerService( 2255): ULight 7->3 f0
Original comment by john.b.h...@gmail.com
on 27 Jul 2010 at 11:52
Output from PS on the Vibrant in "unknown state":
root 1 0 372 248 c0402588 0001411c S /init
root 2 0 0 0 c03accd4 00000000 S kthreadd
root 3 2 0 0 c039d80c 00000000 S ksoftirqd/0
root 4 2 0 0 c03c8158 00000000 S watchdog/0
root 5 2 0 0 c03a92bc 00000000 S events/0
root 6 2 0 0 c03a92bc 00000000 S khelper
root 12 2 0 0 c03a92bc 00000000 S suspend
root 234 2 0 0 c03a92bc 00000000 S kblockd/0
root 242 2 0 0 c0564adc 00000000 S kseriod
root 265 2 0 0 c03a92bc 00000000 S kmmcd
root 271 2 0 0 c03a92bc 00000000 S bluetooth
root 304 2 0 0 c03d4ff0 00000000 S pdflush
root 305 2 0 0 c03d4ff0 00000000 S pdflush
root 306 2 0 0 c03d8f1c 00000000 S kswapd0
root 308 2 0 0 c03a92bc 00000000 S aio/0
root 907 2 0 0 c04da26c 00000000 S kapmd
root 1017 2 0 0 c03a92bc 00000000 S spi_gpio.3
root 1032 2 0 0 c03a92bc 00000000 S fsa9480_workque
root 1040 2 0 0 c0558cd8 00000000 S usb_mass_storag
root 1077 2 0 0 c03a92bc 00000000 S kondemand/0
root 1083 2 0 0 c03a92bc 00000000 S gp2a_wq
root 1121 2 0 0 c06a650c 00000000 S krfcommd
root 1122 2 0 0 c03a92bc 00000000 S krxrpcd/0
root 1134 2 0 0 c03a92bc 00000000 S melfas_touchkey
root 1136 2 0 0 c0591748 00000000 S mmcqd
root 1146 2 0 0 c03a92bc 00000000 S qt602240_wq
root 1157 2 0 0 c0591748 00000000 S mmcqd
root 1170 2 0 0 c03a92bc 00000000 S pmic_int_wq
root 2164 2 0 0 bf1407f8 00000000 S multipdp
root 2174 2 0 0 c03a92bc 00000000 S pvr_timer/0
root 2187 2 0 0 bf1916d0 00000000 D TouchSense Play
root 2189 1 284 132 c04c7efc 00015eac S /system/bin/sh
system 2192 1 780 264 c059cee4 afe0ca0c S
/system/bin/servicemanager
root 2193 1 832 392 c0402588 afe0cb34 S /system/bin/vold
root 2194 1 644 244 c05cc6e8 afe0d3cc S /system/bin/debuggerd
radio 2195 1 5516 892 ffffffff bec48cb0 S /system/bin/efsd
root 2200 1 7496 788 ffffffff afe0d3cc S /system/bin/drexe
root 2201 2 0 0 c03a92bc 00000000 S pvr_workqueue
root 2202 1 7436 856 c03b9980 afe0d9c4 S /system/bin/npsmobex
root 2204 1 150884 28644 c0402588 afe0cb34 S zygote
media 2205 1 42696 7124 ffffffff afe0ca0c S /system/bin/mediaserver
root 2206 1 8332 1180 ffffffff afe0d9c4 S /system/bin/agpsd
bluetooth 2208 1 1084 504 c0402588 bebaa858 S /system/bin/dbus-daemon
root 2209 1 768 316 c065bcc4 afe0c76c S /system/bin/installd
compass 2212 1 5424 724 ffffffff afe0ca0c S
/system/bin/sensorserver_yamaha
keystore 2214 1 1616 408 c05cc6e8 afe0d3cc S /system/bin/keystore
root 2219 1 320 144 c0402588 0001025c S /system/bin/immvibed
root 2220 1 296 108 c05cc6e8 0000a334 S /system/bin/immvbsd
system 2221 1 18268 3060 ffffffff afe0ca0c S /system/bin/tvoutserver
radio 2247 1 13512 2144 ffffffff bea597d4 S /system/bin/rild
system 2251 2204 305544 64408 ffffffff afe0ca0c S system_server
app_37 2301 2204 224468 28756 ffffffff afe0d9c4 S
com.swype.android.inputmethod
radio 2303 2204 220412 27208 ffffffff afe0d9c4 S com.android.phone
app_47 2306 2204 229140 26216 ffffffff afe0d9c4 S android.process.media
app_1 2310 2204 234500 33808 ffffffff ad0172dc R
com.sec.android.app.twlauncher
app_8 2316 2204 239116 27836 ffffffff afe0d9c4 S com.google.process.gapps
system 2320 2204 228484 29676 ffffffff afe0d9c4 S com.android.settings
app_1 2364 2204 213552 25524 ffffffff afe0d9c4 S android.process.acore
app_6 2377 2204 204796 20692 ffffffff afe0d9c4 S
com.google.android.apps.uploader
system 2393 2204 204876 20060 ffffffff afe0d9c4 S
com.sec.android.app.servicemodeapp
app_1 2407 2204 221040 21212 ffffffff afe0d9c4 S
com.sec.android.widgetapp.infoalarm
app_27 2417 2204 204680 19828 ffffffff afe0d9c4 S
com.android.samsung.IcsService
app_78 2420 2204 210832 21476 ffffffff afe0d9c4 S
com.sec.android.app.clockpackage
app_29 2429 2204 204356 23876 ffffffff afe0d9c4 S com.amazon.mp3
app_33 2438 2204 209396 21972 ffffffff afe0d9c4 S com.sec.android.app.sns
app_39 2447 2204 204988 21800 ffffffff afe0d9c4 S
com.oz.mobile.android.voicemail.application
system 2454 2204 212740 20048 ffffffff afe0d9c4 S
com.sec.android.app.factorytest
app_43 2463 2204 206984 22588 ffffffff afe0d9c4 S com.wssyncmldm
app_1 2474 2204 204760 20724 ffffffff afe0d9c4 S
com.sec.android.provider.logsprovider
app_45 2484 2204 215012 19924 ffffffff afe0d9c4 S
com.google.android.partnersetup
app_50 2501 2204 212232 20456 ffffffff afe0d9c4 S
com.telenav.app.android.telenav
app_52 2508 2204 202656 20476 ffffffff afe0d9c4 S
com.sec.android.app.drmua:remote
app_54 2516 2204 211228 23968 ffffffff afe0d9c4 S com.android.calendar
app_62 2524 2204 202756 21040 ffffffff afe0d9c4 S
com.sec.android.providers.downloads
app_47 2534 2204 203740 20860 ffffffff afe0d9c4 S
com.sec.android.providers.drm
app_67 2541 2204 206992 24676 ffffffff afe0d9c4 S com.android.mms
app_68 2555 2204 207112 22764 ffffffff afe0d9c4 S com.android.email
app_80 2579 2204 202700 20464 ffffffff afe0d9c4 S com.android.voicedialer
app_103 2586 2204 207288 21688 ffffffff afe0d9c4 S
com.koushikdutta.rommanager
app_98 2593 2204 204884 21260 ffffffff afe0d9c4 S mobi.qiss.plurq
app_55 2601 2204 207776 22624 ffffffff afe0d9c4 S com.tmobile.selfhelp
app_75 2608 2204 214348 24384 ffffffff afe0d9c4 S
com.google.android.apps.maps:FriendService
app_17 2615 2204 207196 20376 ffffffff afe0d9c4 S
com.android.MtpApplication
app_21 2622 2204 221092 25080 ffffffff afe0d9c4 S com.cooliris.media
app_58 2631 2204 204996 21912 ffffffff afe0d9c4 S com.google.android.gm
app_88 2645 2204 206240 26404 ffffffff afe0d9c4 S android.tether
app_87 2704 2204 203168 22960 ffffffff afe0d9c4 S com.noshufou.android.su
root 2720 2 0 0 c03b15ec 00000000 S iscan_sysioc
root 2721 2 0 0 c03b15ec 00000000 S dhcp_sysioc
root 2722 2 0 0 c03b15ec 00000000 S dhd_watchdog
root 2723 2 0 0 c03b15ec 00000000 S dhd_dpc
root 2724 2 0 0 c03b15ec 00000000 S dhd_sysioc
app_79 2807 2204 235540 35420 ffffffff afe0d9c4 S com.android.vending
app_51 2858 2204 206880 21044 ffffffff afe0d9c4 S com.slacker.radio
app_85 2866 2204 202604 19680 ffffffff afe0d9c4 S com.svox.pico
app_105 2874 2204 206084 22892 ffffffff afe0d9c4 S jackpal.androidterm
wifi 2952 1 2016 1072 c0402588 afe0cb34 S
/system/bin/wpa_supplicant
app_76 3046 2204 238312 31728 ffffffff afe0d9c4 S com.sec.android.app.music
app_105 3055 2874 284 152 c04c7efc 00015eac S /system/bin/sh
shell 3078 1 3368 184 ffffffff 0000f444 S /sbin/adbd
shell 3091 3078 284 152 c039b390 0001cddc S /system/bin/sh
shell 3094 3091 856 340 00000000 afe0c76c R ps
Original comment by marginof...@gmail.com
on 27 Jul 2010 at 11:55
# cat /proc/sys/net/ipv4/ip_forward
1
#
(I don't have 'adb' handy at the moment and can't figure out how to copy/paste
multiple pages out of the terminal on the device itself.)
Original comment by bruce.ad...@gmail.com
on 28 Jul 2010 at 12:10
When its on:
# cat /proc/sys/net/ipv4/ip_forward
1
off:
# cat /proc/sys/net/ipv4/ip_forward
1
Original comment by john.b.h...@gmail.com
on 28 Jul 2010 at 12:15
I start and I can stop. It gets an unknown state on stop and shows two wifi
icons.. one for start tethering which is green and a 2nd one that says stop
which is gray. Show log appears empty
If i press Start Tethering, it looks like it starts up again, but I can't get
dhcp from it. Hope this info helps
Here's the info :
$ su
# cat /proc/sys/net/ipv4/ip_forward
1
# ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 372 256 c0402588 0001411c S /init
root 2 0 0 0 c03accd4 00000000 S kthreadd
root 3 2 0 0 c039d80c 00000000 S ksoftirqd/0
root 4 2 0 0 c03c8158 00000000 S watchdog/0
root 5 2 0 0 c03a92bc 00000000 S events/0
root 6 2 0 0 c03a92bc 00000000 S khelper
root 12 2 0 0 c03a92bc 00000000 S suspend
root 234 2 0 0 c03a92bc 00000000 S kblockd/0
root 242 2 0 0 c0564adc 00000000 S kseriod
root 265 2 0 0 c03a92bc 00000000 S kmmcd
root 271 2 0 0 c03a92bc 00000000 S bluetooth
root 304 2 0 0 c03d4ff0 00000000 S pdflush
root 306 2 0 0 c03d8f1c 00000000 S kswapd0
root 308 2 0 0 c03a92bc 00000000 S aio/0
root 907 2 0 0 c04da26c 00000000 S kapmd
root 1017 2 0 0 c03a92bc 00000000 S spi_gpio.3
root 1032 2 0 0 c03a92bc 00000000 S fsa9480_workque
root 1040 2 0 0 c0558cd8 00000000 S usb_mass_storag
root 1077 2 0 0 c03a92bc 00000000 S kondemand/0
root 1083 2 0 0 c03a92bc 00000000 S gp2a_wq
root 1121 2 0 0 c06a650c 00000000 S krfcommd
root 1122 2 0 0 c03a92bc 00000000 S krxrpcd/0
root 1134 2 0 0 c03a92bc 00000000 S melfas_touchkey
root 1136 2 0 0 c0591748 00000000 S mmcqd
root 1146 2 0 0 c03a92bc 00000000 S qt602240_wq
root 1157 2 0 0 c0591748 00000000 S mmcqd
root 1170 2 0 0 c03a92bc 00000000 S pmic_int_wq
root 2164 2 0 0 bf1407f8 00000000 S multipdp
root 2174 2 0 0 c03a92bc 00000000 S pvr_timer/0
root 2187 2 0 0 bf1916d0 00000000 D TouchSense Play
root 2189 1 716 312 c04c7efc afe0c76c S /system/bin/sh
system 2192 1 780 268 c059cee4 afe0ca0c S
/system/bin/servicemanager
root 2193 1 832 408 c0402588 afe0cb34 S /system/bin/vold
root 2194 1 644 264 c05cc6e8 afe0d3cc S /system/bin/debuggerd
radio 2195 1 5516 972 ffffffff bed37cec S /system/bin/efsd
root 2200 1 7496 668 ffffffff afe0d3cc S /system/bin/drexe
root 2201 2 0 0 c03a92bc 00000000 S pvr_workqueue
root 2202 1 7436 888 c03b9980 afe0d9c4 S /system/bin/npsmobex
root 2204 1 150884 29148 c0402588 afe0cb34 S zygote
media 2205 1 42684 7260 ffffffff afe0ca0c S /system/bin/mediaserver
bluetooth 2206 1 1084 580 c0402588 becda894 S /system/bin/dbus-daemon
root 2207 1 8336 1396 ffffffff afe0d9c4 S /system/bin/agpsd
root 2209 1 768 332 c065bcc4 afe0c76c S /system/bin/installd
compass 2213 1 4404 760 ffffffff afe0ca0c S
/system/bin/sensorserver_yamaha
keystore 2214 1 1616 416 c05cc6e8 afe0d3cc S /system/bin/keystore
root 2218 1 320 144 c0402588 0001025c S /system/bin/immvibed
root 2220 1 296 108 c05cc6e8 0000a334 S /system/bin/immvbsd
system 2222 1 18268 3068 ffffffff afe0ca0c S /system/bin/tvoutserver
shell 2224 1 3368 168 ffffffff 0000f444 S /sbin/adbd
radio 2250 1 13496 2276 ffffffff bedc2810 S /system/bin/rild
system 2256 2204 297804 62224 ffffffff afe0ca0c S system_server
app_37 2323 2204 220408 26860 ffffffff afe0d9c4 S
com.swype.android.inputmethod
radio 2325 2204 224532 29932 ffffffff afe0d9c4 S com.android.phone
app_47 2328 2204 209556 23848 ffffffff afe0d9c4 S android.process.media
app_1 2332 2204 241952 35520 ffffffff afe0d9c4 S
com.sec.android.app.twlauncher
app_8 2346 2204 234000 29200 ffffffff afe0d9c4 S com.google.process.gapps
app_6 2367 2204 204796 21068 ffffffff afe0d9c4 S
com.google.android.apps.uploader
app_1 2400 2204 217616 27712 ffffffff afe0d9c4 S android.process.acore
app_29 2404 2204 204352 24092 ffffffff afe0d9c4 S com.amazon.mp3
app_39 2414 2204 204988 22436 ffffffff afe0d9c4 S
com.oz.mobile.android.voicemail.application
app_62 2423 2204 202752 21276 ffffffff afe0d9c4 S
com.sec.android.providers.downloads
app_33 2428 2204 209288 22164 ffffffff afe0d9c4 S com.sec.android.app.sns
system 2439 2204 210604 23080 ffffffff afe0d9c4 S com.android.settings
system 2448 2204 204876 20376 ffffffff afe0d9c4 S
com.sec.android.app.servicemodeapp
app_1 2457 2204 221036 22964 ffffffff afe0d9c4 S
com.sec.android.widgetapp.infoalarm
app_27 2465 2204 204680 20120 ffffffff afe0d9c4 S
com.android.samsung.IcsService
app_78 2471 2204 210836 22944 ffffffff afe0d9c4 S
com.sec.android.app.clockpackage
system 2479 2204 212740 20468 ffffffff afe0d9c4 S
com.sec.android.app.factorytest
app_43 2488 2204 206972 22800 ffffffff afe0d9c4 S com.wssyncmldm
app_1 2493 2204 204744 20952 ffffffff afe0d9c4 S
com.sec.android.provider.logsprovider
app_45 2504 2204 215012 20184 ffffffff afe0d9c4 S
com.google.android.partnersetup
app_50 2520 2204 212232 22480 ffffffff afe0d9c4 S
com.telenav.app.android.telenav
app_52 2527 2204 202660 20712 ffffffff afe0d9c4 S
com.sec.android.app.drmua:remote
app_54 2535 2204 211600 27448 ffffffff afe0d9c4 S com.android.calendar
app_47 2548 2204 203740 21088 ffffffff afe0d9c4 S
com.sec.android.providers.drm
app_67 2556 2204 206932 24976 ffffffff afe0d9c4 S com.android.mms
app_68 2573 2204 207108 23020 ffffffff afe0d9c4 S com.android.email
app_80 2596 2204 202700 20696 ffffffff afe0d9c4 S com.android.voicedialer
app_75 2604 2204 214348 24944 ffffffff afe0d9c4 S
com.google.android.apps.maps:FriendService
app_88 2611 2204 215172 25208 ffffffff afe0d9c4 S
com.google.android.apps.googlevoice
app_17 2619 2204 203100 20608 ffffffff afe0d9c4 S
com.android.MtpApplication
root 2649 2 0 0 c03d4ff0 00000000 S pdflush
app_58 2652 2204 207048 22596 ffffffff afe0d9c4 S com.google.android.gm
app_79 2688 2204 208164 25140 ffffffff afe0d9c4 S com.android.vending
app_21 2759 2204 227884 23308 ffffffff afe0d9c4 S com.cooliris.media
app_23 2774 2204 207060 25020 ffffffff afe0d9c4 S
com.sec.android.app.myfiles
app_81 2792 2204 209712 24480 ffffffff afe0d9c4 S
com.android.packageinstaller
app_51 2799 2204 206880 21376 ffffffff afe0d9c4 S com.slacker.radio
app_86 2806 2204 202768 21536 ffffffff afe0d9c4 S com.noshufou.android.su
app_85 2815 2204 202604 19904 ffffffff afe0d9c4 S com.svox.pico
app_34 2821 2204 208328 23556 ffffffff afe0d9c4 S com.layar
app_91 2835 2204 210156 31000 ffffffff afe0d9c4 S android.tether
root 2889 2 0 0 c03b15ec 00000000 S iscan_sysioc
root 2890 2 0 0 c03b15ec 00000000 S dhcp_sysioc
root 2891 2 0 0 c03b15ec 00000000 S dhd_watchdog
root 2892 2 0 0 c03b15ec 00000000 S dhd_dpc
root 2893 2 0 0 c03b15ec 00000000 S dhd_sysioc
wifi 2973 1 2012 1060 c0402588 afe0cb34 S
/system/bin/wpa_supplicant
shell 2981 2224 716 332 c039b390 afe0d66c S /system/bin/sh
root 2982 2981 716 332 c039b390 afe0d66c S sh
root 2986 2982 856 340 00000000 afe0c76c R ps
Original comment by elee...@gmail.com
on 28 Jul 2010 at 11:36
Ok, it looks like that ip-forwarding is not disabled.
So ... a "cat /proc/sys/net/ipv4/ip_forward" return 1 which is wrong (should be
0).
I've changed the sequence for the shutdown a bit. Please try -pre5:
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_5-pre5.apk
I don't have this issue on my devices (don't have a galaxy s) ... so I'm not
sure if these changes have any effect.
If this does not resolve this problem - please try to start/stop from
commandline:
adb shell
su
cd /data/data/android.tether/bin
./tether start 1
./tether stop 1
(Please report the output.)
Original comment by harald....@gmail.com
on 28 Jul 2010 at 2:38
With 2_0_5-pre5 shutdown gives no indication of error and
"cat /proc/sys/net/ipv4/ip_forward" gives a "0" (after shutdown).
Original comment by bruce.ad...@gmail.com
on 28 Jul 2010 at 2:47
# ./tether start 1
about to run: [/data/data/android.tether/bin/ifconfig eth0 192.168.2.254
netmask 255.255.255.0]
about to run: [/data/data/android.tether/bin/ifconfig eth0 up]
about to run: [/data/data/android.tether/bin/iwconfig eth0 mode ad-hoc]
Error for wireless request "Set Mode" (8B06) :
SET failed on device eth0 ; Invalid argument.
about to run: [/data/data/android.tether/bin/iwconfig eth0 essid AndroidTether]
about to run: [/data/data/android.tether/bin/iwconfig eth0 channel 6]
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Invalid argument.
about to run: [/data/data/android.tether/bin/iwconfig eth0 commit]
Error for wireless request "Commit changes" (8B00) :
SET failed on device eth0 ; Invalid argument.
about to run: [/data/data/android.tether/bin/iptables -N wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -m
state --state ESTABLISHED,RELATED -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -s
192.168.2.0/24 -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -p 47
-j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -j
DROP]
about to run: [/data/data/android.tether/bin/iptables -A FORWARD -j
wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -I POSTROUTING -s
192.168.2.0/24 -j MASQUERADE]
about to run: [/data/data/android.tether/bin/dnsmasq -i eth0
--resolv-file=/data/data/android.tether/conf/resolv.conf
--conf-file=/data/data/android.tether/conf/dnsmasq.conf]
script result was []
# ./tether stop 2
about to run: [/data/data/android.tether/bin/iptables -D FORWARD -j
wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -X wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/ifconfig eth0 down]
script aborted: Unable to unload wifi-driver: No such file or directory
ui_print Unable to unload wifi-driver: No such file or directory
ui_print
# ./tether stop 2
about to run: [/data/data/android.tether/bin/iptables -D FORWARD -j
wireless-tether]
iptables v1.3.7: Couldn't find target `wireless-tether'
Try `iptables -h' or 'iptables --help' for more information.
about to run: [/data/data/android.tether/bin/ifconfig eth0 down]
script aborted: Unable to unload wifi-driver: No such file or directory
ui_print Unable to unload wifi-driver: No such file or directory
ui_print
#
Original comment by john.b.h...@gmail.com
on 28 Jul 2010 at 2:47
pre5 solves the wifi tether off > unknown state problem for me on my Vibrant,
however, I still can't actually use tethering as clients cannot connect.
Bluetooth is still broken too; it goes into unknown state when Bluetooth
tethering is turned on, although turning it off seems to work properly now.
Original comment by marginof...@gmail.com
on 28 Jul 2010 at 2:55
@marginoferror: First. Some clients (like a Nintendo DS, PSP and Android
devices) are not able to joing ad-hoc networks.
Regarding bluetooth. Please provide some useful information.
1) Change to bluetooth-mode in app-settings.
2) Try to start via gui (this will generate a new config-file which is needed
so we are able to start from commandline).
3) Start from cmd-line:
adb shell
su
cd /data/data/android.tether/bin
./tether start 1
./tether stop 1
(Please report the output.)
Original comment by harald....@gmail.com
on 28 Jul 2010 at 3:18
I am able to connect using captivate pre5.apk no problem. I can join from my
laptop the wireless network without issue and stop the service without errors.
----thanks. on occasion, it did however take two trys as it seems to freeze
when starting which locks up the phone after first attempt to start.
Original comment by spete...@gmail.com
on 28 Jul 2010 at 3:28
Wifi client is a netbook running Ubuntu 10.04. It connected to G1 tether,
although not very reliably so I used Bluetooth on that most of the time. I
will try some different clients.
Bluetooth test results (I rebooted between trying to start Bluetooth in the GUI
and trying to start it from adb to make sure there would be no state conflicts):
$ su
# cd /data/data/android.tether/bin
# ./tether start 1
about to run: [/data/data/android.tether/bin/pand --listen --role NAP --devup
/data/data/android.tether/bin/blue-up.sh --devdown
/data/data/android.tether/bin/blue-down.sh --pidfile
/data/data/android.tether/var/pand.pid]
Failed to open control socket: Protocol not supported
about to run: [/data/data/android.tether/bin/iptables -N wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -m
state --state ESTABLISHED,RELATED -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -s
192.168.2.0/24 -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -p 47
-j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -j
DROP]
about to run: [/data/data/android.tether/bin/iptables -A FORWARD -j
wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -I POSTROUTING -s
192.168.2.0/24 -j MASQUERADE]
script result was []
# ./tether stop 1
about to run: [/data/data/android.tether/bin/iptables -D FORWARD -j
wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -X wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/pand -K]
Failed to open control socket: Protocol not supported
script result was []
#
Original comment by marginof...@gmail.com
on 28 Jul 2010 at 3:29
@john.b.hale:
Regarding these two errors:
about to run: [/data/data/android.tether/bin/iwconfig eth0 mode ad-hoc]
Error for wireless request "Set Mode" (8B06) :
SET failed on device eth0 ; Invalid argument.
about to run: [/data/data/android.tether/bin/iwconfig eth0 essid AndroidTether]
about to run: [/data/data/android.tether/bin/iwconfig eth0 channel 6]
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Invalid argument.
... can this reproduced each time?
What does "/data/data/android.tether/bin/iwconfig" return after you have
started tethering?
And ... are you able to change the channel (after you have started tethering)
from commandline?
Try:
/data/data/android.tether/bin/iwconfig eth0 channel 4
What is the output of "/data/data/android.tether/bin/iwconfig" after this?
Original comment by harald....@gmail.com
on 28 Jul 2010 at 3:29
Hmm, this is a new one. I was trying various things to get Wifi working, which
involved rebooting my phone multiple times. This time when I tried to launch
Wifi after rebooting (with a new SSID and with WEP turned off), the phone
completely froze on the "Start Tethering" screen and doesn't respond in any
way, even to me removing the charge cable.
Original comment by marginof...@gmail.com
on 28 Jul 2010 at 3:50
@marginoferror:
"Failed to open control socket: Protocol not supported" ... indicates that BNEP
(CONFIG_BT_BNEP) is missing in your kernel.
Regarding ubuntu ... check: https://help.ubuntu.com/community/WifiDocs/Adhoc
Original comment by harald....@gmail.com
on 28 Jul 2010 at 7:01
Thanks for the link, I will try to use CLI tools to get ad hoc wifi working. As
for Bluetooth, it sounds like no Bluetooth networking will ever work on the
stock Vibrant 2.1 kernel?
Original comment by marginof...@gmail.com
on 28 Jul 2010 at 7:12
@marginoferror: PAN networking will not work with the stock-kernel (I think).
DUN will work and there are paid-apps available on market for that ...
Original comment by harald....@gmail.com
on 28 Jul 2010 at 7:18
Understood.
I did resolve the issue I was having with using my netbook as a wifi client
(had to install a backported kernel image from Ubuntu 10.10 testing to take
advantage of a new Broadcom wifi driver). As you thought, there was not an
issue with the wifi-tether. Thank you as always for your assistance.
Original comment by marginof...@gmail.com
on 29 Jul 2010 at 5:18
have downloaded the 2 0 5 pre 5 and it is working on my captivate... no
errors... buddy can connect to it on his iphone 4 but i can not connect on my
laptop... any ideas
Original comment by cermak.a...@gmail.com
on 29 Jul 2010 at 9:33
Original issue reported on code.google.com by
john.b.h...@gmail.com
on 20 Jul 2010 at 7:52