wired_tether_1_3.apk still not working with my rooted Froyo EVO

[GoogleCodeExporter]

What steps will reproduce the problem?
1. When trying to start app, still incorrect kernel error
2. Seems to connect when selecting USB Charge or USB Tether but can't connect 
to website
3. When trying all USB wired options, including HTC Sync, USB drive and above 
other two, somehow my USB ports on my laptop disables requiring a reboot

What is the expected output? What do you see instead?
Kernel error, can't connect to website

What version of the product are you using? On what operating system?
1.3 (r32 I assume). Windows XP sp3

Please provide any additional information below.
HTC Evo 4G Evo rooted with Unrevoked3 and upgraded to Froyo using "HTC OTA 
Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed, see thread here 
http://forum.xda-developers.com/showthread.php?t=743352

Thanks for the effort though is solving this problem, I will keep coming back 
to this site several times a day hopefull to find a working solution.

Original issue reported on code.google.com by RFeuerl...@gmail.com on 17 Aug 2010 at 9:37

[GoogleCodeExporter]

I forgot to amend the "unsupported kernel" message, so currently this will 
show, though it should work despite this message.

Here is the process I go through just to be clear as possible (you shouldn't 
need to deviate on the selections):

I plug in my phone via USB; the normal HTC Sense dialog appears and I leave it 
on Charge Only (don't use the USB tethering option here); go to Wired Tether 
and tell it to start (ignoring the kernel message, as I'll get a patch file fix 
to Harald tonight); computer should find a new device -- follow path below.

If this device has not been installed previously, it will want a driver 
naturally.  To get this driver to install, I followed similar directions to 
that of the Nexus One (http://www.android.com/tether), particularly, for 
Windows XP 32-bit SP3, ignoring steps 3-6 (as this is for the built-in 
tethering).  So this means choosing not to use Windows Update for finding a 
driver, telling it you know where to look for the driver, and browsing to the 
directory where you downloaded the tetherxp.inf file.  Once the driver 
installs, operation should follow similar to below as for when the driver is 
previously installed.

After the device is located (drivers are installed), a new network device 
should appear in your Network Connections, and it will start to find an IP 
address via DHCP.  Soon after, the new network connection should show 
connected, and you should be able to use your phone as your Internet 
connection, with usage details showing up on the phone.

When done, hit the stop tethering as normal, the network connection (from the 
phone) will disappear from your computer, and it should revert to normal 
(allowing you to mount the SD Card as a Disk Drive, and usage of ADB).

Note:  when tethering via USB, you won't currently be able to use the SD Card 
as a Disk Drive, nor be able to use ADB.  This should restore fine once you 
complete tethering.

Also note:  you should avoid using the stock (HTC or FroYo) USB tethering 
features as it can interfere with setup and operation of this app and it will 
get into an unrecognizable state and need a reboot of the PC and/or phone.  
This should not be harmful to either, though, as always, take caution as this 
is all on a non-liable basis.

Original comment by dligh...@gmail.com on 17 Aug 2010 at 11:23

Attachments:

• tetherxp.inf

[GoogleCodeExporter]

I am runninf Fresh Evo 3.1.0.1 with King's latest kernel. Following the steps 
above, I get a FC whenever I try to enable or disable tethering. After the FC 
from enabling, i'll reopen WT and it will have the option to stop tethering, 
and if I click that I get FC again. Any suggestions, sir?

Original comment by ERudnit...@gmail.com on 18 Aug 2010 at 2:19

[GoogleCodeExporter]

ERudnitsky, I'm not too deeply familiar with King's kernel, but I'm not seeing 
anything yet that tips me off as to why you're getting force closes.

If you feel comfortable doing so, would you mind grabbing some LogCat 
information (useful for diagnosing programming issues on Android)?  If you're 
familiar with ADB, there is a fairly easy way to grab the LogCat, rather than 
the typical "adb shell" you might be familiar with, it would be "adb logcat > 
WT-logcat.txt".  What this does is issue a command to output the LogCat and 
send it to a file (on your computer, in the directory you ran ADB from).  If 
you can attach or email that file to me, that will hopefully provide some 
insight as to what's happening.

If you're not comfortable with ADB, I believe there is also an app on the 
market (http://www.villainrom.co.uk/viewtopic.php?f=46&t=1322), that can gather 
the data using just the phone and allow you to send it to someone.

If that's not something you're okay with either, I will see about loading up 
the kernel he posted and see if I can reproduce it as well.  One thing to note 
is that King does mention he doesn't actually own an Evo currently, so I don't 
believe he can even test his kernels fully yet.

Original comment by dligh...@gmail.com on 18 Aug 2010 at 3:24

[GoogleCodeExporter]

Sorry still not working. It looks like it connects, and I can see new Local 
Area Connection 5 in status bar, but it ain't moving any packets nor can I 
connect to any website.

I use charge only, and even though I thought I already had the right driver, I 
even tried your link (tetherxp.inf) and installed.

Original comment by RFeuerl...@gmail.com on 18 Aug 2010 at 2:01

[GoogleCodeExporter]

Hmmm, that's peculiar, because I'm on a stock-rooted FroYo ROM almost identical 
to netarchy's (at one point, our uploads were racing to see whose would finish 
first).  When his finished first, I pulled it and compared and it's almost the 
same.

I'm guessing you haven't replaced the kernel with that, but if you have, can 
you let me know which one you're using instead?  (Otherwise I'll assume the 
stock kernel)

I assume from previous discussion that you're on Windows XP, is that correct?  
Which service pack level, and 32- or 64-bit?  You can find most of this by 
going to the System Properties (Windows key + Break is a nice shortcut, or 
right-click My Computer and Properties is handy; I believe there's a link in 
Control Panel as well named System -- I'm on Windows 7 so I can't confirm the 
name at the moment).

Also if you could attach (or email) a couple of outputs that would be 
beneficial as well.  The LogCat as mentioned above would be somewhat helpful, 
but if you could also do the following:

At a command prompt, do the command: ipconfig /all > WT-ip.txt
This will create a file named WT-ip.txt in the directory where you run this 
which contains a simple summary of your network configurations.

Thanks!

Original comment by dligh...@gmail.com on 18 Aug 2010 at 2:17

[GoogleCodeExporter]

I am using Windows XP sp3, 32-bit.

I have my HTC Evo 4G Evo rooted with Unrevoked3 and then upgraded to Froyo 
using "HTC OTA Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed, see thread 
here http://forum.xda-developers.com/showthread.php?t=743352.

When using "adb logcat > WT-logcat.txt", what USB connection do I have to be 
on, I was on Charge Only and it said "Waiting for device", even after switching 
to USB Drive. When switching to HTC Sync it could not find HTC Sync on my 
laptop, properly because something screwed up when I was trying to connect with 
this wired tether. Anyways "WT-logcat.txt" file said:

adb server is out of date.  killing...
* daemon started successfully *

And "WT-ip.txt" said:

Windows IP Configuration

        Host Name . . . . . . . . . . . . : laptop

        Primary Dns Suffix  . . . . . . . : 

        Node Type . . . . . . . . . . . . : Mixed

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Broadcom Wireless:

        Connection-specific DNS Suffix  . : 

        Description . . . . . . . . . . . : Broadcom 802.11g Network Adapter

        Physical Address. . . . . . . . . : 00-14-A5-42-F9-AF

        Dhcp Enabled. . . . . . . . . . . : Yes

        Autoconfiguration Enabled . . . . : Yes

        IP Address. . . . . . . . . . . . : 192.168.3.103

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 192.168.3.254

        DHCP Server . . . . . . . . . . . : 192.168.3.254

        DNS Servers . . . . . . . . . . . : 192.168.3.254

        Lease Obtained. . . . . . . . . . : Wednesday, August 18, 2010 9:59:13 AM

        Lease Expires . . . . . . . . . . : Wednesday, August 18, 2010 9:59:13 PM

Ethernet adapter Local Area Connection:

        Media State . . . . . . . . . . . : Media disconnected

        Description . . . . . . . . . . . : Marvell Yukon 88E8036 PCI-E Fast Ethernet Controller

        Physical Address. . . . . . . . . : 00-03-25-28-BE-45

Original comment by RFeuerl...@gmail.com on 18 Aug 2010 at 2:50

[GoogleCodeExporter]

Is it alright if I contact you by email?  I'll be in-and-out a bit as I'm at 
work, but I definitely want to help you get this resolved.

Original comment by dligh...@gmail.com on 18 Aug 2010 at 3:04

[GoogleCodeExporter]

Sure, you have it?

Original comment by RFeuerl...@gmail.com on 18 Aug 2010 at 3:21

[GoogleCodeExporter]

I think I have to join the project to be able to email you, but I can't find 
where to join project.

Original comment by RFeuerl...@gmail.com on 18 Aug 2010 at 4:33

[GoogleCodeExporter]

I'm new to the android development game, but how can i take the svn and package 
the apk for my phone to install? I've downloaded the r32 code, now I just need 
to figure out how to actually put it on my phone.

Thanks

Original comment by mcgrif...@gmail.com on 19 Aug 2010 at 3:06

[GoogleCodeExporter]

Mcgriffin, if you want just the application including revision 32, you can get 
it here: 
code.google.com/p/android-wired-tether/downloads/detail?name=wired_tether_1_3.ap
k&can=1&q=

If you want to build it yourself, though, I would have to get back with you as 
I don't have a setup for the native code, so Harald has done the build for me 
for now.

Original comment by dligh...@gmail.com on 19 Aug 2010 at 3:12

[GoogleCodeExporter]

Ah, thanks. I see my problem...1.3 is listed as depreciated, so I didn't see it 
in the 'current downloads' listing

Original comment by mcgrif...@gmail.com on 19 Aug 2010 at 3:17

[GoogleCodeExporter]

Yes, I believe the deprecated is because we are still in the testing stages 
with 1.3, so take caution and the usual "we are not liable" notes apply.

Also note that the kernel warning does still show in this version, but it has 
been fixed, patch sent, and will be included when it is next built.  In the 
meantime, you can choose to ignore the warning about the kernel, though, but 
still tread carefully due to the beta state, and let us know if things don't 
work.

Original comment by dligh...@gmail.com on 19 Aug 2010 at 4:10

[GoogleCodeExporter]

New version of the app:
http://android-wired-tether.googlecode.com/files/wired_tether_1_4.apk

Changes I made: r34

Original comment by harald....@gmail.com on 19 Aug 2010 at 7:24

[GoogleCodeExporter]

Awesome. Thank you. Will try in the morning. 

Original comment by sparling...@gmail.com on 19 Aug 2010 at 11:19

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

1.4 FCs for me, while 1.3 works with the exception of the incompatible message

Original comment by mcgrif...@gmail.com on 19 Aug 2010 at 12:05

[GoogleCodeExporter]

Mcgriffin, can you try fully uninstalling wired tether and then installing it 
again?  If you still get a force close, can you attach and/or email me a logcat 
just after it force closes?

Original comment by dligh...@gmail.com on 19 Aug 2010 at 2:14

[GoogleCodeExporter]

Hello,
I have tried both 1.3 and 1.4 with the same, mostly negative, result. I would 
appreciate any help.
I have Sync installed, so my computer doesn't require the whole driver process 
described above.

After starting wired tether, the starts trying to connect for a while, then 
throws a "Limited or No connectivity" error. 
The phone does popup a notification saying that "my_comp(MAC address)" is 
connected. However, there is no data transfer between the two.

After that I need to restart comp/phone to be able to see my phone (via "adb 
devices") to get the log file.

Might HTC sync have anything to do with it?

Running 32bit XP, with HTC sync, and rooted stock ROM.

Original comment by tim.bakh...@gmail.com on 19 Aug 2010 at 6:21

[GoogleCodeExporter]

I apologize for the double post.
Attached is the log file.

Original comment by tim.bakh...@gmail.com on 19 Aug 2010 at 6:32

Attachments:

• WT-logcat.txt

[GoogleCodeExporter]

I'm getting the same issue with 1.4 -- FC as soon as it's launched.

1.3 was loading but would never connect.

I'm running 64bit Win 7, HTC Drivers only, Fresh EVO 3.1.0.2 (froyo)

Original comment by cool...@gmail.com on 19 Aug 2010 at 7:02

[GoogleCodeExporter]

Just so everyone knows, I am indeed following all of the comments here and I'm 
trying to find commonalities as to why it fully works for some (myself 
included), partially works for others, and force closes on the rest.

I have a feeling the Force Close could be a kernel-compatibility issue in there 
somewhere.  The partially working may be connected to HTC Sync, though, as I 
haven't installed it myself and I'm not having any issues.  I'm not sure why it 
would interfere, though.  If anyone wants to try removing HTC Sync, rebooting, 
and trying Wired Tether again, that would be beneficial to find out if that's 
correlated; if not, I'll add that to my investigation list.

I apologize for the slowness, difficulties, errors, and troubles everyone is 
encountering; bear with me/us, as I'm finding the diversity of phones, ROMs, 
and kernels a bit more overwhelming to accommodate just yet, but I don't intend 
to give up. ;)

Original comment by dligh...@gmail.com on 19 Aug 2010 at 8:30

[GoogleCodeExporter]

Tried again on a computer w/o HTC Sync. Same result.
It issues an IP, but still "Limited or No Conductivity".
The app shows a couple of KB for Up/Download, but I can't pull any data or load 
webpages.

Win XP, SP3 (this time with tetherxp.inf drivers)
Rooted Stock 2.2, stock kernel.
Wired_Tether 1.4

Original comment by tim.bakh...@gmail.com on 20 Aug 2010 at 12:34

[GoogleCodeExporter]

Hmm, yeah I compiled a list of what's working and not working and nothing 
stands out 100%, though I have 2 symptoms in particular.  I'm actually going 
down a list of ROMs and Kernels to try; so far on my ROM (stock-ish), with the 
netarchy 4.0.2 kernel, it's working for me.  I'll finish my tests and post the 
results.

Original comment by dligh...@gmail.com on 20 Aug 2010 at 12:38

[GoogleCodeExporter]

I'm running fresh 3.1 with netarchys kernel and I get the same results as #21.

Original comment by zit...@gmail.com on 20 Aug 2010 at 4:22

[GoogleCodeExporter]

Regarding the log posted at #20: The only application I see crashing here is 
the superuser-app. Do other apps work which require root?

Original comment by harald....@gmail.com on 20 Aug 2010 at 11:35

[GoogleCodeExporter]

I have exact same issue as reported by tim.bakh...;
Comment 23 by tim.bakh...@gmail.com, Today (11 hours ago) 
Tried again on a computer w/o HTC Sync. Same result.
It issues an IP, but still "Limited or No Conductivity".
The app shows a couple of KB for Up/Download, but I can't pull any data or load 
webpages.

Win XP, SP3 (this time with tetherxp.inf drivers)
Rooted Stock 2.2, stock kernel.
Wired_Tether 1.4

Except after a few seconds showing "Limited or No Conductivity", it changes 
into an error free connection although still no real connectivity. Also it 
takes almost a full minute to resolve IP address, before initial "Limited or No 
Conductivity" is display.

Original comment by RFeuerl...@gmail.com on 20 Aug 2010 at 12:38

[GoogleCodeExporter]

Update time:  so last night I tried to do some extensive testing and I came 
away with some information at least, but not a solution just yet.

I was going through several ROM and kernel combinations and here's a short 
rundown of what I'm seeing:
- Wired Tether is currently inoperable with Fresh ROMs, and I know the 
reasoning somewhat (native code calls; believe the header/library in particular 
is missing in this case).
- Stock rooted ROMs with stock kernels show up with a connection, but it 
struggles to get to a data transfer stage
- My personal stock rooted ROM with stock kernel somehow works fine

I have some ideas as to the parts in play that are interfering somehow, but I 
haven't nailed down a solution quite yet -- but I have ideas to work with on 
both the Fresh ROMs and the Stock ROMs.  I won't be able to do much for now, 
but I'll dig in deep again this evening.

Original comment by dligh...@gmail.com on 20 Aug 2010 at 1:22

[GoogleCodeExporter]

Harald,
Regarding the log at #20: Wired Tether doesn't crash for me. The connections 
just doesn't transfer anything. It looks like Rene's description is identical 
to mine (#23 and #27). Mine also takes longer than expected to resolve IP.

Original comment by tim.bakh...@gmail.com on 20 Aug 2010 at 6:11

[GoogleCodeExporter]

Tim,

I've encountered that behavior when I've tried alternate ROMs and kernels, so 
apparently something I have done has corrected that.  I'm not trying to step 
backwards into finding what change(s) I made resolve that.

Originally when I provided a patch to Harald (that became part of 1.3), I knew 
it worked for me and really didn't think my setup was that different, so I 
assumed it would be a pretty easy, golden fix for the FroYo Evo users in the 
house.  Unfortunately, something in the little deviance I had from netarchy's 
ROM cleared this up, so now I have to find it.

Depending on how much free time I have this weekend, I plan to do some heavy 
investigation (piece by piece) to nail this down.  I suspect it relates to the 
built-in tethering that was to come with FroYo mixed with Sprint overlapping 
the hotspot functionality they want you to pay for.  I've been looking at the 
internals of this app, CyanogenMod, and native FroYo.  Bear with me; we'll get 
there.

Original comment by dligh...@gmail.com on 20 Aug 2010 at 6:24

[GoogleCodeExporter]

I haven't installed this yet, but I would be willing to help the testing. 
Dlightle, let me show you some appreciation by giving the effort you're giving. 
Thank you. I'm not affected, but I can see you are truly concerned & attempting 
a solution.

Original comment by LAY...@gmail.com on 20 Aug 2010 at 8:37

[GoogleCodeExporter]

Regarding the "no connection" issue:

What happens if you execute below command AFTER you have started tethering in 
terminal-emulator on your phone?

/system/bin/ip route add table gprs 172.20.23.252/30 dev usb0 proto kernel 
scope link  src 172.20.23.254 

(it's probably easier if you first put that one in a script and execute the 
script because you won't have adb after the tethering-start.)

Original comment by harald....@gmail.com on 20 Aug 2010 at 10:02

[GoogleCodeExporter]

I would gladly execute that, except I know nothing about terminal-emulators or 
running scrips on my phone.

I'll go try to figure this out, but if you can give me some instructions or 
directions, that would be great :)

Original comment by tim.bakh...@gmail.com on 21 Aug 2010 at 1:57

[GoogleCodeExporter]

Also, what is that script supposed to do? Just curious.

Original comment by tim.bakh...@gmail.com on 21 Aug 2010 at 2:29

[GoogleCodeExporter]

So I got Android Terminal Emulator and ran command you mentioned. The result:

RTNETLINK answers: invalid argument

I'm pretty sure I got the command right. Does that help or make any sense?

Original comment by tim.bakh...@gmail.com on 21 Aug 2010 at 2:44

[GoogleCodeExporter]

Tim,

That's for routing your network traffic, so it knows to go from WiFi/3G to your 
phone's USB port, to your PC and vice versa.  I output the routing table and it 
appears to already be setting this value correctly, so I don't think that's it 
(but I could easily be wrong).

Original comment by dligh...@gmail.com on 21 Aug 2010 at 2:46

[GoogleCodeExporter]

It appears I have found a fix for the connectivity issues.  The problem seems 
to be with the standard IP binary.  A quick fix is to use a symlink to toolbox 
or busybox.  I'm attaching an update.zip (flashable through a custom recovery, 
signed for Amon Ra as well, no wipe required).  This should fix the 
connectivity part.

As for Fresh and those variants, it appears that the issue is due to multiple 
libnativetask.so as mentioned by Josh H. on XDA.  I think Fresh includes the 
libnativetask.so for Wireless Tether, which means you should be able to delete 
the libnativetask.so from /data/data/android.tether.usb/lib/libnativetask.so

Let me know if these two solutions don't fix the issues for everyone.

Original comment by dligh...@gmail.com on 21 Aug 2010 at 10:25

Attachments:

• SignedWiredTetherFix.zip

[GoogleCodeExporter]

Eureka!

Excellent work! Writing this on my wired tether connection!

THANK YOU VERY MUCH!

Original comment by RFeuerl...@gmail.com on 21 Aug 2010 at 10:48

[GoogleCodeExporter]

I am (was) currently downloading at about 200KB/s over 3G, and was just 
wondering about your comment "That's for routing your network traffic, so it 
knows to go from WiFi/3G to your phone's USB port".

What about 4G? I am asking because I forgot I had turned my 4G off, so I turned 
it on while I was downloading at about 200KB/s, one in browser and two torrents 
via client, and it slowed to a crawl, actually my download in my browser 
halted, only my two torrent in uTorrent seem to keep transferring a bit at 
about 10KB/s. As soon as I turned off 4G again, I was able to restart my 
download in the browser at 140KB/s, while the two torrents proceeded at about 
60KB/s.

Both my 3G and 4G connection was with 4 bars.

Original comment by RFeuerl...@gmail.com on 21 Aug 2010 at 11:26

[GoogleCodeExporter]

Interesting in hearing other user's experience with this. After about two hours 
of being connecting this morning, all transmission stopped, and I am not 
talking about the above mentioned 4G issue. So I stopped and restarted the 
wired tether app, and it worked again for another two hours all while 
downloading, until it stopped again, and this time my HTPC lost it's USB port 
so I had to reboot it, actually it would not shut down so I had to force it. 
Now after reboot my USB ports are back, I am again connected to my phone and 
downloading. Will keep track of how long it works this time uninterrupted.

Original comment by RFeuerl...@gmail.com on 21 Aug 2010 at 4:00

[GoogleCodeExporter]

Hello again Rene!

The routing should be the same across all the data connections (so when I said 
WiFi/3G, that really is more like WiFi/2G/3G/4G/etc.).  Think of it as a 
software router basically I believe.

So I see a couple of issues in your last comment:  tethering internet activity 
stops/crawls after 2 hours, and sometimes your connection doesn't get fully 
removed which causes some temporary system mangling (fixes at reboot, but won't 
even shutdown).

I can say that I experienced the second part a few times myself, but I didn't 
see it toward the end of my testing at all so I thought everything else 
resolved this as well.  It's extremely annoying, that's for sure.  I have an 
idea on a fix here, but I'm not sure it's a full fix and I'm not 100% sure on 
what's causing it (since it stays only some of the time).

On the first issue, though, I initially thought maybe the DHCP lease was 
expiring, but it looks like it's set to 12 hours in the dnsmasq.conf.  I'm not 
sure if that's a special case, or if others are having that issue as well.  
That will be a harder one to test, if it needs two hours to reproduce. ;)

