yashsingh1/xdaforums huggingface dataset:
[EVO 4G Themes and Apps] scottspa74:
I get same as fua1. 'Limited or no network availability'. I. clicked on 'view diagnostic log' on a Windows pop-up, but that was unresponsive. I tried 'diagnose connection error', but that just seemed to stall and produce nothing. Pop-up on bottom right of taskbar said '...problem occurred because network did not assign a network address...'

I don't know if any of this is useful info to you.

I'm on xp 32-bit. No drivers were asked for. I'm trying your v1.4. I used to use v1.2 before froyo, and worked flawlessly.

Don't know if any of this helps, but hope you can get it worked out. God, I miss wired tether. I don't know anything about adb, so not sure how to get you logs. I hoped that first window I encountered would produce one, but as I said, it was unresponsive.

Oh, I'm rooted, and on netarchys stock 2.2 odexed final, using his 4.0 kernel (the first one actually based on froyos 'official' kernel)

Oh, the 'Down' and 'Up' monitors on Evo screen showed 'up' increasing (while tryin to diagnose) to 20.6+, and 'Down' seeming to stall out at 2.7. Again, hope any of this helps. Thanks for your efforts.
[EVO 4G Themes and Apps] davidlightle:
Were you running as root? I don't know if it's necessary off the top of my head, but I believe the root user may get a more accurate listing of the iptables. In theory, you should see a handful of lines if the iptables setup correctly.

If you were running as root, though, can you do a check to see which iptables binary is getting called? The command should be "which iptables" so long as it recognizes the which command -- that may be provided by busybox.

Just for some perspective, I'm using XP 32 bit, no HTC Sync, and 1.3 worked (with kernel warning) and 1.4 works perfectly (including connectivity).

I'm starting to wonder if HTC Sync is having a part in the complications, though I don't know why it would exactly. My next thought is that the network traffic isn't being properly tunneled to the computer from the phone. I'll do some digging around this; if in the meantime you want to remove HTC Sync and try again, that could be useful, too. Hang in there!

That was actually extremely helpful! It looks like you're close to working (the monitor values change); originally with 1.2, the values were pegged at 0.0 on both, so I knew it wasn't close to working; once I found my solution, I tested it, and the values moved, and I got the notification on the phone. The small difference is that mine didn't give the connectivity issues and such. Now to find out why.

I'm running a ROM similar (almost identical) to netarchy's, but with a stock kernel; I have a feeling I may need to nandroid and try a half-dozen setups to see where these issues are stemming from exactly. I have a lot of thoughts, but nothing that points me in a conclusive direction just yet.

