Closed GoogleCodeExporter closed 9 years ago
Do you have root-permission on this device? Could you please press "menu",
choose
"Show log" and post the output?
To be honest ... I'm a bit jealous about that hero :-)
Original comment by harald....@gmail.com
on 4 Aug 2009 at 5:08
Haha, I got it last week. Very pleased with it. Still quite buggy but that
should all
be ironed out.
Yes, I should have root permission. Have Superuser Whitelist installed so when
I run
the app it pops up asking to allow or deny root access. Am assuming that means
its
working.
On 1.51, doing menu and show log displays a full list of green "done"s. from
top to
bottom:
loading wlan.ko
config wifi interface
config network interface
setting up firewall rules
enabling IP forwarding
starting dnsmasq
It's odd, in the top bar where it normally has two arrows for internet access.
Up for
upload and down for download. Whilst running wifi tether I never see the down
arrow...?
Original comment by tom.ox...@gmail.com
on 4 Aug 2009 at 5:23
Fuuu ... let's do some checks.
On your phone:
- Open terminal emulator (download from android market) or use adb
1) Check if ip-forwarding is enabled:
type: cat /proc/sys/net/ipv4/ip_forward
This should return "1".
2) Check if a dnsmasq-process is running.
type: ps
You should find a line similiar to this:
root 713 1 784 332 c00afc70 afe0c584 S
/data/data/android.tether/bin/dnsmasq
On your client/pc:
- Open a command-prompt.
1) Check the wifi-interface.
type: ipconfig
Look for the wireless adapter. On my german win7 it looks like this:
Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
Verbindungsspezifisches DNS-Suffix:
Verbindungslokale IPv6-Adresse . : fe80::852b:c1fe:2930:365c%14
IPv4-Adresse . . . . . . . . . . : 192.168.2.103
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.2.254
2) Are you able to ping the gateway?
ping 192.168.2.254
example-output:
C:\Users\Harry>ping 192.168.2.254
Ping wird ausgeführt für 192.168.2.254 mit 32 Bytes Daten:
Antwort von 192.168.2.254: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.2.254: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.2.254: Bytes=32 Zeit=5ms TTL=64
Antwort von 192.168.2.254: Bytes=32 Zeit=4ms TTL=64
Ping-Statistik für 192.168.2.254:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 4ms, Maximum = 5ms, Mittelwert = 4ms
3) Does the DNS (translation of domainnames) work?
type: nslookup android.com 192.168.2.254
example-output:
C:\Users\Harry>nslookup android.com 192.168.2.254
Server: UnKnown
Address: 192.168.2.254
Nicht autorisierende Antwort:
Name: android.com
Addresses: 74.125.47.99
74.125.91.99
74.125.95.99
Please post your results.
Thanks.
Original comment by harald....@gmail.com
on 4 Aug 2009 at 5:58
Ok I have performed the required PC checks. Running on Win XP. Checks didn't
look
promising... :s
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network
Connection
Physical Address. . . . . . . . . : 00-16-6F-11-B5-EA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.103
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.254
DHCP Server . . . . . . . . . . . : 192.168.2.254
DNS Servers . . . . . . . . . . . : 192.168.2.254
Lease Obtained. . . . . . . . . . : 04 August 2009 22:39:10
Lease Expires . . . . . . . . . . : 05 August 2009 10:39:10
C:\Documents and Settings\Thomas Oxton>ping 192.168.2.254
Pinging 192.168.2.254 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.2.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Documents and Settings\Thomas Oxton>nslookup android.com 192.168.2.254
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.2.254: Timed out
Server: UnKnown
Address: 192.168.2.254
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
_____________
However for the device checks, I can't find a terminal emulator that works with
the
hero's soft keyboard so, if I use ADB what is the command line I need to use to
get
onto the device?
Is it just "adb shell mount /system" ?
Original comment by tom.ox...@gmail.com
on 4 Aug 2009 at 9:49
Don't worry about those last questions about adb, realised was just an "adb
shell"
job
Here are results:
$ cat /proc/sys/net/ipv4/ip_forward
cat /proc/sys/net/ipv4/ip_forward
1
$ ps
ps
root 616 1 784 360 c00befd4 afe0c584 S
/data/data/android.tether/bin/dnsmasq
** Have deleted all the other lines. Can send as well if you need them too.
Thanks.
Original comment by tom.ox...@gmail.com
on 4 Aug 2009 at 10:17
Mmmmh ... the weird thing is that you get an ip-address (from the phone via
dhcp) but
you are not able to ping the gateway.
What happens if you do:
- command-prompt:
ipconfig /release
ipconfig /renew
Do you get a "valid" ip-address (something like 192.168.2.xxx)?
Are you sure that there is not a personal firewall or something which is
blocking
traffic?
Original comment by harald....@gmail.com
on 5 Aug 2009 at 9:38
OK, this time I turned off my firewall just to be sure..
Here are the results. Now the Ping works, which is strange.
C:\Documents and Settings\Thomas Oxton>ping 192.168.2.254
Pinging 192.168.2.254 with 32 bytes of data:
Reply from 192.168.2.254: bytes=32 time=5ms TTL=64
Reply from 192.168.2.254: bytes=32 time=3ms TTL=64
Reply from 192.168.2.254: bytes=32 time=9ms TTL=64
Reply from 192.168.2.254: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.2.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 9ms, Average = 5ms
C:\Documents and Settings\Thomas Oxton>nslookup android.com 192.168.2.254
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.2.254: Timed out
Server: UnKnown
Address: 192.168.2.254
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
________________________________
However, when i do the release and renew ip, after trying to renew it says:
An error occured while renewing the interface Wireles Network Connection:
Unable to
contact your DHCP server. Request timed out.
Original comment by tom.ox...@gmail.com
on 5 Aug 2009 at 9:56
Do you know if the kernel you are using supports netfilter/iptables? Have you
replaced the stock kernel by a custom one?
Original comment by harald....@gmail.com
on 6 Aug 2009 at 7:31
Is there a quick way to check for netfilter/iptable support through the
terminal??
In order to root I had to use a different recovery image, however I think the
kernel
should be the same?
Original comment by tom.ox...@gmail.com
on 6 Aug 2009 at 11:22
I have the same problem with my Hero. I get an IP-address from my phone, but i
cannot
ping the gateway. If i do ipconfig /renew i get "unable to contact your DHCP
server".
I am running the original Hero ROM, and used this guide to get root:
http://forum.xda-
developers.com/showthread.php?t=543571
Root access seems to work.
Original comment by willem.stoker
on 7 Aug 2009 at 6:29
I used the same guide.
So frustrating really want this to work :(.
@willem Any idea about netfilter/iptable support?
Are you on t-mo/orange or sim free?
Original comment by tom.ox...@gmail.com
on 7 Aug 2009 at 6:42
@tom I have simlock-free Hero, and i'm using Vodafone.
I'm not sure if there is netfilter/iptable support in this kernel. If there was
no
netfilter/iptable support, I expect to get the message "No Netfilter" on
startup
(according to the wiki FAQ in this project).
I don't get any messages, everything seems fine.
Do you know a way to test if rooting was successful?
Original comment by willem.stoker
on 7 Aug 2009 at 6:57
yer there is, i can only do it through adb but I assume is the same for
terminal on
the hero:
(providing you installed superuser..)
type:
adb shell
su
should come up with a message on the phone asking for root permissions. click
yes and
then that proves is rooted.
Original comment by tom.ox...@gmail.com
on 7 Aug 2009 at 7:15
To check if your kernel supports ip-tables/netfilter do the following:
1) Copy the kernel-config from you phone to your computer
adb pull /proc/config.gz .
2) Extract the config.gz-file with winrar, 7zip or any other program which can
handle
.gz-files.
3) Open the (extracted) config file in a text-editor and look for such a line:
CONFIG_NETFILTER=y
And ... I could take a look to that file if you post it here.
Original comment by harald....@gmail.com
on 7 Aug 2009 at 9:26
It looks OK:
CONFIG_ANDROID_PARANOID_NETWORK=y
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
See attachment for the compelete file
Original comment by willem.stoker
on 7 Aug 2009 at 9:51
Attachments:
Yes, I think I get exactly the same. However here it is anyway.. thanks.
Original comment by tom.ox...@gmail.com
on 7 Aug 2009 at 11:05
Attachments:
Could you guys please pull an additional config-file from your phones and post
it here?
adb pull /system/etc/wifi/tiwlan.ini .
Original comment by harald....@gmail.com
on 8 Aug 2009 at 9:05
Sure, here it is.
Original comment by tom.ox...@gmail.com
on 8 Aug 2009 at 9:14
Attachments:
Mine is exactly the same (used a differ to check :))
Original comment by willem.stoker
on 8 Aug 2009 at 1:03
Mmmmh ... ok compared with the one pulled from a G1 I see that 2 entries were
added
to the one of the Hero.
Missing:
BThWlanCoexistParamssenseDisableTimer = 400
TxCompleteThreshold = 10
When tethering is started the app is using a modified G1 configuration-file ...
and
yeah these entries are missing there.
Attached is the original one from G1.
Interesting ... will put something together ... stay tuned.
In the meantime ... could you please try "adb logcat" (command prompt) and look
for
an error when tethering is started?
Original comment by harald....@gmail.com
on 8 Aug 2009 at 2:53
Attachments:
Ok ... here is a modified tiwlan.ini file ... please replace this one by typing:
adb push tiwlan.ini /data/data/android.tether/conf/
(first cd to the directory where attached-file was stored.)
Please check with "adb legcat" when starting up and look for errors.
Original comment by harald....@gmail.com
on 8 Aug 2009 at 3:11
Attachments:
I tried to push your file, but it says:
D:\tools\tools>adb push tiwlan.ini /data/data/android.tether/conf
failed to copy 'tiwlan.ini' to '/data/data/android.tether/conf/tiwlan.ini': Perm
ission denied
Do i need to start adb with root access or something?
I have also checked the log when starting wifi-tether. I don't see any errors.
See
the log attached.
Original comment by willem.stoker
on 8 Aug 2009 at 4:44
Attachments:
I tried copying your file in the adb shell (with root). Still no luck..
# mv /sdcard/tiwlan.ini tiwlan.ini
mv /sdcard/tiwlan.ini tiwlan.ini
failed on '/sdcard/tiwlan.ini' - Cross-device link
Is there another place where i can store the file? Everywhere i try it says
"Read-only
file system"
Original comment by willem.stoker
on 8 Aug 2009 at 5:20
Oh ... adb doesn't provide root-permission by default (on your device) ...
cat /sdcard/tiwlan.ini > /data/data/android.tether/conf/tiwlan.ini
(become root first)
Should do the trick.
Original comment by harald....@gmail.com
on 8 Aug 2009 at 9:24
is it working now?
i have the same issue on my htc magic.
i have the error msg about iptable1.3.7
"cant initialize iptable iptable 'filter':iptables who? (do you need to insmod)
Original comment by HaroldOu...@gmail.com
on 8 Aug 2009 at 9:41
@HaroldOuyang: You need a netfilter-enabled kernel. The hero - as we see in the
config
- has a netfilter-enabled kernel but there is another issue which we currently
try to
solve.
Original comment by harald....@gmail.com
on 8 Aug 2009 at 9:47
setting up firewall rules.. ptable v1.3.7:can’t initiallze iptables table
‘filter’:iptables who?(do you need to
insmod? perhaps iptables or your kernel needs to be upgraded faild.
Original comment by HaroldOu...@gmail.com
on 8 Aug 2009 at 9:50
@HaroldOuyang: You need a netfilter-enabled kernel. And (as far as I know)
there are
firmwares/kernel available for Vodafone-branded magic. I'm not sure about
HTC-branded
magics - I don't own such devices.
Original comment by harald....@gmail.com
on 8 Aug 2009 at 10:01
Tried everything as suggested..
Unfortunately the same issue still occurs. When I did the ping and the nslookup
(without firewall on) both failed again..
Original comment by tom.ox...@gmail.com
on 8 Aug 2009 at 11:37
I have tried the new tiwlan.ini, but still the same issue. I get an IP-address
but i
cannot ping the gateway. Still no errors with logcat, see the log attached.
Original comment by willem.stoker
on 9 Aug 2009 at 7:31
Attachments:
[deleted comment]
I'm a bit confused now - who is able to ping the gateway now?
Tom was able to ping once?!? Please ... check if you got a valid ip-address
(something
like 192.168.2.xxx) and try to ping the gateway from the client. Please also
check if
you are able to ping the client from your phone (using terminal emulator).
And ... please disable the access-control-feature for all those checks.
Original comment by harald....@gmail.com
on 9 Aug 2009 at 8:04
[deleted comment]
Following the replacement with the new tiwlan.ini, I could no longer ping the
gateway.
However I did attain a valid IP of 192.168.2.103.
Previously, I was able to ping after I disabled my firewall with the original
tiwlan.ini file.
Original comment by tom.ox...@gmail.com
on 9 Aug 2009 at 10:06
I have a valid IP address. I tried to ping from my laptop to mobile, and from
mobile to
laptop but both did not work...
Original comment by willem.stoker
on 10 Aug 2009 at 6:25
FYI I'm seeing exactly the same symptoms as Willem and Tom. I have root/su
access
on T-Mobile HTC Hero (G2 Touch). Have verified this with various root tools
I'm now
able to use.
Tether starts with no errors and I can connect my MacBook - I get a valid IP
from
DHCP and the DNS is set too. I will catch-up on some of the testing above for
netfiler and verifying pings from the device etc... but also wanted to see
whether
in yet another environment you'd like more testing to be done.
At one point I thought I was able to get a response/page with an IP address
directly
on my client so perhaps this is a DNS issue but I haven't replicated that again
-
will check again today.
Will run the tests above today, but let me know if you need/want anything else
done.
Thanks!
Original comment by peter.w....@gmail.com
on 12 Aug 2009 at 8:13
Hi peter. Thanks for your report. Could you please check the following:
1) Start tether
2) Connect your PC/MAC
3) Type "cat /proc/net/dev" in terminal emulator (on your phone / can be
downloaded
from market). You should find a interface named "tiwlan0".
4) Try to generate some traffic on your PC/MAC. ping 192.168.2.254 (gateway)
open the
browser ... whatever.
5) Check if the number of packets/bytes increase in the "tiwlan0"-line.
Right now I'm just trying to isolate the problem (I don't own a Hero) ...
Original comment by harald....@gmail.com
on 12 Aug 2009 at 9:18
@Peter
FYI, on the hero use this app for terminal
http://www.cyrket.com/package/com.magicandroidapps.betterterm
The other free terminal apps dont work with the soft keyboard. And use
trackball + M
to enter.
Original comment by willem.stoker
on 12 Aug 2009 at 9:28
Thanks for the responses - a couple of things have just happened... on the
first pass I was able to see pkts
in/out and the response from cat /proc/net/dev is:
tiwlan0: 38859 419 0 0 0 0 0 0 1356
18 0 0 0 0 0 0
I disconnected and reconnected and now my client isn't getting IP from DHCP, no
IP, no Gateway, no DNS -
earlier this was fine and looked good. Now my machine is assigning its own IP
only (this is what it tells me),
and I'm getting no Gateway etc..
I'm out of time now but will try restart everything (already tried resetting
the phone) and try again...
Original comment by peter.w....@gmail.com
on 12 Aug 2009 at 12:28
OK had one last go. The DHCP was wierd.... after a few reconnect attempts,
service stop/start I got a healthy
DHCP assigned address and importantly tether showed my MAC as a connected
client (wasn't when I typed the
above)
I've been assigned: IP 192.168.2.100, Sub 255.255.255.0, Router 192.168.2.254,
DNS 192.168.2.254
Same symptom no page loads in browser. 192.168.2.254 isn't pingable from my
client... however.
cat /proc/net/dev shows bytes received for tiwlan0 and increasing through the
ping, and after cancelling the
ping I tried to browse to google.com and again tiwlan0 showed an increase (you
can see in the tables below) -
also note the UP KB count in tether increases - Down KB count does not...
$ cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier
compressed
lo: 1512 18 0 0 0 0 0 0 1512 18 0 0 0 0 0 0
dummy0: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
rmnet0: 137150 327 0 0 0 0 0 0 76232
629 0 0 0 0 0 0
rmnet1: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
rmnet2: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
usb0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
tiwlan0: 53869 496 0 0 0 0 0 0 4518
42 0 0 0 0 0 0
$ cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier
compressed
lo: 1512 18 0 0 0 0 0 0 1512 18 0 0 0 0 0 0
dummy0: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
rmnet0: 137150 327 0 0 0 0 0 0 76503
631 0 0 0 0 0 0
rmnet1: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
rmnet2: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
usb0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
tiwlan0: 54213 499 0 0 0 0 0 0 4518
42 0 0 0 0 0 0
Original comment by peter.w....@gmail.com
on 12 Aug 2009 at 12:56
Thanks for all of that. Could you please post the output of some more commands:
# iptables -L
If that does not work ...
# /data/data/android.tether/bin/iptables -L
And ...
# netstat -nr
Thanks.
Original comment by harald....@gmail.com
on 12 Aug 2009 at 3:05
I also tried "cat /proc/net/dev", and get the same results as peter. However, i
see
receiving bytes/and packets increasing, even when i'm not pinging. I cannot see
an
greater increase when i start pinging. I also see lots of receiving, but almost
no
transmitting.
Below the output of the commands (via adb shell so i could copy/past)
# iptables -L
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy DROP)
target prot opt source destination
FIX ME! implement getnetbyaddr() bionic/libc/bionic/stubs.c:366
ACCEPT 0 -- 192.168.2.0/24 anywhere
ACCEPT 0 -- anywhere anywhere state RELATED,ESTAB
LISHED
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
# netstat -nr
netstat -nr
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:16650 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:7890 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
tcp 0 0 10.14.35.237:53700 209.85.229.188:5228 ESTABLISHED
tcp 0 1 127.0.0.1:16650 127.0.0.1:37810 CLOSE_WAIT
tcp 0 1 10.14.35.237:57524 74.125.77.113:443 CLOSE_WAIT
udp 0 0 0.0.0.0:53 0.0.0.0:*
udp 0 0 0.0.0.0:67 0.0.0.0:*
Original comment by willem.stoker
on 12 Aug 2009 at 3:35
Output from commands:
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy DROP)
target prot opt source destination
FIX ME! implement getnetbyaddr() bionic/libc/bionic/stubs.c:366
ACCEPT 0 -- 192.168.2.0/24 anywhere
ACCEPT 0 -- anywhere anywhere state
RELATED,ESTABLISHED
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
# netstat -nr
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:16650 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:7890 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
tcp 0 0 10.212.253.253:59713 209.85.229.188:5228 ESTABLISHED
udp 0 0 0.0.0.0:53 0.0.0.0:*
udp 0 0 0.0.0.0:67 0.0.0.0:*
udp 0 0 0.0.0.0:52728 0.0.0.0:*
Hope this helps!! So close... but...
Original comment by peter.w....@gmail.com
on 12 Aug 2009 at 7:07
Hmmm so despite not getting error messages about netfilter support, it looks
like the Hero build of Cupcake,
like the magic, doesn't support iptables.... do you agree? :-( Thanks a lot
for all your help.
Original comment by peter.w....@gmail.com
on 12 Aug 2009 at 10:11
Hello.
I also tried get it work. Your application and many other, but it sems like HTC
made
more changes in kernel than we think..
In theory - they have to relase modified kernel because of license GPL.
In practice - couple of weeks ago they promiss to give sources to the end of
month.
Last month..
Without their changes is impossible (or at least very hard) to run iptables on
hero/
magic.
More details you can find for example (for example, because topics about this
exists
on couple android developers forums) here:
http://forum.xda-developers.com/showthread.php?t=531194&page=8
So - for now we can scream, mail them, mail some organisations like Linux/gpl
and
wait. And don't lose hope..;-)
Original comment by pajter
on 13 Aug 2009 at 10:28
Thanks for the comment pajter... here's a thought to perhaps get the carriers
onto
HTC/Google. Given the assumption is I've contracted to a phone on the open
handset
alliance running a GPL OS that isn't open and is restricted - can I cancel my
T-Mobile contact?? I only signed up to the contract and the phone to enjoy this
flexibility, otherwise I'd have contracted to an iPhone on O2 (here in the UK) -
perhaps if contracted owners of Magic/Hero's can do this, it's a stronger
message...
Original comment by peter.w....@gmail.com
on 13 Aug 2009 at 12:02
[deleted comment]
Oh, don't be such a dramatic. ;)
I think (trying to be optimistic) HTC finally have to give us their kernel
version.
They getting many questions, not only for private owners, but also android
developers and
other peoples with "strong back".
But yes, if after a month or two HTC still be like now "Emm.. we working on new
site, you
know, there will be all sources, books, but give as another couple months or
years" then i
will look around how cancel my contract or switch phone to other.
"Software on this phone is against the law" can be a pretty strong argument.;-)
Original comment by pajter
on 13 Aug 2009 at 12:56
Regarding this issue:
It really looks like that netfilter is enabled in kernel (like it was in all
ADP-firmwares before cupcake). The output of iptables and netstat looks good to
me -
at least I can't recognize a difference to my handset.
There is probably something wrong with the wifi-driver or the interface itself.
One last thing to check/test ... DOES BLUETOOTH-TETHERING WORK?
Missing kernel-sources:
IMHO they are in breach of the GPL.
Original comment by harald....@gmail.com
on 13 Aug 2009 at 2:00
how do you activate bluetooth tethering?
i startet wifi tether in bluetooth mode and tried to pair the laptop (running
on xp)
with it but it always tells me it didn't find a service.
Original comment by nuum...@gmail.com
on 13 Aug 2009 at 4:53
Original issue reported on code.google.com by
tom.ox...@gmail.com
on 4 Aug 2009 at 4:33