As to the slowdown of 4G, have you tried stopping USB tethering, enabling 4G, 
and then enabling USB Tethering (not changing your data connection while 
tethering is active)?  If this fixes it (and if you can reproduce the problem 
by changing while active), I have an idea what could be happening, but the fix 
would be more extensive I think.

Original comment by dligh...@gmail.com on 21 Aug 2010 at 5:45

[GoogleCodeExporter]

This time connection stopped almost exactly after one hour, but stopping and 
restarting the app worked.

Yeah I was thinking about your suggestion for the 4G issue, but had not gotten 
around to test. But now that I did, I understand that it how it's to be done - 
It works, I just hoped to see higher download speeds that with 3G and it seem 
exactly the same.

Original comment by RFeuerl...@gmail.com on 21 Aug 2010 at 5:54

[GoogleCodeExporter]

Ok did several tests at Speedtest.net on HTPC via USB Tethering and this app 
v1.4 plus fix.

4G fluctuating between 2-4 bars

Ping: 315, 333, 332, 313ms
Download: 2.2, 3.23, 3.24, 1.32, 3.22Mb/s
Upload: 0.09, 0.12, 0.14, 0.16Mb/s

Anyone have a suggestion of a better, more reliable test?

Original comment by RFeuerl...@gmail.com on 21 Aug 2010 at 6:10