As to the logs and commands, don't worry too much if you can't find/get them; LogCat can be gathered in several ones, and a simplified one is an app called aLogCat on the market (I've never used it myself but read about it), and most commands can be used in any of several terminal-like applications (ADB, ConnectBot, etc.). If it's a little too technical, don't worry about it, as I'm not sure what information is the most beneficial just yet. Thank you for providing all the information you already have, though!

I'll try to do some more enlightening discovery tonight, if I can find the time to do so. I'll keep my eye on here and the issue tracker (and my email) and I'll be thinking on the issue plenty.
[EVO 4G Themes and Apps] XevoX:
Wired Tether 1.4 is working perfectly for me! :D

I'm using netarchy's 4.1.7 kernel and SteelH's Froyo RevE.1 ROM. PC is running Windows 7 Ultimate. I did not have to install drivers either, however I've had HTC Sync already installed.
[EVO 4G Themes and Apps] fua1:
First, thanks a bunch for all you help!!!

So I tried on another computer without sync, and, unfortunately, same result.

"Limited or no conductivity". I posted the details on the issue tracker.

I can provide the log files, if you think them might be helpful.
[EVO 4G Themes and Apps] davidlightle:
Not a problem!

Yeah, I started compiling a list of everyone's ROM, kernel, OS, and HTC Sync status; nothing stood out as 100% the cause, but there are a couple of 90% commonalities, so I'm going to test a few things. I'm actually running through a series of ROMs and kernels to do my own testing to see if I can break it myself. On my list, though, HTC Sync didn't seem to prove more or less symptomatic, so (as I almost expected) I don't think it's a cause.

So far I'm not too far along, but my personal ROM (netarchy-like) with netarchy's 4.0.2 ROM is working.

Stay tuned for more updates!
[EVO 4G Themes and Apps] fua1:
Maybe I should try netarchy's kernel. It looks like the positive reports are from non-stock kernels. Or maybe I'm missing someone.

Either way, I'll be eagerly lurking here.
[EVO 4G Themes and Apps] davidlightle:
Well, personally, I was having the best luck with stock ROM (slightly deviated), and stock kernel. Netarchy 4.0.2 seemed okay, but once I tried 4.1.6 I ran into a problem -- I need to go back and test for it in 4.0.2 as I don't know how to reproduce it exactly but it reoccurs easily at least. Basically tethering worked fine sometimes, but at a certain point it could remain somewhat behind (leaving a network connection on the PC) and then the USB on the phone and the network connections totally die. So I've confirmed that somewhat. I'm still investigating for now, but at least I'm able to see it firsthand.
[EVO 4G Themes and Apps] fua1:
Hmmm, well I'm all stock, except rooted.

Running ADW launcher though, but I can't imagine that would be of any consequence.

Would log files be useful to you?
[EVO 4G Themes and Apps] scottspa74:
First off, massive, massive thanks to Davidlightle for working on this.

Strange that one poster said worked on netarchy 4.1.7 kernel with steelH ROM, but OP reported couldn't make it work on 4.1.6 netarchy kernel with stock-like ROM.

I will probably check out 4.1.7 too to test, if it sounds stable.

Thank you sooo much for working on this though. I will be glued to this thread, far more than any other (thread).
[EVO 4G Themes and Apps] davidlightle:
Okay, a little progress. It appears that Fresh builds are Force Closing due to the native code being used in Wired Tether; I believe a required header/library is missing in Fresh. I have some thoughts on this, but we'll have to see.

As for my testing otherwise, I've tried my ROM with Netarchy 4.0.2, 4.1.6, and 4.1.7 and while each worked, the USB connection can be left in a broken state after usage.

I'm about to go through the paces with Netarchy's Rooted Stock ROM and SteelH's Deodexed Rooted Stock ROM, but I expect the results to be similar so far.

This still doesn't explain the connectivity or no/slow internet access, though.

Well, log files never hurt, but since I'm digging into the ROMs myself, hopefully I can get equivalent logs firsthand. But if you have them readily available, feel free to shoot them my way.

I apologize for the slow progress; I'm digging in deeper than I ever have with Android/Linux and I really expected this to work much simpler than this.
[EVO 4G Themes and Apps] davidlightle:
Alright, morning update: I spent a lot of time last night extensively testing combinations of ROMs and kernels to see if I can get the same results and I think I can reproduce most everything I've seen.

Fresh ROMs are currently not compatible with the current Wired Tether. This is due to the native calls and assumedly a missing header or library.

Stock rooted ROMs with stock kernels definitely experience the lack of connectivity issue. I still need to test netarchy's kernels with the full stock rooted ROMs.

I tried my custom ROM, stock kernel and it works (I need to retest a small piece to compare against the other kernels, though). With 3 variations of netarchy's kernel on this ROM (4.0.2, 4.1.6, 4.1.7), the connection still worked, but I experienced some scenarios where the connection would linger and the PC and phone both would end up in a mucked up state requiring reboot.

I have some thoughts on how to fix both parts, and I'll dig into them this evening.
[EVO 4G Themes and Apps] DrawnToScale:
What advantage does Android Wired Tether give you over PDAnet?
[EVO 4G Themes and Apps] davidlightle:
It's mostly an alternative rather than advantages and disadvantages. Wired Tether is free, open-source, and doesn't require any software on the computer other than drivers; PDANet is free for HTTP only (non-secure sites) and $$ for the paid version, closed-source, and requires software on the computer.

Currently I have both wired and wireless tether apps, but if the wired weren't working, I could just plug in anyway (for battery charging) and run the wireless. The wired is convenient, though.

I'm not trying to say "choose this, down with PDANet" or anything. Just it's nice having alternatives that suit a larger variety of needs.
[EVO 4G Themes and Apps] kmartburrito:
Thanks for all of your help on this!!

I'm anxiously awaiting a Fresh compatible version, although I'm not opposed to frankensteining something if need be.

All I've ever wanted since the Evo and Hero came out was Wired Tether to work with it properly :D
[EVO 4G Themes and Apps] JackDaniels7:
same i want this ported as well
[EVO 4G Themes and Apps] Josh H.:
HALBERT SPEAKS!!

Alright, ego aside, I fixed the Fresh ROM issue (I'm actually using Fusion 2.5, but it seems to have the same FC-ing issue).

The problem:

1) Wired tether uses a "libnativetask.so" library file that is contained within its own .apk.

2) Fresh and similar ROMs have "libnativetask.so" in the system/lib/ folder within the ROM itself, stock ROMs do NOT have this.

