Open GoogleCodeExporter opened 9 years ago
rooted HTC legen 1.31.405.4
used also tether 2.0.2pre6 and pre 7
tether starts with no errors.
but no visible wifi!
Original comment by felix41...@googlemail.com
on 18 May 2010 at 7:29
i just tried from adb shell to start tether, here goes output:
# ./tether start 1
about to run: [/system/bin/tiwlan_loader -f /system/etc/wifi/Fw1273_CHIP.bin -e
/proc/calibration -i /system/etc/wifi/tiwlan.ini]
Set property wlan.driver.status = ok - Ok
about to run: [/data/data/android.tether/bin/ifconfig tiwlan0 192.168.2.254
netmask
255.255.255.0]
about to run: [/data/data/android.tether/bin/ifconfig tiwlan0 up]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 mode ad-hoc]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 essid
AndroidTether]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 channel 6]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 commit]
Error for wireless request "Commit changes" (8B00) :
SET failed on device tiwlan0 ; Operation not supported on transport endpoint.
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 key
s:abcdefghijklm]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 key restricted]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 commit]
Error for wireless request "Commit changes" (8B00) :
SET failed on device tiwlan0 ; Operation not supported on transport endpoint.
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 tiwlan0
--resolv-file=/data/data/android.tether/conf/resolv.conf
--conf-file=/data/data/android.tether/conf/dnsmasq.conf]
script result was []
it looks commit fails! :(
Original comment by neq...@gmail.com
on 18 May 2010 at 8:44
No. Commits can fail - this depends on the wifi-driver.
Could you please check the status of the wireless-interface (after you have
started
via GUI):
adb shell
/data/data/android.tether/bin/iwconfig tiwlan0
What's the output?
Original comment by harald....@gmail.com
on 18 May 2010 at 8:47
output after gui tethering was started:
# /data/data/android.tether/bin/iwconfig tiwlan0
tiwlan0 IEEE 802.11ABG ESSID:""
Mode:Ad-Hoc Channel:0 Cell: Not-Associated
Tx-Power:-51 Sensitivity=-80 dBm
RTS thr=4096 B Fragment thr=4096 B
Encryption key:off
Link Quality=0/0 Signal level=-32 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Original comment by neq...@gmail.com
on 18 May 2010 at 8:53
No essid that's the reason why you can't see it. Stay tuned ... will try to fix
that.
Original comment by harald....@gmail.com
on 18 May 2010 at 9:11
Could you please test:
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_2-pre8.apk
Please do ...
# /data/data/android.tether/bin/iwconfig tiwlan0
after you have started tethering again.
Thanks.
Original comment by harald....@gmail.com
on 18 May 2010 at 10:19
Okay, ESSID exists now. But it is still not working :(
tiwlan0 IEEE 802.11ABG ESSID:"AndroidTether"
Mode:Ad-Hoc Channel:6 Cell: 02:00:00:39:F2:AF
Tx-Power:-51 Sensitivity=-80 dBm
RTS thr=4096 B Fragment thr=4096 B
Encryption key:off
Link Quality=0/0 Signal level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Original comment by felix41...@googlemail.com
on 18 May 2010 at 10:29
after I changed the channel from 6 to 11 it worked!
Thanks a lot!
Original comment by felix41...@googlemail.com
on 18 May 2010 at 10:36
Could you please check if "channel 6" is dirty/used by other accesspoints?
That can be checked by using an app called "netstumbler" - available here:
http://www.stumbler.net/
Original comment by harald....@gmail.com
on 18 May 2010 at 10:41
i can confirm, tether works now on HTC legend! :)
Original comment by neq...@gmail.com
on 18 May 2010 at 10:55
The air seems to be clear on channel 6. I checked it with the Wifi Analyzer
app. Only
on channel 12 is another wifi located.
There must be still a different issue. I tried to connect with the following
devices:
- iPad (found & connected)
- Galaxy I7500 (not found)
- another htc legend (not found)
Why doesn't it work on all devices?
Original comment by felix41...@googlemail.com
on 18 May 2010 at 12:03
@felix41382: a client needs to support joining ad-hoc networks. android-device
with
stock firmwares are not able to do that. That's not an app-related issue.
Original comment by harald....@gmail.com
on 18 May 2010 at 12:09
@harald.mue: oh okay, my fault!
Thanks for your help.
Original comment by felix41...@googlemail.com
on 18 May 2010 at 12:30
Could you guys please give the latest test-release a try?
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_2-pre10.apk
Thanks.
Original comment by harald....@gmail.com
on 25 May 2010 at 10:58
sorry for slow response! confirmation - tether 2.0.2pre10 is working perfect on
HTC
legend!
Original comment by neq...@gmail.com
on 27 May 2010 at 7:34
hey, i think i know what the problem is, worked on this for hours today. i am
usung the latest droid-life 2.2 rom (the one that is supposed to be a direct
copy of 2.2)and it looks like wireless tether keeps changing the mac address it
broadcasts while it is trying to connect. I watched this with a couple of
wireless watchers while playing with the droid. Anyway, while watching the
signals, I was able to see that mac address changing left and right until I was
able to get a device connected. Once I connected my laptop (XP) then the mac
address of the droid stopped changing and I was easily able to connect the ipad
and other devices without a problem in the world. Before that, it was just pure
luck of timing getting the ipad to connect, because I think when the mac
address of the droid changed, the ipad took a dump and configures its own
internal 169 address.
I know barnacle tether includes an option to set the mac address, maybe that is
what is needed here too, because this problem happens even on the latest droid
apk 2.02 or whatever it is. Please feel free to contact me for any additional
info. I am writing this on a now tethered computer, but it was hard work, while
streaming youtube on the ipad, so the connection works great once they connect.
Before i figured this out, the ipad would find the wireless and then most of
the time fault when trying to dhcp and instead of getting the right address, it
would drop to the internal 169.xx.xx.xxx
I was also able to get it to connect once or twice by switching the access
control on and off and such until the ipad connected,but i bet it is completely
related to the changing mac address. I have been watching the stream for a half
hour now and the mac address of the droid has stayed the same, before anything
was connected, it would change every 30 seconds or so. Also, I rebooted just to
the rom and only installed the 2.02 apk, nothing else but the stock droid apps,
so hope that helps too.
I also noted that when I install the titanium backup program, it downloads a
newer/older different version of busybox, so maybe that has something to do
with it, but wireless tether has the same issue on both the older version
included in the droid life rom and the newer version that titanium backup
downloads today. I will update his later with what versions they are. Hope this
helps devs, i use 2.1 all the time, but on 2.2 there is this problem or maybe
with the droid itself, i had not played with this under 2.1. I will also post
this as a new solution for ipad/dev issue.
Original comment by sanjo...@gmail.com
on 9 Jun 2010 at 7:28
i have ATT captivate and i tried different versions pre4, pre6, pre7, pre8 and
pre10
except pre4 all other versions , i am not able to see the Wifi AP on any of the
devices
when i install pre4 it shows up on my iphone and laptop with win 7 and works
perfectly but other galaxy devices like ATT captivate and vibrant cannot see
this AP
any help is appreciated.
Thanks
Anil
Original comment by anil...@gmail.com
on 6 Aug 2010 at 8:35
I can confirm the issue that sanjonny posted using 2.0.2 off the market. I
was keeping an eye on the network using wiviz on my DDWRT WRT54GL router.
About every 30 seconds a new network would pop up. I don't think this is rom
specific as I am getting the same issue on both sapphire 1.0.0 and simply
stunning 4.7. It's causing some increased hair loss trying to get my router to
connect in both/either client bridge mode and adhoc mode.
Original comment by Vac...@gmail.com
on 25 Aug 2010 at 6:32
I hope this is the right place. I have a newly rooted
Samsung Galaxy S3 using Android 4.1.1
Using android-wifi-tether-3.2-beta2 (Tried profiles Auto,SamsungS3, Samsung
Nexus CDMA)
Laptop using Intel 6300 wifi
I've read as much as I can find. I've seen reports of problems, but I can't
find a matching bug in the bug tracker.
The wifi just doesn't exist. I tried all combinations.
Original comment by deedee6...@gmail.com
on 3 Jan 2013 at 8:28
I ran a terminal and found some errors when running tether.
The first error was "iwconfig wlan0 mode ad-hoc"
Error for wireless request "Set Mode" (8b06) :
SET failed on device wlan0 ; Operation not supported on transport endpoint.
Original comment by deedee6...@gmail.com
on 3 Jan 2013 at 9:47
I upgraded to android-wifi-tether-3.3pre2. it still doesn't work, but this
error goes away.
Original comment by deedee6...@gmail.com
on 3 Jan 2013 at 10:41
Original issue reported on code.google.com by
neq...@gmail.com
on 17 May 2010 at 3:03