[GoogleCodeExporter]

Rene, can you do the same tests on the phone (with tethering off) as when 
tethering?  Just to see if that's how fast the phone is going, or if the tether 
is throttled somehow.

I think the speedtest.net website (over the speedtest.net app) is the current 
common test being used anywhere I see.

Original comment by dligh...@gmail.com on 21 Aug 2010 at 6:13

[GoogleCodeExporter]

Sure will do, but currently downloading a file as a test. Downloading at about 
125-145KB/s and should be done in about 12 minutes. Off course this is not a 
very scientific test, as this is most likely throttled from site 
(RapidShare.com as free user, but I get files there frequent and just wanted to 
see the speed.

Original comment by RFeuerl...@gmail.com on 21 Aug 2010 at 6:19

[GoogleCodeExporter]

Speedtest.net via HTC Evo 4G Froyo rooted, no USB connection are wired/wireless 
tether apps running.

4G connection with 3-5 bars

Ping: 141, 212, 151ms
Download: 2.36, 2.52, 4.66Mb/s 
Upload: 0.27, 0.09, 0.46Mb/s

As you might guess, on the last test I had 5 bars. Ping times through wired 
tether seems to be the only one suffering.

Original comment by RFeuerl...@gmail.com on 21 Aug 2010 at 6:41

[GoogleCodeExporter]

Running Freshs latest and still with both fixes mentoined and files loaded I 
get the same kernel error????? I checked those locations for the .so and its 
not located now in either?

Original comment by rjmj...@gmail.com on 21 Aug 2010 at 6:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi rjmjr69!  The .so needs to exist in one or the other (not both and not 
neither obviously), so I'm not sure what exactly happened, but if you can 
download the libnativetask.so from here: 
http://android-wired-tether.googlecode.com/svn/trunk/libs/armeabi/libnativetask.
so

Then you can put it either in the /system/lib folder or in the 
/data/data/android.tether.usb/lib folder.  Let me know if that doesn't work or 
if you need a hand.

Original comment by dligh...@gmail.com on 21 Aug 2010 at 7:00

[GoogleCodeExporter]

HALLELUJAH, 
Just got home after the weekend to find this beautiful treat in form of a .zip 
file. I have no idea what "use a symlink to toolbox or busybox" really does, 
but it works.
I haven't used it long enough to see if I have the some problem and Rene with 
stalled connection after 2 hours, but so far it works great.

Thank you Harald and dlightle so very much. This is awesome, you're awesome!

Original comment by tim.bakh...@gmail.com on 23 Aug 2010 at 7:12