Don't ask me why, but Wired Tether likes its own .so file more than your system's .so file.

The solution? DELETE /system/lib/libnativetask.so

I've attached a BEAUTIFUL .zip that will do it for you if you are so inclined as to use it.

Disclaimer: use at your own risk, blah blah blah, and... I'm personally still working on the no connectivity issue, but this will keep wired tether from FC-ing, and let you try for yourself.

Enjoy! (And someone else please confirm the fix as well!)

Edit: Remember to only use this for the FC issue. The connectivity fix was posted by davidlightle on the next page.
[EVO 4G Themes and Apps] fua1:
Nice find.

Is this Fresh specific? I only have two "libnativetast.so" files located in /data/data/android.tether./lib and ...android.tether.usb/lib. Running stock rooted.

Not sure if this is relevant, but there it is :)
[EVO 4G Themes and Apps] Josh H.:
Stock rooted doesn't have the problem lib file (the one in system/lib). So far, it seems Fresh and Fusion DO have it, and thus are causing wired tether to FC.

Still don't know why I can't get internet access through it though...
[EVO 4G Themes and Apps] rjmjr69:
Will try it out thanks
[EVO 4G Themes and Apps] davidlightle:
Hi Josh, thanks for helping out. I'm a little over my head with some of this, but it sounds like I was kind of on the right track. Is it safer/better to remove the system libnativetask or the one under android tether? (What happens if a different app uses the system-wide one?)

On the internet access, here's something I'm trying to work through but struggling:

I'm on WiFi, trying to run Wired Tether, it either doesn't connect, or struggles to get a connection, but no data goes across. If I use the USB Tethering option from HTC, I quickly get an IP address for the connection and internet works. (Not so on 3g, though, the Error 67 then)​

So what could we be forgetting to do that the native functionality does?

Also, a stock rooted ROM has these issues, but one where I've stripped some APKs out, altered some system/bin symlinks (to use busybox instead of toolbox), and possibly some other pertinent changes I can't think of, there it connects fine and works great (WiFi and 3g with Wired Tether).
[EVO 4G Themes and Apps] v_lestat:
after renaming NOT deleting the libnativetask.so wiredtether opens very quickly without installing or starting anything.

when i click to start tethering, it says could not start tether.....

i was getting the FC prior to the renaming of the libnativetask.so

**ok so i have uninstalled and reinstalled and its opening and starting properly now

BUT

the pc is connecting and getting the IP string i stipulated in the phone settings, and the phone does buzz at me and tell me i am connected but there is ZERO dns resolving going on....

this is my entire 100% issue (and maybe alot of peoples) as far as i can tell of why its not working...

the log says DNSMASQ started but it either is and just isnt working, or it wasnt installed or started and thus isnt working.

i am using Calkulin's EViO 2 1.1 ROM w/ netarchy toastmod 4.0.2

just tried it on my laptop which doesn't have any adb or htc phone drivers and it wants the drivers. in fact it wants ADB and HTC Phone drivers.

hmm thought this didn't require drivers...???
[EVO 4G Themes and Apps] Josh H.:
On your first point, I think if we stripped the libnativetask out of the app itself, everything would break... it seems to me that it just can't be in system/lib for whatever reason or we will get the FC.

Secondly, I think you're on to something with the ROM modifications that you're doing... we just need to narrow down which apk or whatever is causing our issues. We need to ask ourselves: what is the difference between this ROM where it works and that ROM where it doesn't...

As far as the libnativetask in the system folder, I'm at a loss as to why it's even there in the first place. Stock ROMs don't have it, but Fresh/Fusion ROMs do (that's the only reason I risked deleting it in the first place). I haven't noticed anything else breaking as a result of deleting it.

That said, it could be that whatever may or may not depend on that libnativetask in the system/lib folder is the cause of the rest of our problems as well. Maybe that's too convenient, but again, we need to figure out what is different between working ROMs and non-working ROMs.
[EVO 4G Themes and Apps] davidlightle:
Yeah I was just thinking, if they possibly (probably unlikely) were the same code, just ported from one location to another for similar purpose, as long as the app can find the library on the path, it would still function, while leaving the others that depend on it (if any?) working.

The libnativetask part that is breaking is the getProp method, and I see there is a symlink to toolbox that achieves the same thing, so there may be a way to remove that part of Wired Tether's libnativetask, but that's only half of it so I don't know that that matters.

Yup, this is the approach I'm taking right now, but it's tricky so far. I tried removing the same apps live (after loading the ROM), and wiping the dalvik-cache, but that didn't fix things. USB Tether over WiFi still works while Wired Tether over WiFi doesn't. I'm now trying a stripped-before-flashing ROM (closest to how I did it), to see if that's the trick. From there, I'll try to narrow things down, but it'll take some time for sure.
[EVO 4G Themes and Apps] v_lestat:
well the tether screen shows minor upload activity and the download activity is only 2-3kb

what i see the browser on the pc doing is trying to resolve the address and it not being able to....

i tried to ping the Def. Gateway and DHCP Server list on my adapters ipconfig properties and it can not ping them.

The gateway not being pingable concerns me more than the DHCP server not being pingable.

if probably is a rom vs rom issue but the fact that the dns is not resolving and the gateway isnt pingable has to mean something.

in networking it does, but with this app i dont know.

***edit 1**

scratch all the resolving, its resolving it just cant ping anything at all...

ping something and it will resolve it but it just wont ping it.

so... its making it so far as DNS but thats all....?

**edit 2**

rebooted the phone and wiped and restored back to FREAK E Froyo and now its not resolving anything.

not even using a manual DNS server on my laptop.

wiiiierrrrdddd.....

i even copied the libnetwork.so (or whatever it was) from the android usb tether folder to the system/lib folder and it didnt make any difference.

think i am going to try the stock deodexed i have and see what it does.

***edit 3 and then i am off to bed.

I installed SteelH's stock 2.2 deodexed ROM.

the libnativetask.so is not in the system/lib folder.

tethering still does not work....

ping does not result in anything but request times out.

ping a www or any .com and it can not resolve the host, and it tells you it can not resolve it

pinging the gateway or dhcp server is the same thing, no response....

Windows says i have a network connection but no internet access

is there a usb driver or something i am missing here guys?

on my laptop i installed HTC sync and it installed the HTC Remote NDIS based Device under my network devices.

the fact that it connects to the phone, the phone sees it, ad connects to it, and dishes out DHCP says that much is working, but the app is just not letting traffic out to the internet
[EVO 4G Themes and Apps] davidlightle:
Hi v_lestat, I think I may have discovered the solution, testing it now. If you want to join in testing, let me know. You have to have to do a couple of simple terminal commands on the phone (ADB, Terminal Emulator, SSH, etc.), and you need busybox (most ROMs now have it I think anyway).
[EVO 4G Themes and Apps] Josh H.:
I'll join in testing too if you like, feel free to PM me.
[EVO 4G Themes and Apps] davidlightle:
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.. 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.

Edit: Just tested working with Netarchy's Stock Rooted Odexed 2.2 ROM, SteelH's Stock Rooted Deodexed 2.2 ROM, and Fresh 3.1.0.2, using the SignedWiredTetherFix.zip for all and for Fresh also just removing the /data/data/android.tether.usb/lib/libnativetask.so (since a copy resides in /system/lib as well).
[EVO 4G Themes and Apps] Josh H.:
This certainly works!

So just to recap for anyone who wants the fix:

If you are having FC issues (Fresh style ROMs), it is because you have duplicate libnativetask.so files. One needs to be deleted (either manually, or you can use the update.zip I posted earlier to remove the one in system/lib).

Further, if you can connect but have no internet access, it is probably because your ROM does not have the required symlink (as further described by davidlightle above). The fix is to simply flash his attached update.zip.

After implementing either one or both of these fixes, your wired tether will be permanently fixed (until you wipe/reflash/etc of course). Hopefully we can get some of the ROM devs to build these fixes into later releases so we don't need to do this anymore.

Thanks to everyone for their tremendous effort!
[EVO 4G Themes and Apps] v_lestat:
David it was late last night and i had to crash... sorry i missed out on the testing i would have been happy to help out.

David you are the sh|t man,, fracking awesome.

one last question.

in order to tether ANYWHERE anytime, what usb drivers do i need to store on my mSDCard so that i can use them to install the phone where ever i plug my phone into ?

there was a small package containing the inf and drivers floating around but i haven't the slightest clue what thread i saw them in.

also, and this i my personal preference.

i use root explorer to "open in text editor" the resolve file under the usb tether/config folder and removed the sprint dns servers and replaced them with the google dns servers

8.8.8.8 and 8.8.4.4

yeah baby!!! upload speeds suck this morning, but download speeds are normal for me for this time in the morning, in a short while they will drop by about 1/2. uploads are usually 600-700kbps.

this is a sprint issue not tether issue.
[EVO 4G Themes and Apps] v_lestat:
p.s.

anyone had the chance to test on 4G yet ?
[EVO 4G Themes and Apps] jester95:
Works in San Antonio 4G
[EVO 4G Themes and Apps] davidlightle:
On the Wired Tether page, the FAQ has comments that direct to this thread for the driver package.

Also, Google has listed the driver INF (but the driver details are just on your OS already). If you want this approach, but with the driver details, you can find what files are in use by going to the device manager, checking the RNDIS device's details, and it lists the driver files. For the most part, you should only need to carry the INF with you. The driver INF works for XP; Windows 7 picks up the tethering drivers automatically; Mac isn't listed by the Android Team as supported; and I believe Linux picks it up natively.

No problem! I was doing a bit more extensive testing this time, so I was a bit slower to hit the forums. I was pretty sluggish by the time I wrapped up myself. ;)
[EVO 4G Themes and Apps] scottspa74:
Awesome, man. Thank you. About to test. Did I understand this though? Unlike wired tether using Android 2.1, this fix requires you to install drivers, or inf file to the host computer? Just curious. Thanks for everything, you da man Davidlightle

About to test.
[EVO 4G Themes and Apps] davidlightle:
This does require drivers, but the previous version did, too. It just so happens that the bulk of the drivers already exist on Windows (XP and on), so you only need a "driver definition file" that tells it which driver files to use and such. That's all the tetherxp.inf does. (Windows 7 doesn't even need the tetherxp.inf as it recognizes the device natively and knows which files to use)

Drivers are just so the computer knows how to communicate with the hardware, so it's required for any hardware device -- just sometimes it's more seamless and hidden-from-view.

If you had the previous wired tether (1.2) working, this shouldn't be any different once you install it and do the fix(es). If you have problems, though, I'm around. ;)
[EVO 4G Themes and Apps] mikevillarroel:
I did everything, no more errors, no more FC. now.......the stupid question.......how do i know I'm tethering? i mean its supposed to auto connect? or do i have to create a new connection?

Sorry for my ignorance!
[EVO 4G Themes and Apps] jester95:
Auto connects for me using windows 7, windows xp, and ubuntu 10.04

Using Fresh 3.1.0.2, stock kernel, and wired tethering 1.3
[EVO 4G Themes and Apps] davidlightle:
There's a 1.4 version now that should eliminate the kernel warning, just FYI.
[EVO 4G Themes and Apps] mikevillarroel:
May be because i'm using Netarchy's kernel it won't work?
[EVO 4G Themes and Apps] mikevillarroel:
1.4 FC in mine!
[EVO 4G Themes and Apps] jester95:
I tried....got a FC.

1.3 still gives the normal unsupported kernel...but click "close" and it works just fine.
[EVO 4G Themes and Apps] davidlightle:
Did you see/do Josh H.'s fix for having multiple libnativetask.so files? If so, I'll try to track down this new error causing the FC; if not, you can try it if you like, to avoid the FC and the warning both.

Are you on Fresh Evo ROM? If so, see above; if not, can you send a LogCat just after it happens?